SystemError: A manager service named 'default' is already running with pid 4368

Bug #345027 reported by aramil
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
flumotion (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: flumotion

.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/flumotion-manager
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: flumotion 0.4.2-3.1ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python /usr/bin/flumotion-manager -D --daemonize-to /var/cache/flumotion --service-name default /etc/flumotion/managers/default/planet.xml
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/flumotion-manager', '-D', '--daemonize-to', '/var/cache/flumotion', '--service-name', 'default', '/etc/flumotion/managers/default/planet.xml']
SourcePackage: flumotion
Title: flumotion-manager crashed with SystemError in daemonizeHelper()
Uname: Linux 2.6.28-10-generic x86_64
UserGroups:

Revision history for this message
aramil (starship-enterprise) wrote :
Steve Beattie (sbeattie)
Changed in flumotion (Ubuntu):
importance: Undecided → Medium
visibility: private → public
Revision history for this message
Loïc Minier (lool) wrote :

Could you please attach your /var/log/flumotion logs?

Revision history for this message
Loïc Minier (lool) wrote :

Did you start flumotion twice? Note that the package starts an instance for you already

Changed in flumotion (Ubuntu):
status: New → Incomplete
summary: - flumotion-manager crashed with SystemError in daemonizeHelper()
+ SystemError: A manager service named 'default' is already running with
+ pid 4368
Revision history for this message
Vish (vish) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future.
To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".

Changed in flumotion (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.