Awesome work, thanks guys

Hi, You can send request to [email protected]

@zev said in Upgrade 31.0 to 31.1 failed: Looks like debug symbols are not installed on your system so core dump does not contain information. Can you please install netxms-server-dbg and attach core dump again. Also can you please provide result of "SELECT id,passive_elements FROM racks" query in NetXMS database? Ok. Today will be done UPD: After installing latest upgrades today ( to 3.1.261-2 ) - database upgrade work as expected. Thanks

Thanks. Scripts are potentially even better, that would give me enough flexibility I'll have to think of a way to ignore a particular DCI on some nodes. I don't want to use maintenance mode because I want to ignore only 1 DCI for a node, but still get alerts about other serious problems I'm thinking maybe at this point in time the way i'll do it is with a combination, custom parameter but also have a monthly script that runs and looks for any nodes with that custom value higher than i.e. 999999 or -1 and if so it'll email me a summary report so that way I can have a regular notification to see if any I should change back to normal monitoring Are there any plans to have a simple 'ignore DCI thresholds' value implemented into the right click menu though?

Ok, figured it out. Used the script in the message of the event's event configuration and it worked perfect...

Thank you. Best regards, Sch.Donat

/Facepalm Ok the terminate event processing policy had no events defined. I'm thinking maybe I renamed or deleted the event and recreated it at some point and didn't re-apply it to the terminate EPP. Hence it was 'always' triggering as it had no match criteria. Added and its working However I still think I needed to enter some number in the 'repeat event' in DCI configuration/threshold for each entry Anyway i've learned a few things along the way, and its working now

You can set it in server configuration - then it will be the default behaviour of the whole system. It was done as it was assumed that either node has connected and have all DCI's or it has no connection, so that users do not need to make any manual actions if instance gone.

Issue created: https://track.radensolutions.com/issue/NX-1727

Created issue: https://track.radensolutions.com/issue/NX-1725

OK, thanks for your reply.

Hi, thanks for your reply. I've synched all ldap users to netxms and I'll build internal groups. Amitay

Hi, Upgraded from 3.0 to 3.1 and now grafana can not connect, i have updated both webui and webapi. The webapi is active but when you save and test in the grafana connector you get "HTTP Error Internal Server Error" Can not find any logs that shows a description of the error found it in the webui logs: INFO: 2019-12-05 09:21:29 192.168.*.* admin 192.168.*.* 8083 GET /webapi/grafana/datacollection dec 05, 2019 9:21:34 FM org.restlet.resource.ServerResource doCatch SEVERE: Exception or error caught in server resource org.restlet.resource.ResourceException: Internal Server Error (500) - The server encountered an unexpected condition which prevented it from fulfilling the request at org.restlet.resource.ServerResource.doHandle(ServerResource.java:527) at org.restlet.resource.ServerResource.get(ServerResource.java:723) at org.restlet.resource.ServerResource.doHandle(ServerResource.java:603) at org.restlet.resource.ServerResource.doNegotiatedHandle(ServerResource.java:662) at org.restlet.resource.ServerResource.doConditionalHandle(ServerResource.java:348) at org.restlet.resource.ServerResource.handle(ServerResource.java:1020) at org.restlet.resource.Finder.handle(Finder.java:236) at org.restlet.routing.Filter.doHandle(Filter.java:150) at org.restlet.routing.Filter.handle(Filter.java:197) at org.restlet.routing.Router.doHandle(Router.java:422) at org.restlet.routing.Router.handle(Router.java:641) at org.restlet.routing.Filter.doHandle(Filter.java:150) at org.restlet.routing.Filter.handle(Filter.java:197) at org.restlet.routing.Filter.doHandle(Filter.java:150) at org.restlet.routing.Filter.handle(Filter.java:197) at org.restlet.routing.Filter.doHandle(Filter.java:150) at org.restlet.routing.Filter.handle(Filter.java:197) at org.restlet.routing.Filter.doHandle(Filter.java:150) at org.restlet.engine.application.StatusFilter.doHandle(StatusFilter.java:140) at org.restlet.routing.Filter.handle(Filter.java:197) at org.restlet.routing.Filter.doHandle(Filter.java:150) at org.restlet.routing.Filter.handle(Filter.java:197) at org.restlet.engine.CompositeHelper.handle(CompositeHelper.java:202) at org.restlet.engine.application.ApplicationHelper.handle(ApplicationHelper.java:77) at org.restlet.Application.handle(Application.java:385) at org.restlet.routing.Filter.doHandle(Filter.java:150) at org.restlet.routing.Filter.handle(Filter.java:197) at org.restlet.routing.Router.doHandle(Router.java:422) at org.restlet.routing.Router.handle(Router.java:641) at org.restlet.routing.Filter.doHandle(Filter.java:150) at org.restlet.routing.Filter.handle(Filter.java:197) at org.restlet.routing.Router.doHandle(Router.java:422) at org.restlet.routing.Router.handle(Router.java:641) at org.restlet.routing.Filter.doHandle(Filter.java:150) at org.restlet.routing.Filter.handle(Filter.java:197) at org.restlet.engine.CompositeHelper.handle(CompositeHelper.java:202) at org.restlet.Component.handle(Component.java:408) at org.restlet.Server.handle(Server.java:507) at org.restlet.engine.connector.ServerHelper.handle(ServerHelper.java:63) at org.restlet.engine.adapter.HttpServerHelper.handle(HttpServerHelper.java:143) at org.restlet.ext.servlet.ServerServlet.service(ServerServlet.java:1117) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215) at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:110) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) at org.eclipse.jetty.server.Server.handle(Server.java:499) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:311) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257) at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:544) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555) at java.lang.Thread.run(Thread.java:748) Caused by: java.net.SocketTimeoutException: connect timed out at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:589) at org.netxms.client.NXCSession.connect(NXCSession.java:1934) at org.netxms.client.NXCSession.connect(NXCSession.java:1907) at org.netxms.websvc.handlers.AbstractHandler.login(AbstractHandler.java:402) at org.netxms.websvc.handlers.AbstractHandler.attachToSession(AbstractHandler.java:218) at org.netxms.websvc.handlers.AbstractHandler.onGet(AbstractHandler.java:77) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.restlet.resource.ServerResource.doHandle(ServerResource.java:511) ... 61 more Everything runs on the same server, netxmsd, webui and grafana Edit: Downgraded the webapi to "NetXMS web service API version 3.0.2296" then it worked again [image: webapi.png]

Templates are matched on guid.

Problem fixed will be included in next patch release

@meandmybrain said in solved -- netxmsd not working after Update: Hi Victor, that worked. Thanks a lot. Now I´ve got the problem, that my version of netxms is 3.1.242-2 (I`m using "netxms-release-latest.deb") but the (newest?) web interface I can find in the download section is nxmc-3.1.241.war. Using this one gives me an error because of a "non-compatible communication protocol". Is the "...latest.deb" for beta-users? I it possible to downgrade netxms to 3.1.241? Thanks ind advance. Best regards, Sebastian Problem is solved. I deleted the old nxmc.war before copying the new one to /tomcat/webapps, now tomcat deployed the new one correctly. Thanks for ur help guys. Best regards Sebastian

Would be nice to have that documented somewhere. I searched for ages, found zero mention of it. Infact I found a few posts on these forums pointing to 'CRON generators' including the one that generated that I'll test it out tomorrow Edit: Yes using only 5 characters in the CRON schedule works as intended. Thank You. Just wish there was some information in the manual/guides or at least a little ? symbol in Schedule area's that when mousing over says something like "CRON format: [minute] [hour] [day of month] [month] [day] i.e. 5 3 * * * will run at 3:05am every day"

Hi! Yes your right, there is no sound and no vibration However, the status of the node as critical is displayed Regards Clifford Dsouza

Latest NXSL manual: www.netxms.org/documentation/nxsl-3.0/ NXSL manual for version 2.2: www.netxms.org/documentation/nxsl-2.2/

Hi, if you want data on map links, right click on a link, select "Properties", then "Data sources", and add DCIs you want to display on that link. Best regards, Victor