id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
1027	pantasks crash -- perhaps runtime duration related?	jhoblitt	eugene	"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"	enhancement	closed	high		PanTasks	unspecified	minor	fixed