nginx agent produces spurious error messages (includes patch)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
resource-agents (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
When running the nginx agent syslog is spammed with these messages:
Aug 2 14:29:15 p2c2ppx01 lrmd: [17150]: info: RA output: (p2nginx:
Aug 2 14:29:15 p2c2ppx01 lrmd: [17150]: info: RA output: (p2nginx:
Aug 2 14:29:15 p2c2ppx01 lrmd: [17150]: info: RA output: (p2nginx:
Aug 2 14:29:15 p2c2ppx01 lrmd: [17150]: info: RA output: (p2nginx:
Aug 2 14:29:15 p2c2ppx01 lrmd: [17150]: info: RA output: (p2nginx:
Due to this line in nginx.conf
include /etc/nginx/
This seemed strange since the only "ls" line in the nginx script contains a error redirect. Strace to the rescue:
31799 execve("/bin/sh", ["sh", "-c", "ls /etc/nginx/
Not removing the ; on the input line. I expect that the author of the awk script had a space before the ; on each line in his config. Similarly for the other include line:
31801 stat("/
To fix replace the procline function in the awk script with this:
function procline() {
if( a[1]~/^[Ii]nclude$/ ) {
} else {
}
}
Note the gsub replacing trailing ; with nothing.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: resource-agents 1:3.9.2-5ubuntu4.1
ProcVersionSign
Uname: Linux 3.2.0-26-generic x86_64
ApportVersion: 2.0.1-0ubuntu11
Architecture: amd64
Date: Thu Aug 2 14:24:43 2012
InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 (20120424.1)
SourcePackage: resource-agents
UpgradeStatus: No upgrade log present (probably fresh install)
Thank you for taking the time to report this bug. In an effort to keep an
up-to-date and valid list of bugs to work on, I have reviewed this report
to verify it still requires effort and occurs on an Ubuntu release in
standard support, and it does not.
It is unfortunate that we were unable to resolve this defect, however
there appears to be no further action possible at this time. I am
therefore moving the bug to 'Incomplete'. If you disagree or have
new information, we would be grateful if you could please add a comment
stating why and then change the status of the bug to 'New'.