On Wed, 20 Apr 2005, Lydia Heck wrote:
> On our CE we get messages of the floowing ....
>
>
> Apr 20 14:05:51 swainby rpc.mountd: authenticated mount request from
> wn10.dur.scotgrid.ac.uk:969 for /export/home (/export/home)
> Apr 20 14:05:52 nod ypserv[2506]: refused connect from
> 129.234.193.30:33087 to procedure ypproc_match
Just to be sure: the previous two messages do not concern this list.
The next message, however, really boils down to a kernel misfeature
that has been complained about with RedHat, as Steve said.
Apart from spamming /var/log/messages the issue is harmless.
> (ippp_grid,shadow.byname;-1) Apr 20 14:05:52 helmsley kernel: application
> bug: edg-gridftpd(4937) has SIGCHLD set to SIG_IGN but calls wait().
> Apr 20 14:05:52 helmsley kernel: (see the NOTES section of 'man 2 wait').
> Workaround activated.
>
>
> ~~~~~~~~~~~~~~~~~~~~~~
> Is there an update to edg-gridftpd, which removes this "warning"?
No, and nothing is planned either. RedHat should fix the kernel.
> Apr 20 14:05:52 helmsley gridftpd[14846]:
> 2005-04-20.14:05:52.939734.0000014846.0000000778 : LCAS authorization
> request
> Apr 20 14:05:52 helmsley gridftpd[14846]:
> 2005-04-20.14:05:52.947624.0000014846.0000000778 : LCMAPS credential
> mapping request
> Apr 20 14:05:52 helmsley gridftpd[14846]: GSSAPI user
> /C=UK/O=eScience/OU=QueenMaryLondon/L=Physics/CN=dave kant is authorized
> as dteam001
> Apr 20 14:05:52 helmsley gridftpd[14846]:
> 2005-04-20.14:05:52.984804.0000014846.0000000778 : LCMAPS credential
> mapping request
> Apr 20 14:05:53 helmsley gridftpd[14846]:
> 2005-04-20.14:05:52.984804.0000014846.0000000778 :
> lcmaps_plugin_posix_enf-log_cred(): uid=60204(dteam001):pgid=1226(dteam)
> Apr 20 14:05:53 helmsley gridftpd[14846]: cannot open pid file
> /var/run/ftp.pids-all: Permission denied
>
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> I have checked the permissions on /var/run and /var/run/ftp.pids-all
> to be
> drwxr-xr-x on /var/run owned by root
> and
> rw-r--r-- on /var/run/ftp.pids-all
> owned by root.
>
> So the pid file (a) exists and is modified at the time where the
> permission denied report is given
>
> any suggestions ?
The process tries to modify the file when it is no longer running as root,
but as the (pool) user to which the DN is mapped. Apart from spamming
the logfile this issue is harmless (now where did I recently read that?).
You could open a bug about it, but we will not consider it high priority.
|