Jobs are not executed

[nolaan.ge...@gmail.com]

Hi,
I've this error while trying to run a job with minion, it works on my workstation but it seems I've a configuration problem on the server eventhough all modules are up to date.

"Can't use string (\"[\"/home/clipwebmanager/ClipWebMa\"...) as an ARRAY ref while \"strict refs\" in use at /home/clipwebmanager/perl5/lib/perl5/Minion/Job.pm line 62.\n"

When I retry the job, the worker segfaults with those messages:

message type 0x43 arrived from server while idle
message type 0x5a arrived from server while idle

You can find the task there : http://fpaste.scsys.co.uk/539761

[Joel Berger]

I've seen this before too. It seems to happen when you listen to postgres notifications before forking. Standard usage in Mojolicious/Minion use-cases shouldn't be affected. Are you listening to postgres notifications in the startup method for an app that uses minion? If so, you probably don't want to do so when starting the workers.

[Nolaan]

Hello,
I'm not following you, I'm just running the basic example provided in the
tutorial, nothing more fancy.

[Nolaan]

In debug mode with Confess, I have this output :

ERROR:  prepared statement "dbdpg_p20543_4" does not exist
at /usr/local/share/perl5/Mojo/Pg.pm line 74.
       eval {...} called at /usr/local/share/perl5/Mojo/Pg.pm line 74
       eval {...} called at /usr/local/share/perl5/Mojo/Pg.pm line 74
       Mojo::Pg::_dequeue(Mojo::Pg=HASH(0x4e24cf8)) called at /usr/local/share/perl5/Mojo/Pg.pm line 39
       Mojo::Pg::db(Mojo::Pg=HASH(0x4e24cf8)) called at /home/clipwebmanager/perl5/lib/perl5/Minion/Backend/Pg.pm line 25
       Minion::Backend::Pg::dequeue(Minion::Backend::Pg=HASH(0x50f7cd0), 4, 5, HASH(0x513ad50)) called at /home/clipwebmanager/perl5/lib/perl5/Minion/Worker.pm line 16
       Minion::Worker::dequeue(Minion::Worker=HASH(0x5149510), 5, HASH(0x513ad50)) called at /home/clipwebmanager/perl5/lib/perl5/Minion/Command/minion/worker.pm line 67
       Minion::Command::minion::worker::_work(Minion::Command::minion::worker=HASH(0x512b528)) called at /home/clipwebmanager/perl5/lib/perl5/Minion/Command/minion/worker.pm line 36
       eval {...} called at /home/clipwebmanager/perl5/lib/perl5/Minion/Command/minion/worker.pm line 36
       Minion::Command::minion::worker::run(Minion::Command::minion::worker=HASH(0x512b528)) called at /home/clipwebmanager/perl5/lib/perl5/Mojolicious/Commands.pm line 54
       Mojolicious::Commands::run(Minion::Command::minion=HASH(0x50fd1d0), 'worker') called at /home/clipwebmanager/perl5/lib/perl5/Mojolicious/Commands.pm line 54
       Mojolicious::Commands::run(Mojolicious::Commands=HASH(0x4e17030), 'minion', 'worker') called at /home/clipwebmanager/perl5/lib/perl5/Mojolicious.pm line 187
       Mojolicious::start(ClipWebManager=HASH(0x31c3b38)) called at /home/clipwebmanager/perl5/lib/perl5/Mojolicious/Commands.pm line 71
       Mojolicious::Commands::start_app('Mojolicious::Commands', 'ClipWebManager') called at script/clipwebmanager line 11

[Joel Berger]

Ok so if your app is just the example then that error is certainly not expected. That said since it is an error I've seen when connections are crossed, is it possible your pg setup is unusual? Behind an haproxy for example?