Ordeals in upgrading
March 25, 2008 11:26 PM Filed in: Rants
I recently started a project to upgrade my stickman.org server. What I thought would be a few nights work has turned into a true ordeal.
Most of my issues have centered around the web server. I prefer to use Apache - and I grabbed the latest 2.2.8 server from apache.org. All seemed to go well until I tried getting the https side of the server working. I kept getting strange failures from Firefox about an incorrect mathematical response or something of the like. Turns out, it was a problem with OpenSSL 0.9.8 which I had compiled. And it wasn't a problem with the source. It was a problem with the *compiler* - the Sun Studio 11 compiler to be exact.
I was getting, running make test:
*** Error code 9
make: Fatal error: Command failed for target `test_evp'
Turns out it was a known problem - writeup here: http://forum.sun.com/thread.jspa?messageID=99121
I chose to just get the newest Studio12 compiler. Thought I was done.
Um....nope not yet.
Now I kept getting:
Syntax error on line 78 of /usr/local/apache2/conf/extra/httpd-ssl.conf:
Could not resolve address '255.255.255.255' -- check resolver configuration.
Arrrghh...this is the virtual host entry in the ssl config file that defines:
So the manual says, this means DNS isn't getting consulted. Well....it is. Everywhere. But guess what? My old friend nscd is to blame again (a great idea, but one that has killed me so many times...) nscd apparently has problems dealing with lookups to anything other than files. Doing an svcadm disable name-service-cache and then starting the web server worked great! Except, there are some efficiencies to be gained by using nscd. I'd like to try to keep that running if possible.
So....off to install 127111-11 (latest as of this posting). And its prereqs. All in an attempt to try to resolve bug 6612782 which appeared to fit my problem. Still no dice. Apparently some major changes went into Solaris 10 08/07 have, again, left nscd somewhat non-functional.
So I'm bypassing nscd for a bit until I can sort this out further. Actually, I'll probably file a bug....this seems to be a regression from Solaris 10 06/06.
blog comments powered by Disqus