While experimenting I could reproduce this somehow.
There was a boinc process running in the background still (for whatever reason,
I cannot say), and starting a new one failed quickly like this:
==> stderrdae.txt <==
gstate.init() failed
Error Code: -180
==> stdoutdae.txt <==
18-Sep-2010 23:58:42 [---] [error] GUI RPC bind to port 31416 failed: 98
"is_running" did not report BOINC to be running already - because the PID
obviously was not the same as in the PIDFILE anymore.
I will fix this by adding a message (via log_progress_msg, which is
ignored on Ubuntu btw (bug 282638)!).
There have been quite a log of duplicated for this, so there really must
be something triggering this, but I could not reproduce it a second time
(after "sudo pkill -u boinc").
btw: using "pgrep -u boinc" and "pkill -u boinc" to see if BOINC is
running already, or to more reliably kill all running processed (even if
PIDFILE is wrong) might make sense.
** Changed in: boinc (Ubuntu)
Status: Triaged => In Progress
** Changed in: boinc (Ubuntu)
Assignee: (unassigned) => Daniel Hahler (blueyed)
--
package boinc-client 6.10.58+dfsg-2 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1: chrt failure
("no such process")
https://bugs.launchpad.net/bugs/629649
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
