Bugzilla – Bug 3699
pbs scheduler event generator must be started after logs appear
Last modified: 2006-04-07 16:30:44
You need to log in before you can comment on or make changes to this bug.
It seems that if the globus container is started after pbs logs appear for the day, the globus container can't see the logs at all, and no notifications come through.
Subject: Re: New: pbs scheduler event generator must be started after logs appear Ah crud. I mean, if the globus container is started BEFORE a log file appears for the day. Sorry. On Tue, 2005-08-30 at 00:51 -0500, bugzilla-daemon@mcs.anl.gov wrote: > http://bugzilla.globus.org/bugzilla/show_bug.cgi?id=3699 > > Summary: pbs scheduler event generator must be started after logs > appear > Product: GRAM > Version: 4.0.1 > Platform: PC > OS/Version: Linux > Status: NEW > Severity: normal > Priority: P3 > Component: wsrf managed job factory service > AssignedTo: lane@mcs.anl.gov > ReportedBy: damon@vpac.org > CC: damon@vpac.org,lane@mcs.anl.gov,madduri@mcs.anl.gov,smar > tin@mcs.anl.gov > > > It seems that if the globus container is started after pbs logs appear for the > day, the globus container can't see the logs at all, and no notifications come > through. > > > > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > You are on the CC list for the bug, or are watching someone who is.
Reassigning to Joe since he should have a better idea about what's going on here.
I've committed fixes to the log parser to eliminate the problem. An update is available on the globus web at http://www.globus.org/toolkit/advisories.html joe