Bug 5200 - GRAM (pre-webservices) from OSG 0.6.0 (VDT 1.6.1) has bad syslog format
: GRAM (pre-webservices) from OSG 0.6.0 (VDT 1.6.1) has bad syslog format
Status: RESOLVED WONTFIX
: GRAM
gt2 Gatekeeper/Jobmanager
: unspecified
: PC Linux
: P3 minor
: ---
Assigned To:
: http://atgrid.grid.umich.edu/php-sysl...
:
:
:
  Show dependency treegraph
 
Reported: 2007-04-10 17:03 by
Modified: 2012-09-05 13:44 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2007-04-10 17:03:28
The syslog messages being emitted by the globus-gatekeeper have an incorrect
format.  Typical syslog messages have the form:

<timestamp> <hostname> <service> ...

We are receiving messages from GRAM that look like:

Apr 10 16:48:05 GRAM gatekeeper[28862]:
/afs/atlas.umich.edu/OSG060/globus/sbin/globus-gatekeeper pid=28862 starting at
Tue Apr 10 16:48:05 2007

Note the missing <hostname>

This causes problems for our syslog-ng logging (messages appear to come from
host "GRAM").  You can see for yourself by acessing the URL ("guest"/"guest")

Is this a known problem?  How best to debug it?

Thanks,

Shawn McKee
------- Comment #1 From 2007-04-11 09:55:26 -------
This sounds more like an enhancement request as opposed to something to debug.

I think the print statement in the gatekeeper code would need to add the
hostname to it.  Is that something you could do and test and then give us a
patch?

Thanks,
Stu
------- Comment #2 From 2007-04-11 11:20:05 -------
Subject: RE:  GRAM (pre-webservices) from OSG 0.6.0 (VDT 1.6.1) has bad syslog
format

Hi Stu,

Since you write to syslog and all other services/applications that write
to syslog include the host it seems to be a bug to me.

Can you point me to the source?  I have only an stock OSG 0.6.0 install
based upon VDT 1.6.1 with no available source.  Where are the syslog
writes?

Shawn

-----Original Message-----
From: bugzilla-daemon@mcs.anl.gov [mailto:bugzilla-daemon@mcs.anl.gov] 
Sent: Wednesday, April 11, 2007 10:55 AM
To: McKee, Shawn
Subject: [Bug 5200] GRAM (pre-webservices) from OSG 0.6.0 (VDT 1.6.1)
has bad syslog format

http://bugzilla.globus.org/bugzilla/show_bug.cgi?id=5200


smartin@mcs.anl.gov changed:

           What    |Removed                     |Added
------------------------------------------------------------------------
----

URL|http://atgrid.grid.umich.edu|http://atgrid.grid.umich.edu
                   |/php-syslog-ng              |/php-syslog-ng
             Status|NEW                         |ASSIGNED




------- Comment #1 from smartin@mcs.anl.gov  2007-04-11 09:55 -------
This sounds more like an enhancement request as opposed to something to
debug.

I think the print statement in the gatekeeper code would need to add the
hostname to it.  Is that something you could do and test and then give
us a
patch?

Thanks,
Stu




------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
------- Comment #3 From 2007-04-11 12:50:02 -------
Subject: RE:  GRAM (pre-webservices) from OSG 0.6.0 (VDT 1.6.1) has bad syslog
format

FYI the previous OSG 0.4.1 had gram working correctly when reporting to
syslog.  Here is an example of when it worked:

Apr 10 16:47:17 gate01 GRAM gatekeeper[26814]: Authorized as local user:
usatlas3
Apr 10 16:47:17 gate01 GRAM gatekeeper[26814]: Authorized as local uid:
789090
Apr 10 16:47:17 gate01 GRAM gatekeeper[26814]:           and local gid:
55670
Apr 10 16:47:17 gate01 GRAM gatekeeper[26808]: Requested service:
jobmanager-condor

The hostname was there in the prior version...yesterday we cut-over to
OSG 0.6.0 and then noticed GRAM was reporting to syslog differently.

Thanks,

Shawn

-----Original Message-----
From: bugzilla-daemon@mcs.anl.gov [mailto:bugzilla-daemon@mcs.anl.gov] 
Sent: Wednesday, April 11, 2007 10:55 AM
To: McKee, Shawn
Subject: [Bug 5200] GRAM (pre-webservices) from OSG 0.6.0 (VDT 1.6.1)
has bad syslog format

http://bugzilla.globus.org/bugzilla/show_bug.cgi?id=5200


smartin@mcs.anl.gov changed:

           What    |Removed                     |Added
------------------------------------------------------------------------
----

URL|http://atgrid.grid.umich.edu|http://atgrid.grid.umich.edu
                   |/php-syslog-ng              |/php-syslog-ng
             Status|NEW                         |ASSIGNED




------- Comment #1 from smartin@mcs.anl.gov  2007-04-11 09:55 -------
This sounds more like an enhancement request as opposed to something to
debug.

I think the print statement in the gatekeeper code would need to add the
hostname to it.  Is that something you could do and test and then give
us a
patch?

Thanks,
Stu




------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
------- Comment #4 From 2007-04-11 15:05:03 -------
Subject: RE:  GRAM (pre-webservices) from OSG 0.6.0 (VDT
  1.6.1) has bad syslog format

I just did some CVS archaeology. While I didn't do a definitive scan, 
I'm pretty sure that the syslog output from the globus_gatekeeper has 
never has the date, time, or host in it: that's only been the file output.

Has something changed in your syslog configuration?

-alain

At 01:46 PM 4/11/2007 -0400, McKee, Shawn wrote:
>FYI the previous OSG 0.4.1 had gram working correctly when reporting to
>syslog.  Here is an example of when it worked:
>
>Apr 10 16:47:17 gate01 GRAM gatekeeper[26814]: Authorized as local user:
>usatlas3
>Apr 10 16:47:17 gate01 GRAM gatekeeper[26814]: Authorized as local uid:
>789090
>Apr 10 16:47:17 gate01 GRAM gatekeeper[26814]:           and local gid:
>55670
>Apr 10 16:47:17 gate01 GRAM gatekeeper[26808]: Requested service:
>jobmanager-condor
>
>The hostname was there in the prior version...yesterday we cut-over to
>OSG 0.6.0 and then noticed GRAM was reporting to syslog differently.
>
>Thanks,
>
>Shawn
>
>-----Original Message-----
>From: bugzilla-daemon@mcs.anl.gov [mailto:bugzilla-daemon@mcs.anl.gov]
>Sent: Wednesday, April 11, 2007 10:55 AM
>To: McKee, Shawn
>Subject: [Bug 5200] GRAM (pre-webservices) from OSG 0.6.0 (VDT 1.6.1)
>has bad syslog format
>
>http://bugzilla.globus.org/bugzilla/show_bug.cgi?id=5200
>
>
>smartin@mcs.anl.gov changed:
>
>            What    |Removed                     |Added
>------------------------------------------------------------------------
>----
>
>URL|http://atgrid.grid.umich.edu|http://atgrid.grid.umich.edu
>                    |/php-syslog-ng              |/php-syslog-ng
>              Status|NEW                         |ASSIGNED
>
>
>
>
>------- Comment #1 from smartin@mcs.anl.gov  2007-04-11 09:55 -------
>This sounds more like an enhancement request as opposed to something to
>debug.
>
>I think the print statement in the gatekeeper code would need to add the
>hostname to it.  Is that something you could do and test and then give
>us a
>patch?
>
>Thanks,
>Stu
>
>
>
>
>------- You are receiving this mail because: -------
>You reported the bug, or are watching the reporter.
------- Comment #5 From 2007-04-11 15:05:04 -------
Subject: RE:  GRAM (pre-webservices) from OSG 0.6.0 (VDT  1.6.1) has bad syslog
format

Thanks Alain,

I will do some more exploring on our system.  We may have had an update
of syslog-ng via yum-autoupdate (for example).

It is strange that only GRAM seems to have the problem. The 'gridinfo'
service on the gatekeeper (and all other services writing to syslog)
works fine (host is present in the syslog messages).

I will let everyone know what I find out.

Shawn

-----Original Message-----
From: Alain Roy [mailto:roy@cs.wisc.edu] 
Sent: Wednesday, April 11, 2007 4:00 PM
To: McKee, Shawn; bugzilla@globus.org
Cc: Rob Gardner
Subject: RE: [Bug 5200] GRAM (pre-webservices) from OSG 0.6.0 (VDT
1.6.1) has bad syslog format

I just did some CVS archaeology. While I didn't do a definitive scan, 
I'm pretty sure that the syslog output from the globus_gatekeeper has 
never has the date, time, or host in it: that's only been the file
output.

Has something changed in your syslog configuration?

-alain

At 01:46 PM 4/11/2007 -0400, McKee, Shawn wrote:
>FYI the previous OSG 0.4.1 had gram working correctly when reporting to
>syslog.  Here is an example of when it worked:
>
>Apr 10 16:47:17 gate01 GRAM gatekeeper[26814]: Authorized as local
user:
>usatlas3
>Apr 10 16:47:17 gate01 GRAM gatekeeper[26814]: Authorized as local uid:
>789090
>Apr 10 16:47:17 gate01 GRAM gatekeeper[26814]:           and local gid:
>55670
>Apr 10 16:47:17 gate01 GRAM gatekeeper[26808]: Requested service:
>jobmanager-condor
>
>The hostname was there in the prior version...yesterday we cut-over to
>OSG 0.6.0 and then noticed GRAM was reporting to syslog differently.
>
>Thanks,
>
>Shawn
>
>-----Original Message-----
>From: bugzilla-daemon@mcs.anl.gov [mailto:bugzilla-daemon@mcs.anl.gov]
>Sent: Wednesday, April 11, 2007 10:55 AM
>To: McKee, Shawn
>Subject: [Bug 5200] GRAM (pre-webservices) from OSG 0.6.0 (VDT 1.6.1)
>has bad syslog format
>
>http://bugzilla.globus.org/bugzilla/show_bug.cgi?id=5200
>
>
>smartin@mcs.anl.gov changed:
>
>            What    |Removed                     |Added
>-----------------------------------------------------------------------
-
>----
>
>URL|http://atgrid.grid.umich.edu|http://atgrid.grid.umich.edu
>                    |/php-syslog-ng              |/php-syslog-ng
>              Status|NEW                         |ASSIGNED
>
>
>
>
>------- Comment #1 from smartin@mcs.anl.gov  2007-04-11 09:55 -------
>This sounds more like an enhancement request as opposed to something to
>debug.
>
>I think the print statement in the gatekeeper code would need to add
the
>hostname to it.  Is that something you could do and test and then give
>us a
>patch?
>
>Thanks,
>Stu
>
>
>
>
>------- You are receiving this mail because: -------
>You reported the bug, or are watching the reporter.
------- Comment #6 From 2007-04-11 18:55:02 -------
Subject: RE:  GRAM (pre-webservices) from OSG 0.6.0 (VDT  1.6.1) has bad syslog
format

OK...Mystery solved.

The syslog-ng conf file was changed about the time we cut-over to OSG
0.6.0.

The following thread describes the issue with a similar example:
https://lists.balabit.hu/pipermail/syslog-ng/2002-January/002886.html 

The "TAG" part for the GRAM messages is "GRAM gatekeeper[<n>]"

The RFC3164 is apparently somewhat ambiguous.  When there is a space in
the TAG syslog or syslog-ng will assume the first part is the hostname.
There is a configuration option in syslog-ng "keep-hostname" which was
turned on.  This causes "GRAM" to become the hostname for these
messages.  I have turned it back off for out gatekeeper and now the
correct host is inserted by syslog-ng based upon the origin of the
syslog message.

Sorry for the confusion...I had assumed this was controlled by the
syslog callout in the application.

Shawn

-----Original Message-----
From: McKee, Shawn 
Sent: Wednesday, April 11, 2007 4:04 PM
To: 'Alain Roy'; bugzilla@globus.org
Cc: Rob Gardner
Subject: RE: [Bug 5200] GRAM (pre-webservices) from OSG 0.6.0 (VDT
1.6.1) has bad syslog format

Thanks Alain,

I will do some more exploring on our system.  We may have had an update
of syslog-ng via yum-autoupdate (for example).

It is strange that only GRAM seems to have the problem. The 'gridinfo'
service on the gatekeeper (and all other services writing to syslog)
works fine (host is present in the syslog messages).

I will let everyone know what I find out.

Shawn

-----Original Message-----
From: Alain Roy [mailto:roy@cs.wisc.edu] 
Sent: Wednesday, April 11, 2007 4:00 PM
To: McKee, Shawn; bugzilla@globus.org
Cc: Rob Gardner
Subject: RE: [Bug 5200] GRAM (pre-webservices) from OSG 0.6.0 (VDT
1.6.1) has bad syslog format

I just did some CVS archaeology. While I didn't do a definitive scan, 
I'm pretty sure that the syslog output from the globus_gatekeeper has 
never has the date, time, or host in it: that's only been the file
output.

Has something changed in your syslog configuration?

-alain

At 01:46 PM 4/11/2007 -0400, McKee, Shawn wrote:
>FYI the previous OSG 0.4.1 had gram working correctly when reporting to
>syslog.  Here is an example of when it worked:
>
>Apr 10 16:47:17 gate01 GRAM gatekeeper[26814]: Authorized as local
user:
>usatlas3
>Apr 10 16:47:17 gate01 GRAM gatekeeper[26814]: Authorized as local uid:
>789090
>Apr 10 16:47:17 gate01 GRAM gatekeeper[26814]:           and local gid:
>55670
>Apr 10 16:47:17 gate01 GRAM gatekeeper[26808]: Requested service:
>jobmanager-condor
>
>The hostname was there in the prior version...yesterday we cut-over to
>OSG 0.6.0 and then noticed GRAM was reporting to syslog differently.
>
>Thanks,
>
>Shawn
>
>-----Original Message-----
>From: bugzilla-daemon@mcs.anl.gov [mailto:bugzilla-daemon@mcs.anl.gov]
>Sent: Wednesday, April 11, 2007 10:55 AM
>To: McKee, Shawn
>Subject: [Bug 5200] GRAM (pre-webservices) from OSG 0.6.0 (VDT 1.6.1)
>has bad syslog format
>
>http://bugzilla.globus.org/bugzilla/show_bug.cgi?id=5200
>
>
>smartin@mcs.anl.gov changed:
>
>            What    |Removed                     |Added
>-----------------------------------------------------------------------
-
>----
>
>URL|http://atgrid.grid.umich.edu|http://atgrid.grid.umich.edu
>                    |/php-syslog-ng              |/php-syslog-ng
>              Status|NEW                         |ASSIGNED
>
>
>
>
>------- Comment #1 from smartin@mcs.anl.gov  2007-04-11 09:55 -------
>This sounds more like an enhancement request as opposed to something to
>debug.
>
>I think the print statement in the gatekeeper code would need to add
the
>hostname to it.  Is that something you could do and test and then give
>us a
>patch?
>
>Thanks,
>Stu
>
>
>
>
>------- You are receiving this mail because: -------
>You reported the bug, or are watching the reporter.
------- Comment #7 From 2012-09-05 13:44:37 -------
Doing some bugzilla cleanup...  Resolving old GRAM3 and GRAM4 issues that are
no longer relevant since we've moved on to GRAM5.  Also, we're now tracking
issue in jira.  Any new issues should be added here:

http://jira.globus.org/secure/VersionBoard.jspa?selectedProjectId=10363