[opensuse-buildservice] /srv/obs/events/lastnotifications

Carsten Höger

24 Feb 2020 24 Feb '20

12:04

Hi, I recently noticed that this file is quite huge in our installation: 2.8G /srv/obs/events/lastnotifications Can this file be removed? It looks like a logfile to me with new entries added at the end. Is some component of OBS reading the content of that file? -- kind regards, Carsten Hoeger Engineering Services Email: carsten.hoeger@open-xchange.com ------------------------------------------------------------------------------ Open-Xchange AG, Hohenzollernring 72, 50672 Cologne, District Court Cologne HRB 95366 Managing Board: Rafael Laguna de la Vera, Carsten Dirks, Michael Knapstein, Stephan Martin Chairman of the Board: Richard Seibt European Office: Open-Xchange GmbH, Olper Huette 5f, D-57462 Olpe, Germany, District Court Siegen, HRB 8718 Managing Director: Frank Hoberg US Office: Open-Xchange. Inc., 530 Lytton Avenue, Palo Alto, CA 94301, USA ------------------------------------------------------------------------------ -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Show replies by date

Michael Schroeder

24 Feb 24 Feb

12:17

On Mon, Feb 24, 2020 at 01:04:04PM +0100, Carsten Höger wrote:

...

I recently noticed that this file is quite huge in our installation:

2.8G /srv/obs/events/lastnotifications

Can this file be removed?

Nope.

...

It looks like a logfile to me with new entries added at the end. Is some component of OBS reading the content of that file?

It's a queue of notifications. The API is supposed to read it, read events are deleted and thus the file shrinks. A lastnotifications file that big is an indication that the delayed job for notification processing is not running in the API. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Carsten Höger

12:23

Hi Michael,

...

On 24. Feb 2020, at 13:17 , Michael Schroeder wrote:

On Mon, Feb 24, 2020 at 01:04:04PM +0100, Carsten Höger wrote:

...
I recently noticed that this file is quite huge in our installation:

2.8G /srv/obs/events/lastnotifications

Can this file be removed?

Nope.

...
It looks like a logfile to me with new entries added at the end. Is some component of OBS reading the content of that file?

It's a queue of notifications. The API is supposed to read it, read events are deleted and thus the file shrinks.

A lastnotifications file that big is an indication that the delayed job for notification processing is not running in the API.

How to verify that? Are you talking about this? Checking for service delayed OBS api jobs running ● obsapidelayed.service - LSB: OBS api delayed jobs Loaded: loaded (/etc/init.d/obsapidelayed; bad; vendor preset: disabled) Active: active (running) since Fri 2019-11-29 14:44:42 CET; 2 months 26 days ago Docs: man:systemd-sysv-generator(8) Tasks: 32 (limit: 512) CGroup: /system.slice/obsapidelayed.service ├─2072 delayed_job.0 ├─2078 delayed_job.1 ├─2084 delayed_job.2 ├─2247 delayed_job.1000 ├─2263 delayed_job.1010 ├─2276 delayed_job.1020 ├─2294 delayed_job.1030 ├─2319 delayed_job.1040 ├─2333 delayed_job.1050 ├─2594 /usr/bin/searchd --pidfile --config /srv/www/obs/api/config/production.sphinx.conf ├─2595 /usr/bin/searchd --pidfile --config /srv/www/obs/api/config/production.sphinx.conf └─2611 clockworkd.ruby2.5.clock -- kind regards, Carsten Hoeger Engineering Services Email: carsten.hoeger@open-xchange.com ------------------------------------------------------------------------------ Open-Xchange AG, Hohenzollernring 72, 50672 Cologne, District Court Cologne HRB 95366 Managing Board: Rafael Laguna de la Vera, Carsten Dirks, Michael Knapstein, Stephan Martin Chairman of the Board: Richard Seibt European Office: Open-Xchange GmbH, Olper Huette 5f, D-57462 Olpe, Germany, District Court Siegen, HRB 8718 Managing Director: Frank Hoberg US Office: Open-Xchange. Inc., 530 Lytton Avenue, Palo Alto, CA 94301, USA ------------------------------------------------------------------------------ -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Carsten Höger

12:39

Hi,

...

On 24. Feb 2020, at 13:23 , Carsten Höger wrote:

...
...
I recently noticed that this file is quite huge in our installation:

2.8G /srv/obs/events/lastnotifications

Can this file be removed?

Nope.

...
It looks like a logfile to me with new entries added at the end. Is some component of OBS reading the content of that file?

It's a queue of notifications. The API is supposed to read it, read events are deleted and thus the file shrinks.

A lastnotifications file that big is an indication that the delayed job for notification processing is not running in the API.

Btw.: Just checked on a fresh 2.10 testinstallation. Even though there's just two workers and almost nothing to build, those files are there and growing: buildservice:~ # ls -al /srv/obs/events/ total 392 drwxr-xr-x 8 obsrun obsrun 4096 Jan 30 14:07 . drwxr-xr-x 17 obsrun obsrun 4096 Jan 30 14:35 .. drwxr-xr-x 2 obsrun obsrun 4096 Jan 30 13:06 deltastore drwxr-xr-x 2 obsrun obsrun 4096 Feb 24 13:35 i586 -rw-r--r-- 1 obsrun obsrun 33236 Feb 24 13:35 lastevents -rw-r--r-- 1 obsrun obsrun 319815 Feb 24 13:35 lastnotifications drwxr-xr-x 2 obsrun obsrun 4096 Feb 8 17:38 publish drwxr-xr-x 2 obsrun obsrun 4096 Feb 24 09:55 repository drwxr-xr-x 2 obsrun obsrun 4096 Feb 8 17:37 signer drwxr-xr-x 2 obsrun obsrun 4096 Feb 24 13:35 x86_64 Nothing seems to consume anything within these files. -- kind regards, Carsten Hoeger Engineering Services Email: carsten.hoeger@open-xchange.com ------------------------------------------------------------------------------ Open-Xchange AG, Hohenzollernring 72, 50672 Cologne, District Court Cologne HRB 95366 Managing Board: Rafael Laguna de la Vera, Carsten Dirks, Michael Knapstein, Stephan Martin Chairman of the Board: Richard Seibt European Office: Open-Xchange GmbH, Olper Huette 5f, D-57462 Olpe, Germany, District Court Siegen, HRB 8718 Managing Director: Frank Hoberg US Office: Open-Xchange. Inc., 530 Lytton Avenue, Palo Alto, CA 94301, USA ------------------------------------------------------------------------------ -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Adrian Schröter

12:38

On Montag, 24. Februar 2020, 13:39:25 CET Carsten Höger wrote:

...

Hi,

...
On 24. Feb 2020, at 13:23 , Carsten Höger wrote:

...
...
I recently noticed that this file is quite huge in our installation:

2.8G /srv/obs/events/lastnotifications

Can this file be removed?

Nope.

...
It looks like a logfile to me with new entries added at the end. Is some component of OBS reading the content of that file?

It's a queue of notifications. The API is supposed to read it, read events are deleted and thus the file shrinks.

A lastnotifications file that big is an indication that the delayed job for notification processing is not running in the API.

Btw.: Just checked on a fresh 2.10 testinstallation. Even though there's just two workers and almost nothing to build, those files are there and growing:

buildservice:~ # ls -al /srv/obs/events/ total 392 drwxr-xr-x 8 obsrun obsrun 4096 Jan 30 14:07 . drwxr-xr-x 17 obsrun obsrun 4096 Jan 30 14:35 .. drwxr-xr-x 2 obsrun obsrun 4096 Jan 30 13:06 deltastore drwxr-xr-x 2 obsrun obsrun 4096 Feb 24 13:35 i586 -rw-r--r-- 1 obsrun obsrun 33236 Feb 24 13:35 lastevents -rw-r--r-- 1 obsrun obsrun 319815 Feb 24 13:35 lastnotifications drwxr-xr-x 2 obsrun obsrun 4096 Feb 8 17:38 publish drwxr-xr-x 2 obsrun obsrun 4096 Feb 24 09:55 repository drwxr-xr-x 2 obsrun obsrun 4096 Feb 8 17:37 signer drwxr-xr-x 2 obsrun obsrun 4096 Feb 24 13:35 x86_64

Nothing seems to consume anything within these files.

And you have checked that your delayed jobs are running? -- Adrian Schroeter Build Infrastructure Project Manager SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany (HRB 247165, AG München), Geschäftsführer: Felix Imendörffer -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Carsten Höger

12:47

Hi,

...

On 24. Feb 2020, at 13:38 , Adrian Schröter wrote:

...
...
...
...
It looks like a logfile to me with new entries added at the end. Is some component of OBS reading the content of that file?

It's a queue of notifications. The API is supposed to read it, read events are deleted and thus the file shrinks.

A lastnotifications file that big is an indication that the delayed job for notification processing is not running in the API.

Btw.: Just checked on a fresh 2.10 testinstallation. Even though there's just two workers and almost nothing to build, those files are there and growing:

buildservice:~ # ls -al /srv/obs/events/ total 392 drwxr-xr-x 8 obsrun obsrun 4096 Jan 30 14:07 . drwxr-xr-x 17 obsrun obsrun 4096 Jan 30 14:35 .. drwxr-xr-x 2 obsrun obsrun 4096 Jan 30 13:06 deltastore drwxr-xr-x 2 obsrun obsrun 4096 Feb 24 13:35 i586 -rw-r--r-- 1 obsrun obsrun 33236 Feb 24 13:35 lastevents -rw-r--r-- 1 obsrun obsrun 319815 Feb 24 13:35 lastnotifications drwxr-xr-x 2 obsrun obsrun 4096 Feb 8 17:38 publish drwxr-xr-x 2 obsrun obsrun 4096 Feb 24 09:55 repository drwxr-xr-x 2 obsrun obsrun 4096 Feb 8 17:37 signer drwxr-xr-x 2 obsrun obsrun 4096 Feb 24 13:35 x86_64

Nothing seems to consume anything within these files.

And you have checked that your delayed jobs are running?

Well, they are running on our 2.9 production instance (see my last mail), but not on the 2.10 test instance. On the 2.10 test instance, I am also unable to find a service/package which could provide it. buildservice:~ # systemctl status obsapidelayed Unit obsapidelayed.service could not be found. What's the package providing it on 2.10? -- kind regards, Carsten Hoeger Engineering Services Email: carsten.hoeger@open-xchange.com ------------------------------------------------------------------------------ Open-Xchange AG, Hohenzollernring 72, 50672 Cologne, District Court Cologne HRB 95366 Managing Board: Rafael Laguna de la Vera, Carsten Dirks, Michael Knapstein, Stephan Martin Chairman of the Board: Richard Seibt European Office: Open-Xchange GmbH, Olper Huette 5f, D-57462 Olpe, Germany, District Court Siegen, HRB 8718 Managing Director: Frank Hoberg US Office: Open-Xchange. Inc., 530 Lytton Avenue, Palo Alto, CA 94301, USA ------------------------------------------------------------------------------ -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Andreas Schwab

13:19

New subject: [opensuse-buildservice] Re: /srv/obs/events/lastnotifications

# systemctl list-unit-files | grep obs-delayedjob Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Carsten Höger

13:57

...

On 24. Feb 2020, at 14:19 , Andreas Schwab wrote:

# systemctl list-unit-files | grep obs-delayedjob

buildservice:~ # systemctl list-unit-files | grep obs-delayedjob obs-delayedjob-queue-consistency_check.service disabled obs-delayedjob-queue-default.service disabled obs-delayedjob-queue-issuetracking.service disabled obs-delayedjob-queue-mailers.service disabled obs-delayedjob-queue-project_log_rotate.service disabled obs-delayedjob-queue-quick@.service disabled obs-delayedjob-queue-releasetracking.service disabled obs-delayedjob-queue-staging.service disabled Which one do I need? -- kind regards, Carsten Hoeger Engineering Services Email: carsten.hoeger@open-xchange.com ------------------------------------------------------------------------------ Open-Xchange AG, Hohenzollernring 72, 50672 Cologne, District Court Cologne HRB 95366 Managing Board: Rafael Laguna de la Vera, Carsten Dirks, Michael Knapstein, Stephan Martin Chairman of the Board: Richard Seibt European Office: Open-Xchange GmbH, Olper Huette 5f, D-57462 Olpe, Germany, District Court Siegen, HRB 8718 Managing Director: Frank Hoberg US Office: Open-Xchange. Inc., 530 Lytton Avenue, Palo Alto, CA 94301, USA ------------------------------------------------------------------------------ -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Carsten Höger

25 Feb 25 Feb

08:29

New subject: [opensuse-buildservice] Problem with delayed job(s), WAS: /srv/obs/events/lastnotifications

Hi, any idea about the problem? Should I open an issue? Summary: The file /srv/obs/events/lastnotifications is growing without limit on OBS 2.9 and 2.10. On 2.9 the service obsdelayed is installed and running: Checking for service delayed OBS api jobs running ● obsapidelayed.service - LSB: OBS api delayed jobs Loaded: loaded (/etc/init.d/obsapidelayed; bad; vendor preset: disabled) Active: active (running) since Fri 2019-11-29 14:44:42 CET; 2 months 26 days ago Docs: man:systemd-sysv-generator(8) Tasks: 32 (limit: 512) CGroup: /system.slice/obsapidelayed.service ├─2072 delayed_job.0 ├─2078 delayed_job.1 ├─2084 delayed_job.2 ├─2247 delayed_job.1000 ├─2263 delayed_job.1010 ├─2276 delayed_job.1020 ├─2294 delayed_job.1030 ├─2319 delayed_job.1040 ├─2333 delayed_job.1050 ├─2594 /usr/bin/searchd --pidfile --config /srv/www/obs/api/config/production.sphinx.conf ├─2595 /usr/bin/searchd --pidfile --config /srv/www/obs/api/config/production.sphinx.conf └─2611 clockworkd.ruby2.5.clock On 2.10 there is no such service available, instead, there are the following services (no idea if one or more of those have the same purpose as that one available on 2.9 and earlier: buildservice:~ # systemctl list-unit-files | grep obs-delayedjob obs-delayedjob-queue-consistency_check.service disabled obs-delayedjob-queue-default.service disabled obs-delayedjob-queue-issuetracking.service disabled obs-delayedjob-queue-mailers.service disabled obs-delayedjob-queue-project_log_rotate.service disabled obs-delayedjob-queue-quick@.service disabled obs-delayedjob-queue-releasetracking.service disabled obs-delayedjob-queue-staging.service disabled

...

On 24. Feb 2020, at 14:57 , Carsten Höger wrote:

...
On 24. Feb 2020, at 14:19 , Andreas Schwab wrote:

# systemctl list-unit-files | grep obs-delayedjob

buildservice:~ # systemctl list-unit-files | grep obs-delayedjob obs-delayedjob-queue-consistency_check.service disabled obs-delayedjob-queue-default.service disabled obs-delayedjob-queue-issuetracking.service disabled obs-delayedjob-queue-mailers.service disabled obs-delayedjob-queue-project_log_rotate.service disabled obs-delayedjob-queue-quick@.service disabled obs-delayedjob-queue-releasetracking.service disabled obs-delayedjob-queue-staging.service disabled

Which one do I need?

--

kind regards, Carsten Hoeger Engineering Services

Email: carsten.hoeger@open-xchange.com

------------------------------------------------------------------------------ Open-Xchange AG, Hohenzollernring 72, 50672 Cologne, District Court Cologne HRB 95366 Managing Board: Rafael Laguna de la Vera, Carsten Dirks, Michael Knapstein, Stephan Martin Chairman of the Board: Richard Seibt

European Office: Open-Xchange GmbH, Olper Huette 5f, D-57462 Olpe, Germany, District Court Siegen, HRB 8718 Managing Director: Frank Hoberg

US Office: Open-Xchange. Inc., 530 Lytton Avenue, Palo Alto, CA 94301, USA ------------------------------------------------------------------------------

-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

-- kind regards, Carsten Hoeger Engineering Services Email: carsten.hoeger@open-xchange.com ------------------------------------------------------------------------------ Open-Xchange AG, Hohenzollernring 72, 50672 Cologne, District Court Cologne HRB 95366 Managing Board: Rafael Laguna de la Vera, Carsten Dirks, Michael Knapstein, Stephan Martin Chairman of the Board: Richard Seibt European Office: Open-Xchange GmbH, Olper Huette 5f, D-57462 Olpe, Germany, District Court Siegen, HRB 8718 Managing Director: Frank Hoberg US Office: Open-Xchange. Inc., 530 Lytton Avenue, Palo Alto, CA 94301, USA ------------------------------------------------------------------------------ -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Carsten Höger

27 Feb 27 Feb

15:04

Hi, to answer my own question:

...

On 24. Feb 2020, at 14:57 , Carsten Höger wrote:

...
On 24. Feb 2020, at 14:19 , Andreas Schwab wrote:

# systemctl list-unit-files | grep obs-delayedjob

buildservice:~ # systemctl list-unit-files | grep obs-delayedjob obs-delayedjob-queue-consistency_check.service disabled obs-delayedjob-queue-default.service disabled obs-delayedjob-queue-issuetracking.service disabled obs-delayedjob-queue-mailers.service disabled obs-delayedjob-queue-project_log_rotate.service disabled obs-delayedjob-queue-quick@.service disabled obs-delayedjob-queue-releasetracking.service disabled obs-delayedjob-queue-staging.service disabled

Which one do I need?

What's needed is grouped behind the obs-api-support.target, overlooked that in README.UPDATERS -- kind regards, Carsten Hoeger Engineering Services Email: carsten.hoeger@open-xchange.com ------------------------------------------------------------------------------ Open-Xchange AG, Hohenzollernring 72, 50672 Cologne, District Court Cologne HRB 95366 Managing Board: Rafael Laguna de la Vera, Carsten Dirks, Michael Knapstein, Stephan Martin Chairman of the Board: Richard Seibt European Office: Open-Xchange GmbH, Olper Huette 5f, D-57462 Olpe, Germany, District Court Siegen, HRB 8718 Managing Director: Frank Hoberg US Office: Open-Xchange. Inc., 530 Lytton Avenue, Palo Alto, CA 94301, USA ------------------------------------------------------------------------------ -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Stefan Seyfried

25 Feb 25 Feb

08:36

Am 24.02.20 um 13:17 schrieb Michael Schroeder:

...

On Mon, Feb 24, 2020 at 01:04:04PM +0100, Carsten Höger wrote:

...
I recently noticed that this file is quite huge in our installation:

2.8G /srv/obs/events/lastnotifications

Can this file be removed?

Nope.

...
It looks like a logfile to me with new entries added at the end. Is some component of OBS reading the content of that file?

It's a queue of notifications. The API is supposed to read it, read events are deleted and thus the file shrinks.> A lastnotifications file that big is an indication that the delayed job for notification processing is not running in the API.

It is also possible that there is an "invalid" entry in the lastevents file (UTF-8 anyone?) and the backend chokes on that line every time. I had this some (12-36?) months ago, not sure if I reported it here. Cleaning up this one line then made the lastevents processor continue. You should find cryptic messages in the logs when this happens. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Stefan Seyfried

08:40

Am 24.02.20 um 13:17 schrieb Michael Schroeder:

...

On Mon, Feb 24, 2020 at 01:04:04PM +0100, Carsten Höger wrote:

...
I recently noticed that this file is quite huge in our installation:

2.8G /srv/obs/events/lastnotifications

Can this file be removed?

Nope.

...
It looks like a logfile to me with new entries added at the end. Is some component of OBS reading the content of that file?

It's a queue of notifications. The API is supposed to read it, read events are deleted and thus the file shrinks.

A lastnotifications file that big is an indication that the delayed job for notification processing is not running in the API.

https://lists.opensuse.org/opensuse-buildservice/2018-06/msg00029.html https://lists.opensuse.org/opensuse-buildservice/2018-06/msg00030.html This had happened to me, removing the offending line fixed it. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Carsten Höger

12:58

Hi,

...

On 25. Feb 2020, at 9:40 , Stefan Seyfried wrote:

...
...
I recently noticed that this file is quite huge in our installation:

2.8G /srv/obs/events/lastnotifications

Can this file be removed?

Nope.

...
It looks like a logfile to me with new entries added at the end. Is some component of OBS reading the content of that file?

It's a queue of notifications. The API is supposed to read it, read events are deleted and thus the file shrinks.

A lastnotifications file that big is an indication that the delayed job for notification processing is not running in the API.

https://lists.opensuse.org/opensuse-buildservice/2018-06/msg00029.html https://lists.opensuse.org/opensuse-buildservice/2018-06/msg00030.html

This had happened to me, removing the offending line fixed it.

Looks like my case is slightly different. I see this src_server.log-20200225.xz:2020-02-24 21:20:54: [5776] GET (127.0.0.1) /lastnotifications?block=1&start=15663719 src_server.log-20200225.xz:2020-02-24 21:20:54: [1970] GET (AJAX) /lastnotifications?start=15663719&block=1 approx every 15 minutes in the logs, but there's no 15663719 in my lastnotifications file. I also wonder what's broken now since the system appears to be working fine. -- kind regards, Carsten Hoeger Engineering Services Email: carsten.hoeger@open-xchange.com ------------------------------------------------------------------------------ Open-Xchange AG, Hohenzollernring 72, 50672 Cologne, District Court Cologne HRB 95366 Managing Board: Rafael Laguna de la Vera, Carsten Dirks, Michael Knapstein, Stephan Martin Chairman of the Board: Richard Seibt European Office: Open-Xchange GmbH, Olper Huette 5f, D-57462 Olpe, Germany, District Court Siegen, HRB 8718 Managing Director: Frank Hoberg US Office: Open-Xchange. Inc., 530 Lytton Avenue, Palo Alto, CA 94301, USA ------------------------------------------------------------------------------ -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Stephan Kulow

26 Feb 26 Feb

07:15

Am 25.02.20 um 13:58 schrieb Carsten Höger:

...

Hi,

...
On 25. Feb 2020, at 9:40 , Stefan Seyfried wrote:

...
...
I recently noticed that this file is quite huge in our installation:

2.8G /srv/obs/events/lastnotifications

Can this file be removed?

Nope.

...
It looks like a logfile to me with new entries added at the end. Is some component of OBS reading the content of that file?

It's a queue of notifications. The API is supposed to read it, read events are deleted and thus the file shrinks.

A lastnotifications file that big is an indication that the delayed job for notification processing is not running in the API.

https://lists.opensuse.org/opensuse-buildservice/2018-06/msg00029.html https://lists.opensuse.org/opensuse-buildservice/2018-06/msg00030.html

This had happened to me, removing the offending line fixed it.

Looks like my case is slightly different. I see this

src_server.log-20200225.xz:2020-02-24 21:20:54: [5776] GET (127.0.0.1) /lastnotifications?block=1&start=15663719 src_server.log-20200225.xz:2020-02-24 21:20:54: [1970] GET (AJAX) /lastnotifications?start=15663719&block=1

approx every 15 minutes in the logs, but there's no 15663719 in my lastnotifications file.

I also wonder what's broken now since the system appears to be working fine.

Well, it's missing notifications - but you will only notice if you cared for e.g. 'build failed' emails. What I'd do: `RAILS_ENV=production rails c` on api and `puts Delayed::Job.first.last_error` it will be a string containing a backtrace hopefully hinting at the problem. Greetings, Stephan -- Lighten up, just enjoy life, smile more, laugh more, and don't get so worked up about things. Kenneth Branagh -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Carsten Höger

07:49

Hi Stephan,

...

On 26. Feb 2020, at 8:15 , Stephan Kulow wrote:

...
I see this

src_server.log-20200225.xz:2020-02-24 21:20:54: [5776] GET (127.0.0.1) /lastnotifications?block=1&start=15663719 src_server.log-20200225.xz:2020-02-24 21:20:54: [1970] GET (AJAX) /lastnotifications?start=15663719&block=1

approx every 15 minutes in the logs, but there's no 15663719 in my lastnotifications file.

I also wonder what's broken now since the system appears to be working fine.

Well, it's missing notifications - but you will only notice if you cared for e.g. 'build failed' emails.

Our buildservice does not send emails at all. And we would not need that, so I am fine with that.

...

What I'd do: `RAILS_ENV=production rails c` on api and `puts Delayed::Job.first.last_error` it will be a string containing a backtrace hopefully hinting at the problem.

Indeed. Looks like that project is broken. I assume that's related to one of my attempts to remove dead sources. Can this somehow be reseted? If we don't need notifications anywhere, can I remove that file (lastnotifications)? <status code="400"> <summary>Debian:Squeeze/_project/136601816b500ca23c714c7eac6b51c6: not in repository. Either not existing or misconfigured server setting for '$nosharedtrees' setting in BSConfig.pm</summary> </status> /srv/www/obs/api/lib/backend/connection.rb:126:in `handle_response' /srv/www/obs/api/lib/backend/connection.rb:31:in `get' /srv/www/obs/api/lib/backend/connection_helper.rb:48:in `http_get' /srv/www/obs/api/lib/backend/api/sources/project.rb:36:in `meta' /srv/www/obs/api/app/jobs/consistency_check_job.rb:86:in `project_meta_check' /srv/www/obs/api/app/jobs/consistency_check_job.rb:21:in `block in perform' /usr/lib64/ruby/gems/2.5.0/gems/activerecord-5.1.4/lib/active_record/relation/batches.rb:63:in `block (2 levels) in find_each' /usr/lib64/ruby/gems/2.5.0/gems/activerecord-5.1.4/lib/active_record/relation/batches.rb:63:in `each' /usr/lib64/ruby/gems/2.5.0/gems/activerecord-5.1.4/lib/active_record/relation/batches.rb:63:in `block in find_each' /usr/lib64/ruby/gems/2.5.0/gems/activerecord-5.1.4/lib/active_record/relation/batches.rb:129:in `block in find_in_batches' /usr/lib64/ruby/gems/2.5.0/gems/activerecord-5.1.4/lib/active_record/relation/batches.rb:230:in `block in in_batches' /usr/lib64/ruby/gems/2.5.0/gems/activerecord-5.1.4/lib/active_record/relation/batches.rb:214:in `loop' /usr/lib64/ruby/gems/2.5.0/gems/activerecord-5.1.4/lib/active_record/relation/batches.rb:214:in `in_batches' /usr/lib64/ruby/gems/2.5.0/gems/activerecord-5.1.4/lib/active_record/relation/batches.rb:128:in `find_in_batches' /usr/lib64/ruby/gems/2.5.0/gems/activerecord-5.1.4/lib/active_record/relation/batches.rb:62:in `find_each' /usr/lib64/ruby/gems/2.5.0/gems/activerecord-5.1.4/lib/active_record/querying.rb:9:in `find_each' /srv/www/obs/api/app/jobs/consistency_check_job.rb:10:in `perform' /usr/lib64/ruby/gems/2.5.0/gems/activejob-5.1.4/lib/active_job/execution.rb:37:in `block in perform_now' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:108:in `block in run_callbacks' /usr/lib64/ruby/gems/2.5.0/gems/i18n-0.9.1/lib/i18n.rb:265:in `with_locale' /usr/lib64/ruby/gems/2.5.0/gems/activejob-5.1.4/lib/active_job/translation.rb:7:in `block (2 levels) in module:Translation' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:117:in `instance_exec' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:117:in `block in run_callbacks' /usr/lib64/ruby/gems/2.5.0/gems/activejob-5.1.4/lib/active_job/logging.rb:24:in `block (4 levels) in module:Logging' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/notifications.rb:166:in `block in instrument' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/notifications/instrumenter.rb:21:in `instrument' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/notifications.rb:166:in `instrument' /usr/lib64/ruby/gems/2.5.0/gems/activejob-5.1.4/lib/active_job/logging.rb:23:in `block (3 levels) in module:Logging' /usr/lib64/ruby/gems/2.5.0/gems/activejob-5.1.4/lib/active_job/logging.rb:44:in `block in tag_logger' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/tagged_logging.rb:69:in `block in tagged' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/tagged_logging.rb:26:in `tagged' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/tagged_logging.rb:69:in `tagged' /usr/lib64/ruby/gems/2.5.0/gems/activejob-5.1.4/lib/active_job/logging.rb:44:in `tag_logger' /usr/lib64/ruby/gems/2.5.0/gems/activejob-5.1.4/lib/active_job/logging.rb:20:in `block (2 levels) in module:Logging' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:117:in `instance_exec' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:117:in `block in run_callbacks' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:135:in `run_callbacks' /usr/lib64/ruby/gems/2.5.0/gems/activejob-5.1.4/lib/active_job/execution.rb:33:in `perform_now' /usr/lib64/ruby/gems/2.5.0/gems/activejob-5.1.4/lib/active_job/execution.rb:22:in `block in execute' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:108:in `block in run_callbacks' /usr/lib64/ruby/gems/2.5.0/gems/activejob-5.1.4/lib/active_job/railtie.rb:26:in `block (4 levels) in class:Railtie' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/execution_wrapper.rb:85:in `wrap' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/reloader.rb:68:in `block in wrap' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/execution_wrapper.rb:85:in `wrap' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/reloader.rb:67:in `wrap' /usr/lib64/ruby/gems/2.5.0/gems/activejob-5.1.4/lib/active_job/railtie.rb:25:in `block (3 levels) in class:Railtie' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:117:in `instance_exec' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:117:in `block in run_callbacks' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:135:in `run_callbacks' /usr/lib64/ruby/gems/2.5.0/gems/activejob-5.1.4/lib/active_job/execution.rb:20:in `execute' /usr/lib64/ruby/gems/2.5.0/gems/activejob-5.1.4/lib/active_job/queue_adapters/delayed_job_adapter.rb:36:in `perform' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/backend/base.rb:81:in `block in invoke_job' /usr/lib64/ruby/gems/2.5.0/gems/airbrake-7.1.0/lib/airbrake/delayed_job.rb:11:in `block (2 levels) in class:Airbrake' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/lifecycle.rb:79:in `block (2 levels) in add' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/lifecycle.rb:61:in `block in initialize' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/lifecycle.rb:79:in `block in add' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/lifecycle.rb:66:in `execute' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/lifecycle.rb:40:in `run_callbacks' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/backend/base.rb:78:in `invoke_job' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/worker.rb:230:in `block (2 levels) in run' /usr/lib64/ruby/2.5.0/timeout.rb:93:in `block in timeout' /usr/lib64/ruby/2.5.0/timeout.rb:103:in `timeout' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/worker.rb:230:in `block in run' /usr/lib64/ruby/2.5.0/benchmark.rb:308:in `realtime' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/worker.rb:229:in `run' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/worker.rb:312:in `block in reserve_and_run_one_job' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/lifecycle.rb:61:in `block in initialize' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/lifecycle.rb:66:in `execute' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/lifecycle.rb:40:in `run_callbacks' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/worker.rb:312:in `reserve_and_run_one_job' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/worker.rb:213:in `block in work_off' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/worker.rb:212:in `times' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/worker.rb:212:in `work_off' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/worker.rb:175:in `block (4 levels) in start' /usr/lib64/ruby/2.5.0/benchmark.rb:308:in `realtime' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/worker.rb:174:in `block (3 levels) in start' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/lifecycle.rb:61:in `block in initialize' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/lifecycle.rb:66:in `execute' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/lifecycle.rb:40:in `run_callbacks' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/worker.rb:173:in `block (2 levels) in start' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/worker.rb:172:in `loop' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/worker.rb:172:in `block in start' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/plugins/clear_locks.rb:7:in `block (2 levels) in class:ClearLocks' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/lifecycle.rb:79:in `block (2 levels) in add' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/lifecycle.rb:61:in `block in initialize' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/lifecycle.rb:79:in `block in add' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/lifecycle.rb:66:in `execute' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/lifecycle.rb:40:in `run_callbacks' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/worker.rb:171:in `start' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/command.rb:137:in `run' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/command.rb:125:in `block in run_process' /usr/lib64/ruby/gems/2.5.0/gems/daemons-1.2.6/lib/daemons/application.rb:270:in `block in start_proc' /usr/lib64/ruby/gems/2.5.0/gems/daemons-1.2.6/lib/daemons/daemonize.rb:84:in `call_as_daemon' /usr/lib64/ruby/gems/2.5.0/gems/daemons-1.2.6/lib/daemons/application.rb:274:in `start_proc' /usr/lib64/ruby/gems/2.5.0/gems/daemons-1.2.6/lib/daemons/application.rb:300:in `start' /usr/lib64/ruby/gems/2.5.0/gems/daemons-1.2.6/lib/daemons/controller.rb:56:in `run' /usr/lib64/ruby/gems/2.5.0/gems/daemons-1.2.6/lib/daemons.rb:197:in `block in run_proc' /usr/lib64/ruby/gems/2.5.0/gems/daemons-1.2.6/lib/daemons/cmdline.rb:92:in `catch_exceptions' /usr/lib64/ruby/gems/2.5.0/gems/daemons-1.2.6/lib/daemons.rb:196:in `run_proc' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/command.rb:123:in `run_process' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/command.rb:98:in `daemonize' script/delayed_job.api.rb:5:in `<main>' => nil -- kind regards, Carsten Hoeger Engineering Services Email: carsten.hoeger@open-xchange.com ------------------------------------------------------------------------------ Open-Xchange AG, Hohenzollernring 72, 50672 Cologne, District Court Cologne HRB 95366 Managing Board: Rafael Laguna de la Vera, Carsten Dirks, Michael Knapstein, Stephan Martin Chairman of the Board: Richard Seibt European Office: Open-Xchange GmbH, Olper Huette 5f, D-57462 Olpe, Germany, District Court Siegen, HRB 8718 Managing Director: Frank Hoberg US Office: Open-Xchange. Inc., 530 Lytton Avenue, Palo Alto, CA 94301, USA ------------------------------------------------------------------------------ -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Carsten Höger

2 Mar 2 Mar

07:10

Hi, I removed the file /srv/obs/events/lastnotifications, but it is growing again. Reason seems to be the error below. Is it somehow possible to resolve that problem? Or can I disable that notification system since it doesn't seem to be needed for us?

...

...
What I'd do: `RAILS_ENV=production rails c` on api and `puts Delayed::Job.first.last_error` it will be a string containing a backtrace hopefully hinting at the problem.

Indeed. Looks like that project is broken. I assume that's related to one of my attempts to remove dead sources. Can this somehow be reseted? If we don't need notifications anywhere, can I remove that file (lastnotifications)?

<status code="400"> <summary>Debian:Squeeze/_project/136601816b500ca23c714c7eac6b51c6: not in repository. Either not existing or misconfigured server setting for '$nosharedtrees' setting in BSConfig.pm</summary> </status>

/srv/www/obs/api/lib/backend/connection.rb:126:in `handle_response' /srv/www/obs/api/lib/backend/connection.rb:31:in `get' /srv/www/obs/api/lib/backend/connection_helper.rb:48:in `http_get' /srv/www/obs/api/lib/backend/api/sources/project.rb:36:in `meta' /srv/www/obs/api/app/jobs/consistency_check_job.rb:86:in `project_meta_check' /srv/www/obs/api/app/jobs/consistency_check_job.rb:21:in `block in perform' /usr/lib64/ruby/gems/2.5.0/gems/activerecord-5.1.4/lib/active_record/relation/batches.rb:63:in `block (2 levels) in find_each' /usr/lib64/ruby/gems/2.5.0/gems/activerecord-5.1.4/lib/active_record/relation/batches.rb:63:in `each' /usr/lib64/ruby/gems/2.5.0/gems/activerecord-5.1.4/lib/active_record/relation/batches.rb:63:in `block in find_each' /usr/lib64/ruby/gems/2.5.0/gems/activerecord-5.1.4/lib/active_record/relation/batches.rb:129:in `block in find_in_batches' /usr/lib64/ruby/gems/2.5.0/gems/activerecord-5.1.4/lib/active_record/relation/batches.rb:230:in `block in in_batches' /usr/lib64/ruby/gems/2.5.0/gems/activerecord-5.1.4/lib/active_record/relation/batches.rb:214:in `loop' /usr/lib64/ruby/gems/2.5.0/gems/activerecord-5.1.4/lib/active_record/relation/batches.rb:214:in `in_batches' /usr/lib64/ruby/gems/2.5.0/gems/activerecord-5.1.4/lib/active_record/relation/batches.rb:128:in `find_in_batches' /usr/lib64/ruby/gems/2.5.0/gems/activerecord-5.1.4/lib/active_record/relation/batches.rb:62:in `find_each' /usr/lib64/ruby/gems/2.5.0/gems/activerecord-5.1.4/lib/active_record/querying.rb:9:in `find_each' /srv/www/obs/api/app/jobs/consistency_check_job.rb:10:in `perform' /usr/lib64/ruby/gems/2.5.0/gems/activejob-5.1.4/lib/active_job/execution.rb:37:in `block in perform_now' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:108:in `block in run_callbacks' /usr/lib64/ruby/gems/2.5.0/gems/i18n-0.9.1/lib/i18n.rb:265:in `with_locale' /usr/lib64/ruby/gems/2.5.0/gems/activejob-5.1.4/lib/active_job/translation.rb:7:in `block (2 levels) in module:Translation' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:117:in `instance_exec' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:117:in `block in run_callbacks' /usr/lib64/ruby/gems/2.5.0/gems/activejob-5.1.4/lib/active_job/logging.rb:24:in `block (4 levels) in module:Logging' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/notifications.rb:166:in `block in instrument' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/notifications/instrumenter.rb:21:in `instrument' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/notifications.rb:166:in `instrument' /usr/lib64/ruby/gems/2.5.0/gems/activejob-5.1.4/lib/active_job/logging.rb:23:in `block (3 levels) in module:Logging' /usr/lib64/ruby/gems/2.5.0/gems/activejob-5.1.4/lib/active_job/logging.rb:44:in `block in tag_logger' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/tagged_logging.rb:69:in `block in tagged' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/tagged_logging.rb:26:in `tagged' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/tagged_logging.rb:69:in `tagged' /usr/lib64/ruby/gems/2.5.0/gems/activejob-5.1.4/lib/active_job/logging.rb:44:in `tag_logger' /usr/lib64/ruby/gems/2.5.0/gems/activejob-5.1.4/lib/active_job/logging.rb:20:in `block (2 levels) in module:Logging' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:117:in `instance_exec' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:117:in `block in run_callbacks' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:135:in `run_callbacks' /usr/lib64/ruby/gems/2.5.0/gems/activejob-5.1.4/lib/active_job/execution.rb:33:in `perform_now' /usr/lib64/ruby/gems/2.5.0/gems/activejob-5.1.4/lib/active_job/execution.rb:22:in `block in execute' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:108:in `block in run_callbacks' /usr/lib64/ruby/gems/2.5.0/gems/activejob-5.1.4/lib/active_job/railtie.rb:26:in `block (4 levels) in class:Railtie' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/execution_wrapper.rb:85:in `wrap' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/reloader.rb:68:in `block in wrap' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/execution_wrapper.rb:85:in `wrap' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/reloader.rb:67:in `wrap' /usr/lib64/ruby/gems/2.5.0/gems/activejob-5.1.4/lib/active_job/railtie.rb:25:in `block (3 levels) in class:Railtie' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:117:in `instance_exec' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:117:in `block in run_callbacks' /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:135:in `run_callbacks' /usr/lib64/ruby/gems/2.5.0/gems/activejob-5.1.4/lib/active_job/execution.rb:20:in `execute' /usr/lib64/ruby/gems/2.5.0/gems/activejob-5.1.4/lib/active_job/queue_adapters/delayed_job_adapter.rb:36:in `perform' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/backend/base.rb:81:in `block in invoke_job' /usr/lib64/ruby/gems/2.5.0/gems/airbrake-7.1.0/lib/airbrake/delayed_job.rb:11:in `block (2 levels) in class:Airbrake' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/lifecycle.rb:79:in `block (2 levels) in add' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/lifecycle.rb:61:in `block in initialize' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/lifecycle.rb:79:in `block in add' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/lifecycle.rb:66:in `execute' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/lifecycle.rb:40:in `run_callbacks' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/backend/base.rb:78:in `invoke_job' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/worker.rb:230:in `block (2 levels) in run' /usr/lib64/ruby/2.5.0/timeout.rb:93:in `block in timeout' /usr/lib64/ruby/2.5.0/timeout.rb:103:in `timeout' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/worker.rb:230:in `block in run' /usr/lib64/ruby/2.5.0/benchmark.rb:308:in `realtime' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/worker.rb:229:in `run' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/worker.rb:312:in `block in reserve_and_run_one_job' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/lifecycle.rb:61:in `block in initialize' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/lifecycle.rb:66:in `execute' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/lifecycle.rb:40:in `run_callbacks' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/worker.rb:312:in `reserve_and_run_one_job' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/worker.rb:213:in `block in work_off' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/worker.rb:212:in `times' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/worker.rb:212:in `work_off' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/worker.rb:175:in `block (4 levels) in start' /usr/lib64/ruby/2.5.0/benchmark.rb:308:in `realtime' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/worker.rb:174:in `block (3 levels) in start' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/lifecycle.rb:61:in `block in initialize' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/lifecycle.rb:66:in `execute' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/lifecycle.rb:40:in `run_callbacks' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/worker.rb:173:in `block (2 levels) in start' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/worker.rb:172:in `loop' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/worker.rb:172:in `block in start' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/plugins/clear_locks.rb:7:in `block (2 levels) in class:ClearLocks' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/lifecycle.rb:79:in `block (2 levels) in add' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/lifecycle.rb:61:in `block in initialize' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/lifecycle.rb:79:in `block in add' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/lifecycle.rb:66:in `execute' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/lifecycle.rb:40:in `run_callbacks' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/worker.rb:171:in `start' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/command.rb:137:in `run' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/command.rb:125:in `block in run_process' /usr/lib64/ruby/gems/2.5.0/gems/daemons-1.2.6/lib/daemons/application.rb:270:in `block in start_proc' /usr/lib64/ruby/gems/2.5.0/gems/daemons-1.2.6/lib/daemons/daemonize.rb:84:in `call_as_daemon' /usr/lib64/ruby/gems/2.5.0/gems/daemons-1.2.6/lib/daemons/application.rb:274:in `start_proc' /usr/lib64/ruby/gems/2.5.0/gems/daemons-1.2.6/lib/daemons/application.rb:300:in `start' /usr/lib64/ruby/gems/2.5.0/gems/daemons-1.2.6/lib/daemons/controller.rb:56:in `run' /usr/lib64/ruby/gems/2.5.0/gems/daemons-1.2.6/lib/daemons.rb:197:in `block in run_proc' /usr/lib64/ruby/gems/2.5.0/gems/daemons-1.2.6/lib/daemons/cmdline.rb:92:in `catch_exceptions' /usr/lib64/ruby/gems/2.5.0/gems/daemons-1.2.6/lib/daemons.rb:196:in `run_proc' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/command.rb:123:in `run_process' /usr/lib64/ruby/gems/2.5.0/gems/delayed_job-4.1.4/lib/delayed/command.rb:98:in `daemonize' script/delayed_job.api.rb:5:in `<main>' => nil

1524

Age (days ago)

1531

Last active (days ago)

List overview

Download

15 comments

6 participants

participants (6)

Adrian Schröter
Andreas Schwab
Carsten Höger
Michael Schroeder
Stefan Seyfried
Stephan Kulow

[opensuse-buildservice] /srv/obs/events/lastnotifications

tags

participants (6)