| View previous topic :: View next topic |
| Author |
Message |
Exterus
-
Joined: 07 Aug 2003
Posts: 69
Location: Sweden
|
 Posted: Mon Oct 13, 2003 11:29 pm Post subject: uptime vs. crashes |
 |
|
My Abyss seems to freak out after 14 days+ uptime (I get a internal error message), is this because some sort of limitation in Abyss (since it's designed for personal use, I mean) or is it rather something with my machine that creates this situation?
After I restart Abyss it works fine again.
The machine is using a fully updated version of Windows NT 4.0 Server, PHP v. 4.3.0 and the latest version of Abyss.
_________________
"Technological progress is like an axe in the hands of a pathological criminal."
-- Albert Einstein |
|
| Back to top |
   |
 |
Karasu Kami
-
Joined: 22 Sep 2003
Posts: 712
Location: Colorado
|
|
| Back to top |
   |
|
Exterus
-
Joined: 07 Aug 2003
Posts: 69
Location: Sweden
|
| Posted: Tue Oct 14, 2003 2:10 am Post subject: |
|
|
Heh, it's a pure webserver running Windows NT4 Server. I've trimmed the processes to a bare minimum and I've installed every patch that microsoft has to offer. The OS is fairly old, true..but it was still designed to manage long uptimes. After 14-15 days the CPU usage and mem usage is not much different than when freshly rebooted.
Yes, it does perform a tad slower but every other process runs just fine.
I'm willing to accept that there's som compability-problem or such. But the machine and OS can manage those uptimes without a problem. So it's not that.
_________________
"Technological progress is like an axe in the hands of a pathological criminal."
-- Albert Einstein |
|
| Back to top |
|
|
chance
-
Joined: 04 Jan 2003
Posts: 27
Location: everett, wa
|
| Posted: Tue Oct 14, 2003 7:31 pm Post subject: |
|
|
Exterus
I run Abyss on an old 450mhz, with w2k pro, ftp and mail servers. The only time I reboot is the first of the month in order to cut the log files. Have never had to shut the machine down for any reason having to do with Abyss. |
|
| Back to top |
|
|
Exterus
-
Joined: 07 Aug 2003
Posts: 69
Location: Sweden
|
| Posted: Wed Oct 15, 2003 7:30 am Post subject: |
|
|
Okay. So it's my machine then. I'll look into it. :)
_________________
"Technological progress is like an axe in the hands of a pathological criminal."
-- Albert Einstein |
|
| Back to top |
|
|
CapFusion
-
Joined: 18 May 2003
Posts: 617
Location: Lost in Abyss' Dungeon
|
| Posted: Thu Oct 16, 2003 5:24 pm Post subject: |
|
|
| Exterus wrote: | Heh, it's a pure webserver running Windows NT4 Server. I've trimmed the processes to a bare minimum and I've installed every patch that microsoft has to offer. The OS is fairly old, true..but it was still designed to manage long uptimes. After 14-15 days the CPU usage and mem usage is not much different than when freshly rebooted.
Yes, it does perform a tad slower but every other process runs just fine.
I'm willing to accept that there's som compability-problem or such. But the machine and OS can manage those uptimes without a problem. So it's not that. |
Check your NT4 LOG, I had this problem long time ago before I dump NT4. Your NT4 log will shutdown when it reach to certain amount.
_________________
CapFusion,... |
|
| Back to top |
|
|
aprelium
-
Joined: 22 Mar 2002
Posts: 6800
|
| Posted: Fri Oct 17, 2003 4:08 pm Post subject: |
|
|
When you start to receive Internal Error even on HTML files, this means that the server is having problems to allocate virtual memory from the operating system. NT4 is known to have some issues with virtual memory usage. The problem is by design and Microsoft patches cannot fully solve it.
_________________
Support Team
Aprelium - http://www.aprelium.com |
|
| Back to top |
|
|
|
