Bug 1387764 - Near end of install "BDB2053 Freeing read locks for locker 0x1: 2280/4395568132608"
Summary: Near end of install "BDB2053 Freeing read locks for locker 0x1: 2280/43955681...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 25
Hardware: All
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-21 19:47 UTC by Jeremy Linton
Modified: 2017-12-12 10:51 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:51:19 UTC
Type: Bug


Attachments (Terms of Use)
/tmp/*.logs from install (120.04 KB, application/x-gzip)
2016-10-27 14:51 UTC, Jeremy Linton
no flags Details

Description Jeremy Linton 2016-10-21 19:47:04 UTC
Description of problem: Near the end of the install:

Performing post-installation setup tasks
Running in chroot, ignoring request.
Installing boot loader
BDB2053 Freeing read locks for locker 0x1: 2280/4395568132608
BDB2053 Freeing read locks for locker 0x3: 2280/4395568132608
BDB2053 Freeing read locks for locker 0x4: 2280/4395568132608
BDB2053 Freeing read locks for locker 0x5: 2280/4395568132608
BDB2053 Freeing read locks for locker 0x6: 2280/4395568132608
BDB2053 Freeing read locks for locker 0x7: 2280/4395568132608
BDB2053 Freeing read locks for locker 0x8: 2280/4395568132608
BDB2053 Freeing read locks for locker 0x9: 2280/4395568132608
BDB2053 Freeing read locks for locker 0xa: 2280/4395568132608
BDB2053 Freeing read locks for locker 0xb: 2280/4395568132608
BDB2053 Freeing read locks for locker 0xc: 2280/4395568132608
BDB2053 Freeing read locks for locker 0xd: 2280/4395568132608
BDB2053 Freeing read locks for locker 0xe: 2280/4395568132608
BDB2053 Freeing read locks for locker 0xf: 2280/4395568132608
BDB2053 Freeing read locks for locker 0x10: 2280/4395568132608
BDB2053 Freeing read locks for locker 0x11: 2280/4395568132608
BDB2053 Freeing read locks for locker 0x12: 2280/4395568132608
BDB2053 Freeing read locks for locker 0x13: 2280/4395568132608
BDB2053 Freeing read locks for locker 0x14: 2280/4395568132608


Version-Release number of selected component (if applicable): This is the F25B, but it was happening on some more recently nightly as well.


How reproducible: Seems like 100% of the time when I install.


Steps to Reproduce:
1. Install fedora with inst.txt, watch the screen output. 


Other:
Per a couple other defects this seems to be caused by crashes during rpmdb accesses. So, ausearch doesn't work from the install image command line 

[anaconda root@localhost tmp]# ausearch -k rpmdb --pid 2280
ausearch: error while loading shared libraries: libauparse.so.0: cannot open shared object file: No such file or directory

And I didn't see anything helpful in the anaconda logs/etc.

Anypointers?

Comment 1 Paul Whalen 2016-10-26 19:31:56 UTC
Happens on all arches, below is x86_64 text install of F25

Performing post-installation setup tasks
Running in chroot, ignoring request.
Installing boot loader
BDB2053 Freeing read locks for locker 0x1: 1936/140328158557952
BDB2053 Freeing read locks for locker 0x3: 1936/140328158557952
BDB2053 Freeing read locks for locker 0x4: 1936/140328158557952
BDB2053 Freeing read locks for locker 0x5: 1936/140328158557952
BDB2053 Freeing read locks for locker 0x6: 1936/140328158557952
BDB2053 Freeing read locks for locker 0x7: 1936/140328158557952
BDB2053 Freeing read locks for locker 0x8: 1936/140328158557952
BDB2053 Freeing read locks for locker 0x9: 1936/140328158557952
BDB2053 Freeing read locks for locker 0xa: 1936/140328158557952
BDB2053 Freeing read locks for locker 0xb: 1936/140328158557952
BDB2053 Freeing read locks for locker 0xc: 1936/140328158557952
BDB2053 Freeing read locks for locker 0xd: 1936/140328158557952
BDB2053 Freeing read locks for locker 0xe: 1936/140328158557952
BDB2053 Freeing read locks for locker 0xf: 1936/140328158557952
BDB2053 Freeing read locks for locker 0x10: 1936/140328158557952
BDB2053 Freeing read locks for locker 0x11: 1936/140328158557952
BDB2053 Freeing read locks for locker 0x12: 1936/140328158557952
BDB2053 Freeing read locks for locker 0x13: 1936/140328158557952
BDB2053 Freeing read locks for locker 0x14: 1936/140328158557952
.
Performing post-installation setup tasks

Comment 2 Jeremy Linton 2016-10-27 14:51:34 UTC
Created attachment 1214650 [details]
/tmp/*.logs from install

Here are the logs from an install with the above message, although the message doesn't appear in them.

Comment 3 Fedora End Of Life 2017-11-16 18:34:10 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2017-12-12 10:51:19 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.