NW6.0 SP3 Strat up error.

Pete Hill

unread,

Jan 29, 2004, 9:24:42 PM1/29/04

to

Can someone tell me if this is a problem? Is this an error or just a notice?
Particularly the last entry regarding NDSILIB.NLM
All volumes are mounted.
Maybe I'm just paranoid.
------------------------------------------
System Error Log File:
1-29-2004 7:24:43 pm: FILESYS-5.13-578
Severity = 4 Locus = 7 Class = 19
SERVER02 TTS shut down
because backout volume VOL1 was dismounted.

1-29-2004 7:25:27 pm: DS-10350.19-264
Severity = 1 Locus = 17 Class = 19
Bindery open requested by the SERVER

1-29-2004 7:25:28 pm: DS-10350.19-262
Severity = 1 Locus = 17 Class = 19
Directory Services: Local database is open

1-29-2004 7:25:29 pm: NCP-5.60-66
Severity = 0 Locus = 14 Class = 19
The Network Address [IPX CCA7116:000001:451] has been registered as an
NCP Service Address.

1-29-2004 7:25:29 pm: NCP-5.60-66
Severity = 0 Locus = 14 Class = 19
The Network Address [TCP 192.168.01.02:0524] has been registered as an
NCP Service Address.

1-29-2004 7:25:29 pm: NCP-5.60-66
Severity = 0 Locus = 14 Class = 19
The Network Address [UDP 192.168.01.02:0524] has been registered as an
NCP Service Address.

1-29-2004 7:25:49 pm: SERVER-5.60-836
Severity = 4 Locus = 0 Class = 4
Error unloading killed loadable module (NDSILIB.NLM) NetWare NFS -
eDirectory Interface Library

------------------------------------------
Sorry for the long post and thanks for any help.

Regards,
Peter M. Hill
Remove "_" for direct mail

John Stoecker

unread,

Jan 29, 2004, 10:05:33 PM1/29/04

to

> Can someone tell me if this is a problem? Is this an error or just a notice?
> Particularly the last entry regarding NDSILIB.NLM

do these messages always occur in this order at some particular point
(I.e. server is starting up), or did some event happen (e.g. shutting down
the server, maybe)?

John

--
--------------------------------------------------
Novell Product Support Forums SysOp
--------------------------------------------------
John's Tips & Links Page:
http://mywebpages.comcast.net/jstoecker/novell/

#include disclaim.h:
# My opinions are not necessarily those of Novell
# or its employees or even the other forum sysops or regulars.
--------------------------------------------------
posted using Xananews 1.16.1.3

Pete Hill

unread,

Jan 30, 2004, 8:26:45 AM1/30/04

to

Always on start up. Always in the same order. The only change I can remember
was to add the user Licenses. This server has been in "test" and I got so
many "network traffic is in a bad state" errors that I may not have noticed
the entries I am referring to. I turned off the Lan Traffic Monitor and they
became obvious.

"John Stoecker" <jstoe...@SIGNkwtennPER.IODcom> wrote in message
news:1SjSb.3456$Wh....@prv-forum2.provo.novell.com...

John Stoecker

unread,

Jan 30, 2004, 4:55:21 PM1/30/04

to

> System Error Log File:
> 1-29-2004 7:24:43 pm: FILESYS-5.13-578
> Severity = 4 Locus = 7 Class = 19
> SERVER02 TTS shut down
> because backout volume VOL1 was dismounted.

Can you still access VOL1 after the server is up and running?

All the other messages are merely informational as you might have
assumed.

>
> 1-29-2004 7:25:49 pm: SERVER-5.60-836
> Severity = 4 Locus = 0 Class = 4
> Error unloading killed loadable module (NDSILIB.NLM) NetWare NFS -
> eDirectory Interface Library

I'd guess here that you have the NFS module loaded but maybe no volumes
configured, or some problem with the NFS namespace, or maybe something
else altogether. If you're not using NFS at all, find the statement "NFSSTART"
near the end of your AUTOEXEC.NCF and remark it out and see if the error
message goes away. (Doing this latter only fixes the error message,
not the possible underlying issue, of course).

Are all your volumes NSS at this point? Are you using the Native File
Access System stuff (e.g. Windows, or NFS, or Mac)?

Pete Hill

unread,

Jan 31, 2004, 9:59:57 AM1/31/04

to

I can access all volumes. The SYS VOL is NSS ( obviously), but VOL1 & VOL2
are traditional.
I am not (deliberately) using any Native File Access System stuff.

There was a "NFSSTART" in my AUTOEXEC.NCF. I commented it out and the: "

Error unloading killed loadable module (NDSILIB.NLM) NetWare NFS -

eDirectory Interface Library" goes away.

Any thoughts on the underlying cause?

Thanks for you help, John.

Pete

"John Stoecker" <jstoe...@SIGNkwtennPER.IODcom> wrote in message

news:dpASb.4213$Wh....@prv-forum2.provo.novell.com...

John Stoecker

unread,

Feb 2, 2004, 12:24:25 PM2/2/04

to

> I can access all volumes. The SYS VOL is NSS ( obviously), but VOL1 & VOL2
> are traditional.
> I am not (deliberately) using any Native File Access System stuff.
>
> There was a "NFSSTART" in my AUTOEXEC.NCF. I commented it out and the: "
> Error unloading killed loadable module (NDSILIB.NLM) NetWare NFS -
> eDirectory Interface Library" goes away.
>
> Any thoughts on the underlying cause?

The first thing that comes to mind is that you might not have the NFS namespace
on one of the TFS volumes that NFS is attempting to make available. When
you do an install you'll get a choice about installing the Native File
Access pieces, and it'll try to make all the volumes available.

If you're not using it, I wouldn't worry about it. In fact, if you're not using
any of the other Native file access pieces, you could save some processor
overhead and memory by commenting them out as well.

Pete Hill

unread,

Feb 2, 2004, 12:58:33 PM2/2/04

to

Thanks for all your help John. I am not using Native File Access stuff. I
think it got there during the SP3 install.
Everything is running fine now.

Thanks,
Pete

"John Stoecker" <jstoe...@SIGNkwtennPER.IODcom> wrote in message

news:dJvTb.5358$Wh....@prv-forum2.provo.novell.com...

John Stoecker

unread,

Feb 2, 2004, 1:06:57 PM2/2/04

to

You're welcome!

> Thanks for all your help John