Process don't get started: I get the »Unknown process:« message. [#1627924]

I have a problem starting a background process. I always get the message:

Typ	bg_process
Datum	Dienstag, Juni 12, 2012 - 02:15
Benutzer	test
Standort	http://www.some-server.com/bgp%3Astart/ab348a8a76d544e777a1ae9438b3dd2f/a223792cf368a14feebd84c03ea43ded
Referrer	http://www.some-server.com/node/add/poi?field_poi_reference=1379&render=overlay
Message	Unknown process: ab348a8a76d544e777a1ae9438b3dd2f
Schweregrad	Mitteilung
Operationen

And after that:

Typ	Zugriff verweigert (access denied)
Datum	Dienstag, Juni 12, 2012 - 02:15
Benutzer	test
Standort	http://www.some-server.com/bgp%3Astart/ab348a8a76d544e777a1ae9438b3dd2f/a223792cf368a14feebd84c03ea43ded
Referrer	http://www.some-server.com/node/add/poi?field_poi_reference=1379&render=overlay
Message	bgp:start/ab348a8a76d544e777a1ae9438b3dd2f/a223792cf368a14feebd84c03ea43ded
Schweregrad	Warnung

And the process will not start. The strange thing is, that this problem occurs after I migrated to an other server although it has exactly the same configuration. Before everything worked well.

I'am using the actual version 7.x-1.12.

Does anybody know, would could be the cause?

Comments

Comment #1

gielfeldt CreditAttribution: gielfeldt commented 12 June 2012 at 04:55

Yes. When migrating db to another system, some of the background process configuration is copied as well, and this might cause problems. Go to the Background Process settings page and click "Determine default service host". Let me know if this works.

Comment #2

gunwald CreditAttribution: gunwald commented 12 June 2012 at 11:00

Thank you very much for your fast reply. That was the solution, it works know very well.

Comment #3

gunwald CreditAttribution: gunwald commented 13 June 2012 at 01:37

It seems that unfortunately I was a little but too enthusiastic. The problem occurs again but not alway like before but sometimes. To click "Determine default service host" always helps for a while.
The strange thing is, that is seems the problem only occurs when I start the bg_process within a menu_hook (hook_node_update), but not starting it manually.
Don't know whether or not this hint could be useful.
Do I have to check some server configurations? Or what else cloud I do?

Comment #4

gielfeldt CreditAttribution: gielfeldt commented 13 June 2012 at 14:03

Aha. This might be a known bug that I'm working on a solution for. I assume your using MySQL and InnoDB?

If so, you can change the database engine for the background_process table to MyISAM. See this thread for an example of how to do it and to follow the progress of the bugfix.

EDIT: Grammar correction...

Active

» Fixed

A better alternative to change table type has been committed: http://drupal.org/node/1489316#comment-6157798

Also, the need for doing a "Determine default service host" after db migration has been eliminated in many (if not most) use cases, namely when $base_url actually does work.