pending state

[mehulbhadra]

when i click button in odoo backend its jobs are always in pending state....

[sschuchlenz]

+1 (odoo v8, magento 1.9.x)

I already tried to use --workers=4 and rely on connector's jobrunner (setting all the options and disabling Enqueue Jobs) but no luck with that either. I'm using a multi-database install and synchronizing metadata works fine, only when I add one of the background jobs in Magento -> Backends the job never gets executed.

Whenever I try to reschedule a job, the Enqueue time stays empty. Logfile does not give any errors and other jobs (like fetching email) work fine.

[sschuchlenz]

Could someone please have a look and provide assistance? This is a dealbreaker since we need the sync between Magento and Odoo for our business. Thank you in advance.

[guewen]

Metadata sync is done synchronously, it doesn't use the jobs.
Jobs staying pending means you have no job runner started.
If you hadn't yet, have a look on http://odoo-connector.com/guides/jobrunner.html
If you think you already did what this page says, please give details on your configuration (what command you run to start Odoo, your connector revision, what contains your odoo configuration file)

[sschuchlenz]

I configured the jobrunner part as mentioned in the link you provided (thanks for the answer) and since there are no errors in the log I reckon it is working as it should.

Here is my odoo start script: http://pastebin.com/SLNerb4w

The versions of the magento connector and its dependencies are the latest git commits from the 8.0 branches.

[sschuchlenz]

Update: I just checked the logfile again, it says:

2015-12-31 10:17:13,168 4113 INFO ? openerp.addons.connector.jobrunner.runner: starting
2015-12-31 10:17:13,168 4113 INFO ? openerp.addons.connector.jobrunner.runner: initializing database connections
2015-12-31 10:17:13,195 4113 INFO ? openerp.addons.connector.jobrunner.runner: database connections ready

This tells me that the jobrunner should be running I guess, but the line from the link you provided is missing:

...INFO...connector.jobrunner.runner: connector runner ready for db <dbname>

Is this due to the fact that we're running a multiple database environment? Is there a way to specify which databased the jobrunner should "take into account"?

[sbidoul]

Ok, almost there. The jobrunner is starting but not connecting to your database.

Since you have %d in your dbfilter, you need OCA/connector#166 or OCA/connector#165.

[sbidoul]

Is there a way to specify which databased the jobrunner should "take into account"?

The connector currently tries to use dbfilter to determine which databases to connect to. But that will probably be removed in the next major release, so connector will connect to all databases where connector is installed, much like the Odoo cron scheduler which is running on all available databases (unless the db_name option is used).

[sschuchlenz]

That did it - thank you very much for your support, especially over the holidays!

[mehulbhadra]

Import is working properly from magente to odoo..can we export product from
odoo to magento

On Sat, Jan 2, 2016 at 2:56 PM, sschuchlenz [email protected]
wrote:

That did it - thank you very much for your support, especially over the
holidays!

—
Reply to this email directly or view it on GitHub
#186 (comment)
.

Thanks,
Mehul Bhadra

[guewen]

See #188.