One of our colleagues ran into this with RHEL7.4 update. Our ganesha.nfsd
wasn't able to read our config files which are stored in /var directory. :-(
On Thu, Sep 14, 2017 at 9:47 PM, Daniel Gryniewicz <d...@redhat.com> wrote:
> As far as I know, this doesn't happen on Fedora, so it hasn't been
> reported anywhere.
>
> On Thu, Sep 14, 2017 at 6:58 AM, Niels de Vos <nde...@redhat.com> wrote:
> > On Wed, Sep 13, 2017 at 10:39:52AM +0200, Niels de Vos wrote:
> >> On Tue, Sep 12, 2017 at 06:41:49PM -0400, William Allen Simpson wrote:
> >> > On 9/12/17 6:06 PM, Frank Filz wrote:
> >> > > So this failure:
> >> > >
> >> > > https://ci.centos.org//job/nfs_ganesha_cthon04/1436/console
> >> > >
> >> > > Is an example of where we need some improvement. I looked at the
> top and
> >> > > scrolled down to the end. I have no idea why it failed. This is a
> case of
> >> > > too much information without a concise error report.
> >> > >
> >> > Installed:
> >> > libntirpc.x86_64 0:1.6.0-dev.7.el7.centos
> >> > nfs-ganesha.x86_64 0:2.6-dev.7.el7.centos
> >> > nfs-ganesha-gluster.x86_64 0:2.6-dev.7.el7.centos
> >> >
> >> > Complete!
> >> > + systemctl start nfs-ganesha
> >> > Job for nfs-ganesha.service failed because the control process exited
> with
> >> > error code. See "systemctl status nfs-ganesha.service" and
> "journalctl -xe"
> >> > for details.
> >> > Build step 'Execute shell' marked build as failure
> >> > Finished: FAILURE
> >> >
> >> > ===
> >> >
> >> > Why not print "systemctl status nfs-ganesha.service" and "journalctl
> -xe"?
> >> >
> >> > Originally I assumed that it was some obscure problem with my code,
> but
> >> > then I looked around, and it seems to be all the submissions for
> >> > nfs_ganesha_cthon04 at the moment....
> >>
> >> The additional information will now be logged as well. This change in
> >> the centos-ci branch does it:
> >>
> >> https://github.com/nfs-ganesha/ci-tests/pull/14/files
> >>
> >> A (manually started) test run logs the errors more clearly:
> >>
> >> https://ci.centos.org/job/nfs_ganesha_cthon04/1439/console
> >>
> >>
> >> Sep 13 09:33:41 n9.pufty.ci.centos.org bash[20711]: 13/09/2017
> 09:33:41 : epoch 59b8ed65 : n9.pufty.ci.centos.org :
> ganesha.nfsd-20711[main] create_log_facility :LOG :CRIT :Cannot create new
> log file (/var/log/ganesha/ganesha.log), because: Permission denied
> >> Sep 13 09:33:41 n9.pufty.ci.centos.org bash[20711]: 13/09/2017
> 09:33:41 : epoch 59b8ed65 : n9.pufty.ci.centos.org :
> ganesha.nfsd-20711[main] init_logging :LOG :FATAL :Create error (Permission
> denied) for FILE (/var/log/ganesha/ganesha.log) logging!
> >> Sep 13 09:33:41 n9.pufty.ci.centos.org systemd[1]:
> nfs-ganesha.service: control process exited, code=exited status=2
> >> Sep 13 09:33:41 n9.pufty.ci.centos.org systemd[1]: Failed to start
> NFS-Ganesha file server.
> >> Sep 13 09:33:41 n9.pufty.ci.centos.org systemd[1]: Unit
> nfs-ganesha.service entered failed state.
> >> Sep 13 09:33:41 n9.pufty.ci.centos.org systemd[1]: nfs-ganesha.service
> failed.
> >>
> >>
> >> Why creating the logfile fail is not clear to me. Maybe something in the
> >> packaging was changed and the /var/log/ganesha/ directory is not
> >> writable for the ganesha.nfsd process anymore? Have changes for running
> >> as non-root been merged, maybe?
> >
> > This seems to be a problem with the CentOS rebuild of RHEL-7.4. The
> > CentOS CI gets the new packages before the release is made available for
> > all users. I have run a test with SELinux in Permissive mode, and this
> > passed just fine.
> >
> > https://ci.centos.org/job/nfs_ganesha_cthon04/1445/consoleFull
> >
> > As a temporary (hopefully!) solution, doing a 'setenforce 0' in the
> > preparation script should help here:
> > https://github.com/nfs-ganesha/ci-tests/pull/15
> >
> > I would like to know if this problem has been reported against Fedora or
> > RHEL already. Once the bug is fixed in selinux-policy for RHEL, the
> > CentOS package will get an update soon after, and we can run our tests
> > with SELinux in Enforcing mode again.
> >
> > Thanks,
> > Niels
> >
> > ------------------------------------------------------------
> ------------------
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> > _______________________________________________
> > Nfs-ganesha-devel mailing list
> > Nfs-ganesha-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Nfs-ganesha-devel mailing list
> Nfs-ganesha-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
