On 07/06/2012 10:06 PM, Musayev, Ilya wrote:
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.
Thank you very much!
I've set param timezone = 'Europe/Moscow' (it was undefined by default)
in postgresql.conf, restarted SW and postgres and voila - actions added
to schedule in correct time.
Problem solved!
--
Yura Demchenko
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
