Fernando
> Does netware creates log files when a server "crashes"? I have this
> server that was working fine for over 8 months+ whithout problems, then
> two days in a row frozed.
Check sys:system\abend.log and see if anything is logged there.
--
Andy Thompson
Novell Product Support Forum SysOp
(No email support, thanks.)
Fernando
> Thanks for your answer.
> Unfortunately I am not at the site to do this, I'll check this this
> afternoon. I was reading in the internet that you can run vrepair only
> in traditional volumes, what do you run in NSS volumes?
See http://support.novell.com/cgi-bin/search/searchtid.cgi?/10065514.htm
Fernando
What backup software are you using?
1-30-2204 8:44:08 am: RMANSRVR-3.3-0
Severity = 3 Locus = 17 Class = 3
RMS Report: Building Driver Table of contents.
1-30-2204 8:44:25 am: RMANSRVR-3.3-0
Severity = 3 Locus = 17 Class = 3
RMS Report: Driver Table of Contents Complete.
I found out about the meaning of severity, locus and class.
3-critical-Critical errores are those that Netware tried to fix and
failed. These can occur when an NLM abends, but the server
continues to work.
17-OS information
3-Authorization failure
by the definition of critical; the NLM for the NPDS Broker abended?What
would cause this? how do I fix this? Do I need to run NSS rebuild?
Thanks for your help.
Fernando
Andy Thompson (SysOp) wrote:
What was the abend?
>how do I fix this? Do I need to run NSS rebuild?
You could try it.
Andy Thompson (SysOp) wrote:
>> by the definition of critical; the NLM for the NPDS Broker
>> abended?What would cause this?
>
>
> What was the abend?
I got a severity 3 code in the SYS$LOG.ERR and I don't know what would
cause this.(info below)
1-30-2204 8:44:08 am: RMANSRVR-3.3-0
Severity = 3 Locus = 17 Class = 3
RMS Report: Building Driver Table of contents.
1-30-2204 8:44:25 am: RMANSRVR-3.3-0
Severity = 3 Locus = 17 Class = 3
RMS Report: Driver Table of Contents Complete.
>> how do I fix this? Do I need to run NSS rebuild?
>
I checked the server this weekend, is working fine, however, I found out
the
backup program ends a few minutes after 8:00 AM. Would the backup
program cause this? denied login to users?( I believe there are users
that start working earlier) I changed the starting time for the backup
program and I'll wait for monday.
> You could try it.
Thanks for the help.
Fernando
>
That's not an abend, those are just system messages. Abends are in
sys:system\abend.log
> backup program ends a few minutes after 8:00 AM. Would the backup
> program cause this? denied login to users?( I believe there are users
> that start working earlier) I changed the starting time for the backup
hmm... what problems are you having exactly? Seems to be changing...
is the server abending? Or is it locking up completely? Or is it just
not letting people login?