Re: [Pacemaker] logging related information- pacemaker
Hi, On Sat, Nov 28, 2009 at 08:45:26PM -0500, Shravan Mishra wrote: Hi, I'm using pacemaker and trying to configure logging for various subsytems like pengine, attrd, crmd etc. On starting corosync the only logs I see are for e.g [...] Nothing related to stonithd or crmd etc. I have started /usr/lib64/heartbeat/ha_logd -d. Under /etc/ha.d/shellfuncs I see variables which I have exported on the command line: HA_LOGD=yes HA_LOGFILE=/tmp/corosync.log Am I taking a completely wrong path, am I supposed to configure just using corosync.conf and use logger_subsys for the above mentioned subsystems? In corosync.conf, you should set use_logd: yes in the service section, then specify the syslog facility in /etc/logd.cf. A bit confusing, but openais/corosync and ha_logd have different configuration files. Thanks, Dejan Sincerely Shravan ___ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker ___ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Re: [Pacemaker] logging related information- pacemaker
Thanks a lot. On Mon, Nov 30, 2009 at 10:42 AM, Dejan Muhamedagic deja...@fastmail.fm wrote: Hi, On Sat, Nov 28, 2009 at 08:45:26PM -0500, Shravan Mishra wrote: Hi, I'm using pacemaker and trying to configure logging for various subsytems like pengine, attrd, crmd etc. On starting corosync the only logs I see are for e.g [...] Nothing related to stonithd or crmd etc. I have started /usr/lib64/heartbeat/ha_logd -d. Under /etc/ha.d/shellfuncs I see variables which I have exported on the command line: HA_LOGD=yes HA_LOGFILE=/tmp/corosync.log Am I taking a completely wrong path, am I supposed to configure just using corosync.conf and use logger_subsys for the above mentioned subsystems? In corosync.conf, you should set use_logd: yes in the service section, then specify the syslog facility in /etc/logd.cf. A bit confusing, but openais/corosync and ha_logd have different configuration files. Thanks, Dejan Sincerely Shravan ___ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker ___ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker ___ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
[Pacemaker] logging related information- pacemaker
Hi,
I'm using pacemaker and trying to configure logging for various
subsytems like pengine, attrd, crmd etc.
On starting corosync the only logs I see are for e.g
Nov 29 00:38:13 corosync [MAIN ] Corosync Cluster Engine ('1.1.1'):
started and ready to provide service.
Nov 29 00:38:13 corosync [MAIN ] Corosync built-in features:
Nov 29 00:38:13 corosync [MAIN ] Successfully read main configuration
file '/etc/corosync/corosync.conf'.
Nov 29 00:38:13 corosync [TOTEM ] Initializing transport (UDP/IP).
Nov 29 00:38:13 corosync [TOTEM ] Initializing transmit/receive
security: libtomcrypt SOBER128/SHA1HMAC (mode 0).
Nov 29 00:38:13 corosync [MAIN ] Compatibility mode set to whitetank.
Using V1 and V2 of the synchronization engine.
Nov 29 00:38:13 corosync [TOTEM ] The network interface [192.168.2.2] is now up.
Nov 29 00:38:13 corosync [pcmk ] info: process_ais_conf: Reading configure
Nov 29 00:38:13 corosync [pcmk ] info: config_find_init: Local
handle: 2013064636357672961 for logging
Nov 29 00:38:13 corosync [pcmk ] info: config_find_next: Processing
additional logging options...
Nov 29 00:38:13 corosync [pcmk ] info: get_config_opt: Found 'off'
for option: debug
Nov 29 00:38:13 corosync [pcmk ] info: get_config_opt: Defaulting to
'off' for option: to_file
Nov 29 00:38:13 corosync [pcmk ] info: get_config_opt: Defaulting to
'daemon' for option: syslog_facility
Nov 29 00:38:13 corosync [pcmk ] info: config_find_init: Local
handle: 4730966301143465986 for service
Nov 29 00:38:13 corosync [pcmk ] info: config_find_next: Processing
additional service options...
Nov 29 00:38:13 corosync [pcmk ] info: get_config_opt: Defaulting to
'no' for option: use_logd
Nov 29 00:38:13 corosync [pcmk ] info: get_config_opt: Defaulting to
'no' for option: use_mgmtd
Nov 29 00:38:13 corosync [pcmk ] info: pcmk_startup: CRM: Initialized
Nov 29 00:38:13 corosync [pcmk ] Logging: Initialized pcmk_startup
Nov 29 00:38:13 corosync [pcmk ] info: pcmk_startup: Maximum core
file size is: 18446744073709551615
Nov 29 00:38:13 corosync [pcmk ] info: pcmk_startup: Service: 9
Nov 29 00:38:13 corosync [pcmk ] info: pcmk_startup: Local hostname:
node2.itactics.com
Nov 29 00:38:13 corosync [pcmk ] info: pcmk_update_nodeid: Local node
id: 33728704
Nov 29 00:38:13 corosync [pcmk ] info: update_member: Creating entry
for node 33728704 born on 0
Nov 29 00:38:13 corosync [pcmk ] info: update_member: 0x543670 Node
33728704 now known as node2.itactics.com (was: (null))
==
Nothing related to stonithd or crmd etc.
I have started /usr/lib64/heartbeat/ha_logd -d.
Under /etc/ha.d/shellfuncs
I see variables which I have exported on the command line:
HA_LOGD=yes
HA_LOGFILE=/tmp/corosync.log
Am I taking a completely wrong path, am I supposed to configure just
using corosync.conf and use logger_subsys for the above mentioned
subsystems?
Sincerely
Shravan
___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
