NetXMS Support Forum

Hello.

It's unfinished yet, I'll try to push complete version today.

Reporting server can be downloaded here  or built from sources (http://git.netxms.org/public/netxms.git/tree/develop:/src/java/nxreporting). I also put sample configuration and report into archive.

I'm actually writing this piece of documentation right now. Will be available here later today.

Please provide backtrace of this crash (details on how to get a backtrace: https://wiki.debian.org/HowToGetABacktrace#Running_gdb)

Check nxclapi.h for complete list: http://git.netxms.org/public/netxms.git/blob/HEAD:/include/nxclapi.h?js=1#l132

Type "bt" on gdb prompt "(gdb)", this will produce complete backtrace

Note about enabled filemgr subagent on the large network, there are two ways:

1) Create configuration policy and deploy to all agents, where required.
Sample policy:
<config>
  <agent>
    <subagent>filemgr.nsm</subagent>
  </agent>

  <filemgr>
    <RootFolder>/opt</RootFolder>
    <RootFolder>/private/etc</RootFolder>
  </filemgr>
</config>

2) Use nxshell-based script to fetch existing agent config remotely, modify it and reapply. I don't have script on hand at the moment, but can share it later.

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)