NetXMS 1.2.13 released

[andrey--k]

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)

[victor]

@andrey-k said in NetXMS 1.2.13 released:

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

[skoti]

@victor said in NetXMS 1.2.13 released:

• Management console:
    - Implemented alarm sounds

How can i setup and use this ?

[jeffreyz]

@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.

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.

[jeffreyz]

@victor said in NetXMS 1.2.13 released:

@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.

[victor]

It should be there.

Best regards,
Victor

[KArt]

Hello, 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?

[victor]

Hi!

You mean it crashed?

Best regards,
Victor

[KArt]

Yeap, crashed

[raypetter]

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.

[jeffreyz]

@raypetter said in NetXMS 1.2.13 released:

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.

[raypetter]

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

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]

@raypetter said in NetXMS 1.2.13 released:

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

[andrey--k]

Здраствуйте!
Когда планируется (приблизительно) выход следующей версии?

[victor]

Пока рассчитываем в конце этой недели, но может немного задержится.