Apache looping? 2006-07-12 - By Ed Wilts
Back
On Wed, Jul 12, 2006 at 02:16:32PM -0500, Stanley, Jon wrote:
> How long was the box up? I know of some bugs in various software that
> occur at 248 days (haven't looked into the significance of that number -
> probably the time a short int rolls over or something like that).
248 days is 21,427,200 seconds. That's 1/100 of a signed 32-bit
integer.
Here's a Sun article on issues at 248 days:
http://sunsolve.sun.com/search/document.do?assetkey=1-26-57640-1
Googling also found this:
In version 8.0.X up to 8.1.6 of Oracle, there is a problem running it on
Solaris/UNIX. If your system clock ticks is set to milliseconds, the bug
affects systems with uptime of 24.8+ days, while centiseconds configured
(which is default and quite normal) will translate to 248 days. The bug
affects start/stop of Oracle if the uptime is higher than the above
mentioned. A better description of the bug would be a timer overflow,
which causes background processes to loop forever after this amount of
uptime.
This is reported by Oracle support, document ID 118228.1 (aswell as
Oracle bugID# 1084273).
The solution to the problem is either to reboot the system every 247:th
day (or every 24th depending on your clock settings) or patch it with
any of the available patches that solves this problem. If I remember
correctly, patch #1265297 would be the correct patch for 8.0.6 to solve
this problem.
.../Ed
--
Ed Wilts, RHCE
Mounds View, MN, USA
mailto:ewilts@(protected)
Member #1, Red Hat Community Ambassador Program
--
Taroon-list mailing list
Taroon-list@(protected)
https://www.redhat.com/mailman/listinfo/taroon-list
|
|
