Oh... Just saw that the checksum error occurs when run on a "client"..Am 15.12.2016 22:48 schrieb Daryl Rose :
One more thought
What would happen if I were to delete the current RHEL channel and repository and recreate them? What will happen to all of the packages and clients
Daryl,Are you using a proxy to download the repositories? The checksum error indicates that maybe something gets corrupted. Am 15.12.2016 22:48 schrieb Daryl Rose :
One more thought
What would happen if I were to delete the current RHEL channel and repository and recreate them
One more thought
What would happen if I were to delete the current RHEL channel and repository
and recreate them? What will happen to all of the packages and clients
currently registered to the channel/repo? I know that the packages will become
orphan, but can I put them back into the ne
Hello Chris,
Thank you for the following steps. I think this resolved this immanent issue,
but the issue of not being able to sync from the parent Red Hat repository is
still an issue.
Do you know how the contents of ./cache/rhn/reposync are created? As a work
around, I copied the contents
Hello All,
I just upgraded to Spacewalk 2.6 and everything seems to be working fine with
the exception of Taskomatic which will not fire up… From the Taskomatic log:
STATUS | wrapper | 2016/12/14 16:03:25 | Launching a JVM...
ERROR | wrapper | 2016/12/14 16:03:25 | JVM exited while loading t
Check the taskomatic log to see if you are exceeding the memory limits. I ran into that several times because the RHEL repos can get huge over time.
I am running v2.6. I had inadvertently upgraded to 2.6 when I stood up the new
server.
I had upgraded the original server to v2.5. When switching over, I installed
SW thinking that it was v2.5 not realizing that v2.6 had just been published
that day. That did cause some initial issues with