← Back to team overview

ubuntu-bugcontrol team mailing list archive

[Bug 530541] Re: desktopcouch-service crashed with RuntimeError in run_couchdb()

 

I don't know if this means anything to anybody, but...

I was just looking at my 'apport' logs and one of them says:

apport (pid 1588) Thu Apr  8 23:37:14 2010: called for pid 1386, signal 6
apport (pid 1588) Thu Apr  8 23:37:14 2010: script: /usr/lib/desktopcouch/desktopcouch-service, interpreted by /usr/bin/python2.6 (command line "/usr/bin/python /usr/lib/desktopcouch/desktopcouch-service")
apport (pid 1588) Thu Apr  8 23:37:14 2010: this executable already crashed 2 times, ignoring
apport (pid 1853) Fri Apr  9 21:57:51 2010: called for pid 1670, signal 6
apport (pid 1853) Fri Apr  9 21:57:51 2010: script: /usr/lib/desktopcouch/desktopcouch-service, interpreted by /usr/bin/python2.6 (command line "/usr/bin/python /usr/lib/desktopcouch/desktopcouch-service")
apport (pid 1853) Fri Apr  9 21:57:55 2010: wrote report /var/crash/_usr_lib_desktopcouch_desktopcouch-service.1000.crash
apport (pid 1544) Fri Apr  9 22:13:34 2010: called for pid 1358, signal 6
apport (pid 1544) Fri Apr  9 22:13:34 2010: script: /usr/lib/desktopcouch/desktopcouch-service, interpreted by /usr/bin/python2.6 (command line "/usr/bin/python /usr/lib/desktopcouch/desktopcouch-service")
apport (pid 1544) Fri Apr  9 22:13:34 2010: this executable already crashed 2 times, ignoring
apport (pid 1829) Sat Apr 10 00:20:05 2010: called for pid 1641, signal 6
apport (pid 1829) Sat Apr 10 00:20:06 2010: script: /usr/lib/desktopcouch/desktopcouch-service, interpreted by /usr/bin/python2.6 (command line "/usr/bin/python /usr/lib/desktopcouch/desktopcouch-service")
apport (pid 1829) Sat Apr 10 00:20:06 2010: this executable already crashed 2 times, ignoring

As you can see -- after deleting the pid file -- everything was okay for
approx 24 hrs... then back to the same old/same old...

-- 
desktopcouch-service crashed with RuntimeError in run_couchdb()
https://bugs.launchpad.net/bugs/530541
You received this bug notification because you are a member of Ubuntu
Bug Control, which is a subscriber of a duplicate bug.