Bug 1216880 - [abrt] vdsm: __init__.py:936:_open:IOError: [Errno 6] No such device or address: '/dev/stdout'
Summary: [abrt] vdsm: __init__.py:936:_open:IOError: [Errno 6] No such device or addre...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: Core
Version: 4.16.14
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.1.7
: 4.19.35
Assignee: Yaniv Bronhaim
QA Contact: Pavol Brilla
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-29 06:40 UTC by blachniom
Modified: 2019-04-28 13:12 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-13 12:26:45 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.1+


Attachments (Terms of Use)
File: backtrace (710 bytes, text/plain)
2015-04-29 06:40 UTC, blachniom
no flags Details
File: environ (123 bytes, text/plain)
2015-04-29 06:40 UTC, blachniom
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 80231 0 master MERGED Handling fatal fail in supervdsm when log conf is invalid 2020-12-13 12:42:06 UTC
oVirt gerrit 82787 0 None MERGED Handling fatal fail in supervdsm when log conf is invalid 2020-12-13 12:42:08 UTC

Description blachniom 2015-04-29 06:40:00 UTC
Description of problem:
I issued 'service libvirtd restart'

Version-Release number of selected component:
vdsm-4.16.14-0.fc21

Additional info:
reporter:       libreport-2.3.0
cmdline:        /usr/bin/python /usr/share/vdsm/supervdsmServer --sockfile /var/run/vdsm/svdsm.sock
dso_list:       python-libs-2.7.8-9.fc21.x86_64
executable:     /usr/share/vdsm/supervdsmServer
kernel:         3.19.5-200.fc21.x86_64
runlevel:       N 5
type:           Python
uid:            0

Truncated backtrace:
__init__.py:936:_open:IOError: [Errno 6] No such device or address: '/dev/stdout'

Traceback (most recent call last):
  File "/usr/share/vdsm/supervdsmServer", line 43, in <module>
    level=logging.DEBUG)
  File "/usr/lib64/python2.7/logging/__init__.py", line 1540, in basicConfig
    hdlr = FileHandler(filename, mode)
  File "/usr/lib64/python2.7/logging/__init__.py", line 911, in __init__
    StreamHandler.__init__(self, self._open())
  File "/usr/lib64/python2.7/logging/__init__.py", line 936, in _open
    stream = open(self.baseFilename, self.mode)
IOError: [Errno 6] No such device or address: '/dev/stdout'

Local variables in innermost frame:
self: <logging.FileHandler object at 0x7f25aaecf310>

Comment 1 blachniom 2015-04-29 06:40:03 UTC
Created attachment 1019984 [details]
File: backtrace

Comment 2 blachniom 2015-04-29 06:40:05 UTC
Created attachment 1019985 [details]
File: environ

Comment 3 Yaniv Bronhaim 2015-06-11 20:45:55 UTC
environment issue - not a bug. can't understand how it happened, if someone can explain from the attached info please do..

Comment 4 Pavol Brilla 2017-10-25 10:35:20 UTC
Installed Packages
vdsm.x86_64         4.19.35-1.el7.centos            @ovirt-4.1-pre

Comment 5 Pavol Brilla 2017-10-25 12:26:19 UTC
Oct 25 06:33:31 host.brilla systemd[1]: Starting Auxiliary vdsm service for running helper functions as root...
-- Subject: Unit supervdsmd.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit supervdsmd.service has begun starting up.
Oct 25 06:33:31 host.brilla supervdsmServer[2989]: Supervdsm failed to start: No section: 'loggers'
Oct 25 06:33:31 host.brilla python2[2989]: detected unhandled Python exception in '/usr/share/vdsm/supervdsmServer'
Oct 25 06:33:31 host.brilla daemonAdapter[2989]: Traceback (most recent call last):
Oct 25 06:33:31 host.brilla daemonAdapter[2989]: File "/usr/share/vdsm/supervdsmServer", line 351, in <module>
Oct 25 06:33:31 host.brilla daemonAdapter[2989]: main(**argDict)
Oct 25 06:33:31 host.brilla daemonAdapter[2989]: File "/usr/share/vdsm/supervdsmServer", line 248, in main
Oct 25 06:33:31 host.brilla daemonAdapter[2989]: raise FatalError("Cannot configure logging: %s" % e)
Oct 25 06:33:31 host.brilla daemonAdapter[2989]: __main__.FatalError: Cannot configure logging: No section: 'loggers'
Oct 25 06:33:31 host.brilla systemd[1]: supervdsmd.service: main process exited, code=exited, status=1/FAILURE
Oct 25 06:33:31 host.brilla systemd[1]: Unit supervdsmd.service entered failed state.
Oct 25 06:33:31 host.brilla systemd[1]: supervdsmd.service failed.
Oct 25 06:33:31 host.brilla systemd[1]: supervdsmd.service holdoff time over, scheduling restart.
Oct 25 06:33:31 host.brilla systemd[1]: start request repeated too quickly for supervdsmd.service
Oct 25 06:33:31 host.brilla systemd[1]: Failed to start Auxiliary vdsm service for running helper functions as root.
-- Subject: Unit supervdsmd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit supervdsmd.service has failed.
-- 
-- The result is failed.

Comment 6 Pavol Brilla 2017-10-25 12:26:41 UTC
error message is now readable


Note You need to log in before you can comment on or make changes to this bug.