Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - fewter

Pages: [1]
1
Update -- my server is a Virtualbox virtual machine so I took a snapshot and tried
Quote
sudo apt-get install --reinstall ebox
The good news is that nothing was lost but the bad news is that my problem with the GUI is unchanged. Ebox still crashes as soon as I log onto the web interface, with this error message:
Quote
A really nasty bug has occurred
Exception
gconf error using function all_entries and params /ebox-ro/modules/mail/VDomains/keys/vdom7038/aliases/keys/vdom6159 Configuration server couldn't be contacted: CORBA error: IDL:omg.org/CORBA/COMM_FAILURE:1.0 at /usr/share/perl5/EBox/GConfModule.pm line 285.
Ebox is version 1.4. I have made sure that I am running the latest releases of everything using apt-get update and apt-get upgrade.
Is there any information I can provide that would help to find a solution?

2
Although my eBox 1.4 installation seems to be working OK, I can no longer log onto the web interface to administer it. The error message is set out below. I have tried the suggestions in this post:
http://forum.ebox-platform.com/index.php?topic=2606.0
but with no success.

Is there a way I can reinstall the eBox interface without affecting all my settings and data? All my email is on the system and I don't want to lose anything.

I don't know if this is relevant, but the ebox server (which is a Virtualbox virtual machine) has also stopped keeping time. The clock can be half an hour out until I correct it.

This is the full message I get when I log onto the web admin page:

Quote
A really nasty bug has occurred
Exception
gconf error using function all_entries and params /ebox-ro/modules/mail/VDomains/keys/vdom7038/aliases/keys/vdom6159 Configuration server couldn't be contacted: CORBA error: IDL:omg.org/CORBA/COMM_FAILURE:1.0 at /usr/share/perl5/EBox/GConfModule.pm line 285.
Trace
gconf error using function all_entries and params /ebox-ro/modules/mail/VDomains/keys/vdom7038/aliases/keys/vdom6159
Configuration server couldn't be contacted: CORBA error: IDL:omg.org/CORBA/COMM_FAILURE:1.0 at /usr/share/perl5/EBox/GConfModule.pm line 285.
at /usr/share/perl5/EBox/GConfModule.pm line 295
EBox::GConfModule::_gconf_wrapper('EBox::Mail=HASH(0xbe16080)', 'all_entries', '/ebox-ro/modules/mail/VDomains/keys/vdom7038/aliases/keys/vdo...') called at /usr/share/perl5/EBox/GConfModule.pm line 1043
EBox::GConfModule::_delete_dir_internal('EBox::Mail=HASH(0xbe16080)', '/ebox-ro/modules/mail/VDomains/keys/vdom7038/aliases/keys/vdo...') called at /usr/share/perl5/EBox/GConfModule.pm line 1049
EBox::GConfModule::_delete_dir_internal('EBox::Mail=HASH(0xbe16080)', '/ebox-ro/modules/mail/VDomains/keys/vdom7038/aliases/keys') called at /usr/share/perl5/EBox/GConfModule.pm line 1049
EBox::GConfModule::_delete_dir_internal('EBox::Mail=HASH(0xbe16080)', '/ebox-ro/modules/mail/VDomains/keys/vdom7038/aliases') called at /usr/share/perl5/EBox/GConfModule.pm line 1049
EBox::GConfModule::_delete_dir_internal('EBox::Mail=HASH(0xbe16080)', '/ebox-ro/modules/mail/VDomains/keys/vdom7038') called at /usr/share/perl5/EBox/GConfModule.pm line 1049
EBox::GConfModule::_delete_dir_internal('EBox::Mail=HASH(0xbe16080)', '/ebox-ro/modules/mail/VDomains/keys') called at /usr/share/perl5/EBox/GConfModule.pm line 1049
EBox::GConfModule::_delete_dir_internal('EBox::Mail=HASH(0xbe16080)', '/ebox-ro/modules/mail/VDomains') called at /usr/share/perl5/EBox/GConfModule.pm line 1049
EBox::GConfModule::_delete_dir_internal('EBox::Mail=HASH(0xbe16080)', '/ebox-ro/modules/mail') called at /usr/share/perl5/EBox/GConfModule.pm line 130
EBox::GConfModule::_load_from_file('EBox::Mail=HASH(0xbe16080)') called at /usr/share/perl5/EBox/GConfModule.pm line 58
EBox::GConfModule::_create('EBox::Mail', 'name', 'mail', 'printableName', 'Mail', 'domain', 'ebox-mail', 'ro', 1, ...) called at /usr/share/perl5/EBox/Mail.pm line 90
EBox::Mail::_create('EBox::Mail', 'ro', 1) called at /usr/share/perl5/EBox/Global.pm line 737
EBox::Global::modInstance('EBox::Global=HASH(0x9093c90)', 'mail') called at /usr/share/perl5/EBox/Global.pm line 664
EBox::Global::modInstancesOfType('EBox::Global=HASH(0x9093c90)', 'EBox::Mail::FilterProvider') called at /usr/share/perl5/EBox/Mail.pm line 1513
EBox::Mail::_filterDashboardSection('EBox::Mail=HASH(0xa20cdac)') called at /usr/share/perl5/EBox/Mail.pm line 1456
EBox::Mail::mailServicesWidget('EBox::Mail=HASH(0xa20cdac)', 'EBox::Dashboard::Widget=HASH(0x900ddb4)', 'undef') called at /usr/share/perl5/EBox/Module/Base.pm line 651
EBox::Module::Base::widget('EBox::Mail=HASH(0xa20cdac)', 'mail') called at /usr/share/perl5/EBox/CGI/Dashboard/Index.pm line 56
EBox::CGI::Dashboard::Index::masonParameters('EBox::CGI::Dashboard::Index=HASH(0x900de80)') called at /usr/share/perl5/EBox/CGI/Base.pm line 518
EBox::CGI::Base::_process('EBox::CGI::Dashboard::Index=HASH(0x900de80)') called at /usr/share/perl5/EBox/CGI/Base.pm line 263
EBox::CGI::Base::run('EBox::CGI::Dashboard::Index=HASH(0x900de80)') called at /usr/share/perl5/EBox/CGI/Run.pm line 120
EBox::CGI::Run::run('EBox::CGI::Run', '', '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(0x900dcd0)') 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(0x900dc88)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 170
ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0x900dc88)') called at /usr/lib/perl5/ModPerl/Registry.pm line 31
ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0x900dcd0)') called at -e line 0
eval {...} called at -e line 0

3
On a previous occasion I set up eBox using the defaults and it created a system user 'admin' in group 'eboxadmin' with the real name 'eBox Administrator'. As I understand it, it is this user that logs on automatically when the system starts.

This time when I installed eBox I managed to give this default user my own name, say 'john'. I configured everything in eBox but when I came to set up the users in eBox, I couldn't set up a user 'john'. I got an error message saying that the user already existed on the system. My eBox is useless if I can't have user 'john' receiving email and so on.

I have created a new user 'admin' on the host system with exactly the same permissions as 'john'. What I want to do now is to delete the 'john' account and make eBox use the 'admin' account instead. Is there a way to do this?

Pages: [1]