The process entropy-updates [Solved]

[orange_angel]

For some time every time I try to install something with equo I get this message: Another Entropy is currently running. If I go to System activity I find a process called entropy-updates, if I kill that one I can do the equo updates. I've had Sabayon installed on this computer for less than a week and this problem was not there from the beginning. It started around the same time as I went to another place where the wired Internet connection didn't work at first, so I thought perhaps those two problems where related, but now my Internet connection works and entropy-updates are still there.

A bit of more info on the process
Name: entropy-updates
Username: entropy-nopriv, root
Memory: 53 848 K
Shared memory: 5 444 K
Process ID: 8368
Parent: init [3]
Parent's ID: 1
Number of threads: 1
Command: /usr/bin/python2 -O /usr/libexec/entropy-updates-service --debug
Process status: sleeping - Process is waiting for something to happen.
User CPU usage: 0%
System CPU usage: 0%
CPU time spent running as user: 11,3 seconds
CPU time spent running in kernel: 0,8 seconds

The file /var/log/entropy/client-update.log contains a lot of lines like these:

Code: Select all

[16:35:09 21/04/2011 CEST] INFO: [16:35:09 21/04/2011 CEST] Loading Entropy Updates daemon: check every 14400s, logfile: /var/log/entropy/client-updater.log
[16:35:09 21/04/2011 CEST] INFO: [16:35:09 21/04/2011 CEST] _is_system_changed: resources locked!
[16:36:07 21/04/2011 CEST] INFO: [16:36:07 21/04/2011 CEST] client_ping: got client ping
[16:37:07 21/04/2011 CEST] INFO: [16:37:07 21/04/2011 CEST] client_ping: got client ping
[16:37:09 21/04/2011 CEST] INFO: [16:37:09 21/04/2011 CEST] Loading Entropy Updates daemon: check every 14400s, logfile: /var/log/entropy/client-updater.log
[16:37:09 21/04/2011 CEST] INFO: [16:37:09 21/04/2011 CEST] _is_system_changed: resources locked!
[16:38:07 21/04/2011 CEST] INFO: [16:38:07 21/04/2011 CEST] client_ping: got client ping
[16:39:08 21/04/2011 CEST] INFO: [16:39:08 21/04/2011 CEST] client_ping: got client ping
[16:39:09 21/04/2011 CEST] INFO: [16:39:09 21/04/2011 CEST] Loading Entropy Updates daemon: check every 14400s, logfile: /var/log/entropy/client-updater.log
[16:39:09 21/04/2011 CEST] INFO: [16:39:09 21/04/2011 CEST] _is_system_changed: resources locked!
[16:40:08 21/04/2011 CEST] INFO: [16:40:08 21/04/2011 CEST] client_ping: got client ping

Any ideas why this is happening?

[genfool]

Have seen this before, usually is caused by equo being out of date.
You said you can kill it and run the updates.
How are you updating?

su to root in a terminal
equo update
equo install equo entropy
equo upgrade
equo conf update

If this is how you have been updating, post the output of equo --version

[orange_angel]

Just to make sure I hadn't missed anything I did the updates and rebooted, but the process is still there.
My equo and entropy version is 1.0_alpha47 and I believe that's the latest version (I run the 64-bit version of Sabayon).

[genfool]

ok, something is still not correct then.
Before trying to trouble shoot this, rirst run
equo deptest
equo libtest

Is possible they may pull in a missing dependency or lib and cure it for you. I have a 64 bit system and is not an issue here.
Another option is to,
equo install magneto-core
Maybe by re-installing it will correct it, some just remove it, prefer not to have the notifier run at all.

Does sulfur open and work? or do you get the same error.

[orange_angel]

Well after doing that and rebooting the process is still there, but I can start sulfur and use equo commands, so I guess everything is alright then. Perhaps the process is supposed to be there all the time, and whatever was making it stop other instances of entropy is fixed now. Thanks for the help!

[genfool]

Good to hear it.
With entropy you are only allowed one instance at a time, so if the magneto notifier gets hung up, you will be given the error.
magneto can get hung up if it is out dated, finds entropy updates etc...
You were lucky that you were able to kill it, and update... sometimes can be sneaky and hard to kill.

I have found that rebooting, and at kdm or gdm, just use ctrl alt f1 to get to a terminal and log in as root, run your updates and reboot as normal, magneto never gets a chance to start with out starting your gui desktop.