[Spacewalk-list] Spacewalk-list Digest, Vol 79, Issue 97
Waldirio Manhães Pinheiro
waldirio at gmail.com
Wed Dec 24 02:51:25 UTC 2014
Hello Friends
Nick, they don't decided to ignore your emails :-)), Merry X'mas my friend.
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.
You can do everything in SW! Feel free! ;-)
Take Care and Merry X'mas
______________
Atenciosamente
Waldirio
msn: waldirio at gmail.com
Skype: waldirio
Site: www.waldirio.com.br
Blog: blog.waldirio.com.br
LinkedIn: http://br.linkedin.com/pub/waldirio-pinheiro/22/b21/646
PGP: www.waldirio.com.br/public.html
On Tue, Dec 23, 2014 at 7:24 PM, Nick Tailor <HTailor at bclc.com> wrote:
> 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: spacewalk-list-bounces at redhat.com [mailto:
> spacewalk-list-bounces at redhat.com] On Behalf Of Veera Veluchamy
> Sent: Tuesday, December 23, 2014 2:07 AM
> To: spacewalk-list at redhat.com
> 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: spacewalk-list-bounces at redhat.com [mailto:
> spacewalk-list-bounces at redhat.com] On Behalf Of
> spacewalk-list-request at redhat.com
> Sent: Tuesday, December 23, 2014 3:22 PM
> To: spacewalk-list at redhat.com
> Subject: Spacewalk-list Digest, Vol 79, Issue 97
>
> Send Spacewalk-list mailing list submissions to spacewalk-list at redhat.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://www.redhat.com/mailman/listinfo/spacewalk-list
> or, via email, send a message with subject or body 'help' to
> spacewalk-list-request at redhat.com
>
> You can reach the person managing the list at
> spacewalk-list-owner at redhat.com
>
> 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 at BCLC.com>
> To: "spacewalk-list at redhat.com" <spacewalk-list at redhat.com>
> Subject: Re: [Spacewalk-list] Reg:OSA-dispatcher is not running
> Message-ID: <8FCFC665E3D16B4592779FE49FAA4EF450FA4F72 at 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: spacewalk-list-bounces at redhat.com [mailto:
> spacewalk-list-bounces at redhat.com] On Behalf Of Veera Veluchamy
> Sent: Monday, December 22, 2014 7:48 PM
> To: spacewalk-list at redhat.com
> 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: <
> https://www.redhat.com/archives/spacewalk-list/attachments/20141223/4c811bcc/attachment.html
> >
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: ~WRD000.jpg
> Type: image/jpeg
> Size: 823 bytes
> Desc: ~WRD000.jpg
> URL: <
> https://www.redhat.com/archives/spacewalk-list/attachments/20141223/4c811bcc/attachment.jpg
> >
>
> ------------------------------
>
> Message: 2
> Date: Tue, 23 Dec 2014 09:46:50 +0000
> From: Matt Bayliss <aarrgghh765 at gmail.com>
> To: spacewalk-list at redhat.com
> Subject: Re: [Spacewalk-list] Schedling & Action Chain Timing Question
> Message-ID:
> <CAJivT9kshuyujzdSaLhPp2H6wW5NQtSY8fz4KYgecXkWQVcMpg at mail.gmail.com>
> 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 <aarrgghh765 at gmail.com> 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: <
> https://www.redhat.com/archives/spacewalk-list/attachments/20141223/c20072e2/attachment.html
> >
>
> ------------------------------
>
> Message: 3
> Date: Tue, 23 Dec 2014 09:52:17 +0000
> From: Alexander Innes <senni at necurity.co.uk>
> To: spacewalk-list at redhat.com
> Subject: Re: [Spacewalk-list] Reg:Spacewalk Configuration steps
> Message-ID:
> <CAM8GbV75fn5RPMZiW4C7u4RBy14vTa45qXV2=D2KOH4-qgNhfQ at mail.gmail.com>
> 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
>
> http://www.devops-blog.net/spacewalk/registering-ubuntu-and-debian-servers-with-spacewalk
> and
> https://fedorahosted.org/spacewalk/wiki/RegisteringClients
>
> The mailing list is more suited to troubleshooting then guides :)
>
> On 22 December 2014 at 14:40, Veera Veluchamy <
> veera.veluchamy at aspiresys.com
> > 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
> > Spacewalk-list at redhat.com
> > https://www.redhat.com/mailman/listinfo/spacewalk-list
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://www.redhat.com/archives/spacewalk-list/attachments/20141223/224ad9ef/attachment.html
> >
>
> ------------------------------
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
> 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
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
> ________________________________
> 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
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20141224/bde93095/attachment.htm>
More information about the Spacewalk-list
mailing list