NetXMS 2.0-M1 released
-
We also get an error on Windows2012R2 server with NetXMS V2.0M1 agent. Here in Eventlog:
Faulting application name: nxagentd.exe, version: 0.0.0.0, time stamp: 0x54afa34c Faulting module name: libnxsnmp.dll, version: 6.3.9600.17476, time stamp: 0x54516b13 Exception code: 0xc0000135 Fault offset: 0x00000000000ec5a0 Faulting process id: 0xdb8 Faulting application start time: 0x01d02dab874d8b4d Faulting application path: C:\Program Files\NetXMS\bin\nxagentd.exe Faulting module path: libnxsnmp.dll Report Id: c4fa1742-999e-11e4-8129-00155d0a6422 Faulting package full name: Faulting package-relative application ID:In agent install directory (bin) is no such DLL 'libnxsnmp.dll'
-
-
Yes, it's a bug in installer. I just uploaded installer with a fix, please try it (file names are the same).
Best regards,
Victor -
Thanks Victor for the fast fix.
Manual upgrade install local on a node is working now (Win x64).But deploy from NetXMS server to a node where agent V1.2.17 is installed does' not work.
The two agent processes (agent and watchdog) are terminated but no update. In Windows eventlog is an error with Event-ID 10006, Source: RestartManager, 'Application or service 'nxagnetd' could not be shut down.edit1:
I don't see any updated files and in Windows Control Panel V1.2.17 is still installed. In 'Services' the NetXMS agent is in 'running' state, but in Task Manager I cannot see any running 'nxagnetd' processes.
Then I 'stopped' the NetXMS agent in 'Services' and started again, service is than in state 'running' but still no 'nxagentd' processes running, and NetXMS server cannot connect to agent.edit2:
I also tested the agent upgrade by package deploy on a Win-x64 node with 'EnableWatchdog=no', that works! So the problem only exists with 'EnableWatchdog=yes'edit3:
Agent install path is 'C:\Program Files\NetXMS' -
-
I've made some changes in installer - hopefully it will help. Please try 2.0-M2 when it will be available.
Best regards,
Victor -
-
Nice catch!
Fixed, will be released in upcoming 2.0-M2.@volkoff said in NetXMS 2.0-M1 released:
Funny bug:
configuration parameter in nxagent ListenAddress actually read backwards.
So instead of 192.168.1.2 you should write 2.1.168.192 -
This one is much more serious:
I can't create or delete DCI.
History:
I tried to play with SNMP's table DCI, but wasn't successful. Later we'll get back to that
But I created one for the node (printer). And since that I can't create or delete DCI. Looks like after "sync" period something breaks, sync thread stops answering to watchdog and I can't connect with console.
So, my opinion - something is wrong in sync thread.
Error is 100% reproducible, so I can supply you with any kind of data.
DB is SQLite, Windows server 2008 R2, but since data is accumulated correctly I do believe something is wrong in sync thread (or with SQLite). -
@volkoff said in NetXMS 2.0-M1 released:
This one is much more serious:
I can't create or delete DCI.
History:
I tried to play with SNMP's table DCI, but wasn't successful. Later we'll get back to that
But I created one for the node (printer). And since that I can't create or delete DCI. Looks like after "sync" period something breaks, sync thread stops answering to watchdog and I can't connect with console.
So, my opinion - something is wrong in sync thread.
Error is 100% reproducible, so I can supply you with any kind of data.
DB is SQLite, Windows server 2008 R2, but since data is accumulated correctly I do believe something is wrong in sync thread (or with SQLite).DCI tables do not work with SQLite.
This is a known issue.
As a workaround for now, you can use a different DB.
-
@tomaskir said in NetXMS 2.0-M1 released:
DCI tables do not work with SQLite.
This is a known issue.
As a workaround for now, you can use a different DB.How terrible
I didn't know about that.
But as a guy who do some programming, I'm aware of the fact, that if there is some issue that prevents using of the product you should provide some bugfix rather than "it's a known issue" even for free and open source product
And since I have this particular bug isolated I can provide some (or even all in my case) data to fix it. -
Proper solution is to migrate to any sane DBMS – you can do it using "nxdbmgr" tool, there is special "nxdbmgr migrate" mode.
SQLite never was intended for use in production environment, and we will probably remove support in future altogether.
Main reason for that – a lot of features are not supported in SQLite (lack of ALTER TABLE DROP COLUMN is perfect example) or implemented poorly – and while it's possible to add workarounds, it require time, which we prefer to spend on more critical tasks.@volkoff said in NetXMS 2.0-M1 released:
@tomaskir said in NetXMS 2.0-M1 released:
DCI tables do not work with SQLite.
This is a known issue.
As a workaround for now, you can use a different DB.How terrible
I didn't know about that.
But as a guy who do some programming, I'm aware of the fact, that if there is some issue that prevents using of the product you should provide some bugfix rather than "it's a known issue" even for free and open source product
And since I have this particular bug isolated I can provide some (or even all in my case) data to fix it. -
-
Migration process is really easy:
- stop server
- copy existing netxmsd.conf into netxmsd.conf.old
- create user and database in new DBMS
- edit netxmsd.conf – change DBDriver and all other DB* parameters
- run "nxdbmgr migrate /etc/netxmsd.conf.old"
@volkoff said in NetXMS 2.0-M1 released:
@alk said in NetXMS 2.0-M1 released:
SQLite never was intended for use in production environment, and we will probably remove support in future altogether.
Well, that's the answer
Ok, I'll use other DBMS. -
@alk said in NetXMS 2.0-M1 released:
- stop server
- copy existing netxmsd.conf into netxmsd.conf.old
- create user and database in new DBMS
- edit netxmsd.conf – change DBDriver and all other DB* parameters
- run "nxdbmgr migrate /etc/netxmsd.conf.old"
Well I used another step "3.5 - Initialize database", because migrate didn't work on empty database (said something about not detecting something (the same as check command on empty database), but anyway it didn't work out, since migration command breaks on syncronization of the first table "config" or something like that with error of SQL statement preparation.
So since it was clean installation and I didn't set up much DCIs so I just used new initialized MySQL database without migration.
If you need/want this SQLite database for some additional testing I can send it to you. -
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login