Worker shows up in Unhandled hosts "mod_gearman_worker down"

[litsupport.box]

In the log file, it looks like the max-jobs that the worker ran was hit. The setting in your config file is set to 1000. Here is the description of what that option is for.
max-jobs
Controls the amount of jobs a worker will do before he exits.
Use this to control how fast the amount of workers will go down after high load times. Disabled when set to 0. Default: 1000

It look like if this limit is hit, it will restart the worker. In the log file, it looks like that happened on your system but the worker wouldn't restart.
You may need to look in other log files to see why that didn't restart. See if there is any information in the messages or debug logs.

You can try and set the max-jobs to 0 to disable it, that should prevent it from restarting and then it will not have that issue.

What are the side effects of it being turned off?

[tgriep]

Actually, I'll take that back about my post of max-jobs. I think this is what caused the worker to restart.

idle-timeout=30
# Time after which an idling worker exists
# This parameter controls how fast your waiting workers will
# exit if there are no jobs waiting.

For some reason it wouldn't restart because of the PID file existed.

pidfile already exists, cannot start

The only thing left to do is to change debug=2 to debug=3 in the worker config file and wait until it fails again to get a better error from the log.

[litsupport.box]

Still getting this error, and debug level is 3. Log is exactly the same.

[litsupport.box]

I will just use this workaround - >

Created cronjob so mod_gearman_worker service gets checked (every hour) start if not working.

http://www.akamaras.com/linux/linux-scr ... s-stopped/

[lmiltchev]

Do you want us to keep the thread open in case the "workaround" doesn't solve the issue or we can lock this topic?