Quantcast

snmp-graph.properties file is causing a http 503 error

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

snmp-graph.properties file is causing a http 503 error

mritorto
guys

I am the following changes to my snmp-graph properties file to graph jvm and now my I can't access opennms

I get a http 503 error


can any one help me

see settings below







top of file


mssql, mssql.log, mssql.data, mssql.perf
jvm.heap, jvm.nonheap,jvm.threads, jvm.uptime, jvm.gc, jvm.mempool \



lower section

###
## JVM by marc j ritorto
###






report.jvm.heap.name=JVM Heap Memory
report.jvm.heap.columns=jvmHeapUsed, jvmHeapCommitted, jvmHeapMax
report.jvm.heap.type=nodeSnmp
report.jvm.heap.command=--title="JVM Heap Memory" \
 DEF:used={rrd1}:jvmHeapUsed:AVERAGE \
 DEF:comm={rrd2}:jvmHeapCommitted:AVERAGE \
 DEF:max={rrd3}:jvmHeapMax:AVERAGE \
 AREA:used#0000ff:"Used     " \
 GPRINT:used:AVERAGE:" Avg  \\: %5.2lf %s" \
 GPRINT:used:MIN:"Min  \\: %5.2lf %s" \
 GPRINT:used:MAX:"Max  \\: %5.2lf %s\\n" \
 LINE2:comm#00ff00:"Committed" \
 GPRINT:comm:AVERAGE:" Avg  \\: %5.2lf %s" \
 GPRINT:comm:MIN:"Min  \\: %5.2lf %s" \
 GPRINT:comm:MAX:"Max  \\: %5.2lf %s\\n" \
 LINE2:max#ff0000:"Max           " \
 GPRINT:max:AVERAGE:" Avg  \\: %5.2lf %s" \
 GPRINT:max:MIN:"Min  \\: %5.2lf %s" \
 GPRINT:max:MAX:"Max  \\: %5.2lf %s\\n"

report.jvm.nonheap.name=JVM Non-Heap Memory
report.jvm.nonheap.columns=jvmNonHeapUsed, jvmNonHeapCommitted, jvmNonHeapMax
report.jvm.nonheap.type=nodeSnmp
report.jvm.nonheap.command=--title="JVM Non-Heap Memory" \
 DEF:used={rrd1}:jvmNonHeapUsed:AVERAGE \
 DEF:comm={rrd2}:jvmNonHeapCommitted:AVERAGE \
 DEF:max={rrd3}:jvmNonHeapMax:AVERAGE \
 AREA:used#0000ff:"Used     " \
 GPRINT:used:AVERAGE:" Avg  \\: %5.2lf %s" \
 GPRINT:used:MIN:"Min  \\: %5.2lf %s" \
 GPRINT:used:MAX:"Max  \\: %5.2lf %s\\n" \
 LINE2:comm#00ff00:"Committed" \
 GPRINT:comm:AVERAGE:" Avg  \\: %5.2lf %s" \
 GPRINT:comm:MIN:"Min  \\: %5.2lf %s" \
 GPRINT:comm:MAX:"Max  \\: %5.2lf %s\\n" \
 LINE2:max#ff0000:"Max          " \
 GPRINT:max:AVERAGE:" Avg  \\: %5.2lf %s" \
 GPRINT:max:MIN:"Min  \\: %5.2lf %s" \
 GPRINT:max:MAX:"Max  \\: %5.2lf %s\\n"
 
report.jvm.threads.name=JVM Threads
report.jvm.threads.columns=jvmThreadCount
report.jvm.threads.type=nodeSnmp
report.jvm.threads.command=--title="JVM Thread Count" \
 DEF:threads={rrd1}:jvmThreadCount:AVERAGE \
 LINE2:threads#0000ff:"Threads" \
 GPRINT:threads:AVERAGE:" Avg \\: %8.2lf %s" \
 GPRINT:threads:MIN:"Min  \\: %8.2lf %s" \
 GPRINT:threads:MAX:"Max  \\: %8.2lf %s\\n"
 
report.jvm.uptime.name=JVM Uptime
report.jvm.uptime.columns=jvmRTUptimeMs
report.jvm.uptime.type=nodeSnmp
report.jvm.uptime.command=--title="JVM Uptime" \
 --vertical-label Hours \
 DEF:time={rrd1}:jvmRTUptimeMs:AVERAGE \
 CDEF:hours=time,3600000,/ \
 LINE2:hours#0000ff:"JVM Uptime (Hours)" \
 GPRINT:hours:AVERAGE:"Avg  \\: %8.1lf %s" \
 GPRINT:hours:MIN:"Min  \\: %8.1lf %s" \
 GPRINT:hours:MAX:"Max  \\: %8.1lf %s\\n"

report.jvm.gc.name=JVM GC Time
report.jvm.gc.columns=jvmMemGCCount, jvmMemGCTimeMs
report.jvm.gc.type=jvmMemManagerIndex
report.jvm.gc.propertiesValues=jvmMemManagerName
report.jvm.gc.command=--title="JVM GC Time {jvmMemManagerName}" \
 DEF:gccount={rrd1}:jvmMemGCCount:LAST \
 DEF:gctimems={rrd2}:jvmMemGCTimeMs:LAST \
 CDEF:gctimes=gctimems,1000,/ \
 LINE2:gctimes#ff0000:"Time (s) :" \
 GPRINT:gctimes:LAST:" Current  \\: %8.2lf %s" \
 GPRINT:gctimes:MIN:"Min  \\: %8.2lf %s" \
 GPRINT:gctimes:MAX:"Max  \\: %8.2lf %s\\n"





report.jvm.mempool.name=JVM Memory Pool
report.jvm.mempool.columns=jvmMemPoolInitSize, jvmMemPoolUsed, jvmMemPoolMaxSize, jvmMemPoolCommit
report.jvm.mempool.type=jvmMemPoolIndex
report.jvm.mempool.propertiesValues=jvmMemPoolName
report.jvm.mempool.command=--title="JVM Memory Pool - {jvmMemPoolName}" \
 --vertical-label="Bytes" \
 --base=1024 \
 DEF:used={rrd1}:jvmMemPoolUsed:AVERAGE \
 DEF:max={rrd2}:jvmMemPoolMaxSize:AVERAGE \
 DEF:init={rrd3}:jvmMemPoolInitSize:AVERAGE \
 DEF:commit={rrd4}:jvmMemPoolCommit:AVERAGE \
 AREA:used#00a876:"Used     " \
 GPRINT:used:AVERAGE:" Average  \\: %5.2lf %s" \
 GPRINT:used:MIN:"Min  \\: %5.2lf %s" \
 GPRINT:used:MAX:"Max  \\: %5.2lf %s\\n" \
 LINE2:max#FF5900:"Max      " \
 GPRINT:max:AVERAGE:" Average  \\: %5.2lf %s" \
 GPRINT:max:MIN:"Min  \\: %5.2lf %s" \
 GPRINT:max:MAX:"Max  \\: %5.2lf %s\\n" \
 LINE2:commit#1047a9:"Committed" \
 GPRINT:commit:AVERAGE:" Average  \\: %5.2lf %s" \
 GPRINT:commit:MIN:"Min  \\: %5.2lf %s" \
 GPRINT:commit:MAX:"Max  \\: %5.2lf %s\\n" \
 LINE2:init#000000:"Initial  " \
 GPRINT:init:AVERAGE:" Average  \\: %5.2lf %s" \
 GPRINT:init:MIN:"Min  \\: %5.2lf %s" \
 GPRINT:init:MAX:"Max  \\: %5.2lf %s\\n"


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: snmp-graph.properties file is causing a http 503 error

Rob Walker-2-3
Marc,

I don't know how accurately you represented the top of your file, but in
my snmp-graph.properties file, I have to have a , (comma) after each
graph name, even if they are at the end of a line and are followed by a
\ (backslash) character.  Is that the actual representation of your
"reports=" line?

Thanks,
Rob

On 3/1/12 8:48 AM, mritorto wrote:

> guys
>
> I am the following changes to my snmp-graph properties file to graph jvm and
> now my I can't access opennms
>
> I get a http 503 error
>
>
> can any one help me
>
> see settings below
>
>
>
>
>
>
>
> top of file
>
>
> mssql, mssql.log, mssql.data, mssql.perf
> jvm.heap, jvm.nonheap,jvm.threads, jvm.uptime, jvm.gc, jvm.mempool \
>
>
>
> lower section
>
> ###
> ## JVM by marc j ritorto
> ###
>
>
>
>
>
>
> report.jvm.heap.name=JVM Heap Memory
> report.jvm.heap.columns=jvmHeapUsed, jvmHeapCommitted, jvmHeapMax
> report.jvm.heap.type=nodeSnmp
> report.jvm.heap.command=--title="JVM Heap Memory" \
>  DEF:used={rrd1}:jvmHeapUsed:AVERAGE \
>  DEF:comm={rrd2}:jvmHeapCommitted:AVERAGE \
>  DEF:max={rrd3}:jvmHeapMax:AVERAGE \
>  AREA:used#0000ff:"Used     " \
>  GPRINT:used:AVERAGE:" Avg  \\: %5.2lf %s" \
>  GPRINT:used:MIN:"Min  \\: %5.2lf %s" \
>  GPRINT:used:MAX:"Max  \\: %5.2lf %s\\n" \
>  LINE2:comm#00ff00:"Committed" \
>  GPRINT:comm:AVERAGE:" Avg  \\: %5.2lf %s" \
>  GPRINT:comm:MIN:"Min  \\: %5.2lf %s" \
>  GPRINT:comm:MAX:"Max  \\: %5.2lf %s\\n" \
>  LINE2:max#ff0000:"Max           " \
>  GPRINT:max:AVERAGE:" Avg  \\: %5.2lf %s" \
>  GPRINT:max:MIN:"Min  \\: %5.2lf %s" \
>  GPRINT:max:MAX:"Max  \\: %5.2lf %s\\n"
>
> report.jvm.nonheap.name=JVM Non-Heap Memory
> report.jvm.nonheap.columns=jvmNonHeapUsed, jvmNonHeapCommitted,
> jvmNonHeapMax
> report.jvm.nonheap.type=nodeSnmp
> report.jvm.nonheap.command=--title="JVM Non-Heap Memory" \
>  DEF:used={rrd1}:jvmNonHeapUsed:AVERAGE \
>  DEF:comm={rrd2}:jvmNonHeapCommitted:AVERAGE \
>  DEF:max={rrd3}:jvmNonHeapMax:AVERAGE \
>  AREA:used#0000ff:"Used     " \
>  GPRINT:used:AVERAGE:" Avg  \\: %5.2lf %s" \
>  GPRINT:used:MIN:"Min  \\: %5.2lf %s" \
>  GPRINT:used:MAX:"Max  \\: %5.2lf %s\\n" \
>  LINE2:comm#00ff00:"Committed" \
>  GPRINT:comm:AVERAGE:" Avg  \\: %5.2lf %s" \
>  GPRINT:comm:MIN:"Min  \\: %5.2lf %s" \
>  GPRINT:comm:MAX:"Max  \\: %5.2lf %s\\n" \
>  LINE2:max#ff0000:"Max          " \
>  GPRINT:max:AVERAGE:" Avg  \\: %5.2lf %s" \
>  GPRINT:max:MIN:"Min  \\: %5.2lf %s" \
>  GPRINT:max:MAX:"Max  \\: %5.2lf %s\\n"
>  
> report.jvm.threads.name=JVM Threads
> report.jvm.threads.columns=jvmThreadCount
> report.jvm.threads.type=nodeSnmp
> report.jvm.threads.command=--title="JVM Thread Count" \
>  DEF:threads={rrd1}:jvmThreadCount:AVERAGE \
>  LINE2:threads#0000ff:"Threads" \
>  GPRINT:threads:AVERAGE:" Avg \\: %8.2lf %s" \
>  GPRINT:threads:MIN:"Min  \\: %8.2lf %s" \
>  GPRINT:threads:MAX:"Max  \\: %8.2lf %s\\n"
>  
> report.jvm.uptime.name=JVM Uptime
> report.jvm.uptime.columns=jvmRTUptimeMs
> report.jvm.uptime.type=nodeSnmp
> report.jvm.uptime.command=--title="JVM Uptime" \
>  --vertical-label Hours \
>  DEF:time={rrd1}:jvmRTUptimeMs:AVERAGE \
>  CDEF:hours=time,3600000,/ \
>  LINE2:hours#0000ff:"JVM Uptime (Hours)" \
>  GPRINT:hours:AVERAGE:"Avg  \\: %8.1lf %s" \
>  GPRINT:hours:MIN:"Min  \\: %8.1lf %s" \
>  GPRINT:hours:MAX:"Max  \\: %8.1lf %s\\n"
>
> report.jvm.gc.name=JVM GC Time
> report.jvm.gc.columns=jvmMemGCCount, jvmMemGCTimeMs
> report.jvm.gc.type=jvmMemManagerIndex
> report.jvm.gc.propertiesValues=jvmMemManagerName
> report.jvm.gc.command=--title="JVM GC Time {jvmMemManagerName}" \
>  DEF:gccount={rrd1}:jvmMemGCCount:LAST \
>  DEF:gctimems={rrd2}:jvmMemGCTimeMs:LAST \
>  CDEF:gctimes=gctimems,1000,/ \
>  LINE2:gctimes#ff0000:"Time (s) :" \
>  GPRINT:gctimes:LAST:" Current  \\: %8.2lf %s" \
>  GPRINT:gctimes:MIN:"Min  \\: %8.2lf %s" \
>  GPRINT:gctimes:MAX:"Max  \\: %8.2lf %s\\n"
>
>
>
>
>
> report.jvm.mempool.name=JVM Memory Pool
> report.jvm.mempool.columns=jvmMemPoolInitSize, jvmMemPoolUsed,
> jvmMemPoolMaxSize, jvmMemPoolCommit
> report.jvm.mempool.type=jvmMemPoolIndex
> report.jvm.mempool.propertiesValues=jvmMemPoolName
> report.jvm.mempool.command=--title="JVM Memory Pool - {jvmMemPoolName}" \
>  --vertical-label="Bytes" \
>  --base=1024 \
>  DEF:used={rrd1}:jvmMemPoolUsed:AVERAGE \
>  DEF:max={rrd2}:jvmMemPoolMaxSize:AVERAGE \
>  DEF:init={rrd3}:jvmMemPoolInitSize:AVERAGE \
>  DEF:commit={rrd4}:jvmMemPoolCommit:AVERAGE \
>  AREA:used#00a876:"Used     " \
>  GPRINT:used:AVERAGE:" Average  \\: %5.2lf %s" \
>  GPRINT:used:MIN:"Min  \\: %5.2lf %s" \
>  GPRINT:used:MAX:"Max  \\: %5.2lf %s\\n" \
>  LINE2:max#FF5900:"Max      " \
>  GPRINT:max:AVERAGE:" Average  \\: %5.2lf %s" \
>  GPRINT:max:MIN:"Min  \\: %5.2lf %s" \
>  GPRINT:max:MAX:"Max  \\: %5.2lf %s\\n" \
>  LINE2:commit#1047a9:"Committed" \
>  GPRINT:commit:AVERAGE:" Average  \\: %5.2lf %s" \
>  GPRINT:commit:MIN:"Min  \\: %5.2lf %s" \
>  GPRINT:commit:MAX:"Max  \\: %5.2lf %s\\n" \
>  LINE2:init#000000:"Initial  " \
>  GPRINT:init:AVERAGE:" Average  \\: %5.2lf %s" \
>  GPRINT:init:MIN:"Min  \\: %5.2lf %s" \
>  GPRINT:init:MAX:"Max  \\: %5.2lf %s\\n"
>
>
>
>
> --
> View this message in context: http://opennms.530661.n2.nabble.com/snmp-graph-properties-file-is-causing-a-http-503-error-tp7333194p7333194.html
> Sent from the OpenNMS - discuss mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> Please read the OpenNMS Mailing List FAQ:
> http://www.opennms.org/index.php/Mailing_List_FAQ
>
> opennms-discuss mailing list
>
> To *unsubscribe* or change your subscription options, see the bottom of this page:
> https://lists.sourceforge.net/lists/listinfo/opennms-discuss
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: snmp-graph.properties file is causing a http 503 error

mritorto
can you send me a piece of what yours looks like

thanks
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: snmp-graph.properties file is causing a http 503 error

Ken Eshelby
Try adding a definition one at a time, loading the graph's page to verify it doesn't break.  Process of elimination should get you to where the problem lies.

I have had some hidden characters sneak in that caused me to retype the entire definition by hand.

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: snmp-graph.properties file is causing a http 503 error

Patrick Tuite
Also check the /var/log/opennms/webapp/jetty.log. It should provide some context.

P


On 02/03/12 03:09, Ken Eshelby wrote:
Try adding a definition one at a time, loading the graph's page to verify it doesn't break.  Process of elimination should get you to where the problem lies.

I have had some hidden characters sneak in that caused me to retype the entire definition by hand.


------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/


_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss


------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: snmp-graph.properties file is causing a http 503 error

Seibold, Michael
In reply to this post by mritorto


> mssql, mssql.log, mssql.data, mssql.perf jvm.heap, jvm.nonheap,jvm.threads, jvm.uptime, jvm.gc, jvm.mempool \

just adding a semicolon after jvm.mempool should do the trick (if  there is no other error)

- Michael

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Loading...