[root@localhost ~]# service abrtd stop Stopping abrt daemon: [FAILED] [root@localhost ~]# service abrtd start Starting abrt daemon: [ OK ] [root@localhost ~]# service abrtd status abrt dead but pid file exists [root@localhost ~]# service abrtd stop Stopping abrt daemon: [FAILED] [root@localhost ~]# service abrtd status abrt dead but pid file exists [root@localhost ~]# tail -n 20 /var/log/messages Jan 12 14:49:05 localhost abrtd: Plugin Bugzilla (0.0.4) succesfully loaded Jan 12 14:49:05 localhost abrtd: Plugin Kerneloops (0.0.2) succesfully loaded Jan 12 14:49:05 localhost abrtd: Plugin RunApp (0.0.1) succesfully loaded Jan 12 14:49:05 localhost abrtd: Plugin SQLite3 (0.0.2) succesfully loaded Jan 12 14:49:05 localhost abrtd: Plugin CCpp (0.0.1) succesfully loaded Jan 12 14:49:05 localhost abrtd: Plugin Logger (0.0.1) succesfully loaded Jan 12 14:49:05 localhost abrtd: Plugin KerneloopsReporter (0.0.1) succesfully loaded Jan 12 14:49:05 localhost abrtd: Plugin Python (0.0.1) succesfully loaded Jan 12 14:49:05 localhost abrtd: Plugin KerneloopsScanner (0.0.1) succesfully loaded Jan 12 14:49:05 localhost abrtd: Registered plugin Bugzilla(Reporter) Jan 12 14:49:05 localhost abrtd: warning: /proc/sys/kernel/core_pattern already contains |/usr/libexec/abrt-hook-ccpp /var/cache/abrt %p %s %u %c, did abrt daemon crash recently? Jan 12 14:49:05 localhost abrtd: Registered plugin CCpp(Analyzer) Jan 12 14:49:05 localhost abrtd: Registered plugin Kerneloops(Analyzer) Jan 12 14:49:05 localhost abrtd: Registered plugin KerneloopsReporter(Reporter) Jan 12 14:49:05 localhost abrtd: Registered plugin KerneloopsScanner(Action) Jan 12 14:49:05 localhost abrtd: Registered plugin Logger(Reporter) Jan 12 14:49:05 localhost abrtd: Registered plugin Python(Analyzer) Jan 12 14:49:05 localhost abrtd: Registered plugin RunApp(Action) Jan 12 14:49:05 localhost abrtd: Registered plugin SQLite3(Database) Jan 12 14:49:05 localhost abrtd: Can't read lock file '/var/cache/abrt/pyhook-1259610056-28257.lock': Invalid argument [root@localhost ~]# rpm -qa 'abrt*' abrt-addon-python-1.0.3-1.fc12.i686 abrt-plugin-bugzilla-1.0.3-1.fc12.i686 abrt-addon-ccpp-1.0.3-1.fc12.i686 abrt-gui-1.0.3-1.fc12.i686 abrt-1.0.3-1.fc12.i686 abrt-plugin-runapp-1.0.3-1.fc12.i686 abrt-libs-1.0.3-1.fc12.i686 abrt-plugin-logger-1.0.3-1.fc12.i686 abrt-desktop-1.0.3-1.fc12.i686 abrt-addon-kerneloops-1.0.3-1.fc12.i686 [root@localhost ~]# 1: "service abrt stop" should remove pid file 2: a problem with one "coredump" should never cause the service to stop running 3: if an error is fatal and causes the daemon to die then please log it as such 4: abrtd logs a lot by default (which might be another problem), but a line telling that it is starting would be very helpful.
Please rm -rf /var/cache/abrt, it contains old-style lock files. Newer version of abrt doesn't understand old locks.
Yes, removing just the lock file worked around the problem, but still, abrt shouldn't choke on old locks like that.
(In reply to comment #2) > Yes, removing just the lock file worked around the problem, but still, abrt > shouldn't choke on old locks like that. hi, I was having the same issue almost [root@localhost abrt]# service abrtd restart Stopping abrt daemon: [FAILED] Starting abrt daemon: [ OK ] [root@localhost abrt]# service abrtd status abrt dead but pid file exists removing the /var/cache/abrt looks like it solved the problem. I got this in my /var/log/messages | grep abrtd Jan 31 20:45:48 localhost abrtd: Registered Analyzer plugin 'Python' Jan 31 20:45:48 localhost abrtd: Registered Action plugin 'KerneloopsScanner' Jan 31 20:45:48 localhost abrtd: Registered Reporter plugin 'Logger' Jan 31 20:45:48 localhost abrtd: Registered Analyzer plugin 'Kerneloops' Jan 31 20:45:48 localhost abrtd: Registered Reporter plugin 'KerneloopsReporter' Jan 31 20:45:48 localhost abrtd: warning: /proc/sys/kernel/core_pattern already contains |/usr/libexec/abrt-hook-ccpp /var/cache/abrt %p %s %u %c, did abrt daemon crash recently? Jan 31 20:45:48 localhost abrtd: Registered Analyzer plugin 'CCpp' Jan 31 20:45:48 localhost abrtd: Registered Reporter plugin 'Bugzilla' Jan 31 20:45:48 localhost abrtd: Registered Database plugin 'SQLite3' Jan 31 20:45:49 localhost abrtd: can't load '/usr/lib64/abrt/lib.so': /usr/lib64/abrt/lib.so: cannot open shared object file: No such file or directory There is no lib.so there.. i checked. regards, Ankur
(In reply to comment #3) > I was having the same issue almost ... > Jan 31 20:45:49 localhost abrtd: can't load '/usr/lib64/abrt/lib.so': > /usr/lib64/abrt/lib.so: cannot open shared object file: No such file or > directory Ankur, that is probably a completely different problem - which just happens to trig the same error handling. I suggest you file a new bug and include the output of rpm -qa '*abrt*' rpm -qaV '*abrt*'
> Jan 31 20:45:48 localhost abrtd: Registered Reporter plugin 'Bugzilla' > Jan 31 20:45:48 localhost abrtd: Registered Database plugin 'SQLite3' > Jan 31 20:45:49 localhost abrtd: can't load '/usr/lib64/abrt/lib.so': > /usr/lib64/abrt/lib.so: cannot open shared object file: No such file or > directory Hi Ankur, Did you build abrt from source (as opposed to installing a prebuilt rpm)? If yes, with which configure/make options did you do it?
(In reply to comment #5) > > Jan 31 20:45:48 localhost abrtd: Registered Reporter plugin 'Bugzilla' > > Jan 31 20:45:48 localhost abrtd: Registered Database plugin 'SQLite3' > > Jan 31 20:45:49 localhost abrtd: can't load '/usr/lib64/abrt/lib.so': > > /usr/lib64/abrt/lib.so: cannot open shared object file: No such file or > > directory > > Hi Ankur, > > Did you build abrt from source (as opposed to installing a prebuilt rpm)? If > yes, with which configure/make options did you do it? hi, i havent built any rpms myself for abrt. whatever is on my system came from regular updates from official fedora repos. Ive filed a new bug here https://bugzilla.redhat.com/show_bug.cgi?id=560642 regards, Ankur
*** This bug has been marked as a duplicate of bug 560642 ***