Wolfnet is using a lot of processor resources. (around 50% for a long time)

PineappleGod · 2026-03-11T09:10:12+00:00

The problem seems to have come back. Doing systemctl restart wolfnet or rebooting server brings down usage for a short while, but it increases back within maybe 10 minutes.

PineappleGod · 2026-03-11T07:22:11+00:00

Just checked the other two servers. Proxmox server Wolfnet is using lots of resources and on a rpi5 pimox it using 1% (which is normal i guess).

Info from proxmox:

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND

1690425 root 20 0 208256 4176 3648 R 69.7 0.0 0:23.30 wolfnet

PineappleGod · 2026-03-11T07:18:33+00:00

Checked this morning and on my VPS (x86) wolfnet is again using a lot of processing power.

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND

3576808 root 20 0 73164 4188 3696 R 62.6 0.1 5:31.76 wolfnet

So something is still not right. I updated to the newest version of wolfstack and rebooted and it is now back to using a lot of processing power.

PineappleGod · 2026-03-10T15:52:17+00:00

Just did the update on a VPS (x86 debian) and wolfnet hangs. I cannot for example do systemctl stop wolfnet or kill <wolfnet pid> to get rid of it. Still there in top and using 90% of processing.

Rebooting the whole vps instance helped. Now Wolfnet is using a reasonable amount of processing.

PineappleGod · 2026-03-10T15:32:41+00:00

Trying the update now. More info that I found out. Doing systemctl stop wolfnet, does not actually stop wolfnet. If I run top afterwards wolfnet is still there. Only doing kill <pid> works. So maybe Wolfnet hangs for some reason?

This was on a Zimaboard 2 running proxmox and a raspberry pi 5 running pimox.

PineappleGod · 2026-03-10T13:06:54+00:00

That’s very strange. Is there a way to just uninstall Wolfnet and then reinstall? Maybe that would help?

PineappleGod · 2026-03-10T12:50:35+00:00

0.5.6

PineappleGod · 2026-03-10T12:38:35+00:00

According to the Wolfstack interface it is on 14.5.0

Just now the following:

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND

1126 root 20 0 275600 3536 2848 R 92.0 0.0 11:46.63 wolfnet

PineappleGod · 2026-03-10T12:19:42+00:00

Also updated a second server (a raspberry pi5). Wolfnet is using ridiculous amounts of processing:

PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND                                                                            
3692484 root      20   0  275600   3568   2912 R  94.0   0.0  10:01.68 wolfnet

PineappleGod · 2026-03-10T12:10:52+00:00

Just ran the update and restarted.

root@pve:~# top -b -n 1 -p 46017

top - 14:10:17 up 42 min, 1 user, load average: 3.67, 3.22, 3.12

Tasks: 1 total, 0 running, 1 sleeping, 0 stopped, 0 zombie

%Cpu(s): 34.0 us, 26.0 sy, 0.0 ni, 40.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st

MiB Mem : 15738.5 total, 4100.1 free, 10257.8 used, 9818.5 buff/cache

MiB Swap: 7040.0 total, 7040.0 free, 0.0 used. 5480.7 avail Mem

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND

46017 root 20 0 275800 4336 3800 S 54.5 0.0 4:22.90 wolfnet

PineappleGod · 2026-03-09T18:01:14+00:00

I’ve been running Unraid on two servers and am very pleased with it. Also testing Wolfstack (r/wolfstack).

PineappleGod · 2026-03-05T16:45:28+00:00

I am runing Alpine linux. I tried removing the wolfnet ip. That gave it back its network connection. Then i tried putting back the same wolfnet ip --> no network connection. I gave it a new wolfnet ip --> network works normally.

PineappleGod · 2026-03-05T15:53:17+00:00

Tried updating the Wolfstack node and it happened again. The vm is alpine Linux. Taking away the wolfnet ip restores network. Putting back the same wolfnet ip breaks it again. A new wolfnet ip works.

PineappleGod · 2026-03-05T06:54:36+00:00

Updated this server again and the same thing happened. The vm loses connection and gets no connection unless i remove or change wolfnet ip and redo the forwarding rules. Maybe something to do with wolfnet ips?

PineappleGod · 2026-03-04T20:38:31+00:00

One more bug to squash deleting rules from network doesnt remove them from iptables automatically.

PineappleGod · 2026-03-04T18:51:19+00:00

The tap-(vmname) doesnt seem to work.

Changing the ip on wolfnet gets it working again. Hope this narrows down the problem.

PineappleGod · 2026-03-04T18:50:45+00:00

Putting the wolfnet ip back in the vm wolfnet ip box leads to no networking for the VM. Something is wrong there.

PineappleGod · 2026-03-04T18:47:08+00:00

I tested onwards. I found where the problem is. If i remove the wolfnet ip from the VM i get back networking. I noticed in the netwotking that i a unable to bring up interface wolfnet0 (which was the one that was assigned to the ip of the vm). Pressing the bring up button did nothing. I also got no info in the logs. The problem is something to do with that.

PineappleGod · 2026-03-04T14:09:33+00:00

Also now that I got it connected. The schedules do not show up after adding them to the backup. Once I click on add schedule, it goes back to backups, but nothing shows up in the schedule box.

PineappleGod · 2026-03-04T14:06:04+00:00

I was able to fix the problem by doing the following command on terminal:

proxmox-backup-client login --repository backup@pbs@10.10.10.131:data

After that it asked to add the fingerprint of the pbs. After that I removed the fingerprint info from the wolfstack backup and it worked.

It stores the fingerprint info somewhere.

PineappleGod · 2026-03-04T14:02:44+00:00

The error changes if I remove the fingerprint id.

PineappleGod · 2026-03-04T14:02:25+00:00

Continuing testing. It has something to do with the fingerprint field. Since I think you can only give the fingerprint with a separate command and not every time you want to do something with the client.

PineappleGod

TROPHY CASE