Still no logging in /var/log/asterisk/full on FreePBX 17

FreePBX Applications / Modules
1

I am finding that on a large number of our PBXes, calls are not being recorded in /var/log/asterisk/full. On the system that I am working on this morning, an asterisk -rx “logger reload” solved the issue for the first call and then it stopped logging again after that.

asterisk -rx “logger show channels”
Logger queue limit: 1000

Channel Type Formatter Status Configuration

/var/log/asterisk/fail2ban File default Enabled - NOTICE WARNING SECURITY
/var/log/asterisk/full File default Enabled - DEBUG NOTICE WARNING ERROR VERBOSE
Console default Enabled - DEBUG NOTICE WARNING ERROR VERBOSE

It seems similar to this, but this bug is reported as fixed. My system is fully up to date.

Sparse Logfiles - General Help - FreePBX Community Forums

fwconsole ma upgradeall
No repos specified, using: [standard,commercial,extended] from last GUI settings

Up to date.
Updating Hooks…Done

apt-get upgrade
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
Calculating upgrade… Done
The following packages were automatically installed and are no longer required:
libdaxctl1 libndctl6 libpmem1
Use ‘apt autoremove’ to remove them.
The following packages have been kept back:
freepbx17 libnode-dev libnode108 linux-image-amd64 node-minipass node-postcss node-serialize-javascript nodejs
0 upgraded, 0 newly installed, 0 to remove and 8 not upgraded.

2

Does it start working after “fwconsole chown”?

3

I’m having exactly the same problem. The bug is that the GUI isn’t sending proper commands to Asterisk.

If you do a /sbin/asterisk -r

then do

core show settings

then it will dump the settings in Asterisk, and among them you can see:

.

.

.

Maximum calls:               Not set
Maximum open file handles:   1048576
Root console verbosity:      0
Current console verbosity:   0
Debug level:                 0
Trace level:                 0
Dump core on crash:          No
Core dump file:              core

.

.

.

While at exactly the same time you can go to Settings, Asterisk Logfile Settings, Log Files, in FreePBX and see that Debug is set to on.

Note that according to:

Collecting Debug Information - Asterisk Documentation

core set debug is a number NOT an on/off. However, in the dropdown in FreePBX, only the verbosity dropdown has a number.

Clearly there’s been some changes in Asterisk debugging which were not updated in FreePBX’s settings.

My workaround is to only use FreePBX, Reports, System Logfiles as a sort of browser for the log file, and turn on and off debugging from the Asterisk command line

5

Can you please try the below comment mentioned logfiles module and steps and let us know the result. Thanks

Regards,
Kapil

6

I was already running the latest version 17.0.3.5. I went ahead and updated everything that’s installed and set Verbose to 3 and did an apt update and apt upgrade at the command prompt then rebooted the PBX for good measure. Maybe the problem is that the installation default for Verbose is “on” instead of “3”

Yes, this puts a bit more in the log. But there are no numbers in the debug dropdown just on or off.

8

I changed the Log File Setting for full from “On” to “3” and logging is working right now. I tried a bit later and it stayed working

Why was the bug closed?

9

How do I script this change so I don’t have to log into each PBX (I have a lot) to change it?

10

That is due to the fact that only the verbose option can take an integer value. None of the other options have that.

11

That is not the case.

At the Asterisk command line you can do

core set debug 1

core set debug 2

core set debug 3

and so on until level 10 is reached.

core set debug 0

turns it off.

I understand the confusion. Most online docs on debugging Asterisk are incorrect as it appears there’s been vast changes in debug setting in recent versions.

12

Those are in the console and not related to the actual logger.conf file or its settings. Did you not read the documents I linked to?