NetXMS Support Forum

Any tips what may be wrong with timescaleDB?

BR
MI

"EXPLAIN ANALYZE SELECT max(event_id) FROM event_log;"
Message: Successfully run. Total query runtime: 3 min 42 secs. 26641 rows affected.
Output = attached in 7z file

For the second query: "EXPLAIN ANALYZE SELECT max(alarm_id) FROM alarms;"
Message:  Successfully run. Total query runtime: 9 secs 232 msec. 3211 rows affected.
Output: attached

In 7z I also included running postgresql.conf file.
After applying timescaleDB extension I run their tuning script and accepted the suggested changes.
It means postgresql.conf contains values alterred by tune script + my mod = increased "max_locks_per_transaction".
The original clasic netxms DB also served by the engine works fine with the settings.

Regards
MI

I did run nxdbmgr init and selected timescale prior migrating from classic db.
Prior migration I also run nxdbmgr check to make sure the source is clean.
Migration took some 20min but overall went smooth without any error reported.
After migration nxdbmgr check does not complan also.

Attached is log file (.7z) captured with -D 9.   

Thanks
MI

so just the log file is attached

Update:

Following https://docs.timescale.com/latest/getting-started/configuring
max_locks_per_transaction = 2 * num_chunks
I increased max_locks_per_transaction from 64 (default) to 256.

The server service starts in 4min, however produces at right after about 10k failed SQL queries and the number keeps growing (current count exids 180k).

BTW what value you suggest to set.

Client starts and seems to work.

Wanted to attache info file (2MB in size ) but getting "413 Request Entity Too Large" error.

Regards
MI

The logs are attached.
_net* is the file I found very surprising.
It seems the service got started eventually - after over 8h.

Regards
Marek

With TS db the server does not crash nor exits -  the service simply remains in "starting" state indefinitely.
CPU load it generates during start is almost zero, also postgres is idling. 
I'll attached the log file created with -D 7 likely tomorrow.

Thanks for your support.

BR
MI

Thanks for prompt reply.

nxdbmgr check - no errors.
Both clasic and TS are clean.
I attached the complete output generated by your script.

BR
MI 

Hello,

I am struggling to get 3.4.178 on Windows to work with PostgreSQL 12.1 + timescale running on Centos 8.1. 
I upgraded working system from 3.2 to 3.4.
It can work with "clasic" DB still.
Working db has been migrated to TimeScale type with no error.
Netxms 3.4.178 works if I direct it to use the "old" db.
With the migrated db the daemon service stucks on start.

Could you advise what to check, please.

Diagnostic log is attached.


Thanks
MI

Hi,

Follow the below steps and you will have NetXMS working, regardless if PG is installed on your local NetXMS host or on a remote DB server (assuming pgadmin4 works remotely for you).

1. Install / upgrade the required version of PostgreSQL on your NetXMS machine or extract the \bin folder from PostgreSQL binary zip package to a folder of your choice (actually you will need dlls only).
2. Make sure the folder is included in windows env path variable or in case of the regular PostgreSQL install, execute the batch file that comes with the install to set local environment up. Make sure it has successfully applied the required changes. (Run "cmd" and then "set" commands to verify system variables. In case they are not set, do it by hand following the batch file content).
3. Rename ...\NetXMS\bin\libpq.dll  to e.g. "_libpq.dll"
4.From the folder to which you have extracted PostgreSQL package or from ..\PostgreSQL\xx\bin\ installation folder, copy "libpq.dll" file to ...\NetXMS\bin\ folder (in place of the earlier renamed dll).
5. Start netxmsd.exe -D 9 to make sure it follows your config file settings and it connects to DB (can be on localhost or on remote serverver machine).
6. Start nx client, it should work fine, stop netxmsd.exe and start NetXMS service the normal way. Reconnect the client.

I hope it'd be of help.

BR
MI