Conversation
Oops, sorry 😑 |
|
Only a few lint from travis to fix: |
simahawk
left a comment
There was a problem hiding this comment.
LG, I'd replace a var name, but that's it :)
tnx for the change!
| def _connection_info_for(db_name): | ||
| db_or_uri, connection_info = odoo.sql_db.connection_info_for(db_name) | ||
|
|
||
| for p in ('host', 'port'): |
There was a problem hiding this comment.
If you don't mind, I will keep it as it to keep it consistent with the same piece of code that is in the other versions of the module.
There was a problem hiding this comment.
yeah, sorry, I missed the original code 😅 👍
a96e0de to
c01ddf8
Compare
|
Could this merge cause queue to not start anymore? I took the latest 10.0 merge and deployed it in my test-environment and now no jobs will start anymore. In the log the job runner gives the usual acknowledgement it runs on the db etc. |
|
No, no error messages, although log in DEBUG level. And no connection pooler either.
Met vriendelijke groet/Kind regards,
Magnus Red
Willem Hulshof
+31 88 696 60 00 | +31 651 243 710 | www.magnus.nl<http://www.magnus.nl/red/>
[id:4FD331F6-E3AE-4679-826C-9D6015959C97]
Van: Nils Hamerlinck <notifications@github.com>
Beantwoorden - Aan: OCA/queue <reply@reply.github.com>
Datum: donderdag 2 augustus 2018 om 14:04
Aan: OCA/queue <queue@noreply.github.com>
CC: Willem Hulshof <w.hulshof@magnus.nl>, Mention <mention@noreply.github.com>
Onderwerp: Re: [OCA/queue] [FIX/ADD] configuration options (#86)
Hi @whulshof<https://github.com/whulshof>, the PR for 10.0 is #77<#77>
Any error message? Are you using a connection pooler (pgbouncer)?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#86 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AK1rqbUjXNe06olUDo0j6M-tSSIEsEJbks5uMuqtgaJpZM4Vh9Ua>.
|
|
A common cause for jobs not starting is jobs in remaining in state |
|
I know that, so I requeued or set to done all pending, started en enqueued jobs already. To no avail.
But do I have to do any configuration change as the result of Nils’ PR?
Met vriendelijke groet/Kind regards,
Magnus Red
Willem Hulshof
+31 88 696 60 00 | +31 651 243 710 | www.magnus.nl<http://www.magnus.nl/red/>
[id:4FD331F6-E3AE-4679-826C-9D6015959C97]
Van: "Stéphane Bidoul (ACSONE)" <notifications@github.com>
Beantwoorden - Aan: OCA/queue <reply@reply.github.com>
Datum: donderdag 2 augustus 2018 om 14:16
Aan: OCA/queue <queue@noreply.github.com>
CC: Willem Hulshof <w.hulshof@magnus.nl>, Mention <mention@noreply.github.com>
Onderwerp: Re: [OCA/queue] [FIX/ADD] configuration options (#86)
A common cause for jobs not starting is jobs in remaining in state enqueued or started when the server has not been shut down properly.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#86 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AK1rqRKOI6Az_hKuL667Y7v5edaJOPlqks5uMu2ogaJpZM4Vh9Ua>.
|
|
@whulshof do you have more than 1 database visible by your Odoo instance? If it's the case, can you retry with only 1 database visible by odoo? |
|
Yes, i’ll do right away
Met vriendelijke groet/Kind regards,
Magnus Red
Willem Hulshof
+31 88 696 60 00 | +31 651 243 710 | www.magnus.nl<http://www.magnus.nl/red/>
[id:4FD331F6-E3AE-4679-826C-9D6015959C97]
Van: "Laurent Mignon (ACSONE)" <notifications@github.com>
Beantwoorden - Aan: OCA/queue <reply@reply.github.com>
Datum: donderdag 2 augustus 2018 om 14:40
Aan: OCA/queue <queue@noreply.github.com>
CC: Willem Hulshof <w.hulshof@magnus.nl>, Mention <mention@noreply.github.com>
Onderwerp: Re: [OCA/queue] [FIX/ADD] configuration options (#86)
@whulshof<https://github.com/whulshof> do you have more than 1 database visible by your Odoo instance? If it's the case, can you retry with only 1 database visible by odoo?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#86 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AK1rqdvL5PZ_OqIiDotEs3sYXxN1_7vZks5uMvMcgaJpZM4Vh9Ua>.
|
|
This seems to be doing the trick! Is there a possibility to keep the job queue working for more than 1 database, like before? If yes, how?
Met vriendelijke groet/Kind regards,
Magnus Red
Willem Hulshof
+31 88 696 60 00 | +31 651 243 710 | www.magnus.nl<http://www.magnus.nl/red/>
[id:4FD331F6-E3AE-4679-826C-9D6015959C97]
Van: "Laurent Mignon (ACSONE)" <notifications@github.com>
Beantwoorden - Aan: OCA/queue <reply@reply.github.com>
Datum: donderdag 2 augustus 2018 om 14:40
Aan: OCA/queue <queue@noreply.github.com>
CC: Willem Hulshof <w.hulshof@magnus.nl>, Mention <mention@noreply.github.com>
Onderwerp: Re: [OCA/queue] [FIX/ADD] configuration options (#86)
@whulshof<https://github.com/whulshof> do you have more than 1 database visible by your Odoo instance? If it's the case, can you retry with only 1 database visible by odoo?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#86 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AK1rqdvL5PZ_OqIiDotEs3sYXxN1_7vZks5uMvMcgaJpZM4Vh9Ua>.
|
http://localhost;-)