Forum Moderators: phranque

Message Too Old, No Replies

Help needed with Apache

         

daktau

6:32 pm on Jan 16, 2010 (gmt 0)

10+ Year Member



Hi,
I have a problem that I think arose after installing an update for apache.

If I access localhost I see:-

Index of /
[ICO]NameLast modifiedSizeDescription
Apache/2.2.12 (Ubuntu) Server at 127.0.0.1 Port 80

if I access localhost/**anything else here** I see a page with index.php on it and nothing else.

The virtual hosts do not work at all either.

Can anyone explain what is occuring here?

thank you,
George.

g1smd

8:20 pm on Jan 16, 2010 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



What version did you upgrade from?

daktau

10:24 pm on Jan 16, 2010 (gmt 0)

10+ Year Member



I have checked /var/log/dist-upgrade/apt.log and can only find reference to apache2.2

Does this mean that it is down to the config file?

daktau

4:57 pm on Jan 17, 2010 (gmt 0)

10+ Year Member



I would like to completely remove apache2 and start again so as to overcome my problems.

Is this good way to go?

Also, if I am setting up virtual hosts on my machine which will be serving them up locally to itself then what is the best way to acheive this? I have read many threads and am confused by the array of options. Before, I have successfully used /etc/hosts to list the virtual host names but have become unstuck in setting up the different conf files.

I am now receiving the following error that I cannot fix which is why I want to reinstall apache2.

(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs

thank you,
George.

g1smd

7:54 pm on Jan 17, 2010 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



What version did you upgrade from?

daktau

9:05 pm on Jan 17, 2010 (gmt 0)

10+ Year Member



As I mentioned, I have checked /var/log/dist-upgrade/apt.log and can only find reference to apache2.2

daktau

8:41 pm on Jan 18, 2010 (gmt 0)

10+ Year Member



I managed to solve the problem.
In desperation\fustration I commented out the line

Listen 80

in ports.conf

Th error no longer appears and I have everything running as I expect it to.