Well, following what I thought was a successful migration, it turns out nothing in any of our hosted site's cgi-bin is working. trying to access any of them gives a 403 error and the following in the site's error_log:



(don't let the reference to .htaccess fool you -- this is a generic error. There is no .htaccess - the script I'm testing with is just a hello world script)

There's nothing in suexec.log

Just for once, the great god Google does not help me, nor does any KB.





If I chmod cgi-bin to 755 it works fine. However, this is not how it is supposed to be.

So this is some sort of permissions thing.

I do note suexec doesn't seem to be different to the default one:



There's another one in /usr/local/psa/suexec that's a different size:



In the old days, I seem to remember there were problems with the plesk-centric suexec being overwritten when suexec got updated by yum, and you were supposed to copy it back from somewhere.

I'm wondering if the psa-suexec should be copied over to /usr/sbin/suexec?

Can someone check the sizes of theirs for me please? I'm on EL6 x86_64 with Plesk 10.4.4 MU26

And any other suggestions would be appreciated!!!!!

OK, well I went ahead and copied the psa-suexec over the suexec and restarted apache, but no difference.

Interesting.

Seems cgi-bin needed to be chowned ftpuser.psaserv (not 755, obviously, and not ftpuser.psacln which is what was causing the problem)

It isn't clear where this issue came from - a Plesk bug or a Migration Manager bug.

Have noticed similar permission/ownership issues with group name "psaserv" vs "psacln" since migrating to 10.4 which I never encountered previously.
Plesk directories are supposedly set to "psaserv" group, and files to "psacln" group, in practise they are all set to psacln when using ftp and I suppose migration manager is affected also.
Glad you were able to resolve the issue.

Thanks Kalimari.

In a way, I'm glad the migration manager doesn't try to fiddle with ownerships or permissions -- I might have set them in a certain way. On the other hand, it seems to me that there's a big bug somewhere because this has happened on three systems, all 8.6 -> 10.4.4 so there's obviously something being missed somewhere. On the other other hand (i have three) there's also no reference to this in an KB or even on the forum, so I wonder if I've found some new little twist that needs to be looked into.