in reply to Perl?Apache issue on newly installed server

Two more things to check: (1) Can you run the scripts from the command line as the user the webserver is running as (apache, www,...), instead of as root?  (2) Does the new distro have SELinux enabled? (which might be constraining what apache is allowed to do)  Check with /usr/sbin/getenforce as a first step...

  • Comment on Re: Perl?Apache issue on newly installed server

Replies are listed 'Best First'.
Re^2: Perl?Apache issue on newly installed server
by Dranzaz (Sexton) on Apr 08, 2009 at 15:03 UTC
    Ok, checked the SELinux status: 
    # cat /selinux/enforce
1

    [download]
    was set to enforcing, did the following: 
    # echo 0 >/selinux/enforce

    [download]
    It now writes the files and no longer gets the "could not open socket" error. Now it is timing out on the DNS Resolver, httpd log: 
    [Wed Apr 08 10:51:09 2009] [error] [client 209.18.32.79] Name "main::r
+everse" used only once: possible typo at /var/www/cgi-bin/ipsectest/i
+psectest.pl line 98., referer: http://inoc.cdptpa.rr.com/tools/ipsect
+est.html

[Wed Apr 08 10:53:09 2009] [warn] [client 209.18.32.79] Timeout waitin
+g for output from CGI script /var/www/cgi-bin/ipsectest/ipsectest.pl,
+ referer: http://inoc.cdptpa.rr.com/tools/ipsectest.html

[Wed Apr 08 10:53:09 2009] [error] [client 209.18.32.79] (70007)The ti
+meout specified has expired: ap_content_length_filter: apr_bucket_rea
+d() failed, referer: http://inoc.cdptpa.rr.com/tools/ipsectest.html

    [download]
    Changed the Resolvers nameserver variable and the output is fine now. SELinux apparently was the culprit. Thanks for the help.
[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom