-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extreme high memory usage on Docker almost brings server down #107
Comments
I think this is a Docker thing. I used to run SS in a Docker container on my Synology NAS and kept running into the same thing. Limiting the amount of RAM attributed to that container helped the problem. If you give it full access to all the RAM given to Docker then yes, it can take it out. The reason I think this is a Docker thing is I moved my setup into a VMWare ESXi server running Ubunutu and I don't have any issues with RAM usage at all. It still takes up all the RAM assigned but it never crashes and doesn't affect the over VM's in any way. |
I actually think this is the way the docker is constructed because I did restrict everything! Do you have any good guide creating and setting up a VM running Seedsync :-) |
Not a Linux expert by any means but for me.... AFAIK mounted volumes are always in the mnt folder. Navigate through the file structure via SSH and find the mnt folder. You should see the mounted volume there and be able to see the files/folders on the remote system. Whatever path you went through to get there is the same path you put in SS In my case I mounted a remote folder on my NAS to /mnt/ss_downloads. So that is the path that I put in SS Hope that helps |
Also, make sure you edit fstab to make the mount persistent across reboots https://askubuntu.com/questions/154180/how-to-mount-a-new-drive-on-startup |
Cant say I am any Linux expert either :-) All the guides say you have to create the mount point in the username dir But in the log file I can see this: So you also did the fstab path in the ubuntu VM right? mine looks like this: So how does your path string look like? And what is your path in the UI/GUI? |
First, have you created the target folder where you are telling Ubunutu to map the contents of the external share? "/home/username/share" needs to actually exist. The system won't just automatically create that folder. Also, I may be wrong but I recall that externally mounted volumes need to be in the mnt folder. Putting it in the /homes/$user folder won't work.
//192.168.200.89/Sync/Seedbox/1-Incoming - The target on my NAS where files are stored /mnt/ss_downloads - The directory on the SS box that the NAS contents are mapped to cifs - Share protocol uid={uid},username={uname},password={passwrd} - Credentials needed to authenticate on the remote server NAS iocharset=utf8,file_mode=0777,dir_mode=0777 - Used to configure permissions and communications charset I'm also assuming that where you put "username" you really mean the actual user's username. It is not a dynamic field that will change depending on who's logged into the SS system. |
Yes all my mounted folders are created by me....nothing is automatic on Linux LOL I moved the mount to: But then after reboot I get this error and Seedsync dosent start up casperse@seedsync:~/Downloads$ sudo dpkg -i seedsync_0.8.6_amd64.deb I have removed it and all the files in the: But something is now broken? journalctl -xe-- A start job for unit 192.168.0.6-SEED.mount has finished with a failure.-- The job identifier is 1779 and the job result is failed.
|
take the user out of the mnt path. Mounts are not user-specific they are system level. /mnt/mount '/home/user-name/.seedsync' is where all the config files are. Leve that alone. All we need to do is map the network drive to a mount folder in Ubuntu. That's what the line in FSTAB does. If you SSH to that mounted folder, can you see the files on the remote server? If you can't the shared mount needs to be resolved before anything will start to work. |
Do you have cifs-utils installed? sudo apt-get install cifs-utils |
what are the permissions on the mounted parent DIR (//192.168.0.6/SERVER)? Also, Unix-based systems are case-sensitive. Could there be a mixed-case thing going on here? I tend to keep everything lower case all the time. I'm also thinking about the hash prepending the folder name. I tested it on my NAS and I could create it but I wonder if it might be causing issues? |
The UID is going to be the users account on the mounted system along with the username and password. Make the username and password on the Seedsync server the same. From the SS SSH, try and create a folder in the mounted DIR. See if it works or if you get an error or if it create a folder. |
Ok, mnt is at the root level, it's not inside the home dire MNT and HOME are at the same level |
so next thing is determine what user SS is running under HTOP |
-Add your user account to the SUDO group -Check the assignment It should come back as 'root' |
This should be working AFAIK if you're logged in as casperse and you've created a folder in the mnt/SEED folder. And SS is running as casperse. There shouldn't be any issues for SS to store files there. The only thing left that we can try is to drop the hash tag from the folder names. |
Hang on a sec here. Looking at the path in the screenshot you posted, your share is /192.168.0.6/seed/downloads that is not the path you have in FSTAB first, you entered SEED not seed. Those are different directories in the eyes of Linux. Also, there's another folder after seed, downloads. Is that where you want SS to save downloads to? If so then you need to edit your mount. //192.168.0.6/seed/downloads /mnt/seed cifs uid={uid},username={uname},password={passwrd},iocharset=utf8,file_mode=0777,dir_mode=077 |
I would suggest skipping the credentials file as it may be introducing its own permissions problems to the situation. I inline my credentials in FSTAB. I'm the only one using this system so I'm not concerned about hyper security. |
No I actually changed that after you showed me your config (I removed the credential file) The server SMB share is: (SEED is the drive sharename) This should work....didn't help sleeping on it :-) |
Hi
I just found why I have had so many problems running Seedsync and the slow unresponsive usage of the UI


Some configuration ? in the docker creates a very high memory usage after some time
It almost crashed all my dockers....
I have also created a support post to the where the Docker was created here:
https://forums.unraid.net/topic/87798-support-selfhostersnets-template-repository/?do=findComment&comment=1042710
The text was updated successfully, but these errors were encountered: