NetXMS Support Forum

Quote from: jeffreyz on March 23, 2014, 08:15:13 PM
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

Win 7 + NetXMS 1.2.13 Management Console
Edit Script window: ctrl+c does not copy selected text.

Quote from: Alex Kirhenshtein on March 25, 2014, 07:59:04 PM

Quote from: jeffreyz on March 23, 2014, 08:15:13 PM
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.

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

Jeff,

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

Quote from: raypetter on March 29, 2014, 11:50:16 PM
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

No idea, to be honest. I'd try to capture traffic with tcpdump when nxdbmgr connects (successfully) and compare it to traffic when server connects (with error)

Quote from: jeffreyz on March 28, 2014, 05:40:52 PM
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.

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)


Quote from: andrey--k on March 31, 2014, 03:55:32 PM
Debian 7 + Oracle
next error apears:

Code Select Expand


[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

Quote from: Victor Kirhenshtein on March 21, 2014, 12:32:37 AM

- Management console:
   - Implemented alarm sounds

How can i setup and use this ?

Quote from: jeffreyz on March 23, 2014, 08:15:13 PM
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.

Quote from: Victor Kirhenshtein on March 31, 2014, 11:29:29 AM

Quote from: raypetter on March 29, 2014, 11:50:16 PM
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.

It should be there.

Best regards,
Victor

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?

Hi!

You mean it crashed?

Best regards,
Victor