centos suexec breaks scripts from running bad!

[105547111]

Damn suexec is blocking my scripts and causing issues.

[2011-02-25 08:58:28]: uid: (10001/aus-city) gid: (505/psacln) cmd: ultimatebb.cgi
[2011-02-25 08:58:28]: target uid/gid (10001/505) mismatch with directory (10001/504) or program (10001/505)
[2011-02-25 08:58:45]: uid: (10001/aus-city) gid: (505/psacln) cmd: ultimatebb.cgi
[2011-02-25 08:58:45]: target uid/gid (10001/505) mismatch with directory (10001/504) or program (10001/505)
[2011-02-25 08:59:01]: uid: (10001/aus-city) gid: (505/psacln) cmd: ultimatebb.cgi
[2011-02-25 08:59:01]: target uid/gid (10001/505) mismatch with directory (10001/504) or program (10001/505)
[2011-02-25 09:00:01]: uid: (10001/aus-city) gid: (505/psacln) cmd: auto_pickup.pl
[2011-02-25 09:00:57]: uid: (10001/aus-city) gid: (505/psacln) cmd: mail.cgi
[2011-02-25 09:01:27]: uid: (10001/aus-city) gid: (505/psacln) cmd: mail.cgi

How can I fix this. For now I renamed /usr/sbin/suexec to suexec.disabled and restarted httpd, atleast stuiff runs!

What's a proper way to fix it?

Thanks!

 

[daveparrish]

I am having the same problem with a fresh VPS on HostGator. It is setup with Parallels, Plesk and CentOS 5.6.

I found this blog entry which helped me fix the issue, but I don't know why the issue occured at all.

http://philipalex23.blogspot.com/2011/04/cgi-files-showing-500-internal-server.html

 

[105547111]

I found if your got scripts that break, the best way to disable it is to edit your /etc/httpd/httpd.conf

find and change calling up the suexec by adding '#' in-front:

#LoadModule suexec_module modules/mod_suexec.so

Now apache runs without suexec

 

[daveparrish]

Good to know. I never mentioned what I did. I basically copied the psa version of suexec over the running version.

cp -arf /usr/local/psa/suexec/psa-suexec /usr/sbin/suexec

So far it looks like it is working fine for my issues with PHP and suexec can still run. Although, I don't know why I need suexec to be running at all. Perhaps it is more trouble than it is worth.

 

[105547111]

I found with dada mail it breaks bug time if you want cron running discussion lists. Basically it's failing as cron is trying to call apache to check the mailboxes and relay any messages that are new.

Anyway if suexec does give you grief if you edit the httpd.conf as I suggest, then restarting apache not bring upnan error like other people say to rename the actual file. That results in the module not loading but an ugly error message sayingnit can't find it.

I also had issues with my forum and posting images due to suexec.