Forum

Getting SQLSTATE 25...
 
Notifications
Retirer tout

Getting SQLSTATE 25P02 Error

9 Posts
2 Utilisateurs
0 Reactions
6,456 Vu
(@divyesh)
Posts: 30
Trusted Member
Début du sujet
 
[#7217]

We are using postgresql 13.1 in centos linux with Projeqtor 9.0.2 latest version.
We have two issues.
[1] We have enable history archiving which is reflecting sql state 23505 error in log file.
[2] Frequent Exception-[25P02] SQLSTATE[25P02]: In failed sql transaction: 7 ERROR:  current transaction is aborted, commands ignored until end of transaction block error is also reflected on user ticket entry screen.

Whole logs file while time of above issue is provided for further investigation.
Request you to please brief for above two issues.
 


 
Posté : 18/01/2021 8:28 am
(@babynus)
Posts: 14952
Membre Admin
 

Hi,

You have duplicates : lines of history stored in historyarchive but still existing in history.

Delte these lines with the query

DELETE FROM `historyarchive` WHERE id IN (SELECT id from `history`);

This query will be added to V9.0.3 to avoid similar issues


 
Posté : 23/01/2021 1:01 pm
(@divyesh)
Posts: 30
Trusted Member
Début du sujet
 

Thanks for response.
As per query no rows found.


 
Posté : 23/01/2021 3:19 pm
(@babynus)
Posts: 14952
Membre Admin
 

So I think issue won't reproduce


 
Posté : 23/01/2021 8:29 pm
(@divyesh)
Posts: 30
Trusted Member
Début du sujet
 

Same errors encountered from user end after your reply.
Seems two different status from treatment window and GUI status modification produces this type of error.


 
Posté : 01/02/2021 12:57 pm
(@babynus)
Posts: 14952
Membre Admin
 

Seems two different status from treatment window and GUI status modification produces this type of error.

Sorry, I don't understand, could you explain use case that produces the error ?


 
Posté : 01/02/2021 1:15 pm
(@divyesh)
Posts: 30
Trusted Member
Début du sujet
 

 


 
Posté : 01/02/2021 1:33 pm
(@divyesh)
Posts: 30
Trusted Member
Début du sujet
 

When user modifies existing ticket if both the status in attached screen is not same than this will trigger such type of errors.


 
Posté : 01/02/2021 1:35 pm
(@babynus)
Posts: 14952
Membre Admin
 

Hi,
This is not a normal situation. Both status listed should always be the same (after saving of course).
It may happen that they are different if network issue occuers. In that case, after saving user doe snot gert the correct save message.
So refresh of the screen should fix the issue.


 
Posté : 01/02/2021 2:10 pm
Share:
Retour en haut