similar to: sync guest time

On Thu, Apr 30, 2020 at 2:15 PM Daniel P. Berrangé <berrange@redhat.com> wrote: > > On Thu, Apr 30, 2020 at 01:52:12PM +0200, Miguel Duarte de Mora Barroso wrote: > > Hi, > > > > I'm seeing the following issue when attempting to update the guest's > > clock on a running fc32 guest (using guest agent): > > > > ``` > >

On Thu, Apr 30, 2020 at 01:52:12PM +0200, Miguel Duarte de Mora Barroso wrote: > Hi, > > I'm seeing the following issue when attempting to update the guest's > clock on a running fc32 guest (using guest agent): > > ``` > [root@virt-launcher-vmi-masquerade-mh2xm /]# virsh domtime 1 --pretty > Time: 2020-04-30 23:27:29 > [root@virt-launcher-vmi-masquerade-mh2xm

Hi friends, I am running Nagios 2.7-1 on Centos 5.0 32-bit hosted on Vmware ESX 4.0. The issue I am seeing on the server is sometimes nagios is showing the below messages in /var/log/messages and as the system time gets changed some false alarms gets generated. I searched it on the google but I am not able to find the correct solution. I even posted on the nagios forum and they asked me to see

Hi all. When resuming guest after suspend, the time is wrong (because the guest doesn't know it has been suspended). Apparently, ntp running on the guest doesn't solve this. At least on Linux system. I read it works on Windows guests. I don't understand why, so I'd appreciate a link to an explanation, but I understand it is out of scope for this list. The HW clock is correct and

On Friday, 15 May 2020 11.33.26 WEST I?aki Ucar wrote: > The rationale behind the user settings is that the user dir is not > controlled by the system, so versioning it is the only way to avoid > breakage. For the system library, there are better tools to prevent > that. Do you know the difference between theory and practice? :-) In theory they are equal but in practice... :-) >

On Thursday, 14 May 2020 23.58.02 WEST I?aki Ucar wrote: > But we still have to rebuild the packages anyway, and this setup > doesn't force us to actually rebuild them, nor the user to update > them. So a user could end up with R major.minor and a bunch of > packages installed in some major.minor-1 path that are just junk. Or > the other way around: a bunch of packages updated

On Tue, 7 Jul 2020 at 09:58, Jos? Ab?lio Matos <jamatos at fc.up.pt> wrote: > > On Tuesday, 7 July 2020 11.44.48 WEST I?aki Ucar wrote: > > Try with the CLI (see "man bodhi"): > > > > $ bodhi updates edit <update> --addbuilds <builds> > > I found that the best call in this case is instead of --addbuilds to use > --from-tag since then

I am trying to hwclock to set the time. (hwclock -w) this is what I get on standard 5.2 x86_64. hwclock --debug hwclock from util-linux-2.13-pre7 hwclock: Open of /dev/rtc failed, errno=19: No such device. No usable clock interface found. Cannot access the Hardware Clock via any known method. [root at devcentos5x64 src]# ls -l /dev/rtc crw------- 1 root root 10, 135 Feb 6 13:32 /dev/rtc Any

Hi. I run peridocally (from cron) on all of my machines 30 * * * * root /sbin/hwclock --systohc All of those machines in question take their time via NTP from the same local server, and that server gets its time from a ntp pool. Now I had to reboot a couple of them two days ago and to my surprise all had problems with the time upon booting. Here are the important files: [root at XXXXXX ~]

On Sat, Feb 07, 2015 at 01:05:58PM -0600, g wrote: > so much for all that. > > i just thought it was working. :-( > > only way i can get system clock to show correct CST is to set bios > clock to CST. I suggest reading the man page for 'hwclock'. Namely, the --utc option. If you don't tell your system that the BIOS is stored as UTC, then it will assume it's

I am getting this error: hwclock --debug hwclock from util-linux-2.13-pre7 hwclock: Open of /dev/rtc failed, errno=16: Device or resource busy. No usable clock interface found. Cannot access the Hardware Clock via any known method. [root at devcentos5x64 src]# uname -a Linux devcentos5x64.msgnet.com 2.6.18-128.el5 #1 SMP Wed Jan 21 10:41:14 EST 2009 x86_64 x86_64 x86_64 GNU/Linux rpm -qa | grep

Hi all, I am having an issue with some older CentOS 5.3 servers. Every time the server boots, it gives the error "Cannot access the hardware clock by any known method", and then promptly sets the time 5 hours behind the hardware clock, down to the second. After the system is up. "hwclock" works fine. hwclock --debug does not show any error at all. The hardware clock is

On Tue, 7 Jul 2020 at 12:38, Jos? Ab?lio Matos <jamatos at fc.up.pt> wrote: > > On Monday, 6 July 2020 21.08.53 WEST Tom Callaway wrote: > > R-BiocFileCache is now branched for f32 (finally). You should be able to > > build it if/when the PDC comes back up. Lotta random outages right now. > > > > Tom > > I have re/built them using the side tag but I do not

Does any know of a way to sync the hardware clock without a reboot? Graham Johnston Senior Network Analyst Westman Communications Group 204.725.4300 ext 382 johnstong at westmancom.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20060719/70ef23ce/attachment-0002.html>

Is there a package to do this? Normally the hardware clock is set during shutdown if one is running ntpd. But if a long-running server shuts down unexpectedly, this isn't done, and the hardware clock might be off by a lot when it comes back up. So setting it periodically from a cron job could be useful. What do others do? Adding a one liner to /etc/cron.daily that invokes

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.16.1"> </HEAD> <BODY> Hello All, I have a problem with hwclock on centos 5.3. in xen guest environment<FONT

Hello, I'm having a major problem with the timestamps in both the Icecast access.log and error.log. The timestamp on the logfiles themselves is accurate, but the logging of the various connections to my streams is in UTC. No matter how I try to configure the hwclock or the system clock, the log timestamp is always UTC, which is 8 hours ahead of my current time zone. I've even tried

Hi Folks, how do you handle the change from standard time to daylight saving time? We are using LotusNotes 6.5.1 and Wine 20041019 on Kubuntu 5.10 Breezy Badger. This is the combination where we experienced the least amount of Bugs. Our hosts run UTC on the hardwareclock and live in the timezone Europe/Vienna, which will change from CET to CEST on sunday. Tests have shown, that

Hi BACKGROUND INFO:I have a new Eaton 5E 1100i USB UPS which their website claims is supported on Linux. They don't provide software for it for Linux, only for Windows.Referring links: https://www.eaton.com/za/en-gb/catalog/backup-power-ups-surge-it-power-distribution/Eaton_5E_UPS.html https://www.eaton.com/za/en-gb/skuPage.5E1100IUSB.specifications.html It was manufactured in May 2020

Hi, the date jumps within 30 seconds to a wrong value. ntp service is stopped at the beginning. Whereas hwclock seems more precise. [root at kerio ~]# service ntpd stop Shutting down ntpd: [ OK ] [root at kerio ~]# ntpdate 0.centos.pool.ntp.org 13 Mar 07:04:48 ntpdate[23003]: step time server 131.234.137.24 offset -3450.678273 sec [root at