similar to: Clock skew on domU, no ntpd

I am posting the message below again because it did not go through last night. Help! Steve Timm -- ------------------------------------------------------------------ Steven C. Timm, Ph.D (630) 840-8525 timm@fnal.gov http://home.fnal.gov/~timm/ Fermilab Computing Division, Scientific Computing Facilities, Grid Facilities Department, FermiGrid Services Group, Assistant Group Leader.

I have a Xen DomU configuration that was made in the days before libvirt and virt-install. In this configuration I have: vif = [ ''mac=00:16:3e:05:06:01, bridge=xenbr0'', ''mac=00:16:3e:05:06:0a, bridge=xenbr1'' ] and then in xend-config.sxp I define (network-script my-network-bridge) where my-network-bridge is in the scripts directory and looks like this:

I have the xensource 3.1.0 x86_64 tarball installed over a RHEL5 clone distribution. The "ethtool" utility only returns the following information: [root@fermigrid5 etc]# ethtool eth0 Settings for eth0: Link detected: yes [root@fermigrid5 etc]# Since I have no vanilla-installed rhel5 machines with which to compare, I am not sure if I am dealing with a bug in the ethtool (whose

I''m running xen 3.1.2 as bastardized by RedHat on a redhat clone operating system. I''m using the xendomains script as it came out of the box to start my domU''s at boot and stop them at shutdown. There are three problems right now: 1) left to its own devices, service xendomains stop attempts to do "xm save" on each of the domU''s. that takes quite a

I have installed the xen 3.1.0 x86_64 tarball compiled for RHEL5 on a RHEL5 system. The system in question was able to boot with the xen kernel that came with RHEL5. I untarred the tarball, and did cd /boot mkinitrd /boot/initrd-2.6.18-xen.img 2.6.18-xen The command exited properly and made a initrd image. The machine booted with a grub.conf entry like this: title Xen 3.1.0 root

Hi all, After rebooting my CentOS 5.5 server, i have the following message: ================================== Red Hat nash version 5.1.19.6 starting EXT3-fs: unable to read superblock mount: error mounting /dev/root on /sysroot as ext3: invalid argument setuproot: moving /root failed: No such file or directory setuproot: error mounting /proc: No such file or directory setuproot: error mounting

I installed 64-bit xen 3.1.0 (from xensource.com tarballs) on three new machines today, using a configuration setup that I''ve used successfully many times before. However, I encountered a new problem. These are Dell Poweredge 1950 servers, by the way. >From lspci 04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12) 08:00.0 Ethernet

Has anyone yet figured out what it would take to make Xen run on top of the Red Hat Enterprise Linux 6 beta? We are heavily invested in Xen under RHEL5 (actually a redhat clone) distribution, but already the xen kernel they are shipping with update 4 and 5 is shaky and has bugs which they don''t seem to be in a hurry to fix. Basically I am wondering if Redhat 6 is just going to have

I have seen the following kernel panic 5 times today on three different machines, two of which had been stable for months and one of which is a brand new install. We are running the x86_64 xen kernel and userland tools that came in the Xen 3.1.0 tarball from xen.org, on top of scientific linux (redhat clone) 5.1 or 5.2. <Aug/28 12:21 pm>Unable to handle kernel NULL pointer dereference at

Hi, ok this time i have really done every thing i can do. i went to http://www.bytefusion.com/download/win2000/middle.htm and downloaded the presentTense time server for windows 2000. i installed it on my backup domain controller. my sys admin wont allow it on the primary domain controller. ok so after installing it on niit91 (10.10.11.91) i came back to my linux box started the ntpd and

Hi Andrew, Am 28.08.2016 um 11:05 schrieb Andrew Bartlett via samba: > Many clients will use the error generated above to re-sync their clock > to the KDC, to avoid failure in this case. > > Or, they will log in with NTLM over the NETLOGON service. > > Time in modern networks is just too fragile to allow for direct failure > here, so a lot of work is done to avoid it, both

This ntp.conf file works fine under RedHat 9: authenticate no #enable auth driftfile /etc/ntp/drift keys /etc/ntp/ntp.keys server 127.127.1.0 fudge 127.127.1.0 stratum 10 trustedkey 1 enable bclient broadcastclient However, it doesn't work on CentOS 4.1. ntpd complains with this error message: Unable to listen for broadcasts, no

On Sun, 2016-08-28 at 12:42 +0200, Marc Muehlfeld wrote: > Hi Andrew, > > Am 28.08.2016 um 11:05 schrieb Andrew Bartlett via samba: > > > > Many clients will use the error generated above to re-sync their > > clock > > to the KDC, to avoid failure in this case. > > > > Or, they will log in with NTLM over the NETLOGON service.  > > > >

Hi Experts , I have a situation where I have to demonstrate that if the time difference between Samba4 (AD) and Windows Client is more that 5 Min ( as per Kerbrose ) , the user should note be allowed to login via that windows PC . When I simulate it I get Clock skew in the logs ( as shown below ) but the user is allowed to login . / Kerberos: Too large time skew, client time

Does anyone know if the Xen 3.1.0 kernels as distributed in the "open source" tarballs (x86_64 version) are vulnerable to the recently-announced vulnerability CVE-2007-4573? IF so, is there any plan to release patched tarballs anytime soon? Thanks Steve Timm -- ------------------------------------------------------------------ Steven C. Timm, Ph.D (630) 840-8525 timm@fnal.gov

This ntp.conf file works fine with RedHat Enterprise 3.0 and below. However, it doesn't work with CentOS 4.1. #authenticate no #enable auth driftfile /etc/ntp/drift keys /etc/ntp/ntp.keys server 127.127.1.0 <http://127.127.1.0> fudge 127.127.1.0 <http://127.127.1.0> stratum 10 trustedkey 1 enable bclient broadcastclient This is the error reported in /var/log/messages: Sep 29

I'm running latest CentOS 4.3 (2.6.9-34.0.2.ELsmp) and found that the included 'ntpd' 4.2.0a at 1.1190-r will not accept NTP broadcast packets. There is a documented bug in ntpd 4.2.0 to this effect, resolved way back in 2004: https://ntp.isc.org/bugs/show_bug.cgi?id=267 Any chance someone can include a more recent version of 'ntpd' in the next CentOS RPM update

I've been running Samba 4x on FreeBSD successfully for years with a single Active Directory domain controller but have recently added a second domain controller. The setup worked great for a few days but suddenly developed a series of permission-denied style errors and UID mapping errors on the new/second DC2 which I've been slowly working through. My current issue which I've been

On Sat, 2016-08-27 at 19:56 +0530, Biswajit Banerjee via samba wrote: > Hi Experts , > > I have a situation where I have to demonstrate that if the time  > difference between  Samba4 (AD) and Windows Client is more that 5 Min > (  > as per Kerbrose ) , the user should note be allowed to login via > that  > windows PC . > > When I simulate it I get Clock skew in the

Hi, I'm having a problem with significant clock skew on fedora29 with qemu-system-x86-3.0.0 and ibvirt-daemon-kvm-4.7.0. This is on my desktop and appears to happen between suspends of the host each night. It appears like the time just stops while the guest is suspended, of course, but then doesn't update once the guest is resumed. I'm pretty sure time is configured correctly on the