NetXMS Support Forum

Quote from: flynao on August 04, 2014, 11:41:46 PM
the only way I found to deploy these xml files to my nodes was as follows:

I created a npi file for each file, so then I uploaded the xml files as a software using the package manager, then as usual I deployed the files to the nodes (the files have been stores at the directory set up on the agent's configuration file.

Package manager should not be affected by changes in file transfer (and introducing filemgr subagent). Could you please check it with "nxupload" command line tool? Syntax is "nxupload AGENT_IP local_file_name". File should be uploaded into FileStore (C:\NetXMS\etc in your case).

I'd use slightly different way (but you'll need file manager subagent for that):

1) Tools -> Upload File to Server (select target XML configuration as "local file", leave "remote name" empty to use local name)
2) Right click on any node or container and select "File upload". Click on "select" button and select file you uploaded in step 1, leave name blank
3) Click "Ok"

Если такое еще раз повторится, проверьте пожалуйста хеш неработающего пароля до смены и после смены на такой же:

SELECT password FROM users WHERE name='user'

А если принудительно сбросить пароль? Правый клик на юзере -> Change password

Системные события нельзя удалить.
В Event Processing Policy уберите правило, которое создает алармы для этого события.

There are no "test" button, but you can check it like this:

1) add new rule to EPP, any (preferablty unsued) event will do - with action "send email", don't forget to save EPP
2) send this event using command line tool "nxevent":nxevent -u admin -P adminpassword localhost SYS_NODE_DOWN

P.S. replace "SYS_NODE_DOWN" with event you choose in step 1.

В аттаче сборка для версии 1.2.15

Исходники есть в гите: http://git.netxms.org/public/netxms.git/tree/develop:/src/java/netxms-jira-connector

Quote from: Dani@M3T on July 28, 2014, 11:29:49 AM
But I get this db upgrade error when I upgrade from V1.2.14 to V1.2.15 on linux 64bit with PostgreSQL:

Hello.

Thank you for report. This bug in upgrade procedure is already fixed, we testing it right now.

SQLite предназначен только для совсем маленьких, тестовых систем - надо для начала сделать миграцию на нормальную базу, я советую PostgreSQL.

В английской ветке форума я писал про процесс миграции: https://www.netxms.org/forum/general-support/database-locked-error/msg14453/#msg14453

To use "nxdbmgr migrate", you need to do a few preparation steps:

1) Create a copy of existing netxmsd.conf, I'll name it "netxmsd_old.conf" in this example
2) Create new database
3) Init with initial schema: nxdbmgr init /opt/netxms/share/netxms/sql/dbinit_pgsql.sql
Please note, that there are different files for different database types, in this example - "dbinit_pgsql.sql" is for PostgreSQL.
4) Adjust "netxmsd.conf" - change DBDriver, DBName, etc. to match new database
5) (optional) run "nxdbmgr check" to verify connectivity to new database
6) run "nxdbmgr migrate netxmsd_old.conf". This will load data from old database (using credentials in netxmsd_old.conf) and migrate it into new one (as configured in netxmsd.conf)

Hello.

Bundled DB engine is SQLite. You can try to export/reimport db into a new file (run in cmd.exe): echo ".dump" | sqlite3 c:\netxms\ database\netxms_db | sqlite3 c:\netxms\ database\netxms_db.new

sqlite3.exe can be downloaded here: http://www.sqlite.org/2014/sqlite-shell-win32-x86-3080500.zip

This should produce a clean copy of the database in file netxms_db.new. Move original netxms_db tor backup and rename netxms_db.new to netxms_db.

I also highly recommend you to migrate to any other database engines, PostgreSQL is common and quite good choice - it's powerful, free and require just a little of the system resources in default configuration.

nxdbmgr can be used for migration (so you don't have to dump data and reimport it manually).

Если подвести курсор к объекту, появится тултип (первый скриншот)
Для каждого DCI на любой ноде (или в темплейте) можно включить опцию "Network Maps -> Show last value on network map" (второй скриншот)
Третий скриншот - пример ноды из первого скриншота, на которой я включил эту опцию на двух DCI

Сейчас IP есть только в tooltip-е (который кстати настраивается)

You need to create all required tables and load initial configuration. This can be done with "nxdbmgr init path_to_sql_file" command, for example:

nxdbmgr init /opt/netxms/share/netxms/sql/dbinit_pgsql.sql


You need to change path (/opt/netxms/share/netxms/sql/) to conform your installation, and please note, that file name is different for different database types:

AirAlk:~() $ ls -l /opt/netxms/share/netxms/sql/dbinit_*.sql
-rw-r--r--  1 alk  admin  120673 Jun 22 22:17 /opt/netxms/share/netxms/sql/dbinit_db2.sql
-rw-r--r--  1 alk  admin  119910 Jun 22 22:17 /opt/netxms/share/netxms/sql/dbinit_mssql.sql
-rw-r--r--  1 alk  admin  112856 Jun 22 22:17 /opt/netxms/share/netxms/sql/dbinit_mysql.sql
-rw-r--r--  1 alk  admin  120498 Jun 22 22:17 /opt/netxms/share/netxms/sql/dbinit_oracle.sql
-rw-r--r--  1 alk  admin  117540 Jun 22 22:17 /opt/netxms/share/netxms/sql/dbinit_pgsql.sql
-rw-r--r--  1 alk  admin  118248 Jun 22 22:17 /opt/netxms/share/netxms/sql/dbinit_sqlite.sql


In your case, most likely command will be

nxdbmgr init /usr/share/netxms/sql/dbinit_sqlite.sql



NB! We strongly suggest not to use SQLite for anything than testing or development

Yes, it's known, low priority issue - it does not affect anything except scary record in log file (server tries to delete collected data for template itself - and fails, since idata_* tables are created only for nodes).

nxdbmgr unlock
nxdbmgr check