Quote:
Originally Posted by chrishewitt  Hmmmm... I had the first "end of week" event overnight and things rolled over and I got the following email this morning. Any ideas on why the Java exception is thrown?
>>>>>>>>>>> START <<<<<<<<<<<<<
Full Backup started at: 01:30
Old backups found...old week= 18 current week= 19
......
java.net.UnknownHostException: zim.chrishewitt.net: zim.chrishewitt.net
at java.net.InetAddress.getLocalHost(InetAddress.java :1353)
at com.zimbra.common.localconfig.LC.<clinit>(LC.java: 350)
at com.zimbra.common.localconfig.KnownKey.<clinit>(Kn ownKey.java:32)
at com.zimbra.common.localconfig.LocalConfig.expandAl l(LocalConfig.java:327)
at com.zimbra.common.localconfig.LocalConfig.<init>(L ocalConfig.java:177)
at com.zimbra.common.localconfig.LocalConfig.readConf ig(LocalConfig.java:343)
at com.zimbra.common.localconfig.LocalConfig.<clinit> (LocalConfig.java:348)
at com.zimbra.common.localconfig.Main.main(Main.java: 108)
Setting date & version Marker into /opt/zimbra/DATE_VERSION.txt
java.net.UnknownHostException: zim.chrishewitt.net: zim.chrishewitt.net
at java.net.InetAddress.getLocalHost(InetAddress.java :1353)
at com.zimbra.common.localconfig.LC.<clinit>(LC.java: 350)
at com.zimbra.common.localconfig.KnownKey.<clinit>(Kn ownKey.java:32)
at com.zimbra.common.localconfig.LocalConfig.expandAl l(LocalConfig.java:327)
at com.zimbra.common.localconfig.LocalConfig.<init>(L ocalConfig.java:177)
at com.zimbra.common.localconfig.LocalConfig.readConf ig(LocalConfig.java:343)
at com.zimbra.common.localconfig.LocalConfig.<clinit> (LocalConfig.java:348)
at com.zimbra.common.localconfig.Main.main(Main.java: 108)
......
:::::::::::::::::::::::::::::::::::::::::::::::::: :::::::::::::::::::
Full Zimbra Backup ended at: 03:08
Backup took Hr:1 Min:98 Sec:31 to complete
:::::::::::::::::Cheers Osoffice for the script:::::::::::::::::::::::
>>>>>>>>>>>>> END <<<<<<<<<<<<
Note the strange elapsed time (as normal)..
Any ideas?
Christian |
Hi Christian!
I have no idea why the Java exception is thrown. But it seems to happen when one calls 'zmcontrol' commands.
Try running a "zmcontrol status" as the zimbra user. I bet you will get the same exceptions.
About the funny time issue, I will have a look at that soon. I see the time stats a as a nice extra but not of real importance...( thus not that high on the list to fix in the limited time I currently have, sorry)
heinzg