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

    CentOS 7 VM on Hyper-V losing DHCP assigned address

    IT Discussion
    centos 7 dhcp failed hyper-v chrony
    8
    60
    12.3k
    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.
    • JaredBuschJ
      JaredBusch
      last edited by gjacobse

      Server a spun up a month ago for community.bundystl.com just was unreachable.

      Guess what.. WTF 4 active damned servers listed... why can it not stay f***ing working?

      [root@bna-cmty ~]# nano /etc/chrony.conf
# These servers were defined in the installation:
server 0.centos.pool.ntp.org iburst
server 1.centos.pool.ntp.org iburst
server 2.centos.pool.ntp.org iburst
server 3.centos.pool.ntp.org iburst
# Use public servers from the pool.ntp.org project.
# Please consider joining the pool (http://www.pool.ntp.org/join.html).

      [root@bna-cmty ~]# grep chrony /var/log/messages*
/var/log/messages:Jan 22 20:15:23 bna-cmty chronyd[621]: Selected source 74.120.81.219
/var/log/messages:Feb 14 02:13:15 bna-cmty chronyd[618]: chronyd version 2.1.1 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +DEBUG +ASYNCDNS +IPV6 +SECHASH)
/var/log/messages:Feb 14 02:13:15 bna-cmty chronyd[618]: Frequency -18.365 +/- 0.044 ppm read from /var/lib/chrony/drift
/var/log/messages:Jan 25 21:01:26 bna-cmty chronyd[618]: Selected source 104.232.3.3
/var/log/messages:Jan 25 21:01:26 bna-cmty chronyd[618]: System clock wrong by -1660320.927108 seconds, adjustment started
/var/log/messages:Jan 25 21:01:26 bna-cmty chronyd[618]: System clock was stepped by -1660320.927108 seconds
/var/log/messages:Jan 25 21:02:31 bna-cmty chronyd[618]: Selected source 129.250.35.251
/var/log/messages:Jan 26 05:29:06 bna-cmty chronyd[618]: Can't synchronise: no selectable sources
/var/log/messages:Jan 28 00:09:15 bna-cmty chronyd[618]: Source 104.232.3.3 offline
/var/log/messages:Jan 28 00:09:15 bna-cmty chronyd[618]: Source 129.250.35.251 offline
/var/log/messages:Jan 28 00:09:15 bna-cmty chronyd[618]: Source 104.245.33.76 offline
/var/log/messages:Jan 28 00:09:15 bna-cmty chronyd[618]: Source 66.228.42.59 offline
/var/log/messages:Jan 28 00:09:15 bna-cmty chronyd[618]: Source 104.232.3.3 online
/var/log/messages:Jan 28 00:09:15 bna-cmty chronyd[618]: Source 129.250.35.251 online
/var/log/messages:Jan 28 00:09:15 bna-cmty chronyd[618]: Source 104.245.33.76 online
/var/log/messages:Jan 28 00:09:15 bna-cmty chronyd[618]: Source 66.228.42.59 online
/var/log/messages:Jan 28 00:09:16 bna-cmty chronyd[618]: Selected source 129.250.35.251
/var/log/messages-20170101:Dec 25 23:04:57 bna-cmty yum[37947]: Updated: chrony-2.1.1-4.el7.centos.x86_64
/var/log/messages-20170101:Dec 25 23:06:33 bna-cmty chronyd[736]: chronyd exiting
/var/log/messages-20170101:Dec 25 23:06:33 bna-cmty chronyd[4840]: chronyd version 2.1.1 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +DEBUG +ASYNCDNS +IPV6 +SECHASH)
/var/log/messages-20170101:Dec 25 23:06:33 bna-cmty chronyd[4840]: Frequency -17.944 +/- 0.124 ppm read from /var/lib/chrony/drift
/var/log/messages-20170101:Dec 25 23:06:38 bna-cmty chronyd[4840]: Selected source 192.155.90.13
/var/log/messages-20170101:Jan 19 00:13:55 bna-cmty chronyd[638]: chronyd version 2.1.1 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +DEBUG +ASYNCDNS +IPV6 +SECHASH)
/var/log/messages-20170101:Jan 19 00:13:56 bna-cmty chronyd[638]: Frequency -17.944 +/- 0.136 ppm read from /var/lib/chrony/drift
/var/log/messages-20170101:Dec 26 00:39:42 bna-cmty chronyd[638]: Selected source 209.50.48.237
/var/log/messages-20170101:Dec 26 00:39:42 bna-cmty chronyd[638]: System clock wrong by -2072062.504299 seconds, adjustment started
/var/log/messages-20170101:Dec 26 00:39:42 bna-cmty chronyd[638]: System clock was stepped by -2072062.504299 seconds
/var/log/messages-20170101:Dec 26 02:37:08 bna-cmty chronyd[638]: Selected source 66.151.147.38
/var/log/messages-20170101:Dec 26 09:17:31 bna-cmty chronyd[638]: Can't synchronise: no selectable sources
/var/log/messages-20170101:Dec 26 15:03:37 bna-cmty chronyd[638]: Source 74.120.8.2 offline
/var/log/messages-20170101:Dec 26 15:03:37 bna-cmty chronyd[638]: Source 66.151.147.38 offline
/var/log/messages-20170101:Dec 26 15:03:37 bna-cmty chronyd[638]: Source 66.135.44.92 offline
/var/log/messages-20170101:Dec 26 15:03:37 bna-cmty chronyd[638]: Source 209.50.48.237 offline
/var/log/messages-20170101:Dec 26 15:03:38 bna-cmty chronyd[638]: Source 74.120.8.2 online
/var/log/messages-20170101:Dec 26 15:03:38 bna-cmty chronyd[638]: Source 66.151.147.38 online
/var/log/messages-20170101:Dec 26 15:03:38 bna-cmty chronyd[638]: Source 66.135.44.92 online
/var/log/messages-20170101:Dec 26 15:03:38 bna-cmty chronyd[638]: Source 209.50.48.237 online
/var/log/messages-20170101:Dec 26 15:03:38 bna-cmty chronyd[638]: Selected source 209.50.48.237
/var/log/messages-20170101:Dec 26 18:04:47 bna-cmty chronyd[638]: Selected source 66.151.147.38
/var/log/messages-20170101:Dec 27 17:55:13 bna-cmty chronyd[638]: Selected source 209.50.48.237
/var/log/messages-20170101:Dec 28 07:08:18 bna-cmty chronyd[638]: Selected source 66.151.147.38
/var/log/messages-20170101:Dec 28 11:35:31 bna-cmty chronyd[638]: Selected source 209.50.48.237
/var/log/messages-20170101:Dec 28 18:03:54 bna-cmty chronyd[638]: Selected source 66.151.147.38
/var/log/messages-20170101:Dec 30 20:46:01 bna-cmty chronyd[638]: Selected source 209.50.48.237
/var/log/messages-20170101:Dec 31 04:48:48 bna-cmty chronyd[638]: Selected source 66.151.147.38
/var/log/messages-20170101:Dec 31 13:00:24 bna-cmty chronyd[638]: System clock status set to insert leap second
/var/log/messages-20170101:Dec 31 18:00:01 bna-cmty chronyd[638]: System clock status set to not insert/delete leap second
/var/log/messages-20170101:Dec 31 18:01:48 bna-cmty chronyd[638]: Source 74.120.8.2 replaced with 69.89.207.99
/var/log/messages-20170101:Dec 31 18:08:16 bna-cmty chronyd[638]: Selected source 69.89.207.99
/var/log/messages-20170109:Jan 18 06:33:17 bna-cmty chronyd[621]: chronyd version 2.1.1 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +DEBUG +ASYNCDNS +IPV6 +SECHASH)
/var/log/messages-20170109:Jan 18 06:33:17 bna-cmty chronyd[621]: Frequency -18.334 +/- 0.010 ppm read from /var/lib/chrony/drift
/var/log/messages-20170109:Jan  6 15:37:26 bna-cmty chronyd[621]: Selected source 69.89.207.99
/var/log/messages-20170109:Jan  6 15:37:26 bna-cmty chronyd[621]: System clock wrong by -1004160.299142 seconds, adjustment started
/var/log/messages-20170109:Jan  6 15:37:26 bna-cmty chronyd[621]: System clock was stepped by -1004160.299142 seconds
/var/log/messages-20170109:Jan  6 22:08:29 bna-cmty chronyd[621]: Source 198.55.111.50 offline
/var/log/messages-20170109:Jan  6 22:08:29 bna-cmty chronyd[621]: Source 204.2.134.162 offline
/var/log/messages-20170109:Jan  6 22:08:29 bna-cmty chronyd[621]: Source 74.120.81.219 offline
/var/log/messages-20170109:Jan  6 22:08:29 bna-cmty chronyd[621]: Source 69.89.207.99 offline
/var/log/messages-20170109:Jan  6 22:08:29 bna-cmty chronyd[621]: Can't synchronise: no selectable sources
/var/log/messages-20170109:Jan  6 22:08:30 bna-cmty chronyd[621]: Source 198.55.111.50 online
/var/log/messages-20170109:Jan  6 22:08:30 bna-cmty chronyd[621]: Source 204.2.134.162 online
/var/log/messages-20170109:Jan  6 22:08:30 bna-cmty chronyd[621]: Source 69.89.207.99 online
/var/log/messages-20170109:Jan  6 22:08:30 bna-cmty chronyd[621]: Source 74.120.81.219 online
/var/log/messages-20170109:Jan  6 22:08:30 bna-cmty chronyd[621]: Selected source 69.89.207.99
      1 Reply Last reply Reply Quote 0
      • ObsolesceO
        Obsolesce
        last edited by

        Is there a specific reason I missed why you arent using the vm integration service time sync with the host?

        Could you install the latest hyperV LIS on the linux vms, enable the guest time sync, and use windows/microsoft time sync on the host if its not on the domain?

        1 Reply Last reply Reply Quote 0
        • stacksofplatesS
          stacksofplates
          last edited by stacksofplates

          I'm amazed that just restarting the service fixes the issue. I wonder if the hardware clock isn't being updated and the skew is too great so Chrony just gives up.

          If you install ntpdate and enable it, it will update the hw clock every 11 minutes. I don't think it's installed by default with the minimal installs.

          You could also just go back to ntpd. It's still available and might not have the issue. It also has a file under /etc/sysconfig/ntpd where you can set ntpd to update the hw clock.

          JaredBuschJ 1 Reply Last reply Reply Quote 0
          • JaredBuschJ
            JaredBusch
            last edited by

            Another server this morning.

            /var/log/messages:Jan 31 02:22:57 nginxproxy chronyd[649]: Frequency -15.399 +/- 0.022 ppm read from /var/lib/chrony/drift
/var/log/messages:Jan 29 21:37:01 nginxproxy chronyd[649]: Selected source 208.75.88.4
/var/log/messages:Jan 29 21:37:01 nginxproxy chronyd[649]: System clock wrong by -103565.091462 seconds, adjustment started
/var/log/messages:Jan 29 21:37:01 nginxproxy chronyd[649]: System clock was stepped by -103565.091462 seconds
/var/log/messages:Jan 29 21:38:07 nginxproxy chronyd[649]: Selected source 138.236.128.112
/var/log/messages:Jan 29 21:39:13 nginxproxy chronyd[649]: Selected source 208.75.88.4
/var/log/messages:Jan 29 23:34:35 nginxproxy chronyd[649]: Selected source 10.254.0.1
/var/log/messages:Jan 30 06:16:14 nginxproxy chronyd[649]: Can't synchronise: no selectable sources
/var/log/messages:Jan 30 08:35:35 nginxproxy chronyd[649]: Source 138.236.128.112 offline
/var/log/messages:Jan 30 08:35:35 nginxproxy chronyd[649]: Source 10.254.0.1 offline
/var/log/messages:Jan 30 08:35:35 nginxproxy chronyd[649]: Source 204.2.134.162 offline
/var/log/messages:Jan 30 08:35:35 nginxproxy chronyd[649]: Source 208.75.88.4 offline
/var/log/messages:Jan 30 08:35:37 nginxproxy chronyd[649]: Source 138.236.128.112 online
/var/log/messages:Jan 30 08:35:37 nginxproxy chronyd[649]: Source 10.254.0.1 online
/var/log/messages:Jan 30 08:35:37 nginxproxy chronyd[649]: Source 204.2.134.162 online
/var/log/messages:Jan 30 08:35:37 nginxproxy chronyd[649]: Source 208.75.88.4 online
/var/log/messages:Jan 30 08:35:37 nginxproxy chronyd[649]: Selected source 10.254.0.1
/

            server 10.254.0.1 iburst
server 1.centos.pool.ntp.org iburst
server 2.centos.pool.ntp.org iburst
server 3.centos.pool.ntp.org iburst
# Use public servers from the pool.ntp.org project.
# Please consider joining the pool (http://www.pool.ntp.org/join.html).
            1 Reply Last reply Reply Quote 0
            • JaredBuschJ
              JaredBusch
              last edited by

              I am slowly but surely changing all the servers to the following

              # These servers were defined in the installation:
server 0.us.pool.ntp.org iburst
server 1.us.pool.ntp.org iburst
server 2.us.pool.ntp.org iburst
server 3.us.pool.ntp.org iburst
# Use public servers from the pool.ntp.org project.
# Please consider joining the pool (http://www.pool.ntp.org/join.html).
              1 Reply Last reply Reply Quote 1
              • JaredBuschJ
                JaredBusch
                last edited by

                So, the brand new server I setup on Sunday was just offline.

                The uptime on this server is only 15 hours because I shut it down yesterday to make a change to memory. and it was set to use the us pool when created.

                [root@bnasc ~]# uptime
 09:05:30 up 15:13,  3 users,  load average: 0.02, 0.02, 0.05
[root@bnasc ~]# cat /etc/chrony.conf
# These servers were defined in the installation:
server 0.us.pool.ntp.org iburst
server 1.us.pool.ntp.org iburst
server 2.us.pool.ntp.org iburst
server 3.us.pool.ntp.org iburst
# Use public servers from the pool.ntp.org project.
# Please consider joining the pool (http://www.pool.ntp.org/join.html).

                0_1485961470769_upload-84cba2f2-aff1-4ed3-9fe6-60fbd8601e0d

                [root@bnasc ~]# grep chrony /var/log/messages*
Jan 29 12:02:30 bnasc chronyd[628]: chronyd version 2.1.1 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +DEBUG +ASYNCDNS +IPV6 +SECHASH)
Jan 29 12:02:30 bnasc chronyd[628]: Generated key 1
Jan 29 11:52:40 bnasc chronyd[628]: Selected source 74.120.8.2
Jan 29 11:52:40 bnasc chronyd[628]: System clock wrong by -599.208892 seconds, adjustment started
Jan 29 11:52:40 bnasc chronyd[628]: System clock was stepped by -599.208892 seconds
Jan 29 11:54:52 bnasc chronyd[628]: Selected source 4.53.160.75
Jan 29 11:55:45 bnasc yum[10204]: Updated: chrony-2.1.1-4.el7.centos.x86_64
Jan 29 11:55:58 bnasc chronyd[628]: chronyd exiting
Jan 29 11:55:59 bnasc chronyd[11345]: chronyd version 2.1.1 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +DEBUG +ASYNCDNS +IPV6 +SECHASH)
Jan 29 11:55:59 bnasc chronyd[11345]: Frequency -15.874 +/- 5.866 ppm read from /var/lib/chrony/drift
Jan 29 11:56:04 bnasc chronyd[11345]: Selected source 216.218.254.202
Jan 29 11:57:11 bnasc chronyd[11345]: Selected source 132.163.4.102
Jan 29 17:23:45 bnasc chronyd[11345]: Source 38.229.71.1 offline
Jan 29 17:23:45 bnasc chronyd[11345]: Source 108.59.2.24 offline
Jan 29 17:23:45 bnasc chronyd[11345]: Source 216.218.254.202 offline
Jan 29 17:23:45 bnasc chronyd[11345]: Source 132.163.4.102 offline
Jan 29 17:23:45 bnasc chronyd[11345]: Can't synchronise: no selectable sources
Jan 29 17:23:46 bnasc chronyd[11345]: Source 38.229.71.1 online
Jan 29 17:23:46 bnasc chronyd[11345]: Source 132.163.4.102 online
Jan 29 17:23:46 bnasc chronyd[11345]: Source 108.59.2.24 online
Jan 29 17:23:46 bnasc chronyd[11345]: Source 216.218.254.202 online
Jan 29 17:23:47 bnasc chronyd[11345]: Selected source 132.163.4.102
Jan 29 23:39:31 bnasc chronyd[622]: chronyd version 2.1.1 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +DEBUG +ASYNCDNS +IPV6 +SECHASH)
Jan 29 23:39:31 bnasc chronyd[622]: Frequency -15.386 +/- 0.007 ppm read from /var/lib/chrony/drift
Jan 29 17:46:38 bnasc chronyd[622]: Selected source 71.210.146.228
Jan 29 17:46:38 bnasc chronyd[622]: System clock wrong by -21182.172665 seconds, adjustment started
Jan 29 17:46:38 bnasc chronyd[622]: System clock was stepped by -21182.172665 seconds
Jan 30 01:17:52 bnasc chronyd[616]: chronyd version 2.1.1 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +DEBUG +ASYNCDNS +IPV6 +SECHASH)
Jan 30 01:17:52 bnasc chronyd[616]: Frequency -15.397 +/- 0.041 ppm read from /var/lib/chrony/drift
Jan 29 21:37:17 bnasc chronyd[616]: Selected source 45.127.112.2
Jan 29 21:37:17 bnasc chronyd[616]: System clock wrong by -13244.251559 seconds, adjustment started
Jan 29 21:37:17 bnasc chronyd[616]: System clock was stepped by -13244.251559 seconds
Jan 29 21:49:12 bnasc chronyd[616]: Selected source 4.53.160.75
Jan 30 01:13:39 bnasc chronyd[616]: Selected source 45.127.112.2
Jan 30 06:23:50 bnasc chronyd[616]: Can't synchronise: no selectable sources
Jan 30 07:32:52 bnasc chronyd[616]: Selected source 45.127.112.2
Jan 30 14:38:54 bnasc chronyd[616]: chronyd exiting
Jan 31 07:37:15 bnasc chronyd[615]: chronyd version 2.1.1 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +DEBUG +ASYNCDNS +IPV6 +SECHASH)
Jan 31 07:37:15 bnasc chronyd[615]: Frequency -15.340 +/- 0.046 ppm read from /var/lib/chrony/drift
Jan 30 14:42:50 bnasc chronyd[615]: Selected source 167.88.117.204
Jan 30 14:42:50 bnasc chronyd[615]: System clock wrong by -60875.125649 seconds, adjustment started
Jan 30 14:42:50 bnasc chronyd[615]: System clock was stepped by -60875.125649 seconds
Jan 30 14:46:04 bnasc chronyd[615]: Selected source 173.255.246.13
Jan 30 14:50:52 bnasc chronyd[614]: chronyd version 2.1.1 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +DEBUG +ASYNCDNS +IPV6 +SECHASH)
Jan 30 14:50:52 bnasc chronyd[614]: Frequency -15.237 +/- 0.675 ppm read from /var/lib/chrony/drift
Jan 30 14:50:44 bnasc chronyd[614]: Selected source 74.120.81.219
Jan 30 14:50:44 bnasc chronyd[614]: System clock wrong by -16.271980 seconds, adjustment started
Jan 30 14:50:44 bnasc chronyd[614]: System clock was stepped by -16.271980 seconds
Jan 30 14:51:50 bnasc chronyd[614]: Selected source 204.2.134.163
Jan 30 14:52:55 bnasc chronyd[614]: Selected source 74.120.81.219
Jan 30 17:02:29 bnasc chronyd[614]: chronyd exiting
Jan 30 19:05:34 bnasc chronyd[633]: chronyd version 2.1.1 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +DEBUG +ASYNCDNS +IPV6 +SECHASH)
Jan 30 19:05:34 bnasc chronyd[633]: Frequency -15.245 +/- 0.393 ppm read from /var/lib/chrony/drift
Jan 30 17:04:13 bnasc chronyd[633]: Selected source 45.79.111.114
Jan 30 17:04:13 bnasc chronyd[633]: System clock wrong by -7289.265261 seconds, adjustment started
Jan 30 17:04:13 bnasc chronyd[633]: System clock was stepped by -7289.265261 seconds
Jan 31 07:57:55 bnasc chronyd[633]: Selected source 184.105.182.7
Jan 31 13:50:56 bnasc chronyd[633]: Selected source 45.79.111.114
Jan 31 17:50:41 bnasc chronyd[633]: chronyd exiting
Feb  1 18:29:46 bnasc chronyd[632]: chronyd version 2.1.1 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +DEBUG +ASYNCDNS +IPV6 +SECHASH)
Feb  1 18:29:47 bnasc chronyd[632]: Frequency -15.386 +/- 0.029 ppm read from /var/lib/chrony/drift
Jan 31 17:52:24 bnasc chronyd[632]: Selected source 216.218.254.202
Jan 31 17:52:24 bnasc chronyd[632]: System clock wrong by -88651.453210 seconds, adjustment started
Jan 31 17:52:24 bnasc chronyd[632]: System clock was stepped by -88651.453210 seconds
Jan 31 17:53:29 bnasc chronyd[632]: Selected source 199.102.46.76
Jan 31 18:04:17 bnasc chronyd[632]: Source 173.71.80.235 replaced with 74.82.59.143
Feb  1 02:26:09 bnasc chronyd[632]: Can't synchronise: no selectable sources
Feb  1 09:00:20 bnasc chronyd[632]: Source 107.151.174.199 offline
Feb  1 09:00:20 bnasc chronyd[632]: Source 216.218.254.202 offline
Feb  1 09:00:20 bnasc chronyd[632]: Source 199.102.46.76 offline
Feb  1 09:00:20 bnasc chronyd[632]: Source 74.82.59.143 offline
Feb  1 09:00:22 bnasc chronyd[632]: Source 107.151.174.199 online
Feb  1 09:00:22 bnasc chronyd[632]: Source 216.218.254.202 online
Feb  1 09:00:22 bnasc chronyd[632]: Source 199.102.46.76 online
Feb  1 09:00:22 bnasc chronyd[632]: Source 74.82.59.143 online
Feb  1 09:00:22 bnasc chronyd[632]: Selected source 199.102.46.76
[root@bnasc ~]#

                So WTF is chrony shit or what?

                1 Reply Last reply Reply Quote 0
                • JaredBuschJ
                  JaredBusch
                  last edited by

                  The DHCP server is set to a lease time of 6 hours.
                  0_1485961850580_upload-bb4c5a9c-8912-4034-911f-f7293502b2ee

                  Here is grep dhcp /var/log/messages and you can see the log timestamp going way ahead.

                  Jan 31 15:42:17 bnasc NetworkManager[662]: <info>  [1485898937.9740] dhcp4 (eth0):   address 10.254.0.36
Jan 31 15:42:17 bnasc NetworkManager[662]: <info>  [1485898937.9742] dhcp4 (eth0):   plen 24 (255.255.255.0)
Jan 31 15:42:17 bnasc NetworkManager[662]: <info>  [1485898937.9742] dhcp4 (eth0):   gateway 10.254.0.1
Jan 31 15:42:17 bnasc NetworkManager[662]: <info>  [1485898937.9742] dhcp4 (eth0):   server identifier 10.254.0.21
Jan 31 15:42:17 bnasc NetworkManager[662]: <info>  [1485898937.9743] dhcp4 (eth0):   lease time 21600
Jan 31 15:42:17 bnasc NetworkManager[662]: <info>  [1485898937.9743] dhcp4 (eth0):   nameserver '10.254.0.21'
Jan 31 15:42:17 bnasc NetworkManager[662]: <info>  [1485898937.9743] dhcp4 (eth0):   nameserver '10.254.0.27'
Jan 31 15:42:17 bnasc NetworkManager[662]: <info>  [1485898937.9743] dhcp4 (eth0):   domain name 'ad.bundystl.com'
Jan 31 15:42:17 bnasc NetworkManager[662]: <info>  [1485898937.9743] dhcp4 (eth0): state changed bound -> bound
Jan 31 15:42:17 bnasc nm-dispatcher: req:1 'dhcp4-change' [eth0]: new request (3 scripts)
Jan 31 15:42:17 bnasc nm-dispatcher: req:1 'dhcp4-change' [eth0]: start running ordered scripts...
Feb  1 18:29:49 bnasc NetworkManager[659]: <info>  [1485995389.2647] dhcp-init: Using DHCP client 'dhclient'
Feb  1 18:29:49 bnasc NetworkManager[659]: <info>  [1485995389.9799] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Feb  1 18:29:49 bnasc NetworkManager[659]: <info>  [1485995389.9932] dhcp4 (eth0): dhclient started with pid 761
Feb  1 18:29:50 bnasc NetworkManager[659]: <info>  [1485995390.2462] dhcp4 (eth0):   address 10.254.0.36
Feb  1 18:29:50 bnasc NetworkManager[659]: <info>  [1485995390.2462] dhcp4 (eth0):   plen 24 (255.255.255.0)
Feb  1 18:29:50 bnasc NetworkManager[659]: <info>  [1485995390.2463] dhcp4 (eth0):   gateway 10.254.0.1
Feb  1 18:29:50 bnasc NetworkManager[659]: <info>  [1485995390.2463] dhcp4 (eth0):   server identifier 10.254.0.21
Feb  1 18:29:50 bnasc NetworkManager[659]: <info>  [1485995390.2463] dhcp4 (eth0):   lease time 21600
Feb  1 18:29:50 bnasc NetworkManager[659]: <info>  [1485995390.2463] dhcp4 (eth0):   nameserver '10.254.0.21'
Feb  1 18:29:50 bnasc NetworkManager[659]: <info>  [1485995390.2463] dhcp4 (eth0):   nameserver '10.254.0.27'
Feb  1 18:29:50 bnasc NetworkManager[659]: <info>  [1485995390.2463] dhcp4 (eth0):   domain name 'ad.bundystl.com'
Feb  1 18:29:50 bnasc NetworkManager[659]: <info>  [1485995390.2464] dhcp4 (eth0): state changed unknown -> bound
Feb  1 09:00:20 bnasc NetworkManager[659]: <info>  [1485961220.8147] dhcp4 (eth0): canceled DHCP transaction, DHCP client pid 761
Feb  1 09:00:20 bnasc NetworkManager[659]: <info>  [1485961220.8147] dhcp4 (eth0): state changed bound -> done
Feb  1 09:00:22 bnasc NetworkManager[659]: <info>  [1485961222.0533] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Feb  1 09:00:22 bnasc NetworkManager[659]: <info>  [1485961222.0577] dhcp4 (eth0): dhclient started with pid 20673
Feb  1 09:00:22 bnasc NetworkManager[659]: <info>  [1485961222.1079] dhcp4 (eth0):   address 10.254.0.36
Feb  1 09:00:22 bnasc NetworkManager[659]: <info>  [1485961222.1080] dhcp4 (eth0):   plen 24 (255.255.255.0)
Feb  1 09:00:22 bnasc NetworkManager[659]: <info>  [1485961222.1080] dhcp4 (eth0):   gateway 10.254.0.1
Feb  1 09:00:22 bnasc NetworkManager[659]: <info>  [1485961222.1080] dhcp4 (eth0):   server identifier 10.254.0.21
Feb  1 09:00:22 bnasc NetworkManager[659]: <info>  [1485961222.1080] dhcp4 (eth0):   lease time 21600
Feb  1 09:00:22 bnasc NetworkManager[659]: <info>  [1485961222.1080] dhcp4 (eth0):   nameserver '10.254.0.21'
Feb  1 09:00:22 bnasc NetworkManager[659]: <info>  [1485961222.1080] dhcp4 (eth0):   nameserver '10.254.0.27'
Feb  1 09:00:22 bnasc NetworkManager[659]: <info>  [1485961222.1081] dhcp4 (eth0):   domain name 'ad.bundystl.com'
Feb  1 09:00:22 bnasc NetworkManager[659]: <info>  [1485961222.1081] dhcp4 (eth0): state changed unknown -> bound
                  1 Reply Last reply Reply Quote 0
                  • JaredBuschJ
                    JaredBusch
                    last edited by

                    Nothing in the DHCP Server event logs except the reservation creation and deletion informational events.

                    0_1485962795906_upload-35677eb9-1963-4c69-adf2-a2fe500b6fa7

                    1 Reply Last reply Reply Quote 0
                    • JaredBuschJ
                      JaredBusch
                      last edited by

                      I have no clue where to go with this now. Any recommendations would be greatly appreciated.

                      1 Reply Last reply Reply Quote 0
                      • JaredBuschJ
                        JaredBusch
                        last edited by JaredBusch

                        Look what I found..

                        grep clock /var/log/messages*
/var/log/messages-20170213:Feb 28 07:17:53 jaredweb kernel: Switched to clocksource hyperv_clocksource
/var/log/messages-20170213:Feb 28 07:17:53 jaredweb kernel: rtc_cmos 00:00: setting system clock to 2017-02-28 13:17:53 UTC (1488287873)
/var/log/messages-20170213:Feb 28 07:17:53 jaredweb kernel: Switched to clocksource hyperv_clocksource_tsc_page

                        How in the fuck do I fix this?

                        Time sync from the host has never been enabled. I realize it always gets it at boot and I did reboot last night because I updated the Hyper-V host.

                        The host also has the correct time.

                        C:\>time /t
04:03 PM

C:\>date /t
Mon 02/13/2017

C:\Users\bnaadmin>

                        0_1487023176288_upload-dcf7870a-69c7-4de9-a003-cc359b10a384

                        ObsolesceO 1 Reply Last reply Reply Quote 0
                        • JaredBuschJ
                          JaredBusch
                          last edited by

                          Do I blame integration services for this one? Microsoft has a different line of Integration services that can be installed, but then it breaks the built in package method.

                          1 Reply Last reply Reply Quote 0
                          • JaredBuschJ
                            JaredBusch
                            last edited by JaredBusch

                            This would also be why @scottalanmiller never sees this. I do not believe that he has hyper-v running anywhere with a bunch of CentOS systems on it, that are also using DHCP.

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

                              @stacksofplates said in CentOS 7 VM on Hyper-V losing DHCP assigned address:

                              You could also just go back to ntpd. It's still available and might not have the issue. It also has a file under /etc/sysconfig/ntpd where you can set ntpd to update the hw clock.

                              Looks like chrony was actually keeping things good. It was just not catching the weird skew from the hardware good enough.

                              stacksofplatesS 1 Reply Last reply Reply Quote 1
                              • momurdaM
                                momurda
                                last edited by

                                I dont have a specific answer for you, but I always seem to have a problem with pool.org ntp servers. So much so that i dont use them anymore.
                                I use nist servers instead.
                                time.nist.gov global address for all servers Multiple locations
                                time-nw.nist.gov 131.107.13.100 Microsoft, Redmond, Washington
                                There are probably other regional ones nearer to you

                                JaredBuschJ 1 Reply Last reply Reply Quote 0
                                • JaredBuschJ
                                  JaredBusch @momurda
                                  last edited by gjacobse

                                  @momurda said in CentOS 7 VM on Hyper-V losing DHCP assigned address:

                                  I dont have a specific answer for you, but I always seem to have a problem with pool.org ntp servers. So much so that i dont use them anymore.

                                  Problem seems to not be with the ntp.org servers. It is the hardware clock seemingly being random as f***.

                                  1 Reply Last reply Reply Quote 0
                                  • momurdaM
                                    momurda
                                    last edited by momurda

                                    @JaredBusch said in CentOS 7 VM on Hyper-V losing DHCP assigned address:

                                    Look what I found..

                                    grep clock /var/log/messages*
/var/log/messages-20170213:Feb 28 07:17:53 jaredweb kernel: Switched to clocksource hyperv_clocksource
/var/log/messages-20170213:Feb 28 07:17:53 jaredweb kernel: rtc_cmos 00:00: setting system clock to 2017-02-28 13:17:53 UTC (1488287873)
/var/log/messages-20170213:Feb 28 07:17:53 jaredweb kernel: Switched to clocksource hyperv_clocksource_tsc_page

                                    I just noticed the time skew here 1488287873 seconds is the real time, inseconds, since Unix Time began. Is it possibly something wrong with the clock on the hw itself? Battery, something else not easily fixable.
                                    edit: unless the time wasnt actually 00:00 jan 1 1970 when it was changed
                                    edit2: your clock was actually in the future here and set back in time a couple weeks. ignore what i say.

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

                                      @momurda said in CentOS 7 VM on Hyper-V losing DHCP assigned address:

                                      @JaredBusch said in CentOS 7 VM on Hyper-V losing DHCP assigned address:

                                      Look what I found..

                                      grep clock /var/log/messages*
/var/log/messages-20170213:Feb 28 07:17:53 jaredweb kernel: Switched to clocksource hyperv_clocksource
/var/log/messages-20170213:Feb 28 07:17:53 jaredweb kernel: rtc_cmos 00:00: setting system clock to 2017-02-28 13:17:53 UTC (1488287873)
/var/log/messages-20170213:Feb 28 07:17:53 jaredweb kernel: Switched to clocksource hyperv_clocksource_tsc_page

                                      I just noticed the time skew here 1488287873 seconds is the real time, inseconds, since Unix Time began.

                                      That is not displaying a skew, that is displaying the time it is setting it to.

                                      1 Reply Last reply Reply Quote 0
                                      • JaredBuschJ
                                        JaredBusch
                                        last edited by

                                        A little more digging, but no answers yet.

                                        cat /sys/devices/system/clocksource/clocksource0/current_clocksource
hyperv_clocksource_tsc_page


cat /sys/devices/system/clocksource/clocksource0/available_clocksource
hyperv_clocksource_tsc_page hyperv_clocksource acpi_pm
                                        1 Reply Last reply Reply Quote 0
                                        • stacksofplatesS
                                          stacksofplates @JaredBusch
                                          last edited by

                                          @JaredBusch said in CentOS 7 VM on Hyper-V losing DHCP assigned address:

                                          @stacksofplates said in CentOS 7 VM on Hyper-V losing DHCP assigned address:

                                          You could also just go back to ntpd. It's still available and might not have the issue. It also has a file under /etc/sysconfig/ntpd where you can set ntpd to update the hw clock.

                                          Looks like chrony was actually keeping things good. It was just not catching the weird skew from the hardware good enough.

                                          Ya I have found chronyd to be more reliable than ntpd, but that's anecdotal. I can't say I've seen this happen, but I don't have any Hyper-V servers at all. Even though I don't have DHCP setup (I want to move all of our static stuff to reservations though), I would at least notice because we authenticate to all of the RHEL systems with Kerberos

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

                                            @JaredBusch said in CentOS 7 VM on Hyper-V losing DHCP assigned address:

                                            Look what I found..

                                            grep clock /var/log/messages*
/var/log/messages-20170213:Feb 28 07:17:53 jaredweb kernel: Switched to clocksource hyperv_clocksource
/var/log/messages-20170213:Feb 28 07:17:53 jaredweb kernel: rtc_cmos 00:00: setting system clock to 2017-02-28 13:17:53 UTC (1488287873)
/var/log/messages-20170213:Feb 28 07:17:53 jaredweb kernel: Switched to clocksource hyperv_clocksource_tsc_page

                                            How in the fuck do I fix this?

                                            Time sync from the host has never been enabled. I realize it always gets it at boot and I did reboot last night because I updated the Hyper-V host.

                                            The host also has the correct time.

                                            C:\>time /t
04:03 PM

C:\>date /t
Mon 02/13/2017

C:\Users\bnaadmin>

                                            0_1487023176288_upload-dcf7870a-69c7-4de9-a003-cc359b10a384

                                            Can you remind me again why you will not or can not use the Hypervisor time? Does the time match the host if you actually enable the "Time Synchronization" service?

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