I am trying to launch Asterisk on a different directory with the parameter 'C asterisk -vvvvvvvvvvvvvvvvvvgc -C /etc/asterisk1/asterisk.conf Parsing '/etc/asterisk1/extconfig.conf': Found Resetting translation matrix UUID system initiated Parsing /etc/asterisk1/asterisk.conf == Parsing '/etc/asterisk1/asterisk.conf': Found Not changing threadpool size since new size 0 is the same as current 0 gl_pathc 0 == Sorcery registered wizard 'bucket' == Sorcery registered wizard 'bucket_file' Cannot update type 'bucket' in module 'core' because it has no existing documentation! Failed to register 'bucket' object type in Bucket sorcery The debug level is 5, and so is the verbose level. The logger.conf has this line myDebugLog => notice,warning,error,debug,verbose,dtmf And it does not even get created. /etc/asterisk1/asterisk.conf has these lines astetcdir => /etc/asterisk1 astmoddir => /usr/lib/asterisk/modules astvarlibdir => /var/lib/asterisk1 astdbdir => /var/lib/asterisk1 astkeydir => /var/lib/asterisk1 astdatadir => /var/lib/asterisk1 astagidir => /var/lib/asterisk/agi-bin astspooldir => /var/spool/asterisk1 astrundir => /temp/run/asterisk1 astlogdir => /var/log/asterisk1 astsbindir => /usr/sbin All directories mentioned above do exist. Should I open a bug or there is something I am missing?
Matthew Jordan
2014-Jul-20 22:53 UTC
[asterisk-users] Asterisk 12 fails to launch with option -C
On Sun, Jul 20, 2014 at 6:47 AM, CDR <venefax at gmail.com> wrote:> I am trying to launch Asterisk on a different directory with the parameter 'C > > asterisk -vvvvvvvvvvvvvvvvvvgc -C /etc/asterisk1/asterisk.conf > > Parsing '/etc/asterisk1/extconfig.conf': Found > Resetting translation matrix > UUID system initiated > Parsing /etc/asterisk1/asterisk.conf > == Parsing '/etc/asterisk1/asterisk.conf': FoundThis means that yes, it parsed the config file you told it to parse.> Not changing threadpool size since new size 0 is the same as current 0 > gl_pathc 0 > == Sorcery registered wizard 'bucket' > == Sorcery registered wizard 'bucket_file' > Cannot update type 'bucket' in module 'core' because it has no > existing documentation! > Failed to register 'bucket' object type in Bucket sorcery > > The debug level is 5, and so is the verbose level.Nothing you've shown would indicate whether or not Asterisk should or should not have a particular debug/verbose level. You have started Asterisk with a particular verbosity; however, that level is ignored if your asterisk.conf file specifies a particular verbosity.> The logger.conf has this line > myDebugLog => notice,warning,error,debug,verbose,dtmf > > And it does not even get created.The operation of logger (and the parsing of logger.conf) has nothing to do with asterisk.conf, save for the location of the Asterisk log file directory.> /etc/asterisk1/asterisk.conf has these lines > astetcdir => /etc/asterisk1 > astmoddir => /usr/lib/asterisk/modules > astvarlibdir => /var/lib/asterisk1 > astdbdir => /var/lib/asterisk1 > astkeydir => /var/lib/asterisk1 > astdatadir => /var/lib/asterisk1 > astagidir => /var/lib/asterisk/agi-bin > astspooldir => /var/spool/asterisk1 > astrundir => /temp/run/asterisk1 > astlogdir => /var/log/asterisk1 > astsbindir => /usr/sbin > > All directories mentioned above do exist. > > Should I open a bug or there is something I am missing? >I suspect you have some configuration error or environment problem. The Asterisk Test Suite - which runs on every commit and nightly - makes extensive use of custom asterisk.conf files to sandbox instances of Asterisk that run concurrently. This runs against every branch of Asterisk and trunk. I do not think there is anything wrong with the '-C' option. -- Matthew Jordan Digium, Inc. | Engineering Manager 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at: http://digium.com & http://asterisk.org