Bug 789925

Summary: Logfile format needs tweaking
Product: [Fedora] Fedora Reporter: Andrew Beekhof <abeekhof>
Component: corosyncAssignee: Angus Salkeld <asalkeld>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: agk, fdinitto, jfriesse, sdake
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-17 23:29:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Andrew Beekhof 2012-02-13 09:58:42 UTC 
Description of problem:


Corosync logs contain messages like so:

Feb 13 08:25:51 notice  [MAIN  ] Corosync Cluster Engine exiting normally
Feb 13 08:32:10 notice  [TOTEM ] Initializing transport (UDP/IP Multicast).

It would be useful to:
- include the pid file so we can differentiate between different instances of corosync
- include the host name so that CTS can look for node-specific patterns
- include the process name if possible.  this makes post-filtering easier as it is useful to have pacemaker log to the same file.
  
Actual results:

Feb 13 08:25:51 notice  [MAIN  ] Corosync Cluster Engine exiting normally

Expected results:

Something like syslog or perhaps:

Feb 13 08:25:51 [22196] pcmk-3 corosync notice  [MAIN  ] Corosync Cluster Engine exiting normally


Additional info:
Comment 1 Angus Salkeld 2012-03-14 08:24:12 UTC 
https://github.com/corosync/corosync/commit/f628ccba8b0576704466b168e8dbf23e6a879097