NetXMS Support Forum

Hi all!

NetXMS version 1.0.11 is out. It's a bugfix release, which fixes few bugs in server and legacy management console.

Best regards,
Victor

Hi!

Yes, there is the limitation on script size of about 256KB, imposed by communication protocol. I'll fix that.

Best regards,
Victor

Popravil v 1.0.11.

You can try to execute the following SQL script to downgrade database:

DROP TABLE ap_common;
DROP TABLE ap_bindings;
DROP TABLE ap_config_files;
ALTER TABLE items DROP COLUMN system_tag;

ALTER TABLE users DROP COLUMN auth_failures;
ALTER TABLE users DROP COLUMN last_passwd_change;
ALTER TABLE users DROP COLUMN min_passwd_length;
ALTER TABLE users DROP COLUMN disabled_until;
ALTER TABLE users DROP COLUMN last_login;
ALTER TABLE users DROP COLUMN password_history;

DROP TABLE network_maps;
DROP TABLE network_map_elements;
DROP TABLE network_map_links;

UPDATE metadata SET var_value='105';

Best regards,
Victor

Hi!

There are no standard downgrade procedure. It is not safe to just change schema version. I'll take a look how to downgrade database manually.

Best regards,
Victor

Hi!

Unfortunately it requires more changes in server's code then I expect initially. I'm working on this right now. It should be included in 1.1.1 release.

Best regards,
Victor

Dobrij den'!

Vozmozno problema vse-ze v konkretnom faile. Poproboval sejchas zagruzit' proizvol'nij bol'shoj fail http://robotics10.utcluj.ro/images/big_map.jpg (9921x7015, 12M) - vrode vse ok.

Mozet est' vozmoznost' kuda-to vilozit' vashu kartu? Poprobuju posmotret', pochemu ne gruzitsja.

Viktor

Proveril, eto bug v konsoli - nel'zja postavit' pravo na upravlenie kartami. Kak workaround, mozno pomenjat' prava pol'zovatelja v baze:

UPDATE users SET system_access = 4194303 WHERE id = <user_id>

Eto dast pol'zovatelju vse prava.

Hi!

Try to use SQL server authentication and ODBC driver. MSSQL driver uses very old and outdated client library, which may now work as expected on WIndows Server 2008.

Best regards,
Victor

If it is not here, you just need to create new variable with that name.

Best regards,
Victor

Hi!

Yes, you can change it by setting server's configuration parameter SMTPPort to desired value.

Best regards,
Victor

Hi!

You need to control communication with the site somehow, by pinging router for example. Then you can use situation objects to do manual event correlation. Also, if NetXMS server knows the whole route from itself to managed nodes and has all routers entered as managed nodes as well, it tries to do automatic event correlation based on network topology.

Best regards,
Victor

Hi!

I have two Debian Linux nodes called netxms-1 (10.0.0.11) and netxms-2 (10.0.0.12) with heartbeat and DRBD. Database engine is PostgreSQL, with database on shared disk. There are also virtual IP 10.0.0.10 used for client connection. Configuration files looks like following:

/etc/ha.d/ha.cf

keepalive 1
deadtime 5
warntime 3
initdead 20
bcast eth0
bcast eth1
auto_failback no
node netxms-1
node netxms-2
crm no


/etc/ha.d/haresources

netxms-1 IPaddr::10.0.0.10/24 drbddisk::netxmsdb Filesystem::/dev/drbd0::/postgresql::reiserfs postgresql-8.3 netxmsd


/etc/drbd.conf

global {
        usage-count no;
}

common {
        syncer {
                rate 10M;
        }
}

resource netxmsdb {
        protocol B;
        handlers {
                pri-on-incon-degr "echo o > /proc/sysrq-trigger ; halt -f";
                pri-lost-after-sb "echo o > /proc/sysrq-trigger ; halt -f";
                local-io-error "echo o > /proc/sysrq-trigger ; halt -f";
                # outdate-peer "/usr/lib/heartbeat/drbd-peer-outdater -t 5";
        }

        startup {
                wfc-timeout 0;
                degr-wfc-timeout 120;
        }

        disk {
                on-io-error   detach;
        }

        net {
                cram-hmac-alg "sha1";
                shared-secret "*********";
                after-sb-0pri disconnect;
                after-sb-1pri disconnect;
                after-sb-2pri disconnect;
                rr-conflict disconnect;
        }

        syncer {
                al-extents 257;
        }

        on netxms-1 {
                device /dev/drbd0;
                disk /dev/sdb;
                address 10.10.10.1:7788;
                meta-disk  internal;
        }

        on netxms-2 {
                device /dev/drbd0;
                disk /dev/sdb;
                address 10.10.10.2:7788;
                meta-disk internal;
        }
}


/etc/netxmsd.conf

DBDriver = /usr/lib/libnxddr_pgsql.so
DBServer = 127.0.0.1
DBName = netxms_db
DBLogin = netxms
DBPassword = ******
LogFailedSQLQueries = yes
LogFile = /var/log/netxmsd


File /etc/postgresql/8.3/main/postgresql.conf is quite big, so I don't see any reason to put it here entirely. The only non-default setting there is

data_directory = '/postgresql/main'


PostgreSQL and netxmsd removed from auto-start, as they should be started by heartbeat.

Each node has NetXMS agent running instantly. Agent's configuration file looks like following:


MasterServers = 127.0.0.1, 10.0.0.11, 10.0.0.12
LogFile = /var/log/nxagentd
FileStore = /tmp
SubAgent = /usr/lib/libnsm_portCheck.so


Note that IP addresses of both nodes listed in MasterServers parameter.

Best regards,
Victor

Hi!

I've fixed this bug. Next release will contain the fix.

Best regards,
Victor

Sejchas proveril u sebja na 1.0.10 - rabotaet. Vozmozno problema pojavljaetsja pri kakoj-to specifichnoj konfiguracii. Vi mogli bi prislat', kak vigljadit konfiguracija problemnogo DCI?