Posted this in general, but it might be more suitable in this thread as it did not occur on the previous version of netxms.

Please use general support instead of announces - it is more suitable for support questions.

Best regards,
Victor

I've had netxms die on me two times. Not much in logs except this;

Apr  4 09:52:07 netxms kernel: [6647577.566437] netxmsd[29596]: segfault at 0 ip 00007f2a203a8f96 sp 00007f2a152bc9e0 error 4 in libnetxms.so.1.0.0[7f2a20382000+39000]

Victor, thanks for fixing the debian package.

Jeff, my guess is that the issue is _not_ netxms related, but in fact postgresql related. I'd downgrade postgresql instead of running bleeding edge. I'm running the latest netxms release on postgresql 9.1 and having no issues.

I am coming to the same conclusion, but have not yet tested this hypothesis. But I am successfully running NetXMS 1.2.13 with PostgreSQL 9.3.4 on another machine (Ubuntu, not Debian), although in that case NetXMS was installed from Debian packages and here I am installing from sources.

Thanks for the input.

Jeff, my guess is that the issue is _not_ netxms related, but in fact postgresql related. I'd downgrade postgresql instead of running bleeding edge. I'm running the latest netxms release on postgresql 9.1 and having no issues.

You mean it crashed?

Best regards,
Victor

I am upgraded to new version 1.2.13. And after that NetXMS became shutdown. I haven't found error for a long time. And now I find only 1 error.

[ERROR] SQL query failed (Query = "INSERT INTO alarm_events (alarm_id,event_id,event_code,event_name,severity,source_object_id,event_timestamp,message) VALUES (?,?,?,?,?,?,?,?)"): 23505 ERROR:  duplicate key value violates unique constraint "alarm_events_pkey"
DETAIL:  Key (alarm_id, event_id)=(3, 354) already exists.

How can I use stable version without shutdown? Maybe it depends on postrgesql version?

Best regards,
Victor

@raypetter said in NetXMS 1.2.13 released:

Victor, please update the postgresql package so that it does NOT depend on postgresql 8.4

Most of us are running 9.1 and newer. For every update I need to extract the package and remove/update the package dependency (DEBIAN/control).

Thanks

I've changed dependency for Debian 7 package. Next release should be ok.

Best regards,
Victor

Is this change present in the hourly snapshot: http://git.netxms.org/netxms-snapshot-develop.tar.gz ?

I don't see it mentioned in the ChangeLog file.

I upgraded from 1.2.12 to 1.2.13 and now I cannot start the server because the server cannot log into the database.

I found that if I change "md5" to "trust" for 127.0.0.1 in pg_hba.conf, then NetXMS server starts up OK and can connect with the PostgreSQL database, i.e., if I change:

host    all             all             127.0.0.1/32            md5

to

host    all             all             127.0.0.1/32            trust

then the problem goes away, although so does the security

To sum things up, nxdbmgr and psql connect flawlessly to the PostgreSQL database with auth-method = md5, but in order for NetXMS server to connect, I need to set auth-method = trust.  Strange.  It worked fine with v1.2.12.  Could it be that something did not get built properly (I installed and upgraded from sources)?

I will try upgrading to v1.2.14 when it appears. Fingers crossed.

• Management console:
    - Implemented alarm sounds

How can i setup and use this ?

Debian 7 + Oracle
next error apears:

[31-Mar-2014 12:13:06.971] [ERROR] SQL query failed (Query = "INSERT INTO event_log (event_id,event_code,event_timestamp,event_source,event_severity,event_message,root_event_id,user_tag) VALUES (?,?,?,?,?,?,?,?)"): ORA-12899: value too large for column "NETXMS"."EVENT_LOG"."USER_TAG" (actual: 73, maximum: 63)
[31-Mar-2014 12:13:31.038] [ERROR] SQL query failed (Query = "INSERT INTO event_log (event_id,event_code,event_timestamp,event_source,event_severity,event_message,root_event_id,user_tag) VALUES (?,?,?,?,?,?,?,?)"): ORA-12899: value too large for column "NETXMS"."EVENT_LOG"."USER_TAG" (actual: 71, maximum: 63)

Fixed.

Best regards,
Victor

[31-Mar-2014 12:13:06.971] [ERROR] SQL query failed (Query = "INSERT INTO event_log (event_id,event_code,event_timestamp,event_source,event_severity,event_message,root_event_id,user_tag) VALUES (?,?,?,?,?,?,?,?)"): ORA-12899: value too large for column "NETXMS"."EVENT_LOG"."USER_TAG" (actual: 73, maximum: 63)
[31-Mar-2014 12:13:31.038] [ERROR] SQL query failed (Query = "INSERT INTO event_log (event_id,event_code,event_timestamp,event_source,event_severity,event_message,root_event_id,user_tag) VALUES (?,?,?,?,?,?,?,?)"): ORA-12899: value too large for column "NETXMS"."EVENT_LOG"."USER_TAG" (actual: 71, maximum: 63)

@jeffreyz said in NetXMS 1.2.13 released:

Do you have any other suggestions?  The data is not very important since this is for a server that I am only using for testing.  Plus it is on a virtual machine so I am willing to try anything - I can always revert to a snapshot if things go south. But I do need to get it going somehow.

Victor, please update the postgresql package so that it does NOT depend on postgresql 8.4

Most of us are running 9.1 and newer. For every update I need to extract the package and remove/update the package dependency (DEBIAN/control).

Thanks

I've changed dependency for Debian 7 package. Next release should be ok.

Best regards,
Victor

I'm also running postgres, although on debian stable 9.1

Only difference from my config versus yours are the following;

netxms.conf
host: 127.0.0.1
driver: libnxddr_pgsql.so

pg_hba

• #local  all            all                                    peer

• local  all            all                                    peer

Most of us are running 9.1 and newer. For every update I need to extract the package and remove/update the package dependency (DEBIAN/control).

Thanks

@jeffreyz said in NetXMS 1.2.13 released:

I upgraded from 1.2.12 to 1.2.13 and now I cannot start the server because the server cannot log into the database.  Here is the output from the server log file (DebugLevel = 9):

1. Try to change "localhost" to "127.0.0.1"
2. Please show your pg_hba.conf

Unfortunately, changing "localhost" to "127.0.0.1" did not work.  Same result. Here is the log file from that attempt:

[28-Mar-2014 16:29:45.942] Log file opened
[28-Mar-2014 16:29:45.942] [DEBUG] Code page set to ASCII
[28-Mar-2014 16:29:45.948] [INFO ] Platform subagent "/usr/local/lib/netxms/linux.nsm" successfully loaded
[28-Mar-2014 16:29:45.948] [DEBUG] Debug callback set for DB library
[28-Mar-2014 16:29:45.952] [INFO ] Database driver "pgsql.ddr" loaded and initialized successfully
[28-Mar-2014 16:29:45.952] [DEBUG] DBConnect: server=127.0.0.1 db=netxms_db login=netxms schema=netxms
[28-Mar-2014 16:29:50.966] [DEBUG] DBConnect: server=127.0.0.1 db=netxms_db login=netxms schema=netxms
[28-Mar-2014 16:29:55.979] [DEBUG] DBConnect: server=127.0.0.1 db=netxms_db login=netxms schema=netxms
[28-Mar-2014 16:30:00.992] [DEBUG] DBConnect: server=127.0.0.1 db=netxms_db login=netxms schema=netxms
[28-Mar-2014 16:30:06.003] [DEBUG] DBConnect: server=127.0.0.1 db=netxms_db login=netxms schema=netxms
[28-Mar-2014 16:30:11.015] [DEBUG] DBConnect: server=127.0.0.1 db=netxms_db login=netxms schema=netxms
[28-Mar-2014 16:30:11.023] [ERROR] Unable to establish connection with database (fe_sendauth: no password supplied)

Here is my pg_hba.conf:

# Database administrative login by Unix domain socket
local   all             postgres                                peer

# TYPE  DATABASE        USER            ADDRESS                 METHOD

# "local" is for Unix domain socket connections only
#local   all             all                                     peer
local   all             all                                     md5

# IPv4 local connections:
host    all             all             127.0.0.1/32            md5

# IPv4 connections from my local subnet
host    all             all             10.0.0.0/16             md5
host    all             all             ::1/128                 md5

Do you have any other suggestions?  The data is not very important since this is for a server that I am only using for testing.  Plus it is on a virtual machine so I am willing to try anything - I can always revert to a snapshot if things go south. But I do need to get it going somehow.

I upgraded from 1.2.12 to 1.2.13 and now I cannot start the server because the server cannot log into the database.  Here is the output from the server log file (DebugLevel = 9):

1. Try to change "localhost" to "127.0.0.1"
2. Please show your pg_hba.conf

Netxms snapshot (2014-03-21)
Debian 7
Oracle 11g

Еще одна ошибочка в sql:

[25-Mar-2014 10:09:26.716] [ERROR] SQL query failed (Query = "INSERT INTO event_log (event_id,event_code,event_timestamp,event_source,event_severity,event_message,root_event_id,user_tag) VALUES (?,?,?,?,?,?,?,?)"): ORA-12899: value too large for column "NETXMS"."EVENT_LOG"."USER_TAG" (actual: 70, maximum: 63)
[25-Mar-2014 10:09:26.716] [DEBUG] EVENT 52 (ID:72059 F:0x0001 S:4 TAG:"") FROM localhost: Database query failed (Query: INSERT INTO event_log (event_id,event_code,event_timestamp,event_source,event_severity,event_message,root_event_id,user_tag) VALUES (?,?,?,?,?,?,?,?); Error: ORA-12899: value too large for column "NETXMS"."EVENT_LOG"."USER_TAG" (actual: 70, maximum: 63))

Я так понимаю - тут тоже надо увеличить длину поля?

Hi!

So nxdbmgr can login to database? That's very strange, because both nxdbmgr and netxmsd uses same library and same config. Just in case please show me your pg_hba.conf.

Yes, nxdbmgr can log in fine.  Here is some output I copied from a shell that also shows

• pg_hba.conf
• logging in to the database using psql (I specified the password from /etc/netxmsd.conf).

All commands are executed from the NetXMS server machine, of course:

root@netxms-debian-vm:~# nxdbmgr check
NetXMS Database Manager Version 1.2.13 Build 7864

Checking database (excluding collected data):
* Checking zone objects...                                            [PASSED]
* Checking node objects...                                            [PASSED]
* Checking interface objects...                                       [PASSED]
* Checking network service objects...                                 [PASSED]
* Checking cluster objects...                                         [PASSED]
* Checking template to node mapping...                                [PASSED]
* Checking object properties...                                       [PASSED]
* Checking event processing policy...                                 [PASSED]
* Checking network map links...                                       [PASSED]
Database doesn't contain any errors
Database check completed

root@netxms-debian-vm:~# nxdbmgr upgrade
NetXMS Database Manager Version 1.2.13 Build 7864

Upgrading database...
Your database format is up to date

root@netxms-debian-vm:~# tail -23 /etc/postgresql/9.3/main/pg_hba.conf
# Database administrative login by Unix domain socket
local   all             postgres                                peer

# TYPE  DATABASE        USER            ADDRESS                 METHOD

# "local" is for Unix domain socket connections only
#local   all             all                                     peer
local   all             all                                     md5

# IPv4 local connections:
host    all             all             127.0.0.1/32            md5

# IPv4 connections from my local subnet
# (so psql or pgAdmin can be used remotely, for example):
host    all             all             10.0.0.0/16             md5

# IPv6 local connections:
host    all             all             ::1/128                 md5
# Allow replication connections from localhost, by a user with the
# replication privilege.
#local   replication     postgres                                peer
#host    replication     postgres        127.0.0.1/32            md5
#host    replication     postgres        ::1/128                 md5

root@netxms-debian-vm:~# psql netxms_db netxms
Password for user netxms:
psql (9.3.4)
Type "help" for help.

netxms_db=> \q
root@netxms-debian-vm:~#

I am at a loss for how to debug this. Are there any other tests that you can suggest?