theGrok Posted August 10, 2023 Share Posted August 10, 2023 (edited) 41 minutes ago, itimpi said: You are being protected against the fact that moving files between a physical device and a User Share in the same command can lead to data loss so this option is not allowed by Dynamix File Manager. Instead try moving it from the ‘downloads’ User Share to the /Media User Share. If you must use the physical cache drive as the source then you need to select a physical target drive as well. Thank you for the info. That is helpful info. I did start my source from the /downloads user share from the shares tab, however despite this I see the source being /mnt/cache_download and not /mnt/user. Does this have to do with the fact that this share is set to a cache pool as the primary storage and NONE as the secondary? It defaults to the physical disk instead of /mnt/user/downloads as the source? Edited August 10, 2023 by theGrok Quote Link to comment
itimpi Posted August 10, 2023 Share Posted August 10, 2023 2 minutes ago, theGrok said: Thank you for the info. That is helpful info. I did start my source from the /downloads user share from the shares tab, however despite this I see the source being /mnt/cache_download and not /mnt/user. Does this have to do with the fact that this share is set to a cache pool as the primary storage and NONE as the secondary? It defaults to the physical disk instead of /mnt/user/downloads as the source? possible I guess. Might be a bug then in the Dynamix File Manager not correctly handling Exclusive shares. Quote Link to comment
Marcel Wolf Posted August 16, 2023 Share Posted August 16, 2023 (edited) Hello 🙂 Since yesterday i know about the feature of copy-processes showing the speed and remaining time in footer. I wondered if this feature is new because i didn't realize before. But in most cases i do not copy, i move data. And i think these informations are only available on rsync processes, not mv as it's used on moving data, am i right ? Thanks 🙂 Edited August 16, 2023 by Marcel Wolf Quote Link to comment
cyeilo Posted August 19, 2023 Share Posted August 19, 2023 On 6/29/2023 at 10:50 PM, bonienl said: Please update the chinese language pack to the latest version. Or remove the language pack and install again, this will automatically update to the latest version. works for me, thx! 实测有用 Quote Link to comment
leawhig Posted September 3, 2023 Share Posted September 3, 2023 Hi! I've run into a rather frustrating issue. Whenever I try to upload files using this plugin, no matter what I do, the uploaded files end up getting corrupted. What's even stranger is that the file size always becomes 2.1MB, and they can't be opened correctly. Quote Link to comment
leawhig Posted September 3, 2023 Share Posted September 3, 2023 Just now, wdnaser said: Hi! I've run into a rather frustrating issue. Whenever I try to upload files using this plugin, no matter what I do, the uploaded files end up getting corrupted. What's even stranger is that the file size always becomes 2.1MB, and they can't be opened correctly. The issue only seems to occur when I attempt to upload the same file again. This problem went unnoticed with my previous file uploads, which got corrupted as well. Quote Link to comment
Bushibot Posted September 4, 2023 Share Posted September 4, 2023 I have a big 7T copy running from an smb mount of my old stuff nas to the my new unraid share. I'm notting that other docker contains can't seem to write any data to the unraid share. Is this as intended? Is there a better way to do a large copy like this that won't lock my share for... umm days? It's slowing down my ability to setup torrents and other things that need access to some of the folders (that are not write targets). I have also had this process stop twice unexpectedly, little frustrating. Not sure where to fish for why. I do see some errors: Sep 4 01:21:16 nas-mass kernel: docker0: port 5(vethdb6cece) entered disabled state Sep 4 01:21:16 nas-mass kernel: veth1380de3: renamed from eth0 Sep 4 01:21:17 nas-mass kernel: docker0: port 5(vethdb6cece) entered disabled state Sep 4 01:21:17 nas-mass kernel: device vethdb6cece left promiscuous mode Sep 4 01:21:17 nas-mass kernel: docker0: port 5(vethdb6cece) entered disabled state Sep 4 01:24:09 nas-mass unassigned.devices: Removing configuration '//PLEXSTORE/Public'. Sep 4 01:26:37 nas-mass nginx: 2023/09/04 01:26:37 [error] 7577#7577: *80325 open() "/usr/local/emhttp/images/file-types.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/file-types.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Shares/Browse?dir=/mnt/user/T_Media" Sep 4 01:26:48 nas-mass nginx: 2023/09/04 01:26:48 [error] 7577#7577: *80310 open() "/usr/local/emhttp/images/file-types.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/file-types.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Shares/Browse?dir=/mnt%2Fuser" Sep 4 01:27:05 nas-mass nginx: 2023/09/04 01:27:05 [error] 7577#7577: *80325 open() "/usr/local/emhttp/images/ui-icons_222222_256x240.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/ui-icons_222222_256x240.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Shares/Browse?dir=/mnt%2Fuser" Sep 4 01:27:19 nas-mass nginx: 2023/09/04 01:27:19 [error] 7577#7577: *80325 open() "/usr/local/emhttp/images/file-types.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/file-types.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Shares/Browse?dir=%2Fmnt%2Fuser%2Fappdata" Sep 4 01:27:26 nas-mass nginx: 2023/09/04 01:27:26 [error] 7577#7577: *80325 open() "/usr/local/emhttp/images/file-types.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/file-types.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Shares/Browse?dir=%2Fmnt%2Fuser%2Fappdata%2Fbinhex-qbittorrentvpn" Sep 4 01:27:30 nas-mass nginx: 2023/09/04 01:27:30 [error] 7577#7577: *81249 open() "/usr/local/emhttp/images/file-types.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/file-types.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Shares/Browse?dir=%2Fmnt%2Fuser%2Fappdata%2Fbinhex-qbittorrentvpn%2FqBittorrent" Sep 4 01:27:47 nas-mass nginx: 2023/09/04 01:27:47 [error] 7577#7577: *80324 open() "/usr/local/emhttp/images/file-types.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/file-types.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Shares/Browse?dir=/mnt" Sep 4 01:28:03 nas-mass unassigned.devices: Mounting Remote Share '//192.168.1.90/Public'... Sep 4 01:28:03 nas-mass unassigned.devices: Mount SMB share '//192.168.1.90/Public' using SMB default protocol. Sep 4 01:28:03 nas-mass unassigned.devices: Mount SMB command: /sbin/mount -t 'cifs' -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,credentials='/tmp/unassigned.devices/credentials_192.168.1.90_Public' '//192.168.1.90/Public' '/mnt/remotes/192.168.1.90_Public' Sep 4 01:28:04 nas-mass kernel: Key type dns_resolver registered Sep 4 01:28:04 nas-mass kernel: Key type cifs.idmap registered Sep 4 01:28:04 nas-mass kernel: CIFS: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3.1.1), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3.1.1 (or even SMB3 or SMB2.1) specify vers=1.0 on mount. Sep 4 01:28:04 nas-mass kernel: CIFS: Attempting to mount \\192.168.1.90\Public Sep 4 01:28:04 nas-mass unassigned.devices: Successfully mounted '//192.168.1.90/Public' on '/mnt/remotes/192.168.1.90_Public'. Sep 4 01:28:04 nas-mass unassigned.devices: Device '//192.168.1.90/Public' is not set to be shared. Sep 4 01:28:10 nas-mass nginx: 2023/09/04 01:28:10 [error] 7577#7577: *81906 open() "/usr/local/emhttp/images/file-types.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/file-types.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Main/Browse?dir=/mnt/remotes/192.168.1.90_Public" Sep 4 01:28:17 nas-mass nginx: 2023/09/04 01:28:17 [error] 7577#7577: *81249 open() "/usr/local/emhttp/images/file-types.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/file-types.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Main/Browse?dir=%2Fmnt%2Fremotes%2F192.168.1.90_Public%2F.gallery" Sep 4 01:28:24 nas-mass nginx: 2023/09/04 01:28:24 [error] 7577#7577: *81066 open() "/usr/local/emhttp/images/file-types.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/file-types.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Main/Browse?dir=/mnt%2Fremotes%2F192.168.1.90_Public" Sep 4 01:29:08 nas-mass nginx: 2023/09/04 01:29:08 [error] 7577#7577: *82730 open() "/usr/local/emhttp/images/ui-icons_222222_256x240.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/ui-icons_222222_256x240.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Main/Browse?dir=/mnt%2Fremotes%2F192.168.1.90_Public" Sep 4 01:35:55 nas-mass kernel: docker0: port 4(veth7140fcd) entered disabled state Sep 4 01:35:55 nas-mass kernel: veth6acee59: renamed from eth0 Sep 4 01:35:55 nas-mass kernel: docker0: port 4(veth7140fcd) entered disabled state Sep 4 01:35:55 nas-mass kernel: device veth7140fcd left promiscuous mode Sep 4 01:35:55 nas-mass kernel: docker0: port 4(veth7140fcd) entered disabled state Sep 4 01:35:55 nas-mass kernel: docker0: port 4(veth32c8a55) entered blocking state Sep 4 01:35:55 nas-mass kernel: docker0: port 4(veth32c8a55) entered disabled state Sep 4 01:35:55 nas-mass kernel: device veth32c8a55 entered promiscuous mode Sep 4 01:35:55 nas-mass kernel: docker0: port 4(veth32c8a55) entered blocking state Sep 4 01:35:55 nas-mass kernel: docker0: port 4(veth32c8a55) entered forwarding state Sep 4 01:35:55 nas-mass kernel: eth0: renamed from veth40fef6f Sep 4 01:35:55 nas-mass kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth32c8a55: link becomes ready Sep 4 02:10:22 nas-mass kernel: hp[29934]: segfault at 28 ip 00001481bdd7bd29 sp 00007ffc8b6ca328 error 4 in ld-musl-x86_64.so.1[1481bdd3d000+48000] likely on CPU 6 (core 2, socket 0) Sep 4 02:10:22 nas-mass kernel: Code: e8 a8 16 00 00 31 c0 5a c3 31 c0 c3 b8 16 00 00 00 c3 b9 0a 00 00 00 31 c0 48 89 fa f3 ab 48 85 f6 74 04 8b 06 89 02 31 c0 c3 <8b> 07 83 e0 0f 74 07 31 f6 e9 15 00 00 00 ba 10 00 00 00 f0 0f b1 Sep 4 02:10:50 nas-mass kernel: hp[30739]: segfault at 28 ip 0000152f7d3a3d29 sp 00007ffecd5d34d8 error 4 in ld-musl-x86_64.so.1[152f7d365000+48000] likely on CPU 3 (core 3, socket 0) Sep 4 02:10:50 nas-mass kernel: Code: e8 a8 16 00 00 31 c0 5a c3 31 c0 c3 b8 16 00 00 00 c3 b9 0a 00 00 00 31 c0 48 89 fa f3 ab 48 85 f6 74 04 8b 06 89 02 31 c0 c3 <8b> 07 83 e0 0f 74 07 31 f6 e9 15 00 00 00 ba 10 00 00 00 f0 0f b1 Sep 4 02:11:43 nas-mass kernel: hp[32230]: segfault at 28 ip 000014b4378b8d29 sp 00007ffdc5707128 error 4 in ld-musl-x86_64.so.1[14b43787a000+48000] likely on CPU 7 (core 3, socket 0) Sep 4 02:11:43 nas-mass kernel: Code: e8 a8 16 00 00 31 c0 5a c3 31 c0 c3 b8 16 00 00 00 c3 b9 0a 00 00 00 31 c0 48 89 fa f3 ab 48 85 f6 74 04 8b 06 89 02 31 c0 c3 <8b> 07 83 e0 0f 74 07 31 f6 e9 15 00 00 00 ba 10 00 00 00 f0 0f b1 Sep 4 02:12:57 nas-mass kernel: docker0: port 5(veth2333498) entered blocking state Sep 4 02:12:57 nas-mass kernel: docker0: port 5(veth2333498) entered disabled state Sep 4 02:12:57 nas-mass kernel: device veth2333498 entered promiscuous mode Sep 4 02:12:57 nas-mass kernel: docker0: port 5(veth2333498) entered blocking state Sep 4 02:12:57 nas-mass kernel: docker0: port 5(veth2333498) entered forwarding state Sep 4 02:12:57 nas-mass kernel: docker0: port 5(veth2333498) entered disabled state Sep 4 02:12:58 nas-mass kernel: eth0: renamed from vethe87c871 Sep 4 02:12:58 nas-mass kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth2333498: link becomes ready Sep 4 02:12:58 nas-mass kernel: docker0: port 5(veth2333498) entered blocking state Sep 4 02:12:58 nas-mass kernel: docker0: port 5(veth2333498) entered forwarding state Sep 4 02:14:47 nas-mass kernel: docker0: port 5(veth2333498) entered disabled state Sep 4 02:14:47 nas-mass kernel: vethe87c871: renamed from eth0 Sep 4 02:14:47 nas-mass kernel: docker0: port 5(veth2333498) entered disabled state Sep 4 02:14:47 nas-mass kernel: device veth2333498 left promiscuous mode Sep 4 02:14:47 nas-mass kernel: docker0: port 5(veth2333498) entered disabled state Sep 4 02:16:23 nas-mass kernel: hp[7093]: segfault at 28 ip 0000146101f86d29 sp 00007ffc9803fe78 error 4 in ld-musl-x86_64.so.1[146101f48000+48000] likely on CPU 5 (core 1, socket 0) Sep 4 02:16:23 nas-mass kernel: Code: e8 a8 16 00 00 31 c0 5a c3 31 c0 c3 b8 16 00 00 00 c3 b9 0a 00 00 00 31 c0 48 89 fa f3 ab 48 85 f6 74 04 8b 06 89 02 31 c0 c3 <8b> 07 83 e0 0f 74 07 31 f6 e9 15 00 00 00 ba 10 00 00 00 f0 0f b1 Sep 4 02:18:18 nas-mass kernel: hp[10574]: segfault at 28 ip 00001499f8fb5d29 sp 00007fff6fccf188 error 4 in ld-musl-x86_64.so.1[1499f8f77000+48000] likely on CPU 0 (core 0, socket 0) Sep 4 02:18:18 nas-mass kernel: Code: e8 a8 16 00 00 31 c0 5a c3 31 c0 c3 b8 16 00 00 00 c3 b9 0a 00 00 00 31 c0 48 89 fa f3 ab 48 85 f6 74 04 8b 06 89 02 31 c0 c3 <8b> 07 83 e0 0f 74 07 31 f6 e9 15 00 00 00 ba 10 00 00 00 f0 0f b1 Sep 4 02:24:11 nas-mass kernel: hp[20512]: segfault at 28 ip 000014dcad753d29 sp 00007ffd761623e8 error 4 in ld-musl-x86_64.so.1[14dcad715000+48000] likely on CPU 4 (core 0, socket 0) Sep 4 02:24:11 nas-mass kernel: Code: e8 a8 16 00 00 31 c0 5a c3 31 c0 c3 b8 16 00 00 00 c3 b9 0a 00 00 00 31 c0 48 89 fa f3 ab 48 85 f6 74 04 8b 06 89 02 31 c0 c3 <8b> 07 83 e0 0f 74 07 31 f6 e9 15 00 00 00 ba 10 00 00 00 f0 0f b1 Sep 4 02:27:24 nas-mass kernel: hp[26270]: segfault at 28 ip 000014b383af2d29 sp 00007fff54e25e88 error 4 in ld-musl-x86_64.so.1[14b383ab4000+48000] likely on CPU 0 (core 0, socket 0) Sep 4 02:27:24 nas-mass kernel: Code: e8 a8 16 00 00 31 c0 5a c3 31 c0 c3 b8 16 00 00 00 c3 b9 0a 00 00 00 31 c0 48 89 fa f3 ab 48 85 f6 74 04 8b 06 89 02 31 c0 c3 <8b> 07 83 e0 0f 74 07 31 f6 e9 15 00 00 00 ba 10 00 00 00 f0 0f b1 Sep 4 02:41:27 nas-mass kernel: hp[17881]: segfault at 28 ip 000014c9d4c71d29 sp 00007ffcd9917e08 error 4 in ld-musl-x86_64.so.1[14c9d4c33000+48000] likely on CPU 6 (core 2, socket 0) Sep 4 02:41:27 nas-mass kernel: Code: e8 a8 16 00 00 31 c0 5a c3 31 c0 c3 b8 16 00 00 00 c3 b9 0a 00 00 00 31 c0 48 89 fa f3 ab 48 85 f6 74 04 8b 06 89 02 31 c0 c3 <8b> 07 83 e0 0f 74 07 31 f6 e9 15 00 00 00 ba 10 00 00 00 f0 0f b1 Sep 4 02:42:06 nas-mass monitor: Stop running nchan processes Sep 4 02:50:29 nas-mass sshd[21691]: Connection from 192.168.1.189 port 64510 on 192.168.1.99 port 22 rdomain "" Sep 4 02:50:29 nas-mass sshd[21691]: error: kex_exchange_identification: Connection closed by remote host Sep 4 02:50:29 nas-mass sshd[21691]: Connection closed by 192.168.1.189 port 64510 Sep 4 02:50:30 nas-mass sshd[21695]: Connection from 192.168.1.189 port 64513 on 192.168.1.99 port 22 rdomain "" Sep 4 02:50:34 nas-mass sshd[21695]: Connection closed by 192.168.1.189 port 64513 [preauth] Sep 4 02:50:34 nas-mass sshd[21722]: Connection from 192.168.1.189 port 64519 on 192.168.1.99 port 22 rdomain "" Sep 4 02:50:34 nas-mass sshd[21722]: Accepted password for root from 192.168.1.189 port 64519 ssh2 Sep 4 02:50:34 nas-mass sshd[21722]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0) Sep 4 02:50:34 nas-mass sshd[21722]: Starting session: shell on pts/0 for root from 192.168.1.189 port 64519 id 0 Sep 4 02:50:38 nas-mass sshd[21761]: Connection from 192.168.1.189 port 64522 on 192.168.1.99 port 22 rdomain "" Sep 4 02:50:38 nas-mass sshd[21761]: error: kex_exchange_identification: Connection closed by remote host Sep 4 02:50:38 nas-mass sshd[21761]: Connection closed by 192.168.1.189 port 64522 Sep 4 02:50:52 nas-mass sshd[21828]: Connection from 192.168.1.189 port 64533 on 192.168.1.99 port 22 rdomain "" Sep 4 02:50:52 nas-mass sshd[21828]: error: kex_exchange_identification: Connection closed by remote host Sep 4 02:50:52 nas-mass sshd[21828]: Connection closed by 192.168.1.189 port 64533 Sep 4 02:51:12 nas-mass sshd[21933]: Connection from 192.168.1.189 port 64544 on 192.168.1.99 port 22 rdomain "" Sep 4 02:51:12 nas-mass sshd[21933]: error: kex_exchange_identification: Connection closed by remote host Sep 4 02:51:12 nas-mass sshd[21933]: Connection closed by 192.168.1.189 port 64544 Sep 4 02:51:32 nas-mass sshd[22018]: Connection from 192.168.1.189 port 64555 on 192.168.1.99 port 22 rdomain "" Sep 4 02:51:32 nas-mass sshd[22018]: error: kex_exchange_identification: Connection closed by remote host Sep 4 02:51:32 nas-mass sshd[22018]: Connection closed by 192.168.1.189 port 64555 Sep 4 02:51:52 nas-mass sshd[22101]: Connection from 192.168.1.189 port 64566 on 192.168.1.99 port 22 rdomain "" Sep 4 02:51:52 nas-mass sshd[22101]: error: kex_exchange_identification: Connection closed by remote host Sep 4 02:51:52 nas-mass sshd[22101]: Connection closed by 192.168.1.189 port 64566 Sep 4 02:57:55 nas-mass sshd[25330]: Connection from 192.168.1.189 port 64578 on 192.168.1.99 port 22 rdomain "" Sep 4 02:57:55 nas-mass sshd[25330]: error: kex_exchange_identification: Connection closed by remote host Sep 4 02:57:55 nas-mass sshd[25330]: Connection closed by 192.168.1.189 port 64578 Sep 4 02:58:02 nas-mass sshd[25470]: Connection from 192.168.1.189 port 64587 on 192.168.1.99 port 22 rdomain "" Sep 4 02:58:02 nas-mass sshd[25470]: error: kex_exchange_identification: Connection closed by remote host Sep 4 02:58:02 nas-mass sshd[25470]: Connection closed by 192.168.1.189 port 64587 Sep 4 02:58:22 nas-mass sshd[25597]: Connection from 192.168.1.189 port 64599 on 192.168.1.99 port 22 rdomain "" Sep 4 02:58:22 nas-mass sshd[25597]: error: kex_exchange_identification: Connection closed by remote host Sep 4 02:58:22 nas-mass sshd[25597]: Connection closed by 192.168.1.189 port 64599 Sep 4 02:58:39 nas-mass monitor: Stop running nchan processes Sep 4 02:58:42 nas-mass sshd[25792]: Connection from 192.168.1.189 port 64610 on 192.168.1.99 port 22 rdomain "" Sep 4 02:58:42 nas-mass sshd[25792]: error: kex_exchange_identification: Connection closed by remote host Sep 4 02:58:42 nas-mass sshd[25792]: Connection closed by 192.168.1.189 port 64610 Sep 4 02:59:02 nas-mass sshd[25901]: Connection from 192.168.1.189 port 64621 on 192.168.1.99 port 22 rdomain "" Sep 4 02:59:02 nas-mass sshd[25901]: error: kex_exchange_identification: Connection closed by remote host Sep 4 02:59:02 nas-mass sshd[25901]: Connection closed by 192.168.1.189 port 64621 Sep 4 02:59:22 nas-mass sshd[25988]: Connection from 192.168.1.189 port 64632 on 192.168.1.99 port 22 rdomain "" Sep 4 02:59:22 nas-mass sshd[25988]: error: kex_exchange_identification: Connection closed by remote host Sep 4 02:59:22 nas-mass sshd[25988]: Connection closed by 192.168.1.189 port 64632 Sep 4 02:59:42 nas-mass sshd[26058]: Connection from 192.168.1.189 port 64643 on 192.168.1.99 port 22 rdomain "" Sep 4 02:59:42 nas-mass sshd[26058]: error: kex_exchange_identification: Connection closed by remote host Sep 4 02:59:42 nas-mass sshd[26058]: Connection closed by 192.168.1.189 port 64643 Sep 4 03:08:37 nas-mass sshd[21722]: Connection closed by 192.168.1.189 port 64519 Sep 4 03:08:37 nas-mass sshd[21722]: Close session: user root from 192.168.1.189 port 64519 id 0 Sep 4 03:08:37 nas-mass sshd[21722]: pam_unix(sshd:session): session closed for user root Sep 4 03:08:37 nas-mass sshd[21722]: pam_elogind(sshd:session): Failed to release session: Interrupted system call Sep 4 03:08:37 nas-mass sshd[21722]: Transferred: sent 9916, received 6260 bytes Sep 4 03:08:37 nas-mass sshd[21722]: Closing connection to 192.168.1.189 port 64519 Sep 4 11:22:43 nas-mass nginx: 2023/09/04 11:22:43 [error] 7577#7577: *251337 open() "/usr/local/emhttp/images/file-types.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/file-types.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Shares/Browse?dir=/mnt/user/Datapool" Sep 4 11:23:05 nas-mass nginx: 2023/09/04 11:23:05 [error] 7577#7577: *251735 open() "/usr/local/emhttp/images/file-types.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/file-types.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Shares/Browse?dir=%2Fmnt%2Fuser%2FDatapool%2FAnime" Sep 4 11:23:12 nas-mass nginx: 2023/09/04 11:23:12 [error] 7577#7577: *251336 open() "/usr/local/emhttp/images/file-types.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/file-types.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Shares/Browse?dir=/mnt/user/Datapool" Sep 4 11:23:18 nas-mass nginx: 2023/09/04 11:23:18 [error] 7577#7577: *251336 open() "/usr/local/emhttp/images/file-types.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/file-types.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Shares/Browse?dir=%2Fmnt%2Fuser%2FDatapool%2Fsshkeys" Sep 4 11:23:20 nas-mass nginx: 2023/09/04 11:23:20 [error] 7577#7577: *251336 open() "/usr/local/emhttp/images/file-types.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/file-types.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Shares/Browse?dir=/mnt/user/Datapool" Sep 4 11:24:25 nas-mass nginx: 2023/09/04 11:24:25 [error] 7577#7577: *253049 open() "/usr/local/emhttp/images/file-types.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/file-types.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Shares/Browse?dir=%2Fmnt%2Fuser%2FDatapool%2FMA%20training%20reference" Sep 4 11:35:25 nas-mass ool www[17084]: /usr/local/emhttp/plugins/dynamix/scripts/rsyslog_config Sep 4 11:35:27 nas-mass rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="17149" x-info="https://www.rsyslog.com"] start Sep 4 11:47:34 nas-mass kernel: docker0: port 4(veth32c8a55) entered disabled state Sep 4 11:47:34 nas-mass kernel: veth40fef6f: renamed from eth0 Sep 4 11:47:34 nas-mass kernel: docker0: port 4(veth32c8a55) entered disabled state Sep 4 11:47:34 nas-mass kernel: device veth32c8a55 left promiscuous mode Sep 4 11:47:34 nas-mass kernel: docker0: port 4(veth32c8a55) entered disabled state Sep 4 11:47:36 nas-mass kernel: docker0: port 4(veth8e4db53) entered blocking state Sep 4 11:47:36 nas-mass kernel: docker0: port 4(veth8e4db53) entered disabled state Sep 4 11:47:36 nas-mass kernel: device veth8e4db53 entered promiscuous mode Sep 4 11:47:37 nas-mass kernel: eth0: renamed from veth8b387b8 Sep 4 11:47:37 nas-mass kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth8e4db53: link becomes ready Sep 4 11:47:37 nas-mass kernel: docker0: port 4(veth8e4db53) entered blocking state Sep 4 11:47:37 nas-mass kernel: docker0: port 4(veth8e4db53) entered forwarding state Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.044831, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.046206, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.047633, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.049217, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.050438, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.051586, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.052621, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.053609, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.232696, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.234060, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.235245, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.236436, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.237603, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.238596, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.302731, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.303732, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.304675, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.305578, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.306487, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.307372, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.308314, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.309191, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.333881, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.335332, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.336585, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.337819, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.339026, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.340279, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.341898, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.375225, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.376231, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.377275, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.378200, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.404282, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.405382, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.406433, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.407559, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.408552, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.409503, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.410470, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:57:06 nas-mass kernel: docker0: port 3(veth1304500) entered disabled state Sep 4 11:57:06 nas-mass kernel: vethc85e8f4: renamed from eth0 Sep 4 11:57:06 nas-mass kernel: docker0: port 3(veth1304500) entered disabled state Sep 4 11:57:06 nas-mass kernel: device veth1304500 left promiscuous mode Sep 4 11:57:06 nas-mass kernel: docker0: port 3(veth1304500) entered disabled state Sep 4 11:57:06 nas-mass kernel: docker0: port 3(veth1637733) entered blocking state Sep 4 11:57:06 nas-mass kernel: docker0: port 3(veth1637733) entered disabled state Sep 4 11:57:06 nas-mass kernel: device veth1637733 entered promiscuous mode Sep 4 11:57:06 nas-mass kernel: docker0: port 3(veth1637733) entered blocking state Sep 4 11:57:06 nas-mass kernel: docker0: port 3(veth1637733) entered forwarding state Sep 4 11:57:07 nas-mass kernel: eth0: renamed from vetheee5eca Sep 4 11:57:07 nas-mass kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth1637733: link becomes ready Sep 4 11:57:17 nas-mass kernel: docker0: port 3(veth1637733) entered disabled state Sep 4 11:57:17 nas-mass kernel: vetheee5eca: renamed from eth0 Sep 4 11:57:17 nas-mass kernel: docker0: port 3(veth1637733) entered disabled state Sep 4 11:57:17 nas-mass kernel: device veth1637733 left promiscuous mode Sep 4 11:57:17 nas-mass kernel: docker0: port 3(veth1637733) entered disabled state Sep 4 11:57:37 nas-mass kernel: docker0: port 3(veth1842340) entered blocking state Sep 4 11:57:37 nas-mass kernel: docker0: port 3(veth1842340) entered disabled state Sep 4 11:57:37 nas-mass kernel: device veth1842340 entered promiscuous mode Sep 4 11:57:38 nas-mass kernel: eth0: renamed from veth495f9aa Sep 4 11:57:38 nas-mass kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth1842340: link becomes ready Sep 4 11:57:38 nas-mass kernel: docker0: port 3(veth1842340) entered blocking state Sep 4 11:57:38 nas-mass kernel: docker0: port 3(veth1842340) entered forwarding state Sep 4 11:58:46 nas-mass kernel: docker0: port 3(veth1842340) entered disabled state Sep 4 11:58:46 nas-mass kernel: veth495f9aa: renamed from eth0 Sep 4 11:58:46 nas-mass kernel: docker0: port 3(veth1842340) entered disabled state Sep 4 11:58:46 nas-mass kernel: device veth1842340 left promiscuous mode Sep 4 11:58:46 nas-mass kernel: docker0: port 3(veth1842340) entered disabled state Sep 4 11:59:01 nas-mass kernel: docker0: port 3(vethbec5965) entered blocking state Sep 4 11:59:01 nas-mass kernel: docker0: port 3(vethbec5965) entered disabled state Sep 4 11:59:01 nas-mass kernel: device vethbec5965 entered promiscuous mode Sep 4 11:59:01 nas-mass kernel: docker0: port 3(vethbec5965) entered blocking state Sep 4 11:59:01 nas-mass kernel: docker0: port 3(vethbec5965) entered forwarding state Sep 4 11:59:01 nas-mass kernel: docker0: port 3(vethbec5965) entered disabled state Sep 4 11:59:01 nas-mass kernel: eth0: renamed from veth54082bc Sep 4 11:59:01 nas-mass kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethbec5965: link becomes ready Sep 4 11:59:01 nas-mass kernel: docker0: port 3(vethbec5965) entered blocking state Sep 4 11:59:01 nas-mass kernel: docker0: port 3(vethbec5965) entered forwarding state Sep 4 12:25:18 nas-mass monitor: Stop running nchan processes Sep 4 14:24:53 nas-mass monitor: Stop running nchan processes nas-mass-syslog-20230904-2355.zip Quote Link to comment
Bushibot Posted September 5, 2023 Share Posted September 5, 2023 41 minutes ago, Bushibot said: I have a big 7T copy running from an smb mount of my old stuff nas to the my new unraid share. I'm notting that other docker contains can't seem to write any data to the unraid share. Is this as intended? Is there a better way to do a large copy like this that won't lock my share for... umm days? It's slowing down my ability to setup torrents and other things that need access to some of the folders (that are not write targets). I have also had this process stop twice unexpectedly, little frustrating. Not sure where to fish for why. I do see some errors: Sep 4 01:21:16 nas-mass kernel: docker0: port 5(vethdb6cece) entered disabled state Sep 4 01:21:16 nas-mass kernel: veth1380de3: renamed from eth0 Sep 4 01:21:17 nas-mass kernel: docker0: port 5(vethdb6cece) entered disabled state Sep 4 01:21:17 nas-mass kernel: device vethdb6cece left promiscuous mode Sep 4 01:21:17 nas-mass kernel: docker0: port 5(vethdb6cece) entered disabled state Sep 4 01:24:09 nas-mass unassigned.devices: Removing configuration '//PLEXSTORE/Public'. Sep 4 01:26:37 nas-mass nginx: 2023/09/04 01:26:37 [error] 7577#7577: *80325 open() "/usr/local/emhttp/images/file-types.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/file-types.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Shares/Browse?dir=/mnt/user/T_Media" Sep 4 01:26:48 nas-mass nginx: 2023/09/04 01:26:48 [error] 7577#7577: *80310 open() "/usr/local/emhttp/images/file-types.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/file-types.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Shares/Browse?dir=/mnt%2Fuser" Sep 4 01:27:05 nas-mass nginx: 2023/09/04 01:27:05 [error] 7577#7577: *80325 open() "/usr/local/emhttp/images/ui-icons_222222_256x240.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/ui-icons_222222_256x240.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Shares/Browse?dir=/mnt%2Fuser" Sep 4 01:27:19 nas-mass nginx: 2023/09/04 01:27:19 [error] 7577#7577: *80325 open() "/usr/local/emhttp/images/file-types.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/file-types.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Shares/Browse?dir=%2Fmnt%2Fuser%2Fappdata" Sep 4 01:27:26 nas-mass nginx: 2023/09/04 01:27:26 [error] 7577#7577: *80325 open() "/usr/local/emhttp/images/file-types.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/file-types.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Shares/Browse?dir=%2Fmnt%2Fuser%2Fappdata%2Fbinhex-qbittorrentvpn" Sep 4 01:27:30 nas-mass nginx: 2023/09/04 01:27:30 [error] 7577#7577: *81249 open() "/usr/local/emhttp/images/file-types.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/file-types.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Shares/Browse?dir=%2Fmnt%2Fuser%2Fappdata%2Fbinhex-qbittorrentvpn%2FqBittorrent" Sep 4 01:27:47 nas-mass nginx: 2023/09/04 01:27:47 [error] 7577#7577: *80324 open() "/usr/local/emhttp/images/file-types.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/file-types.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Shares/Browse?dir=/mnt" Sep 4 01:28:03 nas-mass unassigned.devices: Mounting Remote Share '//192.168.1.90/Public'... Sep 4 01:28:03 nas-mass unassigned.devices: Mount SMB share '//192.168.1.90/Public' using SMB default protocol. Sep 4 01:28:03 nas-mass unassigned.devices: Mount SMB command: /sbin/mount -t 'cifs' -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,credentials='/tmp/unassigned.devices/credentials_192.168.1.90_Public' '//192.168.1.90/Public' '/mnt/remotes/192.168.1.90_Public' Sep 4 01:28:04 nas-mass kernel: Key type dns_resolver registered Sep 4 01:28:04 nas-mass kernel: Key type cifs.idmap registered Sep 4 01:28:04 nas-mass kernel: CIFS: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3.1.1), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3.1.1 (or even SMB3 or SMB2.1) specify vers=1.0 on mount. Sep 4 01:28:04 nas-mass kernel: CIFS: Attempting to mount \\192.168.1.90\Public Sep 4 01:28:04 nas-mass unassigned.devices: Successfully mounted '//192.168.1.90/Public' on '/mnt/remotes/192.168.1.90_Public'. Sep 4 01:28:04 nas-mass unassigned.devices: Device '//192.168.1.90/Public' is not set to be shared. Sep 4 01:28:10 nas-mass nginx: 2023/09/04 01:28:10 [error] 7577#7577: *81906 open() "/usr/local/emhttp/images/file-types.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/file-types.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Main/Browse?dir=/mnt/remotes/192.168.1.90_Public" Sep 4 01:28:17 nas-mass nginx: 2023/09/04 01:28:17 [error] 7577#7577: *81249 open() "/usr/local/emhttp/images/file-types.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/file-types.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Main/Browse?dir=%2Fmnt%2Fremotes%2F192.168.1.90_Public%2F.gallery" Sep 4 01:28:24 nas-mass nginx: 2023/09/04 01:28:24 [error] 7577#7577: *81066 open() "/usr/local/emhttp/images/file-types.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/file-types.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Main/Browse?dir=/mnt%2Fremotes%2F192.168.1.90_Public" Sep 4 01:29:08 nas-mass nginx: 2023/09/04 01:29:08 [error] 7577#7577: *82730 open() "/usr/local/emhttp/images/ui-icons_222222_256x240.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/ui-icons_222222_256x240.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Main/Browse?dir=/mnt%2Fremotes%2F192.168.1.90_Public" Sep 4 01:35:55 nas-mass kernel: docker0: port 4(veth7140fcd) entered disabled state Sep 4 01:35:55 nas-mass kernel: veth6acee59: renamed from eth0 Sep 4 01:35:55 nas-mass kernel: docker0: port 4(veth7140fcd) entered disabled state Sep 4 01:35:55 nas-mass kernel: device veth7140fcd left promiscuous mode Sep 4 01:35:55 nas-mass kernel: docker0: port 4(veth7140fcd) entered disabled state Sep 4 01:35:55 nas-mass kernel: docker0: port 4(veth32c8a55) entered blocking state Sep 4 01:35:55 nas-mass kernel: docker0: port 4(veth32c8a55) entered disabled state Sep 4 01:35:55 nas-mass kernel: device veth32c8a55 entered promiscuous mode Sep 4 01:35:55 nas-mass kernel: docker0: port 4(veth32c8a55) entered blocking state Sep 4 01:35:55 nas-mass kernel: docker0: port 4(veth32c8a55) entered forwarding state Sep 4 01:35:55 nas-mass kernel: eth0: renamed from veth40fef6f Sep 4 01:35:55 nas-mass kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth32c8a55: link becomes ready Sep 4 02:10:22 nas-mass kernel: hp[29934]: segfault at 28 ip 00001481bdd7bd29 sp 00007ffc8b6ca328 error 4 in ld-musl-x86_64.so.1[1481bdd3d000+48000] likely on CPU 6 (core 2, socket 0) Sep 4 02:10:22 nas-mass kernel: Code: e8 a8 16 00 00 31 c0 5a c3 31 c0 c3 b8 16 00 00 00 c3 b9 0a 00 00 00 31 c0 48 89 fa f3 ab 48 85 f6 74 04 8b 06 89 02 31 c0 c3 <8b> 07 83 e0 0f 74 07 31 f6 e9 15 00 00 00 ba 10 00 00 00 f0 0f b1 Sep 4 02:10:50 nas-mass kernel: hp[30739]: segfault at 28 ip 0000152f7d3a3d29 sp 00007ffecd5d34d8 error 4 in ld-musl-x86_64.so.1[152f7d365000+48000] likely on CPU 3 (core 3, socket 0) Sep 4 02:10:50 nas-mass kernel: Code: e8 a8 16 00 00 31 c0 5a c3 31 c0 c3 b8 16 00 00 00 c3 b9 0a 00 00 00 31 c0 48 89 fa f3 ab 48 85 f6 74 04 8b 06 89 02 31 c0 c3 <8b> 07 83 e0 0f 74 07 31 f6 e9 15 00 00 00 ba 10 00 00 00 f0 0f b1 Sep 4 02:11:43 nas-mass kernel: hp[32230]: segfault at 28 ip 000014b4378b8d29 sp 00007ffdc5707128 error 4 in ld-musl-x86_64.so.1[14b43787a000+48000] likely on CPU 7 (core 3, socket 0) Sep 4 02:11:43 nas-mass kernel: Code: e8 a8 16 00 00 31 c0 5a c3 31 c0 c3 b8 16 00 00 00 c3 b9 0a 00 00 00 31 c0 48 89 fa f3 ab 48 85 f6 74 04 8b 06 89 02 31 c0 c3 <8b> 07 83 e0 0f 74 07 31 f6 e9 15 00 00 00 ba 10 00 00 00 f0 0f b1 Sep 4 02:12:57 nas-mass kernel: docker0: port 5(veth2333498) entered blocking state Sep 4 02:12:57 nas-mass kernel: docker0: port 5(veth2333498) entered disabled state Sep 4 02:12:57 nas-mass kernel: device veth2333498 entered promiscuous mode Sep 4 02:12:57 nas-mass kernel: docker0: port 5(veth2333498) entered blocking state Sep 4 02:12:57 nas-mass kernel: docker0: port 5(veth2333498) entered forwarding state Sep 4 02:12:57 nas-mass kernel: docker0: port 5(veth2333498) entered disabled state Sep 4 02:12:58 nas-mass kernel: eth0: renamed from vethe87c871 Sep 4 02:12:58 nas-mass kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth2333498: link becomes ready Sep 4 02:12:58 nas-mass kernel: docker0: port 5(veth2333498) entered blocking state Sep 4 02:12:58 nas-mass kernel: docker0: port 5(veth2333498) entered forwarding state Sep 4 02:14:47 nas-mass kernel: docker0: port 5(veth2333498) entered disabled state Sep 4 02:14:47 nas-mass kernel: vethe87c871: renamed from eth0 Sep 4 02:14:47 nas-mass kernel: docker0: port 5(veth2333498) entered disabled state Sep 4 02:14:47 nas-mass kernel: device veth2333498 left promiscuous mode Sep 4 02:14:47 nas-mass kernel: docker0: port 5(veth2333498) entered disabled state Sep 4 02:16:23 nas-mass kernel: hp[7093]: segfault at 28 ip 0000146101f86d29 sp 00007ffc9803fe78 error 4 in ld-musl-x86_64.so.1[146101f48000+48000] likely on CPU 5 (core 1, socket 0) Sep 4 02:16:23 nas-mass kernel: Code: e8 a8 16 00 00 31 c0 5a c3 31 c0 c3 b8 16 00 00 00 c3 b9 0a 00 00 00 31 c0 48 89 fa f3 ab 48 85 f6 74 04 8b 06 89 02 31 c0 c3 <8b> 07 83 e0 0f 74 07 31 f6 e9 15 00 00 00 ba 10 00 00 00 f0 0f b1 Sep 4 02:18:18 nas-mass kernel: hp[10574]: segfault at 28 ip 00001499f8fb5d29 sp 00007fff6fccf188 error 4 in ld-musl-x86_64.so.1[1499f8f77000+48000] likely on CPU 0 (core 0, socket 0) Sep 4 02:18:18 nas-mass kernel: Code: e8 a8 16 00 00 31 c0 5a c3 31 c0 c3 b8 16 00 00 00 c3 b9 0a 00 00 00 31 c0 48 89 fa f3 ab 48 85 f6 74 04 8b 06 89 02 31 c0 c3 <8b> 07 83 e0 0f 74 07 31 f6 e9 15 00 00 00 ba 10 00 00 00 f0 0f b1 Sep 4 02:24:11 nas-mass kernel: hp[20512]: segfault at 28 ip 000014dcad753d29 sp 00007ffd761623e8 error 4 in ld-musl-x86_64.so.1[14dcad715000+48000] likely on CPU 4 (core 0, socket 0) Sep 4 02:24:11 nas-mass kernel: Code: e8 a8 16 00 00 31 c0 5a c3 31 c0 c3 b8 16 00 00 00 c3 b9 0a 00 00 00 31 c0 48 89 fa f3 ab 48 85 f6 74 04 8b 06 89 02 31 c0 c3 <8b> 07 83 e0 0f 74 07 31 f6 e9 15 00 00 00 ba 10 00 00 00 f0 0f b1 Sep 4 02:27:24 nas-mass kernel: hp[26270]: segfault at 28 ip 000014b383af2d29 sp 00007fff54e25e88 error 4 in ld-musl-x86_64.so.1[14b383ab4000+48000] likely on CPU 0 (core 0, socket 0) Sep 4 02:27:24 nas-mass kernel: Code: e8 a8 16 00 00 31 c0 5a c3 31 c0 c3 b8 16 00 00 00 c3 b9 0a 00 00 00 31 c0 48 89 fa f3 ab 48 85 f6 74 04 8b 06 89 02 31 c0 c3 <8b> 07 83 e0 0f 74 07 31 f6 e9 15 00 00 00 ba 10 00 00 00 f0 0f b1 Sep 4 02:41:27 nas-mass kernel: hp[17881]: segfault at 28 ip 000014c9d4c71d29 sp 00007ffcd9917e08 error 4 in ld-musl-x86_64.so.1[14c9d4c33000+48000] likely on CPU 6 (core 2, socket 0) Sep 4 02:41:27 nas-mass kernel: Code: e8 a8 16 00 00 31 c0 5a c3 31 c0 c3 b8 16 00 00 00 c3 b9 0a 00 00 00 31 c0 48 89 fa f3 ab 48 85 f6 74 04 8b 06 89 02 31 c0 c3 <8b> 07 83 e0 0f 74 07 31 f6 e9 15 00 00 00 ba 10 00 00 00 f0 0f b1 Sep 4 02:42:06 nas-mass monitor: Stop running nchan processes Sep 4 02:50:29 nas-mass sshd[21691]: Connection from 192.168.1.189 port 64510 on 192.168.1.99 port 22 rdomain "" Sep 4 02:50:29 nas-mass sshd[21691]: error: kex_exchange_identification: Connection closed by remote host Sep 4 02:50:29 nas-mass sshd[21691]: Connection closed by 192.168.1.189 port 64510 Sep 4 02:50:30 nas-mass sshd[21695]: Connection from 192.168.1.189 port 64513 on 192.168.1.99 port 22 rdomain "" Sep 4 02:50:34 nas-mass sshd[21695]: Connection closed by 192.168.1.189 port 64513 [preauth] Sep 4 02:50:34 nas-mass sshd[21722]: Connection from 192.168.1.189 port 64519 on 192.168.1.99 port 22 rdomain "" Sep 4 02:50:34 nas-mass sshd[21722]: Accepted password for root from 192.168.1.189 port 64519 ssh2 Sep 4 02:50:34 nas-mass sshd[21722]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0) Sep 4 02:50:34 nas-mass sshd[21722]: Starting session: shell on pts/0 for root from 192.168.1.189 port 64519 id 0 Sep 4 02:50:38 nas-mass sshd[21761]: Connection from 192.168.1.189 port 64522 on 192.168.1.99 port 22 rdomain "" Sep 4 02:50:38 nas-mass sshd[21761]: error: kex_exchange_identification: Connection closed by remote host Sep 4 02:50:38 nas-mass sshd[21761]: Connection closed by 192.168.1.189 port 64522 Sep 4 02:50:52 nas-mass sshd[21828]: Connection from 192.168.1.189 port 64533 on 192.168.1.99 port 22 rdomain "" Sep 4 02:50:52 nas-mass sshd[21828]: error: kex_exchange_identification: Connection closed by remote host Sep 4 02:50:52 nas-mass sshd[21828]: Connection closed by 192.168.1.189 port 64533 Sep 4 02:51:12 nas-mass sshd[21933]: Connection from 192.168.1.189 port 64544 on 192.168.1.99 port 22 rdomain "" Sep 4 02:51:12 nas-mass sshd[21933]: error: kex_exchange_identification: Connection closed by remote host Sep 4 02:51:12 nas-mass sshd[21933]: Connection closed by 192.168.1.189 port 64544 Sep 4 02:51:32 nas-mass sshd[22018]: Connection from 192.168.1.189 port 64555 on 192.168.1.99 port 22 rdomain "" Sep 4 02:51:32 nas-mass sshd[22018]: error: kex_exchange_identification: Connection closed by remote host Sep 4 02:51:32 nas-mass sshd[22018]: Connection closed by 192.168.1.189 port 64555 Sep 4 02:51:52 nas-mass sshd[22101]: Connection from 192.168.1.189 port 64566 on 192.168.1.99 port 22 rdomain "" Sep 4 02:51:52 nas-mass sshd[22101]: error: kex_exchange_identification: Connection closed by remote host Sep 4 02:51:52 nas-mass sshd[22101]: Connection closed by 192.168.1.189 port 64566 Sep 4 02:57:55 nas-mass sshd[25330]: Connection from 192.168.1.189 port 64578 on 192.168.1.99 port 22 rdomain "" Sep 4 02:57:55 nas-mass sshd[25330]: error: kex_exchange_identification: Connection closed by remote host Sep 4 02:57:55 nas-mass sshd[25330]: Connection closed by 192.168.1.189 port 64578 Sep 4 02:58:02 nas-mass sshd[25470]: Connection from 192.168.1.189 port 64587 on 192.168.1.99 port 22 rdomain "" Sep 4 02:58:02 nas-mass sshd[25470]: error: kex_exchange_identification: Connection closed by remote host Sep 4 02:58:02 nas-mass sshd[25470]: Connection closed by 192.168.1.189 port 64587 Sep 4 02:58:22 nas-mass sshd[25597]: Connection from 192.168.1.189 port 64599 on 192.168.1.99 port 22 rdomain "" Sep 4 02:58:22 nas-mass sshd[25597]: error: kex_exchange_identification: Connection closed by remote host Sep 4 02:58:22 nas-mass sshd[25597]: Connection closed by 192.168.1.189 port 64599 Sep 4 02:58:39 nas-mass monitor: Stop running nchan processes Sep 4 02:58:42 nas-mass sshd[25792]: Connection from 192.168.1.189 port 64610 on 192.168.1.99 port 22 rdomain "" Sep 4 02:58:42 nas-mass sshd[25792]: error: kex_exchange_identification: Connection closed by remote host Sep 4 02:58:42 nas-mass sshd[25792]: Connection closed by 192.168.1.189 port 64610 Sep 4 02:59:02 nas-mass sshd[25901]: Connection from 192.168.1.189 port 64621 on 192.168.1.99 port 22 rdomain "" Sep 4 02:59:02 nas-mass sshd[25901]: error: kex_exchange_identification: Connection closed by remote host Sep 4 02:59:02 nas-mass sshd[25901]: Connection closed by 192.168.1.189 port 64621 Sep 4 02:59:22 nas-mass sshd[25988]: Connection from 192.168.1.189 port 64632 on 192.168.1.99 port 22 rdomain "" Sep 4 02:59:22 nas-mass sshd[25988]: error: kex_exchange_identification: Connection closed by remote host Sep 4 02:59:22 nas-mass sshd[25988]: Connection closed by 192.168.1.189 port 64632 Sep 4 02:59:42 nas-mass sshd[26058]: Connection from 192.168.1.189 port 64643 on 192.168.1.99 port 22 rdomain "" Sep 4 02:59:42 nas-mass sshd[26058]: error: kex_exchange_identification: Connection closed by remote host Sep 4 02:59:42 nas-mass sshd[26058]: Connection closed by 192.168.1.189 port 64643 Sep 4 03:08:37 nas-mass sshd[21722]: Connection closed by 192.168.1.189 port 64519 Sep 4 03:08:37 nas-mass sshd[21722]: Close session: user root from 192.168.1.189 port 64519 id 0 Sep 4 03:08:37 nas-mass sshd[21722]: pam_unix(sshd:session): session closed for user root Sep 4 03:08:37 nas-mass sshd[21722]: pam_elogind(sshd:session): Failed to release session: Interrupted system call Sep 4 03:08:37 nas-mass sshd[21722]: Transferred: sent 9916, received 6260 bytes Sep 4 03:08:37 nas-mass sshd[21722]: Closing connection to 192.168.1.189 port 64519 Sep 4 11:22:43 nas-mass nginx: 2023/09/04 11:22:43 [error] 7577#7577: *251337 open() "/usr/local/emhttp/images/file-types.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/file-types.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Shares/Browse?dir=/mnt/user/Datapool" Sep 4 11:23:05 nas-mass nginx: 2023/09/04 11:23:05 [error] 7577#7577: *251735 open() "/usr/local/emhttp/images/file-types.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/file-types.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Shares/Browse?dir=%2Fmnt%2Fuser%2FDatapool%2FAnime" Sep 4 11:23:12 nas-mass nginx: 2023/09/04 11:23:12 [error] 7577#7577: *251336 open() "/usr/local/emhttp/images/file-types.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/file-types.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Shares/Browse?dir=/mnt/user/Datapool" Sep 4 11:23:18 nas-mass nginx: 2023/09/04 11:23:18 [error] 7577#7577: *251336 open() "/usr/local/emhttp/images/file-types.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/file-types.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Shares/Browse?dir=%2Fmnt%2Fuser%2FDatapool%2Fsshkeys" Sep 4 11:23:20 nas-mass nginx: 2023/09/04 11:23:20 [error] 7577#7577: *251336 open() "/usr/local/emhttp/images/file-types.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/file-types.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Shares/Browse?dir=/mnt/user/Datapool" Sep 4 11:24:25 nas-mass nginx: 2023/09/04 11:24:25 [error] 7577#7577: *253049 open() "/usr/local/emhttp/images/file-types.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.169, server: , request: "GET /images/file-types.png HTTP/1.1", host: "nas-mass.local", referrer: "http://nas-mass.local/Shares/Browse?dir=%2Fmnt%2Fuser%2FDatapool%2FMA%20training%20reference" Sep 4 11:35:25 nas-mass ool www[17084]: /usr/local/emhttp/plugins/dynamix/scripts/rsyslog_config Sep 4 11:35:27 nas-mass rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="17149" x-info="https://www.rsyslog.com"] start Sep 4 11:47:34 nas-mass kernel: docker0: port 4(veth32c8a55) entered disabled state Sep 4 11:47:34 nas-mass kernel: veth40fef6f: renamed from eth0 Sep 4 11:47:34 nas-mass kernel: docker0: port 4(veth32c8a55) entered disabled state Sep 4 11:47:34 nas-mass kernel: device veth32c8a55 left promiscuous mode Sep 4 11:47:34 nas-mass kernel: docker0: port 4(veth32c8a55) entered disabled state Sep 4 11:47:36 nas-mass kernel: docker0: port 4(veth8e4db53) entered blocking state Sep 4 11:47:36 nas-mass kernel: docker0: port 4(veth8e4db53) entered disabled state Sep 4 11:47:36 nas-mass kernel: device veth8e4db53 entered promiscuous mode Sep 4 11:47:37 nas-mass kernel: eth0: renamed from veth8b387b8 Sep 4 11:47:37 nas-mass kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth8e4db53: link becomes ready Sep 4 11:47:37 nas-mass kernel: docker0: port 4(veth8e4db53) entered blocking state Sep 4 11:47:37 nas-mass kernel: docker0: port 4(veth8e4db53) entered forwarding state Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.044831, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.046206, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.047633, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.049217, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.050438, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.051586, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.052621, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.053609, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.232696, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.234060, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.235245, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.236436, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.237603, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.238596, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.302731, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.303732, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.304675, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.305578, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.306487, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.307372, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.308314, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.309191, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.333881, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.335332, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.336585, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.337819, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.339026, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.340279, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.341898, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.375225, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.376231, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.377275, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.378200, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.404282, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.405382, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.406433, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.407559, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.408552, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.409503, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:48:50 nas-mass smbd[9745]: [2023/09/04 11:48:50.410470, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Sep 4 11:48:50 nas-mass smbd[9745]: make_connection_snum: canonicalize_connect_path failed for service download, path /mnt/user/download Sep 4 11:57:06 nas-mass kernel: docker0: port 3(veth1304500) entered disabled state Sep 4 11:57:06 nas-mass kernel: vethc85e8f4: renamed from eth0 Sep 4 11:57:06 nas-mass kernel: docker0: port 3(veth1304500) entered disabled state Sep 4 11:57:06 nas-mass kernel: device veth1304500 left promiscuous mode Sep 4 11:57:06 nas-mass kernel: docker0: port 3(veth1304500) entered disabled state Sep 4 11:57:06 nas-mass kernel: docker0: port 3(veth1637733) entered blocking state Sep 4 11:57:06 nas-mass kernel: docker0: port 3(veth1637733) entered disabled state Sep 4 11:57:06 nas-mass kernel: device veth1637733 entered promiscuous mode Sep 4 11:57:06 nas-mass kernel: docker0: port 3(veth1637733) entered blocking state Sep 4 11:57:06 nas-mass kernel: docker0: port 3(veth1637733) entered forwarding state Sep 4 11:57:07 nas-mass kernel: eth0: renamed from vetheee5eca Sep 4 11:57:07 nas-mass kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth1637733: link becomes ready Sep 4 11:57:17 nas-mass kernel: docker0: port 3(veth1637733) entered disabled state Sep 4 11:57:17 nas-mass kernel: vetheee5eca: renamed from eth0 Sep 4 11:57:17 nas-mass kernel: docker0: port 3(veth1637733) entered disabled state Sep 4 11:57:17 nas-mass kernel: device veth1637733 left promiscuous mode Sep 4 11:57:17 nas-mass kernel: docker0: port 3(veth1637733) entered disabled state Sep 4 11:57:37 nas-mass kernel: docker0: port 3(veth1842340) entered blocking state Sep 4 11:57:37 nas-mass kernel: docker0: port 3(veth1842340) entered disabled state Sep 4 11:57:37 nas-mass kernel: device veth1842340 entered promiscuous mode Sep 4 11:57:38 nas-mass kernel: eth0: renamed from veth495f9aa Sep 4 11:57:38 nas-mass kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth1842340: link becomes ready Sep 4 11:57:38 nas-mass kernel: docker0: port 3(veth1842340) entered blocking state Sep 4 11:57:38 nas-mass kernel: docker0: port 3(veth1842340) entered forwarding state Sep 4 11:58:46 nas-mass kernel: docker0: port 3(veth1842340) entered disabled state Sep 4 11:58:46 nas-mass kernel: veth495f9aa: renamed from eth0 Sep 4 11:58:46 nas-mass kernel: docker0: port 3(veth1842340) entered disabled state Sep 4 11:58:46 nas-mass kernel: device veth1842340 left promiscuous mode Sep 4 11:58:46 nas-mass kernel: docker0: port 3(veth1842340) entered disabled state Sep 4 11:59:01 nas-mass kernel: docker0: port 3(vethbec5965) entered blocking state Sep 4 11:59:01 nas-mass kernel: docker0: port 3(vethbec5965) entered disabled state Sep 4 11:59:01 nas-mass kernel: device vethbec5965 entered promiscuous mode Sep 4 11:59:01 nas-mass kernel: docker0: port 3(vethbec5965) entered blocking state Sep 4 11:59:01 nas-mass kernel: docker0: port 3(vethbec5965) entered forwarding state Sep 4 11:59:01 nas-mass kernel: docker0: port 3(vethbec5965) entered disabled state Sep 4 11:59:01 nas-mass kernel: eth0: renamed from veth54082bc Sep 4 11:59:01 nas-mass kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethbec5965: link becomes ready Sep 4 11:59:01 nas-mass kernel: docker0: port 3(vethbec5965) entered blocking state Sep 4 11:59:01 nas-mass kernel: docker0: port 3(vethbec5965) entered forwarding state Sep 4 12:25:18 nas-mass monitor: Stop running nchan processes Sep 4 14:24:53 nas-mass monitor: Stop running nchan processes nas-mass-syslog-20230904-2355.zip 24.54 kB · 0 downloads Okay now I'm extra confused the bottom/minimized progress bar had gone away... so it looked daed, but I just clicked into a share to look at a folder setup and re appeared and is still running... Quote Link to comment
SP67 Posted September 5, 2023 Share Posted September 5, 2023 I'm recently having this issue appear on the logs when I access the shares: Sep 5 19:13:46 NAS nginx: 2023/09/05 19:13:46 [error] 12072#12072: *464713 open() "/usr/local/emhttp/plugins/dynamix.file.manager/javascript/ace/mode-log.js" failed (2: No such file or directory) while sending to client, client: 192.168.88.1 (my router ip), server: , request: "GET /plugins/dynamix.file.manager/javascript/ace/mode-log.js HTTP/1.1", host: "unraid ip address", referrer: "unraid ip address/Shares/Browse?dir=/mnt/user/logs" Any idea what's happening? Quote Link to comment
leawhig Posted September 5, 2023 Share Posted September 5, 2023 On 9/4/2023 at 5:32 AM, wdnaser said: Hi! I've run into a rather frustrating issue. Whenever I try to upload files using this plugin, no matter what I do, the uploaded files end up getting corrupted. What's even stranger is that the file size always becomes 2.1MB, and they can't be opened correctly. Can someone reply to my message? Quote Link to comment
SShadow Posted September 5, 2023 Share Posted September 5, 2023 (edited) 5 hours ago, SP67 said: I'm recently having this issue appear on the logs when I access the shares: Sep 5 19:13:46 NAS nginx: 2023/09/05 19:13:46 [error] 12072#12072: *464713 open() "/usr/local/emhttp/plugins/dynamix.file.manager/javascript/ace/mode-log.js" failed (2: No such file or directory) while sending to client, client: 192.168.88.1 (my router ip), server: , request: "GET /plugins/dynamix.file.manager/javascript/ace/mode-log.js HTTP/1.1", host: "unraid ip address", referrer: "unraid ip address/Shares/Browse?dir=/mnt/user/logs" I am seeing similar errors in my syslog as @SP67. I am currently running on 6.12.3. Going back through my syslog history it started around October 2022. This covers versions 6.11.1 through 6.12.3 for me. It appears to happen more frequently than it did, it was very random and sporadic before (only a couple of times per month, if that). On my server I do not see any usage issues, everything appears to work normally including shares. Not sure if this is an issue or not. Thank you. Sep 5 14:35:11 Tower nginx: 2023/09/05 14:35:11 [error] 10764#10764: *226615 open() "/usr/local/emhttp/plugins/dynamix.file.manager/javascript/ace/mode-log.js" failed (2: No such file or directory) while sending to client, client: 192.168.10.50, server: , request: "GET /plugins/dynamix.file.manager/javascript/ace/mode-log.js HTTP/2.0", host: "192.168.10.10", referrer: "https://192.168.10.10/Shares/Browse?dir=%2Fmnt%2Fuser%2Fdomains%2FBackup%2Flogs" Sep 5 15:14:38 Tower nginx: 2023/09/05 15:14:38 [error] 10764#10764: *250316 open() "/usr/local/emhttp/plugins/dynamix.file.manager/javascript/ace/mode-log.js" failed (2: No such file or directory) while sending to client, client: 192.168.10.50, server: , request: "GET /plugins/dynamix.file.manager/javascript/ace/mode-log.js HTTP/2.0", host: "192.168.10.10", referrer: "https://192.168.10.10/Dashboard/Browse?dir=%2Fmnt%2Fuser%2Fsyslog" Edited September 5, 2023 by SShadow 1 Quote Link to comment
Zzz Posted September 6, 2023 Share Posted September 6, 2023 On 6/29/2023 at 10:50 PM, bonienl said: 博尼尔于 2023 年 6 月 29 日晚上 10:50 说道： Please update the chinese language pack to the latest version. 请将中文语言包更新至最新版本。 Or remove the language pack and install again, this will automatically update to the latest version. 或者删除语言包并重新安装，这会自动更新到最新版本。 感谢问题得到了解决! Quote Link to comment
mattalat Posted September 7, 2023 Share Posted September 7, 2023 File editing does not work on 6.12.4. I'm not sure exactly when this broke, but now when I try to click on yaml files to edit it just shows a blank square. Quote Link to comment
Squid Posted September 7, 2023 Share Posted September 7, 2023 14 hours ago, mattalat said: File editing does not work on 6.12.4. I'm not sure exactly when this broke, but now when I try to click on yaml files to edit it just shows a blank square. It's the update to Connect that broke this. @ljm42 Quote Link to comment
elibosley Posted September 7, 2023 Share Posted September 7, 2023 Hi All - We have a fix and are publishing a Connect plugin update to fix it today. Thanks for letting us know. Quote Link to comment
mattalat Posted September 7, 2023 Share Posted September 7, 2023 1 hour ago, elibosley said: Hi All - We have a fix and are publishing a Connect plugin update to fix it today. Thanks for letting us know. Thx! Quote Link to comment
zspearmint Posted September 7, 2023 Share Posted September 7, 2023 Unraid Connect v2023.09.07.1147 has been released to remedy the conflict with Dynamix File Manager to fix file editing. 1 Quote Link to comment
tjb_altf4 Posted September 8, 2023 Share Posted September 8, 2023 4 hours ago, zspearmint said: Unraid Connect v2023.09.07.1147 has been released to remedy the conflict with Dynamix File Manager to fix file editing. Can confirm this was impacting me on 6.11.5, and the Connect update resolved the issue. 1 Quote Link to comment
dopeytree Posted September 10, 2023 Share Posted September 10, 2023 On 8/15/2022 at 9:41 PM, bonienl said: Add the .sh extension to the list defined in /config/editor.cfg located on your usb drive. Note: you can use the file manager to edit the above file How does this work with future updates etc? There was an elegant solution provided of allowed text editing of all non binary files. Could this be implemented? I want to be able to edit .yml & .config files as these are regularly used in frigate and home assistant etc. Quote Link to comment
Kilrah Posted September 10, 2023 Share Posted September 10, 2023 1 hour ago, dopeytree said: How does this work with future updates etc? It stays as you put it. 1 Quote Link to comment
Nirvash Posted September 14, 2023 Share Posted September 14, 2023 Hi! The user manual pdf in the first posts is unavailable. Can you fix it, please? I'm trying to figure how what the job / scheduler does and how it works (how to actually schedule a job) and maybe that pdf explained it. Basically my goal is to start a copy job after the current disk rebuild is completed, as I don't want to tax the system too much by doing multiple stuff at the same time. Quote Link to comment
Nirvash Posted September 15, 2023 Share Posted September 15, 2023 I feel that, even though I stopped a file transfer between a SMB share and a local share, the transfer is till happening. I see both disk activity and 3 rsync processes still running even though I cancelled the file transfer: Attached are the diagnostics. Another "issue" I have is related to the previous post. According to this post, the scheduler functionality doesn't really schedule anything, I feel like the name is a bit misleading, as all it really does it queue a list of jobs, but you can't really schedule it with trigger like time, array status, disk activity or something like that. homeserver-diagnostics-20230915-1825.zip Quote Link to comment
daixuan201 Posted September 19, 2023 Share Posted September 19, 2023 In unreid6.12.4 version, this plugin runs very slowly. If a folder contains many files and subfolders inside, it will continue to be in a scanning state and cannot be displayed Quote Link to comment
mlitz123 Posted October 11, 2023 Share Posted October 11, 2023 would there be a chance you could add a option so I could view the inode number? I like to double check that my hard links are working properly. Quote Link to comment
Joly0 Posted October 19, 2023 Share Posted October 19, 2023 Hey, would it be possible to get support for more file extension? For example json is a file extension that i use quite often, but isnt supported, or toml, yaml or those text based configuration files. Or an option to add those simply manually by ourselves would be cool :) Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.