That's good to know, couch potato did that a few months back and I had the same problem.

Can anyone tell me what I'm doing wrong?

 

I would upgrade to 5.0.5 or 5.0.6, follow the upgrade instructions.

delete all plugins - Add just the first three you are needing to get working.  Hold off on Plex.

rename all plugin databases/config directories and start over with a fresh system.  You should not have that many issues.  Use your cache to start the config directories in.  Create a cache only directory to store the configs in

 

Follow the trouble shooting procedures at the beginning of this thread.

 

You will have to set everything up again, but it sounds like you have issues.

 

Get SABnzbd, CouchPotato, SickBeard all working standalone, then integrated before you introduce Plex.  By stand alone, i mean import the the databases back into CP and SB, and set all of the settings as appropriate.  Then make the changes so SAB is used.  Take it one step at a time an make sure each lower level is working before you try to introduce the next level that depends on on the lower levels working correctly.

Can anyone tell me what I'm doing wrong?

 

I would upgrade to 5.0.5 or 5.0.6, follow the upgrade instructions.

delete all plugins - Add just the first three you are needing to get working.  Hold off on Plex.

rename all plugin databases/config directories and start over with a fresh system.  You should not have that many issues.  Use your cache to start the config directories in.  Create a cache only directory to store the configs in

 

Follow the trouble shooting procedures at the beginning of this thread.

 

You will have to set everything up again, but it sounds like you have issues.

 

Get SABnzbd, CouchPotato, SickBeard all working standalone, then integrated before you introduce Plex.  By stand alone, i mean import the the databases back into CP and SB, and set all of the settings as appropriate.  Then make the changes so SAB is used.  Take it one step at a time an make sure each lower level is working before you try to introduce the next level that depends on on the lower levels working correctly.

You can also try just deleting everything in your USB/packages folder then reboot. 7/10 times that fixes complications with dependencies, also if you have a USB/extras folder, see what's in there. They folder auto installs everything in it on each boot so to test you can rename that folder and reboot to see if it all starts working.

I've been attempting to install the MediaBrowser plugin on a clean test Unraid 6 b10a and continue to see errors like this:

 

/sbin/ldconfig: Writing of cache data failed: No space left on device

 

and the last line

 

Warning: file_put_contents(): Only 0 of 279 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/plgMan/plugin on line 238

 

There is still 3.93 GB available on the flash.  Must be something I'm not familiar with causing this

Any help is appreciated.

 

Been following your progress on this one with great interest.  Keep it up!!

 

I saw similar issues with the same kind of messages as the second one. If I installed it first it just wouldn't work. If I tried to install it with other plug-ins it would mess them up too so they gave similar error messages when starting. Even the Docker plugin wouldn't start.

 

I also had the same type of issues with the nzbDrone plugin. Completely hosed the setup already on the server.

 

I am playing with a test server so if you have anything you want tested I can do that.

 

Is there anything I can do to improve the upload and download speed for BitTorrent Sync? I have FiOS, so speed should not be an issue? Both up and down are about 7 bytes! I do notice that the Live database is still syncing. Is that the reason for the slow speed?

Is there anything I can do to improve the upload and download speed for BitTorrent Sync? I have FiOS, so speed should not be an issue? Both up and down are about 7 bytes! I do notice that the Live database is still syncing. Is that the reason for the slow speed?

 

Honestly, this is one of the reasons I stopped using bittorrentSync and still use a FTP client to download. My average was about 500KB/s and it would peak at about 1.5MB/s intermittently. Maybe someone else knows the secret recipe. lol I don't sorry...

PhAzE, I was wondering if you were still working on the update for Media Browser so that different release levels could be selected (dev, beta, release).

 

Wasn't sure if it was best to check here on the MB forum (so I did both ) hope you don't mind.

Is there anything I can do to improve the upload and download speed for BitTorrent Sync? I have FiOS, so speed should not be an issue? Both up and down are about 7 bytes! I do notice that the Live database is still syncing. Is that the reason for the slow speed?

 

It turns out that restarting the server helped increase the speed (a bit)! Not sure if it will eventually go down again, though.

 

It turns out that restarting the server helped increase the speed (a bit)! Not sure if it will eventually go down again, though.

 

Well, it did go down!  I ended up scrapping the original share and drilled one level deeper (since one folder contained 99% of the data) and that seems to have done the trick! I am at 20MB now. I added the other folders separately and their sync times are... well, they are already in sync!

Hey All,

 

I had a shutdown of my UnRAID that has lead to a bizarre problem with NZBDrone.  NZBDrone keeps stopping periodically and I am getting the following weird display on the Plugin page:

 

 

I have tried removing the nzbdrone.plg and deleting the settings I could fine including the mono pkg files, but I think there are still remnants around I haven't been able to fully remove because when I add NZBDrone again it has this same problem.  It also shows the update link even when running the latest version.  The issue occurs with both the normal and development branches.

 

Any ideas on how I can remove everything so I can start fresh?

Hey All,

 

I had a shutdown of my UnRAID that has lead to a bizarre problem with NZBDrone.  NZBDrone keeps stopping periodically and I am getting the following weird display on the Plugin page:

 

I have tried removing the nzbdrone.plg and deleting the settings I could fine including the mono pkg files, but I think there are still remnants around I haven't been able to fully remove because when I add NZBDrone again it has this same problem.  It also shows the update link even when running the latest version.  The issue occurs with both the normal and development branches.

 

Any ideas on how I can remove everything so I can start fresh?

 

Im also getting this error but i never shut-down my server, i was just going to update it and i got that error.  Im not able top update it as it stay on "Installed Version: 2.0.0.2199".

 

If i stop it and try and update it, it doesnt change a thing.

 

 

I have been working with this BitTorrent client for a few days now, and it seems that the primary server is still indexing  - which might be the reason for the (once again) slow transfer rates - but I was wondering if there was a setup guide or an FAQ for using the BitTorrentSync (currently called BTSync). I know I still have question like 'Is it normal for the transfer rates to be low while the main server is still indexing?' or 'Do I need to open any ports  once I take the backup server offsite?' 'How will I manage the backup server offsite?' 'Is it better to share smaller sub-folders or share one massive root folder?'

 

I'm not sure if there is a guide or a walk-thru on setting up an offsite backup server using BitTorrentSync, but once I learn the answers, I'd be glad to put it together! Also, if you have any suggestions or answers to those questions, please do share! 

NZBDrone is showing this when I try and update the plugin

 

Status:  RUNNING with version: 2.0.0.2180

 

 

Installed Version: 2.0.0.2180?

Update to Version: 2.0.0.2180 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 2.8.1+md54+dhx3-1~xamarin1 3.8-0xamarin1 1.1-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.8-0xamarin2 3.10.0-0xamarin1 3.10.0-0xamarin1 3.1.1.26+dfsg2-2~xamarin1 3.10.0-0xamarin1 3.10-1~xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 2.12.26-0xamarin1 3.10.0-0xamarin1 3.1.1.26+dfsg2-2~xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.8-0xamarin2 2.6.3+dfsg-1~xamarin2 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 1.1-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 2.6.3+dfsg-1~xamarin2 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.8-0xamarin1 2.6.3+dfsg-1~xamarin2 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 2.12.26-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10-1~xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 2.6.3+dfsg-1~xamarin2 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 2.12.26-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 2.6.3+dfsg-1~xamarin2 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 2.12.26-0xamarin1 3.8-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 1.1-0xamarin1 3.8-0xamarin2 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.8-0xamarin2 2.12.26-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 1.1-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 2.12.26-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.8-0xamarin2 2.12.26-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 2.6.3+dfsg-1~xamarin2 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.8-0xamarin2 3.10-1~xamarin1 3.8-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 5.5.0.227-0xamarin4 3.10.0-0xamarin1 1.1-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 5.5.0.227-0xamarin4 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 2.6.3+dfsg-1~xamarin2 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10-1~xamarin1 2.8.1+md54+dhx3-1~xamarin1 3.8-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 2.6.3+dfsg-1~xamarin2 3.8-0xamarin2 2.6.3+dfsg-1~xamarin2 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.8-0xamarin2 3.10.0-0xamarin1 3.10.0-0xamarin1 3.8-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.8-0xamarin2 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.8-0xamarin2 3.10-1~xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 2.6.3+dfsg-1~xamarin2 3.8-0xamarin2 3.8-0xamarin2 3.10.0-0xamarin1 3.10.0-0xamarin1 3.8-0xamarin2 3.10.0-0xamarin1 3.10.0-0xamarin1 2.8.1+md54+dhx3-1~xamarin1 3.10.0-0xamarin1 3.8-0xamarin2 1.1-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.8-0xamarin2 3.1.1.26+dfsg2-2~xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 2.6.3+dfsg-1~xamarin2 5.5.0.227-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 2.12.26-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10-1~xamarin1 3.10.0-0xamarin1 5.5.0.227-0xamarin4 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.8-0xamarin2 3.10.0-0xamarin1 3.10.0-0xamarin1 2.6.3+dfsg-1~xamarin2 3.10.0-0xamarin1 3.10.0-0xamarin1 1.1-0xamarin1 3.8-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 0.9~xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 2.12.26-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin1 2.12.26-0xamarin1 3.10.0-0xamarin1 0.9~xamarin1 3.10.0-0xamarin1 3.10.0-0xamarin

Wow. ok, i'll have a look at the nzbdrone plugin. It's possibly related to them changing the app name and website and all that fun stuff.

Media Browser plugin updated to 1.5.7Beta, now uses the 'new' download url so you can actually get the latest versions. Also a fix for the BETA option as now it will download beta if available and stable if it's newer than the beta release. That is only of course if you have "use beta" set to yes otherwise it only gets stable releases.

 

-=PhAzE=-

Ok turns out they changed the 'packages' info page that used to only hold the nzbdrone information, now it has information for every dependency also. I've updated the plugin so it culls out only nzbdrone information and all looks good again.

 

-=PhAzE=-

Ok turns out they changed the 'packages' info page that used to only hold the nzbdrone version, now it has versions for every dependency. I've updated the plugin so it culls out only nzbdrone information and all looks good again.

 

-=PhAzE=-

 

Thanks for the quick fix!

One more nzbdrone update, same issue in the install function was found and fixed.  Now updated to v 1.5.4

 

-=PhAzE=-

BYSync updated to v1.5.6 - Name is updated to BitTorrentSync now except for the plugin file name.

One more nzbdrone update, same issue in the install function was found and fixed.  Now updated to v 1.5.4

 

-=PhAzE=-

 

Im getting a failed MD5 checksum when trying to update from 2.0.0.2215 using the develop branch.

 

it downloads to the packages folder and then fails to install with the MD5 checksum error.

One more nzbdrone update, same issue in the install function was found and fixed.  Now updated to v 1.5.4

 

-=PhAzE=-

 

awesome, thanks

One more nzbdrone update, same issue in the install function was found and fixed.  Now updated to v 1.5.4

 

-=PhAzE=-

 

Im getting a failed MD5 checksum when trying to update from 2.0.0.2215 using the develop branch.

 

it downloads to the packages folder and then fails to install with the MD5 checksum error.

Fixed in 1.5.5.  The file I use to parse out the latest version has been changed a lot by the devs, and in the develop branch it actually has a lot of duplicates of versions, like they are forgetting to remove the old develop versions after a new one comes out. 

 

Anyways, parses properly now, let me know if it breaks again.

One more nzbdrone update, same issue in the install function was found and fixed.  Now updated to v 1.5.4

 

-=PhAzE=-

 

Im getting a failed MD5 checksum when trying to update from 2.0.0.2215 using the develop branch.

 

it downloads to the packages folder and then fails to install with the MD5 checksum error.

Fixed in 1.5.5.  The file I use to parse out the latest version has been changed a lot by the devs, and in the develop branch it actually has a lot of duplicates of versions, like they are forgetting to remove the old develop versions after a new one comes out. 

 

Anyways, parses properly now, let me know if it breaks again.

 

Im still getting the MD5 checksum failed.

 

I have updated the plugin to 1.5.5.

 

Delete any partially downloaded .deb from your packages folder then try the install again. Also what unraid version are you running?

Delete any partially downloaded .deb from your packages folder then try the install again. Also what unraid version are you running?

 

.deb file deleted still the same error

 

using unRAID  5.0.6