<div dir="ltr">Hello Friends<div> </div><div>Nick, they don't decided to ignore your emails :-)), Merry X'mas my friend.</div><div> </div><div>Veeram, about your questions, about OS, I really don't know, about emails, by default of SW you don't have any place to configure it, but you can create tasks using spacecmd or api, so you will create a script for example, and check if you have any schedule, case yes, you send a email alert.</div><div> </div><div>You can do everything in SW! Feel free! ;-)</div><div> </div><div>Take Care and Merry X'mas</div></div><div class="gmail_extra"> <div><div class="gmail_signature"><div>______________ Atenciosamente Waldirio msn: <a href="mailto:waldirio@gmail.com" target="_blank">waldirio@gmail.com</a> Skype: waldirio Site: <a href="http://www.waldirio.com.br" target="_blank">www.waldirio.com.br</a> Blog: <a href="http://blog.waldirio.com.br" target="_blank">blog.waldirio.com.br</a></div> <div>LinkedIn: <a href="http://br.linkedin.com/pub/waldirio-pinheiro/22/b21/646" target="_blank">http://br.linkedin.com/pub/waldirio-pinheiro/22/b21/646</a> PGP: <a href="http://www.waldirio.com.br/public.html" target="_blank">www.waldirio.com.br/public.html</a></div></div></div> <div class="gmail_quote">On Tue, Dec 23, 2014 at 7:24 PM, Nick Tailor <<a href="mailto:HTailor@bclc.com" target="_blank">HTailor@bclc.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Veeram, Currently, no one to my knowledge has successfully got Ubuntu or Debian working 100%. I have been trying for a couple of weeks to get debian wheezy working 100%. I am close, however unless someone on here has and has just decided to ignore my emails. I don't believe debian or Ubuntu work 100% with spacewalk. You kind of have to go through an fix the problems as they come. Cheers Nick Tailor Nicktailor.com -----Original Message----- From: <a href="mailto:spacewalk-list-bounces@redhat.com">spacewalk-list-bounces@redhat.com</a> [mailto:<a href="mailto:spacewalk-list-bounces@redhat.com">spacewalk-list-bounces@redhat.com</a>] On Behalf Of Veera Veluchamy Sent: Tuesday, December 23, 2014 2:07 AM To: <a href="mailto:spacewalk-list@redhat.com">spacewalk-list@redhat.com</a> <div class="HOEnZb"><div class="h5">Subject: Re: [Spacewalk-list] Spacewalk-list Digest, Vol 79, Issue 97 Hi Nick Tailor, I have one more question about spacewalk configuration 1.Does it supports Ubuntu 12.04 2.How to configure spacewalk to send alerts when we schedule any patching . Thanks & Regards Veerakumar V Infrastructure Application Support -----Original Message----- From: <a href="mailto:spacewalk-list-bounces@redhat.com">spacewalk-list-bounces@redhat.com</a> [mailto:<a href="mailto:spacewalk-list-bounces@redhat.com">spacewalk-list-bounces@redhat.com</a>] On Behalf Of <a href="mailto:spacewalk-list-request@redhat.com">spacewalk-list-request@redhat.com</a> Sent: Tuesday, December 23, 2014 3:22 PM To: <a href="mailto:spacewalk-list@redhat.com">spacewalk-list@redhat.com</a> Subject: Spacewalk-list Digest, Vol 79, Issue 97 Send Spacewalk-list mailing list submissions to <a href="mailto:spacewalk-list@redhat.com">spacewalk-list@redhat.com</a> To subscribe or unsubscribe via the World Wide Web, visit <a href="https://www.redhat.com/mailman/listinfo/spacewalk-list" target="_blank">https://www.redhat.com/mailman/listinfo/spacewalk-list</a> or, via email, send a message with subject or body 'help' to <a href="mailto:spacewalk-list-request@redhat.com">spacewalk-list-request@redhat.com</a> You can reach the person managing the list at <a href="mailto:spacewalk-list-owner@redhat.com">spacewalk-list-owner@redhat.com</a> When replying, please edit your Subject line so it is more specific than "Re: Contents of Spacewalk-list digest..." Today's Topics: 1. Re: Reg:OSA-dispatcher is not running (Nick Tailor) 2. Re: Schedling & Action Chain Timing Question (Matt Bayliss) 3. Re: Reg:Spacewalk Configuration steps (Alexander Innes) ---------------------------------------------------------------------- Message: 1 Date: Tue, 23 Dec 2014 05:35:34 +0000 From: Nick Tailor <HTailor@BCLC.com> To: "<a href="mailto:spacewalk-list@redhat.com">spacewalk-list@redhat.com</a>" <<a href="mailto:spacewalk-list@redhat.com">spacewalk-list@redhat.com</a>> Subject: Re: [Spacewalk-list] Reg:OSA-dispatcher is not running Message-ID: <8FCFC665E3D16B4592779FE49FAA4EF450FA4F72@kam1opeml04> Content-Type: text/plain; charset="us-ascii" Hi Veera, I have found osad dispatcher to be very unreliable and buggy. Both in spacewalk and in redhat satellite server. Its easier and more effective to setup a cron that does an rhn_check every 5 minutes on your clients, it also frees up memory on a process that doesn't need to be running in the background this way. Cheers Nick Tailor Nicktailor.com From: <a href="mailto:spacewalk-list-bounces@redhat.com">spacewalk-list-bounces@redhat.com</a> [mailto:<a href="mailto:spacewalk-list-bounces@redhat.com">spacewalk-list-bounces@redhat.com</a>] On Behalf Of Veera Veluchamy Sent: Monday, December 22, 2014 7:48 PM To: <a href="mailto:spacewalk-list@redhat.com">spacewalk-list@redhat.com</a> Subject: [Spacewalk-list] Reg:OSA-dispatcher is not running Hi, I have got some issues while restarting spacewalk service .Can anybody help me to resolve this issue. Starting osa-dispatcher: Traceback (most recent call last): File "/usr/sbin/osa-dispatcher", line 28, in <module> mod = __import__("osad." + mod_name) File "/usr/share/rhn/osad/osa_dispatcher.py", line 24, in <module> from spacewalk.common.rhnConfig import initCFG, CFG File "/usr/lib/python2.6/site-packages/spacewalk/common/rhnConfig.py", line 522, in <module> ALL_CFG.parse() File "/usr/lib/python2.6/site-packages/spacewalk/common/rhnConfig.py", line 135, in parse self.__parsedConfig = parse_file(self.filename) File "/usr/lib/python2.6/site-packages/spacewalk/common/rhnConfig.py", line 406, in parse_file (keys, values) = parse_line(line) File "/usr/lib/python2.6/site-packages/spacewalk/common/rhnConfig.py", line 371, in parse_line (keys, vals) = [c.strip() for c in line.split('=', 1)] spacewalk.common.rhnConfig.ConfigParserError: Parse Error: </etc/rhn/rhn.conf:60>: ' RHN::Task::ErrataQueue, ' [FAILED] Veerakumar V Infrastructure Application Support [Image removed by sender. Aspire Systems] This e-mail message and any attachments are for the sole use of the intended recipient(s) and may contain proprietary, confidential, trade secret or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited and may be a violation of law. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. ________________________________ This email is intended only for the addressee. It may contain confidential or proprietary information that cannot be disclosed without BCLC's permission. If you have received this email in error, please notify the sender immediately and delete the email. -------------- next part -------------- An HTML attachment was scrubbed... URL: <<a href="https://www.redhat.com/archives/spacewalk-list/attachments/20141223/4c811bcc/attachment.html" target="_blank">https://www.redhat.com/archives/spacewalk-list/attachments/20141223/4c811bcc/attachment.html</a>> -------------- next part -------------- A non-text attachment was scrubbed... Name: ~WRD000.jpg Type: image/jpeg Size: 823 bytes Desc: ~WRD000.jpg URL: <<a href="https://www.redhat.com/archives/spacewalk-list/attachments/20141223/4c811bcc/attachment.jpg" target="_blank">https://www.redhat.com/archives/spacewalk-list/attachments/20141223/4c811bcc/attachment.jpg</a>> ------------------------------ Message: 2 Date: Tue, 23 Dec 2014 09:46:50 +0000 From: Matt Bayliss <<a href="mailto:aarrgghh765@gmail.com">aarrgghh765@gmail.com</a>> To: <a href="mailto:spacewalk-list@redhat.com">spacewalk-list@redhat.com</a> Subject: Re: [Spacewalk-list] Schedling & Action Chain Timing Question Message-ID: <<a href="mailto:CAJivT9kshuyujzdSaLhPp2H6wW5NQtSY8fz4KYgecXkWQVcMpg@mail.gmail.com">CAJivT9kshuyujzdSaLhPp2H6wW5NQtSY8fz4KYgecXkWQVcMpg@mail.gmail.com</a>> Content-Type: text/plain; charset="utf-8" OK, so I've doing some more testing on this - since I couldn't remember preciseley the time I submitted the previous jobs so I've recorded times more accurately now. Yesterday morning between 1045-1100 GMT I submitted a number of jobs to run at 9AM over the next 4 days too see when they were picked up and executed. The first job was scheduled to execute today after 9AM, according to the schedule its showing: - *Summary:* Package Install scheduled by mattb - *Details:* This action will be executed after 12/23/14 9:00:00 AM GMT This action's status is: Queued. This action has not yet been picked up. Packages Scheduled: - kernel-2.6.32-504.3.3.el6.x86_64 - rsyslog-5.8.10-10.el6_6.x86_64 - kernel-firmware-2.6.32-504.3.3.el6.noarch - *Time:* 12/23/14 9:00:00 AM GMT I'm surprised that the action "has not yet been picked up" since the server checked in (via the spacewalk proxy) just 35 minutes before the "execute after" time. I've checked and times on the three involved nodes (spacewalk, proxy & client) are all in sync. Regards, On 19 December 2014 at 12:10, Matt Bayliss <<a href="mailto:aarrgghh765@gmail.com">aarrgghh765@gmail.com</a>> wrote: > I scheduled a jobs on the morning of the 17th December to execute the > following morning at 9AM, it seems that although the rhnsd interval is > set to 240 [1] the job was not picked up and executed until approx 28 > hours after I created the schedule. > > [1] # cat /etc/sysconfig/rhn/rhnsd > INTERVAL=240 > > > Summary: > Package Install scheduled by swadmin > Details: > This action will be executed after 12/18/14 9:00:00 AM GMT > This action's status is: Completed. > The client picked up this action on 12/18/14 3:03 PM > The client completed this action on 12/18/14 3:05 PM > Client execution returned "Update Succeeded" (code 0) > Packages Scheduled: > nss-util-3.16.2.3-2.el6_6.x86_64 > rpm-python-4.8.0-38.el6_6.x86_64 > rpm-4.8.0-38.el6_6.x86_64 > system-config-firewall-base-1.2.27-7.2.el6_6.noarch > selinux-policy-3.7.19-260.el6_6.1.noarch > nss-3.16.2.3-3.el6_6.x86_64 > nss-sysinit-3.16.2.3-3.el6_6.x86_64 > rpm-build-4.8.0-38.el6_6.x86_64 > nss-tools-3.16.2.3-3.el6_6.x86_64 > ruby-1.8.7.374-3.el6_6.x86_64 > ruby-libs-1.8.7.374-3.el6_6.x86_64 > rpm-libs-4.8.0-38.el6_6.x86_64 > selinux-policy-targeted-3.7.19-260.el6_6.1.noarch > Time: > 12/18/14 9:00:00 AM GMT > > Also, this job was pard of an action chain to reboot the system when > the package update was complete (not necessary but I wanted to test > it) this was not completed until 4-5 hours after the package update > which would have only taken a few minutes. I'm surprised that this > didn't happen immediately afterward. > > Summary: > System reboot scheduled by mattb > Details: > This action will be executed after 12/18/14 9:00:00 AM GMT This > action's status is: Completed. > The client picked up this action on 12/18/14 3:05 PM The client > completed this action on 12/18/14 7:48 PM Client execution returned > "null" (code null) > Time: > 12/18/14 9:00:00 AM GMT > > Am I misunderstanding how the scheduler works? I won't be able to > rely on this in production if I can't predict with some accuracy when > the jobs will execute. > > Regards, > -------------- next part -------------- An HTML attachment was scrubbed... URL: <<a href="https://www.redhat.com/archives/spacewalk-list/attachments/20141223/c20072e2/attachment.html" target="_blank">https://www.redhat.com/archives/spacewalk-list/attachments/20141223/c20072e2/attachment.html</a>> ------------------------------ Message: 3 Date: Tue, 23 Dec 2014 09:52:17 +0000 From: Alexander Innes <<a href="mailto:senni@necurity.co.uk">senni@necurity.co.uk</a>> To: <a href="mailto:spacewalk-list@redhat.com">spacewalk-list@redhat.com</a> Subject: Re: [Spacewalk-list] Reg:Spacewalk Configuration steps Message-ID: <CAM8GbV75fn5RPMZiW4C7u4RBy14vTa45qXV2=<a href="mailto:D2KOH4-qgNhfQ@mail.gmail.com">D2KOH4-qgNhfQ@mail.gmail.com</a>> Content-Type: text/plain; charset="utf-8" for email alerts they should be on by default as long as you create an account with a valid email address. Can the box itself send emails correctly? You may need to use "postconf -e 'relay.host=X.X.X.X' " to configure postfixes mail relay (thats off the top of my head though so it is postonf but maybe not the relay.host!) As for the buntu hosts there is <a href="http://www.devops-blog.net/spacewalk/registering-ubuntu-and-debian-servers-with-spacewalk" target="_blank">http://www.devops-blog.net/spacewalk/registering-ubuntu-and-debian-servers-with-spacewalk</a> and <a href="https://fedorahosted.org/spacewalk/wiki/RegisteringClients" target="_blank">https://fedorahosted.org/spacewalk/wiki/RegisteringClients</a> The mailing list is more suited to troubleshooting then guides :) On 22 December 2014 at 14:40, Veera Veluchamy <<a href="mailto:veera.veluchamy@aspiresys.com">veera.veluchamy@aspiresys.com</a> > wrote: > Hi , > > > > Can anyone help me how to configure email alerts in spacewalk and I > need step by step procedure to configure spacewalk server to support > Ubuntu clients. > > > > Thank you. > > > > Veerakumar V > > Infrastructure Application Support > > > [image: Aspire Systems] > > This e-mail message and any attachments are for the sole use of the > intended recipient(s) and may contain proprietary, confidential, trade > secret or privileged information. Any unauthorized review, use, > disclosure or distribution is prohibited and may be a violation of > law. If you are not the intended recipient, please contact the sender > by reply e-mail and destroy all copies of the original message. > > _______________________________________________ > Spacewalk-list mailing list > <a href="mailto:Spacewalk-list@redhat.com">Spacewalk-list@redhat.com</a> > <a href="https://www.redhat.com/mailman/listinfo/spacewalk-list" target="_blank">https://www.redhat.com/mailman/listinfo/spacewalk-list</a> > -------------- next part -------------- An HTML attachment was scrubbed... URL: <<a href="https://www.redhat.com/archives/spacewalk-list/attachments/20141223/224ad9ef/attachment.html" target="_blank">https://www.redhat.com/archives/spacewalk-list/attachments/20141223/224ad9ef/attachment.html</a>> ------------------------------ _______________________________________________ Spacewalk-list mailing list <a href="mailto:Spacewalk-list@redhat.com">Spacewalk-list@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/spacewalk-list" target="_blank">https://www.redhat.com/mailman/listinfo/spacewalk-list</a> End of Spacewalk-list Digest, Vol 79, Issue 97 ********************************************** [Aspire Systems] This e-mail message and any attachments are for the sole use of the intended recipient(s) and may contain proprietary, confidential, trade secret or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited and may be a violation of law. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. _______________________________________________ Spacewalk-list mailing list <a href="mailto:Spacewalk-list@redhat.com">Spacewalk-list@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/spacewalk-list" target="_blank">https://www.redhat.com/mailman/listinfo/spacewalk-list</a> ________________________________ This email is intended only for the addressee. It may contain confidential or proprietary information that cannot be disclosed without BCLC's permission. If you have received this email in error, please notify the sender immediately and delete the email. _______________________________________________ Spacewalk-list mailing list <a href="mailto:Spacewalk-list@redhat.com">Spacewalk-list@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/spacewalk-list" target="_blank">https://www.redhat.com/mailman/listinfo/spacewalk-list</a> </div></div></blockquote></div> </div>