Skip to content
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

Open
WurtZen opened this issue Nov 28, 2016 · 4 comments
Open

Portus crono not working #32

WurtZen opened this issue Nov 28, 2016 · 4 comments
Assignees

Comments

@WurtZen
Copy link

WurtZen commented Nov 28, 2016

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

@s4mur4i
Copy link

s4mur4i commented Jan 9, 2017

I tested crono by me, and same behavior without any changes:

/usr/sbin/portus_crono
/srv/Portus /
I, [2017-01-09T10:30:10.032961 #757] INFO -- : [Mailer config] Host: xxxx
I, [2017-01-09T10:30:10.033091 #757] INFO -- : [Mailer config] Protocol: https://
I, [2017-01-09T10:30:10.647051 #757] INFO -- : Loading Crono 0.9.0
I, [2017-01-09T10:30:10.647136 #757] INFO -- : Running in ruby 2.1.2p95 (2014-05-08 revision 45877) [x86_64-linux-gnu]
I, [2017-01-09T10:30:10.647202 #757] INFO -- : Jobs:
I, [2017-01-09T10:30:10.647492 #757] INFO -- : 'CatalogJob' with rule 'every 600 seconds' next time will perform at 2017-01-09 10:40:10 UTC
I, [2017-01-09T10:40:11.665984 #757] INFO -- : Perform CatalogJob
W, [2017-01-09T10:40:16.725723 #757] WARN -- : Exception: execution expired
I, [2017-01-09T10:40:16.725951 #757] INFO -- : Finished CatalogJob in 5.06 seconds

I am using registry:v2 container with portus:2.0 container.

@Djelibeybi
Copy link
Contributor

Djelibeybi commented Feb 13, 2017

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 docker run parameters for both so that the Crono container connects to the same registry and database as the main Portus container.

@mssola
Copy link
Contributor

mssola commented Feb 17, 2017

@WurtZen since PR #39 has just been merged, could you try it now ?

@ElGranLoky
Copy link

ElGranLoky commented Jul 21, 2017

With opensuse/portus:head

And crono enable in PORTUS_INIT_COMMAND bin/crono - same problem but no always happend

21/7/2017 13:01:40+ _timeout=150
21/7/2017 13:01:40+ _count=0
21/7/2017 13:01:40+ _status=0
21/7/2017 13:01:40+ stat /usr/sbin/portusctl
21/7/2017 13:01:40+ cmd_prefix='portusctl exec'
21/7/2017 13:01:40+ '[' 0 -le 150 ']'
21/7/2017 13:01:40+ portusctl exec crono
21/7/2017 13:01:49[Mailer config] Host: portus.test.lan
21/7/2017 13:01:49[Mailer config] Protocol: https://
21/7/2017 13:01:52I, [2017-07-21T11:01:52.237174 #40] INFO -- : Loading Crono 0.9.0
21/7/2017 13:01:52I, [2017-07-21T11:01:52.237406 #40] INFO -- : Running in ruby 2.1.9p490 (2016-03-30 revision 54437) [x86_64-linux-gnu]
21/7/2017 13:01:52I, [2017-07-21T11:01:52.237808 #40] INFO -- : Jobs:
21/7/2017 13:01:52I, [2017-07-21T11:01:52.238737 #40] INFO -- : 'CatalogJob' with rule 'every 600 seconds' next time will perform at 2017-07-21 11:11:52 UTC
21/7/2017 13:11:52I, [2017-07-21T11:11:52.237169 #40] INFO -- : Perform CatalogJob
21/7/2017 13:11:54Exception: execution expired
21/7/2017 13:11:54I, [2017-07-21T11:11:54.286987 #40] INFO -- : Finished CatalogJob in 2.05 seconds
21/7/2017 13:21:52I, [2017-07-21T11:21:52.237703 #40] INFO -- : Perform CatalogJob
21/7/2017 13:21:53I, [2017-07-21T11:21:53.718240 #40] INFO -- : Finished CatalogJob in 1.48 seconds
21/7/2017 13:31:52I, [2017-07-21T11:31:52.238033 #40] INFO -- : Perform CatalogJob
21/7/2017 13:31:54I, [2017-07-21T11:31:54.287527 #40] INFO -- : Finished CatalogJob in 2.05 seconds
21/7/2017 13:41:52I, [2017-07-21T11:41:52.238351 #40] INFO -- : Perform CatalogJob
21/7/2017 13:41:54Exception: execution expired
21/7/2017 13:41:54I, [2017-07-21T11:41:54.250668 #40] INFO -- : Finished CatalogJob in 2.01 seconds
21/7/2017 13:51:52I, [2017-07-21T11:51:52.238659 #40] INFO -- : Perform CatalogJob
21/7/2017 13:51:54I, [2017-07-21T11:51:54.284173 #40] INFO -- : Finished CatalogJob in 2.05 seconds
21/7/2017 14:01:52I, [2017-07-21T12:01:52.238976 #40] INFO -- : Perform CatalogJob
21/7/2017 14:01:54Exception: execution expired
21/7/2017 14:01:54I, [2017-07-21T12:01:54.251649 #40] INFO -- : Finished CatalogJob in 2.01 seconds
21/7/2017 14:11:52I, [2017-07-21T12:11:52.241182 #40] INFO -- : Perform CatalogJob
21/7/2017 14:11:54Exception: execution expired
21/7/2017 14:11:54I, [2017-07-21T12:11:54.250442 #40] INFO -- : Finished CatalogJob in 2.01 seconds

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants