• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 532
  • Last Modified:

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!
0
Barca
Asked:
Barca
  • 9
  • 8
  • 4
1 Solution
 
Galtar99Commented:
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.
0
 
BarcaAuthor Commented:
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...

0
 
Galtar99Commented:
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?
0
Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

 
BarcaAuthor Commented:
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,
0
 
ShineOnCommented:
Is the apps volume on its own nss pool, separate from SYS: pool?
0
 
BarcaAuthor Commented:
to:shineOn

yes
0
 
ShineOnCommented:
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.
0
 
Galtar99Commented:
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?
0
 
Galtar99Commented:
Any updates?
0
 
BarcaAuthor Commented:
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.
0
 
Galtar99Commented:
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.
0
 
BarcaAuthor Commented:
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.
0
 
Galtar99Commented:
arcserve and sav should definately be loaded last after everything else.  I would put a delay before those two, so arcserve loads and then ultimately sav, but everything else before those two should have completed their loading before they begin.  You'll have to time it and use trial and error to get it right.  Once you have it right, you might actually notice it load faster since the modules loading don't fight over resources.
0
 
ShineOnCommented:
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.
0
 
Galtar99Commented:
Any updates?
0
 
BarcaAuthor Commented:
I will build a development environment in future 2 weeks , please wait..
0
 
BarcaAuthor Commented:
the development environment is ready now, hope I can solve the problem in these few days
0
 
Galtar99Commented:
Any updates?
0
 
BarcaAuthor Commented:
1 more week, the solution may come out
0
 
Galtar99Commented:
Can you post any results you're getting?  What do you mean "the solution may come out"?
0
 
ShineOnCommented:
Give him a week, Galtar99...
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 9
  • 8
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now