Re: New kernel errors after last update, Fedora 33

On 26/02/2021 16:48, Jerome Lille wrote: On Thu, 2021-02-25 at 13:19 -0400, George N. White III wrote: On Sun, 21 Feb 2021 at 12:46, Jerome Lille wrote: I tried to simply change type from nfs to nfs4 in the fstab in the client. Unfortunately I then get the response mount.nfs4: access denied b

Re: New kernel errors after last update, Fedora 33

On Thu, 2021-02-25 at 13:19 -0400, George N. White III wrote: > On Sun, 21 Feb 2021 at 12:46, Jerome Lille > wrote: > > I tried to simply change type from nfs to nfs4 in the fstab in the > > client. Unfortunately I then get the response > > > > mount.nfs4: access denied by server while mounting

Re: New kernel errors after last update, Fedora 33

On 26/02/2021 07:38, George N. White III wrote: So, I still can't find a way to duplicate the OP's problem without specifically changing a config file. There is always the possibility of some "invisible character" error in a config file. The OP has said he hadn't modified any config f

Re: New kernel errors after last update, Fedora 33

On Thu, 25 Feb 2021 at 18:11, Ed Greshko wrote: > On 26/02/2021 04:21, George N. White III wrote: > > On Thu, 25 Feb 2021 at 14:03, Ed Greshko > wrote: > > > > On 26/02/2021 01:19, George N. White III wrote: > > > I haven't used CentOS7 for several years, s

Re: New kernel errors after last update, Fedora 33

On 26/02/2021 04:21, George N. White III wrote: On Thu, 25 Feb 2021 at 14:03, Ed Greshko mailto:ed.gres...@greshko.com>> wrote: On 26/02/2021 01:19, George N. White III wrote: > I haven't used CentOS7 for several years, so I was ignoring this > thread in the hope others could answer.

Re: New kernel errors after last update, Fedora 33

On Thu, 25 Feb 2021 at 14:03, Ed Greshko wrote: > On 26/02/2021 01:19, George N. White III wrote: > > I haven't used CentOS7 for several years, so I was ignoring this > > thread in the hope others could answer. > > > > My not very trustworthy memory is that "/etc/exports" on > > the server needs

Re: New kernel errors after last update, Fedora 33

On 26/02/2021 01:19, George N. White III wrote: I haven't used CentOS7 for several years, so I was ignoring this thread in the hope others could answer. My not very trustworthy memory is that "/etc/exports" on the server needs the "insecure" option for NFS4 to work, see: https://access.redhat.co

Re: New kernel errors after last update, Fedora 33

On Sun, 21 Feb 2021 at 12:46, Jerome Lille wrote: > I tried to simply change type from nfs to nfs4 in the fstab in the > client. Unfortunately I then get the response > > mount.nfs4: access denied by server while mounting ... > > There is nothing in the server logs about this. And it is not the >

Re: New kernel errors after last update, Fedora 33

On Thu, 2021-02-25 at 07:40 +0800, Ed Greshko wrote: > > Well, I'm sorry but I'm out of ideas. > > I can mount file systems hosted on a Centos7 server from an F33 > client with no problems with nfsv4. > I can't figure out how to create the problems you're seeing without > modification to configur

Re: New kernel errors after last update, Fedora 33

On 24/02/2021 22:22, Jerome Lille wrote: On Wed, 2021-02-24 at 05:41 +0800, Ed Greshko wrote: What is the output of cat /run/sysconfig/nfs-utils RPCNFSDARGS=" " RPCMOUNTDARGS="" STATDARGS="" SMNOTIFYARGS="" RPCIDMAPDARGS="" GSSDARGS="" BLKMAPDARGS="" GSS_USE_PROXY="yes" Oh, also, do you happ

Re: New kernel errors after last update, Fedora 33

On Wed, 2021-02-24 at 05:41 +0800, Ed Greshko wrote: > > What is the output of > > cat /run/sysconfig/nfs-utils RPCNFSDARGS=" " RPCMOUNTDARGS="" STATDARGS="" SMNOTIFYARGS="" RPCIDMAPDARGS="" GSSDARGS="" BLKMAPDARGS="" GSS_USE_PROXY="yes" > Oh, also, do you happen to have a /etc/nfs.conf.d direc

Re: New kernel errors after last update, Fedora 33

On 24/02/2021 05:41, Ed Greshko wrote: That polkitd message occurs here as well.  So, not an issue. What is the output of cat /run/sysconfig/nfs-util Oh, also, do you happen to have a /etc/nfs.conf.d directory? -- People who believe they don't make mistakes have already made one. __

Re: New kernel errors after last update, Fedora 33

On 24/02/2021 04:41, Jerome Lille wrote: On Wed, 2021-02-24 at 02:38 +0800, Ed Greshko wrote: The other way to disable NFSv4 is to modify /etc/sysconfig/nfs to have the line # Optional arguments passed to rpc.nfsd. See rpc.nfsd(8) RPCNFSDARGS="--no-nfs-version 4" You should check that as well.

Re: New kernel errors after last update, Fedora 33

On Wed, 2021-02-24 at 02:38 +0800, Ed Greshko wrote: > > The other way to disable NFSv4 is to modify /etc/sysconfig/nfs to > have the line > > # Optional arguments passed to rpc.nfsd. See rpc.nfsd(8) > RPCNFSDARGS="--no-nfs-version 4" > > You should check that as well. > > Bottom line, NFSv4 is

Re: New kernel errors after last update, Fedora 33

On 24/02/2021 00:27, Jerome Lille wrote: On Tue, 2021-02-23 at 23:16 +0800, Ed Greshko wrote: [mountd] debug=all And then restart the server. After doing the mount from the client, check the journal for rpc.mountd messages. Ok, what I got when doing 'mount -v server:/path /path' (i.e. it trie

Re: New kernel errors after last update, Fedora 33

On Tue, 2021-02-23 at 23:16 +0800, Ed Greshko wrote: > [mountd] > debug=all > > And then restart the server. > > After doing the mount from the client, check the journal for rpc.mountd > messages. Ok, what I got when doing 'mount -v server:/path /path' (i.e. it tried v4 first then succeeded on v

Re: New kernel errors after last update, Fedora 33

On 23/02/2021 21:58, Jerome Lille wrote: On Tue, 2021-02-23 at 04:37 +0800, Ed Greshko wrote: On 23/02/2021 00:27, Jerome Lille wrote: My nfs.conf is untouched. You do mean that file on the nfs server side, right? Exactly OK Modify that file to have # [mountd] debug=all And then

Re: New kernel errors after last update, Fedora 33

On Tue, 2021-02-23 at 04:37 +0800, Ed Greshko wrote: > On 23/02/2021 00:27, Jerome Lille wrote: > > My nfs.conf is untouched. > > You do mean that file on the nfs server side, right? Exactly > > When I do the following command > > mount -v server:/path /path > > > > I get the following > > I

Re: New kernel errors after last update, Fedora 33

On 23/02/2021 00:27, Jerome Lille wrote: On Mon, 2021-02-22 at 08:39 +0800, Ed Greshko wrote: On 22/02/2021 08:24, Ed Greshko wrote:  have not made any changes to the nfs server configuration file /etc/ nfs.conf so the defaults are in effect. # vers2=n # vers3=y # vers4=y # vers4.0=y # vers4.

Re: New kernel errors after last update, Fedora 33

On Mon, 2021-02-22 at 08:39 +0800, Ed Greshko wrote: > On 22/02/2021 08:24, Ed Greshko wrote: > >  have not made any changes to the nfs server configuration file /etc/ > > nfs.conf so the defaults are > > in effect. > > > > # vers2=n > > # vers3=y > > # vers4=y > > # vers4.0=y > > # vers4.1=y > >

Re: New kernel errors after last update, Fedora 33

On 22/02/2021 08:24, Ed Greshko wrote:  have not made any changes to the nfs server configuration file /etc/nfs.conf  so the defaults are in effect. # vers2=n # vers3=y # vers4=y # vers4.0=y # vers4.1=y # vers4.2=y Check to make sure these haven't been altered. FWIW, I did do a test and modi

Re: New kernel errors after last update, Fedora 33

On 22/02/2021 00:46, Jerome Lille wrote: I tried to simply change type from nfs to nfs4 in the fstab in the client. Unfortunately I then get the response mount.nfs4: access denied by server while mounting ... There is nothing in the server logs about this. And it is not the firewall, because ev

Re: New kernel errors after last update, Fedora 33

On Thu, 2021-02-18 at 14:23 -0800, Gordon Messmer wrote: > On 2/18/21 8:38 AM, Jerome Lille wrote: > > But as I said the nfs shares seem to work fine, I can read and > > write to > > files on them. > > > Yep, everything will look fine until an application on your client > tries > to lock a file,

Re: New kernel errors after last update, Fedora 33

On 2/18/21 8:38 AM, Jerome Lille wrote: But as I said the nfs shares seem to work fine, I can read and write to files on them. Yep, everything will look fine until an application on your client tries to lock a file, and then it will hang forever. Locking files during editing is pretty common

Re: New kernel errors after last update, Fedora 33

On 19/02/2021 00:38, Jerome Lille wrote: On Thu, 2021-02-18 at 07:43 +0800, Ed Greshko wrote: On 18/02/2021 03:07, Jerome Lille wrote: 192.168.1.101 is the IP of my local NFS server (Centos7), my Fedora desktop that produces these error messages has some shares from it mounted. No errors on the

Re: New kernel errors after last update, Fedora 33

On Thu, 2021-02-18 at 07:43 +0800, Ed Greshko wrote: > On 18/02/2021 03:07, Jerome Lille wrote: > > 192.168.1.101 is the IP of my local NFS server (Centos7), my Fedora > > desktop that produces these error messages has some shares from it > > mounted. No errors on the NFS server and the nfs shares

Re: New kernel errors after last update, Fedora 33

On 18/02/2021 03:07, Jerome Lille wrote: 192.168.1.101 is the IP of my local NFS server (Centos7), my Fedora desktop that produces these error messages has some shares from it mounted. No errors on the NFS server and the nfs shares seems to work fine. Are you using NFSv3 or NFSv4 to mount the s

Re: New kernel errors after last update, Fedora 33

On Wed, Feb 17, 2021 at 12:08 PM Jerome Lille wrote: > Thanks for the suggestion. I did get more logging > > RPC: 5d78dc3a connect status 107 connected 0 sock state 7 > xs_tcp_setup_socket: connect returned unhandled error -107 > RPC: xs_tcp_state_change client 5d78dc3a

Re: New kernel errors after last update, Fedora 33

On Wed, 2021-02-17 at 11:43 -0700, Jerry James wrote: > On Wed, Feb 17, 2021 at 10:33 AM Jerome Lille > wrote: > > After the latest update there are some errors in the log that I > > haven't > > seen before. > > > > kernel: xs_tcp_setup_socket: connect returned unhandled error -107 > > > > There

Re: New kernel errors after last update, Fedora 33

On Wed, Feb 17, 2021 at 10:33 AM Jerome Lille wrote: > After the latest update there are some errors in the log that I haven't > seen before. > > kernel: xs_tcp_setup_socket: connect returned unhandled error -107 > > There are two of those per minute continuously. I haven't noticed any > other pro

Re: New kernel errors after last update, Fedora 33

On Wed, 17 Feb 2021 10:10:23 -0800 Clifford Snow wrote: > I'm running 5.10.15-200.fc33.x86_64 and have not seen those errors. Same here. Sounds like some application is running that causes that error and I'm not running that app. ___ users mailing list

Re: New kernel errors after last update, Fedora 33

I'm running 5.10.15-200.fc33.x86_64 and have not seen those errors. On Wed, Feb 17, 2021 at 9:34 AM Jerome Lille wrote: > After the latest update there are some errors in the log that I haven't > seen before. > > kernel: xs_tcp_setup_socket: connect returned unhandled error -107 > > There are tw

New kernel errors after last update, Fedora 33

After the latest update there are some errors in the log that I haven't seen before. kernel: xs_tcp_setup_socket: connect returned unhandled error -107 There are two of those per minute continuously. I haven't noticed any other problems with the system, but wondering about those messages are abou