[Pacemaker] Logging in syslog daemon can't be stopped
Grüninger, Andreas (LGL Extern)
Andreas.Grueninger at lgl.bwl.de
Wed Sep 26 09:55:21 CEST 2012
Works great.
This is the output in /var/adm/messages
.......
Sep 25 13:01:34 zd-sol-s2 pacemakerd[3343]: [ID 702911 daemon.notice] notice: crm_add_logfile: Additional logging available in /opt/ha/var/log/corosync.log
Sep 25 13:01:34 zd-sol-s2 stonith-ng[3625]: [ID 702911 daemon.notice] notice: crm_add_logfile: Additional logging available in /opt/ha/var/log/corosync.log
Sep 25 13:01:34 zd-sol-s2 attrd[3627]: [ID 702911 daemon.notice] notice: crm_add_logfile: Additional logging available in /opt/ha/var/log/corosync.log
Sep 25 13:01:34 zd-sol-s2 cib[3624]: [ID 702911 daemon.notice] notice: crm_add_logfile: Additional logging available in /opt/ha/var/log/corosync.log
Sep 25 13:01:34 zd-sol-s2 lrmd[3626]: [ID 702911 daemon.notice] notice: crm_add_logfile: Additional logging available in /opt/ha/var/log/corosync.log
Sep 25 13:01:34 zd-sol-s2 crmd[3629]: [ID 702911 daemon.notice] notice: crm_add_logfile: Additional logging available in /opt/ha/var/log/corosync.log
Sep 25 13:01:34 zd-sol-s2 pengine[3628]: [ID 702911 daemon.notice] notice: crm_add_logfile: Additional logging available in /opt/ha/var/log/corosync.log
.......
Thanks a lot
Andreas
-----Ursprüngliche Nachricht-----
Von: Andrew Beekhof [mailto:andrew at beekhof.net]
Gesendet: Dienstag, 25. September 2012 03:55
An: The Pacemaker cluster resource manager
Betreff: Re: [Pacemaker] Logging in syslog daemon can't be stopped
On Tue, Sep 25, 2012 at 9:21 AM, Larry Brigman <larry.brigman at gmail.com> wrote:
> On Mon, Sep 24, 2012 at 4:08 PM, Andrew Beekhof <andrew at beekhof.net> wrote:
>>
>> On Tue, Sep 25, 2012 at 6:00 AM, Grüninger, Andreas (LGL Extern)
>> <Andreas.Grueninger at lgl.bwl.de> wrote:
>> >
>> > When I use the corosync.conf attached below with logging to syslog
>> > disabled and loggong to file enabled all messages from corosync
>> > goes to the file.
>> > Pacemaker send the logging to both destinations and uses different
>> > formats. The messages sent to syslog are other messages than sent
>> > to the file.
>> > The syslog_facility is ignored and always "daemon.notice" is used.
>>
>> Weird, it looks like we want to do the right thing...
>>
>> Sep 25 09:06:30 [4092] pcmk-1 pacemakerd: ( corosync.c:580 )
>> info: read_config: User configured file based logging and explicitly
>> disabled syslog.
>>
>> Did you try setting syslog_facility to 'none' ?
>
>
> There is at least one if not more pacemaker processes that don't honor
> the facility. It always goes to daemon.
> crmd I know doesn't honor the config settings and always goes to daemon.
> pengine also logs
>
> I'm using version 1.1.5. on Linux.
I have a hard time believing that, all the daemons expect the lrmd use the same logging initialisation function.
In any case, I just verified that with
https://github.com/beekhof/pacemaker/commit/da8809c, all this works as expected.
>
>>
>> >
>> >
>> > System is Solaris 11U6
>> > Pacemaker 1.1.8 (Build: 34303f8)
>> > Corosync Cluster Engine ('2.0.1.136-5ce59-dirty')
>> >
>> > Andreas
>> >
>> > ############## /opt/ha/etc/corosync/corosync.conf
>> > # Please read the corosync.conf.5 manual page
>> > compatibility: whitetank
>> >
>> > totem {
>> > version: 2
>> > secauth: off
>> > # threads: 0
>> > crypto_cipher: none
>> > crypto_hash: none
>> > interface {
>> > ringnumber: 0
>> > bindnetaddr: 10.50.232.0 # hier am besten das Drbd
>> > Netz verwenden sonst machen alle corosync im subnetz im Cluster mit ;-)
>> > broadcast: yes
>> > mcastaddr: 226.94.1.1
>> > mcastport: 5405
>> > # ttl: 1
>> > }
>> > transport: udpu
>> > }
>> >
>> > logging {
>> > fileline: on
>> > function_name: on
>> > to_stderr: on
>> > to_logfile: on
>> > to_syslog: off
>> > syslog_facility: local6
>> > logfile: /opt/ha/var/log/corosync.log
>> > debug: off
>> > logfile_priority: error
>> > syslog_priority: error
>> > tags: enter|leave|trace
>> > timestamp: on
>> > # logger_subsys {
>> > # logfile: /opt/ha/var/log/corosync-msg.log
>> > # subsys: MSG
>> > # debug: off
>> > # tags: enter|trace4
>> > # }
>> > }
>> >
>> > quorum {
>> > # Enable and configure quorum subsystem (default: off)
>> > # see also corosync.conf.5 and votequorum.5
>> > provider: corosync_votequorum
>> > expected_votes: 2
>> > # two_node: 1
>> > }
>> >
>> > nodelist {
>> > node {
>> > ring0_addr: 10.50.232.54
>> > }
>> > }
>> >
>> > node {
>> > ring0_addr: 10.50.232.55
>> > }
>> > }
>> >
>> > ################################## Syslog entries in
>> > /var/adm/messages Sep 24 18:59:21 zd-sol-s2 pacemakerd[21226]: [ID
>> > 702911 daemon.notice]
>> > notice: crm_add_logfile: Additional logging available in
>> > /opt/ha/var/log/corosync.log Sep 24 18:59:21 zd-sol-s2
>> > pacemakerd[21226]: [ID 702911 daemon.notice]
>> > notice: main: Starting Pacemaker 1.1.8 (Build: 34303f8): ncurses
>> > libqb-logging libqb-ipc lha-fencing upstart systemd heartbeat
>> > corosync-native snmp libesmtp Sep 24 18:59:21 zd-sol-s2
>> > pacemakerd[21226]: [ID 702911 daemon.notice]
>> > notice: update_node_processes: 8052450 Node 171108407 now known as
>> > zd-sol-s2, was:
>> > Sep 24 18:59:21 zd-sol-s2 pacemakerd[21226]: [ID 702911
>> > daemon.notice]
>> > notice: update_node_processes: 80525a0 Node 171108406 now known as
>> > zd-sol-s1, was:
>> > Sep 24 18:59:21 zd-sol-s2 cib[21325]: [ID 702911 daemon.notice]
>> > notice: crm_add_logfile: Additional logging available in
>> > /opt/ha/var/log/corosync.log Sep 24 18:59:21 zd-sol-s2
>> > stonith-ng[21326]: [ID 702911 daemon.notice]
>> > notice: crm_add_logfile: Additional logging available in
>> > /opt/ha/var/log/corosync.log Sep 24 18:59:21 zd-sol-s2
>> > stonith-ng[21326]: [ID 702911 daemon.notice]
>> > notice: crm_cluster_connect: Connecting to cluster infrastructure:
>> > corosync Sep 24 18:59:21 zd-sol-s2 lrmd[21327]: [ID 702911
>> > daemon.notice]
>> > notice: crm_add_logfile: Additional logging available in
>> > /opt/ha/var/log/corosync.log Sep 24 18:59:21 zd-sol-s2
>> > attrd[21328]: [ID 702911 daemon.notice]
>> > notice: crm_add_logfile: Additional logging available in
>> > /opt/ha/var/log/corosync.log Sep 24 18:59:21 zd-sol-s2
>> > attrd[21328]: [ID 702911 daemon.notice]
>> > notice: crm_cluster_connect: Connecting to cluster infrastructure:
>> > corosync Sep 24 18:59:21 zd-sol-s2 pengine[21329]: [ID 702911
>> > daemon.notice]
>> > notice: crm_add_logfile: Additional logging available in
>> > /opt/ha/var/log/corosync.log Sep 24 18:59:21 zd-sol-s2 crmd[21330]:
>> > [ID 702911 daemon.notice]
>> > notice: crm_add_logfile: Additional logging available in
>> > /opt/ha/var/log/corosync.log Sep 24 18:59:21 zd-sol-s2 crmd[21330]:
>> > [ID 702911 daemon.notice]
>> > notice: main: CRM Git Version: 34303f8 Sep 24 18:59:21 zd-sol-s2
>> > attrd[21328]: [ID 702911 daemon.notice]
>> > notice: main: Starting mainloop...
>> > Sep 24 18:59:21 zd-sol-s2 cib[21325]: [ID 702911 daemon.notice]
>> > notice: crm_cluster_connect: Connecting to cluster infrastructure:
>> > corosync Sep 24 18:59:22 zd-sol-s2 stonith-ng[21326]: [ID 702911
>> > daemon.notice]
>> > notice: setup_cib: Watching for stonith topology changes Sep 24
>> > 18:59:22 zd-sol-s2 crmd[21330]: [ID 702911 daemon.notice]
>> > notice: crm_cluster_connect: Connecting to cluster infrastructure:
>> > corosync Sep 24 18:59:22 zd-sol-s2 crmd[21330]: [ID 702911
>> > daemon.notice]
>> > notice: init_quorum_connection: Quorum acquired Sep 24 18:59:23
>> > zd-sol-s2 crmd[21330]: [ID 702911 daemon.notice]
>> > notice: corosync_node_name: Inferred node name 'zd-sol-s1' for
>> > nodeid
>> > 171108406 from DNS
>> > Sep 24 18:59:23 zd-sol-s2 crmd[21330]: [ID 702911 daemon.notice]
>> > notice: crm_update_peer_state: pcmk_quorum_notification: Node
>> > zd-sol-s1[171108406] - state is now member Sep 24 18:59:23
>> > zd-sol-s2 crmd[21330]: [ID 702911 daemon.notice]
>> > notice: crm_update_peer_state: pcmk_quorum_notification: Node
>> > zd-sol-s2[171108407] - state is now member Sep 24 18:59:23
>> > zd-sol-s2 crmd[21330]: [ID 702911 daemon.notice]
>> > notice: do_started: The local CRM is operational Sep 24 18:59:25
>> > zd-sol-s2 crmd[21330]: [ID 702911 daemon.notice]
>> > notice: do_state_transition: State transition S_PENDING -> S_NOT_DC
>> > [ input=I_NOT_DC cause=C_HA_MESSAGE
>> > origin=do_cl_join_finalize_respond ] Sep 24 18:59:25 zd-sol-s2
>> > attrd[21328]: [ID 702911 daemon.notice]
>> > notice: attrd_local_callback: Sending full refresh (origin=crmd)
>> > Sep 24 18:59:26 zd-sol-s2 crmd[21330]: [ID 702911 daemon.notice]
>> > notice: process_lrm_event: LRM operation zone_zd-sol-s25_monitor_0
>> > (call=6, rc=7, cib-update=8, confirmed=true) not running Sep 24
>> > 18:59:26 zd-sol-s2 attrd[21328]: [ID 702911 daemon.notice]
>> > notice: attrd_trigger_update: Sending flush op to all hosts for:
>> > probe_complete (true)
>> > Sep 24 18:59:26 zd-sol-s2 attrd[21328]: [ID 702911 daemon.warning]
>> > warning: attrd_cib_callback: Update shutdown=(null) failed: No such
>> > device or address Sep 24 18:59:26 zd-sol-s2 attrd[21328]: [ID
>> > 702911 daemon.warning]
>> > warning: attrd_cib_callback: Update terminate=(null) failed: No
>> > such device or address Sep 24 18:59:26 zd-sol-s2 attrd[21328]: [ID
>> > 702911 daemon.notice]
>> > notice: attrd_perform_update: Sent update 6: probe_complete=true
>> > Sep 24 18:59:50 zd-sol-s2 pacemakerd[21226]: [ID 702911
>> > daemon.notice]
>> > notice: pcmk_ipc_dispatch: Shutting down in responce to ticket
>> > quit-pacemakerd-1348505990-0 (main) Sep 24 18:59:50 zd-sol-s2
>> > pacemakerd[21226]: [ID 702911 daemon.notice]
>> > notice: pcmk_shutdown_worker: Shuting down Pacemaker Sep 24
>> > 18:59:50 zd-sol-s2 pacemakerd[21226]: [ID 702911 daemon.notice]
>> > notice: stop_child: Stopping crmd: Sent -15 to process 21330 Sep 24
>> > 18:59:50 zd-sol-s2 crmd[21330]: [ID 702911 daemon.notice]
>> > notice: crm_shutdown: Requesting shutdown, upper limit is 1200000ms
>> > Sep 24 18:59:50 zd-sol-s2 attrd[21328]: [ID 702911 daemon.notice]
>> > notice: attrd_ais_dispatch: Update relayed from zd-sol-s1 Sep 24
>> > 18:59:50 zd-sol-s2 attrd[21328]: [ID 702911 daemon.notice]
>> > notice: attrd_trigger_update: Sending flush op to all hosts for:
>> > shutdown
>> > (1348505990)
>> > Sep 24 18:59:50 zd-sol-s2 attrd[21328]: [ID 702911 daemon.notice]
>> > notice: attrd_perform_update: Sent update 9: shutdown=1348505990
>> > Sep 24 18:59:50 zd-sol-s2 crmd[21330]: [ID 702911 daemon.notice]
>> > notice: do_state_transition: State transition S_NOT_DC ->
>> > S_STOPPING [ input=I_STOP cause=C_HA_MESSAGE origin=route_message ]
>> > Sep 24 18:59:50 zd-sol-s2 crmd[21330]: [ID 702911 daemon.notice]
>> > notice: terminate_cs_connection: Disconnecting from Corosync Sep 24
>> > 18:59:50 zd-sol-s2 cib[21325]: [ID 702911 daemon.warning]
>> > warning: do_local_notify: A-Sync reply to crmd failed: No message
>> > of desired type Sep 24 18:59:50 zd-sol-s2 pacemakerd[21226]: [ID
>> > 702911 daemon.notice]
>> > notice: stop_child: Stopping pengine: Sent -15 to process 21329 Sep
>> > 24 18:59:50 zd-sol-s2 pacemakerd[21226]: [ID 702911 daemon.notice]
>> > notice: stop_child: Stopping attrd: Sent -15 to process 21328 Sep
>> > 24 18:59:50 zd-sol-s2 attrd[21328]: [ID 702911 daemon.notice]
>> > notice: main: Exiting...
>> > Sep 24 18:59:50 zd-sol-s2 pacemakerd[21226]: [ID 702911
>> > daemon.notice]
>> > notice: stop_child: Stopping lrmd: Sent -15 to process 21327 Sep 24
>> > 18:59:50 zd-sol-s2 pacemakerd[21226]: [ID 702911 daemon.notice]
>> > notice: stop_child: Stopping stonith-ng: Sent -15 to process 21326
>> > Sep 24 18:59:52 zd-sol-s2 pacemakerd[21226]: [ID 702911
>> > daemon.notice]
>> > notice: pcmk_child_exit: Child process stonith-ng terminated with
>> > signal 11 (pid=21326, core=128) Sep 24 18:59:52 zd-sol-s2
>> > pacemakerd[21226]: [ID 702911 daemon.notice]
>> > notice: stop_child: Stopping cib: Sent -15 to process 21325 Sep 24
>> > 18:59:52 zd-sol-s2 cib[21325]: [ID 702911 daemon.notice]
>> > notice: terminate_cs_connection: Disconnecting from Corosync Sep 24
>> > 18:59:52 zd-sol-s2 pacemakerd[21226]: [ID 702911 daemon.notice]
>> > notice: pcmk_shutdown_worker: Shutdown complete
>> > ###########################
>> >
>> > _______________________________________________
>> > Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
>> > http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>> >
>> > Project Home: http://www.clusterlabs.org Getting started:
>> > http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> > Bugs: http://bugs.clusterlabs.org
>>
>> _______________________________________________
>> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>>
>> Project Home: http://www.clusterlabs.org Getting started:
>> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> Bugs: http://bugs.clusterlabs.org
>
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org Getting started:
> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>
_______________________________________________
Pacemaker mailing list: Pacemaker at oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
More information about the Pacemaker
mailing list