Solaris container date diference

UNIX Solaris
1

Hi people,

I dont have a real problem, its also a so strange issue.

When i connect to my system from a ssh session or telnet normaly from putty and execute the command "date" its show me the correctly time in BRT format for root and all other users.

But when i connect from the global machine from zlogin or zlogin -C and execute the command "date" its show me the time on GMT format, like a date -u with a 3 hours difference from Brazil time for root and all other users on the system.

I think its not a problem because all external users connect from ssh, but i have other time/date issue on this machine and the only different thing i found is this.

Can anyone help me know why its happens?

Thanks very mutch all.

Observation: Its only happens on this container, in all others the date is OK from ssh and from console.

The commands out:

The console command out from the global machine (wrong):

root@n1grid20 # for a in `zoneadm list | tail -9`; do zlogin $a date; done
Wed Apr 13 18:43:37 BRT 2011
Wed Apr 13 18:43:37 BRT 2011
Wed Apr 13 18:43:37 BRT 2011
Wed Apr 13 18:43:37 BRT 2011
Wed Apr 13 18:43:37 BRT 2011
Wed Apr 13 18:43:37 BRT 2011
Wed Apr 13 18:43:37 BRT 2011
Wed Apr 13 21:43:37 GMT 2011
Wed Apr 13 18:43:37 BRT 2011
root@n1grid20 #

The command from a normal ssh (correctly):

-bash-3.00# date
Wednesday, April 13, 2011 06:43:53 PM BRT
-bash-3.00#

Im running a Solaris 10 10/09 on a M8K machine.

2

Timezone is setup a different way than for other zones ?

3

A missing or wrong timezone setting is more than likely but it can't be NTP. There is a single clock shared by all zones so all zones are synchronized by design. NTP is configured in one zone only, usually the global one as non global zones haven't the privilege to set the clock (by default).

4

The NTP configuration is the same on all the zones and others servers too:

-bash-3.00# ntpq -p
remote refid st t when poll reach delay offset disp

*10.8.1.30 .GPS. 1 u 830 1024 377 2.50 0.359 0.21
+sbcpd04 10.8.1.30 2 u 191 1024 377 4.94 1.558 1.31
-bash-3.00#

10.8.1.30 is a Atomic time machine, samething like that and sbcpd04 is a secundary server.

My /etc/TIMEZONE

#
# Copyright 1992, 1999-2002 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
#
#ident "@(#)init.dfl 1.7 02/12/03 SMI"
#
# This file is /etc/default/init. /etc/TIMEZONE is a symlink to this file.
# This file looks like a shell script, but it is not. To maintain
# compatibility with old versions of /etc/TIMEZONE, some shell constructs
# (i.e., export commands) are allowed in this file, but are ignored.
#
# Lines of this file should be of the form VAR=value, where VAR is one of
# TZ, LANG, CMASK, or any of the LC_* environment variables. value may
# be enclosed in double quotes (") or single quotes (').
#
#####TZ=Brazil/East
#####CMASK=022
#####LC_COLLATE=en_US.ISO8859-1
#####LC_CTYPE=en_US.ISO8859-1
#####LC_MESSAGES=C
#####LC_MONETARY=en_US.ISO8859-1
#####LC_NUMERIC=en_US.ISO8859-1
#####LC_TIME=en_US.ISO8859-1
TZ=Brazil/East
CMASK=022
LC_COLLATE=en_US.ISO8859-1
LC_CTYPE=en_US.ISO8859-1
LC_MESSAGES=C
LC_MONETARY=en_US.ISO8859-1
LC_NUMERIC=en_US.ISO8859-1
LC_TIME=en_US.ISO8859-1

this is weird because when we connect via ssh its returns the date command a normal BRT time if i start the sap for example via ssh everything is normal, if we connect via the global machine console, start the sap he gets time wrong.

The file /etc/TIMEZONE is the same for all the zones.

Thanks for the answers.