PHP warning makes debugging a chore about gearmanmanager HOT 10 CLOSED

Oh? and how did u make workers to log there? I get warning and notices in error log allright, but fatal errors (logged in Gearman Manager log as 'child has exited') never make it there.

from gearmanmanager.

I will leave the debate about the "recommended debugging method" alone. However, the error you mention is coming from PECL/Gearman and not GearmanManager. Please file a bug in the PECL bug system for tthat.

from gearmanmanager.

Recommended = copy & paste from GearmanManager readme debug section.

I'll try reporting it in PECL bug system, but I will not hold my breath - PECL package receives hardly any attention.

from gearmanmanager.

Touché. The beauty of OSS. I guess one of my contributors added that.

from gearmanmanager.

BTW how does one efficiently debug workers?

from gearmanmanager.

I log all their output to a logfile and echo debug info. But, I am kind of old school.

from gearmanmanager.

I do the same, but the problems start if worker dies completly - does not work at all. In that case exactly nothing is echoed or logged. Uncaught exception is the same.

from gearmanmanager.

Those things go to my PHP error log.

from gearmanmanager.

For the record – I added this because it seemed impossible to find out why workers might die otherwise. There are a couple @ all around which hide errors in work-code. If however you workers work, you should continue with scream. It is as the README advices, a tool for debugging. ;-)

from gearmanmanager.

@brianlmoon : what is the answer to @c2h5oh's last question?

Oh? and how did u make workers to log there?

from gearmanmanager.