On Thursday 21 August 2014 17:23:24 Daniel Vratil wrote:
If the migrator cannot get lock, then it's probably before some
other
process is holding it - I assume you have the baloo_file process running,
so stop it (just kill it, there's no other way) and run the migrator - this
time it could work. Then start baloo_file again.
A bit better, no lock errors, but still crashing :
$ nepomukctl start
$ nepomukctl status
Nepomuk Server is running.
Service storage is running.
Service filewatch is running.
$ balooctl stop
$ balooctl status
Baloo File Indexer is NOT running
Indexed 64273 / 64273 files
Failed to index 0 files
$ nepomukbaloomigrator
Object::connect: No such signal
org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal
org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
nepomukbaloomigrator(14590): Bananana Error
nepomukbaloomigrator(14590):
nepomukbaloomigrator(14590): Bananana Error
nepomukbaloomigrator(14590): Serious Error:
nepomukbaloomigrator(14590): Error opening table
`/home/piotr/.local/share/baloo/file/postlist.':
Couldn't open /home/piotr/.local/share/baloo/file/postlist.baseA: Too many open
files
Couldn't open /home/piotr/.local/share/baloo/file/postlist.baseB: Too many open
files
DatabaseOpeningError: Error opening table
`/home/piotr/.local/share/baloo/file/postlist.':
Couldn't open /home/piotr/.local/share/baloo/file/postlist.baseA: Too many open
files
Couldn't open /home/piotr/.local/share/baloo/file/postlist.baseB: Too many open
files
KCrash: Application 'nepomukbaloomigrator' crashing...
KCrash: Attempting to start /usr/libexec/kde4/drkonqi from kdeinit
sock_file=/home/piotr/.kde/socket-takeshi.reconnix.com/kdeinit4__0
QSocketNotifier: Invalid socket 23 and type 'Read', disabling...
Any ideas ?
--
Piotr Gbyliczek
Systems Administrator (LPIC 3, Novell CLA certified)
Reconnix Ltd
T: 0845 421 0444