GenericAgent, Can´t create PID

[ferrosti]

I am running into some problems with the Generic Agent on one of my systems.
I have got several GAs which close Out of Office replies automatically every ten minutes. Every once in a while my log shows

Code: Select all

[Thu Jul  7 14:20:03 2011][Notice][Kernel::System::PID::PIDCreate] Can't create PID GenericAgent, because it's already running (*FQDN*/9583)!
[Thu Jul  7 14:20:03 2011][Notice][Kernel::System::GenericAgent::JobRun] Run GenericAgent Job 'CLOSE Abwesenheit' from db.
[Thu Jul  7 14:20:03 2011][Notice][Kernel::System::GenericAgent::JobRun] Run GenericAgent Job 'CLOSE Abwesenheitsnotiz' from db.
[Thu Jul  7 14:20:03 2011][Notice][Kernel::System::GenericAgent::JobRun] Run GenericAgent Job 'CLOSE Automatische' from db.
[Thu Jul  7 14:20:03 2011][Notice][Kernel::System::GenericAgent::JobRun] Run GenericAgent Job 'CLOSE Autoreply' from db.
[Thu Jul  7 14:20:03 2011][Notice][Kernel::System::GenericAgent::JobRun] Run GenericAgent Job 'CLOSE Out of Office' from db.

Weird thing is that even when I look into my DB, there is no ProcessID noted in its respective table as I would assume when it fails on the very first log entry. All others come too fast to look at DB level.
Sometimes it happens that this error comes up in the middle.
Version is 3.0.8.

Entering GA with force option into cron is no good idea.

Does someone else have this problem?

[crythias]

Yes, I've encountered it and ignored it, probably because I had multiple generic agent database entries or something.

[ferrosti]

Hi, crythias,

this is true, I have got all of them in DB. All these Jobs are supposed to run every 10 minutes. It is not too bad if theres one or two OoO replies not closed within this period.
If I´ve got a job that is supposed to run once a day and is not executed I might be screwed.

Do you see any regularity in this behavior in your log files?