HELP - Apache 2.0.47 package crashes on HP-UX 11.11

[Marco Muishout]

Hi,

We have downloaded the latest HP-UX apache webserver package for UX11 (which includes apache 2.0.47). We are running HP-UX 11.11 on a partitioned HP9000/800 machine.

Whenever we try to start the http daemon or try to use apachectl, we get an 'Illegal instruction' message and a core dump. This probably means that some instruction was used that is not supported by the kernel or the system hardware.

Does anyone have similar experiences? Should I build my own apache version? (Which I can, but if this is not required I definately do not want to do this)

The strange thing is that the download site says this package should work on our platform.

Thanks,
Marco

[Steven E. Protter]

sweverify \*

Check the status of the install.

swconfig \* if warranted.

Maybe swremove apache
then re-insall.

Bottom line is no, I have not been able to duplicate your error and I'm using the product on a D320(32 bit) 11.11 system.

Are we fully patched?

Do you have enough shared memory(shmmax,shmseg), check ipcs

I think you are much better off getting the depot working.

SEP

[Ken Penland_1]

well, if you can build your own, I would recommend that, as apache just came out with 2.0.48 that has some extra bug fixes in it ;)

[Helen French]

One thing that comes to mind is the new Apache version that supports IPv6. Did you download that version? If yes, are you using IP version 6 on your system? The IPv6 version does need that package installed on your system and if it's not there, Apache start will fail.

[Marco Muishout]

Thanks for your swift replies!

We already tried 2.0.39, too. Same result. I also tried running a 2.0.47 package that I compiled on a 11.00 machine, same result.

I do not like building one myself because I would have to install all the build tools on a production machine.

I am going to have some SHM & Semaphores & ipV6 checked tomorrow. Although I do have some root privileges, I cannot perform the swremove/swconfig command. I do however doubt whether this is going to solve my problem.

Will get back to you guys, thanks sofar

[Marco Muishout]

I downloaded the depot again and compared it to the original one. They matched exactly, same checksum etc.

Then I simply deinstalled everything and installed it again (got the required permissions in the mean time). Result: it works!

Apparently the guy who did the original installation missed out on a few errors or warnings - I do not know of any other reason why this happened. We did not change anything else.

Thank you all for your help,
Marco