NetXMS Support Forum

Server is running on Windows

Though the 30sec interval in running this i don't how that can show anything, if the console times out i can just restart management console and will work instant there is no long running hanging it is just the current network connection for the session that times out.

Can it be the webapi?

Tested some other things with grafana and i noticed that all the connections live long after grafana is closed i.e no data polling.

Just to be clear this is when dashboard is refreshed or loaded in the browser after some time the connections are closed and then only one connection per browser session is open and is used for when a grafana updates.
So it is only when browser loads it creates many connections not when grafana updates.

correct 1.2.3

manage to get the timeout with only 1 client connected so less noise in log.
This time show sessions had no problem but when i typed help, no data was recieved to console it stoped working as soon as i hit enter.

tested more and some times console is stable except from that prompt does not show half the time after command but i can still run command again, close tab and open console again then it is unstable again very odd

Here is the server log.

The console log has no entries for this, everything in this log is from earlier versions.

Hi,

tested the version from github and i still get alot of connections

Hi,

no problems using nxadm -c "show sessions" on server

Hi,

running 3.5.90 and the connection with management is unstable, if i run 'show sessions' in server console the output can stop halfway and then after a while the entire client gets Cannot open server console: Request timed out.
If all the output from sessions is recieved it never returns to prompt need to close the server console tab and open it again to type new command

Hi,

I have a problem that i am trying to understand and see if it is something that can be fixed with config.

When i refresh a dashboard in grafana that has alot of unique DCI values, every tile creates its own session to the server via the webapi meaning you max out available connections to the server and then everything hangs until sessions starts to close.
What i trying to understand if this is how grafana works or is it the netxms datasource plugin or webapi that causes this problem.

If anyone has any knowledge of this i'd be happy to hear it.

Is the driver included in the latest installer the only ncd files i get are these?

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

Thanks for clearing that one up, if it is by design i'll try to stick with it and i kind of got a liking for changing interfaces via object details now

Upgraded server to 3.0.2305 now and in the management console on the nodes in objects the arrow to expand interfaces does not show.
Noticed that the management console is still build 2283 on the download page can this cause this?