Re: [ovirt-users] supervdsmd IOError to /dev/stdout

2017-08-03 Thread Richard Chan
Did it change the file permissions when you copied svdsm.logger.conf.rpmnew? No, the file permission were the same root:root 0644 Yes reproducible with 3.6 config file - it is definitely due to the 3.6 svdsm.logger.conf: when I copied the rpmnew file from 4.1, it works again.

Re: [ovirt-users] supervdsmd IOError to /dev/stdout

2017-08-02 Thread Yaniv Bronheim
Did it change the file permissions when you copied svdsm.logger.conf.rpmnew? can you reproduce it? On Tue, Aug 1, 2017 at 3:06 PM Richard Chan wrote: > Hi, > > Could this be the cause of the access issue (old system upgraded from 3.4 > all the way to 4.1)? > ##

Re: [ovirt-users] supervdsmd IOError to /dev/stdout

2017-08-01 Thread Nir Soffer
On Tue, Aug 1, 2017 at 3:07 PM Richard Chan wrote: > Hi, > > Could this be the cause of the access issue (old system upgraded from 3.4 > all the way to 4.1)? > ## change in python class name?? > > [handler_logfile] > -class=logUtils.UserGroupEnforcingHandler >

Re: [ovirt-users] supervdsmd IOError to /dev/stdout

2017-08-01 Thread Richard Chan
Hi, Could this be the cause of the access issue (old system upgraded from 3.4 all the way to 4.1)? ## change in python class name?? [handler_logfile] -class=logUtils.UserGroupEnforcingHandler +class=vdsm.logUtils.UserGroupEnforcingHandler When I copied svdsm.logger.conf.rpmnew over

Re: [ovirt-users] supervdsmd IOError to /dev/stdout

2017-08-01 Thread Yaniv Bronheim
Hi, Seems like I already bumped in such issue awhile ago - https://bugzilla.redhat.com/show_bug.cgi?id=1216880 but now I see what's wrong - it happens after failing to read /etc/vdsm/svdsm.logger.conf for some reason then we have a bug in our fallback which tries to run

Re: [ovirt-users] supervdsmd IOError to /dev/stdout

2017-07-30 Thread Richard Chan
Hi Yaniv, On this one node, it happened from 3.6 -> 4.0. It persisted after 4.0->4.1. Current: vdsm-4.19.24-1.el7.centos.x86_64 In systemd override I now have to have: StandardOutput=null Jul 29 01:19:21 systemd[1]: Starting Auxiliary vdsm service for running helper functions as

Re: [ovirt-users] supervdsmd IOError to /dev/stdout

2017-07-30 Thread Yaniv Kaul
On Fri, Jul 28, 2017 at 8:37 PM, Richard Chan wrote: > After an upgrade to 4.0 I have a single host that cannot start supervdsmd > because of IOError on /dev/stdout. All other hosts upgraded correctly. > Upgrade from which version? 3.6? Did you stay on 4.0 or

[ovirt-users] supervdsmd IOError to /dev/stdout

2017-07-28 Thread Richard Chan
After an upgrade to 4.0 I have a single host that cannot start supervdsmd because of IOError on /dev/stdout. All other hosts upgraded correctly. In the systemd unit I have to hack StandardOutput=null. Any thing I have overlooked? The hosts are all identical and it is just this one that has this