Not all non-global zones updated for DST
We have one server with Solaris 10 and four non-global zones. I installed patch 122032-03 to the global zone and it installed successfull, according to the log. With the DST change on 3/11, TWO of the non-global zones and the global zone updated correctly to daylight time, but the other TWO non-global zone DID NOT.Does anyone know what would cause this?
I have also tried to manually change the time on the two non-global zones and have not been able to; as root I get the message "not owner"
ainsworth:hughesm> su -
Password:
Sun Microsystems Inc.SunOS 5.10Generic January 2005
You have mail.
# date
Tue Mar 13 12:02:45 PST 2007
# date -u
Tue Mar 13 20:03:16 GMT 2007
# date
Tue Mar 13 12:04:31 PST 2007
# date 0313130007
date: Not owner
usage: date [-u] mmddHHMM[[cc]yy][.SS]
date [-u] [+format]
date -a [-]sss[.fff]
#
Fortunately, these were just test zones. They were set up by a previous admin to be used for pgpftp, so I'm wondering if there are some special configurations for security that is preventing the time change.
[1150 byte] By [
hughesm1a] at [2007-11-26 21:29:38]
# 1
> We have one server with Solaris 10 and four
> non-global zones. I installed patch 122032-03 to the
> global zone and it installed successfull, according
> to the log. With the DST change on 3/11, TWO of the
> non-global zones and the global zone updated
> correctly to daylight time, but the other TWO
> non-global zone DID NOT.Does anyone know what
> would cause this?
Was the machine rebooted?
Sparse or full-root zones? I'm assuming full-root.
What are the timezone settings on each of the zones (global and non-global)? That zone is found in /usr/share/lib/zoneinfo. Is the file representing the timezone on each of the zones identical (/usr/share/lib/zoneinfo/US/Pacific as an example)? I can't see how it wouldn't be if you're running a sparse zone.
> I have also tried to manually change the time on the
> two non-global zones and have not been able to; as
> root I get the message "not owner"
The "clock" is not what is wrong. Changing the date is not an appropriate remedy.
> ainsworth:hughesm> su -
> Password:
> Sun Microsystems Inc.SunOS 5.10Generic
> January 2005
> You have mail.
> # date
> Tue Mar 13 12:02:45 PST 2007
> # date -u
> Tue Mar 13 20:03:16 GMT 2007
> # date
> Tue Mar 13 12:04:31 PST 2007
> # date 0313130007
Ignore 'date'. What does 'zdump -v US/Pacific | grep 2007' return on each zone? If it shows dates in April instead of March, then the zoneinfo library was not properly installed on that zone.As to why, you'd have to go back to the logs for the patch and see what it says about the installation in that zone.
If this is a full-root zone, you can either re-apply the patch to that zone, or you can simply copy /usr/share/lib/zoneinfo from a patched machine to a non-patched one.
> Fortunately, these were just test zones. They were
> set up by a previous admin to be used for pgpftp, so
> I'm wondering if there are some special
> configurations for security that is preventing the
> time change.
No. The time didn't "change". The OS uses the timezone descriptions to translate from UTC time ('date -u') to local time. The translation understands DST.
--
Darren
# 2
Thanks for replying.
I rebooted from the global zone. All the zones have the same uptime as the global zone, except one that was rebooted more recently.
Quick question - how do I tell if it's a sparse zone or full zone?
One of the zones that the time change worked on:
$ zdump -v US/Pacific | grep 2007
US/Pacific Tue Mar 13 22:37:59 2007 UTC = Tue Mar 13 15:37:59 2007 PDT isdst=1
US/Pacific Sun Mar 11 09:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 PST isdst=0
US/Pacific Sun Mar 11 10:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 PDT isdst=1
US/Pacific Sun Nov 4 08:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 PDT isdst=1
US/Pacific Sun Nov 4 09:00:00 2007 UTC = Sun Nov 4 01:00:00 2007 PST isdst=0
tsbackup:hughesm> cd /usr/share/lib/zoneinfo; ls -al | grep Pac
drwxr-xr-x2 rootbin 1024 Jan 19 11:19 Pacific
cathedral:hughesm> cd /usr/share/lib/zoneinfo; ls -al | grep Pac(the global zone)
drwxr-xr-x2 rootbin 1024 Jan 19 11:19 Pacific
One zone that didn't work: (the other one that did not work is the same)
# zdump -v US/Pacific | grep 2007
US/Pacific Tue Mar 13 22:45:33 2007 UTC = Tue Mar 13 14:45:33 2007 PST isdst=0
US/Pacific Sun Apr 1 09:59:59 2007 UTC = Sun Apr 1 01:59:59 2007 PST isdst=0
US/Pacific Sun Apr 1 10:00:00 2007 UTC = Sun Apr 1 03:00:00 2007 PDT isdst=1
US/Pacific Sun Oct 28 08:59:59 2007 UTC = Sun Oct 28 01:59:59 2007 PDT isdst=1
US/Pacific Sun Oct 28 09:00:00 2007 UTC = Sun Oct 28 01:00:00 2007 PST isdst=0
# uname -a
SunOS albina 5.10 Generic_118822-02 sun4u sparc SUNW,Ultra-4
# cd /usr/share/lib/zoneinfo(non-global zone that did not update)
# ls -al | grep Pac
drwxr-xr-x2 rootbin 1024 Apr 20 2005 Pacific
I was thinking of trying to apply the patch within the zone itself, but when I tried smpatch analyze, it didn't list it:
# smpatch analyze
120900-04 SunOS 5.10: libzonecfg Patch
121133-02 SunOS 5.10: zones library and zones utility patch
119254-27 SunOS 5.10: Install and Patch Utilities Patch
119574-02 SunOS 5.10: su patch
121453-02 SunOS 5.10: Sun Update Connection Client Foundation
121118-08 SunOS 5.10: Sun Update Connection System Client 1.0.8
121081-05 SunOS 5.10: Connected Customer Agents 1.1.0
122231-01 SunOS 5.10 Sun Connection agents, transport certificate update
I attempted to add the patch using smpatch, but I've never run it here before so it's probably not configured right:
# smpatch update -i 122032-03
122032-03 cannot be validated.
com.sun.patchpro.model.PatchProRuntimeException: Unexpected throwable
at com.sun.patchpro.cli.PatchServices.waitForThread(PatchServices.java:1284)
at com.sun.patchpro.cli.PatchServices.installPatches(PatchServices.java:1121)
at com.sun.patchpro.cli.PatchServices.main(PatchServices.java:510)
Caused by:
java.lang.Throwable: ERROR: Failed to validate the digital signature(s).
at com.sun.patchpro.model.PatchProModel$InnerDownloadPatchThread.downloadPatchFail ed(PatchProModel.java:2855)
at com.sun.patchpro.server.GroupPatchDownloader.dispatchFailedEvent(GroupPatchDown loader.java:384)
at com.sun.patchpro.server.GroupPatchDownloader.downloadPatchFailed(GroupPatchDown loader.java:335)
at com.sun.patchpro.server.ServerPatchServiceProvider.dispatchFailedEvent(ServerPa tchServiceProvider.java:2577
at com.sun.patchpro.server.ServerPatchServiceProvider.validatePatchBundle(ServerPa tchServiceProvider.java:2196
at com.sun.patchpro.server.ServerPatchServiceProvider.requestDownload(ServerPatchS erviceProvider.java:1780)
at com.sun.patchpro.server.ServerPatchServiceProvider.performDownloadPatches(Serve rPatchServiceProvider.java:1
2)
at com.sun.patchpro.server.ServerPatchServiceProvider.downloadPatches(ServerPatchS erviceProvider.java:860)
at com.sun.patchpro.server.PatchServerProxy.downloadPatches(PatchServerProxy.java: 142)
at com.sun.patchpro.server.GroupPatchDownloader.downloadPatches(GroupPatchDownload er.java:124)
at com.sun.patchpro.model.PatchProModel.performPatchDownload(PatchProModel.java:19 32)
at com.sun.patchpro.model.PatchProStateMachine$10.run(PatchProStateMachine.java:52 6)
at com.sun.patchpro.util.State.run(State.java:266)
at java.lang.Thread.run(Thread.java:595)
#
So then I attempted to add the patch using patchadd:
# patchadd 122032-03
Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Done!
Checking patches that you specified for installation.
Done!
Global patches.
0 Patch 122032-03 is for global zone only - cannot be installed on local zone.
No patches to install.
#
?
under /var/sadm/patch/122032-03 on the Global zone, the log shows:
-rw-r--r--1 rootroot2666 Jan 19 11:19 log
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
WARNING: /usr/share/lib/zoneinfo/Africa/Timbuktu <no longer a regular file>
WARNING: /usr/share/lib/zoneinfo/America/Argentina/ComodRivadavia <no longer a regular file>
WARNING: /usr/share/lib/zoneinfo/America/Indiana/Indianapolis <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/America/Indianapolis <no longer a regular file>
WARNING: /usr/share/lib/zoneinfo/America/Kentucky/Louisville <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/America/Louisville <no longer a regular file>
WARNING: /usr/share/lib/zoneinfo/CST6CDT <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/EST <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/EST5EDT <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/Europe/Belfast <no longer a regular file>
WARNING: /usr/share/lib/zoneinfo/HST <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/MST <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/MST7MDT <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/PST8PDT <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/Pacific/Yap <no longer a regular file>
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
WARNING: /usr/share/lib/zoneinfo/Africa/Timbuktu <no longer a regular file>
WARNING: /usr/share/lib/zoneinfo/America/Argentina/ComodRivadavia <no longer a regular file>
WARNING: /usr/share/lib/zoneinfo/America/Indiana/Indianapolis <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/America/Indianapolis <no longer a regular file>
WARNING: /usr/share/lib/zoneinfo/America/Kentucky/Louisville <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/America/Louisville <no longer a regular file>
WARNING: /usr/share/lib/zoneinfo/CST6CDT <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/EST <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/EST5EDT <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/Europe/Belfast <no longer a regular file>
WARNING: /usr/share/lib/zoneinfo/HST <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/MST <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/MST7MDT <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/PST8PDT <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/Pacific/Yap <no longer a regular file>
Installation of <SUNWcsu> was successful.
On the non-global zones, either there is nothing under /var/sadm/patch or there isn't even a patch directory under /var/sadm. Is there somewhere else to look?
Thanks.
# 3
Should've added this - the directory US is different:
Global zone and ones that updated:
# cd /usr/share/lib/zoneinfo/US
# ls -al
total 36
drwxr-xr-x2 rootbin 512 Jan 19 11:19 .
drwxr-xr-x 21 rootbin 1536 Jan 19 11:19 ..
-rw-r--r--2 rootbin 861 Dec 27 23:27 Alaska
-rw-r--r--3 rootbin 858 Dec 27 23:27 Aleutian
-rw-r--r--2 rootbin 130 Jan 21 2005 Arizona
-rw-r--r--2 rootbin 1279 Dec 27 23:27 Central
-rw-r--r--4 rootbin 606 Dec 27 23:27 East-Indiana
-rw-r--r--2 rootbin 1267 Dec 27 23:27 Eastern
-rw-r--r--2 rootbin 130 Jan 21 2005 Hawaii
-rw-r--r--3 rootbin 869 Dec 27 23:27 Indiana-Starke
-rw-r--r--2 rootbin 811 Dec 27 23:27 Michigan
-rw-r--r--4 rootbin 877 Dec 27 23:27 Mountain
-rw-r--r--3 rootbin 1017 Dec 27 23:27 Pacific
-rw-r--r--3 rootbin 1017 Dec 27 23:27 Pacific-New
-rw-r--r--3 rootbin 125 Jan 21 2005 Samoa
#
Non-global zones that did not update:
# cd /usr/share/lib/zoneinfo/US
# ls -al
total 34
drwxr-xr-x2 rootbin 512 Apr 20 2005 .
drwxr-xr-x 21 rootbin 1024 Apr 20 2005 ..
-rw-r--r--2 rootbin 856 Jan 21 2005 Alaska
-rw-r--r--3 rootbin 858 Jan 21 2005 Aleutian
-rw-r--r--3 rootbin 130 Jan 21 2005 Arizona
-rw-r--r--3 rootbin 1279 Jan 21 2005 Central
-rw-r--r--5 rootbin 286 Jan 21 2005 East-Indiana
-rw-r--r--3 rootbin 1267 Jan 21 2005 Eastern
-rw-r--r--3 rootbin 130 Jan 21 2005 Hawaii
-rw-r--r--3 rootbin 549 Jan 21 2005 Indiana-Starke
-rw-r--r--2 rootbin 811 Jan 21 2005 Michigan
-rw-r--r--5 rootbin 877 Jan 21 2005 Mountain
-rw-r--r--4 rootbin 1017 Jan 21 2005 Pacific
-rw-r--r--4 rootbin 1017 Jan 21 2005 Pacific-New
-rw-r--r--3 rootbin 125 Jan 21 2005 Samoa
