Koenig

I never found a solution to this, so I have lived with it up until today when I updated the "unraid-api-plugin", so I guess that was the culprit somehow. Now everything is snappy again and I'm happy!

Will try. The thing is it ran just beatifully until I had a powerout (I wrote crash earlier, but it was actually a powerout), after it rebooted it was starting to go slow, it's like 15-25 seconds after I push anything or change tab, sometimes the browser (chrome) opens a popup that says the website has become unresponsive ans ask if I wish to wait or something else. VM's and dockers works just fine anyway, it just annoying when it is that slow you know....

Hi! My servers web-UI became very slow after a crash and I can't figure out why, I have tried rebooting it several times with no luck. It's been like this for a couple of weeks everything else works so due to lack of time it has just been running anyway, until today I also noticed that it won't respond to me manually invoking the mover (via the button) thinking it might be related. It might also be 2 issues. Anyway I attched my diagnostics and hope this great community can come up with what my problem is. unraid-diagnostics-20231023-1706.zip

It will eventually get updated, but probably not until there´s a 6.12.1 stable. If that is the only course of action we have to wait, it is not like I will forget the issue anyway as there's plenty to remind me in the log

Unfortunately me changing this so the setting says "ToK" on both servers didn't help, lines like the ones below continue to come frequently: May 4 02:28:55 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:1182285 May 4 02:54:55 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:1291108 May 4 02:57:00 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:1299810 May 4 02:58:02 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:1304178 May 4 03:17:17 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:1384761

Nice catch, changed it too see if it matters.

Yeah, the screenshot is from a unraid-server running 6.11.5 that is the one that contains the share that I'm mounting on one with unraid 6.12.0-rc5, wich is the one that is throwing CIFS-lines in the log. Attaching diagnostics from both servers. "unraid" runs RC5, "nas" runs 6.11.5 (stable) A courious thing here is that "nas" (stable) also have a mounted SMB-share from "unraid" but is not throwing those errors into the log, while "unraid" (RC5) has a mounted share and thows a lot of those lines in the log EDIT: Fixed the quote. nas-diagnostics-20230503-2019.zip unraid-diagnostics-20230503-2019.zip

Yeah, sorry about that, the NFS-share was an attempt to get rid of the messages in the log, but I couldn't get write permissions on the NFS-share (not beeing familiar with how linux networks shares work) so it is not beeing used, but this is not how it has been setup in the long run, just the last couple of days - and it did not lessen or increase the amount of those messages in the log. But I agree with you, it is not meant to be that way, I have been using the SMB-share for years though.

Like this

It is a SMB-share from a Unraid server, running latest stable.

I'm still getting a lot of this in my log: May 3 07:40:54 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:3047123 May 3 07:56:07 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:3110621 May 3 08:03:55 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:3143452 May 3 08:23:18 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:3224409 May 3 08:34:51 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:3272533 May 3 08:35:23 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:3274724 Any idea what could be causing it? unraid-diagnostics-20230503-1011.zip

Both servers are on 24/7 the NAS has an uptime of 44 days as for now, had a power-outage back then otherwisw it would have an uptime since last OS-upgrade. I have the NAS set as master already but the line with "os level = 255" I have not, I will add it. They both act as client and server. On "NAS" I have a share "Backups" wich is then mounted on the other server, just namned Unraid. On "Unraid I have a share "ISOs" wich is then mounted on NAS, I thought it to be a good way of sharing the storage of ISO's for VM-deployment. This setup I have had for atleast 3 years now, should be 4 in just a matter of a month or so, but I have never before seen the log filling up with that message, I cannot be sure but I would bet good money on it not beeing so in RC2 even, due to it beeing some time between, and the fact that I do check to logs intemittently.

I have all clients on my network set to use DHCP, and then I manage all IP and network from my pfSense router. They have had the same IP since the day they first connected to my network. Again I do not know if this is the best way to go about it but I started doing it this way long before I got my first Unraid-server and it has been working well, but as I mentioned earlier if this is a bad way to do it I'm open to suggestions.

You meaning it is not set to share? I don't want to share it from the server where I use unassigned devices to mount it, it is just supposed to be mounted so I can be able to map it in the docker "duplicati" On the other server (backup server - NAS) it is set to share on the network and from there it is visible on the network. Perhaps there's a better way of doing this, but this way has worked for atleast 3 years now, but I'm open to suggestions if there's a better way to go about it. EDIT: Both servers are Unraid, but the "backup"-server is on the latest "stable" version. I usually wait a good while before updating that one. EDIT2: Attached a fresh diagnostics EDIT3: Attached a diagnostics from "NAS" as well. unraid-diagnostics-20230419-1014.zip nas-diagnostics-20230419-1021.zip

Might very well be, but I've not seen them before, that I can remember... But now they are very frequent, as I run "Duplicati" as a docker and backup some shares and appdata (different shares on diffrent days) to another Unraid server and have been doing that for atleast a couple of years and can't remember something like this filling up the log.