ap-wtioit
Members
-
Joined
-
Last visited
-
The python3 plugin 2024.07.06 does not support the latest unraid 6.12.11 release. I proposed a fix here: https://github.com/dlandon/python3/pull/2 For anybody also updated to 6.12.11 and missing python3 now, you can try to install the plugin from this url (until the PR is accepted, then you should use the official url again): https://raw.githubusercontent.com/ap-wtioit/python3/main/Python3.plg
-
I used /etc/rc.d/rc.sshd restart from https://forums.unraid.net/topic/52990-solved-restart-ssh-after-editing-ssh_config/?do=findComment&comment=584207 to restart the service (seemed faster than the UI)
-
Unraid needs updated btrfs progs for v6.2.2+ root@redacted:~# btrfs version btrfs-progs v6.2.1 root@redacted:~# btrfs dev stats /mnt/cache [/dev/sdg1].write_io_errs 0 [/dev/sdg1].read_io_errs 0 [/dev/sdg1].flush_io_errs 0 [/dev/sdg1].corruption_errs 4 [/dev/sdg1].generation_errs 0 [/dev/sdf1].write_io_errs 0 [/dev/sdf1].read_io_errs 0 [/dev/sdf1].flush_io_errs 0 [/dev/sdf1].corruption_errs 4 [/dev/sdf1].generation_errs 0 root@redacted:~# btrfs dev stats -T /mnt/cache Id Path Write errors Read errors Flush errors Corruption errors Generation errors -- --------- ------------ ----------- ------------ ----------------- ----------------- 1 /dev/sdg1 0 0 0 0 0 2 /dev/sdf1 0 0 0 0 0 with the current version of btrfs in unraid one does not receive the correct numbers when using `btrfs dev stats -T` (see https://github.com/kdave/btrfs-progs/issues/585) Note: posting without diagnostics (there is still too much information in the anonymized version (e.g. Serial Numbers, VM Names, ...))
-
Current findings: With wireshark i could confirm that the client (gvfs-smb) is terminating the find request after 20seconds (as documented as default timeout for smb-client). Unfortunately i couldn't find any url options for smb:// urls that would allow me to increase the timeout on client side. Also there seems no system wide option available that wouldn't need to be specified as comand line arg for smb-client. Workarround: add the following as extra configuration # split answers for directory listings into 256K chunks to avoid client timeout for directories with many elements smb2 max trans = 262144 This splits the response for SMB2_FIND_ID_BOTH_DIRECTORY_INFO * into 256kb chunks for the answer where the first chunk is available after 0.3 seconds avoiding the 20s timeout. Edited: leave only smb2 max trans as extra configuration, add slightly higher value than 64k, that still gives us an smb2 find response roughly every 1.5 seconds to avoid client timeout (on our system)
-
After we upgraded Unraid to 6.11.1 (from 6.9.2) it seems no longer possible to retrieve directories with many entries via samba. I'm getting "Broken pipe" from Ubuntu Client after a bit more than 20 seconds. Listing the directory on a terminal directly on unraid takes about 30 seconds. Is there any way of increasing the timeouts for directory listings in samba again? (as it seems 6.9.2 had way longer timeouts) The directory contents are created via Ubuntu Deja Dup backup so i cannot directly change the directory structure in there.
-
Graylog accepts remote syslog messages only if i manually set the protocol/format to RSYSLOG_SyslogProtocol23Format. To do this you currently need to: activate the Remote Syslog Server in the Settings GUI Login via ssh as root and edit /etc/rsyslog.conf, add ";RSYSLOG_SyslogProtocol23Format" to the end of the syslog line *.* @@YOUR_REMOTE_SERVER_IP:514;RSYSLOG_SyslogProtocol23Format Change something in the WEBUI again (not touching the remote syslog options) to reload the rsyslog service After editing the config like this the GUI Options for the Remote syslog server seem to no longer have an effect. Can you add a dropdown for the rsyslog format template options?
