Installation of ebox hangs at: restarting eBox module apache

Bug #376054 reported by Niels Egberts
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
ebox (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: ebox

The ebox installation on ubuntu-server karmic just hangs at "Resatring Ebox module: apache [OK]"

The system does not seem to do anything, but eBox *is* working!
When I press ctrl-z I get:

error on handling ebox (--configure):
subprocess post-installation script was being killed
subprocess /usr/bin/dpkg returned an error code (1)

Tags: karmic
Revision history for this message
Javier Uruen Val (juruen) wrote :

Is it possible that you already had an apache server listening on 443, and you selected the same port for the eBox's apache?

Revision history for this message
Niels Egberts (nielsegberts) wrote :

I have done a clean install with Alpha 1. And did a "sudo apt-get install ebox". Now it hangs again at:

Adding user `ebox` to group `adm` ...
Adding user ebox to group adm
Done.
Creating the eboxlogs database
 * Restarting ebox module: apache [OK]

Then the configuration simply stops, but dropbox *is* available at port 433 and seems to work fine.

description: updated
summary: - [karmic] installation of ebox hangs
+ [karmic] installation of ebox hangs at: restarting eBox module apache
Revision history for this message
Niels Egberts (nielsegberts) wrote : Re: [karmic] installation of ebox hangs at: restarting eBox module apache

Sorry I said dropbox, I meant eBox offcourse.

description: updated
Revision history for this message
RobertH (robert-hunt) wrote :

I have the same problem in Karmic i386. It did warn me that maybe port 443 was already being used, but since it only said "maybe" and then there was a continue option, I choose Yes (continue). Then it locked up as described above. I had to abort it with Ctrl+C.

Then I tried "dpkg --configure ebox". This time when it asked about the port number, I said No (don't continue). But I couldn't get past that screen no matter how many times I selected No. So I gave up and selected Yes and then it locked up again.

I couldn't find where in the config files that ebox selected port 443 so I couldn't see where to change it. I gave up and used "apt-get remove ebox" for now.

papukaija (papukaija)
Changed in ebox (Ubuntu):
status: New → Confirmed
Revision history for this message
Auren (auren) wrote :

Any workarounds/fixes for this?

Revision history for this message
Javier Uruen Val (juruen) wrote :

I'm unable to reproduce this. Could you please tell me if you used the ubuntu server edition installer?

Revision history for this message
wannabeelinux (bas-douma) wrote :

I had the same problem with upgrading my Ubuntu studio 9.04 box from command prompt to Karmic Koala. I did use the server edition installer. Got around it opening up a second terminal session by shutting down apache and ebox en starting them up again. After that the upgrade continued:

Here is the command I used:

/etc/init.d/ebox restart

I had two repeat the step twice before the upgrade got anywhere.

The third time it wouldn't work any more and I recieved the error:
Error loading class: EBox::

The installer now hangs with the message:
update-rc.d: warning: ebox stop runlevel arguments (0 1 6) do not match LSB Default-Stop values (0 6)

Because of the upgrade I cannot edit the runlevel arguments.

Maybe it's better to deinstall ebox en reinstall it after the upgrade. But I'm stuck right now with above problem and error.

Help me please.

Revision history for this message
wannabeelinux (bas-douma) wrote :

The upgrade went ahead after giving in Ctrl-C.

Revision history for this message
Víctor Jiménez (capitangolo) wrote :

I tried today from a clean karmic installation.

First it complained about /etc/init.d/postgresql-8.3 not existing (apt-get was installing postgresql-8.4).

Then it showed the update-rc.d warning and an sh error:

Configurando ebox (1.3.6-0ubuntu1~ppa1~jaunty1) ...
update-rc.d: warning: ebox stop runlevel arguments (0 1 6) do not match LSB Default-Stop values (0 6)
sh: Syntax error: "(" unexpected
Creating the eboxlogs database
 * Restarting eBox module: apache
   ...done.
<Then it hangs>

I tried wannabeelinux solution, and it worked to finish the installation. The control panel seems to work. The output for the restart command shows some errors:

$ sudo invoke-rc.d ebox restart
 * Stopping eBox module: events
   ...fail!
root command stop 'ebox.event-daemon' failed.
Error output: stop: Unknown job: ebox.event-daemon

Command output: .
Exit value: 1
 * Stopping eBox module: logs
   ...fail!
root command stop 'ebox.loggerd' failed.
Error output: stop: Unknown job: ebox.loggerd

Command output: .
Exit value: 1
 * Stopping eBox module: apache
   ...done.
 * Starting eBox module: events
   ...done.
 * Starting eBox module: logs
   ...done.
 * Starting eBox module: apache
   ...done.

Revision history for this message
Víctor Jiménez (capitangolo) wrote :

I solved the following errors:

 * Stopping eBox module: logs
   ...fail!
root command stop 'ebox.loggerd' failed.
Error output: stop: Unknown job: ebox.loggerd

By symlinking the ebox scripts like this:

ln -s /etc/event.d/ebox.loggerd /etc/init/ebox.loggerd.conf

Revision history for this message
Javier Uruen Val (juruen) wrote :

@Víctor

You are using jaunty packages. Karmic changed the directory where upstart scripts live from /etc/event.d to /etc/init

Revision history for this message
jehon (jeanhonlet) wrote :

Same problem as others...

It is not my first attempt to install ebox, and usually, it works. But not this time.

Same symptoms: it hangs after restarting apache module.

By the way, it did works once, but then, I had problem with menu items (system, log, event) giving me error pages. If that can help someone to understand what it is about...

papukaija (papukaija)
tags: added: karmic
papukaija (papukaija)
summary: - [karmic] installation of ebox hangs at: restarting eBox module apache
+ Installation of ebox hangs at: restarting eBox module apache
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.