Received: (qmail 9920 invoked by uid 2012); 22 Jul 1998 16:14:26 -0000 Message-Id: <19980722161426.9919.qmail@hyperreal.org> Date: 22 Jul 1998 16:14:26 -0000 From: Tim Hanson Reply-To: tbhanson@startribune.com To: apbugs@hyperreal.org Subject: apache works fine when started manually by root, but there are problems when it is started at boot time with /etc/inittab X-Send-Pr-Version: 3.2 >Number: 2662 >Category: os-aix >Synopsis: apache works fine when started manually by root, but there are problems when it is started at boot time with /etc/inittab >Confidential: no >Severity: serious >Priority: medium >Responsible: apache >State: closed >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Wed Jul 22 09:20:01 PDT 1998 >Last-Modified: Sun Jun 13 04:54:37 PDT 1999 >Originator: tbhanson@startribune.com >Organization: >Release: 1.3 >Environment: aix 4.2.1 (root in / @ mpbgw-demo15) >uname -a AIX mpbgw-demo15 2 4 000002197500 gcc (root in / @ mpbgw-demo15) >gcc -v Reading specs from /usr/local/lib/gcc-lib/powerpc-ibm-aix4.1.5.0/2.8.1/specs gcc version 2.8.1 >Description: I recently installed apache 1.3 and am very happy with it. Previously I had been unable to get cgi to work (though that may have been my own fault.) After going through the .conf files somewhat carefully and referring to some of the docs on your web site it went better this time. However, yesterday I tried to make the step of putting an entry in /etc/inittab so apache would start up automatically at system boot time. Here's what I put in /etc/inittab: apache:2:wait:/etc/rc.apache > /dev/console 2>&1 # start apache web server I put this at the very bottom. Here's the rc.apache I created: (root in /etc @ mpbgw-demo15) >cat rc.ap* #!/usr/bin/ksh /usr/local/apache/sbin/apachectl start Apache starts on system reboot and serves static html just fine. However, cgi seems to time out. If I stop and start apache (using the same line above but with stop/start), the problem goes away. At the moment this is mostly an annoyance. I've thought of, but haven't tried yet, creating a cron job that, say, runs at 6:00am each day; it checks to see if apache is running and if not kicks it off (this would work for me.) But I imagine someone out there will want to run on aix and would like apache to come up automatically on reboot. >How-To-Repeat: I hope it's easily repeatable. It has repeated for me several times with at least two different browsers. I can't give you my URLs because they're inside a firewall. >Fix: I mentioned work-arounds above. >Audit-Trail: From: Marc Slemko To: Tim Hanson Cc: apbugs@hyperreal.org Subject: Re: os-aix/2662: apache works fine when started manually by root, but there are problems when it is started at boot time with /etc/inittab Date: Wed, 22 Jul 1998 09:32:28 -0700 (PDT) On 22 Jul 1998, Tim Hanson wrote: > I recently installed apache 1.3 and am very happy with it. Previously > I had been unable to get cgi to work (though that may have been my own > fault.) > > After going through the .conf files somewhat carefully and referring > to some of the docs on your web site it went better this time. > > However, yesterday I tried to make the step of putting an entry in > /etc/inittab so apache would start up automatically at system boot > time. > > Here's what I put in /etc/inittab: > apache:2:wait:/etc/rc.apache > /dev/console 2>&1 # start apache web server > I put this at the very bottom. Here's the rc.apache I created: > (root in /etc @ mpbgw-demo15) >cat rc.ap* > #!/usr/bin/ksh > > /usr/local/apache/sbin/apachectl start > > Apache starts on system reboot and serves static html just fine. > However, cgi seems to time out. If I stop and start apache (using the > same line above but with stop/start), the problem goes away. At the > moment this is mostly an annoyance. I've thought of, but haven't tried > yet, creating a cron job that, say, runs at 6:00am each day; it checks > to see if apache is running and if not kicks it off (this would work > for me.) But I imagine someone out there will want to run on aix and > would like apache to come up automatically on reboot. This is almost certainly an AIX problem. Is there anything in the error log? Try adding it to /etc/rc.local instead of the inittab. From: Dirk-Willem van Gulik To: Tim Hanson Cc: apbugs@hyperreal.org Subject: Re: os-aix/2662: apache works fine when started manually by root, but there are problems when it is started at boot time with /etc/inittab Date: Wed, 22 Jul 1998 18:47:53 +0200 (CEST) Did you check the ulimit settings. I've found those occasionally restrictive on deamons started from the init. Do a ulimit -a (or do it in CGI) to see what it is set to from the various shells, cgi's and places. We have one box where the # of files is just too low for the ones started at boot time (/etc/login.conf). Dw. On 22 Jul 1998, Tim Hanson wrote: > > >Number: 2662 > >Category: os-aix > >Synopsis: apache works fine when started manually by root, but there are problems when it is started at boot time with /etc/inittab > >Confidential: no > >Severity: serious > >Priority: medium > >Responsible: apache > >State: open > >Class: sw-bug > >Submitter-Id: apache > >Arrival-Date: Wed Jul 22 09:20:01 PDT 1998 > >Last-Modified: > >Originator: tbhanson@startribune.com > >Organization: > apache > >Release: 1.3 > >Environment: > aix 4.2.1 (root in / @ mpbgw-demo15) >uname -a > AIX mpbgw-demo15 2 4 000002197500 > > gcc > (root in / @ mpbgw-demo15) >gcc -v > Reading specs from /usr/local/lib/gcc-lib/powerpc-ibm-aix4.1.5.0/2.8.1/specs > gcc version 2.8.1 > > >Description: > I recently installed apache 1.3 and am very happy with it. Previously I had been unable to get cgi to work (though that may have been my own fault.) > > After going through the .conf files somewhat carefully and referring to some of the docs on your web site it went better this time. > > However, yesterday I tried to make the step of putting an entry in /etc/inittab so apache would start up automatically at system boot time. > > Here's what I put in /etc/inittab: > apache:2:wait:/etc/rc.apache > /dev/console 2>&1 # start apache web server > I put this at the very bottom. Here's the rc.apache I created: > (root in /etc @ mpbgw-demo15) >cat rc.ap* > #!/usr/bin/ksh > > /usr/local/apache/sbin/apachectl start > > Apache starts on system reboot and serves static html just fine. However, cgi seems to time out. If I stop and start apache (using the same line above but with stop/start), the problem goes away. At the moment this is mostly an annoyance. I've thought of, but haven't tried yet, creating a cron job that, say, runs at 6:00am each day; it checks to see if apache is running and if not kicks it off (this would work for me.) But I imagine someone out there will want to run on aix and would like apache to co me up automatically on reboot. > >How-To-Repeat: > I hope it's easily repeatable. It has repeated for me several times with at least two different browsers. I can't give you my URLs because they're inside a firewall. > >Fix: > I mentioned work-arounds above. > >Audit-Trail: > >Unformatted: > [In order for any reply to be added to the PR database, ] > [you need to include in the Cc line ] > [and leave the subject line UNCHANGED. This is not done] > [automatically because of the potential for mail loops. ] > > > > State-Changed-From-To: open-feedback State-Changed-By: lars State-Changed-When: Sat Feb 20 17:48:04 PST 1999 State-Changed-Why: [This is a standard response.] This Apache problem report has not been updated recently. Please reply to this message if you have any additional information about this issue, or if you have answers to any questions that have been posed to you. If there are no outstanding questions, please consider this a request to try to reproduce the problem with the latest software release, if one has been made since last contact. If we don't hear from you, this report will be closed. If you have information to add, BE SURE to reply to this message and include the apbugs@Apache.Org address so it will be attached to the problem report! State-Changed-From-To: feedback-closed State-Changed-By: lars State-Changed-When: Sun Jun 13 04:54:37 PDT 1999 State-Changed-Why: [This is a standard response.] No response from submitter, assuming issue has been resolved. >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ]