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

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

 



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