search

ipsingh06 / seedsync

Sync your seedbox. Fast. And more.
https://ipsingh06.github.io/seedsync/
Apache License 2.0
309 stars 43 forks source link

Error while loading shared libraries: libz.so.1: failed to map segment from shared object #97

Open m7ke opened 3 years ago

m7ke commented 3 years ago

I have seedsync setup on my unRAID server and it's been running fantastic since I've set it up. When I'm not actively using it, I stop the docker container so it's not using any resources and it's been about a month or so since I spun it up, but today I was greeted with this error:

An error occurred while scanning the remote server: '/home/username/scanfs: error while loading shared libraries: libz.so.1: failed to map segment from shared object'.

Anyone have any insights?

quadcom commented 3 years ago

Can't say I've ever come across that error in the past. Sorry I can't be of help with that one.

What I will say is I also run SS in a VM albeit not in a Docker container but instead a full VM in ESXi. I'd suggest not to worry about shutting it down between uses as it really doesn't use resources at all when it's not actually doing anything, Even then when downloading stuff, it uses very little of the host server's resources. I have Plex running on the same box and can transcode 4 x 4K streams while DL'ing stuff at the same time.

Perhaps rebuilding the container and seeing if you run into the same error again?

m7ke commented 3 years ago

I've tried rebuilding the container and spun up a fresh Ubuntu VM and tried that as well but with the same error. I'm thinking it must be on my seedbox providers end, so I'll open a ticket with them and see if they can help.

Thanks again!

quadcom commented 3 years ago

When you rebuilt the container, did you use the same image or did you re-download the image from Dockerhub?

Another option. Have you tried simply installing ubuntu server in a VM and then install SS from the deb file?. That's what I did and getting set up was a breeze. Yeah, I had to figure out Samba shares and persistent mounts so that downloads were stored on the NAS but once that was done I haven't had a problem since. Hopefully I didn't just jinx myself.

ipsingh06 commented 3 years ago

Hey @m7ke apologies for the delayed response. Your intuition is correct - this error is happening on your seedbox. A google search result seems to offer two possible solutions, both need to be run on the seedbox machine:

  1. sudo mount /tmp -o remount,exec
  2. Put export TMPDIR=$HOME/tmp on the ~/.bashrc file

Hopefully one of these resolve the issue for you.