GoDaddy is Experiencing Technical Difficulties
We were notified by one of our readers that his web sites were not resolving correctly. It appears that Go Daddy is experiencing some difficulties and have posted a notice to that effect on their support website. If you have problems with accessing websites today it could be that they are hosted on GoDaddy. GoDaddy is not giving any information as to the cause of the problems or a ETA for the problem resolution.
https://www.godaddy.com/gdshop/support.asp
Thanks to Neal for notifying us.
Update : Following news article will explain more information about GoDaddy's DST issue.
http://www.pcworld.com/article/id,129718/article.html
Update : Following the GoDaddy, they had DDoS attack and the outage is not related with DST issue.
https://www.godaddy.com/gdshop/support.asp
Thanks to Neal for notifying us.
Update : Following news article will explain more information about GoDaddy's DST issue.
http://www.pcworld.com/article/id,129718/article.html
Update : Following the GoDaddy, they had DDoS attack and the outage is not related with DST issue.
Keywords:
0 comment(s)
Yahoo mail problems
We've received e-mail from several readers (and seen ourselves) that Yahoo mail seems to be experiencing some problems. At this point, we don't know whether or not it is related to the DST changes, but today expect just about everything to be blamed on it. We'll update the story if we get any real details.
Update: Some of our readers (and the author of this story) are now able to reach their Yahoo mail. Still not sure what the problem was, but it has been unavailable pretty much all day.
Update: Some of our readers (and the author of this story) are now able to reach their Yahoo mail. Still not sure what the problem was, but it has been unavailable pretty much all day.
Keywords:
0 comment(s)
Sun Alert Notification Dated March 10th, 2007
Some of you may have missed the following Alert Bulletin posted by Sun Microsystems yesterday. It deals with the change in DST and "Olson time zone data tzdata2005r or greater incompatibility". According to the information available from Sun regarding this alert sunsolve.sun.com/search/document.do there is a problem with Eastern, Hawaii and Mountain Time Zones and Sun Java 2 software.
It appears that there are 2 issues that affect the ability for the software to calculate correctly. Both of the issues are covered by bug reports from Sun.
Sun bug 6466476
This issue is an incompatibility in the definition of time zone objects identified by the time zone IDs "EST", "MST" or "HST". Prior to Olson data 2005r these 3 IDs refer to zones which observe daylight savings time. For Olson data 2005r or later these 3 IDs refer to zones which do not observe daylight savings time.
bugs.sun.com/bugdatabase/view_bug.do
Sun bug 6530336
It effects the parsing of date strings containing the strings "EDT", "HDT" or "MDT", for example "July 4th 2007, 1:00 pm EDT".
bugs.sun.com/bugdatabase/view_bug.do
Thanks to Colm for providing the information.
It appears that there are 2 issues that affect the ability for the software to calculate correctly. Both of the issues are covered by bug reports from Sun.
Sun bug 6466476
This issue is an incompatibility in the definition of time zone objects identified by the time zone IDs "EST", "MST" or "HST". Prior to Olson data 2005r these 3 IDs refer to zones which observe daylight savings time. For Olson data 2005r or later these 3 IDs refer to zones which do not observe daylight savings time.
bugs.sun.com/bugdatabase/view_bug.do
Sun bug 6530336
It effects the parsing of date strings containing the strings "EDT", "HDT" or "MDT", for example "July 4th 2007, 1:00 pm EDT".
bugs.sun.com/bugdatabase/view_bug.do
Thanks to Colm for providing the information.
Keywords:
0 comment(s)
A DST Reminder
I almost forgot, with the change in Daylight Saving Time comes a change in batteries for the smoke detectors. Hopefully the Energizer Bunny has done a good job of manufacturing the batteries because they will have to last 3 weeks longer.
Thanks to my fellow handler Scott for reminding me.
Thanks to my fellow handler Scott for reminding me.
Keywords:
0 comment(s)
Daylight Saving Time Change Problem With Watchguard Fireware 8.3.1 and Watchguard System Manager 8.3.1
Again, another report from Alan. He has had problems with Watchguard products. Here is what he had to say:
Watchguard Fireware 8.3.1 and Watchguard System Manager 8.3.1 is reporting incorrect times and symptoms.
Symptoms:
1) Log rolls and scheduled reports advanced one hour with DST change
2) Changing the time of the scheduled log rolls and reports to the desired time results in service shutdowns - service restarts fail with an automatic stoppage of their service - the server itself must be restarted to correct the issue.
3) Webblocker updates report having occurred one hour after the Windows scheduler task reports having launched and and completed the task.
Thanks Alan for the information.
Watchguard Fireware 8.3.1 and Watchguard System Manager 8.3.1 is reporting incorrect times and symptoms.
Symptoms:
1) Log rolls and scheduled reports advanced one hour with DST change
2) Changing the time of the scheduled log rolls and reports to the desired time results in service shutdowns - service restarts fail with an automatic stoppage of their service - the server itself must be restarted to correct the issue.
3) Webblocker updates report having occurred one hour after the Windows scheduler task reports having launched and and completed the task.
Thanks Alan for the information.
Keywords:
0 comment(s)
Daylight Saving Time Change Issues Continue To Roll In
I can't believe that I volunteered for this shift. The emails continue to roll in regarding things that are working quite right this morning. Nothing earth shattering or causing the Internet to crash and burn, however it is making things a little tense for some folks.
We have now received reports of Cell Phones that are not updating. I am happy to say Long Lines Wireless did. (That is my provider as well as my employer).
We have had reports that the Atomic Clocks that we have in our homes is not updating. I can confirm that as well as mine has not updated.
We have had reports of various VOIP phone issues with no time change. Reports of Blackberry's and other electronic devices not updating. Reports of GPS updated devices not updating automatically.
We will keep you updated to new items that we receive.
We have now received reports of Cell Phones that are not updating. I am happy to say Long Lines Wireless did. (That is my provider as well as my employer).
We have had reports that the Atomic Clocks that we have in our homes is not updating. I can confirm that as well as mine has not updated.
We have had reports of various VOIP phone issues with no time change. Reports of Blackberry's and other electronic devices not updating. Reports of GPS updated devices not updating automatically.
We will keep you updated to new items that we receive.
Keywords:
0 comment(s)
Daylight Saving Time Change Problem With Symantec Backup Exec 10d and 10.1
It appears that there is also a problem with Symantec Backup Exec 10d and 10.1. Alan, our reader that discovered the APC problem also discovered a problem with his backup software. Again the software was patched and updated as recommended by Symantec.
Here is what Alan had to say:
Backup jobs previously scheduled for 11:00 PM are now scheduled for 10:00 PM despite 10d and 10.1 reportedly DST compliant http://support.veritas.com/docs/286926. Nor will it allow you to change the time back to the correct time of 11:00 PM. It reports that it will, allows the change, and reports the new time in the summary when the job is resubmitted. But the scheduled time immediately reverts back to 10:00 PM. Restarting the Backup services does not appear to correct this either, so we're now an hour off on all backups and banging our heads on our desks repeating expletives directed at certain vendors.
It looks like Alan is going to have a busy Sunday and maybe even Monday. Good Luck Alan and if you have time keep us updated to your progress on resolving the problems.
Update:
Alan contacted us again with new findings on the Symantec Backup Exec scheduling problem. He indicated that his older.. unpatched backups are fine.
Here is what he had to say:
Ok, so now I'm highly annoyed. It turns out that our servers that have not been updated with more recent APC Powerchute (still running 5.2) and Veritas Backup Exec (8.6 instead of 10(d) or 10.1))handled the DST change correctly whereas the newer versions didn't.
I'm beginning to wonder if the move towards java based tools is the underlying issue with the newer "compliant" applications not working as expected.
Here is what Alan had to say:
Backup jobs previously scheduled for 11:00 PM are now scheduled for 10:00 PM despite 10d and 10.1 reportedly DST compliant http://support.veritas.com/docs/286926. Nor will it allow you to change the time back to the correct time of 11:00 PM. It reports that it will, allows the change, and reports the new time in the summary when the job is resubmitted. But the scheduled time immediately reverts back to 10:00 PM. Restarting the Backup services does not appear to correct this either, so we're now an hour off on all backups and banging our heads on our desks repeating expletives directed at certain vendors.
It looks like Alan is going to have a busy Sunday and maybe even Monday. Good Luck Alan and if you have time keep us updated to your progress on resolving the problems.
Update:
Alan contacted us again with new findings on the Symantec Backup Exec scheduling problem. He indicated that his older.. unpatched backups are fine.
Here is what he had to say:
Ok, so now I'm highly annoyed. It turns out that our servers that have not been updated with more recent APC Powerchute (still running 5.2) and Veritas Backup Exec (8.6 instead of 10(d) or 10.1))handled the DST change correctly whereas the newer versions didn't.
I'm beginning to wonder if the move towards java based tools is the underlying issue with the newer "compliant" applications not working as expected.
Keywords:
0 comment(s)
Daylight Saving Time Change Problem With CISCO Phones
We have received reports from 2 separate people indicating the time did not change correctly on CISCO phone Models 7940, 7960, 7961 and others. The readers that notified us indicating that the phones had been updated per recommendations of the vendors. One of our readers indicated the CISCO TAC is unreachable due to volume so my guess is that Shawn and Peter aren't the only ones that have noticed the problem.
Shawn indicated that it appears to be a Java update problem.
Thanks to Shawn and Peter for providing us with the information.
Shawn indicated that it appears to be a Java update problem.
Thanks to Shawn and Peter for providing us with the information.
Keywords:
0 comment(s)
Daylight Saving Time Change Problem With APC
We received an email this morning from one of our readers saying that his server that was scheduled for reboot at 3:00am did not reboot. Upon investigation he discovered that the his updated and patched APC Power Management Software was the problem.
Here is what Alan had to say:
I have a box running APC Powerchute 7.0.5.108 on Windows Server 2003 SP1 that was scheduled to shutdown and restart one of my systems at 3:00 AM today but didn't do the shutdown until 4:00 AM.
According to my staff, APC had reported that earlier editions of Powerchute had a DST issue, but 7.0.5 was corrected, yet this doesn't appear to be correct. The W2K3 server did update the time correctly to the new DST at 2:00 AM this morning and is reflecting the correct Eastern DST.
Further investigation shows that what actually occurred is that the DST change altered my schedule from 3:00 AM to 4:00 AM on a permanent basis. So I was attempting to verify on the APC website that the version was actually the corrected version and that this was not an error on the part of my staff.
Since then, I have checked other W2K3 boxes with this Powerchute version and found that the change actually advanced my scheduled shutdown time by one hour rather than actually correcting DST.
So it looks like a problem exists with Powerchute.
Alan indicated that he is not able to get any information from the APC web site because they have chosen today to take the site down for maintenance.
So those of you that are running Powerchute software may want to check you systems.
Here is what Alan had to say:
I have a box running APC Powerchute 7.0.5.108 on Windows Server 2003 SP1 that was scheduled to shutdown and restart one of my systems at 3:00 AM today but didn't do the shutdown until 4:00 AM.
According to my staff, APC had reported that earlier editions of Powerchute had a DST issue, but 7.0.5 was corrected, yet this doesn't appear to be correct. The W2K3 server did update the time correctly to the new DST at 2:00 AM this morning and is reflecting the correct Eastern DST.
Further investigation shows that what actually occurred is that the DST change altered my schedule from 3:00 AM to 4:00 AM on a permanent basis. So I was attempting to verify on the APC website that the version was actually the corrected version and that this was not an error on the part of my staff.
Since then, I have checked other W2K3 boxes with this Powerchute version and found that the change actually advanced my scheduled shutdown time by one hour rather than actually correcting DST.
So it looks like a problem exists with Powerchute.
Alan indicated that he is not able to get any information from the APC web site because they have chosen today to take the site down for maintenance.
So those of you that are running Powerchute software may want to check you systems.
Keywords:
0 comment(s)
Reports of Daylight Saving Time Change Problems
Well it has started already. The reports are coming in from our readers of issues that they have identified. I will update the diary today to let you know what our readers are experiencing. Please do let us know of any issues that you have. Make sure that you indicate whether or not we can use the information in the diary.
Keywords:
0 comment(s)
×
![modal content]()
Diary Archives
© 2024 SANS™ Internet Storm Center
Developers: We have an API for you! 
Comments