After running swaret httpd won't start ?
 

Hello,

I recently bought a mini-itx mobo (APIA 500) and used in to build a nice little low power Slackware box which will eventually become my "house server" (i.e. once I get it working properly)

So I then installed Slackware 9.1, added webmin and all was working well. However as there have been several security advisories since 9.1 was released I thought I'd best upgrade everything by using swaret (version 1.3.1)

Sadly after doing so http will no longer start as it gives me the following error message:

Syntax error on line 205 of /etc/apache/httpd.conf
Cannot load /usr/libexec/mod_vhost_alias.so into server: /usr/libexec/mod_vhost_alias.so: cannot open shared object file: No such file or directory

Having looked at /etc/httpd.conf there are indeed numerous entries for various modules to be loaded but none of them seem to be on my box.

So a lot of googling later and I'm still none the wiser as to what's wrong ? If anybody could give me a clue as to how to get httpd working I'd be most grateful.

Thankyou

Huh, well try doing 'swaret --reinstall apache'.

Also, the newest swaret is like 1.6.2, so there might be some bugs in the earlier version.

Firstly thanks for the replies.

And perhaps I should have been a bit more verbose in my post as the first thing I tried was "swaret --reinstall apache" which gave me the message "No available packages matching keyword apache".. . Which caused me to scratch my head somewhat as I'd just watched swaret download and reinstall it about an hour earlier (I had nothing better to do so I was actively watching swaret doing it's stuff)

Even worse when I now do a swaret --list it tells me "No available packages found". Most peculiar.

I should also have mentioned that prior to running swaret for the first time I had just upgraded it to 1.6.1 by using the swaret-1.6.1-noarch-2.tgz from http://www.swaret.org (i.e. the latest stable build)

But the messges from httpd are intriguing me as they first module mentioned seems to be for virtual hosting which I haven't (or at least hadn't) set up.

So if anyone can shed some light on why my httpd server won't start I'd be most grateful ? Or should I manually try reinstalling apache via the use of removepkg and installpkg ?

Or would I be better off nuking the box, doing a fresh slackware install, and sticking with a box that works o.k. ? WHich is the easiest, but least satisfactory answer, even though I only built it last week.....

P.S. As an experiment I also used swaret on my other linux box (after updating swaret to the same version) and now httpd is broken on this box too :)

Now if only I'd have saved a copy of my http.conf before I did it (bloody memory lapse)

So at least there's some consistent behaviour going on here and I reckon I get bonus points for proving that having shot myself in one foot I can still aim well enough to hit the other one !

did you do 'swaret --update' first? thats the only reason why it would say it couldn't find it. Or your using a down mirror.

when you do 'locate <vhost whatever module>' where does it say it is? if you haven't ran the 'updatedb' command yet, do it first.

Firstly thanks again for all the replies.

And I'm afraid I didn't even know about the "updatedb" command so that's something new learnt ! As suggested it's now in my cron tab.

In the meantime the good news is that I eventually found that the problem was that the latest httpd.conf file (which seems to have overwritten my previous effort) was attempting to load modules from /libexec/<mod_name> whereas the modules are now to be found in libexec/apache/<mod_name>.

The worst thing is that I found the answer in another thread in this forum which I simply couldn't find yesterday. But after narrowing my search to "mod_vhost_alias" the required post turned up.

So a quick edit of /etc/apache/http.conf to replace "libexec/" with "libexec/apache/" in the "LoadModule" section and httpd is working again.

Now I've just got to work out how to get webmin back up again (I suspect it's a similar configuration issue)

So thanks again for the replies as my box is fast becoming Slackware-tastic again !

Raptor Ramjet:

I too have had the same problem as you describe above even after running 'swaret --update'. It turns out that changes have been made to the FILELIST.TXT file so you will need the latest version of swaret (1.6.1-3) in order to handle the changes.

Hope this helps.

Paul.

Cheers for the advice.

I'll go and get the update now !