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

    Unsolved Troubleshooting Help Requested

    IT Discussion
    centos virtual machine esxi troubleshooting
    13
    44
    2.8k
    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.
    • DustinB3403D
      DustinB3403
      last edited by

      This is what I get from the non-working VM.

      yum update
      Loaded plugins: fastestmirror
      Loading mirror speeds from cached hostfile
       * base: mirror.atlanticmetro.net
       * extras: bay.uchicago.edu
       * updates: centos.s.uw.edu
      http://repos-va.psychz.net/centos/7.6.1810/os/x86_64/repodata/repomd.xml: [Errno                                                                                                                                                              14] curl#6 - "Could not resolve host: repos-va.psychz.net; Unknown error"
      Trying other mirror.
      

      It just keeps going through all of the mirrors, obviously.

      I've disabled and turned off yum-cron and have reboot numerous times. So that isn't it. I can ping locally by IP and DNS from the non-working machine.

      travisdh1T 1 Reply Last reply Reply Quote 0
      • DustinB3403D
        DustinB3403
        last edited by

        I guess I'll just restore the VM and see what happens from it.

        1 Reply Last reply Reply Quote 0
        • travisdh1T
          travisdh1 @DustinB3403
          last edited by

          @DustinB3403 said in Troubleshooting Help Requested:

          This is what I get from the non-working VM.

          yum update
          Loaded plugins: fastestmirror
          Loading mirror speeds from cached hostfile

          • base: mirror.atlanticmetro.net
          • extras: bay.uchicago.edu
          • updates: centos.s.uw.edu
            http://repos-va.psychz.net/centos/7.6.1810/os/x86_64/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: repos-va.psychz.net; Unknown error"
            Trying other mirror.

          It just keeps going through all of the mirrors, obviously.

          I've disabled and turned off yum-cron and have reboot numerous times. So that isn't it. I can ping locally by IP and DNS from the non-working machine.

          Did I see right that traceroute isn't installed?

          DustinB3403D 1 Reply Last reply Reply Quote 0
          • DustinB3403D
            DustinB3403 @travisdh1
            last edited by

            @travisdh1 yes.

            travisdh1T 1 Reply Last reply Reply Quote 0
            • DustinB3403D
              DustinB3403
              last edited by

              And it isn't required either, as this system has updated fine for months.

              1 Reply Last reply Reply Quote 0
              • travisdh1T
                travisdh1 @DustinB3403
                last edited by travisdh1

                @DustinB3403 said in Troubleshooting Help Requested:

                @travisdh1 yes.

                Makes it difficult to see weather there are peering-point issues between you and the mirror sites.

                edit: Yes, I've seen networks block distribution mirror sites before. So much fun trying to get those fixed.

                DustinB3403D 1 Reply Last reply Reply Quote 0
                • DustinB3403D
                  DustinB3403 @travisdh1
                  last edited by

                  @travisdh1 said in Troubleshooting Help Requested:

                  edit: Yes, I've seen networks block distribution mirror sites before. So much fun trying to get those fixed.

                  But on the very same network, just a different host nothing is blocked. I could of course look at the firewall to see if something was changed. But if changes were to be made, I think I would've been made aware.

                  And every mirror is blocked. It's as though this device itself is blocked.

                  1 Reply Last reply Reply Quote 0
                  • black3dynamiteB
                    black3dynamite
                    last edited by

                    Try ping -4 google.com
                    It’s probably using ipv6 instead of ipv4

                    DustinB3403D 2 Replies Last reply Reply Quote 1
                    • DustinB3403D
                      DustinB3403 @black3dynamite
                      last edited by

                      @black3dynamite said in Troubleshooting Help Requested:

                      Try ping -4 google.com
                      It’s probably using ipv6 instead of ipv4

                      Will test that in a moment. The restore is going.

                      1 Reply Last reply Reply Quote 0
                      • DustinB3403D
                        DustinB3403 @black3dynamite
                        last edited by

                        @black3dynamite said in Troubleshooting Help Requested:

                        Try ping -4 google.com
                        It’s probably using ipv6 instead of ipv4

                        No change.

                        And the backup from yesterday has no change either. Grr. . . I don't want to rebuild this VM. . . going further back.

                        It isn't mission critical either, just irritating.

                        1 Reply Last reply Reply Quote 0
                        • ObsolesceO
                          Obsolesce
                          last edited by

                          Are you using NetworkManager? If so, turn that shit off.

                          DustinB3403D 1 Reply Last reply Reply Quote 0
                          • ObsolesceO
                            Obsolesce
                            last edited by

                            Try adding 127.0.0.1 to /etc/resolv.conf

                            DustinB3403D 1 Reply Last reply Reply Quote 0
                            • DustinB3403D
                              DustinB3403 @Obsolesce
                              last edited by

                              @Obsolesce said in Troubleshooting Help Requested:

                              Are you using NetworkManager? If so, turn that shit off.

                              Not using NM.

                              1 Reply Last reply Reply Quote 0
                              • DustinB3403D
                                DustinB3403 @Obsolesce
                                last edited by

                                @Obsolesce said in Troubleshooting Help Requested:

                                Try adding 127.0.0.1 to /etc/resolv.conf

                                No change with adding the loopback.

                                M 1 Reply Last reply Reply Quote 0
                                • M
                                  manxam @DustinB3403
                                  last edited by

                                  @DustinB3403 : The fact that you can ping the gateway/router by name and IP makes me suspect it's the firewall.
                                  AFAIK, there is nothing on a linux box that would allow it to distinguish between LAN and WAN when performing lookups.

                                  scottalanmillerS 1 Reply Last reply Reply Quote 0
                                  • scottalanmillerS
                                    scottalanmiller @manxam
                                    last edited by

                                    @manxam said in Troubleshooting Help Requested:

                                    @DustinB3403 : The fact that you can ping the gateway/router by name and IP makes me suspect it's the firewall.
                                    AFAIK, there is nothing on a linux box that would allow it to distinguish between LAN and WAN when performing lookups.

                                    the firewall, OR the default gateway is messed up. Check the routes on the VM.

                                    DustinB3403D 1 Reply Last reply Reply Quote 1
                                    • DustinB3403D
                                      DustinB3403 @scottalanmiller
                                      last edited by

                                      @scottalanmiller I have 1 route on the VM, and its a mirror image of the route on the working VM, with the exception of the device name, and IP.

                                      1 Reply Last reply Reply Quote 0
                                      • DustinB3403D
                                        DustinB3403
                                        last edited by

                                        Working
                                        putty_2019-02-22_15-15-43.png

                                        Not Working
                                        putty_2019-02-22_15-15-35.png

                                        M 1 Reply Last reply Reply Quote 0
                                        • M
                                          manxam @DustinB3403
                                          last edited by

                                          @DustinB3403 : Yes, but that doesn't mean the firewall doesn't have a rule (or is a Sonicwall -- see my old post) to block outbound on WAN from that IP.

                                          1 Reply Last reply Reply Quote 0
                                          • 1
                                            1337
                                            last edited by 1337

                                            Double check mac address so you don't have two VMs with the same. That and conflicting ip addresses can cause some strange effects.

                                            1 Reply Last reply Reply Quote 1
                                            • 1
                                            • 2
                                            • 3
                                            • 2 / 3
                                            • First post
                                              Last post