[ClusterLabs] "After = syslog.service" it is not working?

飯田 雄介 iidayuus at intellilink.co.jp
Thu Jan 28 23:27:53 EST 2016


Hi, Ken

I have to get the log.
shutdown the -r now ran to "03:00:22".
rsyslog also "03:00:22" to receive a TERM appears to have stopped.

Regards, Yusuke
> -----Original Message-----
> From: Ken Gaillot [mailto:kgaillot at redhat.com]
> Sent: Friday, January 29, 2016 12:16 AM
> To: users at clusterlabs.org
> Subject: Re: [ClusterLabs] "After = syslog.service" it is not working?
> 
> On 01/28/2016 12:48 AM, 飯田 雄介 wrote:
> > Hi, All
> >
> > I am building a cluster in the following environments.
> > RHEL7.2
> > Pacemaker-1.1.14
> >
> > The OS while it is running the Pacemaker was allowed to shutdown.
> > Logs at this time Pacemaker in the stop was not output to the syslog.
> >
> > This "After = syslog.service" does not work is set to start-up script, it
> seems pacemaker and rsyslog is stopped at the same time.
> >
> > Because I think it's rsyslog.service In RHEL7, whether this setting should
> not be the "After = rsyslog.service"?
> >
> > Regards, Yusuke
> 
> The "After = syslog.service" line neither helps nor hurts, and we should just
> take it out.
> 
> For a long time (and certainly in RHEL 7's systemd version 219), systemd
> automatically orders the system log to start before and stop after other services,
> so I don't think that's the cause of your problem.
> 
> I'm not sure what would cause that behavior; can you post the messages that
> are logged once shutdown is initiated?
> 
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> http://clusterlabs.org/mailman/listinfo/users
> 
> Project Home: http://www.clusterlabs.org Getting started:
> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pcmk_report.tar.bz2
Type: application/octet-stream
Size: 53287 bytes
Desc: pcmk_report.tar.bz2
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20160129/ef29f767/attachment-0003.obj>


More information about the Users mailing list