Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

DFM Email notifications not working - HTTP status 500 error in DFM 2.0.10

Hi All,

I have recently upgraded...
CiscoWorks Common Services from 3.0.5 – 3.0.6
Campus Manager 4.0.6 – 4.0.10 - 4.0.13
Device Fault Manager 2.0.6 – 2.0.10

Now Email notifications stoped working, it was working fine before.
Even when I was upgrading CM from 4.0.6 to 4.0.10, it worked fine meanwhile. After upgraded it from 4.0.10 to 4.0.13, it stoped working completely.


Before I had same issue and resloved by creating new notification group and subscribed.
Now when I am trying to create new notification group I am getting the below error message

DFM-->Notification Services-->Notification Groups


HTTP Status 500 - Internal Server Error

--------------------------------------------------------------------------------

type Exception report

message Internal Server Error

description The server encountered an internal error (Internal Server Error) that prevented it from fulfilling this request.

exception

java.lang.NullPointerException
at com.cisco.nm.trx.nos.action.NGroup.perform(NGroup.java:140)
at org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1786)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1585)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:491)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2417)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:457)
at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:576)
at java.lang.Thread.run(Thread.java:534)

--------------------------------------------------------------------------------

Apache Tomcat/4.1.29

DFM from 2.0.6 to 2.0.10 and Campus Manager

4 REPLIES
Cisco Employee

Re: DFM Email notifications not working - HTTP status 500 error

Shutdown Daemon Manager, then delete all of files and directories under NMSROOT/MDC/tomcat/work/Standalone/localhost.  Restart Daemon Manager, and if the problem persists, post the output of the pdshow command along with the NMSROOT/log/dfmLogs/NOS/nos.log.

Re: DFM Email notifications not working - HTTP status 500 error

Hi Joe,

Thanks for your response.

I deleted the file at the path which you specified, no luck still I am getting the same below error message when attemption to open Notification Groups tab to create new group.

HTTP Status 500 - Internal Server Error


type Exception report

message Internal Server Error

description The server encountered an internal error (Internal Server Error) that prevented it from fulfilling this request.

exception

java.lang.NullPointerException
     at com.cisco.nm.trx.nos.action.NGroup.perform(NGroup.java:140)
     at org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1786)
     at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1585)
     at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:491)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2417)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:457)
     at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:576)
     at java.lang.Thread.run(Thread.java:534)


Apache Tomcat/4.1.29

Regards,

Naidu.

Cisco Employee

Re: DFM Email notifications not working - HTTP status 500 error

If this is the same server in which you removed NMSROOT/log/dfmLogs, then restore that directory before going any further.

Cisco Employee

Re: DFM Email notifications not working - HTTP status 500 error

The dfmLogs directory cannot be removed (nor can any of the subdirectories).  Doing so will result in NullPointerExceptions (because expected log locations do not exist).  Additionally, in NMSROOT/log there is a conf directory that is used by DFM to setup logging parameters.  This directory must also not be removed or DFM daemons will die with NullPointerExceptions.

364
Views
0
Helpful
4
Replies