Re: [Corosync] How to open debug log for totem*.c?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Jason,

> Hi Honza,
> 
> I set to_logfile and logfile and this is my corosync.log:
> 
> [2692] toshiba corosyncnotice  [MAIN  ] Corosync Cluster Engine
> ('2.3.3'): started and ready to provide service.
> [2692] toshiba corosyncinfo    [MAIN  ] Corosync built-in features:
> dbus rdma systemd xmlconf snmp pie relro bindnow
> [2692] toshiba corosyncnotice  [SERV  ] Service engine loaded:
> corosync configuration map access [0]
> [2692] toshiba corosyncdebug   [MAIN  ] Initializing IPC on cmap [0]
> [2692] toshiba corosyncdebug   [MAIN  ] No configured qb.ipc_type.
> Using native ipc
> [2692] toshiba corosyncnotice  [SERV  ] Service engine loaded:
> corosync configuration service [1]
> [2692] toshiba corosyncdebug   [MAIN  ] Initializing IPC on cfg [1]
> [2692] toshiba corosyncdebug   [MAIN  ] No configured qb.ipc_type.
> Using native ipc
> [2692] toshiba corosyncnotice  [SERV  ] Service engine loaded:
> corosync cluster closed process group service v1.01 [2]
> [2692] toshiba corosyncdebug   [MAIN  ] Initializing IPC on cpg [2]
> [2692] toshiba corosyncdebug   [MAIN  ] No configured qb.ipc_type.
> Using native ipc
> [2692] toshiba corosyncnotice  [SERV  ] Service engine loaded:
> corosync profile loading service [4]
> [2692] toshiba corosyncdebug   [MAIN  ] NOT Initializing IPC on pload [4]
> [2692] toshiba corosyncnotice  [QUORUM] Using quorum provider
> corosync_votequorum
> [2692] toshiba corosyncdebug   [QUORUM] Reading configuration (runtime: 0)
> [2692] toshiba corosyncdebug   [QUORUM] ev_tracking=0,
> ev_tracking_barrier = 0: expected_votes = 0
> [2692] toshiba corosyncdebug   [QUORUM] total_votes=1, expected_votes=2
> [2692] toshiba corosyncdebug   [QUORUM] node 1 state=1, votes=1, expected=2
> [2692] toshiba corosyncdebug   [QUORUM] flags: quorate: No Leaving: No
> WFA Status: No First: Yes Qdevice: No QdeviceAlive: No
> QdeviceCastVote: No QdeviceMasterWins: No
> [2692] toshiba corosyncnotice  [SERV  ] Service engine loaded:
> corosync vote quorum service v1.0 [5]
> [2692] toshiba corosyncdebug   [MAIN  ] Initializing IPC on votequorum [5]
> [2692] toshiba corosyncdebug   [MAIN  ] No configured qb.ipc_type.
> Using native ipc
> [2692] toshiba corosyncnotice  [SERV  ] Service engine loaded:
> corosync cluster quorum service v0.1 [3]
> [2692] toshiba corosyncdebug   [MAIN  ] Initializing IPC on quorum [3]
> [2692] toshiba corosyncdebug   [MAIN  ] No configured qb.ipc_type.
> Using native ipc
> [2692] toshiba corosyncdebug   [MAIN  ] Member joined: r(0) ip(192.168.1.12)
> [2692] toshiba corosyncdebug   [QUORUM] got nodeinfo message from cluster node 1
> [2692] toshiba corosyncdebug   [QUORUM] nodeinfo message[1]: votes: 1,
> expected: 2 flags: 8
> [2692] toshiba corosyncdebug   [QUORUM] flags: quorate: No Leaving: No
> WFA Status: No First: Yes Qdevice: No QdeviceAlive: No
> QdeviceCastVote: No QdeviceMasterWins: No
> [2692] toshiba corosyncdebug   [QUORUM] total_votes=1, expected_votes=2
> [2692] toshiba corosyncdebug   [QUORUM] node 1 state=1, votes=1, expected=2
> [2692] toshiba corosyncdebug   [SYNC  ] Committing synchronization for
> corosync configuration map access
> [2692] toshiba corosyncdebug   [CMAP  ] Single node sync -> no action
> [2692] toshiba corosyncdebug   [CPG   ] comparing: sender r(0)
> ip(192.168.1.12) ; members(old:0 left:0)
> [2692] toshiba corosyncdebug   [CPG   ] chosen downlist: sender r(0)
> ip(192.168.1.12) ; members(old:0 left:0)
> [2692] toshiba corosyncdebug   [SYNC  ] Committing synchronization for
> corosync cluster closed process group service v1.01
> [2692] toshiba corosyncdebug   [QUORUM] flags: quorate: No Leaving: No
> WFA Status: No First: Yes Qdevice: No QdeviceAlive: No
> QdeviceCastVote: No QdeviceMasterWins: No
> [2692] toshiba corosyncdebug   [QUORUM] got nodeinfo message from cluster node 1
> [2692] toshiba corosyncdebug   [QUORUM] nodeinfo message[1]: votes: 1,
> expected: 2 flags: 8
> [2692] toshiba corosyncdebug   [QUORUM] flags: quorate: No Leaving: No
> WFA Status: No First: Yes Qdevice: No QdeviceAlive: No
> QdeviceCastVote: No QdeviceMasterWins: No
> [2692] toshiba corosyncdebug   [QUORUM] total_votes=1, expected_votes=2
> [2692] toshiba corosyncdebug   [QUORUM] node 1 state=1, votes=1, expected=2
> [2692] toshiba corosyncdebug   [QUORUM] got nodeinfo message from cluster node 1
> [2692] toshiba corosyncdebug   [QUORUM] nodeinfo message[0]: votes: 0,
> expected: 0 flags: 0
> [2692] toshiba corosyncdebug   [SYNC  ] Committing synchronization for
> corosync vote quorum service v1.0
> [2692] toshiba corosyncdebug   [QUORUM] total_votes=1, expected_votes=2
> [2692] toshiba corosyncdebug   [QUORUM] node 1 state=1, votes=1, expected=2
> [2692] toshiba corosyncnotice  [QUORUM] Members[1]: 1
> [2692] toshiba corosyncdebug   [QUORUM] sending quorum notification to
> (nil), length = 52
> [2692] toshiba corosyncnotice  [MAIN  ] Completed service
> synchronization, ready to provide service.
> [2692] toshiba corosyncdebug   [MAIN  ] connection created
> [2692] toshiba corosyncdebug   [MAIN  ] cs_ipcs_connection_closed()
> [2692] toshiba corosyncdebug   [MAIN  ] cs_ipcs_connection_destroyed()
> 
> 
> 
> 
> Still no [TOTEM] blah bla...... ,which printed by:
> 
> log_printf (instance->totemsrp_log_level_debug, "..."); in totemsrp.c
> 
> 

can you please try corosync from git master and libqb from git master?
I'm remembering some strange issues with logging.

Regards,
  Honza

> 
> On Wed, May 28, 2014 at 10:43 PM, Jan Friesse <jfriesse@xxxxxxxxxx> wrote:
>> Jason,
>>
>>> Hi All,
>>> After switched from corosync-1.4.x to corosync-2.3.x, I can not get debug
>>> log in exec/totem*.c any more. Set debug:on in logging section in
>>> corosync.conf seems does not work as before(corosync-1.4.*). Only those sub
>>> modules who use LOGSYS_DECLARE_SUBSYS  macro still works. How can I get
>>> totem debug log now?
>>>
>>
>> I hope debug (global) still works as before. Only change which maybe you
>> didn't hit before is move some of messages to trace level. This can be
>> activated by setting debug: trace. Also keep in mind that default syslog
>> is usually configured to not log debug messages, so it's better to set:
>>
>> to_logfile: yes
>> logfile: /var/log/cluster/corosync.log
>>
>> and read messages from corosync.log.
>>
>> Regards,
>>   Honza
>>
>>> Below is my corosync.conf
>>>
>>>
>>> totem {
>>> version: 2
>>> secauth: off
>>> cluster_name: MyCluster
>>> transport: udpu
>>> }
>>>
>>> nodelist {
>>>   node {
>>>         ring0_addr: toshiba
>>>         nodeid: 1
>>>        }
>>>   node {
>>>         ring0_addr: vm1
>>>         nodeid: 2
>>>        }
>>> }
>>>
>>> quorum {
>>> provider: corosync_votequorum
>>> }
>>>
>>> logging {
>>> to_syslog: yes
>>> debug: on
>>> }
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> discuss mailing list
>>> discuss@xxxxxxxxxxxx
>>> http://lists.corosync.org/mailman/listinfo/discuss
>>>
>>
> 
> 
> 

_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss




[Index of Archives]     [Linux Clusters]     [Corosync Project]     [Linux USB Devel]     [Linux Audio Users]     [Photo]     [Yosemite News]    [Yosemite Photos]    [Linux Kernel]     [Linux SCSI]     [X.Org]

  Powered by Linux