Meldrak
-
Posts
26 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Meldrak
-
-
is rsa key still supported for authentication? because I have in my logs
userauth_pubkey: signature algorithm ssh-rsa not in PubkeyAcceptedAlgorithms [preauth]I tried to add PubkeyAcceptedKeyTypes +ssh-rsa in sshd_config, but sill no ssh-rsa after
root@MNAS:/boot/config/ssh# sshd -T | grep -i ssh-rsa root@MNAS:/boot/config/ssh# root@MNAS:/boot/config/ssh# ssh -Q PubkeyAcceptedAlgorithms | grep ssh-rsa ssh-rsa [email protected]
-
Hi,
Could be very usefull to add a option to the UPS settings for executing a script at a specific battery level
-
1
-
-
Hello, with 1.7 version of AutoFan nvme disk is autoexcluded or not reconized
From system logs:
Sep 25 11:54:07 MNAS autofan: autofan process ID 1049 started, To terminate it, type: autofan -q -c /sys/devices/platform/nct6775.656/hwmon/hwmon3/pwm1 -f /sys/devices/platform/nct6775.656/hwmon/hwmon3/fan1_input Sep 25 11:54:07 MNAS autofan: autofan excluding drives sdc,sdb,sde,sdd from max temp calculations Sep 25 11:54:12 MNAS autofan: Highest disk temp is 0C, adjusting fan speed from: FULL (100% @ 1324rpm) to: OFF (0% @ 665rpm)
From disk logs:
Sep 17 09:32:57 MNAS kernel: nvme0n1: p1
Sep 17 09:32:57 MNAS kernel: BTRFS: device fsid 7bcb808e-6f15-413d-a924-10609a522dc7 devid 1 transid 1251964 /dev/nvme0n1p1 scanned by udevd (564)
Sep 17 09:34:09 MNAS emhttpd: Seagate_IronWolf510_ZP480NM30001-2S9301_7PJ008XA (nvme0n1) 512 937703088
Sep 23 18:51:24 MNAS autofan: autofan excluding drives sdc,sdb,sde,sdd,nvme0n1 from max temp calculations
-
Hello
Usefull utility thanks, WOL is working fine
I didn't manage to get SOL working with this docker (sol is working if called manually)
I try to change the RWSOLS_SLEEP_CMD variable but not better
-
On 10/2/2021 at 11:00 AM, Omri said:
Nevermind
"Solved" the issue by moving to zerosssl
Solved for me too after switching to zerossl
-
Hi,
What version should be the latest with this image?
My updater says 21.0.4 up to date, is it normal to not have the 22.x?
-
Hi,
Maybe same issue for me, all docker change network about 40 times per day, so docker network is lost for about 3 seconds
Aug 29 16:38:48 MNAS kernel: eth0: renamed from vethc37474d Aug 29 16:38:48 MNAS kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethe47692b: link becomes ready Aug 29 16:38:48 MNAS kernel: docker0: port 1(vethe47692b) entered blocking state Aug 29 16:38:48 MNAS kernel: docker0: port 1(vethe47692b) entered forwarding state Aug 29 16:39:02 MNAS kernel: docker0: port 1(vethe47692b) entered disabled statein some docker I can see errors too
2021/08/29 16:38:49.681624 [info] error handling UDP packet: dns: buffer size too small 2021/08/29 16:38:52.682049 [info] error handling UDP packet: dns: buffer size too smallthis issue appear 2 weeks ago and don't find anything to resolve it
-
I did some little changes to my script, and now data persist on containers restarts and on interfaces name changes
Before running my script as a CRON job (every day is a good choice), you'll need to setup the plugin once with interfaces you'd like to show
To persist on array reboot, you'll also need to run script after docker finish starting all containers
https://github.com/Meldrak/user-scripts/blob/main/networkstats
On 6/7/2021 at 11:40 PM, dorgan said:This is nice, maybe I will rework some of this into identifying applications, and then you can just select which applications to track. Do you know if the network device change upon reboot??
-
1
-
-
On 6/7/2021 at 11:40 PM, dorgan said:
This is nice, maybe I will rework some of this into identifying applications, and then you can just select which applications to track. Do you know if the network device change upon reboot??
Yes the network device name change on reboot or docker update
My script just fill the docker name to the veth device in the config file
It doesn't auto select the device you want to track, you need to select it in your plugin and hit save
I updated the script in previous post to delete the old entry if there's one
-
On 4/15/2020 at 6:54 PM, dorgan said:
I have added the ability to add pretty much any interface to be tracked. I have also added the ability to add an alias to an interface that is used on the graphs. I have found some information on how identify which veth interface maps to a given docker container, but it does not seem consistent, if someone knows an easy way, then maybe I can add this to the interface.
Hello,
I manage to autofill Alias with a script
for container in $(docker ps --format '{{.ID}}'); do veth="" networkmode=$(docker inspect -f "{{.HostConfig.NetworkMode}}" $container) name=$(docker ps --filter "id=$container" --format "{{.Names}}") if [ "$networkmode" == "host" ]; then veth="host" elif [ "$networkmode" == "br0" ]; then veth="br0" else pid=$(docker inspect --format '{{.State.Pid}}' "$container") ifindex=$(nsenter -t $pid -n ip link | sed -n -e 's/.*eth0@if\([0-9]*\):.*/\1/p') if [ -z "$ifindex" ]; then veth="not found" else veth=$(ip -o link | grep ^$ifindex | sed -n -e 's/.*\(veth[[:alnum:]]*\).*/\1/p') fi fi if [[ "$veth" = "veth"* ]]; then echo $container : $name : $veth sed -i "/$name/d" /boot/config/plugins/networkstats/networkstats.cfg sed -i "/alias-$veth/d" /boot/config/plugins/networkstats/networkstats.cfg echo "alias-"$veth"="\"$name\" >> /boot/config/plugins/networkstats/networkstats.cfg fi done -
Finally this issue only occur if Unraid Interface is set to French
Companion seems to works only with English language
-
Hi,
With last Unraid update I had an issue, Array is always shown as stopped (but started in real)
I also have this error in log when using Companion
Mar 18 14:04:18 MNAS webGUI: Successful login user root from 192.168.1.100 Mar 18 14:04:18 MNAS root: error: /main: missing csrf_token Mar 18 14:04:18 MNAS nginx: 2021/03/18 14:04:18 [error] 11120#11120: *730432 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.100, server: , request: "POST /plugins/dynamix.system.temp/include/SystemTemp.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.253" Mar 18 14:04:18 MNAS nginx: 2021/03/18 14:04:18 [error] 11120#11120: *730432 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.100, server: , request: "GET /plugins/gpustat/gpustatus.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.253" -
good to know 👍
-
but the only errors was on parity when I saw it
-
so if cache device go offline parity disk fail? it's not a good behavior
in anycase I will change my cables
-
Hi,
I still have this issue, but I noticed that it only occur after a reboot
I don't understand why, so here I join my full log if someone would check
-
On 11/15/2020 at 11:13 AM, Meldrak said:
Hi,
It does not work for URL with credentials, page is showing but can't login to my server
I think its a normal behavior ? or is there any tips for that ? I do not want to set my server passwordless
It's a web browser issue !! Works fine with Firefox not with Edge
-
Hi,
It does not work for URL with credentials, page is showing but can't login to my server
I think its a normal behavior ? or is there any tips for that ? I do not want to set my server passwordless
-
7 hours ago, trurl said:
Are you saying that you had to clear the disk again before it would let you rebuild? That is the part I am not sure I understand.
Yes and sorry for my english
I did the same as your procedure and at step 6 my disk came back without rebuild in fail state with the same 4 errors
-
a full rebuild is mandatory? when it occurs I only had 4 write errors
unplugging, unassigning disk and rebooting unraid didn't restart parity process, disk always came back with its 4 errors
I had to clear the disk to get parity again, I was not so easy
-
Hi,
My parity disk suddenly stop after seing 4 writes errors, short log below
Aug 21 01:07:46 MNAS kernel: sd 4:0:0:0: [sde] tag#17 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Aug 21 01:07:46 MNAS kernel: sd 4:0:0:0: [sde] tag#17 CDB: opcode=0x8a 8a 00 00 00 00 00 e8 e8 74 b0 00 00 00 08 00 00 Aug 21 01:07:46 MNAS kernel: print_req_error: I/O error, dev sde, sector 3907548336 Aug 21 01:07:46 MNAS kernel: print_req_error: I/O error, dev sde, sector 3907548336 Aug 21 01:07:46 MNAS kernel: md: disk0 write error, sector=3907548272 Aug 21 01:07:46 MNAS kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IOIf I try to execute SMART tests, it fail with
Short INQUIRY response, skip product id A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.After rebooting Unraid, SMART tests were OK, log file attached
So I did a new preclear of the disk and result was good and parity rebuild too
It's the second time that I have this issue, I don't know what to think
where is the problem? hard drive? motherboard? unraid? advice would be appreciated
and is there a better/faster way to reactivate parity without preclear and full rebuild?
thanks
-
On 10/12/2019 at 4:15 AM, ljm42 said:
-
In your router, add a static route that lets your network access the WireGuard "Local tunnel network pool" through the IP address of your Unraid system. For instance, for the default pool of 10.253.0.0/24 you should add this static route:
- Network: 10.253.0.0/24 (aka 10.253.0.0 with subnet 255.255.255.0)
- Gateway: <IP address of your Unraid system>
My operator router does not allow adding ip route, so I can't do this config to get access to all my equipements
If I add the static route in my dockers containers it works, but it's not persistent to update or reboot
Is there a way add route as parameter in docker? I didn't find it. Or is there another solution I could apply?
-
In your router, add a static route that lets your network access the WireGuard "Local tunnel network pool" through the IP address of your Unraid system. For instance, for the default pool of 10.253.0.0/24 you should add this static route:
-
Ok that's a problem while I can't add more drives to this computer other than USB
I check with another USB case and this one is reporting serial and smart attributes
so I will check for a better case with UAS protocol that gives better stability to USB
-
Hi,
I'm new and testing unraid with a double usb drive, I have an issue with it:
disk are detected like this:
WDC_WD40_EFRX-68N32N0_RANDOM__3F4917AD758C-0:0 (sdb) 512 7814037168
WDC_WD40_EFRX-68N32N0_RANDOM__3F4917AD758C-0:1 (sdc) 512 7814037168
but ID in red change everytime unraid reboots, so my array can't autostart and I need to attach drive with the new ID
is there a way to fix manualy the ID of the disk? or to include a wildcard like
WDC_WD40_EFRX-68N32N0_RANDOM__*-0:0 (sdb) 512 7814037168
WDC_WD40_EFRX-68N32N0_RANDOM__*-0:1 (sdc) 512 7814037168
thanks for your help
*** [GUIDE] *** Setup Crowdsec with SWAG
in Docker Containers
Posted
Hello, same for me, it doesn't work. I have about 80 ip that have been block by crowdsec and these IP continue to log in my access.log
I tried a manual ban from one of my IP and I still get access to my servers
I'm also surprised to not see the bouncer Ip adress and version
API pull works once at docker startup and after it never change
on crowdsec dashboard the bouncer appears offline after one day
help is welcome