[Spacewalk-list] Spacewalk 2.1 - Upload kickstart file fails

2014-04-23 Thread Reed, Steven
Hi All, Am attempting to migrate from 1.9 to 2.1 all seems OK but when trying to upload a kickstart file (xml) spacewalk fires out: "There are errors in your kickstart template. Please check the 'Kickstart File' tab to determine the problem with the template" Investigating the 'kickstart file'

Re: [Spacewalk-list] PXE failure

2014-04-23 Thread Paul Robert Marino
Ah okDuring the install anaconda looks for the version in the build tree off the ISO not necessarily the latest in your repo. Import the rpms off of the ISO into the base channel and you should be good.-- Sent from my HP Pre3On Apr 23, 2014 13:52, Macklin, Jason wrote: Hi Paul,Just some more infor

Re: [Spacewalk-list] AUTO: William Darton is out of the office (returning 04/28/2014)

2014-04-23 Thread Paul Robert Marino
Greater to know that's really important info lol :-)-- Sent from my HP Pre3On Apr 23, 2014 16:04, will_dar...@navyfederal.org wrote: I am out of the office until 04/28/2014. Note: This is an automated response to your message "Re: [Spacewalk-list] Orphaned Scheduled Channel" sent on 4/23/201

[Spacewalk-list] AUTO: William Darton is out of the office (returning 04/28/2014)

2014-04-23 Thread Will_Darton
I am out of the office until 04/28/2014. Note: This is an automated response to your message "Re: [Spacewalk-list] Orphaned Scheduled Channel" sent on 4/23/2014 11:43:55 AM. This is the only notification you will receive while this person is away. ___

Re: [Spacewalk-list] PXE failure

2014-04-23 Thread Macklin, Jason
Hi Paul, Just some more information... in trying to track down which files to delete, I noticed that the version the anaconda installer is looking for is actually older then the version in my channels. For example, anaconda gets hung up looking for iputils-20071127-16.el6_4.2.x86_64, but the only

Re: [Spacewalk-list] PXE failure

2014-04-23 Thread Macklin, Jason
Hi Paul, Thank you for your prompt reply! This is exactly what I suspected, but I'm having difficulty finding the best way to address this. Should I manually search out the files and delete them manually? If so, which files are the correct files? Does spacewalk have a mechanism to address this

Re: [Spacewalk-list] Orphaned Scheduled Channel

2014-04-23 Thread Stuart Green
Hello Folks, Anyone know what the current command is to clear a orphaned taskomatic schedule (channel deleted without scheduler knowing about it) Actually I added some extra code to delete reposync schedules for invalid channel_ids 2 months ago. See https://github.com/spacewalkproject/spacewalk

Re: [Spacewalk-list] Orphaned Scheduled Channel

2014-04-23 Thread Paul Robert Marino
Very cool that been bugging me for a while I usually just go into the database and delete the offending task-- Sent from my HP Pre3On Apr 23, 2014 11:55, Tomas Lestach wrote: > Hello Folks, > > Anyone know what the current command is to clear a orphaned > taskomatic > schedule (channel deleted wi

Re: [Spacewalk-list] PXE failure

2014-04-23 Thread Paul Robert Marino
That usually happens when the kickstart sees two different packages with the same name with different checksums in the same or different channels used in the kickstart primarily I've seen it happen when a package which was in EPEL gets moved to the EL base distro. It can also happen in new implemen

[Spacewalk-list] PXE failure

2014-04-23 Thread Macklin, Jason
Good day! I have an instance of spacewalk 2.1 installed with postresql. I have created my default channels for CentOS 6 x86_64 along with spacewalk-client and some other basic channels. I have created my distribution from a copy of CentOS 6.4 x86_64 that I downloaded within the last 3 or 4 month

Re: [Spacewalk-list] Orphaned Scheduled Channel

2014-04-23 Thread Tomas Lestach
> Hello Folks, > > Anyone know what the current command is to clear a orphaned > taskomatic > schedule (channel deleted without scheduler knowing about it) Actually I added some extra code to delete reposync schedules for invalid channel_ids 2 months ago. See https://github.com/spacewalkproject

[Spacewalk-list] Orphaned Scheduled Channel

2014-04-23 Thread Stuart Green
Hello Folks, Anyone know what the current command is to clear a orphaned taskomatic schedule (channel deleted without scheduler knowing about it) Taskomatic bunch repo-sync-bunch was scheduled to run within the repo-sync-2-113 schedule. Subtask repo-sync failed. For more information check

[Spacewalk-list] duplicated monitoring entries after upgrade to 2.1

2014-04-23 Thread Balint Szigeti
hello after I upgraded the spacewalk 2.0 to 2.1 our monitoring entries were duplicated. I deleted all monitoring probes but the duplicates weren't gone. All of them have different rhn-catalog IDs. I've tried to run the duplicated entries and I got the normal output from the good one either duplic

Re: [Spacewalk-list] osa-dispatcher performance

2014-04-23 Thread Stuart Green
Schoolboy error/lack of sleep.. Installing osad will solve my problem of course... I think the openssl error albeit an error in itself is unrelated.. Tar. Stu On 23/04/2014 11:07, Stuart Green wrote: Sorry for the multiple emails, but just noticed the below server side.. Now I don't get

Re: [Spacewalk-list] osa-dispatcher performance

2014-04-23 Thread Stuart Green
Sorry for the multiple emails, but just noticed the below server side.. Now I don't get this as the cert does exist on the client machine and /etc/sysconfig/rhn/up2date points to it, I'll admit I pasted it into an empty file with vi from Notepad++ , but I did the unix conversion first and ha

Re: [Spacewalk-list] osa-dispatcher performance

2014-04-23 Thread Stuart Green
I've just changed my timezone from EDT to United Kingdom now on the spacewalk server. Hopefully this might resolve the problem as there's a lot of time dependency involved. AFAIK I think I've seen the list talking about an EDT issue with 2.1, although I couldn't say for sure what it was set t

[Spacewalk-list] osa-dispatcher performance

2014-04-23 Thread Stuart Green
Hello list, No doubt a topic of this nature has been discussed before, but could anyone point me in the direction as to why osa-dispatcher > up2date patch deployment could be so slooow? 10 hours seems a bit excessive... Details:This action will be executed after 04/17/14 5:24:00 AM E