Building Elastix 4 via RPM Repo
-
System is certainly working at a basic level.
-
Yeah I don't get whats going on. I want to be able to access the site over httpd but the dns name is not resolving. I tried a fresh install on pbx99 and the same thing happens. Are you able to install on another VPS?
-
@dom said:
Yeah I don't get whats going on. I want to be able to access the site over httpd but the dns name is not resolving. I tried a fresh install on pbx99 and the same thing happens. Are you able to install on another VPS?
Name is definitely resolving. Jared showed that working in his examples. It's working here too.
-
@scottalanmiller said:
@dom said:
Yeah I don't get whats going on. I want to be able to access the site over httpd but the dns name is not resolving. I tried a fresh install on pbx99 and the same thing happens. Are you able to install on another VPS?
Name is definitely resolving. Jared showed that working in his examples. It's working here too.
The problem is internal to the Elastix instance inside Apache.
-
I think I'm having the same problem as @dom I have installed using the script onto a cloudatcost vm (testing only). Install completes successfully and reboots. SSH logs in but I cannot resolve the web interface. http gives me a time out and https gives me a 500 error. Happy to provide logs as required, really keen to get this up and tested.
-
@3Mu36 said:
I think I'm having the same problem as @dom I have installed using the script onto a cloudatcost vm (testing only). Install completes successfully and reboots. SSH logs in but I cannot resolve the web interface. http gives me a time out and https gives me a 500 error. Happy to provide logs as required, really keen to get this up and tested.
The tail on the httpd error log is the most likely to be useful. Maybe this too..
systemctl restart httpd; tail -n 20 /var/log/messages -
Mar 14 07:12:54 localhost systemd-logind: New session 928 of user root.
Mar 14 07:12:54 localhost systemd: Starting Session 928 of user root.
Mar 14 07:15:01 localhost systemd: Started Session 929 of user root.
Mar 14 07:15:01 localhost systemd: Starting Session 929 of user root.
Mar 14 07:15:51 localhost systemd: Started Session 930 of user root.
Mar 14 07:15:51 localhost systemd-logind: New session 930 of user root.
Mar 14 07:15:51 localhost systemd: Starting Session 930 of user root.
Mar 14 07:16:41 localhost systemd: Stopping The Apache HTTP Server...
Mar 14 07:16:43 localhost systemd: Starting The Apache HTTP Server...
Mar 14 07:16:43 localhost httpd: AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using localhost.localdomain. Set the 'ServerName' directive globally to suppress this message
Mar 14 07:16:43 localhost systemd: Started The Apache HTTP Server.
Mar 14 07:17:30 localhost systemd: Started Session 931 of user root.
Mar 14 07:17:30 localhost systemd-logind: New session 931 of user root.
Mar 14 07:17:30 localhost systemd: Starting Session 931 of user root.Not sure if it's relevant but since the install completed I can't ping fqdn or access the outside world from the server (although SSH still works). I tried to check the telnet tip above, but it can't download telnet...
-
@3Mu36 Sounds like you've lost networking. If you cannot reach the outside world then definitely nothing here is going to work. The machine is offline and cannot respond. That would make your issue very different than the other one that we are discussing because the one is online and responding. That SSH keeps working is very odd. So networking is not 100% broken, but something major is.
What is the output of ping 8.8.8.8?
-
[root@localhost ~]# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=20.1 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=56 time=19.8 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=56 time=20.6 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=56 time=20.1 msYes, this is why I don't understand what is going on!
-
Okay, so you have networking, that is fine.
Now do this: nslookup google.com
-
@scottalanmiller
[root@localhost ~]# nslookup google.com
-bash: nslookup: command not found
-
That'll be a problem to fix if yum isn't working, I suppose.
What is the output of:
cat /etc/resolv.conf -
This post is deleted! -
I fixed the typo in seconds, as fast as my broken touchpad would allow me, but you tested it before I could fix it.
There is no trailing e.
-
@scottalanmiller
Whoops! I didn't notice either!I'll attempt to fix this now, can't understand how/why the install would break this
# Generated by NetworkManager search cloudatcost.com # No nameservers found; try putting DNS servers into your # ifcfg files in /etc/sysconfig/network-scripts like so: # # DNS1=xxx.xxx.xxx.xxx # DNS2=xxx.xxx.xxx.xxx # DOMAIN=lab.foo.com bar.foo.com -
That would do it, it's blank. No idea why it would break it, but it hasn't broken it other places so it might be something specific to the CloudatCost setup.
FYI: CloudatCost is not viable for a PBX outside of just testing in a lab. Performance issues will cause audio problems and reliability problems will be an issue for a phone system.
You can add the DNS servers directly to this file OR you can use the nmtui command to do so though a text user interface.
-
You can fix this with...
echo "nameserver 8.8.8.8" >> /etc/resolv.conf -
@scottalanmiller Yep thanks, done that and yes, issues with c@c noted, it's an OK sandbox (or that's the idea) tis all.
Anyway, so still have the 500 issue: 45.62.240.149This seems to have got me in:
sed -i 's/(^SELINUX=).*/\SELINUX=disabled/' /etc/selinux/config
-
@3Mu36 said:
@scottalanmiller Yep thanks, done that and yes, issues with c@c noted, it's an OK sandbox (or that's the idea) tis all.
Anyway, so still have the 500 issue: 45.62.240.149This seems to have got me in:
sed -i 's/(^SELINUX=).*/\SELINUX=disabled/' /etc/selinux/config
That's just disabling SELinux. So that tells us that SELinux is misconfigured here, but why is an important question. You don't generally want to be disabling your security systems.
-
@scottalanmiller said:
@3Mu36 said:
@scottalanmiller Yep thanks, done that and yes, issues with c@c noted, it's an OK sandbox (or that's the idea) tis all.
Anyway, so still have the 500 issue: 45.62.240.149This seems to have got me in:
sed -i 's/(^SELINUX=).*/\SELINUX=disabled/' /etc/selinux/config
That's just disabling SELinux. So that tells us that SELinux is misconfigured here, but why is an important question. You don't generally want to be disabling your security systems.
Because Elastix is crap anymore and they never planned to correctly implement.
