Nope. It sure hasn't. Nice of them to think about us, don't you think?
Nice attitude [;)]
I contacted support a while back about this. The following is me paraphrasing what they told me: They aren't releasing an update for V5 that would address the DST change. They were, at the time, working on the V6 update. V7's already compliant.
We're still on V5. So I think it's either change it by hand, or try something like this:
Greg, if you KNOW you aren't entitled to support, then why be upset with their reply? They answered your question, and gracefully, I thought, mentioned what your options are if you wanted to obtain support. If you are responsible for a major firewall implementation, why wouldn't you put a support case in with that license instead? If you're evaluating Astaro wouldn't you have an evaluation license to use instead?
I don't understand what the big deal is with this anyway. If it's so important that the logs might be out by an hour, There is a simple patch that will work on all versions of Astaro, as well as your wristwatch, microwave, and car. Just login & change the time. I don't mean any disrespect, this is meant to be a light-hearted reply.. I just don't get the big hype over this issue. People keep ocmparing it to y2k, but how many problems did that actually cause?
Where is it? No announcements yet. IMO, this update is at least 2 weeks late. No one in their right mind will update a production system on a Thursday or Friday before a weekend.
Where is it? No announcements yet. IMO, this update is at least 2 weeks late. No one in their right mind will update a production system on a Thursday or Friday before a weekend.
I did the upgrade to 6.304 on both my office and home Astaro boxes. The only problem I experienced was that today's network stats disappeared, leaving today's networking strip charts with no data. But that is a relatively minor issue.
Having left my right mind behind many years ago, I'm free to update my Astaro boxes whenever I want. [:D]
LOL. Luckily they appear to have minimized the number of changes for this release. We have pushed it out to non-critical sites with only one issue so far. clamav seems to be dying/restarting every hour and it's generating email alerts.
6.304 doesn't even install on 2 of our 6.303 systems... it just says "done" and doesn't install anything. Methinks there are some corrupt packages on the up2date server. And the clamd issues concern me.
Does it say anything in the Up2date log on the machines that failed? or perhaps the middleware log, since up2date says it needs to restart the middleware? Also, the clamav issue can be fixed with a reboot. See up2date.astaro.com:
"Note (March 9th): Due to symbolic link problem within the new Clam AV scan engine the Up2Date was reloaded. There is no change of the content or functionality, just a corrected link. If you already installed 6.304 and experience problems, please reboot the ASG - this will fix the problem. We apologize for the inconvenience!"
Does it say anything in the Up2date log on the machines that failed? or perhaps the middleware log, since up2date says it needs to restart the middleware? Also, the clamav issue can be fixed with a reboot. See up2date.astaro.com:
"Note (March 9th): Due to symbolic link problem within the new Clam AV scan engine the Up2Date was reloaded. There is no change of the content or functionality, just a corrected link. If you already installed 6.304 and experience problems, please reboot the ASG - this will fix the problem. We apologize for the inconvenience!"
