Apache SWS 2.0 fails to start

[Aaron Sakovich]

I've been running Apache 2.0 since July of last year without any problem. Today, I made a one line mod to my php.ini and restarted the server, and it failed to start. I took the mod back out, and it still failed to start.

There is nothing in any of the log files of interest, so I tried doing "Apache$Startup run" -- no info. It just falls right through the httpd command!

If I try to run the Apache$Startup Start interactively with my fully priv'd account, it just exits about as quickly as it can, and no processes show up on the system. If I submit it as a batch job /user=system, it runs a bit longer -- matter of fact, I can see the Apache$SWS process running. The process runs about 1 second if run interactively and about 7 when submitted as a system batch job. When submitted, I can sometimes see a bg device created on port 80, very briefly, just before the process terminates.

But never do I see any error messages! Not in any of the log files, not if I disable the f$verify in the startup files, not if run interactively.

I even tried putting some deliberately erroneous info in the httpd.conf file, and it caught it -- even when it was at the end of the file! So that's being processed.

I'm at Wits End on this one -- I could deal with it if something was getting logged or if some error message was displayed when I tried Apache$Startup RUN, but there's NOTHING! Heck, I even enabled auditing of file access failures and nothing showed up in the audit logs...

Any ideas???

Plover,
Aaron

[Aaron Sakovich]

Found it!

Turning on Apache$SPL_Disabled (ref. http://h71000.www7.hp.com/openvms/products/ips/apache/csws_install_20.html#trouble_s) and tried starting it again; it said it couldn't start because the host name didn't exist.

Sure enough, I'd changed the host name last week, and this was the first time I'd kicked the server since then.

Whoa, what a nightmare! I felt like I was in a maze of twisty little passages, all alike... ;^)

Aaron