(no subject)
Dec. 9th, 2004 02:33 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
stormdogI worked past eleven again and I was hungry. I thought they might be keeping me later and was going to sneak off for a sandwich at noon, but they let us go.
Technews: I finally, finally, got the virtual hosting configuration of my Apache server to work on my PIII Xeon box. I was running Apache 2.0.52 and I tried every different way I could think of to get it to work. I changed the IP addresses that the virtual hosts operate on from defined to wildcard, I did the same for the individual virtual host definitions, and I spent hours cutting and pasting bits of config code from different test versions of the config file until I couldn't even remember where I started anymore. I did a full reinstall of W2K Advanced Server and tried installing Apache before upgrading it to a domain controller thinking that, for some reason, the fact that Active Directory was on the box was causing issues. No dice. I tried installing on my test machine with a fresh install of 2K pro. No good. I redownloaded the file several times thinking I might have a corrupted archive. Nope. I dug through Google for hours, beseeching the server-gods as I hunted down the ever-elusive 'service specific error code 1' that Apache kept throwing into the Windows event log. Nothing. Apache would install and run just fine with the out-of-the-box settings, but every time I tried to start the service with more than one defined virtual host, Apache died a brief, painful death. I'd been wrestiling with this for months off and on.
Finally, I hit upon one last thing I hadn't yet tried. I dug my copy of Apache that I had originally installed on my current server box out of my application archive folder and compared versions. 2.0.36. "What the heck?" I thought as I uninstalled 2.0.52 and installed the older one. I configured Apache and pasted in my virtual host information. It ran flawlessly, leaving me to wonder what in the name of all that's holy they did to the virtual hosting in 2.0.52 and why, despite hours of poring over the official docs, usenet postings, discussion forums, and server config help sites, I can't get the bloody thing to work when, using 2.0.36, it's a matter of 10 minutes of typing in IP addresses and log file paths!
At least it's set up now. I'm going to be working on migrating all of my server functionality over to my new box; I also want to set it up as a router and remote access (VPN) server. For now it's going to mirror my production server as far as data and configs for http and email services and, once I finally get everything else set up, I'll painlessly swap it in, make sure it's running smoothly, and decomission my old P-Pro 200 server so I can finally use it to learn Linux. At least, that's the plan...
I'll be posting again later tonight with big news on my employment situation as well as other things that will probably be of much more interest to the non-geeks on my reading list.
Technews: I finally, finally, got the virtual hosting configuration of my Apache server to work on my PIII Xeon box. I was running Apache 2.0.52 and I tried every different way I could think of to get it to work. I changed the IP addresses that the virtual hosts operate on from defined to wildcard, I did the same for the individual virtual host definitions, and I spent hours cutting and pasting bits of config code from different test versions of the config file until I couldn't even remember where I started anymore. I did a full reinstall of W2K Advanced Server and tried installing Apache before upgrading it to a domain controller thinking that, for some reason, the fact that Active Directory was on the box was causing issues. No dice. I tried installing on my test machine with a fresh install of 2K pro. No good. I redownloaded the file several times thinking I might have a corrupted archive. Nope. I dug through Google for hours, beseeching the server-gods as I hunted down the ever-elusive 'service specific error code 1' that Apache kept throwing into the Windows event log. Nothing. Apache would install and run just fine with the out-of-the-box settings, but every time I tried to start the service with more than one defined virtual host, Apache died a brief, painful death. I'd been wrestiling with this for months off and on.
Finally, I hit upon one last thing I hadn't yet tried. I dug my copy of Apache that I had originally installed on my current server box out of my application archive folder and compared versions. 2.0.36. "What the heck?" I thought as I uninstalled 2.0.52 and installed the older one. I configured Apache and pasted in my virtual host information. It ran flawlessly, leaving me to wonder what in the name of all that's holy they did to the virtual hosting in 2.0.52 and why, despite hours of poring over the official docs, usenet postings, discussion forums, and server config help sites, I can't get the bloody thing to work when, using 2.0.36, it's a matter of 10 minutes of typing in IP addresses and log file paths!
At least it's set up now. I'm going to be working on migrating all of my server functionality over to my new box; I also want to set it up as a router and remote access (VPN) server. For now it's going to mirror my production server as far as data and configs for http and email services and, once I finally get everything else set up, I'll painlessly swap it in, make sure it's running smoothly, and decomission my old P-Pro 200 server so I can finally use it to learn Linux. At least, that's the plan...
I'll be posting again later tonight with big news on my employment situation as well as other things that will probably be of much more interest to the non-geeks on my reading list.
