-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Portus crono not working #32
Comments
I tested crono by me, and same behavior without any changes: /usr/sbin/portus_crono I am using registry:v2 container with portus:2.0 container. |
I just submitted PR #39 which enables Crono support in the default image. This has been working for me and I don't see any execution timeouts on my setup. Would be great if you could test it to see if it works for you. Note that you have to run two containers: one for Portus itself and another one for Crono. You should match the |
With opensuse/portus:headAnd crono enable in PORTUS_INIT_COMMAND bin/crono - same problem but no always happend 21/7/2017 13:01:40+ _timeout=150 |
I'm running opensuse/portus:head on CentOS docker host
and registry ver 2.5.1
when running just the /usr/sbin/portus_crono
I get this output
I, [2016-11-28T21:38:06.229185 #196] INFO -- : 'CatalogJob' with rule 'every 600 seconds' next time will perform at 2016-11-28 21:48:06 UTC
I, [2016-11-28T21:48:06.228857 #196] INFO -- : Perform CatalogJob
Exception: execution expired
I, [2016-11-28T21:48:26.245175 #196] INFO -- : Finished CatalogJob in 20.02 seconds
And nothing is updated in portus.
When trying to check the service
wwwrun@e1616e9f2a11:/> systemctl status portus_crono
Failed to get D-Bus connection: Unknown error -1
The text was updated successfully, but these errors were encountered: