After installing version 1.5.0, the dashboard is not accessible anymore

Bug #523613 reported by Fabrice Coutadeur
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ebox-usersandgroups (Ubuntu)
Invalid
High
Javier Uruen Val

Bug Description

Binary package hint: ebox-usersandgroups

Hi,

As soon as I install this modules, I'm getting this error in the dashboard web page:
A really nasty bug has occurred
Exception
root command status 'ebox.apache2-usercorner' failed. Error output: status: Unknown job: ebox.apache2-usercorner Command output: . Exit value: 1
Trace
root command status 'ebox.apache2-usercorner' failed.
Error output: status: Unknown job: ebox.apache2-usercorner

Command output: .
Exit value: 1 at /usr/share/perl5/Error.pm line 182
Error::throw('EBox::Exceptions::Sudo::Command', 'cmd', 'status \'ebox.apache2-usercorner\'', 'output', 'ARRAY(0x7fcb57f7b6f0)', 'error', 'ARRAY(0x7fcb57f83b78)', 'exitValue', 1, ...) called at /usr/share/perl5/EBox/Sudo.pm line 215
EBox::Sudo::_rootError('/usr/bin/sudo -p sudo: /var/lib/ebox/tmp/dHbM1QvuSC.cmd 2> /v...', 'status \'ebox.apache2-usercorner\'', 256, 'ARRAY(0x7fcb57f7b6f0)', 'ARRAY(0x7fcb57f83b78)') called at /usr/share/perl5/EBox/Sudo.pm line 182
EBox::Sudo::_root(1, 'status \'ebox.apache2-usercorner\'') called at /usr/share/perl5/EBox/Sudo.pm line 137
EBox::Sudo::root('status \'ebox.apache2-usercorner\'') called at /usr/share/perl5/EBox/Service.pm line 77
EBox::Service::running('ebox.apache2-usercorner') called at /usr/share/perl5/EBox/Module/Service.pm line 275
EBox::Module::Service::_isDaemonRunning('EBox::UserCornerWebServer=HASH(0x7fcb5a37ba38)', 'ebox.apache2-usercorner') called at /usr/share/perl5/EBox/Module/Service.pm line 330
EBox::Module::Service::isRunning('EBox::UserCornerWebServer=HASH(0x7fcb5a37ba38)') called at /usr/share/perl5/EBox/Module/Service.pm line 351
EBox::Module::Service::addModuleStatus('EBox::UserCornerWebServer=HASH(0x7fcb5a37ba38)', 'EBox::Dashboard::Section=HASH(0x7fcb5993e938)') called at /usr/share/perl5/EBox/SysInfo.pm line 75
EBox::SysInfo::modulesWidget('EBox::SysInfo=HASH(0x7fcb59589e78)', 'EBox::Dashboard::Widget=HASH(0x7fcb595f4480)', undef) called at /usr/share/perl5/EBox/Module/Base.pm line 651
EBox::Module::Base::widget('EBox::SysInfo=HASH(0x7fcb59589e78)', 'modules') called at /usr/share/perl5/EBox/CGI/Dashboard/Index.pm line 56
EBox::CGI::Dashboard::Index::masonParameters('EBox::CGI::Dashboard::Index=HASH(0x7fcb57cfc8a8)') called at /usr/share/perl5/EBox/CGI/Base.pm line 517
EBox::CGI::Base::_process('EBox::CGI::Dashboard::Index=HASH(0x7fcb57cfc8a8)') called at /usr/share/perl5/EBox/CGI/Base.pm line 262
EBox::CGI::Base::run('EBox::CGI::Dashboard::Index=HASH(0x7fcb57cfc8a8)') called at /usr/share/perl5/EBox/CGI/Run.pm line 120
EBox::CGI::Run::run('EBox::CGI::Run', 'Dashboard/Index', 'EBox') called at /usr/share/ebox/cgi/ebox.cgi line 19
ModPerl::ROOT::ModPerl::Registry::usr_share_ebox_cgi_ebox_2ecgi::handler('Apache2::RequestRec=SCALAR(0x7fcb5935d610)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204
eval {...} called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204
ModPerl::RegistryCooker::run('ModPerl::Registry=HASH(0x7fcb58cb94f8)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 170
ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0x7fcb58cb94f8)') called at /usr/lib/perl5/ModPerl/Registry.pm line 31
ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0x7fcb5935d610)') called at -e line 0
eval {...} called at -e line 0

Could you have a look?

Thanks,
Fabrice

Changed in ebox-usersandgroups (Ubuntu):
assignee: nobody → Javier Uruen Val (juruen)
status: New → In Progress
importance: Undecided → High
Revision history for this message
Javier Uruen Val (juruen) wrote :

Working on it.

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

I'm unable to reproduce it. I'm gonna reinstall with a full dist-upgrade to see if that reproduces the issue. I hadn't had a full dist-upgrade for a couple of days...

By the way, it seems either you don't have /etc/init/ebox.apache2-usercorner.conf or somehow upstart is not aware of it. Could you please check if that file exists?

Thanks a lot,

Revision history for this message
Fabrice Coutadeur (fabricesp) wrote :

Hi,

I've also tested in a clean chroot, and I can reproduce it: as soon as

also, the conf file exists:
ls -lrt /etc/init/ebox*
-rw-r--r-- 1 root root 42 Feb 17 07:01 /etc/init/ebox.loggerd.conf
-rw-r--r-- 1 root root 177 Feb 17 07:01 /etc/init/ebox.event-daemon.conf
-rw-r--r-- 1 root root 28 Feb 17 07:01 /etc/init/ebox.apache-perl.conf
-rw-r--r-- 1 root root 181 Feb 18 06:21 /etc/init/ebox.slapd-translucent.conf
-rw-r--r-- 1 root root 177 Feb 18 06:21 /etc/init/ebox.slapd-replica.conf
-rw-r--r-- 1 root root 225 Feb 18 06:21 /etc/init/ebox.slapd-frontend.conf
-rw-r--r-- 1 root root 74 Feb 18 06:21 /etc/init/ebox.apache2-usercorner.conf
-rw-r--r-- 1 root root 64 Feb 18 06:21 /etc/init/ebox.ad-pwdsync.conf

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

I'm wondering if upstart works ok within a chroot? I mean are you able to run status ebox.apache2-usercorner ? My tests are in a virtual machine.

Thanks

Revision history for this message
Fabrice Coutadeur (fabricesp) wrote :

I've installed Lucid in another partition and it's working fine. Invalidating the bug report.
Sorry for the noise

Fabrice

Changed in ebox-usersandgroups (Ubuntu):
status: In Progress → Invalid
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.