Re: [PVE-User] Adding a cluster node breaks whole cluster

[Sten Aus]

Are there any corosync/cman related messages in the syslog?

Yes, It's from 7th April, but anyway there are a lot of these messages and they're at the same timestamp. Adding a new node (which has not been in cluster)

Apr 07 18:00:42 corosync [TOTEM ] A processor joined or left the membership and a new membership was formed.

Apr 07 18:00:42 corosync [CMAN  ] quorum regained, resuming activity

Apr 07 18:00:42 corosync [QUORUM] Members[1]: 2
Apr 07 18:00:42 corosync [CMAN  ] quorum lost, blocking activity

Apr 07 18:00:42 corosync [QUORUM] Members[1]: 2
Apr 07 18:00:42 corosync [QUORUM] Members[2]: 2 4
Apr 07 18:00:42 corosync [QUORUM] Members[2]: 2 4
Apr 07 18:00:42 corosync [QUORUM] Members[3]: 2 4 6
Apr 07 18:00:42 corosync [QUORUM] Members[3]: 2 4 6
Apr 07 18:00:42 corosync [QUORUM] Members[4]: 2 4 5 6
Apr 07 18:00:42 corosync [QUORUM] Members[4]: 2 4 5 6
Apr 07 18:00:42 corosync [QUORUM] Members[5]: 2 3 4 5 6
Apr 07 18:00:42 corosync [QUORUM] Members[5]: 2 3 4 5 6
Apr 07 18:00:42 corosync [QUORUM] Members[6]: 2 3 4 5 6 7
Apr 07 18:00:42 corosync [QUORUM] Members[6]: 2 3 4 5 6 7
Apr 07 18:00:42 corosync [CMAN  ] quorum regained, resuming activity

Apr 07 18:00:42 corosync [QUORUM] Members[7]: 2 3 4 5 6 7 13
Apr 07 18:00:42 corosync [QUORUM] Members[7]: 2 3 4 5 6 7 13
Apr 07 18:00:42 corosync [QUORUM] Members[8]: 2 3 4 5 6 7 13 14
Apr 07 18:00:42 corosync [QUORUM] Members[8]: 2 3 4 5 6 7 13 14
Apr 07 18:00:42 corosync [QUORUM] Members[9]: 2 3 4 5 6 7 9 13 14
Apr 07 18:00:42 corosync [QUORUM] Members[9]: 2 3 4 5 6 7 9 13 14
Apr 07 18:00:42 corosync [QUORUM] Members[10]: 2 3 4 5 6 7 8 9 13 14
Apr 07 18:00:42 corosync [QUORUM] Members[10]: 2 3 4 5 6 7 8 9 13 14
Apr 07 18:00:42 corosync [QUORUM] Members[11]: 2 3 4 5 6 7 8 9 10 13 14
Apr 07 18:00:42 corosync [QUORUM] Members[11]: 2 3 4 5 6 7 8 9 10 13 14

Apr 07 18:00:42 corosync [QUORUM] This node is within the primary component and will provide service. Apr 07 18:00:42 corosync [QUORUM] This node is within the non-primary component and will NOT provide any services. Apr 07 18:00:42 corosync [QUORUM] This node is within the primary component and will provide service. Apr 07 18:00:42 corosync [QUORUM] Members[12]: 2 3 4 5 6 7 8 9 10 11 13 14 Apr 07 18:00:42 corosync [QUORUM] Members[12]: 2 3 4 5 6 7 8 9 10 11 13 14 Apr 07 18:00:42 corosync [QUORUM] Members[13]: 2 3 4 5 6 7 8 9 10 11 12 13 14 Apr 07 18:00:42 corosync [QUORUM] Members[13]: 2 3 4 5 6 7 8 9 10 11 12 13 14 Apr 07 18:00:42 corosync [QUORUM] Members[14]: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 Apr 07 18:00:42 corosync [QUORUM] Members[14]: 1 2 3 4 5 6 7 8 9 10 11 12 13 14

Here's the log of re-adding a cluster node (which prior worked in the cluster):

Apr 9 17:50:04 nohutaja pveproxy[6393]: problem with client 192.168.15.17; rsa_padding_check_pkcs1_type_1: block type is not 01 Apr 9 17:50:05 nohutaja pveproxy[6394]: EV: error in callback (ignoring): Can't call method "push_write" on an undefined value at /usr/share/perl5/PVE/HTTPServer.pm line 295. Apr 9 17:50:06 nohutaja pveproxy[6393]: problem with client 192.168.15.17; rsa_padding_check_pkcs1_type_1: block type is not 01 Apr 9 17:50:07 nohutaja pveproxy[6393]: EV: error in callback (ignoring): Can't call method "push_write" on an undefined value at /usr/share/perl5/PVE/HTTPServer.pm line 295. Apr 9 17:50:08 nohutaja pveproxy[6395]: problem with client 192.168.15.17; rsa_padding_check_pkcs1_type_1: block type is not 01 Apr 9 17:50:09 nohutaja pveproxy[6393]: EV: error in callback (ignoring): Can't call method "push_write" on an undefined value at /usr/share/perl5/PVE/HTTPServer.pm line 295. Apr 9 17:50:10 nohutaja pveproxy[6394]: problem with client 192.168.15.17; rsa_padding_check_pkcs1_type_1: block type is not 01 Apr 9 17:50:11 nohutaja pveproxy[6395]: EV: error in callback (ignoring): Can't call method "push_write" on an undefined value at /usr/share/perl5/PVE/HTTPServer.pm line 295.

Apr 09 17:48:18 corosync [TOTEM ] got commit token
Apr 09 17:48:18 corosync [TOTEM ] Sending initial ORF token

Apr 09 17:48:18 corosync [TOTEM ] install seq 0 aru 0 high seq received 0

Apr 09 17:48:18 corosync [TOTEM ] install seq 0 aru 0 high seq received 0

Apr 09 17:48:18 corosync [TOTEM ] install seq 0 aru 0 high seq received 0

Apr 09 17:48:18 corosync [TOTEM ] install seq 0 aru 0 high seq received 0

Apr 09 17:48:18 corosync [TOTEM ] Resetting old ring state
Apr 09 17:48:18 corosync [TOTEM ] recovery to regular 1-0
Apr 09 17:48:18 corosync [CLM   ] CLM CONFIGURATION CHANGE
Apr 09 17:48:18 corosync [CLM   ] New Configuration:
Apr 09 17:48:18 corosync [CLM   ] Members Left:
Apr 09 17:48:18 corosync [CLM   ] Members Joined:
Apr 09 17:48:18 corosync [EVT   ] Evt conf change 1
Apr 09 17:48:18 corosync [EVT   ] m 0, j 0 l 0
Apr 09 17:48:18 corosync [LCK   ] [DEBUG]: lck_confchg_fn
Apr 09 17:48:18 corosync [MSG   ] [DEBUG]: msg_confchg_fn

Apr 09 17:48:18 corosync [TOTEM ] waiting_trans_ack changed to 1
Apr 09 17:48:18 corosync [CLM   ] CLM CONFIGURATION CHANGE
Apr 09 17:48:18 corosync [CLM   ] New Configuration:
Apr 09 17:48:18 corosync [CLM   ]     r(0) ip(192.168.15.25)
Apr 09 17:48:18 corosync [CLM   ] Members Left:
Apr 09 17:48:18 corosync [CLM   ] Members Joined:
Apr 09 17:48:18 corosync [CLM   ]     r(0) ip(192.168.15.25)
Apr 09 17:48:18 corosync [EVT   ] Evt conf change 0
Apr 09 17:48:18 corosync [EVT   ] m 1, j 1 l 0
Apr 09 17:48:18 corosync [LCK   ] [DEBUG]: lck_confchg_fn
Apr 09 17:48:18 corosync [MSG   ] [DEBUG]: msg_confchg_fn

Apr 09 17:48:18 corosync [CMAN  ] ais: last memb_count = 0, current = 1

Apr 09 17:48:18 corosync [TOTEM ] entering OPERATIONAL state.

Apr 09 17:48:18 corosync [CMAN  ] memb: Message on port 0 is 5
Apr 09 17:48:18 corosync [CMAN  ] memb: got TRANSITION from node 12

Apr 09 17:48:18 corosync [QUORUM] Members[1]: 12

Apr 09 17:48:18 corosync [QUORUM] Members[1]: 12

Apr 09 17:48:18 corosync [SYNC  ] confchg entries 1
Apr 09 17:48:18 corosync [SYNC  ] Barrier Start Received From 12

Apr 09 17:48:18 corosync [SYNC  ] Synchronization barrier completed

Apr 09 17:48:18 corosync [CLM   ] got nodejoin message 192.168.15.25
Apr 09 17:48:18 corosync [SYNC  ] confchg entries 1
Apr 09 17:48:18 corosync [SYNC  ] Barrier Start Received From 12

Apr 09 17:48:18 corosync [SYNC  ] Synchronization barrier completed

Apr 09 17:48:18 corosync [SYNC  ] confchg entries 1
Apr 09 17:48:18 corosync [SYNC  ] Barrier Start Received From 12

Apr 09 17:48:18 corosync [SYNC  ] Synchronization barrier completed

Apr 09 17:48:18 corosync [SYNC  ] confchg entries 1
Apr 09 17:48:18 corosync [SYNC  ] Barrier Start Received From 12

Apr 09 17:48:18 corosync [SYNC  ] Synchronization barrier completed

Apr 09 17:48:18 corosync [EVT   ] Evt synchronize initialization
Apr 09 17:48:18 corosync [EVT   ] My node ID r(0) ip(192.168.15.25)
Apr 09 17:48:18 corosync [EVT   ] Process Evt synchronization
Apr 09 17:48:18 corosync [EVT   ] Send max event ID updates
Apr 09 17:48:18 corosync [EVT   ] Process Evt synchronization
Apr 09 17:48:18 corosync [EVT   ] Send open count updates
Apr 09 17:48:18 corosync [EVT   ] DONE Sending open counts
Apr 09 17:48:18 corosync [EVT   ] Remote channel operation request
Apr 09 17:48:18 corosync [EVT   ] my node ID: 0xc

Apr 09 17:48:18 corosync [EVT   ] Process Evt synchronization
Apr 09 17:48:18 corosync [EVT   ] DONE Sending retained events
Apr 09 17:48:18 corosync [EVT   ] Remote channel operation request
Apr 09 17:48:18 corosync [EVT   ] my node ID: 0xc

Apr 09 17:48:18 corosync [EVT   ] Process Evt synchronization
Apr 09 17:48:18 corosync [EVT   ] Recovery complete
Apr 09 17:48:18 corosync [SYNC  ] confchg entries 1
Apr 09 17:48:18 corosync [SYNC  ] Barrier Start Received From 12

Apr 09 17:48:18 corosync [SYNC  ] Synchronization barrier completed
Apr 09 17:48:18 corosync [EVT   ] Evt synchronize activation

Apr 09 17:48:18 corosync [SYNC  ] confchg entries 1
Apr 09 17:48:18 corosync [SYNC  ] Barrier Start Received From 12

Apr 09 17:48:18 corosync [SYNC  ] Synchronization barrier completed

Apr 09 17:48:18 corosync [LCK   ] [DEBUG]: lck_sync_init

Apr 09 17:48:18 corosync [LCK   ] [DEBUG]: lck_sync_process

Apr 09 17:48:18 corosync [LCK   ] [DEBUG]: lck_sync_activate
Apr 09 17:48:18 corosync [LCK   ] [DEBUG]: lck_sync_resource_free

Apr 09 17:48:18 corosync [LCK   ] [DEBUG]:     global_lock_count = 0
Apr 09 17:48:18 corosync [MSG   ] [DEBUG]: msg_sync_init
Apr 09 17:48:18 corosync [MSG   ] [DEBUG]: msg_sync_queue_enter
Apr 09 17:48:18 corosync [MSG   ] [DEBUG]: msg_sync_process
Apr 09 17:48:18 corosync [MSG   ] [DEBUG]: msg_sync_queue_iterate
Apr 09 17:48:18 corosync [MSG   ] [DEBUG]: msg_sync_group_enter
Apr 09 17:48:18 corosync [MSG   ] [DEBUG]: msg_sync_process
Apr 09 17:48:18 corosync [MSG   ] [DEBUG]: msg_sync_group_iterate
Apr 09 17:48:18 corosync [MSG   ] [DEBUG]: msg_sync_reply_enter
Apr 09 17:48:18 corosync [MSG   ] [DEBUG]: msg_sync_process
Apr 09 17:48:18 corosync [MSG   ] [DEBUG]: msg_sync_reply_iterate

Apr 09 17:48:18 corosync [MSG   ] [DEBUG]: msg_sync_activate
Apr 09 17:48:18 corosync [MSG   ] [DEBUG]: msg_sync_queue_free
Apr 09 17:48:18 corosync [MSG   ] [DEBUG]: msg_sync_group_free
Apr 09 17:48:18 corosync [MSG   ] [DEBUG]: msg_sync_reply_free
Apr 09 17:48:18 corosync [MSG   ] [DEBUG]: msg_queue_timer_restart

Apr 09 17:48:18 corosync [TOTEM ] waiting_trans_ack changed to 0

Apr 09 17:48:18 corosync [QUORUM] lib_init_fn: conn=0x866550
Apr 09 17:48:18 corosync [QUORUM] got trackstart request on 0x866550
Apr 09 17:48:18 corosync [QUORUM] sending initial status to 0x866550

Apr 09 17:48:18 corosync [CONFDB] lib_init_fn: conn=0x86b6f0

Apr 09 17:48:20 corosync [CMAN  ] daemon: read 0 bytes from fd 25
Apr 09 17:48:20 corosync [CMAN  ] daemon: Freed 0 queued messages

Apr 09 17:48:20 corosync [CONFDB] lib_init_fn: conn=0x87ac50
Apr 09 17:48:20 corosync [CONFDB] exit_fn for conn=0x87ac50
Apr 09 17:48:20 corosync [CMAN  ] daemon: read 20 bytes from fd 26
Apr 09 17:48:20 corosync [CMAN  ] daemon: client command is 7
Apr 09 17:48:20 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:20 corosync [CMAN  ] memb: command to process is 7

Apr 09 17:48:20 corosync [CMAN  ] memb: get_all_members: retlen = 5720
Apr 09 17:48:20 corosync [CMAN  ] memb: command return code is 13

Apr 09 17:48:20 corosync [CMAN  ] daemon: sending reply 40000007 to fd 26
Apr 09 17:48:20 corosync [CMAN  ] daemon: read 0 bytes from fd 26
Apr 09 17:48:20 corosync [CMAN  ] daemon: Freed 0 queued messages
Apr 09 17:48:22 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:22 corosync [CMAN  ] daemon: client command is 91
Apr 09 17:48:22 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:22 corosync [CMAN  ] memb: command to process is 91
Apr 09 17:48:22 corosync [CMAN  ] memb: command return code is 0

Apr 09 17:48:22 corosync [CMAN  ] daemon: sending reply 40000091 to fd 25
Apr 09 17:48:22 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:22 corosync [CMAN  ] daemon: client command is 9
Apr 09 17:48:22 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:22 corosync [CMAN  ] memb: command to process is 9
Apr 09 17:48:22 corosync [CMAN  ] memb: command return code is 0

Apr 09 17:48:22 corosync [CMAN  ] daemon: sending reply 40000009 to fd 25
Apr 09 17:48:22 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:22 corosync [CMAN  ] daemon: client command is 92
Apr 09 17:48:22 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:22 corosync [CMAN  ] memb: command to process is 92

Apr 09 17:48:22 corosync [CMAN  ] memb: command return code is 0

Apr 09 17:48:22 corosync [CMAN  ] daemon: sending reply 40000092 to fd 25
Apr 09 17:48:22 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:22 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:22 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:22 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:22 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:22 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:22 corosync [CMAN  ] daemon: client command is 90
Apr 09 17:48:22 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:22 corosync [CMAN  ] memb: command to process is 90
Apr 09 17:48:22 corosync [CMAN  ] memb: command return code is -2

Apr 09 17:48:22 corosync [CMAN  ] daemon: sending reply 40000090 to fd 25
Apr 09 17:48:22 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:22 corosync [CMAN  ] daemon: client command is d
Apr 09 17:48:22 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:22 corosync [CMAN  ] memb: command to process is d
Apr 09 17:48:22 corosync [CMAN  ] memb: command return code is 1

Apr 09 17:48:22 corosync [CMAN  ] daemon: sending reply 4000000d to fd 25
Apr 09 17:48:22 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:22 corosync [CMAN  ] daemon: client command is 90
Apr 09 17:48:22 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:22 corosync [CMAN  ] memb: command to process is 90
Apr 09 17:48:22 corosync [CMAN  ] memb: command return code is 0

Apr 09 17:48:22 corosync [CMAN  ] daemon: sending reply 40000090 to fd 25
Apr 09 17:48:22 corosync [CMAN  ] daemon: read 0 bytes from fd 25
Apr 09 17:48:22 corosync [CMAN  ] daemon: Freed 0 queued messages

Apr 09 17:48:22 corosync [CONFDB] lib_init_fn: conn=0x879df0
Apr 09 17:48:22 corosync [CONFDB] exit_fn for conn=0x879df0

Apr 09 17:48:22 corosync [CONFDB] lib_init_fn: conn=0x87fe80
Apr 09 17:48:22 corosync [CONFDB] exit_fn for conn=0x87fe80

Apr 09 17:48:22 corosync [CONFDB] lib_init_fn: conn=0x879df0
Apr 09 17:48:22 corosync [CONFDB] exit_fn for conn=0x879df0
Apr 09 17:48:22 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:22 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:22 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:22 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:22 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:23 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:23 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:23 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:23 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:23 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:24 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:24 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:24 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:24 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:24 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:25 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:25 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:25 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:25 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:25 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:26 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:26 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:26 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:26 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:26 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:27 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:27 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:27 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:27 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:27 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:28 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:28 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:28 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:28 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:28 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:29 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:29 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:29 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:29 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:29 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:30 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:30 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:30 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:30 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:30 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:31 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:31 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:31 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:31 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:31 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:32 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:32 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:32 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:32 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:32 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:33 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:33 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:33 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:33 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:33 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:34 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:34 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:34 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:34 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:34 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:35 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:35 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:35 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:35 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:35 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:36 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:36 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:36 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:36 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:36 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:37 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:37 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:37 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:37 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:37 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:38 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:38 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:38 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:38 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:38 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:39 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:39 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:39 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:39 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:39 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:40 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:40 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:40 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:40 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:40 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:41 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:41 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:41 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:41 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:41 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:42 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:42 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:42 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:42 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:42 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:43 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:43 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:43 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:43 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:43 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:44 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:44 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:44 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:44 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:44 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:45 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:45 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:45 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:45 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:45 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:46 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:46 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:46 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:46 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:46 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:47 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:47 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:47 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:47 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:47 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:48 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:48 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:48 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:48 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:48 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:49 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:49 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:49 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:49 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:49 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:50 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:50 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:50 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:50 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:50 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:51 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:51 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:51 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:51 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:51 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:52 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:52 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:52 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:52 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:52 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:53 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:53 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:53 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:53 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:53 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:54 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:54 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:54 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:54 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:54 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:55 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:55 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:55 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:55 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:55 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:56 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:56 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:56 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:56 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:56 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:57 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:57 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:57 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:57 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:57 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:58 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:58 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:58 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:58 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:58 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:48:59 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:48:59 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:48:59 corosync [CMAN  ] daemon: About to process command
Apr 09 17:48:59 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:48:59 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:49:00 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:49:00 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:49:00 corosync [CMAN  ] daemon: About to process command
Apr 09 17:49:00 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:49:00 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:49:01 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:49:01 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:49:01 corosync [CMAN  ] daemon: About to process command
Apr 09 17:49:01 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:49:01 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:49:02 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:49:02 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:49:02 corosync [CMAN  ] daemon: About to process command
Apr 09 17:49:02 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:49:02 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:49:03 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:49:03 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:49:03 corosync [CMAN  ] daemon: About to process command
Apr 09 17:49:03 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:49:03 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:49:04 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:49:04 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:49:04 corosync [CMAN  ] daemon: About to process command
Apr 09 17:49:04 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:49:04 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:49:05 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:49:05 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:49:05 corosync [CMAN  ] daemon: About to process command
Apr 09 17:49:05 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:49:05 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:49:06 corosync [CMAN  ] daemon: read 20 bytes from fd 25
Apr 09 17:49:06 corosync [CMAN  ] daemon: client command is 5
Apr 09 17:49:06 corosync [CMAN  ] daemon: About to process command
Apr 09 17:49:06 corosync [CMAN  ] memb: command to process is 5

Apr 09 17:49:06 corosync [CMAN  ] daemon: sending reply 40000005 to fd 25
Apr 09 17:49:07 corosync [CMAN  ] daemon: read 0 bytes from fd 25
Apr 09 17:49:07 corosync [CMAN  ] daemon: Freed 0 queued messages

Apr 09 17:48:18 corosync [TOTEM ] token retrans flag is 0 my set retrans flag0 retrans queue empty 1 count 0, aru 0 Apr 09 17:48:18 corosync [TOTEM ] token retrans flag is 0 my set retrans flag0 retrans queue empty 1 count 1, aru 0 Apr 09 17:48:18 corosync [TOTEM ] token retrans flag is 0 my set retrans flag0 retrans queue empty 1 count 2, aru 0 Apr 09 17:48:18 corosync [TOTEM ] token retrans flag is 0 my set retrans flag0 retrans queue empty 1 count 3, aru 0 Apr 09 17:48:18 corosync [TOTEM ] retrans flag count 4 token aru 0 install seq 0 aru 0 0 Apr 09 17:48:18 corosync [CMAN ] ais: confchg_fn called type = 1, seq=59160 Apr 09 17:48:18 corosync [CMAN ] ais: confchg_fn called type = 0, seq=59160 Apr 09 17:48:18 corosync [CMAN ] memb: sending TRANSITION message. cluster_name = hailavaila Apr 09 17:48:18 corosync [CMAN ] ais: comms send message 0x7fff1c6753d0 len = 65 Apr 09 17:48:18 corosync [SYNC ] This node is within the primary component and will provide service. Apr 09 17:48:18 corosync [TOTEM ] A processor joined or left the membership and a new membership was formed. Apr 09 17:48:18 corosync [CMAN ] ais: deliver_fn source nodeid = 12, len=81, endian_conv=0 Apr 09 17:48:18 corosync [CMAN ] memb: Got TRANSITION message. msg->flags=20, node->flags=20, first_trans=1 Apr 09 17:48:18 corosync [CMAN ] memb: add_ais_node ID=12, incarnation = 59160 Apr 09 17:48:18 corosync [QUORUM] sending quorum notification to (nil), length = 52 Apr 09 17:48:18 corosync [QUORUM] sending quorum notification to (nil), length = 52 Apr 09 17:48:18 corosync [SYNC ] Barrier completion status for nodeid 12 = 1. Apr 09 17:48:18 corosync [SYNC ] Synchronization actions starting for (openais cluster membership service B.01.01) Apr 09 17:48:18 corosync [SYNC ] Barrier completion status for nodeid 12 = 1. Apr 09 17:48:18 corosync [SYNC ] Committing synchronization for (openais cluster membership service B.01.01) Apr 09 17:48:18 corosync [SYNC ] Synchronization actions starting for (dummy AMF service) Apr 09 17:48:18 corosync [SYNC ] Barrier completion status for nodeid 12 = 1. Apr 09 17:48:18 corosync [SYNC ] Committing synchronization for (dummy AMF service) Apr 09 17:48:18 corosync [SYNC ] Synchronization actions starting for (openais checkpoint service B.01.01) Apr 09 17:48:18 corosync [SYNC ] Barrier completion status for nodeid 12 = 1. Apr 09 17:48:18 corosync [SYNC ] Committing synchronization for (openais checkpoint service B.01.01) Apr 09 17:48:18 corosync [SYNC ] Synchronization actions starting for (openais event service B.01.01) Apr 09 17:48:18 corosync [EVT ] Receive EVT_CONF_CHANGE_DONE from nodeid r(0) ip(192.168.15.25) members 1 checked in 1 Apr 09 17:48:18 corosync [EVT ] Receive EVT_CONF_DONE from nodeid r(0) ip(192.168.15.25) , members 1 checked in 1 Apr 09 17:48:18 corosync [SYNC ] Barrier completion status for nodeid 12 = 1. Apr 09 17:48:18 corosync [SYNC ] Committing synchronization for (openais event service B.01.01) Apr 09 17:48:18 corosync [SYNC ] Synchronization actions starting for (corosync cluster closed process group service v1.01) Apr 09 17:48:18 corosync [CPG ] comparing: sender r(0) ip(192.168.15.25) ; members(old:0 left:0) Apr 09 17:48:18 corosync [CPG ] chosen downlist: sender r(0) ip(192.168.15.25) ; members(old:0 left:0) Apr 09 17:48:18 corosync [SYNC ] Barrier completion status for nodeid 12 = 1. Apr 09 17:48:18 corosync [SYNC ] Committing synchronization for (corosync cluster closed process group service v1.01) Apr 09 17:48:18 corosync [LCK ] [DEBUG]: lck_sync_resource_lock_timer_stop Apr 09 17:48:18 corosync [SYNCV2] Committing synchronization for openais distributed locking service B.03.01 Apr 09 17:48:18 corosync [LCK ] [DEBUG]: lck_sync_resource_lock_timer_start Apr 09 17:48:18 corosync [SYNCV2] Committing synchronization for openais message service B.03.01 Apr 09 17:48:18 corosync [MAIN ] Completed service synchronization, ready to provide service. Apr 09 17:48:18 corosync [IPC ] IPC credentials for client pid 32454: uid 0. gid 0 Apr 09 17:48:18 corosync [QUORUM] sending quorum notification to 0x866550, length = 52 Apr 09 17:48:18 corosync [IPC ] IPC credentials for client pid 32454: uid 0. gid 0 Apr 09 17:48:18 corosync [IPC ] IPC credentials for client pid 32454: uid 0. gid 0 Apr 09 17:48:18 corosync [CPG ] lib_init_fn: conn=0x8708a0, cpd=0x864740 Apr 09 17:48:18 corosync [CPG ] got procjoin message from cluster node 0xc (r(0) ip(192.168.15.25) ) for pid 32454 Apr 09 17:48:18 corosync [IPC ] IPC credentials for client pid 32454: uid 0. gid 0 Apr 09 17:48:18 corosync [CPG ] lib_init_fn: conn=0x875a70, cpd=0x864fb0 Apr 09 17:48:18 corosync [CPG ] got procjoin message from cluster node 0xc (r(0) ip(192.168.15.25) ) for pid 32454 Apr 09 17:48:20 corosync [IPC ] IPC credentials for client pid 32482: uid 0. gid 0 Apr 09 17:48:20 corosync [CMAN ] memb: get_all_members: allocated new buffer (retsize=1024) Apr 09 17:48:20 corosync [CMAN ] daemon: Returning command data. length = 5720 Apr 09 17:48:22 corosync [CMAN ] daemon: Returning command data. length = 24 Apr 09 17:48:22 corosync [CMAN ] daemon: Returning command data. length = 16 Apr 09 17:48:22 corosync [CMAN ] memb: get_extrainfo: allocated new buffer Apr 09 17:48:22 corosync [CMAN ] daemon: Returning command data. length = 320 Apr 09 17:48:22 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:22 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:22 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:22 corosync [CMAN ] daemon: Returning command data. length = 440 Apr 09 17:48:22 corosync [IPC ] IPC credentials for client pid 33938: uid 0. gid 0 Apr 09 17:48:22 corosync [IPC ] IPC credentials for client pid 33938: uid 0. gid 0 Apr 09 17:48:22 corosync [IPC ] IPC credentials for client pid 33938: uid 0. gid 0 Apr 09 17:48:22 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:23 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:24 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:25 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:26 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:27 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:28 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:29 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:30 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:31 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:32 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:33 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:34 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:35 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:36 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:37 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:38 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:39 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:40 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:41 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:42 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:43 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:44 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:45 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:46 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:47 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:48 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:49 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:50 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:51 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:52 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:53 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:54 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:55 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:56 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:57 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:58 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:48:59 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:49:00 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:49:01 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:49:02 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:49:03 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:49:04 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:49:05 corosync [CMAN ] daemon: Returning command data. length = 0 Apr 09 17:49:06 corosync [CMAN ] daemon: Returning command data. length = 0

smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user