Author Topic: Configuration server couldn't be contacted: CORBA error  (Read 2142 times)

azop

  • Zen Monk
  • **
  • Posts: 53
  • Karma: +0/-0
    • View Profile
Configuration server couldn't be contacted: CORBA error
« on: January 14, 2010, 03:31:04 pm »
I upgraded to the latest Ubuntu packages for Hardy.  openvpn wasn't working for me (the key was vulnerable so I renewed it but it still wouldn't start) so I restarted the server itself hoping to clear up any cache.  When the server restarted I can no longer log into ebox:

An internal error has ocurred. This is most probably a bug, relevant information can be found in the logs.

ebox.log shows:

2010/01/14 08:28:02 WARN> Union.pm:50 EBox::Types::Union::new - Union type cannot be optional. To use the non-defined value, choose EBox::Types::Union::Text
2010/01/14 08:28:03 ERROR> GConfModule.pm:289 EBox::GConfModule::_gconf_wrapper - gconf error using function all_entries and params /ebox-ro/modules/objects/objectTable/keys/obje8783/members/keys/memb8081
 Configuration server couldn't be contacted: CORBA error: IDL:omg.org/CORBA/COMM_FAILURE:1.0 at /usr/share/perl5/EBox/GConfModule.pm line 279.



 

javi

  • Zen Hero
  • *****
  • Posts: 1042
  • Karma: +0/-0
    • View Profile
Re: Configuration server couldn't be contacted: CORBA error
« Reply #1 on: January 14, 2010, 04:04:40 pm »
Check your free disk space please, and run:

sudo /etc/init.d/ebox apache restart

azop

  • Zen Monk
  • **
  • Posts: 53
  • Karma: +0/-0
    • View Profile
Re: Configuration server couldn't be contacted: CORBA error
« Reply #2 on: January 14, 2010, 04:07:11 pm »
Check your free disk space please, and run:

sudo /etc/init.d/ebox apache restart

I did that...the problem still exists.

2010/01/14 09:04:32 INFO> Module.pm:134 EBox::Module::restartService - Restarting service for module: apache
2010/01/14 09:05:15 INFO> EventDaemon.pm:291 EBox::EventDaemon::_loadModules - EBox::Event::Watcher::Runit loaded from registeredEvents
2010/01/14 09:05:17 ERROR> GConfModule.pm:289 EBox::GConfModule::_gconf_wrapper - gconf error using function all_entries and params /ebox-ro/modules/services/serviceTable/keys/serv1715
 Configuration server couldn't be contacted: CORBA error: IDL:omg.org/CORBA/COMM_FAILURE:1.0 at /usr/share/perl5/EBox/GConfModule.pm line 279.
2010/01/14 09:05:17 WARN> EventDaemon.pm:197 EBox::EventDaemon::__ANON__ - Error executing run from EBox::Event::Watcher::Runit: gconf error using function all_entries and params /ebox-ro/modules/services/serviceTable/keys/serv1715
 Configuration server couldn't be contacted: CORBA error: IDL:omg.org/CORBA/COMM_FAILURE:1.0 at /usr/share/perl5/EBox/GConfModule.pm line 279.
2010/01/14 09:05:24 ERROR> GConfModule.pm:289 EBox::GConfModule::_gconf_wrapper - gconf error using function all_entries and params /ebox-ro/modules/services/serviceTable/keys/serv1715
 Configuration server couldn't be contacted: CORBA error: IDL:omg.org/CORBA/COMM_FAILURE:1.0 at /usr/share/perl5/EBox/GConfModule.pm line 279.

javi

  • Zen Hero
  • *****
  • Posts: 1042
  • Karma: +0/-0
    • View Profile
Re: Configuration server couldn't be contacted: CORBA error
« Reply #3 on: January 14, 2010, 04:44:08 pm »
Ok, try this:

sudo pkill gconf
sudo pkill -9 gconf

sudo /etc/init.d/ebox apache restart


how much free disk space do you have?

azop

  • Zen Monk
  • **
  • Posts: 53
  • Karma: +0/-0
    • View Profile
Re: Configuration server couldn't be contacted: CORBA error
« Reply #4 on: January 14, 2010, 04:55:41 pm »
I did that...the problem still remains.  Disk space:

Filesystem            Size  Used Avail Use% Mounted on
/dev/sda1             1.8T  143G  1.7T   8% /
varrun               1005M  1.3M 1004M   1% /var/run
varlock              1005M     0 1005M   0% /var/lock
udev                 1005M   44K 1005M   1% /dev
devshm               1005M     0 1005M   0% /dev/shm

azop

  • Zen Monk
  • **
  • Posts: 53
  • Karma: +0/-0
    • View Profile
Re: Configuration server couldn't be contacted: CORBA error
« Reply #5 on: January 14, 2010, 04:58:57 pm »
I did that...the problem still remains.  Disk space:

Filesystem            Size  Used Avail Use% Mounted on
/dev/sda1             1.8T  143G  1.7T   8% /
varrun               1005M  1.3M 1004M   1% /var/run
varlock              1005M     0 1005M   0% /var/lock
udev                 1005M   44K 1005M   1% /dev
devshm               1005M     0 1005M   0% /dev/shm


I'm toying with upgrading to 1.2.  Would recommend this is the current (slightly broken) state?

Thanks

javi

  • Zen Hero
  • *****
  • Posts: 1042
  • Karma: +0/-0
    • View Profile
Re: Configuration server couldn't be contacted: CORBA error
« Reply #6 on: January 14, 2010, 05:00:26 pm »
I dont know what's happening and it's difficult for me to troubleshoot it from here. This might sound a bit radical, but how about a reboot? :P Actually, I would like to put my hands on it to figure out what's happening...

So you have upgraded from where to where?

azop

  • Zen Monk
  • **
  • Posts: 53
  • Karma: +0/-0
    • View Profile
Re: Configuration server couldn't be contacted: CORBA error
« Reply #7 on: January 14, 2010, 05:04:13 pm »
I dont know what's happening and it's difficult for me to troubleshoot it from here. This might sound a bit radical, but how about a reboot? :P Actually, I would like to put my hands on it to figure out what's happening...

So you have upgraded from where to where?

I've rebooted twice :(

I upgraded what was in Hardy...I don't believe I used a PPA.


Actually I can't PM you...can you email me?  chall <at> callawayso <dot> org
« Last Edit: January 14, 2010, 05:06:23 pm by azop »

azop

  • Zen Monk
  • **
  • Posts: 53
  • Karma: +0/-0
    • View Profile
Re: Configuration server couldn't be contacted: CORBA error
« Reply #8 on: January 14, 2010, 05:25:13 pm »
Quote
Actually I can't PM you...can you email me?  chall <at> callawayso <dot> org

I noticed that gconf2 was upgraded recently.  Would that have any known issues?

azop

  • Zen Monk
  • **
  • Posts: 53
  • Karma: +0/-0
    • View Profile
Re: Configuration server couldn't be contacted: CORBA error
« Reply #9 on: January 14, 2010, 07:37:17 pm »
I tried to upgrade to 1.2 and had this error starting ebox-network:

Setting up ebox-network (1.2.7-0ubuntu1~ppa1~hardy1) ...
gconf error using function all_entries and params /ebox-ro/modules/services/serviceTable/keys/serv1715
 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.

azop

  • Zen Monk
  • **
  • Posts: 53
  • Karma: +0/-0
    • View Profile
Re: Configuration server couldn't be contacted: CORBA error
« Reply #10 on: January 14, 2010, 10:46:47 pm »
well I've really mucked something up and that email address won't work.  Try curtishall <at> gmail.com