Everything posted by Gabriel_B
-
Unraid kernel crash and forgets all shares when deleting files via NFS (repeatable)
This still happens in April 2026.
-
Unraid kernel crash and forgets all shares when deleting files via NFS (repeatable)
Still happening.
-
Unraid kernel crash and forgets all shares when deleting files via NFS (repeatable)
NFS shares are completely unusable. This is after I switched al my business computers to Linux Mint. AutoFS is used to mount these shares; tried all the arguments that are floating around. The problem is always after deleting a file and completely crashes ALL shares. Guess we're switching it all to Samba /sigh. text error warn system array login Nov 19 16:55:55 Fatsally root: plugin: skipping: /boot/config/plugins/unassigned.devices/iso_mount.cfg already exists Nov 19 16:55:55 Fatsally root: plugin: creating: /tmp/unassigned.devices/add-smb - from INLINE content Nov 19 16:55:55 Fatsally root: plugin: setting: /tmp/unassigned.devices/add-smb - mode to 0770 Nov 19 16:55:55 Fatsally root: plugin: running: anonymous Nov 19 16:55:55 Fatsally unassigned.devices: Updating share settings... Nov 19 16:55:55 Fatsally unassigned.devices: Removing SMB share 'HIBERNATION'. Nov 19 16:55:55 Fatsally unassigned.devices: Removing NFS share '/mnt/disks/HIBERNATION'. Nov 19 16:55:55 Fatsally unassigned.devices: Adding SMB share 'HIBERNATION'. Nov 19 16:55:55 Fatsally unassigned.devices: Adding NFS share '/mnt/disks/HIBERNATION'. Nov 19 16:55:55 Fatsally unassigned.devices: Share settings updated. Nov 19 16:55:55 Fatsally root: plugin: unassigned.devices.plg updated Nov 19 17:39:19 Fatsally rpc.mountd[25994]: v4.2 client attached: 0xa660e8a8671590a3 from "192.168.88.23:739" Nov 19 17:40:35 Fatsally rpc.mountd[25994]: v4.2 client detached: 0xa660e8a8671590a3 from "192.168.88.23:739" Nov 19 17:51:53 Fatsally rpc.mountd[25994]: v4.2 client attached: 0xa660e8bc671590a3 from "192.168.88.23:893" Nov 19 17:53:08 Fatsally rpc.mountd[25994]: v4.2 client detached: 0xa660e8bc671590a3 from "192.168.88.23:893" Nov 19 18:07:26 Fatsally rpc.mountd[25994]: v4.2 client attached: 0xa660e8d4671590a3 from "192.168.88.23:706" Nov 19 18:08:41 Fatsally rpc.mountd[25994]: v4.2 client detached: 0xa660e8d4671590a3 from "192.168.88.23:706" Nov 19 18:28:01 Fatsally rpc.mountd[25994]: v4.2 client attached: 0xa660e8f4671590a3 from "192.168.88.23:681" Nov 19 18:29:16 Fatsally rpc.mountd[25994]: v4.2 client detached: 0xa660e8f4671590a3 from "192.168.88.23:681" Nov 19 18:44:20 Fatsally rpc.mountd[25994]: v4.2 client attached: 0xa660e90e671590a3 from "192.168.88.23:897" Nov 19 18:45:35 Fatsally rpc.mountd[25994]: v4.2 client detached: 0xa660e90e671590a3 from "192.168.88.23:897" Nov 19 18:51:52 Fatsally rpc.mountd[25994]: v4.2 client attached: 0xa660e91a671590a3 from "192.168.88.23:677" Nov 19 18:53:07 Fatsally rpc.mountd[25994]: v4.2 client detached: 0xa660e91a671590a3 from "192.168.88.23:677" Nov 19 19:04:55 Fatsally rpc.mountd[25994]: v4.2 client attached: 0xa660e92e671590a3 from "192.168.88.23:937" Nov 19 19:06:10 Fatsally rpc.mountd[25994]: v4.2 client detached: 0xa660e92e671590a3 from "192.168.88.23:937" Nov 19 21:13:11 Fatsally rpc.mountd[25994]: v4.2 client attached: 0xa660e9f4671590a3 from "192.168.88.23:697" Nov 19 21:14:26 Fatsally rpc.mountd[25994]: v4.2 client detached: 0xa660e9f4671590a3 from "192.168.88.23:697" Nov 19 21:28:15 Fatsally rpc.mountd[25994]: v4.2 client attached: 0xa660ea0c671590a3 from "192.168.88.23:727" Nov 19 21:29:30 Fatsally rpc.mountd[25994]: v4.2 client detached: 0xa660ea0c671590a3 from "192.168.88.23:727" Nov 19 21:42:03 Fatsally rpc.mountd[25994]: v4.2 client attached: 0xa660ea22671590a3 from "192.168.88.23:802" Nov 19 21:43:18 Fatsally rpc.mountd[25994]: v4.2 client detached: 0xa660ea22671590a3 from "192.168.88.23:802" Nov 19 21:47:05 Fatsally rpc.mountd[25994]: v4.2 client attached: 0xa660ea2a671590a3 from "192.168.88.23:778" Nov 19 21:48:20 Fatsally rpc.mountd[25994]: v4.2 client detached: 0xa660ea2a671590a3 from "192.168.88.23:778" Nov 19 22:36:17 Fatsally rpc.mountd[25994]: v4.2 client attached: 0xa660ea78671590a3 from "192.168.88.23:762" Nov 19 22:37:32 Fatsally rpc.mountd[25994]: v4.2 client detached: 0xa660ea78671590a3 from "192.168.88.23:762" Nov 19 23:03:38 Fatsally rpc.mountd[25994]: v4.2 client attached: 0xa660eaa0671590a3 from "192.168.88.23:863" Nov 19 23:04:53 Fatsally rpc.mountd[25994]: v4.2 client detached: 0xa660eaa0671590a3 from "192.168.88.23:863" Nov 20 02:00:04 Fatsally root: /etc/libvirt: 30.3 MiB (31797248 bytes) trimmed on /dev/loop3 Nov 20 02:00:04 Fatsally root: /var/lib/docker: 1000.3 MiB (1048875008 bytes) trimmed on /dev/loop2 Nov 20 02:00:04 Fatsally root: /mnt/cache: 220.6 GiB (236889636864 bytes) trimmed on /dev/nvme0n1p1 Nov 20 09:39:30 Fatsally kernel: shfs[2209]: segfault at 10 ip 000014dacd22a5c2 sp 000014dab784fc20 error 4 in libfuse3.so.3.12.0[14dacd226000+19000] likely on CPU 9 (core 14, socket 0) Nov 20 09:39:30 Fatsally kernel: Code: f4 c8 ff ff 8b b3 08 01 00 00 85 f6 0f 85 46 01 00 00 4c 89 ee 48 89 df 45 31 ff e8 18 dc ff ff 4c 89 e7 45 31 e4 48 8b 40 20 <4c> 8b 68 10 e8 15 c2 ff ff 48 8d 4c 24 18 45 31 c0 31 d2 4c 89 ee Nov 20 09:39:30 Fatsally kernel: ------------[ cut here ]------------ Nov 20 09:39:30 Fatsally kernel: nfsd: non-standard errno: -107 Nov 20 09:39:30 Fatsally kernel: WARNING: CPU: 10 PID: 3960 at fs/nfsd/vfs.c:111 nfserrno+0x45/0x51 [nfsd] Nov 20 09:39:30 Fatsally kernel: Modules linked in: nf_tables rpcsec_gss_krb5 vhost_net tun vhost tap kvm_intel kvm md_mod xt_nat xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle vhost_iotlb veth ipvlan xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter nvidia_uvm(PO) xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) i915 drm_buddy i2c_algo_bit ttm drm_display_helper intel_gtt agpgart tcp_diag inet_diag wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc bonding tls e1000e atlantic nvidia_drm(PO) nvidia_modeset(PO) intel_rapl_msr intel_rapl_common iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp Nov 20 09:39:30 Fatsally kernel: nvidia(PO) crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 aesni_intel crypto_simd cryptd video rapl drm_kms_helper btusb btrtl intel_cstate drm btbcm btintel nvme backlight i2c_i801 bluetooth mxm_wmi mpt3sas intel_uncore syscopyarea thunderbolt nvme_core intel_wmi_thunderbolt i2c_smbus sysfillrect mei_me sysimgblt fb_sys_fops i2c_core raid_class scsi_transport_sas ahci mei libahci input_leds ecdh_generic led_class joydev ecc tpm_crb tpm_tis tpm_tis_core tpm wmi acpi_tad button unix [last unloaded: md_mod] Nov 20 09:39:30 Fatsally kernel: CPU: 10 PID: 3960 Comm: nfsd Tainted: P O 6.1.106-Unraid #1 Nov 20 09:39:30 Fatsally kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X299 Creator, BIOS L1.52C 08/05/2022 Nov 20 09:39:30 Fatsally kernel: RIP: 0010:nfserrno+0x45/0x51 [nfsd] Nov 20 09:39:30 Fatsally kernel: Code: c3 cc cc cc cc 48 ff c0 48 83 f8 26 75 e0 80 3d 41 b6 05 00 00 75 15 48 c7 c7 e6 6a 24 a5 c6 05 31 b6 05 00 01 e8 44 a2 e5 db <0f> 0b b8 00 00 00 05 c3 cc cc cc cc 0f 1f 44 00 00 41 57 41 56 41 Nov 20 09:39:30 Fatsally kernel: RSP: 0018:ffffc90000eafd50 EFLAGS: 00010286 Nov 20 09:39:30 Fatsally kernel: RAX: 0000000000000000 RBX: ffff88817fc4c028 RCX: 0000000000000027 Nov 20 09:39:30 Fatsally kernel: RDX: 0000000000000002 RSI: ffffffff820d99e1 RDI: 00000000ffffffff Nov 20 09:39:30 Fatsally kernel: RBP: ffff88817fc10000 R08: 0000000000000000 R09: ffffffff829573f0 Nov 20 09:39:30 Fatsally kernel: R10: 00003fffffffffff R11: ffff88909ffcf08e R12: ffff888104f67b00 Nov 20 09:39:30 Fatsally kernel: R13: ffff888961ec9100 R14: 000000000000000b R15: 0000000000000000 Nov 20 09:39:30 Fatsally kernel: FS: 0000000000000000(0000) GS:ffff88905fe80000(0000) knlGS:0000000000000000 Nov 20 09:39:30 Fatsally kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Nov 20 09:39:30 Fatsally kernel: CR2: 000014f0fca601e0 CR3: 000000000220a004 CR4: 00000000003726e0 Nov 20 09:39:30 Fatsally kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Nov 20 09:39:30 Fatsally kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Nov 20 09:39:30 Fatsally kernel: Call Trace: Nov 20 09:39:30 Fatsally kernel: <TASK> Nov 20 09:39:30 Fatsally kernel: ? __warn+0xab/0x122 Nov 20 09:39:30 Fatsally kernel: ? report_bug+0x109/0x17e Nov 20 09:39:30 Fatsally kernel: ? nfserrno+0x45/0x51 [nfsd] Nov 20 09:39:30 Fatsally kernel: ? handle_bug+0x41/0x6f Nov 20 09:39:30 Fatsally kernel: ? exc_invalid_op+0x13/0x60 Nov 20 09:39:30 Fatsally kernel: ? asm_exc_invalid_op+0x16/0x20 Nov 20 09:39:30 Fatsally kernel: ? nfserrno+0x45/0x51 [nfsd] Nov 20 09:39:30 Fatsally kernel: fh_verify+0x531/0x610 [nfsd] Nov 20 09:39:30 Fatsally kernel: nfsd_lookup+0x3f/0xdb [nfsd] Nov 20 09:39:30 Fatsally kernel: nfsd4_proc_compound+0x444/0x57f [nfsd] Nov 20 09:39:30 Fatsally kernel: nfsd_dispatch+0x1db/0x28f [nfsd] Nov 20 09:39:30 Fatsally kernel: svc_process_common+0x300/0x511 [sunrpc] Nov 20 09:39:30 Fatsally kernel: ? ktime_get+0x35/0x49 Nov 20 09:39:30 Fatsally kernel: ? nfsd_svc+0x2cf/0x2cf [nfsd] Nov 20 09:39:30 Fatsally kernel: ? nfsd_shutdown_threads+0x5b/0x5b [nfsd] Nov 20 09:39:30 Fatsally kernel: svc_process+0xcc/0xe9 [sunrpc] Nov 20 09:39:30 Fatsally kernel: nfsd+0x96/0x108 [nfsd] Nov 20 09:39:30 Fatsally kernel: kthread+0xe4/0xef Nov 20 09:39:30 Fatsally kernel: ? kthread_complete_and_exit+0x1b/0x1b Nov 20 09:39:30 Fatsally kernel: ret_from_fork+0x1f/0x30 Nov 20 09:39:30 Fatsally kernel: </TASK> Nov 20 09:39:30 Fatsally kernel: ---[ end trace 0000000000000000 ]--- Nov 20 09:39:30 Fatsally rsyslogd: file '/mnt/user/appdata/syslog-192.168.88.217.log'[2] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: Transport endpoint is not connected [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Nov 20 09:39:30 Fatsally rsyslogd: file '/mnt/user/appdata/syslog-192.168.88.217.log': open error: Transport endpoint is not connected [v8.2102.0 try https://www.rsyslog.com/e/2433 ] Nov 20 09:42:12 Fatsally smbd[25503]: [2024/11/20 09:42:12.625485, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Nov 20 09:42:12 Fatsally smbd[25503]: make_connection_snum: canonicalize_connect_path failed for service Downloads, path /mnt/user/Downloads
-
Unraid kernel crash and forgets all shares when deleting files via NFS (repeatable)
I keep running into this issue.
-
shfs[12108]: segfault
Any solution yet? Nov 21 09:58:14 Fatsally kernel: shfs[12430]: segfault at 10 ip 000014cf6d31b5c2 sp 000014cf6c2e4c20 error 4 in libfuse3.so.3.12.0[14cf6d317000+19000] likely on CPU 4 (core 5, socket 0) Nov 21 09:58:14 Fatsally kernel: Code: f4 c8 ff ff 8b b3 08 01 00 00 85 f6 0f 85 46 01 00 00 4c 89 ee 48 89 df 45 31 ff e8 18 dc ff ff 4c 89 e7 45 31 e4 48 8b 40 20 <4c> 8b 68 10 e8 15 c2 ff ff 48 8d 4c 24 18 45 31 c0 31 d2 4c 89 ee Nov 21 09:58:14 Fatsally kernel: ------------[ cut here ]------------ Nov 21 09:58:14 Fatsally kernel: nfsd: non-standard errno: -103 Nov 21 09:58:14 Fatsally kernel: WARNING: CPU: 16 PID: 3954 at fs/nfsd/vfs.c:111 nfserrno+0x45/0x51 [nfsd] Nov 21 09:58:14 Fatsally kernel: Modules linked in: rpcsec_gss_krb5 nf_tables xt_nat xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap veth ipvlan xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter nvidia_uvm(PO) xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) i915 drm_buddy i2c_algo_bit ttm drm_display_helper intel_gtt agpgart tcp_diag inet_diag wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc bonding tls e1000e atlantic nvidia_drm(PO) nvidia_modeset(PO) intel_rapl_msr intel_rapl_common iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel nvidia(PO) Nov 21 09:58:14 Fatsally kernel: kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 aesni_intel video crypto_simd cryptd rapl drm_kms_helper btusb btrtl btbcm btintel intel_cstate nvme drm bluetooth mxm_wmi intel_wmi_thunderbolt mpt3sas intel_uncore thunderbolt nvme_core backlight i2c_i801 syscopyarea mei_me sysfillrect i2c_smbus raid_class sysimgblt fb_sys_fops i2c_core scsi_transport_sas mei ahci input_leds libahci ecdh_generic joydev led_class ecc tpm_crb tpm_tis tpm_tis_core tpm wmi acpi_tad button unix [last unloaded: e1000e] Nov 21 09:58:14 Fatsally kernel: CPU: 16 PID: 3954 Comm: nfsd Tainted: P O 6.1.106-Unraid #1 Nov 21 09:58:14 Fatsally kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X299 Creator, BIOS L1.52C 08/05/2022 Nov 21 09:58:14 Fatsally kernel: RIP: 0010:nfserrno+0x45/0x51 [nfsd] Nov 21 09:58:14 Fatsally kernel: Code: c3 cc cc cc cc 48 ff c0 48 83 f8 26 75 e0 80 3d 41 b6 05 00 00 75 15 48 c7 c7 e6 0a 24 a5 c6 05 31 b6 05 00 01 e8 44 02 e6 db <0f> 0b b8 00 00 00 05 c3 cc cc cc cc 0f 1f 44 00 00 41 57 41 56 41 Nov 21 09:58:14 Fatsally kernel: RSP: 0018:ffffc90000e1fd38 EFLAGS: 00010282 Nov 21 09:58:14 Fatsally kernel: RAX: 0000000000000000 RBX: ffff888173b8e028 RCX: 0000000000000027 Nov 21 09:58:14 Fatsally kernel: RDX: 0000000000000002 RSI: ffffffff820d99e1 RDI: 00000000ffffffff Nov 21 09:58:14 Fatsally kernel: RBP: ffffc90000e1fd80 R08: 0000000000000000 R09: ffffffff829573f0 Nov 21 09:58:14 Fatsally kernel: R10: 00003fffffffffff R11: ffff88909ffbd0ce R12: ffff888173b8e100 Nov 21 09:58:14 Fatsally kernel: R13: ffff888108610340 R14: 0000000000000080 R15: ffff88810e3ea3c0 Nov 21 09:58:14 Fatsally kernel: FS: 0000000000000000(0000) GS:ffff889060000000(0000) knlGS:0000000000000000 Nov 21 09:58:14 Fatsally kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Nov 21 09:58:14 Fatsally kernel: CR2: 0000146bd27edf88 CR3: 000000000220a002 CR4: 00000000003726e0 Nov 21 09:58:14 Fatsally kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Nov 21 09:58:14 Fatsally kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Nov 21 09:58:14 Fatsally kernel: Call Trace: Nov 21 09:58:14 Fatsally kernel: <TASK> Nov 21 09:58:14 Fatsally kernel: ? __warn+0xab/0x122 Nov 21 09:58:14 Fatsally kernel: ? report_bug+0x109/0x17e Nov 21 09:58:14 Fatsally kernel: ? nfserrno+0x45/0x51 [nfsd] Nov 21 09:58:14 Fatsally kernel: ? handle_bug+0x41/0x6f Nov 21 09:58:14 Fatsally kernel: ? exc_invalid_op+0x13/0x60 Nov 21 09:58:14 Fatsally kernel: ? asm_exc_invalid_op+0x16/0x20 Nov 21 09:58:14 Fatsally kernel: ? nfserrno+0x45/0x51 [nfsd] Nov 21 09:58:14 Fatsally kernel: ? nfserrno+0x45/0x51 [nfsd] Nov 21 09:58:14 Fatsally kernel: fh_getattr+0x43/0x61 [nfsd] Nov 21 09:58:14 Fatsally kernel: fh_fill_post_attrs+0x55/0xa4 [nfsd] Nov 21 09:58:14 Fatsally kernel: nfsd_unlink+0x1bd/0x250 [nfsd] Nov 21 09:58:14 Fatsally kernel: nfsd4_remove+0x4f/0x6e [nfsd] Nov 21 09:58:14 Fatsally kernel: nfsd4_proc_compound+0x444/0x57f [nfsd] Nov 21 09:58:14 Fatsally kernel: nfsd_dispatch+0x1db/0x28f [nfsd] Nov 21 09:58:14 Fatsally kernel: svc_process_common+0x300/0x511 [sunrpc] Nov 21 09:58:14 Fatsally kernel: ? ktime_get+0x35/0x49 Nov 21 09:58:14 Fatsally kernel: ? nfsd_svc+0x2cf/0x2cf [nfsd] Nov 21 09:58:14 Fatsally kernel: ? nfsd_shutdown_threads+0x5b/0x5b [nfsd] Nov 21 09:58:14 Fatsally kernel: svc_process+0xcc/0xe9 [sunrpc] Nov 21 09:58:14 Fatsally kernel: nfsd+0x96/0x108 [nfsd] Nov 21 09:58:14 Fatsally kernel: kthread+0xe4/0xef Nov 21 09:58:14 Fatsally kernel: ? kthread_complete_and_exit+0x1b/0x1b Nov 21 09:58:14 Fatsally kernel: ret_from_fork+0x1f/0x30 Nov 21 09:58:14 Fatsally kernel: </TASK> Nov 21 09:58:14 Fatsally kernel: ---[ end trace 0000000000000000 ]--- Nov 21 09:58:14 Fatsally rsyslogd: file '/mnt/user/appdata/syslog-192.168.88.217.log'[2] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: Transport endpoint is not connected [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Nov 21 09:58:14 Fatsally rsyslogd: file '/mnt/user/appdata/syslog-192.168.88.217.log': open error: Transport endpoint is not connected [v8.2102.0 try https://www.rsyslog.com/e/2433 ]
-
Unraid Dashboard randomly becomes unresponsive - Incognito solves it
Have this issue for over a year now. Happens after a few days. Reboot seems to be the only solution I have found. Posted my diagnostics a few times, no help.
-
UI keeps becoming unusable.
Problem is back again!
-
[Support] d8sychain - MediaWiki
Can't figure out for the life of me how to put an image or video in here. A Youtube video, or picture from a web address. Also, the whole wiki becomes unusable when trying to install and enable a skin. All instructions were followed. https://www.mediawiki.org/wiki/Extension:DarkMode and https://www.mediawiki.org/wiki/Skin:DarkVector Any pointers would be greatly appreciated!
-
UI keeps becoming unusable.
-
UI keeps becoming unusable.
Updated to the latest Unraid, took less then 24 hours to make the UI mess up again. Reboot did not fix it this time, restarted Docker and now the UI populated again. All Dockers are latest versions (Cloudflared too), Unraid logs show no errors when it started with the UI messed up.
-
UI keeps becoming unusable.
Problem still here. Updating to latest Unraid now.
-
UI keeps becoming unusable.
No, not resolved. 13 days now and it happened again.fatsally-diagnostics-20230615-0810.zip Snagged the latest diag file.
-
UI keeps becoming unusable.
Still working. Getting the latest 'Cloudflared' Docker and the new way of tunneling with the UI, which was easy setup, it's still working, no errors in the log so I guess it's fixed now. Thanks @JorgeBfor pointing me in the right direction.
-
Caddy from DockerHub help
Is there any fix yet? Or maybe an alternative for a simple web file server? Currently using Swag to host a static site, but that's less then elegant and Caddy seems a nice service worth learning.
-
UI keeps becoming unusable.
Uptime 3 days 5 hours 30 minutes Happy to still see it's all good. Couple more days and should be considered fixed.
-
[Support] Linuxserver.io - Nextcloud
Ok. So, when there is a docker update I should check to see if there is an update for the app first to prevent this in the future? Do I understand that right? EDIT: It's working again though with the downgrade fix.
-
[Support] Linuxserver.io - Nextcloud
Getting this, again! This version of Nextcloud is not compatible with PHP>=8.2. You are currently running 8.2.6. Why does this keep happening, did the downgrade and update cycle 2 months ago, now it's broken, again?
-
UI keeps becoming unusable.
In the process of re-seting up those tunnels. Will update. EDIT: I re-configured my most important tunnel (bitwarden), without a reverse proxy, updated the 'cloudflared' docker container to the latest, this is now up and running. No errors so far, will be adding more tunnels for more services. Now the test of time comes in to see if the problem with the UnraidUI is resolved. This video helped me along the way:
-
UI keeps becoming unusable.
I'll have a look over there. Update if I find something useful.
-
UI keeps becoming unusable.
Ok, any solution?
-
UI keeps becoming unusable.
This problem used to come after a few weeks uptime but now it happens after a few days. Shares are accessible, however the logs are not, SSH does not work. Only a reboot fixes it. I managed to snag a diagnostics when it happened last time, shows a lot of errors. Please advise, this is becoming very annoying. Please advise. fatsally-diagnostics-20230524-1934.zip
-
No data shows in GUI, graphql error in Console
Here's the log. syslog.1.txt
-
No data shows in GUI, graphql error in Console
Same issue for months. Happens at random intervals. Used to be weeks, now it's 2 days.
-
WebUI doesn't fully load sometimes
Any solution to this. This keeps happening after a few weeks. Only solution is a reboot.
-
WebUI doesn't fully load sometimes
Guess no one has this issue.