Allmon3 warnings and errors

Hey there-

I was trying to locate logs to see why a permanent connection I set up in my startup_macro was not up. In trying to find some sort of history of the connect/disconnect etc I started looking in the ASL3 cockpit logs section. Very cool, but I can't seem to find a lof of what you might see watching the CLI- things like connect, disconnect, etc. I stumbled on these allmon3 errors that were up at over 8000 by the time I looked at it. Odd thing is I never use allmon3, I use allscan for daily controlling and monitoring.https://allscan.info/

So, I logged into allmon3 and there is really nothing there and the interface is fine. 1- If anyone has suggestions as to what is going on I'd appreciate it. and 2- if you know where the logs for basic node operations is located let me know. Thx

Here is a sample of the log in question after restarting allmon3, and the 4 lines in question w warnings and errors are at the top:

11:29 PM
INFO: (asl_allmon.allmon3_ws_status) node: 48654 - sleeping for RETRY_INTERVAL of 15
allmon3
11:29 PM
WARNING: (asl_allmon.allmon3_ws_status) ami_conn socket problem for node 48654: No active connection for 127.0.0.1:5038:5038
allmon3
11:29 PM
ERROR: (asl_allmon.ami_parser) asl_cmd() message No active connection for 127.0.0.1:5038:5038
allmon3
11:29 PM
ERROR: (asl_allmon.ami_parser) asl_cmd() exception <class 'asl_allmon.ami_conn.AMIException'>
allmon3
11:28 PM
INFO: (asl_allmon.node_db) populated AllStarlink database
allmon3
11:28 PM
INFO: (asl_allmon.node_db) Updated node database in 0.92 seconds
allmon3
11:28 PM
INFO: (asl_allmon.allmon3_ws_status) broadcasting status for 48654 on port 16700
allmon3
11:28 PM
WARNING: (asl_allmon.ami_conn) connection failed to 127.0.0.1:5038:5038: [Errno -2] Name or service not known
allmon3
11:28 PM
INFO: (asl_allmon.node_db) Retrieving database from https://allmondb.allstarlink.org/
allmon3
11:28 PM
INFO: (allmon3) starting node_db updater
allmon3
11:28 PM
INFO: (allmon3) starting allmon3 master ws on port 16080
allmon3
11:28 PM
INFO: (allmon3) starting cmd ws 48654@127.0.0.1:5038 on port 16701
allmon3
11:28 PM
INFO: (allmon3) starting status ws 48654@127.0.0.1:5038 on port 16700
allmon3
11:28 PM
INFO: (allmon3) no /etc/allmon3/menu.ini found; no menu data available
allmon3
11:28 PM
INFO: (asl_allmon.web_configs) Binding sevices to all addresses
allmon3
11:28 PM
INFO: (asl_allmon.web_configs) Allmon3 websockets starting port is 16700
allmon3
11:28 PM
INFO: (asl_allmon.web_configs) Allmon3 Master HTTP port is 16080
allmon3
11:28 PM
Started allmon3.service - Allmon3 daemon.
systemd
11:28 PM
Starting allmon3.service - Allmon3 daemon...

This is an error in allmon3.ini where the ip address is set to "127.0.0.1:5038" instead of just 127.0.0.1.

However app_rpt logs are not available via Allmon3.

Thanks, I changed it to 127.0.0.1 and will look at the logs this eve. No allmon3 errors though on reboot so looks like it solved it.

Also, I was just looking for those logs anywhere, not via allmon3. At least I have something to look for now. I searched for apt in cockpit logs section but apt_rpt was not there. I'll keep digging.

Side note/question- In looking at errors I see the following and I was able to use cockpit to look and see the errors were generated from systemd-modules-load. I found more than one and opening them looked like gibberish. This is a good little learning exercise and can show me how to troubleshoot and resolve errors.

9:46 AM
bgscan simple: Failed to enable signal strength monitoring
wpa_supplicant
9:46 AM
nl80211: kernel reports: Registration to specific type not supported
wpa_supplicant
9:46 AM
Failed to find module 'dahdi_dummy'
systemd-modules-load
9:46 AM
Failed to find module 'dahdi_transcode'
systemd-modules-load
9:46 AM
Failed to find module 'dahdi'

Asterisk itself logs to /var/log/asterisk/messages. But what it logs is highly configurable with verbosity and debug levels for each module. I'd start with simply watching the console with asterisk -rvvvv to see if you get what you need there.