Which first calls rhnServer/server_token.entitle Which calls rhnServer/server_token.process_token It looks like there are a few different entry points in the system registration code to accessing the rhnPrivateChannelFamily table, and inconsistent use of locking may be the problem:Ĭalls rhnServer/server_rver_token
Postgres deadlock full#
Postgres database log attached, showing the full deadlock output. Satellite-schema-5.6.0.ġ.) Do a mass kickstart of ~3,800 systems (over the course of ~3 hours, approximately 1 system registration every 2-3 seconds) using the same activation key.Ģ.) See 'deadlock detected' errors in database and httpd error logs. Version-Release number of selected component (if applicable): Process 32573: SELECT rhn_channel.update_family_counts(1024, 1) Process 31792: SELECT rhn_entitlements.entitle_server(1000156557, E'enterprise_entitled')
Process 32573 waits for ExclusiveLock on tuple (433,6) of relation 18339 of database 16384 blocked by process 32173. Process 31758 waits for ShareLock on transaction 15425340 blocked by process 32573. Process 31792 waits for ShareLock on transaction 15425338 blocked by process 31758. 05:49:45.027 EDT DETAIL: Process 32173 waits for ShareLock on transaction 15425362 blocked by process 31792. 05:49:45.027 EDT ERROR: deadlock detected +++ This bug was initially created as a clone of Bug #1122625 +++ĭeadlocks detected in postgresql when multiple systems are registering simultaneously, e.g.,
0 kommentar(er)
