[asterisk-bugs] [Asterisk 0014831]: Issue starting Asterisk with LinuxHA
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Apr 24 14:14:38 CDT 2009
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=14831
======================================================================
Reported By: chris-mac
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 14831
Category: Resources/res_musiconhold
Reproducibility: always
Severity: minor
Priority: normal
Status: feedback
Asterisk Version: SVN
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.1
SVN Revision (number only!): 186527
Request Review:
======================================================================
Date Submitted: 2009-04-05 11:22 CDT
Last Modified: 2009-04-24 14:14 CDT
======================================================================
Summary: Issue starting Asterisk with LinuxHA
Description:
Just noticed strange behaviour of Music on Hold.
When I start asterisk for the first time (after the server was powered
on), and try to put a SIP call on hold, console shows:
DEBUG[5845]: res_musiconhold.c:726 get_mohbyname: Music on Hold class
'default' not found in memory
the following CLI command shows nothing:
asterisk -r -x "moh show classes"
Only after asterisk is restarted MoH works OK, and 'asterisk -r -x "moh
show classes"' shows:
--------------------
Class: default
Mode: files
Directory: /var/lib/asterisk/moh
--------------------
My musiconhold.conf:
----------------
[general]
cachertclasses=yes
[default]
mode=files
directory=/var/lib/asterisk/moh
----------------
Already tried with cachertclasses=yes/no with the same result.
Best regards,
Chris
======================================================================
----------------------------------------------------------------------
(0103758) chris-mac (reporter) - 2009-04-24 14:14
http://bugs.digium.com/view.php?id=14831#c103758
----------------------------------------------------------------------
Yes, Asterisk starts in the directory you call it from.
However I don't think this is a correct behaviour of a daemon process.
AFAIK all daemons should change their working directory to '/' (which
would fix this bug).
Please see mailing list discussion about this topic:
http://lists.digium.com/pipermail/asterisk-dev/2009-April/038048.html
Issue History
Date Modified Username Field Change
======================================================================
2009-04-24 14:14 chris-mac Note Added: 0103758
======================================================================
More information about the asterisk-bugs
mailing list