Ticket #2247 (closed defect: worksforme)
Zentyal installation error over upgrade to 10.04 Ubuntu server
| Reported by: | woody_sud@… | Owned by: | jacalvo@… |
|---|---|---|---|
| Milestone: | 2.0.X | Component: | base |
| Severity: | normal | Keywords: | |
| Cc: |
Description
Configurando ebox (2.0.1) ... Trace begun at /usr/share/perl5/EBox.pm line 93 EBox::logger at /usr/share/perl5/EBox/Exceptions/Base.pm line 58 EBox::Exceptions::Base::log('EBox::Exceptions::External=HASH(0x9a6b6f0)') called at /usr/share/perl5/EBox/Exceptions/External.pm line 42 EBox::Exceptions::External::new('EBox::Exceptions::External', 'The ebox user has not been set in the config file.') called at /usr/share/perl5/Error.pm line 182 Error::throw('EBox::Exceptions::External', 'The ebox user has not been set in the config file.') called at /usr/share/perl5/EBox/Config.pm line 168 EBox::Config::user at /usr/share/ebox/ebox-sudoers-friendly line 31 Log4perl: Seems like no initialization happened. Forgot to call init()? The ebox user has not been set in the config file.
I already purge all ebox old installation, all dirs, config files, users and same result.
Seems a problem with ebox sudoers creation but, I create manually ebox sudo and same result, same error.
I think install and test a million of time... is 1.4 going to be support for a while??? seriusly thinking to return 1.4..
Attachments
Change History
comment:2 Changed 3 years ago by jacalvo@…
- Status changed from new to closed
- Resolution set to fixed
Check if your /etc/sudoers file has this line at the end:
#includedir /etc/sudoers.d
If not, add it. But I don't know how it can be missing, it seems to be added by default on any Ubuntu system.
comment:3 Changed 2 years ago by thakralrohit@…
- Status changed from closed to reopened
- Resolution fixed deleted
I am having the same problem on version 2.0.16 the line #includedir....
is there in the sudoers file. any other ideas?
The error comes during installation stage and the ebox.conf is not there yet (as the installation hangs in between).
comment:4 Changed 2 years ago by jacalvo@…
- Status changed from reopened to closed
- Resolution set to worksforme
The ebox.conf file does not exist, it was a typo. The right path is /etc/ebox/99ebox.conf
Anyway, we can reproduce this. Could you provide more info about how did you install it? Was it on a regular Ubuntu server or a special one (cloud VM image, etc)?
The /etc/sudoers.d/ebox file should exists, and the above #includedir line present in /etc/sudoers
Hi,
Please, check if you have the file /etc/ebox/ebox.conf and that user key is set to ebox in this file.
Regards.