id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
1456	consider time stamping pantasks error messages	bills	eugene	"pantasks for summit copy  died tonight. The stderr log had the output below. The information would be more useful if it were time
stamped so we could correlate it with the time of the crash

bound to port: 2000
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 (0 tries)
controller is not responding (0 tries)
controller is not responding (0 tries)
controller is not responding (0 tries)
controller is not responding (1 tries)
controller is not responding (0 tries)
controller is not responding (0 tries)
controller is not responding (0 tries)
controller is not responding (0 tries)
ERROR: missing metadata output name on first line
ERROR: missing metadata output name on first line
controller is not responding (0 tries)
controller is not responding (1 tries)
controller is not responding (0 tries)
ERROR: missing metadata output name on first line
controller is not responding (0 tries)
controller is not responding (0 tries)
ERROR: missing metadata output name on first line
ReadtoIOBuffer read error: Connection reset by peer
ReadtoIOBuffer read error: Connection reset by peer
garbage in pcontrol reponse
missing PID in pcontrol message : programming error
ControllerCommand returns: 1
ControllerCommand response: Njobs: 0"	enhancement	new	normal		PanTasks		normal			Serge CHASTEL eugene