Description of problem: $ rm ~/.kde/share/config/nepomukserverrc; nepomukctl start; sleep 5; nepomukbaloomigrator Recently migrated form F19 to F21 and trying to migrate my tags. nepomukctl start; sleep 5; nepomukbaloomigrator would migrate a few tags when nepomuk dies with Nepomuk Server started successfully. ProcessControl: Application '/usr/bin/nepomukfileindexer' stopped unexpected (Process crashed) Application '/usr/bin/nepomukfileindexer ' crashed. No restart! Application '/usr/bin/nepomukfilewatch ' exited normally... Application '/usr/bin/nepomukstorage ' exited normally... So I am using $ rm ~/.kde/share/config/nepomukserverrc; nepomukctl start; sleep 5; nepomukbaloomigrator which usually migrates a fe wobejcts at a time. The problems with nepomuk dying, as well as "nepomukbaloomigrator: Could not obtain lock for Xapian Database." is likely caused by the fact that concurently to nepomukbaloomigrator nepomuk and baloo itself are concurrently reindexing itself, causing race conditions. Version-Release number of selected component: virtuoso-opensource-6.1.6-7.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/bin/virtuoso-t +foreground +configfile /tmp/virtuoso_C27238.ini +wait crash_function: hit_next executable: /usr/bin/virtuoso-t kernel: 3.17.8-300.fc21.i686+PAE runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 hit_next at Dkhashext.c:148 #1 id_hash_rehash at Dkhashext_template.c:409 #2 id_hash_set at Dkhashext_template.c:115 #3 ric_iri_to_sub at rdfinf.c:723 #4 bif_rdf_inf_dir at rdfinf.c:867 #5 ins_call_bif at sqlintrp.c:178 #6 code_vec_run_1 at sqlintrp.c:1896 #7 qn_input at sqlrun.c:680 #8 qr_subq_exec at sqlrun.c:3544 #9 ins_call at sqlintrp.c:453 Potential duplicate: bug 1019900
Created attachment 979744 [details] File: backtrace
Created attachment 979745 [details] File: cgroup
Created attachment 979746 [details] File: core_backtrace
Created attachment 979747 [details] File: dso_list
Created attachment 979748 [details] File: environ
Created attachment 979749 [details] File: exploitable
Created attachment 979750 [details] File: limits
Created attachment 979751 [details] File: maps
Created attachment 979752 [details] File: open_fds
Created attachment 979753 [details] File: proc_pid_status
Created attachment 979754 [details] File: var_log_messages
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.