corosync syslog

[jms1000]

Hallo,

seit einem der letzten Updates (v 5.x) habe ich jede Menge Meldungen vom corosysnc im Syslog. Kann man die auch wieder abschalten? Nervt etwas ...

LG Jörg

 

[Alwin]

Abschalten? Was meldet corosync den?

 

[jms1000]

naja, vielleicht wenigstens die debug meldungen?

Beispiel:

Sep 28 09:06:32 prx1 corosync[2506]: [QUORUM] sending quorum notification to 0x56166bb86b50, length = 64
Sep 28 09:06:32 prx1 corosync[2506]: debug [QB ] HUP conn (2506-19295-24)
Sep 28 09:06:32 prx1 corosync[2506]: debug [QB ] qb_ipcs_disconnect(2506-19295-24) state:2
Sep 28 09:06:32 prx1 corosync[2506]: debug [MAIN ] cs_ipcs_connection_closed()
Sep 28 09:06:32 prx1 corosync[2506]: debug [MAIN ] cs_ipcs_connection_destroyed()
Sep 28 09:06:32 prx1 corosync[2506]: debug [QB ] Free'ing ringbuffer: /dev/shm/qb-cfg-response-2506-19295-24-header
Sep 28 09:06:32 prx1 corosync[2506]: debug [QB ] Free'ing ringbuffer: /dev/shm/qb-cfg-event-2506-19295-24-header
Sep 28 09:06:32 prx1 corosync[2506]: debug [QB ] Free'ing ringbuffer: /dev/shm/qb-cfg-request-2506-19295-24-header
Sep 28 09:06:32 prx1 corosync[2506]: debug [QB ] HUP conn (2506-19295-25)
Sep 28 09:06:32 prx1 corosync[2506]: debug [QB ] qb_ipcs_disconnect(2506-19295-25) state:2
Sep 28 09:06:32 prx1 corosync[2506]: debug [MAIN ] cs_ipcs_connection_closed()
Sep 28 09:06:32 prx1 corosync[2506]: debug [MAIN ] cs_ipcs_connection_destroyed()
Sep 28 09:06:32 prx1 corosync[2506]: debug [QB ] Free'ing ringbuffer: /dev/shm/qb-votequorum-response-2506-19295-25-header
Sep 28 09:06:32 prx1 corosync[2506]: debug [QB ] Free'ing ringbuffer: /dev/shm/qb-votequorum-event-2506-19295-25-header
Sep 28 09:06:32 prx1 corosync[2506]: debug [QB ] Free'ing ringbuffer: /dev/shm/qb-votequorum-request-2506-19295-25-header
Sep 28 09:06:32 prx1 corosync[2506]: [VOTEQ ] got getinfo request on 0x56166be8aa80 for node 1
Sep 28 09:06:32 prx1 corosync[2506]: [VOTEQ ] getinfo response error: 1
Sep 28 09:06:32 prx1 corosync[2506]: [VOTEQ ] got getinfo request on 0x56166be8aa80 for node 2
Sep 28 09:06:32 prx1 corosync[2506]: [VOTEQ ] getinfo response error: 1
Sep 28 09:06:32 prx1 corosync[2506]: [VOTEQ ] got getinfo request on 0x56166be8aa80 for node 3
Sep 28 09:06:32 prx1 corosync[2506]: [VOTEQ ] getinfo response error: 1
Sep 28 09:06:32 prx1 corosync[2506]: [VOTEQ ] got getinfo request on 0x56166be8aa80 for node 4

 

[Alwin]

logging {
  debug: off
  to_syslog: yes
}

Zum abschalten von Debug Nachrichten steht folgendes in der corosync.conf (/etc/pve).

Sep 28 09:06:32 prx1 corosync[2506]: [VOTEQ ] got getinfo request on 0x56166be8aa80 for node 1
Sep 28 09:06:32 prx1 corosync[2506]: [VOTEQ ] getinfo response error: 1
Sep 28 09:06:32 prx1 corosync[2506]: [VOTEQ ] got getinfo request on 0x56166be8aa80 for node 2
Sep 28 09:06:32 prx1 corosync[2506]: [VOTEQ ] getinfo response error: 1
Sep 28 09:06:32 prx1 corosync[2506]: [VOTEQ ] got getinfo request on 0x56166be8aa80 for node 3
Sep 28 09:06:32 prx1 corosync[2506]: [VOTEQ ] getinfo response error: 1
Sep 28 09:06:32 prx1 corosync[2506]: [VOTEQ ] got getinfo request on 0x56166be8aa80 for node 4

Sieht der 'pvecm status' OK aus?

 

[jms1000]

ok, die debug-meldungen sind jetzt weg ...

pvecm status sieht auf allen nodes ok aus, funktioniert auch alles soweit ich sehen kann.