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 d
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
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
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
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
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
> >
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
> >
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 cl
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 serv
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_sock
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
On Sun, 2021-01-10 at 15:44 +0800, Ed Greshko wrote:
> On 06/01/2021 00:10, Jerome Lille wrote:
> > I've just updated a desktop from Fedora 32 to 33 and after that the
> > logs are flooded with the following message
> >
> > systemd-resolved[]: Using degraded featur
On Tue, 2021-01-05 at 18:10 -0500, Sam Varshavchik wrote:
> Chris Murphy writes:
>
> > On Tue, Jan 5, 2021 at 10:32 AM Chris Murphy
> > wrote:
> > >
> > > Maybe this bug:
> >
> > https://github.com/systemd/systemd/issues/13432
>
> "opened this issue on Aug 29, 2019"
>
> I would not expect thi
On Tue, 2021-01-05 at 10:33 -0700, Chris Murphy wrote:
> On Tue, Jan 5, 2021 at 10:32 AM Chris Murphy
> wrote:
> >
> > On Tue, Jan 5, 2021 at 9:10 AM Jerome Lille
> > wrote:
> > >
> > > Hi
> > >
> > > I've just updated a des
On Tue, 2021-01-05 at 11:37 -0500, Tim Evans wrote:
> On 1/5/21 11:10 AM, Jerome Lille wrote:
>
> > This machine uses a VPN service that is always on. The file
> > /etc/resolver.conf has just one line with the nameserver from the
> > VPN
>
> You do mean /
Hi
I've just updated a desktop from Fedora 32 to 33 and after that the
logs are flooded with the following message
systemd-resolved[]: Using degraded feature set TCP instead of UDP for
DNS server 127.0.0.1.
systemd-resolved[]: Using degraded feature set UDP instead of TCP for
DNS server 127.0.0.1
Hi
I'm wondering if anybody else has problems with Electrum when using a
tor proxy? I have version 4.0.7 on Fedora 33. The wallet stays offline
and I get following in the system logs
"Socks version 71 not recognized. (This port is not an HTTP proxy; did
you want to use HTTPTunnelPort?)"
The same
On Fri, 2020-12-18 at 20:14 +1030, Tim via users wrote:
> On Fri, 2020-12-18 at 08:57 +0100, Jerome Lille wrote:
> > I just thought it was strange that I couldn't do better than around
> > 1.5 tries per second. Even though I moved the target disk image
> > from
>
On Thu, 2020-12-17 at 21:15 +0100, Łukasz Posadowski wrote:
> Tue, 15 Dec 2020 22:23:50 +0100
> Jerome Lille :
>
> > I've got it now running. But I'm wondering if 1.5 password tries
> > per
> > second is normal? I've given it several threads, but it d
On Tue, 2020-12-15 at 23:32 +0800, Qiyu Yan wrote:
> Jerome Lille 于2020年12月15日周二 下午11:17写道：
> > Hi
> >
> > I just realized that I've forgotten the password to unlock my
> > laptop. I
> > haven't touched it since the beginning of the year. It has the
Hi
I just realized that I've forgotten the password to unlock my laptop. I
haven't touched it since the beginning of the year. It has the same
password for disc encryption, root and main user. I'm pretty sure about
the 4 first characters and then there should be four more characters
that I can't r
On Wed, 2020-09-16 at 11:24 -0700, Samuel Sieb wrote:
> On 9/16/20 9:29 AM, Jerome Lille wrote:
> > I've noticed in system log the following message popping up from
> > time
> > to time.
> >
> > gnome-shell[4119]: libinput error: event5 - Kingsis mouse
Hi
I've noticed in system log the following message popping up from time
to time.
gnome-shell[4119]: libinput error: event5 - Kingsis mouse: client bug:
event processing lagging behind by 21ms, your system is too slow
What should I do about? What is the actual problem? Is my mouse too old
and n
23 matches
Mail list logo
