Page 1 of 1
Broken frontend
Posted: 27 May 2009, 12:35
by Zeb
Hello,
I accidentally broke my frontend while installing something. Probably Mirage Image Viewer. I can still acces my Bubba, but I can't reach my admin page. 404 error. I tried removing the frontend en re-installing, but something seems to go wrong when I try to remove it...
Can somebody help me?
Thanks!
Re: Broken frontend
Posted: 27 May 2009, 14:34
by carl
Can you post the output from the failed install of bubba-frontend?
/Carl
Re: Broken frontend
Posted: 27 May 2009, 19:56
by Zeb
Code: Select all
bubba:~# apt-get install bubba-frontend
Reading package lists... Done
Building dependency tree... Done
bubba-frontend is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
bubba:~# apt-get remove bubba-frontend
Reading package lists... Done
Building dependency tree... Done
The following packages will be REMOVED:
bubba-frontend
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 0B of archives.
After unpacking 1876kB disk space will be freed.
Do you want to continue [Y/n]? y
(Reading database ... 31000 files and directories currently installed.)
Removing bubba-frontend ...
Site bubba disabled; run /etc/init.d/apache2 reload to fully disable.
Site default installed; run /etc/init.d/apache2 reload to enable.
Forcing reload of web server (apache2)...httpd (no pid file) not running
(98)Address already in use: make_sock: could not bind to address [::]:80
(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
failed!
invoke-rc.d: initscript apache2, action "restart" failed.
dpkg: error processing bubba-frontend (--remove):
subprocess pre-removal script returned error exit status 1
Site default disabled; run /etc/init.d/apache2 reload to fully disable.
Site bubba installed; run /etc/init.d/apache2 reload to enable.
spawn-fcgi.c.89: socket is already used, can't spawn
Errors were encountered while processing:
bubba-frontend
E: Sub-process /usr/bin/dpkg returned an error code (1)
Re: Broken frontend
Posted: 29 May 2009, 10:15
by carl
Could it be that you have some other httpd (like lighttpd) installed that is binding on port 80?
/Carl
Re: Broken frontend
Posted: 29 May 2009, 10:50
by Zeb
Ehm, that could very well be the case. I'm not that advanced of a user. I installed Mirage Image Viewer
http://mirageiv.berlios.de/ and SPGM
http://forum.excito.net/viewtopic.php?f=8&t=781.
Re: Broken frontend
Posted: 02 Jun 2009, 15:03
by Zeb
*bump*
Re: Broken frontend
Posted: 04 Jun 2009, 07:34
by tor
SPGM really should not be able to give these symptoms. How did you install Mirage Image Viewer? From source using a package?
/Tor
Re: Broken frontend
Posted: 04 Jun 2009, 07:49
by Zeb
tor wrote:SPGM really should not be able to give these symptoms. How did you install Mirage Image Viewer? From source using a package?
/Tor
Exactly the same way as SPGM, using
this tutorial. And I may have done this:
INSTALLATION:
Just run 'python setup.py install' as root.
..but i'm not really sure anymore.
Re: Broken frontend
Posted: 09 Jun 2009, 02:44
by Zeb
Is there any way I can uninstall them?
Re: Broken frontend
Posted: 17 Jun 2009, 03:51
by Zeb
*bump* Anyone?