Actually (I guess) pacemaker does not write to /var/log/messages, but to the syslog socket. From there it depends on syslogd's configuration where each message is written.
-----Original Message----- From: Users <users-boun...@clusterlabs.org> On Behalf Of S Sathish S via Users Sent: Friday, June 23, 2023 3:57 PM To: 'users@clusterlabs.org' <users@clusterlabs.org> Cc: S Sathish S <s.s.sath...@ericsson.com> Subject: [EXT] [ClusterLabs] Pacemaker logs written on message which is not expected as per configuration Hi Team, The pacemaker logs is written in both '/var/log/messages' and '/var/log/pacemaker/pacemaker.log'. Could you please help us for not write pacemaker processes in /var/log/messages? Even corosync configuration we have set to_syslog: no. Attached the corosync.conf file. Pacemaker 2.1.6 [root@node1 username]# tail -f /var/log/messages Jun 23 13:45:38 node1 ESAFMA_RA(ESAFMA_node1)[3593054]: INFO: <test1> component is running with 10502 number Jun 23 13:45:38 node1 HealthMonitor_RA(HEALTHMONITOR_node1)[3593055]: INFO: Health Monitor component is running with 3046 number Jun 23 13:45:38 node1 ESAPMA_RA(ESAPMA_OCC)[3593056]: INFO: <test2> component is running with 10902 number Jun 23 13:45:38 node1 HP_AMSD_RA(HP_AMSD_node1)[3593057]: INFO: <test3> component is running with 2540 number Jun 23 13:45:38 node1 HP_SMAD_RA(HP_SMAD_node1)[3593050]: INFO: <test4> component is running with 2536 number Jun 23 13:45:38 node1 SSMAGENT_RA(SSMAGENT_node1)[3593068]: INFO: <test5> component is running with 2771 number Jun 23 13:45:38 node1 HazelCast_RA(HAZELCAST_node1)[3593059]: INFO: <test6> component is running with 13355 number Jun 23 13:45:38 node1 HP_SMADREV_RA(HP_SMADREV_node1)[3593062]: INFO: <test8> component is running with 2735 number Jun 23 13:45:38 node1 ESAMA_RA(ESAMA_node1)[3593065]: INFO: <test9> component is running with 9572 number Jun 23 13:45:38 node1 MANAGER_RA(MANAGER_OCC)[3593071]: INFO: <test10> component is running with 10069 number cat /etc/corosync/corosync.conf totem { version: 2 cluster_name: OCC transport: knet crypto_cipher: aes256 crypto_hash: sha256 cluster_uuid: 20572748740a4ac2a7bcc3a3bb6889e9 } nodelist { node { ring0_addr: node1 name: node1 nodeid: 1 } } quorum { provider: corosync_votequorum } logging { to_logfile: yes logfile: /var/log/cluster/corosync.log to_syslog: no timestamp: on } Thanks and Regards, S Sathish S _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/