Beiträge von malagasy
-
-
I finally found something from the logs,
Code
Alles anzeigenSep 06 08:38:52 xxxx dbus-daemon[1863]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.100' (uid=1000 pid=15909 comm="/snap/code/7> Sep 06 08:38:52 eabha dbus-daemon[1863]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found. Sep 06 08:38:54 xxxx kernel: nouveau 0000:01:00.0: Enabling HDA controller Sep 06 08:40:21 xxxx sudo[16403]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Sep 06 08:40:29 xxxx sudo[16403]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Sep 06 08:40:29 xxxx sudo[16403]: pam_unix(sudo:auth): authentication failure; logname= uid=1000 euid=0 tty=/dev/pts/0 ruser=malagasy rhost= user=malagasy Sep 06 08:40:31 xxxx sudo[16403]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Sep 06 08:40:38 xxxx sudo[16403]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Sep 06 08:40:38 xxxx sudo[16403]: malagasy : TTY=pts/0 ; PWD=/home/malagasy ; USER=root ; COMMAND=/usr/bin/mount 192.168.0.20:/ /mnt/MyBackup/ Sep 06 08:40:38 xxxx sudo[16403]: pam_unix(sudo:session): session opened for user root by (uid=1000) Sep 06 08:40:38 xxxx kernel: FS-Cache: Loaded Sep 06 08:40:38 xxxx kernel: FS-Cache: Netfs 'nfs' registered for caching Sep 06 08:40:38 xxxx kernel: NFS: Registering the id_resolver key type Sep 06 08:40:38 xxxx kernel: Key type id_resolver registered Sep 06 08:40:38 xxxx kernel: Key type id_legacy registered Sep 06 08:40:46 xxxx sudo[16403]: pam_unix(sudo:session): session closed for user root Sep 06 08:41:00 xxxx systemd-resolved[1777]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 192.168.0.254. Sep 06 08:41:04 xxxx sudo[16556]: malagasy : TTY=pts/0 ; PWD=/home/malagasy ; USER=root ; COMMAND=/usr/bin/mount -vvv -t nfs 192.168.0.20:/ /mnt/MyBackup/ Sep 06 08:41:04 xxxx sudo[16556]: pam_unix(sudo:session): session opened for user root by (uid=1000)
That matches the authentication error from the GUI, that I missed earlier.
Code6/9/2021, 08:42:01 CRON[26040]: pam_unix(cron:session): session closed for user root 6/9/2021, 08:42:01 CRON[26040]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
I believe this one is preventing me to mount the shared nfs folder.
What changes should I apply to fix this one?
-
Hello,
I just run the script from github as suggest, to install OMV on a raspberry pi 4. The default user pi was replaced with another one.
After I enabled NFS share, then I cannot mount the remote folder on my linux machine.
[raspberry pi]
----------------
Code
Alles anzeigen$ showmount -e Export list for k8sn01b: /export 192.168.0.0/24 /export/PcyBackup 192.168.0.0/24 $ cat /etc/exports # This file is auto-generated by openmediavault (https://www.openmediavault.org) # WARNING: Do not edit this file, your changes will get lost. # /etc/exports: the access control list for filesystems which may be exporte # to NFS clients. See exports(5). /export/PcyBackup 192.168.0.0/24(fsid=1,rw,sync,insecure,no_root_squash,no_subtree_check) # NFSv4 - pseudo filesystem root # Default: # /export 192.168.0.0/24(ro,fsid=0,root_squash,subtree_check,hide) /export 192.168.0.0/24(rw,fsid=0,root_squash,insecure,no_subtree_check,nohide,sync)
Then, on my machine
Code
Alles anzeigen$ sudo showmount -e 192.168.0.20 Export list for 192.168.0.20: /export 192.168.0.0/24 /export/PcyBackup 192.168.0.0/24 $ sudo mount -vvv -t nfs 192.168.0.20:/export/PcyBackup /mnt/MyBackup/ mount.nfs: timeout set for Sat Sep 4 09:12:32 2021 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.0.20,clientaddr=192.168.0.10' mount.nfs: mount(2): Connection timed out mount.nfs: Connection timed out
I also tried,
but same issue.
There is nothing in the logs, the folder is empty.
Code$ ls -la /var/log/openmediavault/ total 0 drwxr-xr-x 2 root root 40 Dec 14 2020 . drwxr-xr-x 14 root root 1520 Sep 4 00:17 ..
With the GUI in Diagnostic > System Logs, there is nothing at all.
The workaround I found to access my shared folder is to modify the pseudo filesystem root from the export file. This way, I can open directly my shared folder after I click the option to "browse network".
Anyone can help to fix the mount option, so I can set the export file into its default configuration? Thank you.