[Spacewalk-list] Added servers not showing updates in UI without master server restart

[Patrick Blair - Peapod]

Thanks for the tip!

I restarted taskomatic and the newly registered servers are checking in
immediately, so it looks like that may have been the issue.

I set up a cronjob to restart taskomatic every 12 hours, so hopefully that
should solve it.

Thanks again!

Pat Blair
Sr. Unix Administrator
Peapod, LLC
pblair at peapod.com

On Fri, Aug 28, 2015 at 11:46 AM, Coffman, Anthony J <
Tony.Coffman at snapon.com> wrote:

> There is some kind of new bug in the Spacewalk 2.3 version of taskomatic
> where client system reports aren’t processed in a timely fashion.
>
>
>
> If you restart taskomatic, it should process in a few minutes which is
> definitely less painful than a full restart.
>
>
>
> If you are on 2.3 – this might be the issue you are experiencing.
>
>
>
> --Tony
>
>
>
>
>
>
>
>
>
>
>
>
>
> *From:* spacewalk-list-bounces at redhat.com [mailto:
> spacewalk-list-bounces at redhat.com] *On Behalf Of *Patrick Blair - Peapod
> *Sent:* Friday, August 28, 2015 11:59 AM
> *To:* spacewalk-list at redhat.com
> *Subject:* [Spacewalk-list] Added servers not showing updates in UI
> without master server restart
>
>
>
> Hi Spacewalkers,
>
> I was just wondering if anyone has come across a similar problem:
>
> After I register a new server (that requires updates) to our Spacewalk
> instance (either direct or through a proxy), the UI shows that it is fully
> up to date and that no package upgrades are required. This persists even
> through rhn_check(s) and rhn-profile-sync being run on the client servers.
>
> The only way that this seems to resolve itself is through a full restart
> of the Spacewalk master.
>
> Though, if I run a yum update on the client, all the updates will come
> through correctly.
>
> This started happening after I ran pgtune on the postgresql DB and applied
> the optimized settings as follows:
>
> maintenance_work_mem = 704MB
> effective_cache_size = 8GB
> work_mem = 18MB
> wal_buffers = 16MB
> shared_buffers = 2816MB
> default_statistics_target = 100
> checkpoint_segments = 32
>
>
>
> I also enabled autovacuum with the default settings.
>
> Has anyone else experienced these issues and/or found a fix?
>
> Thanks!
>
>
> Pat Blair
> Sr. Unix Administrator
> Peapod, LLC
> pblair at peapod.com
>
>
>
>
>
> This email and any attachments may contain information that is proprietary,
>
> confidential and/or privileged and for the sole use of the intended
> recipients(s)
>
> only.
>
> If you are not the intended recipient, please notify the sender by return
>
> email and delete all copies of this email and any attachments. Ahold
> and/or its
>
> subsidiaries shall neither be liable for the inaccurate or incomplete
> transmission
>
> of the information contained in this email or any attachments, nor for any
> delay
>
> in its receipt. To the extent this email is intended to create any legal
> obligation,
>
> the obligation shall bind only the contracting entity and not any other
> entity within
>
> the Ahold Group.
>
>
>
> This email and any attachments may contain information that is proprietary,
>
> confidential and/or privileged and for the sole use of the intended
> recipients(s)
>
> only.
>
> If you are not the intended recipient, please notify the sender by return
>
> email and delete all copies of this email and any attachments. Ahold
> and/or its
>
> subsidiaries shall neither be liable for the inaccurate or incomplete
> transmission
>
> of the information contained in this email or any attachments, nor for any
> delay
>
> in its receipt. To the extent this email is intended to create any legal
> obligation,
>
> the obligation shall bind only the contracting entity and not any other
> entity within
>
> the Ahold Group.
>

-- 
This email and any attachments may contain information that is proprietary,
confidential and/or privileged and for the sole use of the intended 
recipients(s)
only.
If you are not the intended recipient, please notify the sender by return
email and delete all copies of this email and any attachments. Ahold and/or 
its
subsidiaries shall neither be liable for the inaccurate or incomplete 
transmission
of the information contained in this email or any attachments, nor for any 
delay
in its receipt. To the extent this email is intended to create any legal 
obligation,
the obligation shall bind only the contracting entity and not any other 
entity within
the Ahold Group.

-- 
This email and any attachments may contain information that is proprietary,
confidential and/or privileged and for the sole use of the intended 
recipients(s)
only.
If you are not the intended recipient, please notify the sender by return
email and delete all copies of this email and any attachments. Ahold and/or 
its
subsidiaries shall neither be liable for the inaccurate or incomplete 
transmission
of the information contained in this email or any attachments, nor for any 
delay
in its receipt. To the extent this email is intended to create any legal 
obligation,
the obligation shall bind only the contracting entity and not any other 
entity within
the Ahold Group.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20150829/c73e0fb4/attachment.htm>