I am getting an error when I startup my frontend (standalone) that the timezone is set different than the backend. As soon as I okay out of that, it closes the frontend and I am able to start the frontend with alt-m and everything works fine. As far as I can tell, the timezone is set the same as my backend... Any suggestions on how to troubleshoot this?

_________________
LinHES 8.3, 1 BE, 3 FE

And now it's stopped. Not sure if this issue will crop up again. Weird. I'm almost thinking that my new frontend is maybe just starting up too fast. The other issue I'm having is that one of my NFS shares doesn't mount on a reboot, it will only mount on a boot.

_________________
LinHES 8.3, 1 BE, 3 FE

So, this issue is persisting. If anyone has any suggestions I'd appreciate them, this is definitely impacting the WAF...

Every search I've done about this error isn't coming up with anything wrong. If I do a date command from the CLI on both my frontend and backend, both say that they are MST. If I pull up the settings for both machines in mythweb, both machine's HostTimeZone is set to US/Arizona and both HostTimeZoneRegion_US is set to Arizona.

_________________
LinHES 8.3, 1 BE, 3 FE

Not sure if this will fix the problem, but while reading through linhes forums I came across suggestions that implied that /etc/localtime should be a symlink to /usr/share/zoneinfo. My MythTV installations were not setup this way, so I setup a symlink to /usr/share/zoneinfo/US/Arizona on both boxes. Hopefully this makes the issue go away.

_________________
LinHES 8.3, 1 BE, 3 FE

Is daylight savings time turned off Arizona doesn't follow DST

_________________
My System

Check to see if there's a difference with your hardware clock and system clock. Pretty sure I needed to play around with synchronizing the 2 with hwclock or something similar. You might just need to set you BIOS time to 1 hour behind/forward.

More then likely it's a race issue and ntp resets the clock on you.
I think r7 had a minor bug where it didn't save the hwclock on shutdown.
try running "hwclock --adjust --utc" and see if the problem goes away

I had a similar problem on my system and the way I ended up having to fix it is to stop the NTP check on startup and put an NTP command in the X startup to get the clock to set right. Whilst not elegant it has worked for me.

_________________
Girkers