What methods can be used to analyze the problem that the NMS's background process cannot be started?
For background process:
1.In sysmonitor, change the process' activation mode to manual activation, and then stop the process;
2. In the command line, enter the $N2000ROOT/server/bin directory and manually start the process file of the background of the service. The starting process is shown in the window of the command line. The problem can be basically identified by viewing these messages;
3. View the log files in the $N2000ROOT/server/log/ directory, for example, MA5100V1.log and ma5100v1_gdm.log0, to find out the cause of the problem.
If the NMS platform process cannot be started, you can collect and check the following information:
1. The platform log in $N2000ROOT/server/conf/log;
2. Manually start the n2000 background to check the information printed on the screen. If you execute startn2000.sh (solaris) or startn2000.bat (windows), the screen does not display any useful information except whether the process is started successfully or not. Actually, to start the NMS process, run EmfSysMoniDm to start other process. Therefore, you need to manually start EmfSysMoniDm:
Analyze why the platform fails to start according to the information printed on the screen.
If you still cannot find out the cause of the problem, return these logs and information printed on the screen to HQ for help.
When the NMS platform fails to start, the problem is related to the database in most cases.