Bug 601588 - carod doesn't write logs to log file
Summary: carod doesn't write logs to log file
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: grid
Version: Development
Hardware: All
OS: Linux
low
low
Target Milestone: 1.3
: ---
Assignee: Robert Rati
QA Contact: Lubos Trilety
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-08 09:33 UTC by Martin Kudlej
Modified: 2010-10-20 11:28 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2010-10-20 11:28:55 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Martin Kudlej 2010-06-08 09:33:51 UTC 
Description of problem:
carod doesn't write log entries to log file set in LL_DAEMON_LOG if carod runs as daemon and it is started by condor master. If I remove carod from DAEMON_LIST and run it by hand, it write to stdout and also to log file.

Version-Release number of selected component (if applicable):
condor-low-latency-1.1-0.1.el5

How reproducible:
100%

Steps to Reproduce:
1. set carod to DAEMON_LIST and set LL_DAEMON_LOG

Actual results:
There is no log entry in carod log file.

Expected results:
It writes log entries to log file.
Comment 1 Robert Rati 2010-06-08 15:13:03 UTC 
This isn't really a bug, as the carod currently only logs errors to the log file until the debug option is given (-l).  I've added startup/shutdown logs and function entry logs are now shown by default.  This should give an indication that the daemon is running and processing requests.

Added in:
condor-low-latency-1.1-0.2
Comment 2 Lubos Trilety 2010-06-24 14:46:21 UTC 
Tested with:
condor-low-latency-1.1-0.2

Tested on:
RHEL4 i386   - passed
RHEL4 x86_64 - passed
RHEL5 i386   - passed
RHEL5 x86_64 - passed

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