EON Errors

Current eOn code and boinc distributed computing

Moderator: moderators

Post Reply
Conan
Posts: 18
Joined: Wed Sep 08, 2010 1:03 pm

EON Errors

Post by Conan »

Getting a consistant error code on all work units processed by my Windows XP 32 bit machine

error: bundle: cannot rename client.log to client_0.log: Permission denied

This does not stop the work unit and does not cause it to fail but I was wondering why it is popping up on every work unit that I process?

I was getting the same error on my Linux Fedora 16 64 bit machine but that has been replaced by a different error now

SIGSEGV: segmentation violation
Stack trace (14 frames):
[0x82b4e0e]
[0xf771b400]
[0x82a27ef]
[0x82a289a]
[0x829babb]
[0x80481bf]
[0x83b48a0]
[0x834f8af]
[0x834f901]
[0x82b1786]
[0x82b1933]
[0x8048ceb]
[0x83474ef]
[0x8048171]

Exiting...


Again it does not stop the work unit and does not cause the work unit to fail, I am wondering what the error means?

Conan
NATE1
Posts: 3
Joined: Sat Jul 09, 2011 1:04 pm

Re: EON Errors

Post by NATE1 »

error: bundle: cannot rename client.log to client_0.log: Permission denied
win 7 64 bit
Conan
Posts: 18
Joined: Wed Sep 08, 2010 1:03 pm

Re: EON Errors

Post by Conan »

I have been getting a problem that every few days my BOINC Client gets disconnected from the manager and shuts down.
I have to close the manager and restart Boinc Manager and Client to get things going again.
This is happening on both my Linux computers.

It seems to be related to the eOn Project, as I get the following error messages before the boinc Client shuts down

21-Jan-2013 16:50:19 [eon2] Sending scheduler request: To report completed tasks.
21-Jan-2013 16:50:19 [eon2] Reporting 2 completed tasks, requesting new tasks for CPU
21-Jan-2013 16:50:21 [eon2] Scheduler request completed: got 12 new tasks
21-Jan-2013 16:50:23 [eon2] Started download of 211881964_11_8901667.tgz
21-Jan-2013 16:50:23 [eon2] Started download of 211881964_11_8901668.tgz
21-Jan-2013 16:50:25 [eon2] Finished download of 211881964_11_8901667.tgz
21-Jan-2013 16:50:25 [eon2] Finished download of 211881964_11_8901668.tgz
21-Jan-2013 16:50:25 [eon2] Started download of 1578966636_69_13881759.tgz
21-Jan-2013 16:50:25 [eon2] Started download of 211881964_11_8901661.tgz
21-Jan-2013 16:50:25 [eon2] MD5 computation error for 211881964_11_8901667.tgz: fopen() failed
21-Jan-2013 16:50:25 [eon2] Checksum or signature error for 211881964_11_8901667.tgz
21-Jan-2013 16:50:25 [eon2] MD5 computation error for 211881964_11_8901668.tgz: fopen() failed
21-Jan-2013 16:50:25 [eon2] Checksum or signature error for 211881964_11_8901668.tgz
21-Jan-2013 16:50:25 [---] Can't open client_state_next.xml: fopen() failed
21-Jan-2013 16:50:25 [---] Couldn't write state file: fopen() failed; giving up

This does not happen all the time just now and then. When it can't do the above task BOINC Client closes down.

Anyone have any ideas?

I am using the BOINC Client 6.12.34 with the 6.10.58 Manager, unsure if this is an issue but it does not affect any other project that I have been able to find.

Conan
Conan
Posts: 18
Joined: Wed Sep 08, 2010 1:03 pm

Re: EON Errors

Post by Conan »

Conan wrote:I have been getting a problem that every few days my BOINC Client gets disconnected from the manager and shuts down.
I have to close the manager and restart Boinc Manager and Client to get things going again.
This is happening on both my Linux computers.

It seems to be related to the eOn Project, as I get the following error messages before the boinc Client shuts down

21-Jan-2013 16:50:19 [eon2] Sending scheduler request: To report completed tasks.
21-Jan-2013 16:50:19 [eon2] Reporting 2 completed tasks, requesting new tasks for CPU
21-Jan-2013 16:50:21 [eon2] Scheduler request completed: got 12 new tasks
21-Jan-2013 16:50:23 [eon2] Started download of 211881964_11_8901667.tgz
21-Jan-2013 16:50:23 [eon2] Started download of 211881964_11_8901668.tgz
21-Jan-2013 16:50:25 [eon2] Finished download of 211881964_11_8901667.tgz
21-Jan-2013 16:50:25 [eon2] Finished download of 211881964_11_8901668.tgz
21-Jan-2013 16:50:25 [eon2] Started download of 1578966636_69_13881759.tgz
21-Jan-2013 16:50:25 [eon2] Started download of 211881964_11_8901661.tgz
21-Jan-2013 16:50:25[eon2] MD5 computation error for 211881964_11_8901667.tgz: fopen() failed
21-Jan-2013 16:50:25 [eon2] Checksum or signature error for 211881964_11_8901667.tgz
21-Jan-2013 16:50:25 [eon2] MD5 computation error for 211881964_11_8901668.tgz: fopen() failed
21-Jan-2013 16:50:25 [eon2] Checksum or signature error for 211881964_11_8901668.tgz
21-Jan-2013 16:50:25 [---] Can't open client_state_next.xml: fopen() failed
[21-Jan-2013 16:50:25 [---] Couldn't write state file: fopen() failed; giving up

This does not happen all the time just now and then. When it can't do the above task BOINC Client closes down.

Anyone have any ideas?

I am using the BOINC Client 6.12.34 with the 6.10.58 Manager, unsure if this is an issue but it does not affect any other project that I have been able to find.

Conan
This has happened again on my other Linux computer with the same error message and shut down Boinc Client for over 6 hours till I came home and restarted the Boinc Client.
The manager still runs and says "Disconnected", meaning no connection to the Client.

Why is this happening, I have had no problems in the past.

Conan
vmc
Posts: 1
Joined: Tue Apr 01, 2014 6:57 pm

Re: EON Errors

Post by vmc »

Conan wrote: I was getting the same error on my Linux Fedora 16 64 bit machine but that has been replaced by a different error now

SIGSEGV: segmentation violation
Stack trace (14 frames):
[0x82b4e0e]
[0xf771b400]
[0x82a27ef]
[0x82a289a]
[0x829babb]
[0x80481bf]
[0x83b48a0]
[0x834f8af]
[0x834f901]
[0x82b1786]
[0x82b1933]
[0x8048ceb]
[0x83474ef]
[0x8048171]

Exiting...


Again it does not stop the work unit and does not cause the work unit to fail, I am wondering what the error means?

Conan
I'm still getting these messages on this computer using 64bit Linux.
The SIGSEVs are not shown in 'dmesg' output though, what make me think, that the app is crashing with SIGSEV but the app is catching (via signal handler) and ignoring them.
Also, all the WUs are validated although they segfaulted somewhere ..

What's going on here?

PS: As OP already showed, the WUs also throw errors on Windows platforms, though not a segfault, but permission problems.
Post Reply