PDA

View Full Version : 12/01 - Web5

Ryan
12-01-2006, 07:23 PM
We're currently investigating an issue on Web5. We have no ETA at the moment, and will be updating this thread as soon as possible.

Thanks for your patience.

Ryan
Ryan
12-01-2006, 07:52 PM
The issue on web5 has been resolved. We're continually investigating this issue, and apologize for any inconvenience this may have caused.

If you still are experiencing issues, please feel free to open a support ticket by any of the desired means. Thanks.

Ryan
Ryan
12-01-2006, 09:43 PM
Unfortunately, web5 seems to be on the fritz again. We're working diligently to resolve this issue as soon as possible.

Thanks again for your patience.

Ryan
Ryan
12-01-2006, 09:50 PM
This issue has again been resolved. We apologize for any inconvenience this may have caused.

Additionally, measures have been put in place to ensure this does not happen again. Thanks for your patience in this matter.

As always, if you continue to experience any issues, feel free to get in contact with support.

Ryan
Jeff
12-02-2006, 03:23 PM
Hi folks,

As always, what follows is the after action details regarding the issues with web5 from last night:

We were testing a new backup product, and the software apparently didn't run so well on web5, as it caused it to crash. After the first crash, the servers' logs were examined, and the issue was determined to be associated with the kernel:


Dec 1 18:12:05 web5 kernel: Unable to handle kernel NULL pointer
dereference at virtual address 0000004c


Feeling doubtful that we had ran into a genuine kernel bug since web5 (nor any of our other servers) had ever had a similiar problem, we backtracked mentally to determine what, if any, changes had been made recently on the server. The only change that had been made was the addition of a new backup product we were testing, which just so happens to work at the kernel level.

After attempting to run the backup on web5 a second time, the server crashed again, and the same error was found in the logs. Since we have disabled the use of the backup product we were testing (and notified the developers of this issue), web5 has of course been up and running without issue, just as before.

In both cases, we were aware of the issues immediately and begun working to correct the issue as quickly as possible. The backup product continues to operate on several other servers completely without issue.