Fedora Account System
Red Hat Associate
Red Hat Customer
Version-Release number of selected component: flumotion-0.10.0-7.fc20 Additional info: reporter: libreport-2.2.3 cmdline: /usr/bin/python /usr/sbin/flumotion -C /tmp/tmpOs9a0d.flumotion/etc -L /tmp/tmpOs9a0d.flumotion/var/log -R /tmp/tmpOs9a0d.flumotion/var/run stop worker admin executable: /usr/sbin/flumotion kernel: 3.17.7-200.fc20.x86_64 runlevel: N 5 type: Python uid: 1000 Truncated backtrace: service.py:88:_parseManagersWorkers:FatalError: No worker with name admin Traceback (most recent call last): File "/usr/sbin/flumotion", line 58, in <module> _run_main(PROGRAM_PATH) File "/usr/sbin/flumotion", line 51, in _run_main sys.exit(main(sys.argv)) File "/usr/lib64/flumotion/python/flumotion/service/main.py", line 83, in main return servicer.stop(args[2:]) File "/usr/lib64/flumotion/python/flumotion/service/service.py", line 183, in stop (managers, workers) = self._parseManagersWorkers('stop', args) File "/usr/lib64/flumotion/python/flumotion/service/service.py", line 88, in _parseManagersWorkers raise errors.FatalError, 'No worker with name %s' % name FatalError: No worker with name admin Local variables in innermost frame: managers: [] name: 'admin' workers: [] args: ['worker', 'admin'] command: 'stop' which: 'worker' self: <flumotion.service.service.Servicer instance at 0x1529320> Potential duplicate: bug 904680
Created attachment 991442 [details] File: backtrace
Created attachment 991443 [details] File: environ
*** This bug has been marked as a duplicate of bug 880366 ***