Project

General

Profile

Idea #17286

Adjust the fe logging to be less annoying

Added by Mats Rynge about 2 years ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Frontend
Target version:
-
Start date:
07/27/2017
Due date:
% Done:

0%

Estimated time:
Stakeholders:
Duration:

Description

Developers,

Our frontend is currently configured with 24 schedds. Not all these schedds have jobs all the time, and when the flocking ones have 0 jobs, they don't show up in the collector. This is currently being considered a failure, and my logs are getting filled with:

[2017-07-27 16:25:05,114] ERROR: Runtime Error. Failed to talk to schedd
Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/glideinwms/frontend/glideinFrontendLib.py", line 1048, in getCondorQConstrained
condorq = condorMonitor.CondorQ(schedd)
File "/usr/lib/python2.6/site-packages/glideinwms/lib/condorMonitor.py", line 525, in init
pool_name)
File "/usr/lib/python2.6/site-packages/glideinwms/lib/condorMonitor.py", line 152, in getScheddId
env = self.iGetEnv(schedd_name, pool_name)
File "/usr/lib/python2.6/site-packages/glideinwms/lib/condorMonitor.py", line 175, in iGetEnv
raise RuntimeError, "Schedd '%s' not found"%schedd_name
RuntimeError: Schedd '' not found

A small improvement would be to make this a warning instead of an error, and only log a single line instead of the trace.

A bigger improvement would be to be able to mark these as "optional" in the config, and only log at the debug level if they are missing.



Also available in: Atom PDF