DFM 3.1.3 Notification Services error

Answered Question
Jun 15th, 2009

The following error messages occur when trying to access Notification Groups, SNMP Trap,E-Mail, and Syslog Notification:

Database error; cannot process your request. Please see the nos.log details. The only option is to click ok. Then this error message appears: Problem with File /WEB-INF/screens/Notification/newtrapSubscription.jsp!!!Cannot find bean NewSubscription in scope null


Any suggestions?

Correct Answer by Joe Clarke about 7 years 8 months ago

Something is preventing the CSTM registry from being created, but it is not obvious what that is. There is an issue with the DFM daemons and their start time, though. It looks like they were started (or restarted) after Daemon Manager was last started. Try restarting Daemon Manager to see if all of the daemons sync up.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Joe Clarke Mon, 06/15/2009 - 12:53

Post the output of the pdshow command, the NMSROOT/log/dfmLogs/NOS/NOS.log, and the NMSROOT/MDC/tomcat/logs/stdout.log and stderr.log.

Joe Clarke Mon, 06/15/2009 - 18:46

Check the permissions on NMSROOT/MDC/tomcat/webapps/triveni/WEB-INF/lib/ctmregistry. Make sure the casusers group has full control for this file.

rcgreen77 Tue, 06/16/2009 - 05:59

I have confirmed that the casusers group has full control of the file mentioned above

Correct Answer
Joe Clarke Tue, 06/16/2009 - 10:17

Something is preventing the CSTM registry from being created, but it is not obvious what that is. There is an issue with the DFM daemons and their start time, though. It looks like they were started (or restarted) after Daemon Manager was last started. Try restarting Daemon Manager to see if all of the daemons sync up.

rcgreen77 Tue, 06/16/2009 - 10:55

I restarted all daemons. I can access everythihng in Notification services without any errors. What you think the problem was/is?

Joe Clarke Tue, 06/16/2009 - 11:12

As I said, it probably had to do with some synchronization issue. The registry may have been locked by another daemon.

Actions

This Discussion