Privet Yura, I've seen a similar issue with different product, but in my case the database had its own timezone and OS had its own timezone. The two were not in sync and hence, we had 4 hour delay between jobs. We had to force the DB to match the OS timezone and everything worked as expected.
I'm not postgres expert, but I would suggest to investigate this route as well. Regards ilya -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of ???????? ???? ????????????? Sent: Friday, July 06, 2012 3:26 AM To: [email protected] Subject: Re: [Spacewalk-list] wrong schedule times On 07/06/2012 11:14 AM, Paul Robert Marino wrote: > Well that would seem to be a client bug. > The as soon as possible is executed the next time the client checks in. I have rhn_check in cron every 10 minutes and working OSA on clients - so that's not an issue with checking in > I am curious thoug I know this shouldn't make a diference but is the > time correct on both servers and are they in the same timezone? Yes, both sw server and clients are in same timezone, with correct time and NTP service. Latest timezone packages. > On Jul 6, 2012 2:50 AM, "Yura Demchenko" <[email protected] > <mailto:[email protected]>> wrote: > > SW server and clients have same system TZ ("europe/moscow"), same in > "locale preferences". Latest timezone packages available applied to > server and clients. _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
