System updates gets exception even after reboot

FreePBX
103

Ok, and it turns out that I’m still having some problems too. DAHDi now consistently starts on boot (so far, anyway), but fwconsole restart has a 50/50 chance of throwing a dahdi error:

[root@freepbx ~]# fwconsole restart
Running FreePBX shutdown...

Stopping RestApps Server
Stopped RestApps Server
Stopping UCP Node Server
[>---------------------------] 1 sec
Stopped UCP Node Server
Stopping Chat Server
Stopped Chat Server
Zulu Server is not running
Shutting down Asterisk Gracefully. Will forcefully kill after 30 seconds.
Press C to Cancel
Press N to shut down NOW
[============================] 2 secs
Wanrouter: No valid Sangoma Hardware found, if you have no Sangoma cards this is OK
Stopping DAHDi for Digium Cards
DAHDi Stopped
Queue Callback Server is not running
Running FreePBX startup...
Running Asterisk pre from Dahdiconfig module
Wanrouter: No valid Sangoma Hardware found, if you have no Sangoma cards this is OK
Starting DAHDi for Digium Cards
DAHDi Failed: The command "/etc/init.d/dahdi start" failed.

Exit Code: 1(General error)

Working directory: /root

Output:
================
Starting dahdi (via systemctl):  [FAILED]


Error Output:
================
Job for dahdi.service failed because the control process exited with error code. See "systemctl status dahdi.service" and "journalctl -xe" for details.

Running Asterisk pre from Firewall module
Running Asterisk pre from Sysadmin module
Running Sysadmin Hooks
Restarting fail2ban
fail2ban Restarted
Updating License Information for 58918804
Checking Vpn server
Starting Asterisk...
[============================] 2 secs
Asterisk Started
Running Asterisk post from Dahdiconfig module
Running Asterisk post from Endpoint module
Running Asterisk post from Pagingpro module
Running Asterisk post from Restapps module
Starting RestApps Server...
[>---------------------------] 1 sec
Started RestApps Server. PID is 6307
Running Asterisk post from Ucp module
Starting UCP Node Server...
[>---------------------------] 1 sec
Started UCP Node Server. PID is 6449
Running Asterisk post from Vqplus module
RestApps is not licensed.
Running Asterisk post from Xmpp module
Starting Chat Server...
[>---------------------------] 1 sec
Started Chat Server. PID is 6537
Running Asterisk post from Zulu module
This product is not licensed
[root@freepbx ~]#

Once it has failed like this, a reboot is required to get it going again.

104

Now you see why I am so insistent about testing things multiple times, under different conditions… :wink:

There seems to be quite a few things involved in having this works correctly consistently…

In my case I think timing might be in for some things, in yours I guess we should

See “systemctl status dahdi.service” and “journalctl -xe” for details.

to see if there is anything we can do about your new problem…

Good luck and have a nice day!

Nick

105

2 posts were split to a new topic: Warnings in asterisk console

106

yeah . I had a look at those errors

systemctl status dahdi.service

[root@freepbx ~]# systemctl status dahdi.service
● dahdi.service - LSB: DAHDI kernel modules
   Loaded: loaded (/etc/rc.d/init.d/dahdi; bad; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sun 2017-10-08 02:13:42 BST; 27s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 3566 ExecStart=/etc/rc.d/init.d/dahdi start (code=exited, status=1/FAILURE)

Oct 08 02:13:42 freepbx.mydomain.co.uk dahdi[3566]: Selected signaling not supported
Oct 08 02:13:42 freepbx.mydomain.co.uk dahdi[3566]: Possible causes:
Oct 08 02:13:42 freepbx.mydomain.co.uk dahdi[3566]: FXS signaling is being used on a FXS interface (use a FXO signaling variant)
Oct 08 02:13:42 freepbx.mydomain.co.uk dahdi[3566]: RBS signaling is being used on a E1 CCS span
Oct 08 02:13:42 freepbx.mydomain.co.uk dahdi[3566]: Signaling is being assigned to channel 16 of an E1 CAS span
Oct 08 02:13:42 freepbx.mydomain.co.uk dahdi[3566]: [FAILED]
Oct 08 02:13:42 freepbx.mydomain.co.uk systemd[1]: dahdi.service: control process exited, code=exited status=1
Oct 08 02:13:42 freepbx.mydomain.co.uk systemd[1]: Failed to start LSB: DAHDI kernel modules.
Oct 08 02:13:42 freepbx.mydomain.co.uk systemd[1]: Unit dahdi.service entered failed state.
Oct 08 02:13:42 freepbx.mydomain.co.uk systemd[1]: dahdi.service failed.
[root@freepbx ~]#:

journalctl -xe

Oct 08 02:13:42 freepbx.mydomain.co.uk systemd[1]: Starting LSB: DAHDI kernel modules...
-- Subject: Unit dahdi.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit dahdi.service has begun starting up.
Oct 08 02:13:42 freepbx.mydomain.co.uk dahdi[3566]: Loading DAHDI hardware modules:
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: dahdi: Version: 2.11.1
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: dahdi: Telephony Interface Registered on major 196
Oct 08 02:13:42 freepbx.mydomain.co.uk dahdi[3566]: wct4xxp:  [  OK  ]
Oct 08 02:13:42 freepbx.mydomain.co.uk dahdi[3566]: wcte43x:  [  OK  ]
Oct 08 02:13:42 freepbx.mydomain.co.uk dahdi[3566]: wcte12xp:  [  OK  ]
Oct 08 02:13:42 freepbx.mydomain.co.uk dahdi[3566]: wcte13xp:  [  OK  ]
Oct 08 02:13:42 freepbx.mydomain.co.uk dahdi[3566]: wct1xxp:  [  OK  ]
Oct 08 02:13:42 freepbx.mydomain.co.uk dahdi[3566]: wcte11xp:  [  OK  ]
Oct 08 02:13:42 freepbx.mydomain.co.uk dahdi[3566]: wctdm24xxp:  [  OK  ]
Oct 08 02:13:42 freepbx.mydomain.co.uk dahdi[3566]: wcaxx:  [  OK  ]
Oct 08 02:13:42 freepbx.mydomain.co.uk dahdi[3566]: wcfxo:  [  OK  ]
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: dahdi: Warning: Span WCTDM/4 didn't specify a spantype. Please fix driver!
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: Freshmaker version: 19
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 01 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 02 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 03 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 04 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 05 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 06 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 07 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 08 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 09 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 0a != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 0b != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 0c != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 0d != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 0e != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 0f != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 10 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 11 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 12 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 13 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 14 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 15 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 16 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 17 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 18 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 19 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 1a != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 1b != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 1c != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 1d != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 1e != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 1f != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 20 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 21 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 22 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 23 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 24 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 25 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 26 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 27 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 28 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 29 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 2a != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 2b != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 2c != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 2d != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 2e != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 2f != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 30 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 31 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 32 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 33 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 34 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 35 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 36 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 37 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 38 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 39 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 3a != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 3b != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 3c != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 3d != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 3e != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 3f != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 40 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 41 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 42 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 43 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 44 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 45 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 46 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 47 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 48 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 49 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 4a != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 4b != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 4c != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 4d != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 4e != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 4f != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 50 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 51 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 52 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 53 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 54 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 55 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 56 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 57 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 58 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 59 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 5a != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 5b != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 5c != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 5d != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 5e != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 5f != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 60 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 61 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 62 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 63 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 64 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 65 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 66 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 67 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 68 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 69 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 6a != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 6b != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 6c != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 6d != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 6e != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 6f != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 70 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 71 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 72 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 73 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 74 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 75 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 76 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 77 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 78 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 79 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 7a != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 7b != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 7c != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 7d != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 7e != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 7f != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 80 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 81 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 82 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 83 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 84 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 85 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 86 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 87 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 88 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 89 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 8a != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 8b != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 8c != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 8d != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 8e != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 8f != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 90 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 91 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 92 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 93 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 94 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 95 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 96 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 97 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 98 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 99 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 9a != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 9b != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 9c != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 9d != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 9e != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: 9f != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: a0 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: a1 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: a2 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: a3 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: a4 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: a5 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: a6 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: a7 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: a8 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: a9 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: aa != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: ab != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: ac != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: ad != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: ae != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: af != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: b0 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: b1 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: b2 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: b3 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: b4 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: b5 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: b6 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: b7 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: b8 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: b9 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: ba != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: bb != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: bc != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: bd != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: be != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: bf != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: c0 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: c1 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: c2 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: c3 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: c4 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: c5 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: c6 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: c7 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: c8 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: c9 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: ca != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: cb != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: cc != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: cd != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: ce != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: cf != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: d0 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: d1 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: d2 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: d3 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: d4 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: d5 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: d6 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: d7 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: d8 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: d9 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: da != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: db != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: dc != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: dd != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: de != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: df != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: e0 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: e1 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: e2 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: e3 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: e4 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: e5 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: e6 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: e7 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: e8 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: e9 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: ea != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: eb != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: ec != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: ed != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: ee != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: ef != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: f0 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: f1 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: f2 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: f3 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: f4 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: f5 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: f6 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: f7 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: f8 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: f9 != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: fa != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: fb != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: fc != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: fd != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: fe != 00
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: Freshmaker failed register test
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: dahdi: disable_span: span 1
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: wctdm: probe of 0000:03:00.0 failed with error -5
Oct 08 02:13:42 freepbx.mydomain.co.uk dahdi[3566]: wctdm:  [  OK  ]
Oct 08 02:13:42 freepbx.mydomain.co.uk 'dahdi_handle_device'[3591]: add: /devices/pci0000:00/0000:00:1e.0/0000:03:00.0/pci:0000:03:00.0
Oct 08 02:13:42 freepbx.mydomain.co.uk dahdi[3566]: wcb4xxp:  [  OK  ]
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: dahdi_transcode: Loaded.
Oct 08 02:13:42 freepbx.mydomain.co.uk 'dahdi_handle_device'[3595]: auto_assign_spans=1. Skip /devices/pci0000:00/0000:00:1e.0/0000:03:00.0/pci:0000:03:00.0
Oct 08 02:13:42 freepbx.mydomain.co.uk dahdi[3566]: wctc4xxp:  [  OK  ]
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: INFO-xpp: revision Unknown MAX_XPDS=64 (8*8)
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: INFO-xpp: FEATURE: with PROTOCOL_DEBUG
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: INFO-xpp: FEATURE: with sync_tick() from DAHDI
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: INFO-xpp_usb: revision Unknown
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: usbcore: registered new interface driver xpp_usb
Oct 08 02:13:42 freepbx.mydomain.co.uk dahdi[3566]: xpp_usb:  [  OK  ]
Oct 08 02:13:42 freepbx.mydomain.co.uk dahdi[3566]: r1t1:  [  OK  ]
Oct 08 02:13:42 freepbx.mydomain.co.uk 'dahdi_span_config'[3605]: add: /devices/pci0000:00/0000:00:1e.0/0000:03:00.0/pci:0000:03:00.0/span-1
Oct 08 02:13:42 freepbx.mydomain.co.uk 'dahdi_span_config'[3608]: auto_assign_spans=1. Skip /devices/pci0000:00/0000:00:1e.0/0000:03:00.0/pci:0000:03:00.0/span-1
Oct 08 02:13:42 freepbx.mydomain.co.uk dahdi[3566]: rxt1:  [  OK  ]
Oct 08 02:13:42 freepbx.mydomain.co.uk dahdi[3566]: rcbfx:  [  OK  ]
Oct 08 02:13:42 freepbx.mydomain.co.uk 'dahdi_span_config'[3618]: offline: /devices/pci0000:00/0000:00:1e.0/0000:03:00.0/pci:0000:03:00.0/span-1
Oct 08 02:13:42 freepbx.mydomain.co.uk 'dahdi_handle_device'[3632]: remove: /devices/pci0000:00/0000:00:1e.0/0000:03:00.0/pci:0000:03:00.0
Oct 08 02:13:42 freepbx.mydomain.co.uk 'dahdi_handle_device'[3634]: D: Running '/usr/share/dahdi/handle_device.d/10-span-types'
Oct 08 02:13:42 freepbx.mydomain.co.uk 'dahdi_handle_device'[3634]: D: Running '/usr/share/dahdi/handle_device.d/20-span-assignments'
Oct 08 02:13:42 freepbx.mydomain.co.uk dahdi[3566]: Running dahdi_cfg:  DAHDI_CHANCONFIG failed on channel 1: Invalid argument (22)
Oct 08 02:13:42 freepbx.mydomain.co.uk dahdi[3566]: Selected signaling not supported
Oct 08 02:13:42 freepbx.mydomain.co.uk dahdi[3566]: Possible causes:
Oct 08 02:13:42 freepbx.mydomain.co.uk dahdi[3566]: FXS signaling is being used on a FXS interface (use a FXO signaling variant)
Oct 08 02:13:42 freepbx.mydomain.co.uk dahdi[3566]: RBS signaling is being used on a E1 CCS span
Oct 08 02:13:42 freepbx.mydomain.co.uk dahdi[3566]: Signaling is being assigned to channel 16 of an E1 CAS span
Oct 08 02:13:42 freepbx.mydomain.co.uk kernel: dahdi_ioctl_chanconfig: No channel for number 1
Oct 08 02:13:42 freepbx.mydomain.co.uk dahdi[3566]: [FAILED]
Oct 08 02:13:42 freepbx.mydomain.co.uk systemd[1]: dahdi.service: control process exited, code=exited status=1
Oct 08 02:13:42 freepbx.mydomain.co.uk systemd[1]: Failed to start LSB: DAHDI kernel modules.
-- Subject: Unit dahdi.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit dahdi.service has failed.
--
-- The result is failed.
Oct 08 02:13:42 freepbx.mydomain.co.uk systemd[1]: Unit dahdi.service entered failed state.
Oct 08 02:13:42 freepbx.mydomain.co.uk systemd[1]: dahdi.service failed.
108

The problem seems common, even for supposedly working configs it seems…

If you don’t mind I will take a look at this tomorrow, both my head and my eyes are giving me signs it’s time to take a break…

Gals/guys if you can help him, go ahead!

Good luck and have a nice day!

Nick

109

Ok. New day, new idea.

I’ve removed the TDM410P PCI card from my machine, re-seated all four FXO / FXS daughter cards, and plugged it back in again.I seem to be getting much more reliable results now. I’ve done about 5 reboots, and after each reboot I’ve done about 5 fwconsole restarts and it’s not missed a beat… yet. echo $? is now consistently reporting ‘0’ to both service dahdi status & systemctl status dahdi. It wasn’t doing this before I re-seated the card - one was reporting ‘3’, but I can’t remember which. Let’s hope I’m not talking too soon!

110

Another thing to consider is that not only wanpipe should be off in chkconfig but also Dahdi has fwconsole starts then both.

111

Yes I think that is the case:

[root@freepbx ~]# chkconfig --list | grep -i dahdi

Note: This output shows SysV services only and does not include native
      systemd services. SysV configuration data might be overridden by native
      systemd configuration.

      If you want to list systemd services use 'systemctl list-unit-files'.
      To see services enabled on particular target use
      'systemctl list-dependencies [target]'.

[root@freepbx ~]# chkconfig --list | grep -i wanrouter

Note: This output shows SysV services only and does not include native
      systemd services. SysV configuration data might be overridden by native
      systemd configuration.

      If you want to list systemd services use 'systemctl list-unit-files'.
      To see services enabled on particular target use
      'systemctl list-dependencies [target]'.

wanrouter       0:off   1:off   2:off   3:off   4:off   5:off   6:off
[root@freepbx ~]#
112

Everything still seems to be working fine, but I still see some odd behaviour with dahdi status.

If I stop dahdi using either ‘service dahdi stop’ or ‘systemctl stop dahdi’, then dahdi does seem to stop correctly. However a ‘service dadhi status’ will incorrectly report status ‘0’, whereas a ‘systemctl status dahdi’ will correctly report status ‘3’ to echo $? This doesn’t seem to be having an impact on fwconsole restarts any longer.

113

I’m confused. If you turn them both off in chkconfig do you have to do anything else?

114

I only had to turn wanrouter off in chkconfig. DAHDi was never turned on (or at least, I don’t think it was), so I didn’t make any changes there…

I don’t need to do anything further now to get DAHDi started on boot.

115

Hi!

On my system it is accessible through chkconfig but off…

If I turn off wanrouter at boot for my Sangoma A200 card which does use the Wanpipe drivers that perl program in which I had changed the boot order (/etc/wanpipe/wancfg_zaptel/wancfg_zaptel.pl) unfortunately turns it on again after a reboot so it only last one time…

It looks like there might be a way to pass a switch to that program so that it doesn’t do that (I wish I was better at perl at knew that runs what in those drivers) but I have not found where it is yet…

Have a nice day!

Nick

116

Hi!

I wonder if this problem (and the other one you mentioned yesterday which requires a reboot, were not always present.

Did you ever do that many restarts in the past with FreePBX 14 and, more importantly, FreePBX 13?

Good luck and have a nice day!

Nick

117

Hi!

For him, dahdi doesn’t even show up as a service he can start so it’s essentially off and turning wanrouter off fixes things completely for him.

For me, I see dahdi but it’s off and turning wanrouter off works for one time until /etc/wanpipe/wancfg_zaptel/wancfg_zaptel.pl turn it on again in config_boot_linux().

It looks like everything is absolutely fine for my system when wanrouter if off (and my system boots even faster than ever before) but I would need to do more exhaustive tests to make sure of it… Those tests I have not done I am focusing on trying to find a way to turn off that config_boot_linux() without modifying the script which seems to be possible.

Andrew, is it documented somewhere where this can be turned off by any chance? It would be a much better use of my time if I could focus on making sure turning off wanrouter at boot works consistently for a Sangoma card as well?

Thank you and have a nice day!

Nick

118

OK, I found where the config_boot_linux() which is causing me problems is called from (I had not initially realized there were multiple calls to it) and on a Linux system it is called unconditionally with no way of turning it off so I commented it out…

(It is on line 504 of /etc/wanpipe/wancfg_zaptel/wancfg_zaptel.pl with the version of Wanpipe I have…)

Since commenting out that line didn’t remove the chkconfig on entry I disabled it one last time with

chkconfig wanrouter off

Everything seems to work perfectly and consistently and my system has already gone quite a few reboots ad things are always correctly initialized…

I only have two small problems which occasionally appear when I SSH to my system and for at least one of them I believe I know the cause…

One of them is this:

Exception: SQLSTATE[HY000] [2002] No such file or directory::SQLSTATE[HY000] [2002] No such file or directory in file /var/www/html/admin/libraries/utility.functions.php on line 204
Stack trace:
  1. Exception->() /var/www/html/admin/libraries/utility.functions.php:204
  2. die_freepbx() /var/www/html/admin/libraries/BMO/Database.class.php:154
  3. PDOException->() /var/www/html/admin/libraries/BMO/Database.class.php:149
  4. PDO->__construct() /var/www/html/admin/libraries/BMO/Database.class.php:149
  5. FreePBX\Database->__construct() /var/www/html/admin/libraries/BMO/FreePBX.class.php:69
  6. FreePBX->__construct() /var/www/html/admin/bootstrap.php:151
  7. require_once() /etc/freepbx.conf:9
  8. include_once() /var/lib/asterisk/bin/fwconsole:12
Exception: SQLSTATE[HY000] [2002] No such file or directory::SQLSTATE[HY000] [2002] No such file or directory in     file /var/www/html/admin/libraries/utility.functions.php on line 204
Stack trace:
  1. Exception->() /var/www/html/admin/libraries/utility.functions.php:204
  2. die_freepbx() /var/www/html/admin/libraries/BMO/Database.class.php:154
  3. PDOException->() /var/www/html/admin/libraries/BMO/Database.class.php:149
  4. PDO->__construct() /var/www/html/admin/libraries/BMO/Database.class.php:149
  5. FreePBX\Database->__construct() /var/www/html/admin/libraries/BMO/FreePBX.class.php:69
  6. FreePBX->__construct() /var/www/html/admin/bootstrap.php:151
  7. require_once() /etc/freepbx.conf:9
  8. include_once() /var/lib/asterisk/bin/fwconsole:12

(Yep, it does appear twice…)

I believe this is from the motd-like message we see when we remote our systems…

I believe this happens because now that the boot is much faster I am sometimes able to remote my system before MariaDB is up. This FreePBX code is pretty unhappy with that and complains…

The other is a complaint from System Admin about not being able to do a mkdir…

I guess this too could be caused by database access before MariaDB is up…

The query to get something needed for this mkdir most likely fails and the path to create improperly initialized and mkdir is unhappy with whatever it got asked to create…

I asked myself why are the Wanpipe scripts requiring to be started at boot since it causes so much problems and then it hit me…

Just like those drivers are not required to use their DAHDI compatibility mode because they support other means of being talked to, what they would be used with it not assumed either…

We use it with FreePBX/Asterisk but the drivers/cards could be used with something else so not depending on that something else to later initialize the drivers by doing it during boot is a good idea.

There is now a problem with starting them before network is up but except for this, it looks like there are use cases where starting wanrouter at boot is a good thing…

Now it sounds to me that something needs to be added to those drivers so that it possible to configure them not to setup things so that they start at boot when used with FreePBX.

In the mean time, I did this:

if ($os_type_list =~ m/FreeBSD/){
        config_boot_freebsd();
} else {
#       config_boot_linux();
}

(ie comment out config_boot_linux() at line 504 of /etc/wanpipe/wancfg_zaptel/wancfg_zaptel.pl with the version of Wanpipe I have…)

to address the specific problem I have…

I will keep you posted but right not this seems to have done the trick… It did make me uncover what appears to be a much smaller problem with the motd-like message when I remote my system but that seems to be caused by trying to access the database before it is up…

Have a nice day!

Nick

119

That looks very similar to my problem!

120

It’s the fact that MariaDB isn’t fully booted yes. MariaDB is reporting that error. If you wait a bit longer to login the error won’t be present but MariaDB is still starting and then fwconsole starts right after that.

121

LOL, I got brought back a little later in this thread and had not noticed it…

As far as I know this is caused by remoting the system before MariaDB has had a chance to start…

When we remote the system we get a motd-like notice which apparently accesses the database…

I believe that if you remote your system before MariaDB has finished starting up (which seems to be easier now, at least in my case because the boot is so much faster), you get that error message…

Eventually MariaDB starts by itself later in the boot process so you only get this if you are fast enough to remote into your system before the boot process has completed enough…

I guess a check could be added to see if the database is up before trying to access that motd-like message…

Have a nice day!

Nick

122

I have today gone to my FreePBX 14.0.1.4 machine and done my weekly maintenance of Admin - Updates and hit the System Updates and I have been presented with a list of errors the first of which is:

RPM command errored, tried to run '/usr/bin/rpm -q --queryformat “%{VERSION}.%{RELEASE}\n” alsa-lib.x86_64 audit.x86_64 audit-libs.x86_64 authconfig.x86_64 bash.x86_64 bind-libs.x86_64 bind-libs-lite.x86_64 bind-license.noarch bind-utils.x86_64 binutils.x86_64 biosdevname.x86_64 bluez-libs.x86_64 boost-filesystem.x86_64 boost-program-options.x86_64 boost-system.x86_64 boost-thread.x86_64 btrfs-progs.x86_64 ca-certificates.noarch cairo.x86_64 chkconfig.x86_64 chrony.x86_64 copy-jdk-configs.noarch cpio.x86_64 cpp.x86_64 cronie.x86_64 cronie-noanacron.x86_64 cryptsetup.x86_64 cryptsetup-libs.x86_64 cups-libs.x86_64 curl.x86_64 cyrus-sasl-lib.x86_64 cyrus-sasl-plain.x86_64 device-mapper.x86_64 device-mapper-event.x86_64 device-mapper-event-libs.x86_64 device-mapper-libs.x86_64 device-mapper-multipath.x86_64 device-mapper-multipath-libs.x86_64 device-mapper-persistent-data.x86_64 dhcp-common.x86_64 dhcp-libs.x86_64 dmidecode.x86_64 dnsmasq.x86_64 dos2unix.x86_64 dracut.x86_64 dracut-network.x86_64 e2fsprogs.x86_64 e2fsprogs-libs.x86_64 efibootmgr.x86_64 efivar-libs.x86_64 elfutils-libelf.x86_64 elfutils-libs.x86_64 ethtool.x86_64 fcoe-utils.x86_64 fipscheck.x86_64 fipscheck-lib.x86_64 firewalld.noarch firewalld-filesystem.noarch fontconfig.x86_64 freeradius.x86_64 freetype.x86_64 fuse.x86_64 fuse-libs.x86_64 gcc.x86_64 gcc-c++.x86_64 gdk-pixbuf2.x86_64 gettext.x86_64 gettext-libs.x86_64 gfs2-utils.x86_64 ghostscript.x86_64 glib2.x86_64 glibc.x86_64 glibc-common.x86_64 glibc-devel.x86_64 glibc-headers.x86_64 glibmm24.x86_64 gmp.x86_64 gnutls.x86_64 gobject-introspection.x86_64 grep.x86_64 grub2.x86_64 grub2-tools.x86_64 grubby.x86_64 gzip.x86_64 harfbuzz.x86_64 httpd.x86_64 httpd-tools.x86_64 hwdata.x86_64 initscripts.x86_64 iproute.x86_64 iprutils.x86_64 ipset.x86_64 ipset-libs.x86_64 iptables.x86_64 iptables-services.x86_64 iputils.x86_64 irqbalance.x86_64 iscsi-initiator-utils.x86_64

Am I the only one and is it possible to fix this issue?

Any help would be greatly appreciated.

123

After installing a standby machine with Freepbx using a copy of the downloaded ISO from today I get excatly the same issue so I am certain this is nothing to do with my equipment or my install and I find it incredible that nobody else has encountered the issue?