Hi James and Stuart,
Thanks for sharing your insights. Although I still don't have any idea why I
saw the following errors, I will try out Stuart's suggestion and setup
anaconda's remote logging instead.
A side note, we will be working on FreeBSD soon, and AFAIK anaconda is not
available to the BSD world (yet). So, here again, any suggestions are welcome!
Regards,
-- Zack
> > I have noticed that when the following are done:
> >
> > * anamon_enabled: 1 in /etc/cobbler/settings
> > * $SNIPPET('pre_anamon') and $SNIPPET('post_anamon')
> are in the kickstart template (e.g.
> /var/lib/cobbler/kickstarts/rh.cfg)
> >
> > Sometimes, on a KVM host, some guests after done with
> PXE booting, would show errors like the following on their
> respective virtual machine console:
> >
> > Traceback (most recent call last):
> > File "/usr/local/sbin/anamon", line 275, in
> <module> anamoun_loop()
> > File "/usr/local/sbin/anamon", line 224, in
> anamon_loop wf.update()
> > File "/usr/local/sbin/anamon", line 121, in
> update self.uploadWrapper()
> > [...]
> >
> > But other guests do not show such errors. This
> symptom typically show up when we simultaneously PXE boot a
> number of guests.
> >
> > I have known that anamon is considered deprecated for a
> while. This is even in the official doc for 2.2.3
> <http://cobbler.github.com/manuals/2.2.3/5/4_-_Anaconda_Monitoring.html>
>
> That note is not accurate, and needs to be updated. The
> point is that
> since anamon is Red Hat (and clones) specific, that it is
> not a
> general purpose monitoring solution for cobbler since it has
> started
> supporting other distributions.
>
> If you're using RHEL/Fedora or a clone, anamon is the
> recommended
> solution as far as I know (as Stuart mentioned in his
> response syslog
> is an alternative).
_______________________________________________
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler
