July 29, 201016 yr I just tried the new Perl/Cgi Feature in Froxlor 0.9.11 but i got an 500 Error when executing my test.cgi (hello world) script. I looked into the error logs: customer-error.log [Thu Jul 29 11:06:32 2010] [error] [client 89.202.163.174] suexec policy violation: see suexec log for more details [Thu Jul 29 11:06:32 2010] [error] [client 89.202.163.174] Premature end of script headers: test.cgi suexec.log [2010-07-29 11:06:32]: uid: (10001/web2) gid: (10001/10001) cmd: test.cgi [2010-07-29 11:06:32]: command not in docroot (/var/customers/webs/web2/abauer/test.cgi) Imho this means the script cant be executed in /var/customers/webs because its not in /var/www but suexec is compiled for this directory. Does this mean in need to recompile suexec to get the new perl feature work?
July 29, 201016 yr Does this mean in need to recompile suexec to get the new perl feature work? Yes, or deactivate suexec
July 29, 201016 yr Author I found another solution. 1.) create a directory /var/www/cgi-bin (owner root / chmod 0701) 2.) create a directory /var/www/cgi-bin/YOUR_CUSTOMER (owner YOUR_CUSTOMER / chmod 0701) 3.) add symlink /var/customers/webs/YOUR_CUSTOMER/cgi-bin which points to /var/www/cgi-bin/YOUR_CUSTOMER 4.) add path option in froxlor customer frontend which allows executing perl in /var/customers/webs/YOUR_CUSTOMER/cgi-bin CGI will work. Could you implement creating of this directories / symlinks into the cron job?
July 29, 201016 yr Hm, nice solution indeed, open a bugreport for this. I'll see what i can do there with the symlinking
July 30, 201016 yr If you use debian or ubuntu you could even choose apache2-suexec-custom. Move your starterscripts to /var/customers/php-fcgi-scripts/ and edit /etc/apache2/suexec/www-data .
Archived
This topic is now archived and is closed to further replies.