Link to home
Create AccountLog in
Avatar of Barca
BarcaFlag for Hong Kong

asked on

trouble to load the Broker.nlm everytime when the Server starts up

Hello there,
I am having a trouble to load the Broker.nlm everytime when the Server starts up.  It hang there when it starts the Broker.nlm and do nothing.  I had to restart the Server, not load the Broker, remove the existing ndps directory and re-copy the default blank (new) ndps to allow me to load the Broker up.  

Server Hardware X3650
Netware 6.5 Support Pack 5
Novell eDirectory Revision 8.7.3.7
broker.nlm 3.00.11
ndpsm.nlm 3.01.22

Please help!
Avatar of Galtar99
Galtar99
Flag of United States of America image

Have you patched NDPS/iPrint to the latest version?
http://download.novell.com/Download?buildid=hKfvAmUN9ws~

Is the broker load statement in your autoexec.ncf point to where the broker object is?

Have you done a dsrepair within a month?  If not, do an unattended repair.

Has your server crashed and/or not been shutdown properly?  You'll need to do a nss /poolrebuild=sys

You should patch your server to SP6 or 7 soon.  7 just came out, so 6 might be safer.
Avatar of Barca

ASKER

1, already updated to sp5,
2, pointing to currect object
3, sure, i did
4, the broker cannot start up randomly even the server shutdown properly

suprise!! that I GHOST the server and restore on another server, and the broker has no problem on startup...even I reset...down...or hard boot...

you already updated to sp5, but have you patched NDPS/iPint to the latest version, SP5d?

Have you repaired the NSS SYS volume and the volume where the broker/print manager stores its files?

Do you migrate the server or are you still trying to get this one to work?  If you were able to ghost it over, that implies that you may have some kind of intermittent problem (i.e. Hardware)  What platform is this running on?
Avatar of Barca

ASKER

Although it runs ok to a different server, we cannot afford the time and cost to migrate the server to a different hardware.  
The server hardware we are running on is IBM x3650.  Not sure if it is a hardware problem because we do not have any error messsage.  
Broker modules hang during the server starts up.  As long as we use re-use the default NDPS blank folder to start, it works again but we have to upload all drivers from scratch.  
We actually run the Broker on APPS: volume, not the default SYS  but that will not be a problem.

Thanks,
Avatar of ShineOn
Is the apps volume on its own nss pool, separate from SYS: pool?
Avatar of Barca

ASKER

to:shineOn

yes
Have you run a poolrebuild on APPS: pool?  Might not hurt...

Since it's not on SYS: have you verified that your APPS volume is mounted prior to launching the broker?  Do you have a search path added for your NDPS folder on APPS:?

Do you have an antivirus running on that server?  Is there a real-time scan running against the NDPS folders?  If so, set the antivirus not to scan the NDPS folders at all.

Make sure the NDPS folders on APPS are set to purge immediate, too.
Does everything load all at once or did you put any delays in?

We had so many modules loading all at once that they were impact each other.  We used delay.nlm and delaycmd.nlm to time how the modules load so they loaded more efficiently.

How did the NSS poolrebuilds go?  Were any errors detected/repaired?
Any updates?
Avatar of Barca

ASKER

i am not in office in these 2 days. ;)

I tried rem and start modules one by one and also with different sequence combination.
only the broker hangs.
Have you done all the things we asked and if so, What was the results?  It's hard to troubleshoot without getting all the details.  Be advised that you do need to run dsrepair and nss poolrebuild until it comes up with no errors.  Running once may not suffice.  Please post logs.
Avatar of Barca

ASKER

Hi guys, many many many thanks for the information.  
We have not made any changes as we cannot afford to test these type of attempts without enough justifications however we have noticed if we REM out the broker and ndpsm, start the server with arcserve, sav and nsure audit without loading broker and ndpsm; then followed by load broker and ndpsm manually, it is ok.  so looks like we could do the delay command at the end for the iprint modules.
Apart from that, I am not sure what else can be done.
ASKER CERTIFIED SOLUTION
Avatar of Galtar99
Galtar99
Flag of United States of America image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
I would be thouroughly unsurprised if the whole problem turned out to be caused by SAV.

Once again, make sure SAV realtime monitor is NOT monitoring any NDPS folders.
Any updates?
Avatar of Barca

ASKER

I will build a development environment in future 2 weeks , please wait..
Avatar of Barca

ASKER

the development environment is ready now, hope I can solve the problem in these few days
Any updates?
Avatar of Barca

ASKER

1 more week, the solution may come out
Can you post any results you're getting?  What do you mean "the solution may come out"?
Give him a week, Galtar99...