NetXMS Support Forum

English Support => General Support => Topic started by: vmgracia on August 04, 2021, 12:04:07 AM

Title: event with several server actions generate a SYS_DB_QUERY_FAILED
Post by: vmgracia on August 04, 2021, 12:04:07 AM
Hi All

I have edited several events to declare a single server action in each and they work correctly.

if I add more server actions to any event they still work but I get a critical database error, for example:

496 03.08.2021 22:51:02 03.08. 2021 22:51:02 System LSRPNETXMS1 0 SYS_DB_QUERY_FAILED Critical Database query failed (Query: INSERT INTO server_action_execution_log (id,action_timestamp,action_code,action_name,channel_name,recipient,subject,action_data,success) VALUES (? ,?,?,?,?,?,?,?,?,?,?,?,?); Error: 23505 ERROR: duplicate key value violates unique constraint "server_action_execution_log_pkey"
DETAIL: Key (id)=(494) already exists.) 0

Can someone help me with this?

Title: Re: event with several server actions generate a SYS_DB_QUERY_FAILED
Post by: Filipp Sudanov on August 04, 2021, 02:03:16 PM
What exact netxms version?
Title: Re: event with several server actions generate a SYS_DB_QUERY_FAILED
Post by: vmgracia on August 04, 2021, 02:15:40 PM
NetXMS Server Version 3.9.156 Build 3.9-156-g8c36cbe353 (UNICODE)
NXCP: 5.53.1.31 (AES-256, Blowfish-256, 3DES, AES-128, Blowfish-128)
Built with: g++ (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Title: Re: event with several server actions generate a SYS_DB_QUERY_FAILED
Post by: Filipp Sudanov on August 05, 2021, 07:55:44 AM
And which database are you using?
Title: Re: event with several server actions generate a SYS_DB_QUERY_FAILED
Post by: Filipp Sudanov on August 05, 2021, 08:36:25 AM
This is actually already fixed, will be included in patch release that is coming soon.
Title: Re: event with several server actions generate a SYS_DB_QUERY_FAILED
Post by: vmgracia on August 05, 2021, 11:40:07 AM
thank you very much for your support

just to answer your question, it's postgres:
psql (PostgreSQL) 12.7 (Ubuntu 12.7-0ubuntu0.20.04.1)