your-land/bugtracker
your-land
/
bugtracker
44
20
Code Issues 2.5k Projects 2 Wiki

duplicate key value violates unique constraint "auth_name_key" Key (name)=(basu) already exists. #1189

New Issue
Closed
opened 2021-12-19 14:36:02 +00:00 by AliasAlreadyTaken · 9 comments
AliasAlreadyTaken commented 2021-12-19 14:36:02 +00:00
Owner
Copy Link

2021-12-19 11:56:00: ERROR[Main]: ServerError: AsyncErr: ServerThread::run Lua: Runtime error from mod '' in callback createAuth(): PostgreSQL database error: ERROR: duplicate key value violates unique constraint "auth_name_key"
2021-12-19 11:56:00: ERROR[Main]: DETAIL: Key (name)=(basu) already exists.
2021-12-19 11:56:00: ERROR[Main]: stack traceback:
2021-12-19 11:56:00: ERROR[Main]: [C]: at 0x557f09c49420

2021-12-19 11:56:00: ERROR[Main]: ServerError: AsyncErr: ServerThread::run Lua: Runtime error from mod '' in callback createAuth(): PostgreSQL database error: ERROR: duplicate key value violates unique constraint "auth_name_key" 2021-12-19 11:56:00: ERROR[Main]: DETAIL: Key (name)=(basu) already exists. 2021-12-19 11:56:00: ERROR[Main]: stack traceback: 2021-12-19 11:56:00: ERROR[Main]: [C]: at 0x557f09c49420
AliasAlreadyTaken added the
1. kind/bug
2. prio/critical
 labels 2021-12-19 14:36:10 +00:00
AliasAlreadyTaken commented 2021-12-20 09:57:11 +00:00
Author
Owner
Copy Link

https://github.com/minetest/minetest/issues/11877

https://github.com/minetest/minetest/issues/11877
AliasAlreadyTaken commented 2021-12-20 09:57:14 +00:00
Author
Owner
Copy Link
Minetest version
mt 5.4.1
OS / Hardware

Operating system: debian 11
CPU: AMD Epyc 7282
Postgres postgresql-13 13.5-0+deb11u1

Summary
2021-12-19 11:56:00: ERROR[Main]: ServerError: AsyncErr: ServerThread::run Lua: Runtime error from mod '' in callback createAuth(): PostgreSQL database error: ERROR: duplicate key value violates unique constraint "auth_name_key"
2021-12-19 11:56:00: ERROR[Main]: DETAIL: Key (name)=(basu) already exists.
2021-12-19 11:56:00: ERROR[Main]: stack traceback:
2021-12-19 11:56:00: ERROR[Main]: [C]: at 0x557f09c49420

Backup of 2021-12-16-19-29 does not have a player called "basu" in the auth table, now there is one but logindate is -1

There is a different playername that includes "basu" , like Xyzbasu

Repro

I do not have a repro of any kind, the error happened over the course of 2 years more than once, while the other 16 000 accs had no trouble of that kind.

For my reference 1189

##### Minetest version ``` mt 5.4.1 ``` ##### OS / Hardware <!-- General information about your hardware and operating system --> Operating system: debian 11 CPU: AMD Epyc 7282 Postgres postgresql-13 13.5-0+deb11u1 ##### Summary ``` 2021-12-19 11:56:00: ERROR[Main]: ServerError: AsyncErr: ServerThread::run Lua: Runtime error from mod '' in callback createAuth(): PostgreSQL database error: ERROR: duplicate key value violates unique constraint "auth_name_key" 2021-12-19 11:56:00: ERROR[Main]: DETAIL: Key (name)=(basu) already exists. 2021-12-19 11:56:00: ERROR[Main]: stack traceback: 2021-12-19 11:56:00: ERROR[Main]: [C]: at 0x557f09c49420 ``` Backup of 2021-12-16-19-29 does not have a player called "basu" in the auth table, now there is one but logindate is -1 There is a different playername that includes "basu" , like Xyzbasu ##### Repro I do not have a repro of any kind, the error happened over the course of 2 years more than once, while the other 16 000 accs had no trouble of that kind. For my reference 1189
AliasAlreadyTaken added the
3. source/mod upstream
 label 2021-12-20 09:58:53 +00:00
AliasAlreadyTaken commented 2022-03-31 10:54:12 +00:00
Author
Owner
Copy Link

Happened again:

2022-03-31 12:48:29: ERROR[Main]: ServerError: AsyncErr: Lua: Runtime error from mod '' in callback createAuth(): PostgreSQL database error: ERROR:  duplicate key value violates unique constraint "auth_name_key"
2022-03-31 12:48:29: ERROR[Main]: DETAIL:  Key (name)=(klorenzo) already exists.
2022-03-31 12:48:29: ERROR[Main]: stack traceback:
2022-03-31 12:48:29: ERROR[Main]: 	[C]: at 0x55c4fd2cba30

This time MT server version 5.5.0, OS debian testing, database postgresql 14.2

Happened again: ``` 2022-03-31 12:48:29: ERROR[Main]: ServerError: AsyncErr: Lua: Runtime error from mod '' in callback createAuth(): PostgreSQL database error: ERROR: duplicate key value violates unique constraint "auth_name_key" 2022-03-31 12:48:29: ERROR[Main]: DETAIL: Key (name)=(klorenzo) already exists. 2022-03-31 12:48:29: ERROR[Main]: stack traceback: 2022-03-31 12:48:29: ERROR[Main]: [C]: at 0x55c4fd2cba30 ``` This time MT server version 5.5.0, OS debian testing, database postgresql 14.2
flux commented 2022-03-31 18:27:47 +00:00
Member
Copy Link

I wonder if this happens if 2 attempts are made to register a player "at the same time"? Or, possibly if a "register new player" packet is sent by a client for an already registered name?

I wonder if this happens if 2 attempts are made to register a player "at the same time"? Or, possibly if a "register new player" packet is sent by a client for an already registered name?
flux commented 2022-04-24 19:52:15 +00:00
Member
Copy Link

when i try to replicate this locally i get a different error:

AsyncErr: Lua: Runtime error from mod '*builtin*' in callback on_prejoinplayer(): PostgreSQL database error: ERROR:  current transaction is aborted, commands ignored until end of transaction block

stack traceback:
	[C]: in function 'read'
	/usr/share/minetest/builtin/game/auth.lua:134: in function </usr/share/minetest/builtin/game/auth.lua:130>
	/usr/share/minetest/builtin/game/register.lua:425: in function </usr/share/minetest/builtin/game/register.lua:409>
when i try to replicate this locally i get a different error: ``` AsyncErr: Lua: Runtime error from mod '*builtin*' in callback on_prejoinplayer(): PostgreSQL database error: ERROR: current transaction is aborted, commands ignored until end of transaction block stack traceback: [C]: in function 'read' /usr/share/minetest/builtin/game/auth.lua:134: in function </usr/share/minetest/builtin/game/auth.lua:130> /usr/share/minetest/builtin/game/register.lua:425: in function </usr/share/minetest/builtin/game/register.lua:409> ```
flux commented 2022-04-24 20:05:12 +00:00
Member
Copy Link

or

AsyncErr: Lua: Runtime error from mod '' in callback getAuth(): PostgreSQL database error: ERROR:  current transaction is aborted, commands ignored until end of transaction block

stack traceback:
	[C]: in function 'read'
	/usr/share/minetest/builtin/game/auth.lua:14: in function </usr/share/minetest/builtin/game/auth.lua:12>
or ``` AsyncErr: Lua: Runtime error from mod '' in callback getAuth(): PostgreSQL database error: ERROR: current transaction is aborted, commands ignored until end of transaction block stack traceback: [C]: in function 'read' /usr/share/minetest/builtin/game/auth.lua:14: in function </usr/share/minetest/builtin/game/auth.lua:12> ```
flux commented 2022-04-28 23:32:23 +00:00
Member
Copy Link

https://github.com/minetest/minetest/pull/12234 was merged; we should make use of that ASAP

https://github.com/minetest/minetest/pull/12234 was merged; we should make use of that ASAP
AliasAlreadyTaken commented 2022-05-01 15:39:17 +00:00
Author
Owner
Copy Link

Instead of a 5.5.1 like they should have done, they made a backport branch: https://github.com/minetest/minetest/tree/backport-5

I'll rebuild the engine based on this branch.

Instead of a 5.5.1 like they should have done, they made a backport branch: https://github.com/minetest/minetest/tree/backport-5 I'll rebuild the engine based on this branch.
AliasAlreadyTaken commented 2022-05-09 23:14:04 +00:00
Author
Owner
Copy Link

The backport branch is active now, no more crashes occurred until now.

The backport branch is active now, no more crashes occurred until now.
AliasAlreadyTaken added the
5. result/fixed
 label 2022-05-09 23:14:11 +00:00
AliasAlreadyTaken added this to the 1.1.111 milestone 2022-05-13 05:09:33 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
1. kind/balancing

Depends on balancing

  
1. kind/breaking

something that alters or disables an existing game mechanic

  
1. kind/bug

Something is not working

  
1. kind/construction

A build needs fixing

  
1. kind/documentation

Needs proper documentation

  
1. kind/enhancement

New feature

  
1. kind/griefing

players despoiling builds or nature

  
1. kind/invalid

Not a valid report, e.g. created by mistake with no content.

  
1. kind/meme

issue is mostly a joke

  
1. kind/node limit

something which works for or against the node limit

  
1. kind/other

Something not within the other kinds

  
1. kind/protocol

something concerning how staff should react to player requests, or how players should treat each other

  
2. prio/controversial

not likely to happen w/out a lot of discussion

  
2. prio/critical

Very important

  
2. prio/elevated

something players are eager to have fixed

  
2. prio/good first issue

the resolution to this is could be done by a new minetest contributor, who doesn't yet understand the mod ecosystem

  
2. prio/interesting

one of us has real interest in getting this implemented or fixed. however, more research might be needed.

  
2. prio/low

Not so important

  
3. source/art

art needs to be created or found for this to exist. includes sound, 3d modelling, and in-game building.

  
3. source/client

Issue is with the minetest client, or with player client configuration or the technical details of their setup

  
3. source/engine

Issue is due to a bug or feature of the minetest engine

  
3. source/ingame

Problem and solution exist in-game, e.g. builds or player moderation

  
3. source/integration

Two or more nonbuggy mechanics conflict, or our attempts to rectify conflicting mechanics have created a new bug

  
3. source/lag

A problem which is caused or made worse by lag, due to server processing issues, client processing issues, or network issues

  
3. source/license

A licensing problem is involved

  
3. source/mod upstream

Problem is upstream (not engine/client)

  
3. source/unknown

   
3. source/website

Affects the website

  
4. step/approved

Alias has approved this feature, someone should implement it

  
4. step/at work

Being worked on

  
4. step/blocked

we plan to do this, but other work has to be finished first

  
4. step/discussion

issue is under discussion, a solution has not been dictated or agreed upon

  
4. step/help wanted

Need some help

  
4. step/needs confirmation

   
4. step/partially fixed

this is mitigated or partially solved, but more work needs to be done

  
4. step/question

More information is needed

  
4. step/ready to deploy

has been QA tested by another person. has no outstanding issues. might be installed on prod, but needs final testing

  
4. step/ready to QA test

the code is supposedly fixed, but needs to be tested.

  
4. step/want approval

Someone can quickly implement this if Alias approves the change/feature

  
5. result/cannot reproduce

   
5. result/duplicate

This issue or pull request already exists

  
5. result/fixed

problem is fixed

  
5. result/maybe

not planned currently, but maybe some day

  
5. result/wontfix

the reported issue won't be changed, whether it's intentional or not.

  
ugh/petz

yet another petz bugz.

  
ugh/QA main

That's something we can only wait and see whether it hapens again: On the main server

  
ugh/QA NOK

Fix didn't yield the expected results

  
ugh/QA OK

tested

No Label
1. kind/balancing
1. kind/breaking
1. kind/bug
1. kind/construction
1. kind/documentation
1. kind/enhancement
1. kind/griefing
1. kind/invalid
1. kind/meme
1. kind/node limit
1. kind/other
1. kind/protocol
2. prio/controversial
2. prio/critical
2. prio/elevated
2. prio/good first issue
2. prio/interesting
2. prio/low
3. source/art
3. source/client
3. source/engine
3. source/ingame
3. source/integration
3. source/lag
3. source/license
3. source/mod upstream
3. source/unknown
3. source/website
4. step/approved
4. step/at work
4. step/blocked
4. step/discussion
4. step/help wanted
4. step/needs confirmation
4. step/partially fixed
4. step/question
4. step/ready to deploy
4. step/ready to QA test
4. step/want approval
5. result/cannot reproduce
5. result/duplicate
5. result/fixed
5. result/maybe
5. result/wontfix
ugh/petz
ugh/QA main
ugh/QA NOK
ugh/QA OK
Milestone
Clear milestone
No items
No Milestone
1.1.111
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: your-land/bugtracker#1189
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?