ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Building Elastix 4 via RPM Repo

    Scheduled Pinned Locked Moved IT Discussion
    asteriskcentoscentos 7elastixelastix 4linuxpbxvoip
    184 Posts 15 Posters 126.7k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      scottalanmiller @3Mu36
      last edited by

      @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
      3 1 Reply Last reply Reply Quote 0
      • 3
        3Mu36 @scottalanmiller
        last edited by

        @scottalanmiller

        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...

        S 1 Reply Last reply Reply Quote 0
        • S
          scottalanmiller @3Mu36
          last edited by

          @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?

          3 D 2 Replies Last reply Reply Quote 0
          • 3
            3Mu36 @scottalanmiller
            last edited by

            @scottalanmiller

            [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 ms

            Yes, this is why I don't understand what is going on!

            1 Reply Last reply Reply Quote 0
            • S
              scottalanmiller
              last edited by

              Okay, so you have networking, that is fine.

              Now do this: nslookup google.com

              3 1 Reply Last reply Reply Quote 0
              • 3
                3Mu36 @scottalanmiller
                last edited by

                @scottalanmiller
                [root@localhost ~]# nslookup google.com
                -bash: nslookup: command not found

                😞

                1 Reply Last reply Reply Quote 0
                • S
                  scottalanmiller
                  last edited by scottalanmiller

                  That'll be a problem to fix if yum isn't working, I suppose.

                  What is the output of:

                  cat /etc/resolv.conf
                  3 1 Reply Last reply Reply Quote 0
                  • 3
                    3Mu36 @scottalanmiller
                    last edited by

                    This post is deleted!
                    1 Reply Last reply Reply Quote 0
                    • S
                      scottalanmiller
                      last edited by

                      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.

                      3 1 Reply Last reply Reply Quote 0
                      • 3
                        3Mu36 @scottalanmiller
                        last edited by

                        @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
                        1 Reply Last reply Reply Quote 0
                        • S
                          scottalanmiller
                          last edited by

                          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.

                          1 Reply Last reply Reply Quote 0
                          • S
                            scottalanmiller
                            last edited by

                            You can fix this with...

                            echo "nameserver 8.8.8.8" >> /etc/resolv.conf
                            3 1 Reply Last reply Reply Quote 0
                            • 3
                              3Mu36 @scottalanmiller
                              last edited by 3Mu36

                              @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.149

                              This seems to have got me in:

                              sed -i 's/(^SELINUX=).*/\SELINUX=disabled/' /etc/selinux/config

                              S thiagolimaT 2 Replies Last reply Reply Quote 0
                              • S
                                scottalanmiller @3Mu36
                                last edited by

                                @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.149

                                This 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.

                                JaredBuschJ 1 Reply Last reply Reply Quote 1
                                • JaredBuschJ
                                  JaredBusch @scottalanmiller
                                  last edited by

                                  @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.149

                                  This 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.

                                  S 1 Reply Last reply Reply Quote 0
                                  • S
                                    scottalanmiller @JaredBusch
                                    last edited by

                                    @JaredBusch said:

                                    @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.149

                                    This 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.

                                    But we didn't have this SELinux problem with any other install. So I'm not convinced that that is the problem. We certainly did not disable SELinux on our Elastix 4 system and it works just fine.

                                    1 Reply Last reply Reply Quote 0
                                    • D
                                      dom @scottalanmiller
                                      last edited by

                                      @scottalanmiller said:

                                      @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?

                                      When I ping 8.8.8.8 it just hangs.

                                      Here is the output of my log

                                      Mar 15 16:03:40 pbx77 systemd: Starting Session 2315 of user dom.
                                      Mar 15 16:03:41 pbx77 dbus[643]: [system] Activating service name='org.freedesktop.problems' (using servicehelper)
                                      Mar 15 16:03:41 pbx77 dbus-daemon: dbus[643]: [system] Activating service name='org.freedesktop.problems' (using servicehelper)
                                      Mar 15 16:03:41 pbx77 dbus[643]: [system] Successfully activated service 'org.freedesktop.problems'
                                      Mar 15 16:03:41 pbx77 dbus-daemon: dbus[643]: [system] Successfully activated service 'org.freedesktop.problems'
                                      Mar 15 16:03:49 pbx77 su: (to root) dom on pts/1
                                      Mar 15 16:03:54 pbx77 systemd: Stopping The Apache HTTP Server...
                                      Mar 15 16:03:55 pbx77 systemd: Starting The Apache HTTP Server...
                                      Mar 15 16:03:55 pbx77 httpd: AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using pbx77.cloudapp.net. Set the 'ServerName' directive globally to suppress this message
                                      Mar 15 16:03:55 pbx77 systemd: Started The Apache HTTP Server.

                                      and google lookup
                                      nslookup google.com
                                      Server: 8.8.8.8
                                      Address: 8.8.8.8#53

                                      Non-authoritative answer:
                                      Name: google.com
                                      Address: 74.125.22.113
                                      Name: google.com
                                      Address: 74.125.22.100
                                      Name: google.com
                                      Address: 74.125.22.102
                                      Name: google.com
                                      Address: 74.125.22.101
                                      Name: google.com
                                      Address: 74.125.22.139
                                      Name: google.com
                                      Address: 74.125.22.138

                                      1 Reply Last reply Reply Quote 0
                                      • S
                                        scottalanmiller
                                        last edited by

                                        So pinging hangs but nslookup to 8.8.8.8 works? Sounds to be like you have a networking issue at your firewall. Not the only possibility, of course, but I think that you have something mangling your packets. You know that traffic is getting to 8.8.8.8 as it is responding on on UDP 53. But PING traffic is not making it back. So something is messing with your traffic.

                                        D 1 Reply Last reply Reply Quote 0
                                        • D
                                          dom @scottalanmiller
                                          last edited by

                                          @3Mu36 said:

                                          ping fqdn

                                          Weird
                                          ping pbx77.cloudapp.net
                                          64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.036 ms
                                          64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.063 ms
                                          64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.098 ms

                                          when I install a standard lamp stack on azure its fine its just this Elastix installation thats a problem

                                          S 1 Reply Last reply Reply Quote 0
                                          • S
                                            scottalanmiller @dom
                                            last edited by

                                            @dom said:

                                            @3Mu36 said:

                                            ping fqdn

                                            Weird
                                            ping pbx77.cloudapp.net
                                            64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.036 ms
                                            64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.063 ms
                                            64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.098 ms

                                            when I install a standard lamp stack on azure its fine its just this Elastix installation thats a problem

                                            Try another Elastix install on Azure. Right now, Azure is partially down (we have several VMs not responding, the console is regionally down and some Exchange customers are having issues.) But once Azure recovers, see if a fresh build has the same issues.

                                            1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 4
                                            • 5
                                            • 6
                                            • 7
                                            • 8
                                            • 9
                                            • 10
                                            • 6 / 10
                                            • First post
                                              Last post