Reminder of the L-Root IPv6 address renumbering (fwd)
Anyone know if there's a planned bind RPM update for this? Antonio Querubin e-mail: t...@lavanauts.org xmpp: antonioqueru...@gmail.com -- Forwarded message -- Date: Sun, 20 Mar 2016 18:38:07 + From: David Soltero To: "na...@nanog.org" Subject: Reminder of the L-Root IPv6 address renumbering This is reminder that there is a scheduled change to the IPv6 addresses for the L-Root server, that will take effect on March 23, 2016. The new IP addresses for the L.ROOT-SERVERS.NET will be: 199.7.83.42 2001:500:9f::42 Please remember to update your root “hints” files on your DNS infrastructure.
Re: "Not using downloaded repomd.xml because it is older than what we have:"
On Wed, 9 Mar 2016, John Pilkington wrote: But doesn't SL7 use chrony? We're talking servers (ie. always on systems) right? - where supposedly ntpd is the better choice. I would think the mirrors are running ntpd instead of chronyd. But this discussion got me to rechecking again why ntpd wasn't starting up on some of my own servers and it turns out chronyd was still enabled on those. Perhaps the repo servers have the same issue? Antonio Querubin e-mail: t...@lavanauts.org xmpp: antonioqueru...@gmail.com
RE: "Not using downloaded repomd.xml because it is older than what we have:"
On Wed, 9 Mar 2016, Thomas Leavitt wrote: No feedback? Is everyone else just ignoring these messages? -Original Message- From: owner-scientific-linux-us...@listserv.fnal.gov [mailto:owner-scientific-linux-us...@listserv.fnal.gov] On Behalf Of Thomas Leavitt Sent: Monday, February 29, 2016 10:53 AM To: scientific-linux-us...@fnal.gov Subject: RE: "Not using downloaded repomd.xml because it is older than what we have:" Not using downloaded repomd.xml because it is older than what we have: Current : Tue Feb 16 08:58:20 2016 Downloaded: Tue Feb 16 08:58:13 2016 A 7 second variance shouldn't be that much of an issue. A time offset greater than a fraction of second suggests ntpd really isn't time-synced. Not sure if this is related but I've found that ntpd on SL7 systems dies during bootup and require a manual start (using an unchanged ntp.conf). This is what I see immediately after doing a fresh boot of a SL7 system: $ sudo systemctl status ntpd ● ntpd.service - Network Time Service Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; vendor preset: disabled) Active: inactive (dead) $ sudo systemctl restart ntpd $ sudo systemctl status ntpd ● ntpd.service - Network Time Service Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; vendor preset: disabled) Active: active (running) since Tue 2016-03-08 19:22:28 HST; 3s ago Process: 2417 ExecStart=/usr/sbin/ntpd -u ntp:ntp $OPTIONS (code=exited, status=0/SUCCESS) Main PID: 2418 (ntpd) CGroup: /system.slice/ntpd.service └─2418 /usr/sbin/ntpd -u ntp:ntp -g Mar 08 19:22:28 sl7-dev ntpd[2418]: Listen and drop on 1 v6wildcard :: UDP 123 Mar 08 19:22:28 sl7-dev ntpd[2418]: Listen normally on 2 lo 127.0.0.1 UDP 123 Mar 08 19:22:28 sl7-dev ntpd[2418]: Listen normally on 3 eth0 67.53.202.252...23 Mar 08 19:22:28 sl7-dev ntpd[2418]: Listen normally on 4 lo ::1 UDP 123 Mar 08 19:22:28 sl7-dev ntpd[2418]: Listen normally on 5 eth0 fe80::5054:ff...23 Mar 08 19:22:28 sl7-dev ntpd[2418]: Listen normally on 6 eth0 2605:b00:0:2:...23 Mar 08 19:22:28 sl7-dev ntpd[2418]: Listening on routing socket on fd #23 f...es Mar 08 19:22:29 sl7-dev ntpd[2418]: 0.0.0.0 c016 06 restart Mar 08 19:22:29 sl7-dev ntpd[2418]: 0.0.0.0 c012 02 freq_set kernel -0.605 PPM Mar 08 19:22:29 sl7-dev ntpd[2418]: 0.0.0.0 c615 05 clock_sync If the mirror masters are running SL7 and ntpd is enabled for time sync, somebody may want to verify that ntpd really is running on them. Antonio Querubin e-mail: t...@lavanauts.org xmpp: antonioqueru...@gmail.com
Re: repositories need IPv6 connectivity
On Sat, 6 Feb 2016, Steven C Timm wrote: I can't give any specific dates--but I can say that the main Fermilab websites have been ipv6 accessible for quite some time and we are in the process of testing IPv6 in our scientific networks so it will eventually be available for the linux repository. Does SL have a ticket system that this can be added to so that it's not forgotten? Antonio Querubin e-mail: t...@lavanauts.org xmpp: antonioqueru...@gmail.com
Re: repositories need IPv6 connectivity
On Thu, 28 Nov 2013, Antonio Querubin wrote: Date: Thu, 28 Nov 2013 08:43:16 -1000 From: Antonio Querubin To: scientific-linux-de...@fnal.gov Subject: repositories need IPv6 connectivity Would it be possible to provide IPv6 connectivity for the repositories ftp*.scientificlinux.org? Doing updates for hosts/networks that are IPv6-only is challenging... It's been over two years since I initially inquired about getting IPv6 connectivity for the repo server. Is this on anyone's RADAR to implement? Antonio Querubin e-mail: t...@lavanauts.org xmpp: antonioqueru...@gmail.com
Re: SL 6.7 Kernel headers misses typedef sa_family_t
On Thu, 14 Jan 2016, Mark Stodola wrote: It looks like sa_family_t has been morphing over time. In SL5, it is indeed defined in linux/socket.h. In SL6 I find it defined in bits/sockaddr.h. In SL7 it continues to be in bits/sockaddr.h, but there is also __kernel_sa_family_t defined in linux/socket.h. Try adding bits/sockaddr.h to your includes. That probably should be . From the sockaddr.h: * Never include this file directly; use instead. Antonio Querubin e-mail: t...@lavanauts.org xmpp: antonioqueru...@gmail.com
