Software :: Cron Clock Is An Hour Off To System Time
Mar 31, 2010
I have cron jobs running and the timing is critical, because I'm running Nessus scans on production servers. If I hit them at the wrong time, I'm toast. But when I check the cron log, I see that it is an hour off. Here is the output for the command "clock":
Wed 31 Mar 2010 03:01:26 PM CDT -0.257677 seconds
And this is the tail of the cron log:
Mar 31 16:00:01 nes-001 CROND[8790]: (root) CMD (/Nessus/Targets/NessusScriptDataCenterScan.test)
Mar 31 16:01:02 nes-001 CROND[8822]: (root) CMD (run-parts /etc/cron.hourly)
Mar 31 16:01:02 nes-001 run-parts(/etc/cron.hourly)[8822]: starting 0anacron
Mar 31 16:01:02 nes-001 anacron[8832]: Anacron started on 2010-03-31
Mar 31 16:01:02 nes-001 anacron[8832]: Normal exit (0 jobs run)
Mar 31 16:01:02 nes-001 run-parts(/etc/cron.hourly)[8834]: finished 0anacron
Cron thinks it is 4:00 p.m., but it's really 3:00 p.m. How do I tell Cron what time it is? (Stopping and restarting the crond service did not change it.)
I recently decided to try KDE4 and would like the change the clock on the panel to display 12 hour format and not the default 24hour format but i can not find where to change this option currently the clock looks like the attached picture. Gnome has this option and I would like to see it in KDE if it exists in the default clock. I am willing to replace the default KDE clock with a seperate widget if one exists for this.
Today I updated a bunch of packages, rebooted. I run lucid 10.04 x86_64, originally Xubuntu but now gnome since I cannot make xfce4-panel tasklist behave with compiz. Anyway, by the end of the day my clock was 10min off. If I use ntpdate at about 10min intervals I see things like:
$ sudo ntpdate time.xxx.xxx.de 1 Jun 18:37:02 ntpdate[9734]: step time server xxx.xxx.xxx.xxx offset 10.043055 sec
I have deleted /etc/adjtime and touch'd a blank file to no avail.
Is this problem serious? Is it likely software or hardware? Is running an ntp daemon the right solution or would it be masking a new software or hardware problem that appeared today?
I just switched over to Lubuntu, and so far, it's been great.It's rendering quite well with my laptop, even though the fan is constantly running.I've had some small annoyances that I haven't been able to figure out. How do I get the power button and/or other related actions to the 'start' menu? Is there a way to drag and drop applets like in Ubuntu? How do I setup default brightness like in Ubuntu? How do I change the time to normal US time (12 hour instead of 24 hour)How do I change the time to a 12-hour instead of 24-hour?Is there a software center?
Try as I might I cannot seem to get the system clock to display local time. It looks like it's stuck on GMT. In the System>Administration>Time and Date I have my local time zone set correctly and also set to update automatically with an appropriate time server selected. It still displays my local time +5 hours (I'm central time, USA).
I restored my .kde directory after changing some stuff unrelated to my clock and now all plasma clocks are exactly 5 hours faster than my system time (the correct time).I've set the time zone for Date&Time in System Settings properly and that's working well and I've ALSO gone into the time zone settings for the plasma widgets and switched between UTC and Local manually but that doesn't do anything.
Yesterday I configured an NTP Server, and synched a sever with my NTP Server. Now some how my Client clock jumped one hour ahead at 12:00 AM, while HW Clock and NTP Server Clock remained.
Code: cat /etc/sysconfig/clock # The ZONE parameter is only evaluated by system-config-date. # The timezone of the system is defined by the contents of /etc/localtime. ZONE="Asia/Karachi"
I have adjust the clock to my country current time but after a reboot,all the setting is gone. How to permanently setting the correct time?I have select my country region.
I'm setting the hardware clock on RHEL 5.1 system using /sbin/hwclock --systohc. After setting the clock I issue a date command followed by a /sbin/hwclock --show from within a script to get fast resolution and I see that the hardware clock precedes the system time on average by .5 seconds. I would think the clock should be identical after setting.
My server is a VPS which is running with CentOS. I found a wield problem that the system clock always runs faster than the hardware clock. For example, I set system clock and hardware clock both on 20:00. After about half an hour, the system clock will be 20:34/5 which is wrong while the hardware clock remains correct (20:30).
Very simple question but very frustrating as none of the other threads/bug reports/whatever have had quite the same problem. I want gnome clock to display the time in 12 hour format. The suggested solution is something like right-click the clock -> Preferences and somewhere there will be an option to choose 12/24 hour time. Problem is I don't have that option.
The help has a note that 12 hour time "is not shown if your session language does not use the 12 hour clock" but this really shouldn't be a problem? My language/locale/city, everything I can think of, it's all some variation of en_GB, UK English, Brisbane, Australia: all places which should allow the option of 12 hour clock! So why don't I have that option?
I have Ubuntu 10.04.1 32bit installed on my flash drive so wherever I go I can have my own mini personal computer, but one problem I'm having is every computer it is run on the next time it's rebooted to the OS on the hard drive it has UTC time instead of the actual time for the timezone you're in that Windows uses. So is their a way I can make Ubuntu not automatically change the clock to what it wants?
I wish to run a cron job every half hour, where exactly do I put the job? The reason I am asking is that I am used to entering jobs into crontab, I am not used to using fedora and its cron layout.
I found (Red Hat Fedora Core 6 Server) a CRON entry for "backupmng" that has repeats at 1,16,31 and 46 minutes every hour of every day, 24/7.It is located at:/usr/local/psa/admin/sbin/backupmng >/dev/null 2>&1.
If I set the clock to speak the time, I get this when it tries: starting kttsd failed. I've looked at the various posts, but haven't yet found an actual solution. I've tried to run kttsmgr, but for some reason the "run" dialog doesn't seem to do anything - no error, nothing. Type kttsmgr, press enter since there is not obvious other way to execute the command, and nothing happens.
Is this a module that does not come with KDE? And I give - I can't find time format anywhere. How do you change the clock that appears in the lower right corner to 12 hour instead of what appears to be default 24 hour? I don't see it in "Digital Clock Settings", and I don't see it in System Settings - Date & Time. This is a clean install of slackware 13.1, and whatever version of KDE comes with it.
I'm experiencing a problem with cron.hourly running mcelog.cron on Fedora 11:Quote:mcelog: warning: 18446744073709551600 bytes ignored in each recordmcelog: consider an updateI've read a dead end email thread here from February 2010 describing what I am seeing on Fedora here:Does anyone have any insight into this problem? This is relevant portion of strace(1)ing mcelog which shows /dev/mcelog is open()d and configured correctly:Quote:
Previously I had posted a question on how to make it run every 7 minutes between 7 and and 11pm.However now I found out what I really need is every 7 minuted between 7:30 and 11pm BUT it has to be every 7 minutes, it cannot reset itself on the top of every hour, so the */7 wont work.How can it that it will be every 7 minutes, so it will go at 7:30, 37,44,51, 58, 8:05, etc..
Recently moved into amazon's ec2 cloud and noticed our server time was in UTC where we use EST. I did some looking around, and changed using the following;
Followed up setting the correct time using the date command with the correct time, then date showed;
Now, that is correct, but if I do an ntpdate pool.time.org or any other time server, the offset is huge and the date moves back one hour. Is this a daylight settings or something I am just missing?
I was wondering if any one came across that issue before. Everytime I reboot my PC something (I assume GNOME) reset my system clock to an hour behind what is was the last time. So if a reboot twice in a row that'll be two hours behind and so on. It used to work fine until I had to change my system time backward temporally to overcome and issue with GPG. Since I put it back I get that phenomena. It's like it's adjusting it for the Day light saving everytime a boot. Problem is Japan does not have any day light saving. I run OpenSuse 11.2 with Gnome 2.28.2 as my interface. I'm currently located in Japan GMT+9 not DST. /etc/localtime -> /usr/share/zoneinfo/Asia/Tokyo
I suspect a bug in Gnome or Yast. It's not user specific because the time is already altered even before I log it.
How do I prevent mplayer from sending e-mail by the time mplayer plays the wave file that speaks the time?
Here is the script I use to speak time. I use my natural voice to record like this:
Code:
Last, but not least, I wrote the script:
Code:
Note that I've commented out /bin/cat as a bandage solution to delete mail after mplayer plays the file. I said "bandage solution" because if I have grayson@ubuntu-server forward mail to my e-mail account through SMTP relay, I'm going to be seeing the e-mail messages sent every hour and I need to stop this from happening in the first place.
Example of the mail I've been getting in /var/mail/grayson: