Asterisk closes by itself - issue with modules?

Hello community, I am writing this post because I am at my wits’ end, so sorry for the… uhm, incongruences you may find.

I was in need of a SIP server, so I decided to install on-the-fly Asterisk 13. I encountered problems with the database, but the calls worked just fine. However, I decided to upgrade to Asterik 16 two days ago.
Bad, bad move.

Now I am running Asterisk 16.5.1 on a Bodhi Linux x64 (Ubuntu-based) virtual machine, but… it ends by itself:

Disconnected from Asterisk server
Asterisk cleanly ending (0).
Executing last minute cleanups

Tried the verbose mode, nothing comes up. The debug mode? Nothing at all.
Now, I opened the logs and… ta-dan! It’s something right from a horror movie.

[Sep 26 16:37:47] Asterisk 16.5.1 built by root @ apheniti-VirtualBox on a x86_64 running Linux on 2019-09-25 17:08:27 UTC
[Sep 26 16:37:47] NOTICE[3014] loader.c: 337 modules will be loaded.
[Sep 26 16:37:48] WARNING[3014] res_config_mysql.c: MySQL RealTime: No database user found, using 'asterisk' as default.
[Sep 26 16:37:48] WARNING[3014] res_config_mysql.c: MySQL RealTime: No database password found, using 'asterisk' as default.
[Sep 26 16:37:48] WARNING[3014] res_config_mysql.c: MySQL RealTime: No database host found, using localhost via socket.
[Sep 26 16:37:48] WARNING[3014] res_config_mysql.c: MySQL RealTime: No database name found, using 'asterisk' as default.
[Sep 26 16:37:48] WARNING[3014] res_config_mysql.c: MySQL RealTime: No database port found, using 3306 as default.
[Sep 26 16:37:48] WARNING[3014] res_config_mysql.c: MySQL RealTime: No database socket found (and unable to detect a suitable path).
[Sep 26 16:37:48] NOTICE[3014] res_config_ldap.c: No directory user found, anonymous binding as default.
[Sep 26 16:37:48] ERROR[3014] res_config_ldap.c: No directory URL or host found.
[Sep 26 16:37:48] ERROR[3014] res_config_ldap.c: Cannot load LDAP RealTime driver.
[Sep 26 16:37:48] ERROR[3014] res_config_pgsql.c: PostgreSQL RealTime: Failed to connect database asterisk on 127.0.0.1: 
[Sep 26 16:37:48] WARNING[3014] res_config_pgsql.c: PostgreSQL RealTime: Couldn't establish connection. Check debug.
[Sep 26 16:37:48] NOTICE[3014] cdr.c: CDR simple logging enabled.
[Sep 26 16:37:48] NOTICE[3014] res_smdi.c: No SMDI interfaces are available to listen on, not starting SMDI listener.
[Sep 26 16:37:48] WARNING[3014] res_phoneprov.c: Unable to find a valid server address or name.
[Sep 26 16:37:48] NOTICE[3014] chan_skinny.c: Configuring skinny from skinny.conf
[Sep 26 16:37:48] NOTICE[3075] chan_sip.c: Peer 'bodhi' is now Reachable. (1ms / 2000ms)
[Sep 26 16:37:48] ERROR[3014] chan_mobile.c: No Bluetooth devices found. Not loading module.
[Sep 26 16:37:48] ERROR[3014] ari/config.c: No configured users for ARI
[Sep 26 16:37:48] NOTICE[3075] chan_sip.c: Peer 'apheniti' is now Reachable. (1ms / 2000ms)
[Sep 26 16:37:48] NOTICE[3014] confbridge/conf_config_parser.c: Adding default_menu menu to app_confbridge
[Sep 26 16:37:48] WARNING[3014] cel_pgsql.c: CEL pgsql config file missing global section.
[Sep 26 16:37:48] NOTICE[3014] cdr_pgsql.c: cdr_pgsql configuration contains no global section, skipping module load.
[Sep 26 16:37:48] NOTICE[3014] cel_custom.c: No mappings found in cel_custom.conf. Not logging CEL to custom CSVs.
[Sep 26 16:37:48] NOTICE[3014] cdr_radius.c: Cannot load radiusclient-ng configuration file /etc/radiusclient-ng/radiusclient.conf.
[Sep 26 16:37:48] NOTICE[3014] cel_radius.c: Cannot load radiusclient-ng configuration file /etc/radiusclient-ng/radiusclient.conf.
[Sep 26 16:37:48] NOTICE[3014] cel_tds.c: cel_tds has no global category, nothing to configure.
[Sep 26 16:37:48] WARNING[3014] cel_tds.c: cel_tds module had config problems; declining load
[Sep 26 16:37:49] WARNING[3014] loader.c: Some non-required modules failed to load.
[Sep 26 16:37:49] ERROR[3014] loader.c: chan_mobile declined to load.
[Sep 26 16:37:49] ERROR[3014] loader.c: res_pjsip_transport_websocket declined to load.
[Sep 26 16:37:49] ERROR[3014] loader.c: cel_sqlite3_custom declined to load.
[Sep 26 16:37:49] ERROR[3014] loader.c: cdr_pgsql declined to load.
[Sep 26 16:37:49] ERROR[3014] loader.c: cdr_tds declined to load.
[Sep 26 16:37:49] ERROR[3014] loader.c: cdr_radius declined to load.
[Sep 26 16:37:49] ERROR[3014] loader.c: cdr_sqlite3_custom declined to load.
[Sep 26 16:37:49] ERROR[3014] loader.c: cel_radius declined to load.
[Sep 26 16:37:49] ERROR[3014] loader.c: cel_tds declined to load.

And the log repeats itself every couple of minutes.
Yeah, as I said: HORROR. MOVIE.

systemtcl asterisk restart

fails for timeout exceeded.

However, I suspect that my problems could arise also from the configuration of the two peers…
In other words, I have no guesses on how to begin resolve the problem and I really, really would appreciate some help.

Thanks.

If you suspect it is a module then I’d start first by “no loading” any module you don’t need. Especially ones that are spitting out errors, warnings, or even adverse notices on startup. This has the benefit of making Asterisk not only start faster, but should help you narrow down the problem.

It could be by doing the above your problem resolves itself since it may be possible that a module you are not using is missing a dependency, declines to load and then in turn Asterisk shuts down.

If however, the problem persists then it should be easier at least to locate which module is causing the problem as you now are dealing with less modules.

Second, you say it repeats. Nothing else in the log but the above repeating? Does Asterisk “fully boot”? What debug level is set? I’d turn debug and verbose way up. For instance, I’d put both at level 10 and see what else may show up.

1 Like

asterisk -c runs asterisk in the foreground, not as a daemon, so that you can run it once and observe where it crashes without having to run the start/stop routines and hunt through the logs. The startup output will be right there on your console. asterisk -cvvvvvvv to make it more verbose.

That, along with noload’ing modules until you get it to stay running, should help you find the culprit.

2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.