You have a configuration error most likely. Since this is Debian 10 (which is unfortunate) there is no asyncio.exceptions exception type so it doesn’t get handled cleanly. You need more of the log from /var/log/daemon.log. The log output from systemctl isn’t useful in these cases because it truncates stuff.
You really should run this in the foreground as allmon3 --debug until you actually have a working configuration.
sudo allmon3 --debug
DEBUG: (allmon3) config file is /etc/allmon3/allmon3.ini
DEBUG: (asl_allmon.node_configs) nodes_on_host: 1
DEBUG: (allmon3) web config file is /etc/allmon3/web.ini
INFO: (allmon3) no %s found; no menu data available
DEBUG: (allmon3) user_table file is /etc/allmon3/users
DEBUG: (asl_allmon.security) loaded 1 entries from /etc/allmon3/users
DEBUG: (asl_allmon.node_db) entering get_allmon_db()
INFO: (asl_allmon.node_db) Retrieving database from http://allmondb.allstarlink.org/
INFO: (asl_allmon.node_db) Updated node database in 0.92 seconds
DEBUG: (asl_allmon.node_db) exiting getAllMonDB()
DEBUG: (asl_allmon.node_db) entering set_my_info()
DEBUG: (asl_allmon.node_db) exiting set_my_info()
DEBUG: (allmon3) starting the main work loop
DEBUG: (allmon3) enter start_tasks()
INFO: (allmon3) starting status ws 1200@127.0.0.1 on port 16700
INFO: (allmon3) starting cmd ws 1200@127.0.0.1 on port 16701
INFO: (allmon3) starting allmon3 master ws on port 16080
INFO: (allmon3) starting node_db updater
DEBUG: (asl_allmon.allmon3_ws_status) enter node_status_main(1200)
DEBUG: (asl_allmon.ami_conn) asl_create_connection(failhard=True)
DEBUG: (asl_allmon.ami_conn) connect() using 127.0.0.1:5038
DEBUG: (asl_allmon.ami_conn) AIM version: Asterisk Call Manager/1.0
DEBUG: (asl_allmon.ami_conn) enter asl_cmd_response()
DEBUG: (asl_allmon.ami_conn) command >> ACTION: LOGIN USERNAME: admin SECRET: usgmrs EVENTS: 0 ActionID: 4db960a4-d0f1-41b0-8c2b-a44bb83c3622
DEBUG: (asl_allmon.ami_conn) response >> Response: Success ActionID: 4db960a4-d0f1-41b0-8c2b-a44bb83c3622 Message: Authentication accepted
DEBUG: (asl_allmon.ami_conn) Response: Success ActionID: 4db960a4-d0f1-41b0-8c2b-a44bb83c3622 Message: Authentication accepted
DEBUG: (asl_allmon.ami_conn) leaving asl_create_connection()
INFO: (asl_allmon.allmon3_ws_status) server listening on 0.0.0.0:16700
INFO: (asl_allmon.allmon3_ws_status) server listening on [::]:16700
INFO: (asl_allmon.allmon3_ws_status) broadcasting status for 1200 on port 16700
DEBUG: (asl_allmon.allmon3_ws_status) enter node_status_broadcast()
DEBUG: (asl_allmon.allmon3_ws_status) Node 1200: status_connections: 0
DEBUG: (asl_allmon.allmon3_ws_status) status asyncio.sleep(1)
INFO: (asl_allmon.allmon3_ws_cmd) server listening on 0.0.0.0:16701
INFO: (asl_allmon.allmon3_ws_cmd) server listening on [::]:16701
DEBUG: (allmon3) finally of start_tasks()
DEBUG: (allmon3) main finally
Traceback (most recent call last):
File “/usr/bin/allmon3”, line 95, in start_tasks
await asyncio.gather(*tasks)
File “/usr/lib/python3/dist-packages/asl_allmon/allmon3_server/init.py”, line 254, in main
await site.start()
File “/usr/local/lib/python3.7/dist-packages/aiohttp/web_runner.py”, line 128, in start
reuse_port=self._reuse_port,
File “/usr/lib/python3.7/asyncio/base_events.py”, line 1378, in create_server
% (sa, err.strerror.lower())) from None
OSError: [Errno 99] error while attempting to bind on address (‘::1’, 16080, 0, 0): cannot assign requested address
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File “/usr/bin/allmon3”, line 208, in
asyncio.run(start_tasks())
File “/usr/lib/python3.7/asyncio/runners.py”, line 43, in run
return loop.run_until_complete(main)
File “/usr/lib/python3.7/asyncio/base_events.py”, line 584, in run_until_complete
return future.result()
File “/usr/bin/allmon3”, line 97, in start_tasks
except asyncio.exceptions.CancelledError as e:
AttributeError: module ‘asyncio’ has no attribute ‘exceptions’
Well, there’s why interesting. Delete the line with ::1 and it should start. But if that’s a default thing in ASL2 that’s a problem. It looks like maybe it’s a half-set-up IPv6 network.
I’m not aware of any PC based Allstar Images other than ASL but if you happen to know any please let me know. and I will have no problems in giving it a try.
I am going to image this OS so in the Future I can resume where this one left off…
So just as a PSA, for people who find this later on… deleting the ::1 entry from /etc/hosts is NOT THE RIGHT FIX long-term. The address ::1 is the IPv6 equivalent of 127.0.0.1 from IPv4. In this particular case, when localhost is being resolved, the system believes IPv6 to be enabled however the network configuration is not enabling the address ::1 at boot.
A correctly configured network stack (and this is definitely the default) should look like this for the localhost adapter:
$ ip addr show dev lo
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
Note there is both a 127.0.0.1 and ::1 address. This has been the standard Linux configuration for a decade or more. If the system in question as IPv6 enabled + /etc/hosts points localhost to ::1 + missing ::1 address in combination, then any application that is IPv6 aware will have operational problems.