Hallo Christoph,
> after some time of rather quiet WMS operation we have (again) one WMS
> server that is stuck in changing job states. It might be just by change
> the one server that we upgraded to most recent WMS release 3.1.29
> (following the details in the release node of course). Some few test
> jobs went through but after one of production work the machine seems to
> be stuck.
>
> There are some jobs on the WMS that are still in the state running or
> scheduled although we know that they are done (even the output sandbox
> is on the WMS!). New jobs stay in the infamous Ready/unavailable status
Did you check this page:
http://goc.grid.sinica.edu.tw/gocwiki/Jobs_sent_to_some_CE_stay_in_Ready_state_forever
> for many hours. Trying to understand what's happening to those jobs, we
> see that they make it until to the actual Condor submit but remain in
> the Condor state Idle for whatever reason.
Any clues in the Condor logfiles? You can raise the logging level and
logfile sizes in the Condor configuration file, then restart Condor-G.
|