[asterisk-bugs] [Asterisk 0012652]: Whenever I issue reload, I get "No [csv] section in cdr.conf. Unregistering backend."
noreply at bugs.digium.com
noreply at bugs.digium.com
Thu May 15 10:33:52 CDT 2008
The following issue requires your FEEDBACK.
======================================================================
http://bugs.digium.com/view.php?id=12652
======================================================================
Reported By: DennisD
Assigned To: murf
======================================================================
Project: Asterisk
Issue ID: 12652
Category: CDR/cdr_csv
Reproducibility: always
Severity: minor
Priority: normal
Status: feedback
Asterisk Version: 1.6.0-beta8
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 05-14-2008 14:05 CDT
Last Modified: 05-15-2008 10:33 CDT
======================================================================
Summary: Whenever I issue reload, I get "No [csv] section in
cdr.conf. Unregistering backend."
Description:
It looks like this COULD be the problem:
In cdr_csv.c:
if (!(cfg = ast_config_load(config, config_flags))) {
ast_log(LOG_WARNING, "unable to load config: %s\n", config);
return 0;
} else if (cfg == CONFIG_STATUS_FILEUNCHANGED)
return 0;
Shouldn't line 107 return 1 if the config file status unchanged?
======================================================================
----------------------------------------------------------------------
murf - 05-15-08 10:33
----------------------------------------------------------------------
I'm putting this issue in feedback to have the reporter (and others) give
their opinions on what, if anything, should be done here.
1. have all modules report something to the log when a reload event skips
reading in a config file when FILEUNCHANGED is true?
2. Chop the [csv] section out of the cdr.conf file and put it in
cdr_csv.conf?
and, if the cdr_csv.conf file is not there, it will print a message and
DECLINE
the module load?
3. Completely remove the cdr_csv stuff, users should use cdr_custom
instead
anyway?
4. Do nothing and close this bug, because (1) will just add useless info
to the logs, (2) will result in zero advantage, (3) will inconvenience
those users already using the cdr_csv stuff.
Issue History
Date Modified Username Field Change
======================================================================
05-15-08 10:33 murf Note Added: 0086909
05-15-08 10:33 murf Status assigned => feedback
======================================================================
More information about the asterisk-bugs
mailing list