NetXMS Support Forum

Installed 3.9 on Ubuntu 20.04.
Banging my head on a brick wall trying to get 'nxdbmgr init' working. Testing and testing and testing credentials, delete and recreate database, etc.
Eventually realised that mysql.ddr has been replaced with mariadb.ddr.
Please could references to mysql.ddr be replaced with mariadb.ddr, eg:
https://www.netxms.org/documentation/adminguide/server-management.html

Is this actually an error?:

2021.06.18 14:56:55.860 *D* [poll.discovery     ] Cannot find zone proxy node for address range 172.22.141.0/24@19

I can't tell if it's given up at this point or what. There is no proxy required to reach it, should be direct from the server. On the zone it had a proxy of "unknown", which I have now deleted but doesn't seem to have made any difference.

Running a manual scan on this subnet. It's not discovering a couple of routers in this subnet that I *know* have correct SNMP credentials and can be walked and are pingable from the server.

Upgraded from 2.2.13 to 2.2.15 and since then the service isn't staying up. If I start it with netxmsd -D 9, these are the dying gasps:


2019.05.31 18:03:13.434 *D* StatusPoll(PDU): finished child object poll
2019.05.31 18:03:13.434 *D* StatusPoll(PDU): allDown=false, dynFlags=0x00001001
2019.05.31 18:03:13.441 *D* Node(PDU)->GetItemFromSNMP(.1.3.6.1.2.1.1.3.0): dwResult=0
2019.05.31 18:03:13.441 *D* StatusPoll(PDU [1458]): boot time set to 1554531149 from SNMP
2019.05.31 18:03:13.441 *D* Finished status poll for node PDU (ID: 1458)
2019.05.31 18:03:13.441 *D* ConfigReadStr: (cached) name=DeleteUnreachableNodesPeriod value="0"
2019.05.31 18:03:13.441 *D* [poll.conf          ] Starting configuration poll for node Big-Rack-PDU (ID: 1588)
2019.05.31 18:03:13.441 *D* Node is marked as unreachable, configuration poll aborted
2019.05.31 18:03:13.441 *D* Finished configuration poll for node Big-Rack-PDU (ID: 1588)
2019.05.31 18:03:13.441 *D* [poll.status        ] Starting status poll for node Big-Rack-PDU (ID: 1588)
2019.05.31 18:03:13.441 *D* ConfigReadStr: (cached) name=CapabilityExpirationTime value="604800"
2019.05.31 18:03:13.441 *D* [poll.status        ] StatusPoll(Big-Rack-PDU): check SNMP
2019.05.31 18:03:13.448 *D* [snmp.entity        ] Building component tree for BarkS-Core3-POE [1054
Segmentation fault (core dumped)



The output varies, but out of about 10 attempts, more than half of them end with the same line. That node is a Cisco SB switch, which I see mentioned in the release notes for 2.2.15, so I don't think this is a coincidence. How can I troubleshoot this?
nxdbmgr check comes back clear.

This changelog stops at 2.2.9:

https://www.netxms.org/download/ChangeLog

Where does the changelog live now?

Inching my way towards a reporting server.
I have the server service up and running.
I have uploaded the sample report "Alarm Resolution Time". If I try Execute Report, it thinks for a bit but no report appears and nothing is output in workspace/output/4916972f-87c7-4a37-af2c-4d8522e9e645.
I get events like this logged:


[4916972f-87c7-4a37-af2c-4d8522e9e645]
Hibernate: select reportresu0_.id as id1_1_, reportresu0_.executionTime as executio2_1_, reportresu0_.jobId as jobId3_1_, reportresu0_.reportId as reportId4_1_, reportresu0_.userId as userId5_1_ from reporting_results reportresu0_ where reportresu0_.reportId=? and reportresu0_.userId=? order by reportresu0_.executionTime desc
Hibernate: select reportresu0_.id as id1_1_, reportresu0_.executionTime as executio2_1_, reportresu0_.jobId as jobId3_1_, reportresu0_.reportId as reportId4_1_, reportresu0_.userId as userId5_1_ from reporting_results reportresu0_ where reportresu0_.reportId=? and reportresu0_.userId=? order by reportresu0_.executionTime desc
Hibernate: select reportresu0_.id as id1_1_, reportresu0_.executionTime as executio2_1_, reportresu0_.jobId as jobId3_1_, reportresu0_.reportId as reportId4_1_, reportresu0_.userId as userId5_1_ from reporting_results reportresu0_ where reportresu0_.reportId=? and reportresu0_.userId=? order by reportresu0_.executionTime desc

If I add report to the schedule, I get a stack trace like so immediately:


Exception in thread "Thread-14" org.hibernate.exception.SQLGrammarException: error performing isolated work
        at org.hibernate.exception.internal.SQLExceptionTypeDelegate.convert(SQLExceptionTypeDelegate.java:63)
        at org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter.java:42)
        at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:109)
        at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:95)
        at org.hibernate.resource.transaction.backend.jdbc.internal.JdbcIsolationDelegate.delegateWork(JdbcIsolationDelegate.java:78)
        at org.hibernate.id.enhanced.TableStructure$1.getNextValue(TableStructure.java:125)
        at org.hibernate.id.enhanced.NoopOptimizer.generate(NoopOptimizer.java:40)
        at org.hibernate.id.enhanced.SequenceStyleGenerator.generate(SequenceStyleGenerator.java:412)
        at org.hibernate.event.internal.AbstractSaveEventListener.saveWithGeneratedId(AbstractSaveEventListener.java:101)
        at org.hibernate.event.internal.DefaultSaveOrUpdateEventListener.saveWithGeneratedOrRequestedId(DefaultSaveOrUpdateEventListener.java:192)
        at org.hibernate.event.internal.DefaultSaveEventListener.saveWithGeneratedOrRequestedId(DefaultSaveEventListener.java:38)
        at org.hibernate.event.internal.DefaultSaveOrUpdateEventListener.entityIsTransient(DefaultSaveOrUpdateEventListener.java:177)
        at org.hibernate.event.internal.DefaultSaveEventListener.performSaveOrUpdate(DefaultSaveEventListener.java:32)
        at org.hibernate.event.internal.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:73)
        at org.hibernate.internal.SessionImpl.fireSave(SessionImpl.java:679)
        at org.hibernate.internal.SessionImpl.save(SessionImpl.java:671)
        at org.hibernate.internal.SessionImpl.save(SessionImpl.java:666)
        at com.radensolutions.reporting.service.impl.NotificationServiceImpl.create(NotificationServiceImpl.java:25)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:333)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
        at org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:99)
        at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:282)
        at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:213)
        at com.sun.proxy.$Proxy35.create(Unknown Source)
        at com.radensolutions.reporting.service.impl.SessionImpl.reportNotify(SessionImpl.java:258)
        at com.radensolutions.reporting.service.impl.SessionImpl.processMessage(SessionImpl.java:78)
        at com.radensolutions.reporting.service.impl.SessionWorker.run(SessionWorker.java:53)
        at java.lang.Thread.run(Thread.java:748)
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'netxms.hibernate_sequence' doesn't exist
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
        at com.mysql.jdbc.Util.handleNewInstance(Util.java:400)
        at com.mysql.jdbc.Util.getInstance(Util.java:383)
        at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:980)
        at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3847)
        at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3783)
        at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2447)
        at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2594)
        at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2545)
        at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1901)
        at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:2002)
        at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeQuery(NewProxyPreparedStatement.java:76)
        at org.hibernate.id.enhanced.TableStructure.executeQuery(TableStructure.java:224)
        at org.hibernate.id.enhanced.TableStructure.access$300(TableStructure.java:46)
        at org.hibernate.id.enhanced.TableStructure$1$1.execute(TableStructure.java:139)
        at org.hibernate.id.enhanced.TableStructure$1$1.execute(TableStructure.java:126)
        at org.hibernate.jdbc.WorkExecutor.executeReturningWork(WorkExecutor.java:55)
        at org.hibernate.jdbc.AbstractReturningWork.accept(AbstractReturningWork.java:34)
        at org.hibernate.resource.transaction.backend.jdbc.internal.JdbcIsolationDelegate.delegateWork(JdbcIsolationDelegate.java:56)
        ... 30 more

   
The report server is then unreachable and I eventually get a timeout in nxmc. The service is still running at this point and accepting connections, it seems, because I don't get an immediate error [like when it isn't installed].

I can't find any reference to hibernate in the report. I have tried adding           
<dialect>org.hibernate.dialect.MySQLDialect</dialect>
to nxreporting.xml but it doesn't make any difference.

Is nxmc with Java 11 supposed to work? Ubuntu 18.10 comes with Java 11 by default and nxmc doesn't seem to like it.
From the end of a ~2500-line log:

!ENTRY org.eclipse.osgi 4 0 2019-03-01 17:32:42.819
!MESSAGE Application error
!STACK 1
java.lang.IllegalStateException: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini).
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:74)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
        at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
        at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
        at org.eclipse.equinox.launcher.Main.main(Main.java:1414)


I can install Java 8 but then Davmail won't run, which leaves me with an uncomfortable choice between email and NetXMS!

With Cisco SB "SG550XG-8F8T 16-Port 10G Stackable Managed Switch" [OID .1.3.6.1.4.1.9.6.1.90.16.9] the automatically selected network driver is GENERIC. Everything seems to work OK except the Ports tab which is empty. System consists of a pair of these in a stack.

Followed instructions at https://www.netxms.org/forum/general-support/network-driver-type-incorrect/msg19491/#msg19491 to change driver to CISCO-SB. Ports tab is now populated but shows all ports in "Slot 1". The Components tab looks good - shows each stack member with one "slot" [these aren't modular switches] per stack.
I am not sure if the appearance of the Ports tab is what is expected in a stacked switch.
Assuming that the CISCO-SB driver is correct for this switch, what is required to get this type of device always to be detected as CISCO-SB?

Upgrading to 2.1 today. Post-install scripts in package trigger a database upgrade, and all  updates succeed up to:

Setting up netxms-server:amd64 (2.1.0-1) ...
NetXMS Database Manager Version 2.1 Build 9012 (2.1-RELEASE) (UNICODE)

Upgrading database...
Upgrading from version 404 to 405
Upgrading from version 405 to 406
Upgrading from version 406 to 407
Upgrading from version 407 to 408
Upgrading from version 408 to 409
Upgrading from version 409 to 410
Upgrading from version 410 to 411
Converting table tdata_100: done
Converting table tdata_938: done
Converting table tdata_945: done
Converting table tdata_1053: done
Converting table tdata_1054: done
Converting table tdata_1249: done
Converting table tdata_1451: done
Converting table tdata_1458: done
Converting table tdata_1465: done
Converting table tdata_1468: done
Converting table tdata_1470: done
Converting table tdata_1474: done
Converting table tdata_1487: done
Converting table tdata_1496: done
Converting table tdata_1501: done
Converting table tdata_1553: done
Converting table tdata_1586: done
Converting table tdata_1588: done
Converting table tdata_1595: done
Converting table tdata_1597: done
Converting table tdata_1599: done
Converting table tdata_1623: done
Converting table tdata_1628: done
Converting table tdata_1639: done
Converting table tdata_1652: done
Converting table tdata_1660: done
Converting table tdata_1668: done
Converting table tdata_1670: done
Converting table tdata_1702: done
Converting table tdata_1704: done
Converting table tdata_1706: done
Converting table tdata_1708: done
Converting table tdata_1710: done
Converting table tdata_1712: done
Converting table tdata_1714: done
Converting table tdata_1716: done
Converting table tdata_1718: done
Converting table tdata_1720: done
Converting table tdata_1722: done
Converting table tdata_1724: done
Converting table tdata_1726: done
Converting table tdata_1728: done
Converting table tdata_1730: done
Converting table tdata_1732: done
Converting table tdata_1773: done
Converting table tdata_1816: done
Converting table tdata_1823: done
Converting table tdata_1970: done
Converting table tdata_5662: done
Converting table tdata_5706: done
Converting table tdata_5746: done
Converting table tdata_5748: done
Converting table tdata_5750: done
Converting table tdata_5752: done
Converting table tdata_5755: done
Converting table tdata_5757: done
Converting table tdata_5770: done
Converting table tdata_5776: done
Converting table tdata_5796: done
Converting table tdata_5801: done
Converting table tdata_5803: done
Converting table tdata_5805: done
Converting table tdata_5807: done
Converting table tdata_5811: done
Converting table tdata_5845: done
Converting table tdata_5879: done
Converting table tdata_5880: done
Converting table tdata_5915: done
Converting table tdata_5927: done
Converting table tdata_5653: done
Converting table tdata_5655: done
Converting table tdata_5656: done
Converting table tdata_5657: done
Converting table tdata_5658: done
Converting table tdata_5660: done
Converting table tdata_5779: done
Upgrading from version 411 to 412
Upgrading from version 412 to 413
Upgrading from version 413 to 414
Upgrading from version 414 to 415
Upgrading from version 415 to 416
Upgrading from version 416 to 417
Upgrading from version 417 to 418
Upgrading from version 418 to 419
Upgrading from version 419 to 420
Upgrading from version 420 to 421
Upgrading from version 421 to 422
Upgrading from version 422 to 423
Upgrading from version 423 to 424
Upgrading from version 424 to 425
Upgrading from version 425 to 426
Upgrading from version 426 to 427
Upgrading from version 427 to 428
Upgrading from version 428 to 429
Upgrading from version 429 to 430
Upgrading from version 430 to 431
Upgrading from version 431 to 432


Been sat at 431 to 432 for 30 minutes. Server load average is 1.2 so not heavily loaded. Mysql is working fine. 

It seems to me that inverting values on a chart prevents the values from being stacked.
Four WAN interfaces on one firewall, plotted on one chart. The positive DCIs seem to be stacked correctly but negatively is not. Alternatively, I might be misunderstanding how stacked graphs should work.

Would be good to be able to apply a template group to a host as well as individual templates. That way common objects can be split across templates rather than duplicating objects on each template.

I had discovery running a few days ago:

[17-Nov-2015 07:38:13.433] [DEBUG] AcceptNewNode(172.26.1.3): auto filter, flags=0003
[17-Nov-2015 07:38:13.482] [DEBUG] AcceptNewNode(172.26.1.3): auto filter - bResult=0
[17-Nov-2015 07:38:13.482] [DEBUG] NodePoller: processing node 172.26.1.4/32 in zone 0
[17-Nov-2015 07:38:13.482] [DEBUG] AcceptNewNode(172.26.1.4): auto filter, flags=0003
[17-Nov-2015 07:38:13.532] [DEBUG] AcceptNewNode(172.26.1.4): auto filter - bResult=0
[17-Nov-2015 07:38:13.532] [DEBUG] NodePoller: processing node 172.26.1.5/32 in zone 0
[17-Nov-2015 07:38:13.532] [DEBUG] AcceptNewNode(172.26.1.5): auto filter, flags=0003
[17-Nov-2015 07:38:13.582] [DEBUG] AcceptNewNode(172.26.1.5): auto filter - bResult=0
...
[17-Nov-2015 07:53:20.632] [DEBUG] Finished active discovery check on range 172.26.1.1 - 172.26.1.255


What does flags=0003 and bResult=0 mean? I have Network Discovery configured for Active and Passive and 172.26.1.0/24 is in the Active Discovery Targets, but the above three nodes haven't been added. Also, 172.26.1.0/24 is in zone 11 not zone 0.

Since then I have restarted the netxmsd service and I haven't seen any more active discovery messages. Can I force an active discovery? In the Server Configuration, ActiveNetworkDiscovery = 1 which I assume means 'on'.

Server: 192.168.160.1
Agent: 192.168.160.3
Version: 2.0-RC2

Agent config file:

---

# Log File
LogFile=/var/log/nxagentd
DebugLevel = 3
# IP white list, can contain multiple records separated by comma.
# CIDR notation supported for subnets.
MasterServers=127.0.0.0/8,192.168.160.1/32

RequireAuthentication = no
EnableProxy = yes
EnableSNMPProxy = yes

---

Added agent to server as a new node. Can see details in Overview. Can't poll anything from node though:

---

[2015.11.19 13:43:33] **** Poll request sent to server ****
[2015.11.19 13:43:33] Poll request accepted
[2015.11.19 13:43:33] Starting configuration poll for node monitoring.xxx.local
[2015.11.19 13:43:33] Checking node's capabilities...
[2015.11.19 13:43:33] Capability check finished
[2015.11.19 13:43:33] Checking interface configuration...
[2015.11.19 13:43:39] Unable to get interface list from node
[2015.11.19 13:43:43] Interface configuration check finished
[2015.11.19 13:43:43] Checking node name
[2015.11.19 13:43:43] Node name is OK
[2015.11.19 13:43:43] Reading list of installed software packages
[2015.11.19 13:43:43] Unable to get information about installed software packages
[2015.11.19 13:43:54] Finished configuration poll for node monitoring.xxx.local
[2015.11.19 13:43:54] Node configuration was not changed after poll
[2015.11.19 13:43:54] **** Poll completed successfully ****

---

I can use nxget to fetch info:

---

# nxget 192.168.160.3 'Net.Interface.Description(eth0)'
eth0

---

Turn up debugging on agent to 5, restart agent, try again:

---

[19-Nov-2015 13:42:59.183] [INFO ] NetXMS Agent started
[19-Nov-2015 13:43:02.576] [DEBUG] Incoming connection from 192.168.160.1
[19-Nov-2015 13:43:02.576] [DEBUG] Connection from 192.168.160.1 accepted
[19-Nov-2015 13:43:02.659] [DEBUG] Incoming connection from 192.168.160.3
[19-Nov-2015 13:43:03.091] [DEBUG] Connection from 192.168.160.3 rejected
[19-Nov-2015 13:43:03.091] [DEBUG] [session:0] Established proxy connection to 192.168.160.3:4700
[19-Nov-2015 13:43:03.091] [DEBUG] [session:0] CommSession::disconnect()
...repeats...
[19-Nov-2015 13:43:58.190] [DEBUG] [session:0] Session with 192.168.160.1 closed

---

...so it's using itself as a proxy to talk to itself, but not from 127.0.0.1, from its interface that faces the server.

Is this the expected behaviour? The zone that it's in *did* have this server set up as the default proxy for the zone, but I put it back after it stopped working [I guess I know why now]. Checked the node's properties, it is not configured to use itself to poll itself.

Right now [2.0rc2] the management console window title is "NetXMS Management Console". I think it would be sensible to add [either by default or otherwise] the hostname of the server you're connected to and the user you're logged in as [username@hostname].

Another that might be useful is the number of unacked alarms.