Re: [Spacewalk-list] Antwort: Re: Errata Cache bunch running forever on Spacewalk 2.4

[Robert Paschedag]

Hello Jan,

I don't see anything useful, if debug logging is disabled in taskomatic.

Also when debugging is disabled, the only thing I see, is, that some 
errata-cache tasks are "SKIPPED". I also enabled all logging of SQL statements 
in postgres but - IMHO - everything looks " good".

I already started the whole server, restarted taskomatic, restarted 
spacewalk-service. Nothing seems to help.
I'm not sure, if sometimes the threads are colliding, so I wanted to set the 
number of workers to 1 for some time.

On my test system, everything looks good. But there are only about 10 systems 
registered, so I can't tell, if this "might" be some kind of performance 
problem.

Regards
Robert
Am 14.01.2016 3:52 nachm. schrieb Jan Dobes :
>
> On 12.1.2016 09:08 paschedag.netlut...@swr.de wrote: 
> > Hello again, 
> > 
> > still having problems, 
> > 
> > I noticed that the errata-cache gets triggerd when a client refreshes 
> > its repos or searches for updates. So I manually fired a "zypper ref -s" 
> > or a "apt-get update" on every client connected to this spacewalk 
> > server. This seems to have fixed "something". Suddenly, the 
> > "errata-cache" task has finished and I got some backtraces from spacewalk. 
> > 
> > But I still have trouble. The UI does not seem to get updated correctly 
> > (on the "system" page, nearly all systems look "up-to-date". But I know, 
> > it's not!). But the updates are available to the clients (searching on 
> > the client). 
> > 
> > When I look into the last errata-cache schedules (in Spacewalk "Admin" 
> > -> "Task schedules" -> "errata-cache-bunch") I can see, that the 
> > "errata-cache" tasks is often "SKIPPED" 
> > 
> > errata-cache _2016-01-12 08:50:00 MEZ _ 
> >  
> > 2016-01-12 08:50:00 MEZ SKIPPED 
> > errata-cache _2016-01-12 08:49:00 MEZ _ 
> >  
> > 2016-01-12 08:49:00 MEZ SKIPPED 
> > errata-cache _2016-01-12 08:48:00 MEZ _ 
> >  
> > 2016-01-12 08:48:00 MEZ SKIPPED 
> > errata-cache _2016-01-12 08:47:00 MEZ _ 
> >  
> > 2016-01-12 08:50:00 MEZ FINISHED 
> > errata-cache _2016-01-12 08:46:00 MEZ _ 
> >  
> > 2016-01-12 08:46:00 MEZ SKIPPED 
> > errata-cache _2016-01-12 08:45:00 MEZ _ 
> >  
> > 2016-01-12 08:45:00 MEZ SKIPPED 
> > errata-cache _2016-01-12 08:44:00 MEZ _ 
> >  
> > 2016-01-12 08:46:00 MEZ FINISHED 
> > errata-mailer _2016-01-12 08:43:00 MEZ _ 
> >  
> > 2016-01-12 08:43:00 MEZ FINISHED 
> > errata-cache _2016-01-12 08:43:00 MEZ _ 
> >  
> > 2016-01-12 08:43:00 MEZ FINISHED 
> > errata-cache _2016-01-12 08:42:00 MEZ _ 
> >  
> > 2016-01-12 08:42:00 MEZ SKIPPED 
> > errata-cache _2016-01-12 08:41:00 MEZ _ 
> >  
> > 2016-01-12 08:41:00 MEZ SKIPPED 
> > errata-cache _2016-01-12 08:40:00 MEZ _ 
> >  
> > 2016-01-12 08:40:00 MEZ SKIPPED 
> > errata-cache _2016-01-12 08:39:00 MEZ _ 
> >  
> > 2016-01-12 08:42:00 MEZ FINISHED 
> > errata-mailer _2016-01-12 08:38:00 MEZ _ 
> >  
> > 2016-01-12 08:38:00 MEZ FINISHED 
> > errata-cache _2016-01-12 08:38:00 MEZ _ 
> >  
> > 2016-01-12 08:38:00 MEZ FINISHED 
> > errata-mailer _2016-01-12 08:37:00 MEZ _ 
> >  
> > 2016-01-12 08:37:00 MEZ FINISHED 
> > errata-cache _2016-01-12 08:37:00 MEZ _ 
> >  
> > 2016-01-12 08:37:00 MEZ FINISHED 
> > errata-cache _2016-01-12 08:36:00 MEZ _ 
> >  
> > 2016-01-12 08:36:00 MEZ SKIPPED 
> > errata-cache _2016-01-12 08:35:00 MEZ _ 
> >  
> > 2016-01-12 08:35:00 MEZ SKIPPED 
> > errata-cache _2016-01-12 08:34:00 MEZ _ 
> >  
> > 2016-01-12 08:36:00 MEZ FINISHED 
> > errata-mailer _2016-01-12 08:33:00 MEZ _ 
> >  
> > 2016-01-12 08:33:00 MEZ FINISHED 
> > errata-cache _2016-01-12 08:33:00 MEZ _ 
> > 

Re: [Spacewalk-list] Antwort: Re: Errata Cache bunch running forever on Spacewalk 2.4

[Jan Dobes]

On 12.1.2016 09:08 paschedag.netlut...@swr.de wrote:

Hello again,

still having problems,

I noticed that the errata-cache gets triggerd when a client refreshes
its repos or searches for updates. So I manually fired a "zypper ref -s"
or a "apt-get update" on every client connected to this spacewalk
server. This seems to have fixed "something". Suddenly, the
"errata-cache" task has finished and I got some backtraces from spacewalk.

But I still have trouble. The UI does not seem to get updated correctly
(on the "system" page, nearly all systems look "up-to-date". But I know,
it's not!). But the updates are available to the clients (searching on
the client).

When I look into the last errata-cache schedules (in Spacewalk "Admin"
-> "Task schedules" -> "errata-cache-bunch") I can see, that the
"errata-cache" tasks is often "SKIPPED"

errata-cache_2016-01-12 08:50:00 MEZ _

2016-01-12 08:50:00 MEZ SKIPPED
errata-cache_2016-01-12 08:49:00 MEZ _

2016-01-12 08:49:00 MEZ SKIPPED
errata-cache_2016-01-12 08:48:00 MEZ _

2016-01-12 08:48:00 MEZ SKIPPED
errata-cache_2016-01-12 08:47:00 MEZ _

2016-01-12 08:50:00 MEZ FINISHED
errata-cache_2016-01-12 08:46:00 MEZ _

2016-01-12 08:46:00 MEZ SKIPPED
errata-cache_2016-01-12 08:45:00 MEZ _

2016-01-12 08:45:00 MEZ SKIPPED
errata-cache_2016-01-12 08:44:00 MEZ _

2016-01-12 08:46:00 MEZ FINISHED
errata-mailer   _2016-01-12 08:43:00 MEZ _

2016-01-12 08:43:00 MEZ FINISHED
errata-cache_2016-01-12 08:43:00 MEZ _

2016-01-12 08:43:00 MEZ FINISHED
errata-cache_2016-01-12 08:42:00 MEZ _

2016-01-12 08:42:00 MEZ SKIPPED
errata-cache_2016-01-12 08:41:00 MEZ _

2016-01-12 08:41:00 MEZ SKIPPED
errata-cache_2016-01-12 08:40:00 MEZ _

2016-01-12 08:40:00 MEZ SKIPPED
errata-cache_2016-01-12 08:39:00 MEZ _

2016-01-12 08:42:00 MEZ FINISHED
errata-mailer   _2016-01-12 08:38:00 MEZ _

2016-01-12 08:38:00 MEZ FINISHED
errata-cache_2016-01-12 08:38:00 MEZ _

2016-01-12 08:38:00 MEZ FINISHED
errata-mailer   _2016-01-12 08:37:00 MEZ _

2016-01-12 08:37:00 MEZ FINISHED
errata-cache_2016-01-12 08:37:00 MEZ _

2016-01-12 08:37:00 MEZ FINISHED
errata-cache_2016-01-12 08:36:00 MEZ _

2016-01-12 08:36:00 MEZ SKIPPED
errata-cache_2016-01-12 08:35:00 MEZ _

2016-01-12 08:35:00 MEZ SKIPPED
errata-cache_2016-01-12 08:34:00 MEZ _

2016-01-12 08:36:00 MEZ FINISHED
errata-mailer   _2016-01-12 08:33:00 MEZ _

2016-01-12 08:33:00 MEZ FINISHED
errata-cache_2016-01-12 08:33:00 MEZ _

2016-01-12 08:33:00 MEZ FINISHED
errata-mailer   _2016-01-12 08:32:00 MEZ _

2016-01-12 08:32:00 MEZ FINISHED
errata-cache_2016-01-12 08:32:00 MEZ _

2016-01-12 08:32:00 MEZ FINISHED
errata-mailer   _2016-01-12 08:31:00 MEZ _

2016-01-12 08:31:00 MEZ FINISHED
errata-cache_2016-01-12 08:31:00 MEZ _

2016-01-12 08:31:00 MEZ FINISHED
errata-mailer   _2016-01-12 08:30:00 MEZ _

2016-01-12 08:30:00 MEZ FINISHED
errata-cache_2016-01-12 08:30:00 MEZ _

2016-

[Spacewalk-list] Antwort: Re: Errata Cache bunch running forever on Spacewalk 2.4

[Paschedag . Netlution]

Hello again,

still having problems,

I noticed that the errata-cache gets triggerd when a client refreshes its 
repos or searches for updates. So I manually fired a "zypper ref -s" or a 
"apt-get update" on every client connected to this spacewalk server. This 
seems to have fixed "something". Suddenly, the "errata-cache" task has 
finished and I got some backtraces from spacewalk.

But I still have trouble. The UI does not seem to get updated correctly 
(on the "system" page, nearly all systems look "up-to-date". But I know, 
it's not!). But the updates are available to the clients (searching on the 
client).

When I look into the last errata-cache schedules (in Spacewalk "Admin" -> 
"Task schedules" -> "errata-cache-bunch") I can see, that the 
"errata-cache" tasks is often "SKIPPED"


errata-cache 
2016-01-12 08:50:00 MEZ 
2016-01-12 08:50:00 MEZ 
SKIPPED 
errata-cache 
2016-01-12 08:49:00 MEZ 
2016-01-12 08:49:00 MEZ 
SKIPPED 
errata-cache 
2016-01-12 08:48:00 MEZ 
2016-01-12 08:48:00 MEZ 
SKIPPED 
errata-cache 
2016-01-12 08:47:00 MEZ 
2016-01-12 08:50:00 MEZ 
FINISHED 
errata-cache 
2016-01-12 08:46:00 MEZ 
2016-01-12 08:46:00 MEZ 
SKIPPED 
errata-cache 
2016-01-12 08:45:00 MEZ 
2016-01-12 08:45:00 MEZ 
SKIPPED 
errata-cache 
2016-01-12 08:44:00 MEZ 
2016-01-12 08:46:00 MEZ 
FINISHED 
errata-mailer 
2016-01-12 08:43:00 MEZ 
2016-01-12 08:43:00 MEZ 
FINISHED 
errata-cache 
2016-01-12 08:43:00 MEZ 
2016-01-12 08:43:00 MEZ 
FINISHED 
errata-cache 
2016-01-12 08:42:00 MEZ 
2016-01-12 08:42:00 MEZ 
SKIPPED 
errata-cache 
2016-01-12 08:41:00 MEZ 
2016-01-12 08:41:00 MEZ 
SKIPPED 
errata-cache 
2016-01-12 08:40:00 MEZ 
2016-01-12 08:40:00 MEZ 
SKIPPED 
errata-cache 
2016-01-12 08:39:00 MEZ 
2016-01-12 08:42:00 MEZ 
FINISHED 
errata-mailer 
2016-01-12 08:38:00 MEZ 
2016-01-12 08:38:00 MEZ 
FINISHED 
errata-cache 
2016-01-12 08:38:00 MEZ 
2016-01-12 08:38:00 MEZ 
FINISHED 
errata-mailer 
2016-01-12 08:37:00 MEZ 
2016-01-12 08:37:00 MEZ 
FINISHED 
errata-cache 
2016-01-12 08:37:00 MEZ 
2016-01-12 08:37:00 MEZ 
FINISHED 
errata-cache 
2016-01-12 08:36:00 MEZ 
2016-01-12 08:36:00 MEZ 
SKIPPED 
errata-cache 
2016-01-12 08:35:00 MEZ 
2016-01-12 08:35:00 MEZ 
SKIPPED 
errata-cache 
2016-01-12 08:34:00 MEZ 
2016-01-12 08:36:00 MEZ 
FINISHED 
errata-mailer 
2016-01-12 08:33:00 MEZ 
2016-01-12 08:33:00 MEZ 
FINISHED 
errata-cache 
2016-01-12 08:33:00 MEZ 
2016-01-12 08:33:00 MEZ 
FINISHED 
errata-mailer 
2016-01-12 08:32:00 MEZ 
2016-01-12 08:32:00 MEZ 
FINISHED 
errata-cache 
2016-01-12 08:32:00 MEZ 
2016-01-12 08:32:00 MEZ 
FINISHED 
errata-mailer 
2016-01-12 08:31:00 MEZ 
2016-01-12 08:31:00 MEZ 
FINISHED 
errata-cache 
2016-01-12 08:31:00 MEZ 
2016-01-12 08:31:00 MEZ 
FINISHED 
errata-mailer 
2016-01-12 08:30:00 MEZ 
2016-01-12 08:30:00 MEZ 
FINISHED 
errata-cache 
2016-01-12 08:30:00 MEZ 
2016-01-12 08:30:00 MEZ 
FINISHED 
errata-cache 
2016-01-12 08:29:00 MEZ 
2016-01-12 08:29:00 MEZ 
SKIPPED 

And also I noticed that the "errata-mailer" tasks seems to get only 
started, when the "errata-cache" tasks finished within one minute. (Just 
look above). As soon as the errata-cache tasks runs longer than one 
minute, the "errata-mailer" is not started. I'm also not sure, if 
something went wrong, while I was shutting down the spacewalk server for 
the update.

This is what it looked before (on spacewalk 2.2). I started the update on 
2016-01-04 abount 08:30.

errata-cache 
2016-01-04 10:10:00 MEZ 
2016-01-04 10:10:00 MEZ 
SKIPPED 
errata-cache 
2016-01-04 10:00:00 MEZ 
2016-01-04 10:00:00 MEZ 
SKIPPED 
errata-cache 
2016-01-04 09:50:00 MEZ 
2016-01-04 09:50:00 MEZ 
SKIPPED 
errata-cache 
2016-01-04 09:40:00 MEZ 
2016-01-04 09:40:00 MEZ 
SKIPPED 
errata-cache 
2016-01-04 09:30:00 MEZ 
2016-01-04 09:30:00 MEZ 
SKIPPED 
errata-cache 
2016-01-04 09:20:00 MEZ 
2016-01-04 09:20:00 MEZ 
SKIPPED 
errata-cache 
2016-01-04 09:10:00 MEZ 
2016-01-04 09:10:00 MEZ 
SKIPPED 
errata-cache 
2016-01-04 09:00:00 MEZ 
2016-01-04 09:00:00 MEZ 
SKIPPED 
errata-cache 
2016-01-04 08:50:00 MEZ 
2016-01-04 08:50:00 MEZ 
SKIPPED 
errata-cache 
2016-01-04 08:40:00 MEZ 
2016-01-04 08:40:00 MEZ 
SKIPPED 
errata-cache 
2016-01-04 08:30:00 MEZ 
2016-01-05 08:59:59 MEZ 
INTERRUPTED 
errata-mailer 
2016-01-04 08:30:00 MEZ 
2016-01-04 08:29:57 MEZ 
INTERRUPTED 
errata-mailer 
2016-01-04 08:00:00 MEZ 
2016-01-04 08:00:00 MEZ 
FINISHED 
errata-cache 
2016-01-04 08:00:00 MEZ 
2016-01-04 08:00:00 MEZ 
FINISHED 
errata-mailer 
2016-01-04 07:50:00 MEZ 
2016-01-04 07:50:00 MEZ 
FINISHED 
errata-cache 
2016-01-04 07:50:00 MEZ 
2016-01-04 07:50:00 MEZ 
FINISHED 

I would be glad, if someone could give me further hints, where to look for 
the root cause to this.

Kind regards,
Robert


Mit freundlichen Grüßen

Robert Paschedag
Netlution GmbH
Landteilstr. 33
68163 Mannheim

im Auftrag des
SWR
Südwestrundfunk
Informations- und Kommunikationssysteme
Neckarstraße 230
70190 Stuttgart

Telefon +49 (0)711 /929-12654 oder
Telefon +49 (0)711 /929-13714
paschedag.netlut..