Hello!
On 08/26/2015 03:14 PM, Tomas Lestach wrote:
Are there any errors in taskomatic and repo-sync logs ?
* /var/log/rhn/rhn_taskomatic_daemon.log
* /var/log/rhn/reposync/channel.log
There's no information on both log name, only manual
spacewalk-repo-sync
logged.
Example:
On 27/08/2015 20:02, Matthew Madey wrote:
Is it possible I have my settings set too high? I need to be able to serve
requests for 1600+ clients more or less simultaneously.
I have no idea of the hardware you are running on, but this sounds like way too
much for me. In my experience servers
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
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
Avi,
I just wanted to report that I was able successfully use your docs and use our
*.domain cert in my SW environment. There were a few times that I thought
that I would have to ask for assistance, but I was able to work through those
and get this working.
Thank you again for your
Hey,
On 29 Aug 2015, at 3:43 am, Daryl Rose darylr...@outlook.com wrote:
I just wanted to report that I was able successfully use your docs and use
our *.domain cert in my SW environment. There were a few times that I
thought that I would have to ask for assistance, but I was able to
