Page 1 of 1

rm -rf /etc/apache2/sites-available

Posted: 28 Oct 2010, 15:29
by nerke
Thats stupid to do, but i did it.... does anyone have any ideas what to do now? :oops:

Re: rm -rf /etc/apache2/sites-available

Posted: 28 Oct 2010, 15:53
by RandomUsername
You can probably extract it from the installer image.

Re: rm -rf /etc/apache2/sites-available

Posted: 28 Oct 2010, 16:06
by 6feet5
Reinstalling the packages "apache2.2-common" and "bubba-frontend" should probably do the trick as well.

/Johan

Re: rm -rf /etc/apache2/sites-available

Posted: 28 Oct 2010, 16:08
by nerke
clever. ill try that...

Re: rm -rf /etc/apache2/sites-available

Posted: 28 Oct 2010, 16:20
by nerke
did a;

Code: Select all

apt-get install --reinstall apache2.2-common

Code: Select all

apt-get install --reinstall bubba-frontend
which gave me
Restarting web server: apache2apache2: Syntax error on line 186 of /etc/apache2/apache2.conf: Could not open configuration file /etc/apache2/mods-enabled/proxy_html.conf: No such file or directory
failed!
invoke-rc.d: initscript apache2, action "restart" failed.dpkg: fel vid hantering av bubba-frontend (--configure):
underprocess post-installation script gav felkod 1
Ställer in apache2 (2.2.9-10+lenny4) ...
Fel uppstod vid hantering:
bubba-frontend
E: Sub-process /usr/bin/dpkg returned an error code (1)
so i did

Code: Select all

/usr/bin/dpkg --configure bubba-frontend
and that gave me
Ställer in bubba-frontend (2.0.0.9) ...
Restarting web server: apache2apache2: Syntax error on line 186 of /etc/apache2/apache2.conf: Could not open configuration file /etc/apache2/mods-enabled/proxy_html.conf: No such file or directory
failed!
invoke-rc.d: initscript apache2, action "restart" failed.
dpkg: fel vid hantering av bubba-frontend (--configure):
underprocess post-installation script gav felkod 1
Fel uppstod vid hantering:
bubba-frontend
Seems that bubba-frontend fails to configure...

Re: rm -rf /etc/apache2/sites-available

Posted: 28 Oct 2010, 16:25
by nerke
or more likely that apache2 dont install correct? that apache is missing proxy_html.conf... but if i turn that off wont my slimserver go down?

Re: rm -rf /etc/apache2/sites-available

Posted: 28 Oct 2010, 17:22
by ryz
In my /etc/apache2/apache2.conf line 186 I have the following line

Code: Select all

Include /etc/apache2/mods-enabled/*.conf
Which says that apache should include all files under /etc/apache2/mods-enabled that ends with .conf. So how that can generate an error that a file does not exist I do not understand. Either the file does not exist and will then not be included since it does not match *.conf or it does exist. I suggest you do an ls in the directory /etc/apache2/mods-enabled to see if you have any strange files there. I do not have any proxy_html.conf file on my Bubba 2 install.

Re: rm -rf /etc/apache2/sites-available

Posted: 29 Oct 2010, 06:33
by Kiff
the bubba entry in sites-available is just a symlink to /usr/share/bubba-frontend/apache.site, recreating it (ln -s <target> <link>) should have been enough.

The line above, 185, includes the load files. Check for those as well in /etc/apache2/mods-enabled

I would try to start apache (apache2ctl start) and look in the logfile /var/log/apache2/error.log for additional errors.

Re: rm -rf /etc/apache2/sites-available

Posted: 29 Oct 2010, 07:43
by nerke
i did

Code: Select all

mv /etc/apache2/mods-enabled/proxy_html.conf /etc/apache2/mods-enabled/proxy_html.conf.backup
and removed the corresponding line in apache2.conf and then

Code: Select all

/etc/init.d/apache2 restart
which gave me
Restarting web server: apache2apache2: apr_sockaddr_info_get() failed for bubba
apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
[Fri Oct 29 06:34:57 2010] [warn] NameVirtualHost *:80 has no VirtualHosts
apache2: apr_sockaddr_info_get() failed for bubba
apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
[Fri Oct 29 06:34:58 2010] [warn] NameVirtualHost *:80 has no VirtualHosts
and that solved my problem with apache refused to start.

in my error log i see many entries like this
ri Oct 29 12:40:32 2010] [error] [client 127.0.0.1] File does not exist: /htdocs
[Fri Oct 29 12:49:47 2010] [error] [client 127.0.0.1] File does not exist: /htdocs
[Fri Oct 29 13:11:00 2010] [error] [client 127.0.0.1] File does not exist: /htdocs
[Fri Oct 29 13:19:53 2010] [error] [client 127.0.0.1] File does not exist: /htdocs

Re: rm -rf /etc/apache2/sites-available

Posted: 29 Oct 2010, 08:45
by Ubi
what is your output of

Code: Select all

apache2ctl -St

Re: rm -rf /etc/apache2/sites-available

Posted: 31 Oct 2010, 04:59
by nerke
Ubi wrote:what is your output of

Code: Select all

apache2ctl -St
I get a command not found. strange.... wtf. i will do a reinstall of the system and my sunday is saved... tanks for all the advices!

Re: rm -rf /etc/apache2/sites-available

Posted: 31 Oct 2010, 06:16
by ryz
You need to be root to find the command apache2ctl since it is in the /usr/sbin directory which normally only root has in its path.