🚀 go-pugleaf

Kinda sounds like hardware.   Namely, sometype of 'thermal' problem.

good luck

-- 
From: Darwin Collins   Email: dcollins@fastlane.net
HomePage: http://www.fastlane.net/homepages/dcollins
NDS utilities and links to support and utility pages.

>> 
>> Help??

>	When you refer to locking.. What kind of locking??
>	R U talking about the keyboard locks at startup? what???
>	Novell begins to boot and then it locks up????

>	When and where is necessary to give you eval....

More info. Novell is running, the tape backup runs fine during the
night, then when users show up, it "locks up". That means that the
workstations stop receiving anything from the LAN, the keyboard
doesn't work, and if monitor is running with the screen saver, the
"snake" freezes. 

With no way to talk to it, I have to flip the big red reset switch.
Then if I leave it off for a minute or so, and bring it back up, it
will lock again soon. Even if I down it, exit to dos, and reboot. The
only consistent solution is to leave it powered off for five minutes
or so, then turn it back on.

Question that bothers me is, if it is a thermal problem, why doesn't
it fail during the backup itself, why wait until the next morning when
users are coming on line?

Thanks for any advise.

Darwin Collins wrote:
> 
> Kinda sounds like hardware.   Namely, sometype of 'thermal' problem.
> 
> good luck
> 
> --
> From: Darwin Collins   Email: dcollins@fastlane.net
> HomePage: http://www.fastlane.net/homepages/dcollins
> NDS utilities and links to support and utility pages.


I agree. During periods of high utilisation such as when a backup job is running, you'll find
the Hard Drive(s) and especially the CPU will heat up considerably. Check your server for adequate air 
circulation and think about getting a new fan for the CPU.

Michael
-- 
      ______   _____   __   __ _______ ____   ___   _____   __    __
     | _____|/   _   \|  | |  |__   __|    \ |   |/   _   \ \  \/  /
     | ____||   (_)   |  |_|  |__| |__|   |\     |   (_)   |/  /\  \
     |______|\___   _/ \_____/|_______|___| \____|\_______//__/  \__\
                  \__\
      .    .---------------------------------------------------------.
  _--_|\   | wilsonm@foxtel.com.au             |  "Do or do not.     |    
 /      \  |    			       |   There is no try!" |
 \_.--._/  | http://www.foxtel.com.au/wilsonm/ |	    - Yoda   |	
       .   .---------------------------------------------------------.

In article <31E9DE5E.5287@foxtel.com.au>, wilsonm@foxtel.com.au says...
>
>Darwin Collins wrote:
>> 
>> Kinda sounds like hardware.   Namely, sometype of 'thermal' problem.
>> 
>I agree. During periods of high utilisation such as when a backup job is 
running
>, you'll find
>the Hard Drive(s) and especially the CPU will heat up considerably. Check 
your s
>erver for adequate air 
>circulation and think about getting a new fan for the CPU.

Gee, I dunno, maybe it's my experience with ArcServe, but I'm betting it's 
software... Try running a backup using SBACKUP and see if the problem goes 
away. If it does, get the BackupExec updates...

Don Smith wrote:
> 
> Ok, here's what happens. I have a 4.1 server running on a pentium 133,
> with 32 megs of ram, Adaptec 2940 controller, Quantum 1 meg drive,
> conner tape unit, plextor 4.5 cdrom. I am using BackupExec 7.01a (I
> know 7.01b is out, but don't want to confuse things).
> 
> If I ask for a tape backup in the night, then the next morning the
> server will lock up sometime in the early morning, around 9 am or so.
> If I power it down (which is the only way to talk to it), and leave it
> off for 10 to 15 minutes, it will come back up and stay up for days,
> until I run another tape backup. If I don't leave it off for more than
> a minute, it will go down again. Has been known to go down as many as
> 8 times, or as few as one.
> 
> I have added ram, changed the hard drive, the cdrom, the tape unit.
> All to no avail. What is happening? As far as I can tell, there are no
> warning messages, just a locked unit.
> 
> Help??

	When you refer to locking.. What kind of locking??
	R U talking about the keyboard locks at startup? what???
	Novell begins to boot and then it locks up????

	When and where is necessary to give you eval....

 DS> From: dsmith@mindspring.com (Don Smith)
 DS> Date: Mon, 15 Jul 1996 00:46:52 GMT
 DS> Organization: MindSpring Enterprises

 DS> Ok, here's what happens. I have a 4.1 server running on a pentium
 DS> 133, with 32 megs of ram, Adaptec 2940 controller, Quantum 1 meg
 DS> drive, conner tape unit, plextor 4.5 cdrom. I am using BackupExec
 DS> 7.01a (I know 7.01b is out, but don't want to confuse things). 

 DS> If I ask for a tape backup in the night, then the next morning the
 DS> server will lock up sometime in the early morning, around 9 am or
 DS> so. If I power it down (which is the only way to talk to it), and
 DS> leave it off for 10 to 15 minutes, it will come back up and stay up
 DS> for days, until I run another tape backup. If I don't leave it off
 DS> for more than a minute, it will go down again. Has been known to go
 DS> down as many as 8 times, or as few as one.

Looks like the hardware, still I have to ask: applied all valid patches for
4.1? 

If yes, look at your L2-cache and try what happens if you disable it. Then
take a look at your busspeed and check your IRQ's. You already checked the
termination on your SCSI? Finally, the fan on the CPU is working? 

If these are all OK, do you have suballocation and compression enabled? It is
possible that space is at a premium and when the compression kicks in (default
at 00:00 I believe) it can overload the server when not properly configured.
32 Mb should be enough for the default 64k blocks on one 1Gb volume, but how
are your cachebuffers doing?

Don't forget, if you use a PC for a server, it's still a workstation. No
offense, but if you want a server, buy a server. They ARE more expensive than
the average PC-disguised-and-sold-as-a-server but it saves you a lot of
problems in the end. Like now.

Mazzel, Henk. 
 ###############################################
  Henk Jonkman          henkj@burundi.idn.nl
  The Netherlands       henkj@uni4nn.iaf.nl
 ###############################################

On 15 Jul 1996 12:13:31 GMT, boismier@umich.edu (Tom Boismier) wrote:

>In article <31E9DE5E.5287@foxtel.com.au>, wilsonm@foxtel.com.au says...
>>
>>Darwin Collins wrote:
>>> 
>>> Kinda sounds like hardware.   Namely, sometype of 'thermal' problem.
>>> 
>>I agree. During periods of high utilisation such as when a backup job is 
>running
>>, you'll find
>>the Hard Drive(s) and especially the CPU will heat up considerably. Check 
>your s
>>erver for adequate air 
>>circulation and think about getting a new fan for the CPU.
>
>Gee, I dunno, maybe it's my experience with ArcServe, but I'm betting it's 
>software... Try running a backup using SBACKUP and see if the problem goes 
>away. If it does, get the BackupExec updates...
>
I had the same problem on one of our servers and moved the location of
the astart.ncf up about two line earlier in the autoexec.ncf and it
hasn't abended since.

Don Smith (dsmith@mindspring.com) wrote:
: If I ask for a tape backup in the night, then the next morning the
: server will lock up sometime in the early morning, around 9 am or so.
: If I power it down (which is the only way to talk to it), and leave it
: off for 10 to 15 minutes, it will come back up and stay up for days,
: until I run another tape backup. If I don't leave it off for more than
: a minute, it will go down again. Has been known to go down as many as
: 8 times, or as few as one.
: 

I run Backup Exec 7.01b on a Compaq ProLiant 1500 Pentium133 server
running NW41.  The server has locked up three times since going into
production March 2nd.  After the first two times I removed the
NET-PROT.NLM for virus protection, but it locked a third time.  EVERY TIME
has been while running the Backup Exec client nlm (BE.NLM) on the server!
I've sent files to tech support and talked with them also.  To date there
has been no real answer as to what may be wrong.  My NW41 is up to date,
the latest patches and such from Novell and BackupExec installed, plenty
of memory, hardware is fine, etc.  I am now running without the BE.NLM
(using the client from a workstation).  So far all is well.

My suggestion is to check software and be sure you have the latest patches
for both NW41, BackupExec, and your Adaptec PCI SCSI controller
(&drivers).  BackupExec has a program called "Baxter" which allows you to
perform a dump if the server locks up.  This NLM creates a text file which
they can read to see how to find the offending NLM or process.  This last
lockup it didn't help as we lost the keyboard also, but typically you
still have keyboard functionality so you can enter the Netware debugger.

==========================================
Erick Reverski (CNE)
reverski@access.digex.net
http://www.access.digex.net/~reverski/

Darwin Collins <dcollins@fastlane.net> wrote:

>Kinda sounds like hardware.   Namely, sometype of 'thermal' problem.

>good luck

>-- 
>From: Darwin Collins   Email: dcollins@fastlane.net
>HomePage: http://www.fastlane.net/homepages/dcollins
>NDS utilities and links to support and utility pages.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
my thoughts exactly! . . . the key is in the requirement to wait until
the thing has time to cool . . . 

please let me know via email, or, better yet email and a newsgroup
posting as well, should you positively isolate and expunge this
critter.

regards,
 
Dick Erlacher

In article <31eb522b.0@superego.idcomm.com>, edick@idcomm.com (Dick
Erlacher) wrote:

> >Kinda sounds like hardware.   Namely, sometype of 'thermal' problem.

I don't know if this helps, but I sorta thought the same thing. But I
think the problem came about because you were attempting to do an
unattended, regularly-scheduled backup using Arcserve of your server at
night and got the abend in the morning. As a temporary fix I simply
"Astop" the backup over night and "Astart" in the morning when I come to
work. No abends, and the backups work fine. Hope this helps some. There's
something in the backup software that messes things up.

Mike

-- 
          Mike Perry
          dmperry@access.digex.net

Erick Reverski wrote:
> I run Backup Exec 7.01b on a Compaq ProLiant 1500 Pentium133 server
> running NW41.  The server has locked up three times since going into
> production March 2nd.  After the first two times I removed the
> NET-PROT.NLM for virus protection, but it locked a third time.  EVERY 
> TIME has been while running the Backup Exec client nlm (BE.NLM) on the 
> server!

Hi,
We had a Proliant 1500 P100 lockup intermittently during backup (using 
ProServe). It turned out to be a bad CPU. It passed all the Compaq 
diagnostics. The CE replaced it on a hunch and the problem went away.
Norm