On Linux - "SIGPIPE: write on a pipe with no reader"
6 Mar 2006 13:18:25 UTC
Topic 190871
(moderation:
I have had this scenario on two of six machines - "SIGPIPE: write on a pipe with no reader" (there
is an earlier thread about something similar noted below...)
2006-03-05 06:07:05 [Einstein@Home] Deferring communication with project for 47 minutes and 52 seconds
2006-03-05 06:07:05 [Einstein@Home] Deferring communication with project for 47 minutes and 52 seconds
adding: z1_1227.0__1796_S4R2a_2_0 (deflated 77%)
2006-03-05 06:30:58 [Einstein@Home] Computation for result z1_1227.0__1796_S4R2a finished
2006-03-05 06:30:58 [Einstein@Home] Started upload of z1_1227.0__1796_S4R2a_2_0
SIGPIPE: write on a pipe with no reader
Exiting...
The transcript shows that about 4 hours earlier it succeeded in getting work from the scheduler -
2006-03-05 01:13:18 [Einstein@Home] Deferring communication with project for 15 minutes and 4 seconds
2006-03-05 01:28:23 [---] Insufficient work; requesting more
2006-03-05 01:28:23 [Einstein@Home] Requesting 16824 seconds of work
2006-03-05 01:28:23 [Einstein@Home] Sending request to scheduler: http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
2006-03-05 01:28:59 [Einstein@Home] Scheduler RPC to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi succeeded
2006-03-05 01:28:59 [Einstein@Home] Got request to delete z1_0915.0
2006-03-05 01:28:59 [Einstein@Home] Started download of z1_1227.0
2006-03-05 01:29:00 [Einstein@Home] Started download of skygrid_1230_z_T06.dat
2006-03-05 01:29:01 [Einstein@Home] Finished download of skygrid_1230_z_T06.dat
2006-03-05 01:29:01 [Einstein@Home] Throughput 219885 bytes/sec
2006-03-05 01:29:32 [Einstein@Home] Finished download of z1_1227.0
2006-03-05 01:29:32 [Einstein@Home] Throughput 158679 bytes/sec
2006-03-05 01:29:32 [Einstein@Home] Starting result z1_1227.0__1796_S4R2a_2 using albert version 4.40
Archive: ../../projects/einstein.phys.uwm.edu/skygrid_1230_z_T06.dat
inflating: ./skygrid_1230_z_T06.dat
2006-03-05 05:06:42 [---] May run out of work in 0.10 days; requesting more
2006-03-05 05:06:42 [Einstein@Home] Requesting 8415 seconds of work
2006-03-05 05:06:42 [Einstein@Home] Sending request to scheduler: http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
2006-03-05 05:08:43 [Einstein@Home] Scheduler RPC to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi failed
2006-03-05 05:08:43 [Einstein@Home] Scheduler RPC to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi failed
2006-03-05 05:08:43 [Einstein@Home] No schedulers responded
2006-03-05 05:08:43 [Einstein@Home] No schedulers responded
[ ... more of same, leading up to SIGPIPE ... ]
There is an earlier thread from November, 2004 entitled "Linux version generates SIGPIPE"
My system -
Linux toto.gw-router.comcast.net 2.6.11-6mdk #1 Tue Mar 22 16:04:32 CET 2005 i686 AMD Athlon(tm) XP 2800+ unknown GNU/Linux
using albert version 4.40
Video card: BoardName "NVIDIA GeForce4 (generic)"
I am not running a BOINC screesaver.
On Linux - "SIGPIPE: write on a pipe with no reader"
)
Hi Jim !
There was a scheduled maintenance on the E@H hosts last sunday, and boinc had no connection to the E@H servers (my local time is UTC+1, CET)
==================================================
2006-03-05 09:03:12 [Einstein@Home] Message from server: Project is temporarily
shut down for maintenance
2006-03-05 09:03:12 [Einstein@Home] Project is down
2006-03-05 09:03:12 [Einstein@Home] Project is down
2006-03-05 10:03:16 [Einstein@Home] Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
2006-03-05 10:03:16 [Einstein@Home] Reason: To report results
2006-03-05 10:03:16 [Einstein@Home] Requesting 8640 seconds of new work, and reporting 1 results
2006-03-05 10:05:17 [---] Network error: a timeout was reached
2006-03-05 10:05:17 [---] Network error: a timeout was reached
==================================================
... that woud explain some strange behaviour from boinc; which version are you running (i'm at 5.2.15 on Linux) ?
Regards.
-rg-
RE: Hi Jim ! There was a
)
I am running 4.19 -
boinc_4.19_i686-pc-linux-gnu
I know about the server shutdown, this problem arose when work units
began to get distributed again. Maybe 4.19 is too old to be in use
anymore, I don't know. It seems to work almost all the time, and I
don't want a screensaver, so I have never changed to a later version.
Thanks.
I will update my BOINC to the
)
I will update my BOINC to the latest 5.xxx version. I had no idea
the versions had advanced so far.
Thanks.