James:
Looking at settings.rpmnew and notice it matches the options I have in my
settings config
[root@eden cobbler]# grep report settings.rpmnew
# Email out a report when cobbler finishes installing a system.
build_reporting_enabled: 0
build_reporting_sender: ""
build_reporting_email: [ 'root@localhost' ]
build_reporting_smtp_server: "localhost"
build_reporting_subject: ""
[root@eden cobbler]# grep report settings
# Email out a report when cobbler finishes installing a system.
build_reporting_enabled: 1
build_reporting_sender: "cobb...@eden.potsdam.edu"
build_reporting_email: [ 'sysad...@potsdam.edu' , 'yacke...@potsdam.edu' ]
build_reporting_smtp_server: "smtp.potsdam.edu"
build_reporting_subject: "[COBBLER] "
[root@eden cobbler]# rpm -qa | grep cobbler
cobbler-2.2.3-2.el6.noarch
cobbler-web-2.2.3-2.el6.noarch
On Wednesday, 08 May, 2013 02:07 EDT, "James Cammarata" <j...@sngx.net> wrote:
> On Wed, May 8, 2013 at 1:00 PM, Ronald J. Yacketta
> <yacke...@potsdam.edu>wrote:
>
> > Trying to figure out why I am not getting e-mails from profile / system
> > installs. Found a patch and applied it then compared my KS file to the
> > default one left behind during a fresh install.
> >
> > After a profile / system is installed the install.log just shows a state
> > of 'stop' and never gets a 'finish' which I think is why e-mails are not
> > being sent, am able to send e-mails from the cobbler server and not seeing
> > any Exceptions in cobbler.log.
> >
> > ==KS %post==
> >
> > %post
> > (
> > $SNIPPET('log_ks_post')
> > echo "Post-Install section begins.."
> > sleep 15
> > $yum_config_stanza
> > $SNIPPET('post_install_network_config')
> > $SNIPPET('post_install_kernel_options')
> > $SNIPPET('cobbler_register')
> > $SNIPPET('post_anamon')
> > $SNIPPET('kickstart_done')
> > ) 2>&1 | tee /root/post-install.log
> > %end
> >
> >
> > ==install.log==
> > profile SL-6.3-x86_64 10.137.24.163 start 1367956120.14
> > profile SL-6.3-x86_64 10.137.24.163 stop 1367956688.33
> >
> > ==http access.log==
> > 10.137.24.163 - - [07/May/2013:15:58:08 -0400] "GET
> > /cblr/svc/op/trig/mode/post/profile/SL-6.3-x86_64 HTTP/1.0" 200 4 "-"
> > "Wget/1.12 (linux
> > -gnu)"
> >
> > ==cobbler.log==
> > Tue May 7 15:58:08 2013 - INFO | REMOTE run_install_triggers; user(?)
> > Tue May 7 15:58:08 2013 - DEBUG | running python triggers from
> > /var/lib/cobbler/triggers/install/post/*
> > Tue May 7 15:58:08 2013 - DEBUG | running python trigger
> > cobbler.modules.install_post_puppet
> > Tue May 7 15:58:08 2013 - DEBUG | running python trigger
> > cobbler.modules.install_post_report
> > Tue May 7 15:58:08 2013 - DEBUG | running python trigger
> > cobbler.modules.install_post_power
> > Tue May 7 15:58:08 2013 - DEBUG | running python trigger
> > cobbler.modules.install_post_log
> >
>
> This should be getting fired off from the cobblerd server as a post install
> trigger. You have all of the build_reporting* settings configured
> correctly? These are the default values:
>
> build_reporting_email: [root@localhost]
> build_reporting_enabled: 0
> build_reporting_sender: ''
> build_reporting_smtp_server: localhost
> build_reporting_subject: ''
> build_reporting_to_address: ''
_______________________________________________
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler
