Hello, friends.
I have a problem with my crontab for root and non-root user.
I created:
0 9 * * * /home/oracle/bin/checktablespace.sh
This script executed in 17:00
I founded:

# hwclock
Wed 22 Jan 2014 03:06:23 PM MSK -0.824326 seconds

# date
Wed Jan 22 11:06:50 MSK 2014

# more /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="Etc/GMT+4"
UTC=true
ARC=false

# more /etc/issue
Oracle Linux Server release 5.6
Kernel \r on an \m

How can I set my crontab timezone to server timezone?

you want to run the cron job at a specific time which is the same as your server timezone?

or you need a script function to convert the timezone?

I want ro run all my crontab jobs automatically in my timezone, which is server timezone "Etc/GMT+4".

I wonder if the time/date is set up correctly on your box.

- Is you hardware clock ("BIOS" time) set to UTC or localtime (MSK / GMT+4)?
If it is set to MSK/GMT+4 than your system clock does not use UTC.

From the info you posted it seems like you have a hardware clock that is set to MSK/GMT+4, but you also told the system that the system clock is set to UTC, which is not correct.

If that is true: Re-run the system-config-date command and select the timezone you are in (Etc/GMT+4 or Europe/Moscow) and make sure that the [ ] System clock uses UTC is not selected (no *)

check out this link: Sync hardware clock with current system date and time (http://www.linuxweblog.com/node/199)

from above link:
Then sync your hardware clock with the system time.

1 members found this post helpful.

In system-config-date everything is OK.
Command #hwclock --systohc helped me to normalise hwclock time, but crontab works with 8 hours delay.
Problem is something other place.

Just to make sure: Time and date are shown/used correctly, except when using crontab?

Time and date are shown correctly. I'm not shure abous "used". So crontab time is wrong.

That is strange. The manual page (man anacron) mentions in the NOTES section that the time-zone needs to be set correctly in order for cron to work correctly.

You mention this in your previous reply:That doesn't tell us if the BIOS clock is set to UTC or your local time (which seems to be MSK).

- What does your BIOS time show: UTC or localtime?
- Which entries are set in the system-config-date tool?

If this machine only runs Linux than the BIOS time should be set to UTC. If this is a dual boot system (Windows/Linux) the BIOS time should be set to localtime. This, the UTC vs localtime setting, should be reflected in the System clock uses UTC entry.

I do believe you need to reboot your machine if you change the time-zone settings, logging out and in again won't reflect the changes made.

One other thing that comes to mind and which might influence time and date: Is the TZ variable set (echo $TZ)

In system-config-date:
GMT+4
(MSK is GMT+4)
marked "System clock uses UTC"

My mashine is Linux only.

I have no $TZ

It's the production mushine, so I can't reboot it when I want to do it.

You still haven't answered this: What does your BIOS time show?

All the other things discussed are pointless if you do not answer that one! Everything that is time/date related is based on the BIOS time setting.

I have:

# clock
Wed 22 Jan 2014 04:48:43 PM MSK -0.196592 seconds
# hwclock
Wed 22 Jan 2014 04:48:45 PM MSK -0.321253 seconds
# date
Wed Jan 22 16:48:46 MSK 2014

and
device bay iLO Date/Time Wed Jan 22 16:47:45 2014
time on basket is 16:50

everything seems to be right.

If the cron job actually ran at 1700 vs 0900 then the difference is +6 hours which does not match with a UTC vs local time problem. Was this a typo? In your first post the hardware clock vs system clock were +4 difference which matches your configuration and the hardware (BIOS clock) is set to UTC. However in your last post the hardware clock and date command match.

Does /etc/localtime file exist?
Does the output of the command
zdump -v /etc/localtime | grep 2014

Show info for the MSK timezone?

If you have altered your systems timezone information (and it sounds like you did) you have to restart crond so that it will pick up the new values.

1 members found this post helpful.

09:00 -> 17:00 is an 8 hour difference, not 6... Or am I overlooking something?