[Spacewalk-list] Unable to sync (manually or through schedule) repos after upgrade 2.2 -> 2.3

Erin Landis erin.landis at msufcu.org
Tue Jun 16 15:16:07 UTC 2015


Howdy,

I recently upgraded spacewalk from 2.2 to 2.3, it took me a week or two to notice, but my scheduled channel syncs are not running any longer.  I have re-scheduled them (deleted the schedule and recreated) and this didn’t help.

I have also ran the spacewalk-repo-sync command manually and while the command seems to run ok, the sync’d packages don’t appear to end up in the proper channel.

I have verified that all of the spacewalk services are running:

[root at server ~]# spacewalk-service status
router (pid 1860) is running...
sm (pid 1868) is running...
c2s (pid 1876) is running...
s2s (pid 1884) is running...
tomcat6 (pid 1819) is running...
httpd (pid  1840) is running...
osa-dispatcher (pid  1899) is running...
rhn-search is running (1927).
cobblerd (pid 41004) is running...
RHN Taskomatic is running (2016).
[root at server~]#

Has anybody ran into this before?

Also, the spacewalk server is running on:

[root at server ~]# cat /etc/redhat-release
CentOS release 6.6 (Final)
[root at server ~]# uname -a
Linux server 2.6.32-504.16.2.el6.x86_64 #1 SMP Wed Apr 22 06:48:29 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
[root at server ~]#

Thanks,

Erin


________________________________
This electronic transmission and any information that it contains is the property of MSU Federal Credit Union and is intended for the use of the intended recipient. If you are not the intended recipient, any disclosure, copying or other use of this information is strictly prohibited. If you acquired this transmission in error or feel that any of the information contained within it is offensive or inappropriate, please contact internalaudit at msufcu.org<mailto:internalaudit at msufcu.org>.




More information about the Spacewalk-list mailing list