The ebox group has not been set in the config file

[zentyal@…]

I was changing file permissions of one of the directories we share using Samba and soon afterwards no more login was possible: The Zentyal web UI reported the error given below, and connecting via ssh failed with "connection reset by peer":

Zentyal web error:

Trace The ebox group has not been set in the config file. at /usr/share/perl5/EBox/Config.pm line 179 EBox::Config::groups() called at /usr/share/perl5/EBox.pm line 127 EBox::init() called at /usr/share/ebox/cgi/ebox.cgi line 34 ModPerl::ROOT::ModPerl::Registry::usr_share_ebox_cgi_ebox_2ecgi::handler('Apache2::RequestRec?=SCALAR(0x7faf2eb973f8)') 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(0x7faf2eb96ee8)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 170 ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0x7faf2eb96ee8)') called at /usr/lib/perl5/ModPerl/Registry.pm line 31 ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec?=SCALAR(0x7faf2eb973f8)') called at -e line 0 eval {...} called at -e line 0

Has anybody run into a similar problem and could help me here?

Thanks for any pointers!

[jamor@…]

You need to have the variable group set to ebox in the config file.

If you are using 2.0 the file is /etc/ebox/99ebox.conf

If you are in 2.1 or greater the file is /etc/zentyal/zentyal.conf

Go to the appropiate fiel and assure that exists the following assignment:

group = ebox

I am interested on how you had come to this problem:

• do you modified the fiels by hand ?

• or you upgraded from 2.0 to a 2.1?

• or you restored in 2.0 a backup made in 2.1? or a 2.1 in 2.0?.

Cheers,

Javier

[jacalvo@…]

We can't reproduce this, please reopen if you can answer javier's questions or provide enough information (preferably detailed steps) on how to do it.

Also, it seems you are using 2.0, which I have never seen this bug, but maybe you want to try the next stable version (2.2) which has just been published.