Skip to content
  • Owner

    For me this log-message occurs when the job is either failed or deleted for instance, and there is (therefore) no queue info in the .local file for that job.

  • Owner

    Still a problem - 2 million lines of this in Jens log files with a file < 12 hours old.

  • I have currently 5373 jobs that reports this in the infoprovider.log every minute or so. They all share one thing. The job.XXXXXXXXXXXXXXXXXXXXXXXXXXxxx.errors file contains this (with different time stamps):

    2019-07-19T16:27:44Z Job state change FINISHED -> DELETED Reason: Job stayed unattended too long

    and the .local file looks like this:

    args=
    argscode=0
    rerun=0
    cleanuptime=19700108000000Z
    diskspace=0
    freestagein=no
    transfershare=_default
    priority=50

    Thus no queue info.

    It's a completely other question why these files aren't cleaned out of the system. Some of them are from mid June.

0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment