Control: severity -1 important
On Mon, 2020-02-24 at 16:01 +0100, Elimar Riesebieter wrote:
> Control: found -1 1.3.4-2.5
> Control: severity -1 grave
>
> Hi all,
>
> this bug causes kernel panics at least on i386 and x86-64 running
> nfsv4 servers so set severity to grave.
[...]
This bug is as
Control: found -1 1.3.4-2.5
Control: severity -1 grave
Hi all,
this bug causes kernel panics at least on i386 and x86-64 running
nfsv4 servers so set severity to grave.
* Hieu Luu [2017-09-26 21:24 +0700]:
> Hello Stephen,
>
> I was able to resolve this by following these steps (after doing s
Thanks Hieu,
I can confirm that the suggested workaround does remove the error message.
Maintainers, it may be sufficient to follow these steps to initialize
the database if it is not present during package install.
Stephen
Hello Stephen,
I was able to resolve this by following these steps (after doing strace
nfsdcltrack init to find out why it returned -13) **[1]**
1. `# mkdir /var/lib/nfs/nfsdcltrack`
2. `# nfsdcltrack init`
3. check if file `/var/lib/nfs/nfsdcltrack/main.sqlite` is present
4. check with `sqlit
4 matches
Mail list logo
