IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Opened 18 years ago

Closed 18 years ago

#1027 closed enhancement (fixed)

pantasks crash -- perhaps runtime duration related?

Reported by: jhoblitt Owned by: eugene
Priority: high Milestone:
Component: PanTasks Version: unspecified
Severity: minor Keywords:
Cc:

Description

This is the output of pantasks crashing on ipp019 after running summit.copy.pro for several days.

job dtime: 16.394671
controller is not responding (0 tries)
controller is not responding (1 tries)
controller is not responding (2 tries)
controller is not responding (3 tries)
controller is not responding (4 tries)
controller is not responding (5 tries)
controller is not responding (6 tries)
controller is not responding (7 tries)
controller is not responding (8 tries)
controller is not responding (9 tries)
controller still not responding, giving up
controller is not responding (0 tries)
controller is not responding (1 tries)
controller is not responding (2 tries)
controller is not responding (3 tries)
controller is not responding (4 tries)
controller is not responding (5 tries)
controller is not responding (6 tries)
controller is not responding (7 tries)
controller is not responding (8 tries)
controller is not responding (9 tries)
controller still not responding, giving up
pipe error:: Too many open files

timeout for: pztool -pendingimfile -limit 120
job exit status: 255
job host: ipp019
job dtime: 16.394671
controller is not responding (0 tries)
controller is not responding (1 tries)
controller is not responding (2 tries)
controller is not responding (3 tries)
controller is not responding (4 tries)
controller is not responding (5 tries)
controller is not responding (6 tries)
controller is not responding (7 tries)
controller is not responding (8 tries)
controller is not responding (9 tries)
controller still not responding, giving up
pipe error:: Too many open files
pipe error:: Too many open files
pipe error:: Too many open files
pipe error:: Too many open files
ReadtoIOBuffer read error: Bad file descriptor
serious IO error

Change History (1)

comment:1 by jhoblitt, 18 years ago

Resolution: fixed
Status: newclosed

haven't seen this for awhile

Note: See TracTickets for help on using tickets.