Hi,
when booting I have a message
a start ob is running for de-disk-by\...
It takes one and half a minute until it gives up.
After googling I found that this is because of an entry in crypttab for
an encrypted disk that is not available at boot time. Actually it is a
external back-up disk that I only mount when needed and then remove again.
So I removed that entry from crypttab and next boot was fine, but
because of some magic the entry in crypttab appeares again and the boot
delay also happens again, of course.
That external disk isn't in fstab. I just plug it, wait for the notifier
to see it, click to attach it, enter the passphrase. Later I remove it
with that same notifier.
Why is an entry written to crypttab? Can I avoid that somehow?
Thanks for hints.
Daniel
Opensuse 15.1, KDE, all updated to current
--
Daniel Bauer photographer Basel Málaga
https://www.patreon.com/danielbauerhttps://www.daniel-bauer.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I was working at my desktop machine. My little server machine, media
server, was playing the internet radio with Kodi. I went to the kitchen to
put the dinner on the oven. On return, the media server had rebooted and
was asking for login.
There is no trace in the syslog:
<1.5> 2021-01-23T21:15:03.643324+01:00 Isengard Sistema - - - Logging the current external IP= (omitted)
<3.6> 2021-01-23T21:16:56.732717+01:00 Isengard systemd 1 - - Started Daily Cleanup of Snapper Snapshots.
<3.6> 2021-01-23T21:16:56.873624+01:00 Isengard dbus-daemon 1109 - - [system] Activating service name='org.opensuse.Snapper' requested by ':1.1048'
(uid=0 pid=5447 comm="/usr/lib/snapper/systemd-helper --cleanup ") (using servicehelper)
<3.6> 2021-01-23T21:16:57.131185+01:00 Isengard dbus-daemon 1109 - - [system] Successfully activated service 'org.opensuse.Snapper'
<3.6> 2021-01-23T21:21:56.728956+01:00 Isengard systemd 1 - - Starting Cleanup of Temporary Directories...
<3.5> 2021-01-23T21:21:56.875752+01:00 Isengard systemd-tmpfiles 5561 - - [/usr/lib/tmpfiles.d/net-snmp.conf:1] Line references path below legacy directory /var/run/, updating /var/run/net-snmp → /run/net-snmp; please update the tmpfiles.d/ drop-in file accordingly.
<3.5> 2021-01-23T21:21:56.879004+01:00 Isengard systemd-tmpfiles 5561 - - [/usr/lib/tmpfiles.d/radvd.conf:1] Line references path below legacy directory /var/run/, updating /var/run/radvd → /run/radvd; please update the tmpfiles.d/ drop-in file accordingly.
<3.5> 2021-01-23T21:21:56.879901+01:00 Isengard systemd-tmpfiles 5561 - - [/usr/lib/tmpfiles.d/samba.conf:1] Line references path below legacy directory /var/run/, updating /var/run/samba → /run/samba; please update the tmpfiles.d/ drop-in file accordingly.
<3.5> 2021-01-23T21:21:56.883365+01:00 Isengard systemd-tmpfiles 5561 - - [/usr/lib/tmpfiles.d/svnserve.conf:1] Line references path below legacy directory /var/run/, updating /var/run/svnserve → /run/svnserve; please update the tmpfiles.d/ drop-in file accordingly.
<3.5> 2021-01-23T21:21:56.887213+01:00 Isengard systemd-tmpfiles 5561 - - [/usr/lib/tmpfiles.d/tmp.conf:13] Duplicate line for path "/var/tmp", ignoring.
<3.5> 2021-01-23T21:21:56.888626+01:00 Isengard systemd-tmpfiles 5561 - - [/usr/lib/tmpfiles.d/var.conf:21] Duplicate line for path "/var/lib", ignoring.
<3.5> 2021-01-23T21:21:56.889240+01:00 Isengard systemd-tmpfiles 5561 - - [/usr/lib/tmpfiles.d/var.conf:23] Duplicate line for path "/var/spool", ignoring.
<3.6> 2021-01-23T21:21:56.965040+01:00 Isengard systemd 1 - - Started Cleanup of Temporary Directories.
<1.5> 2021-01-23T21:30:03.251921+01:00 Isengard Sistema - - - Logging the current external IP= (omitted)
<3.6> 2021-01-23T21:33:54.528052+01:00 Isengard smartd 1103 - - Device: /dev/sda [SAT], SMART Usage Attribute: 189 Airflow_Temperature_Cel changed from 41 to 46
<3.6> 2021-01-23T21:33:54.529239+01:00 Isengard smartd 1103 - - Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 41 to 46
<3.6> 2021-01-23T21:33:54.603175+01:00 Isengard smartd 1103 - - Device: /dev/disk/by-id/wwn-0x5000c5009399305f [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 66 to 65
<3.6> 2021-01-23T21:33:54.603840+01:00 Isengard smartd 1103 - - Device: /dev/disk/by-id/wwn-0x5000c5009399305f [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 34 to 35
<1.5> 2021-01-23T21:45:03.043504+01:00 Isengard Sistema - - - Logging the current external IP= (omitted)
2021-01-23 22:06:23+01:00 - Booting the system now ================================================================================ Linux Isengard 5.3.18-lp152.60-default #1 SMP Tue Jan 12 23:10:31 UTC 2021 (9898712) x86_64 x86_64 x86_64 GNU/Linux
<3.6> 2021-01-23T22:06:24.780509+01:00 Isengard systemd 1 - - systemd 234 running in system mode. (+PAM -AUDIT +SELINUX -IMA +APPARMOR -SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 -IDN default-hierarchy=hybrid)
<0.6> 2021-01-23T22:06:24.780976+01:00 Isengard kernel - - - [ 0.000000] microcode: microcode updated early to revision 0x411, date = 2019-04-23
<0.5> 2021-01-23T22:06:24.781721+01:00 Isengard kernel - - - [ 0.000000] Linux version 5.3.18-lp152.60-default (geeko@buildhost) (gcc version 7.5.
...
Aside note:
Kernel boot information is missing from syslog. New bug? Compare with leap 15.1 syslog:
2020-09-24 13:57:39+02:00 - Halting the system now =========================================== uptime: 13:57:39 up 82 days 15:43, 0 users, load average: 1.20, 1.30, 1.47
2020-09-24 20:48:11+02:00 - Booting the system now ================================================================================ Linux Isengard 4.12.14-lp151.28.67-default #1 SMP Fri Sep 4 15:23:21 UTC 2020 (2c5a14f) x86_64 x86_64 x86_64 GNU/Linux
<0.6> 2020-09-24T20:48:12.560421+02:00 Isengard kernel - - - [ 0.000000] microcode: microcode updated early to revision 0x411, date = 2019-04-23
<0.5> 2020-09-24T20:48:12.560854+02:00 Isengard kernel - - - [ 0.000000] Linux version 4.12.14-lp151.28.67-default (geeko@buildhost) (gcc version 7.5.0 (SUSE Linux) ) #1 SMP Fri Sep 4 15:23:21 UTC 2020 (2c5a14f)
<0.6> 2020-09-24T20:48:12.560862+02:00 Isengard kernel - - - [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.12.14-lp151.28.67-default root=UUID=0d457df1-b43d-4587-aa5a-6c919bcbedb8 showopts resume=/dev/disk/by-label/Swap splash=verbose
That would indicate a power failure, but the thing is on an UPS. I tested
flipping the mains, for 5 seconds, and it survived. I was in the house, I
would have noticed any power failure bigger than 0.1 second.
A thermal event would be logged, and the machine is not loaded, anyway.
Let's see if the journal has something:
cer@Isengard:~> journalctl --list-boots
- -9 6454520f76ef411aae4048bcad74bf29 Tue 2020-01-28 02:12:23 CET—Sun 2020-02-23 20:40:58 CET
- -8 690c025a20e74949aa3b14a9920bc965 Sun 2020-02-23 20:41:43 CET—Sun 2020-04-12 19:41:11 CEST
- -7 c931092ce6b742a0bcef0e0c789cc2d9 Sun 2020-04-12 19:41:55 CEST—Fri 2020-07-03 22:12:29 CEST
- -6 d0d9dcc6f41d4d95bfb1bb7017fd89b9 Fri 2020-07-03 22:14:26 CEST—Thu 2020-09-24 13:59:17 CEST
- -5 deddc3a843ba4ace9580e54614df5918 Thu 2020-09-24 20:46:37 CEST—Sat 2021-01-16 16:27:19 CET
- -4 0078032ae9f446389daef4b9b1546184 Sat 2021-01-16 16:28:09 CET—Sat 2021-01-16 20:55:05 CET
- -3 71982ddc703b49398aac561ae95a491f Sun 2021-01-17 10:12:08 CET—Sun 2021-01-17 21:01:44 CET
- -2 ff6a60796ff94a26a514a8bff51fd3e0 Sun 2021-01-17 21:02:19 CET—Sat 2021-01-23 21:45:03 CET
- -1 84c1f9d5c6c34fdbb83fe961e42bef1f Sat 2021-01-23 22:01:18 CET—Sat 2021-01-23 22:24:05 CET
0 ecd9e2c9fa9945e4ae57ef7e55938b36 Sat 2021-01-23 22:24:40 CET—Sat 2021-01-23 22:46:51 CET
cer@Isengard:~>
I need session 2, -2 Sun 2021-01-17 21:02:19 CET—Sat 2021-01-23 21:45:03 CET
cer@Isengard:~> journalctl --boot=2
- -- Logs begin at Tue 2020-01-28 02:12:23 CET, end at Sat 2021-01-23 22:48:07 CET. --
No - then session 3?
- -- Logs begin at Tue 2020-01-28 02:12:23 CET, end at Sat 2021-01-23 22:48:38 CET. --
No... wtf?
cer@Isengard:~> journalctl --boot=ff6a60796ff94a26a514a8bff51fd3e0
- -- Logs begin at Tue 2020-01-28 02:12:23 CET, end at Sat 2021-01-23 22:48:38 CET. --
That's the whole journal, not number 2.
Where is the journal number 2? Another bug in the journal?
Ok, let's find the boot point by grepping the whole journal, old style
Jan 23 21:16:57 Isengard dbus-daemon[1109]: [system] Successfully activated service 'org.opensuse.Snapper'
Jan 23 21:21:56 Isengard systemd[1]: Starting Cleanup of Temporary Directories...
Jan 23 21:21:56 Isengard systemd-tmpfiles[5561]: [/usr/lib/tmpfiles.d/net-snmp.conf:1] Line references path below legacy directory /var/run/, updating /var/run/net-snmp → /run/net-snmp; please update the tmpfiles.d/ drop-in file accordin>
Jan 23 21:21:56 Isengard systemd-tmpfiles[5561]: [/usr/lib/tmpfiles.d/radvd.conf:1] Line references path below legacy directory /var/run/, updating /var/run/radvd → /run/radvd; please update the tmpfiles.d/ drop-in file accordingly.
Jan 23 21:21:56 Isengard systemd-tmpfiles[5561]: [/usr/lib/tmpfiles.d/samba.conf:1] Line references path below legacy directory /var/run/, updating /var/run/samba → /run/samba; please update the tmpfiles.d/ drop-in file accordingly.
Jan 23 21:21:56 Isengard systemd-tmpfiles[5561]: [/usr/lib/tmpfiles.d/svnserve.conf:1] Line references path below legacy directory /var/run/, updating /var/run/svnserve → /run/svnserve; please update the tmpfiles.d/ drop-in file accordin>
Jan 23 21:21:56 Isengard systemd-tmpfiles[5561]: [/usr/lib/tmpfiles.d/tmp.conf:13] Duplicate line for path "/var/tmp", ignoring.
Jan 23 21:21:56 Isengard systemd-tmpfiles[5561]: [/usr/lib/tmpfiles.d/var.conf:21] Duplicate line for path "/var/lib", ignoring.
Jan 23 21:21:56 Isengard systemd-tmpfiles[5561]: [/usr/lib/tmpfiles.d/var.conf:23] Duplicate line for path "/var/spool", ignoring.
Jan 23 21:21:56 Isengard systemd[1]: Started Cleanup of Temporary Directories.
Jan 23 21:30:03 Isengard Sistema[5776]: Logging the current external IP= (omitted)
Jan 23 21:33:54 Isengard smartd[1103]: Device: /dev/sda [SAT], SMART Usage Attribute: 189 Airflow_Temperature_Cel changed from 41 to 46
Jan 23 21:33:54 Isengard smartd[1103]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 41 to 46
Jan 23 21:33:54 Isengard smartd[1103]: Device: /dev/disk/by-id/wwn-0x5000c5009399305f [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 66 to 65
Jan 23 21:33:54 Isengard smartd[1103]: Device: /dev/disk/by-id/wwn-0x5000c5009399305f [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 34 to 35
Jan 23 21:45:03 Isengard Sistema[6157]: Logging the current external IP= (omitted)
- -- Reboot --
Jan 23 22:01:18 Isengard kernel: microcode: microcode updated early to revision 0x411, date = 2019-04-23
Jan 23 22:01:18 Isengard kernel: Linux version 5.3.18-lp152.60-default (geeko@buildhost) (gcc version 7.5.0 (SUSE Linux)) #1 SMP Tue Jan 12 23:10:31 UTC 2021 (9898712)
Jan 23 22:01:18 Isengard kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.3.18-lp152.60-default root=UUID=0d457df1-b43d-4587-aa5a-6c919bcbedb8 showopts splash=verbose splash=silent resume=/dev/disk/by-label/Swap mitigations=auto quiet
Jan 23 22:01:18 Isengard kernel: x86/fpu: x87 FPU will use FXSAVE
Jan 23 22:01:18 Isengard kernel: BIOS-provided physical RAM map:
Jan 23 22:01:18 Isengard kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000003efff] usable
Jan 23 22:01:18 Isengard kernel: BIOS-e820: [mem 0x000000000003f000-0x000000000003ffff] ACPI NVS
Same info, that is, no info about what caused the machine to reboot. Has been fully reliable since I bought it on 2016:
2016-11-27 23:38:32+01:00 - Booting the system now ================================================================================ Linux Isengard 4.4.27-2-default #1 SMP Thu Nov 3 14:59:54 UTC 2016 (5c21e7c) x86_64 x86_64 x86_64 GNU/Linux
2016-12-04 15:44:09+01:00 - Halting the system now =========================================== uptime: 15:44pm up 6 days 16:06, 0 users, load average: 0.66, 0.25, 0.14
But now it is running Leap 15.2 since 2021-01-17, that is, a week ago.
It rebooted perhaps just at 22:00 - cronjob? I don't have, yet, any log
entry on a Saturday at 22:00 with leap 15.2, the machine was upgraded from 15.1
to 15.2 just on past Saturday (with DVD).
On previous 15.1, this is what happens normally:
<1.5> 2021-01-09T21:30:03.324416+01:00 Isengard Sistema - - - Logging the current external IP= (omitted)
<1.5> 2021-01-09T21:45:05.372100+01:00 Isengard Sistema - - - Logging the current external IP= (omitted)
<3.6> 2021-01-09T21:48:37.584878+01:00 Isengard smartd 25710 - - Device: /dev/sda [SAT], SMART Usage Attribute: 189 Airflow_Temperature_Cel changed from 42 to 43
<3.6> 2021-01-09T21:48:37.586113+01:00 Isengard smartd 25710 - - Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 42 to 43
<3.6> 2021-01-09T21:48:37.640372+01:00 Isengard smartd 25710 - - Device: /dev/disk/by-id/wwn-0x5000c5009399305f [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 67 to 66
<3.6> 2021-01-09T21:48:37.641443+01:00 Isengard smartd 25710 - - Device: /dev/disk/by-id/wwn-0x5000c5009399305f [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 33 to 34
<3.6> 2021-01-09T22:00:03.382980+01:00 Isengard systemd 1 - - Started Timeline of Snapper Snapshots.
<3.6> 2021-01-09T22:00:03.514452+01:00 Isengard dbus-daemon 1186 - - [system] Activating service name='org.opensuse.Snapper' requested by ':1.16079' (uid=0 pid=23673 comm="/usr/lib/snapper/systemd-helper --timeline ") (using servicehelper)
<3.6> 2021-01-09T22:00:03.775706+01:00 Isengard dbus-daemon 1186 - - [system] Successfully activated service 'org.opensuse.Snapper'
<1.5> 2021-01-09T22:00:08.698222+01:00 Isengard Sistema - - - Logging the current external IP= (omitted)
<9.6> 2021-01-09T22:15:01.744156+01:00 Isengard run-crons.daily - - - Considering my daily cron jobs.
<9.6> 2021-01-09T22:15:01.885387+01:00 Isengard run-crons.daily - - - Adjusting permissions of Video directories
I'll have to keep watching and see...
- --
Cheers
Carlos E. R.
(from 15.2 x86_64 at Telcontar)
-----BEGIN PGP SIGNATURE-----
iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYAyj2hwccm9iaW4ubGlz
dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfV5CYAoIQFFQZGRpCSsGwRl9bj
jWgcgHdvAJ0TCi2Cbp5P5RkyBNJLKTzsNojWVw==
=D6AM
-----END PGP SIGNATURE-----
Hi,
I am looking for a simple kubernetes distribution which will run on
vanilla tumbleweed with btrfs and will not require a VM.
I intend to edit live container/pod code via vscode's docker integration.
Seems like minikube does not like btrfs and would require a VM which I
don't like on a dev laptop.
In Windows and Mac scenarios I just run the kubernetes options of Docker
Desktop.
This is obviously nothing to expose to the internet or run live
workloads, just an easy dev setup.
Which option would you suggest?
Regards
Ralf
--
Ralf Lang
Linux Consultant / Developer
Tel.: +49-170-6381563
Mail: lang(a)b1-systems.de
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
On an up-to-date Tumbleweed computer, my daughter now has trouble with
things like the clock in the KDE status bar. She suspected that it was not
updating properly so she turned on showing seconds. And she sees that it is
very uneven about when time is updated. We have looked at the processes
running and the memory and swap usage. I cannot see anything that would
explain such delays.
The clock update is useful when she is taking remote exams (at the
University). Also, after the update, programs like zoom have become
unstable. Zoom itself was not updated. But all else has been as part of the
usual Tumbleweed updates.
My own system (different laptop so not the same hardware) with basically
the same versions of all software does not exhibit this behavior.
I'm not sure where to start looking. X is whatever the default would be as
the result of a Tumbleweed install. My daughter's install is a couple years
old. It has been fine up to the update done in late December. All updates
since then are also installed, but they have not helped.
Any suggestions where to look? As I seldom have trouble, I confess that I'm
a bit rusty at this type of thing. I googled the clock thing but I did not
find much. Of course, it may not even be the clock part that is the real
problem...
--
Roger Oberholtzer
Hi,
it seems that after my latest update of vim (on Leap 15.2) my syntax
highlighting configuration is not working correctly anymore.
I have something along the following lines in my .vimrc:
let color = "true"
if has("syntax")
if color == "true"
" This will switch colors ON
" if we use xterm we use our own color definitions
" in cause of background color
if &term=="xterm"
syntax on
And xterm is still what I use here.
My vimrc is VERY old and apparently something changed recently so it's
not cooperating with the rest of the system configuration I assume?
In the vim changelog I find:
- stop owning /etc/vimrc so the old, distro provided config actually
gets removed. Leaving it around leads to a duplicated autocmd for
* .spec, leading to spec file template inserted twice.
But I cannot really tell if that is relevant and where it broke for me.
Any hints?
Thanks,
Wolfgang
Has anyone tried a headset like the Jabra Evolve 65 with Tumbleweed? I need
a headset for things like Teams, and I am considering this Bluetooth
headset. I generally do not use Bluetooth, so I'm not sure how well it is
working with things like this. My laptop's built-in microphone is pretty
crappy (very bad quality sound), so I am looking for an alternative. And
there is the disturbance factor. My laptop does not have any standard USB
ports, so I am trying not to get devices that need this. An adapter is ok.
But if I can avoid it, that is a plus.
--
Roger Oberholtzer
how does one turn off "autoplay" of videos in chromium?
the solutions/paths provided via search on google do not seem available on
chromium.
--
(paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri
http://en.opensuse.org openSUSE Community Member facebook/ptilopteri
Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
After upgrade of both server and client to Leap 15.2, an NFS export is not
working (it worked before).
Server:
Isengard:~ # systemctl status nfsserver.service
● nfsserver.service - Alias for NFS server
Loaded: loaded (/usr/lib/systemd/system/nfsserver.service; enabled; vendor preset: disabled)
Active: active (exited) since Mon 2021-01-18 01:26:07 CET; 9min ago
Process: 14117 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
Main PID: 14117 (code=exited, status=0/SUCCESS)
Tasks: 0
CGroup: /system.slice/nfsserver.service
Jan 18 01:26:07 Isengard systemd[1]: Starting Alias for NFS server...
Jan 18 01:26:07 Isengard systemd[1]: Started Alias for NFS server.
Isengard:~ #
The service was stopped because "dependency". I did not study why, just restarted it.
Isengard:~ # cat /etc/exports
/data/hoard_1 192.168.1.14(rw,no_root_squash,sync,subtree_check)
/data/hoard_2 192.168.1.14(rw,no_root_squash,sync,subtree_check)
Isengard:~ #
Client:
Telcontar:~ # grep hoard_ /etc/fstab
Isengard.valinor:/data/hoard_1/ /mnt/nfs/Isengard/hoard_1 nfs4 noauto,nofail,x-systemd.automount,x-systemd.idle-timeout=300,_netdev,user,users,lazytime 0 0
Isengard.valinor:/data/hoard_2/ /mnt/nfs/Isengard/hoard_2 nfs4 noauto,nofail,x-systemd.automount,x-systemd.idle-timeout=300,_netdev,user,users,lazytime 0 0
Telcontar:~ #
It does not automount, nor does it mount manually:
Telcontar:~ # mount -v /mnt/nfs/Isengard/hoard_1
mount.nfs4: timeout set for Mon Jan 18 01:41:13 2021
mount.nfs4: trying text-based options 'vers=4.2,addr=192.168.1.16,clientaddr=192.168.1.14'
mount.nfs4: mount(2): Connection refused <==========
mount.nfs4: trying text-based options 'addr=192.168.1.16'
mount.nfs4: prog 100003, trying vers=3, prot=6
mount.nfs4: portmap query retrying: RPC: Program not registered
mount.nfs4: prog 100003, trying vers=3, prot=17
mount.nfs4: portmap query failed: RPC: Program not registered
mount.nfs4: trying text-based options 'vers=4.2,addr=192.168.1.16,clientaddr=192.168.1.14'
mount.nfs4: mount(2): Connection refused
mount.nfs4: trying text-based options 'addr=192.168.1.16'
mount.nfs4: prog 100003, trying vers=3, prot=6
mount.nfs4: portmap query retrying: RPC: Program not registered
mount.nfs4: prog 100003, trying vers=3, prot=17
mount.nfs4: portmap query failed: RPC: Program not registered
mount.nfs4: trying text-based options 'vers=4.2,addr=192.168.1.16,clientaddr=192.168.1.14'
mount.nfs4: mount(2): Connection refused
mount.nfs4: trying text-based options 'addr=192.168.1.16'
mount.nfs4: prog 100003, trying vers=3, prot=6
mount.nfs4: portmap query retrying: RPC: Program not registered
mount.nfs4: prog 100003, trying vers=3, prot=17
mount.nfs4: portmap query failed: RPC: Program not registered
mount.nfs4: requested NFS version or transport protocol is not supported
Telcontar:~ #
Nothing on server log when I try to connect. NOthing on firewalls logs. Nothing on apparmor.
What is going on?
Server:
Isengard:~ # showmount
Hosts on Isengard:
Isengard:~ # showmount --all
All mount points on Isengard:
Isengard:~ # showmount --exports
Export list for Isengard:
Isengard:~ #
Why doesn't the command list the exports in the /etc/exports file?
- --
Cheers
Carlos E. R.
(from 15.2 x86_64 at Telcontar)
-----BEGIN PGP SIGNATURE-----
iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYATb6Rwccm9iaW4ubGlz
dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVo1cAoI2C901up/Ng1AaP0VWL
M0XwRZawAJ9nVqYbdZoWmhCbUSCwt1KFX/k0xQ==
=QxFZ
-----END PGP SIGNATURE-----
Hello:
I prefer to look the mailing list messages on the website.
Previously I used
https://lists.opensuse.org/opensuse/
and that site was absolutely clear and easy to use.
Now I am trying read messages at:
https://lists.opensuse.org/archives/list/users@lists.opensuse.org/
But it only shows messages back until January 5.
If I choose to see more threads (click All Threads) or select a month
on the left, the message list extends, that is not only the title but
some of the messages' bodies are shown. It is very difficult to read
the titles only.
OK, how can I get a condensed, titles only view, when I want to see
more threads than those shown at the start page?
Thanks,
Istvan
I am running unbound.
I have defined an AA-profile for it.
From time to time unbound does not start. The reason I find in the logs:
could not open autotrust-file for writing /var/lib/unbound/root.key.2112-0
permission denied.
I tried to set AA on complain, but it does not encounter something to complain
and to adapt. I recall I granted the right to that process in AA.
Moreover, when I start the unbound by hand in "service" the process starts
without any problem. And without giving error.
So the issue seems only when it tries to update the autotrust-file.
So, I do not understand why it needs to write to autotrust and I would like to
know what permissions it should have, to compare with the ones I have:
ls -l /var/lib/unbound/
entropia@roadrunner:~> ls -l /var/lib/unbound/
totale 4
-rw-r--r-- 1 unbound unbound 1251 20 gen 02.14 root.key
Seems about right??
Or does the permission here need to be root:unbound?
Thanks in advance. (Once it runs it is fast and reliable, but it is irritating
that it fallbacks all the time due to this error.
