mskenderian Posted August 17, 2022 Report Share Posted August 17, 2022 I am trying to migrate a server from ubuntu to debian. Install Debian, used vodia script to install. change the install script to use the same version and the current running PBX. which is 68.0. tried (it failed.): VERSION=68.0.0 tried (success): VERSION=68.0 but now it wont start, tried: /etc/init.d/pbx restart output: Shutting down PBX daemon: Starting PBX daemon sudo netstat -tulpn | grep LISTEN tcp 0 0 0.0.0.0:5061 0.0.0.0:* LISTEN 42155/pbxctrl tcp 0 0 0.0.0.0:2345 0.0.0.0:* LISTEN 42155/pbxctrl tcp 0 0 0.0.0.0:2346 0.0.0.0:* LISTEN 42155/pbxctrl tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 42155/pbxctrl tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1808/sshd: /usr/sbi tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 1122/exim4 tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 42155/pbxctrl tcp 0 0 0.0.0.0:5060 0.0.0.0:* LISTEN 42155/pbxctrl tcp6 0 0 :::5061 :::* LISTEN 42155/pbxctrl tcp6 0 0 :::2345 :::* LISTEN 42155/pbxctrl tcp6 0 0 :::2346 :::* LISTEN 42155/pbxctrl tcp6 0 0 :::80 :::* LISTEN 42155/pbxctrl tcp6 0 0 :::22 :::* LISTEN 1808/sshd: /usr/sbi tcp6 0 0 ::1:25 :::* LISTEN 1122/exim4 tcp6 0 0 :::443 :::* LISTEN 42155/pbxctrl tcp6 0 0 :::10050 :::* LISTEN 849/zabbix_agent2 tcp6 0 0 :::5060 :::* LISTEN 42155/pbxctrl it is running but cant access web gui. where can i see logs? and i just noticed "/etc/init.d/pbx status" doesnt work. it runs the command "checkproc pbx && echo OK || echo No process" debian or ubuntu doesnt have checkproc, maybe change this to pgrep or pidof Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted August 17, 2022 Report Share Posted August 17, 2022 You can always see what is out there with ./pbxctrl --help. For example, if you want to run it just from the shell without any daemon stuff, you can start it with ./pbxctrl --no-daemon --log 9 which usually will give you an abundance of information of what is going on. Quote Link to comment Share on other sites More sharing options...
mskenderian Posted August 17, 2022 Author Report Share Posted August 17, 2022 2 minutes ago, Vodia PBX said: You can always see what is out there with ./pbxctrl --help. For example, if you want to run it just from the shell without any daemon stuff, you can start it with ./pbxctrl --no-daemon --log 9 which usually will give you an abundance of information of what is going on. ok i also tried to install the newest version, same issue. I started a new VPS, same issue, i have install vodia many times no issues, i dont know what is going on. /usr/local/pbx/pbxctrl --no-daemon --log 9 Starting up [1] 20220817144343: Starting up version 68.0.18 [7] 20220817144343: Checked recording timestamps [7] 20220817144343: Found Interface lo with IP 127.0.0.1/255.0.0.0 [7] 20220817144343: Found Interface enp1s0 with IP 45.32.86.29/255.255.252.0 [1] 20220817144343: Adding DNS server 108.61.10.10 to the dns server list [1] 20220817144343: Adding DNS server [2001:19f0:300:1704::6] to the dns server list [7] 20220817144343: Loaded wakeup list [7] 20220817144343: Loaded certificates [7] 20220817144343: Refreshed license [7] 20220817144343: Loaded buttons [8] 20220817144343: Scheduler precision is 0 us [1] 20220817144343: Working Directory is /root [5] 20220817144343: Starting threads [7] 20220817144343: Found Interface lo with IP 127.0.0.1/255.0.0.0 [7] 20220817144343: Found Interface enp1s0 with IP 45.32.86.29/255.255.252.0 [8] 20220817144343: No from address for sending text email [7] 20220817144343: TCP(IPv4): Opening socket on 0.0.0.0:80 [7] 20220817144343: TCP(IPv6): Opening socket on [::]:80 [7] 20220817144343: TCP(IPv4): Opening socket on 0.0.0.0:443 [7] 20220817144343: TCP(IPv6): Opening socket on [::]:443 [7] 20220817144343: TCP(IPv4): Opening socket on 0.0.0.0:2345 [7] 20220817144343: TCP(IPv6): Opening socket on [::]:2345 [7] 20220817144343: TCP(IPv4): Opening socket on 0.0.0.0:2346 [7] 20220817144343: TCP(IPv6): Opening socket on [::]:2346 [7] 20220817144343: TCP(IPv4): Opening socket on 0.0.0.0:5060 [5] 20220817144343: Set scheduling priority to 1 [7] 20220817144343: TCP(IPv6): Opening socket on [::]:5060 [5] 20220817144343: Set process affinity to 1 [7] 20220817144343: UDP (IPv4): Opening socket on 0.0.0.0 [7] 20220817144343: TCP(IPv4): Opening socket on 0.0.0.0:5061 [7] 20220817144343: TCP(IPv6): Opening socket on [::]:5061 [7] 20220817144343: UDP (IPv4): Opening socket on 0.0.0.0:161 [7] 20220817144343: UDP (IPv6): Opening socket on [::]:161 [7] 20220817144343: UDP (IPv4): Opening socket on 0.0.0.0:514 [7] 20220817144343: UDP (IPv6): Opening socket on [::]:514 [7] 20220817144343: UDP (IPv4): Opening socket on 0.0.0.0:5060 [4] 20220817144343: Join multicast group on address 0.0.0.0 [8] 20220817144343: Joined multicast group 224.0.1.75 [7] 20220817144343: UDP (IPv6): Opening socket on [::]:5060 [7] 20220817144343: UDP (IPv4): Opening broadcast socket on 67 [7] 20220817144343: UDP (IPv4): Opening socket on 127.0.0.1 [7] 20220817144343: Last message repeated 2 times [7] 20220817144343: UDP (IPv6): Opening socket on [::] [7] 20220817144343: UDP (IPv4): Opening socket on 0.0.0.0 [7] 20220817144343: UDP (IPv6): Opening socket on [::] above is the output, i dont see anything wrong. can someone help me figure this out, Quote Link to comment Share on other sites More sharing options...
mskenderian Posted August 17, 2022 Author Report Share Posted August 17, 2022 Figured it out. Solution: I disabled IPv6 and it worked. even though i had enabled both ipv4 and ipv6, there was an issue with the server. I dont know why this would have happened, it should nativily work with both IPv4 and IPv6, but we dont need ipv6 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.