Fresh install issue

Andyd358 · Jun 12, 2020

Hi

Version 4.5.14
Git Information Branch: master

Debian 9.12

5 times today I have tried to install Fusion on a debian CT in proxmox each time I get the same problem I can add a gateway but it wont start and when i click on sip status I get "connection to event socket failed" also if i look at the log viewer it seem a little broke!!!

Any Ideas?

The only thing i can think of is that there may be an issue with proxmox. I know it does not like its IP address changed but it was setup on dhcp in a different location so I had to chaneg the ip and dns for it.

Adrian Fretwell · Jun 12, 2020

Last person I remember having that sort of trouble had accidentally installed the 32 bit version of Debian.

Andyd358 · Jun 12, 2020

Adrian Fretwell said:
Last person I remember having that sort of trouble had accidentally installed the 32 bit version of Debian.

Yeah I seen th eold thread you been helping someonw with

Andyd358 · Jun 12, 2020

initially i was getting lots of locale errors directory not found when i was trying to install via ssh but ive since tried using the console on proxmox, dont get the errors any longer but still the same outcome.. I had the same issue with trying in on raspberry pi earlier in the week.

Andyd358 · Jun 12, 2020

Only error i get when installing again (Debian 10 standard) this time is
Ver Cluster Port Status Owner Data directory Log file
11 main 5432 down postgres /var/lib/postgresql/11/main /var/log/postgresql/postgresql-11-main.log
update-alternatives: using /usr/share/postgresql/11/man/man1/postmaster.1.gz to provide /usr/share/man/man1/postmaster.1.gz (postmaster.1.gz) in auto mode
Setting up postgresql (11+200+deb10u3) ...
Setting up sysstat (12.0.3-2) ...

Andyd358 · Jun 12, 2020

Seen another error at the end of the install
Job for freeswitch.service failed because the control process exited with error code.
See "systemctl status freeswitch.service" and "journalctl -xe" for details.

* freeswitch.service - freeswitch
Loaded: loaded (/lib/systemd/system/freeswitch.service; enabled; vendor preset: en
Active: failed (Result: exit-code) since Fri 2020-06-12 17:07:39 UTC; 22min ago
Process: 15918 ExecStartPre=/bin/mkdir -p /var/run/freeswitch (code=exited, status=

Jun 12 17:07:39 CT100 systemd[1]: freeswitch.service: Service RestartSec=100ms expire
Jun 12 17:07:39 CT100 systemd[1]: freeswitch.service: Scheduled restart job, restart
Jun 12 17:07:39 CT100 systemd[1]: Stopped freeswitch.
Jun 12 17:07:39 CT100 systemd[1]: freeswitch.service: Start request repeated too quic
Jun 12 17:07:39 CT100 systemd[1]: freeswitch.service: Failed with result 'exit-code'.
Jun 12 17:07:39 CT100 systemd[1]: Failed to start freeswitch.
lines 1-11/11 (END)

Adrian Fretwell · Jun 12, 2020

Difficult to call, but this may be a permissions issue. You really need some input from a Proxmox expert.

Andyd358 · Jun 12, 2020

Could it be because im using proxmox do you think Ive never had an issue like this before, coul dit be related to this:

Is it possible to correctly launch fusionpвx/freeswitch in an unprivileged LXC on Proxmox VE?

Dear colleagues! Maybe I again raise the topic that was previously discussed here. But still... Tell me, please, is it possible to install Fusionpbx in an unprivileged container on Proxmox VE? If not, why? P.S. Yesterday I tried to install Fusionpbx in an unprivileged LXC on Proxmox VE 6.1 and...

www.pbxforums.com

Adrian Fretwell · Jun 12, 2020

I don't know the answer. I know @DigitalDaz has some experience with Proxmox, maybe he (or others) will be able to provide a more educated guess than me.

Andyd358 · Jun 12, 2020

Stangley I have had the same problem with a Raspberry Pi so i was thinking is there a proble with the master

zenvoip · Jun 15, 2020

I am trying to install on VPS never had this issue before.

Andyd358 · Jun 15, 2020

Thought i would try again this morning but still getting the same error :
Success. You can now start the database server using:

pg_ctlcluster 12 main start

Ver Cluster Port Status Owner Data directory Log file
12 main 5432 down postgres /var/lib/postgresql/12/main /var/log/postgresql/postgresql-12-main.log
update-alternatives: using /usr/share/postgresql/12/man/man1/postmaster.1.gz to provide /usr/share/man/man1/postmaster.1.gz (postmaster.1.gz) in auto mode
Setting up postgresql (12+215.pgdg90+1) ...
Processing triggers for systemd (232-25+deb9u12) ...
CREATE DATABASE
CREATE DATABASE
CREATE ROLE
CREATE ROLE
GRANT
GRANT
GRANT
ALTER ROLE
ALTER ROLE
INSERT 0 1
INSERT 0 1
INSERT 0 1
Job for freeswitch.service failed because the control process exited with error code.
See "systemctl status freeswitch.service" and "journalctl -xe" for details.

Adrian Fretwell · Jun 15, 2020

What do you see if you run "systemctl status freeswitch.service" and "journalctl -xe" ?

Andyd358 · Jun 15, 2020

* freeswitch.service - freeswitch
Loaded: loaded (/lib/systemd/system/freeswitch.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2020-06-15 08:08:56 UTC; 35min ago
Process: 18034 ExecStartPre=/bin/mkdir -p /var/run/freeswitch (code=exited, status=214/SETSCHEDULER)

Jun 15 08:08:56 CT100 systemd[1]: freeswitch.service: Control process exited, code=exited status=214
Jun 15 08:08:56 CT100 systemd[1]: Failed to start freeswitch.
Jun 15 08:08:56 CT100 systemd[1]: freeswitch.service: Unit entered failed state.
Jun 15 08:08:56 CT100 systemd[1]: freeswitch.service: Failed with result 'exit-code'.
Jun 15 08:08:56 CT100 systemd[1]: freeswitch.service: Service hold-off time over, scheduling restart.
Jun 15 08:08:56 CT100 systemd[1]: Stopped freeswitch.
Jun 15 08:08:56 CT100 systemd[1]: freeswitch.service: Start request repeated too quickly.
Jun 15 08:08:56 CT100 systemd[1]: Failed to start freeswitch.
Jun 15 08:08:56 CT100 systemd[1]: freeswitch.service: Unit entered failed state.
Jun 15 08:08:56 CT100 systemd[1]: freeswitch.service: Failed with result 'exit-code'.

Jun 15 08:43:21 CT100 sshd[19242]: Received disconnect from 49.88.112.76 port 34039:11: [preauth]
Jun 15 08:43:21 CT100 sshd[19242]: Disconnected from 49.88.112.76 port 34039 [preauth]
Jun 15 08:43:21 CT100 sshd[19242]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.76
Jun 15 08:43:53 CT100 sshd[19260]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.
Jun 15 08:43:55 CT100 sshd[19260]: Failed password for root from 218.92.0.173 port 22922 ssh2
Jun 15 08:43:58 CT100 sshd[19260]: Failed password for root from 218.92.0.173 port 22922 ssh2
Jun 15 08:44:01 CT100 sshd[19260]: Failed password for root from 218.92.0.173 port 22922 ssh2
Jun 15 08:44:04 CT100 sshd[19260]: Failed password for root from 218.92.0.173 port 22922 ssh2
Jun 15 08:44:07 CT100 sshd[19260]: Failed password for root from 218.92.0.173 port 22922 ssh2
Jun 15 08:44:07 CT100 sshd[19260]: error: maximum authentication attempts exceeded for root from 218.92.0.173 port 22922 ssh2 [
Jun 15 08:44:07 CT100 sshd[19260]: Disconnecting: Too many authentication failures [preauth]
Jun 15 08:44:07 CT100 sshd[19260]: PAM 4 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.173
Jun 15 08:44:07 CT100 sshd[19260]: PAM service(sshd) ignoring max retries; 5 > 3
Jun 15 08:44:16 CT100 sshd[19273]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.
Jun 15 08:44:18 CT100 sshd[19273]: Failed password for root from 218.92.0.173 port 61872 ssh2
Jun 15 08:44:21 CT100 sshd[19277]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.8
Jun 15 08:44:22 CT100 sshd[19273]: Failed password for root from 218.92.0.173 port 61872 ssh2
Jun 15 08:44:23 CT100 sshd[19277]: Failed password for root from 49.88.112.76 port 60386 ssh2
Jun 15 08:44:25 CT100 sshd[19277]: Failed password for root from 49.88.112.76 port 60386 ssh2
Jun 15 08:44:26 CT100 ntpd[1903]: local_clock: ntp_loopfilter.c line 818: ntp_adjtime: Operation not permitted
Jun 15 08:44:26 CT100 sshd[19273]: Failed password for root from 218.92.0.173 port 61872 ssh2
Jun 15 08:44:28 CT100 sshd[19277]: Failed password for root from 49.88.112.76 port 60386 ssh2
Jun 15 08:44:28 CT100 sshd[19277]: Received disconnect from 49.88.112.76 port 60386:11: [preauth]
Jun 15 08:44:28 CT100 sshd[19277]: Disconnected from 49.88.112.76 port 60386 [preauth]
Jun 15 08:44:28 CT100 sshd[19277]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.76
Jun 15 08:44:29 CT100 sshd[19273]: Failed password for root from 218.92.0.173 port 61872 ssh2
Jun 15 08:44:34 CT100 sshd[19273]: Failed password for root from 218.92.0.173 port 61872 ssh2
Jun 15 08:44:37 CT100 sshd[19273]: Failed password for root from 218.92.0.173 port 61872 ssh2
Jun 15 08:44:37 CT100 sshd[19273]: error: maximum authentication attempts exceeded for root from 218.92.0.173 port 61872 ssh2 [
Jun 15 08:44:37 CT100 sshd[19273]: Disconnecting: Too many authentication failures [preauth]
Jun 15 08:44:37 CT100 sshd[19273]: PAM 5 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.173
Jun 15 08:44:37 CT100 sshd[19273]: PAM service(sshd) ignoring max retries; 6 > 3
Jun 15 08:44:44 CT100 sshd[19290]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.
Jun 15 08:44:46 CT100 sshd[19290]: Failed password for root from 218.92.0.173 port 31571 ssh2
Jun 15 08:44:47 CT100 sshd[19290]: Received disconnect from 218.92.0.173 port 31571:11: [preauth]
Jun 15 08:44:47 CT100 sshd[19290]: Disconnected from 218.92.0.173 port 31571 [preauth]
Jun 15 08:45:01 CT100 CRON[19301]: pam_unix(cron:session): session opened for user root by (uid=0)
Jun 15 08:45:01 CT100 CRON[19302]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun 15 08:45:01 CT100 CRON[19301]: pam_unix(cron:session): session closed for user root
lines 1114-1152/1152 (END)

Adrian Fretwell · Jun 15, 2020

As I said before, it does look like a permissions issue to me (but I know nothing about Proxmox). I assume it has failed to create the directory /var/run/freeswitch.

I believe the FreeSwitch startup process needs to start as root in order to execute things like /bin/mkdir -p /var/run/freeswitch and then drop its privileges to the www-data user specified by the -u on the command line.

Is there any more useful information written in the freeswitch log? (Assuming it has managed to get as far as creating a log file.)

Andyd358 · Jun 15, 2020

Ok I think the Promox install is fubar somehow Ive just done a fresh install on a VPS using proxmox and its worked fine by the look of it. Just need to test with a sip trunk and a phone

Andyd358 · Jun 15, 2020

Adrian Fretwell said:
As I said before, it does look like a permissions issue to me (but I know nothing about Proxmox). I assume it has failed to create the directory /var/run/freeswitch.

I believe the FreeSwitch startup process needs to start as root in order to execute things like /bin/mkdir -p /var/run/freeswitch and then drop its privileges to the www-data user specified by the -u on the command line.

Is there any more useful information written in the freeswitch log? (Assuming it has managed to get as far as creating a log file.)

Ive checked persmissions for the freeswitch directory (nothing in the directory from what i can see)

drwxrwx--- 2 www-data www-data 40 Jun 15 09:54 freeswitch

Scott Williams · Aug 4, 2020

Yes, you have to change some settings in Propxmox. I worked with the Fusion guys to post some pics.

Scott Williams · Aug 4, 2020

I was creating privileged containers, and Freeswitch would not install properly. Secondly it wouldn't sync time, so then I had to allow nesting.

HTH

Fresh install issue

Member

Well-Known Member

Member

Member

Member

Member

Well-Known Member

Member

Well-Known Member

Member

Member

Member

Well-Known Member

Member

Well-Known Member

Member

Member

Member

Member