user20C
Members
-
Joined
-
Last visited
-
I updated to the new latest image and I am still getting an error. The new error is 2022-05-13 16:58:04.060 Error App: ProcessRun 'StreamTranscode 1c46dc': Error starting Ffmpeg. WorkingFolder: null Anyone have any ideas?
-
I am getting the same error. I switched back to V2 and the error goes away.
-
I was having the same problem. I fixed it by REPLACING the cipher in the new opvn file with the AES-256-GCM. In a newbie at this stuff so I was confused at first if I just needed to add a line or replace the existing line. It also appears to be case sensitive so make sure the cipher is in all caps. Also, making the changes in notepad on my windows machine would not work. I had to use Atom to make the changes. Hope this helps.
-
Hello everyone. I am submitting this bug report at the request of a moderator in the general support section. I had a thread going over there trying to figure this out but we hit a dead end. I have run into the problem where the process SHFS consumes all of my available memory over time. I have a total of 192GB installed which shows as 189GB available to unraid. It takes around 24 hours for SHFS to consume all that memory, then SHFS will crash and all shares disappear until a restart. Booting in safe mode exhibits the same issue. I have been observing this issue by opening a terminal window and running the htop command. I then sort by mem% which brings multiple instances of SHFS to the top. Then I just sit and watch as it gradually consumes more and more memory. I was instructed in the general support thread to redo my flash drive which I did. The flash drive was formatted and recreated and only the super.dat and key file were restored from the old config file as instructed. Attached are a screen shot of htop showing the shfs instances that were running and also diagnostics from last night. This is a completely clean OS install (using existing data disks). No plugins installed, Docker is set of off, and No VMS. Any help would be greatly appreciated! I didn't know what priority to set, its urgent for me but I am probably the only person with this issue so that makes it not so urgent for the community. Feel free to change it. tower-diagnostics-20200330-2034.zip
-
I will, thank you for help provided so far!
-
Ok, I restarted with docker set to off, no plugins installed, and no VMs. After starting the array i saw 1.8G of memory being used. 30 minutes in it was at 4.59G. 40 mins it was at 6.06G. And at 1 hour it was at 8.36G of memory used. So a steady increase. I beleive this would go on for about 24 hours until it maxes out the total 189G available. I attached a screenshot of htop again sorted by mem% and also added another diagnostics file. Any ideas or help is greatly appreciated and thank you for the help so far. tower-diagnostics-20200330-2034.zip
-
I guess I thought we had already ruled anything docker and plugin related out as the cause. I will restart with docker set to off and see if that changes anything with the newly created USB.
-
I shutdown the server, pulled the USB and put it in my windows PC. I copied the config file to my desktop then formatted the drive. I downloaded the USB creator tool from the unraid website and created a new USB with 6.8.3. I then copied over the super.dat file and the key file from the old config folder to the new config folder. Put the USB back in my server and started it up. After starting the array manually I get the same behavior. Several instances of shfs are running again and slowly consuming memory. Its only been running for 40 mins so total mem% is still low but the trend is there as it was before. So we have rulled out plugins, dockers, and the USB drive. It only happens when the array is started. Another issue I have discovered is if I try to stop the Array the system hangs. I get a message in the bottom left of the browser that says "Array Stopping Retry unmounting user share(s)...) I guess this related to the shfs processes not stopping or hanging.
-
booted into safe mode with web GUI. With the array not started everything ran as expected. System idling with shfs not showing up. As soon as I started they array, shfs processes started and ram utilization has been slowing going up. I know shfs is a normal process and is expected to run. However i have multiple instances of it and they all slowing eat up the ram. Again this is in safe mode with web GUI enabled. I am observing all this by opening a terminal window and running htop and sorting by mem%. I assume this is an acceptable way to monitor this. So it seems I have an underlying OS problem? Or could a hardware issue cause this. There are alot of ram modules in this server. I purchased it off ebay as is. 192GB ram total. I haven't been in the case recently or changed anything hardware wise. Just thinking out loud here and trying to give as much relevent information as possible.
-
I have disabled docker completely and restarted twice now and shfs is still slowly consuming memory. I guess I need to start with plugins next. Is there switch to shut off all plugins? Poking around a few of them there doesn't seem to be an explicit on/off toggle for them. I guess I will have to uninstall one by one until those processes that are consuming the memory go away.
-
Still doing the daily restarts. Last night I let the server keep running until shfs filling crashed. At that point ram % went down to 3% but all my shares disappeared. A restart brought everything back. Can anyone tell me what shfs is or does? Is there any way to tell if a certain plugin or docker is using it? I have disabled cache directories based on some forum searches but that doesn't help. A forum search didn't really bring up anything, most other problems with shfs have dealt with it utilizing to much CPU which is not happening for me. Any help would be greatly appreciated!
-
Hey everyone, I was hoping to get some help with this memory issue I am having. About every 24 hours I have to reboot my server because the memory keeps maxing out. when I run htop in the terminal and sort by mem % i get the attached picture. It has been going on for a few weeks. I haven't changed anything hardware wise with the server and I don't recall any unraid updates triggering it. It happened with 6.8.2 and 6.8.3. Attached are a screenshot of the terminal window with htop running and my diagnostics. Any help would be greatly appreciated. tower-diagnostics-20200327-1622.zip
