Jump to content
linuxserver.io

[Support] Linuxserver.io - SABnzbd

601 posts in this topic Last Reply

Recommended Posts

Like I said, you guys have amazing support and I do use a few of your containers

Share this post


Link to post

Don't forget to give credit where credit is due lol.

Share this post


Link to post

Well...New location. 5 hours West.  High speed data. Tried both local Wi-Fi and Verizon and sorry to say it still does not seem to be able to pull the update. I even went on a VPN and connected through other servers in NY, Chicago, and San Fran.  Seems to stop at the same place when it tries to run one of the scripts.

 

Kind of at a loss as to why.  Very pondering to say the least.

 

-----------------------------------

GID/UID

-----------------------------------

User uid:    99

User gid:    100

-----------------------------------

 

Hit http://ppa.launchpad.net trusty InRelease

Ign http://mirrors.syringanetworks.net/ubuntu-archive/ trusty InRelease

Hit http://ppa.launchpad.net trusty/main amd64 Packages

Hit http://mirrors.syringanetworks.net/ubuntu-archive/ trusty-security InRelease

Hit http://mirrors.syringanetworks.net/ubuntu-archive/ trusty-updates InRelease

Get:1 http://mirrors.syringanetworks.net/ubuntu-archive/ trusty Release.gpg [933 B]

Get:2 http://mirrors.syringanetworks.net/ubuntu-archive/ trusty-security/main Sources [127 kB]

Hit http://mirrors.syringanetworks.net/ubuntu-archive/ trusty-security/universe Sources

Get:3 http://mirrors.syringanetworks.net/ubuntu-archive/ trusty-security/multiverse Sources [2,165 B]

Hit http://ubuntu.mirror.constant.com/ trusty Release

Hit http://ubuntu.mirror.constant.com/ trusty-security/restricted Sources

*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...

*** Running /etc/my_init.d/10_add_user_abc.sh...

*** Running /etc/my_init.d/20_apt_update.sh...

E: Method gave invalid 103 Redirect message

*** Running /etc/my_init.d/30_set_config.sh...

*** Running /etc/rc.local...

*** Booting runit daemon...

*** Runit started as PID 41

Share this post


Link to post

And here it is from a different location, bouncing through different servers. I know you can not do anything about it, but very weird to say the least.

 

-----------------------------------

GID/UID

-----------------------------------

User uid:    99

User gid:    100

-----------------------------------

 

Hit http://ppa.launchpad.net trusty InRelease

Ign http://mirror.nexcess.net/ubuntu/ trusty InRelease

Hit http://ppa.launchpad.net trusty/main amd64 Packages

Get:1 http://mirror.nexcess.net/ubuntu/ trusty-security InRelease [64.4 kB]

Get:2 http://mirror.nexcess.net/ubuntu/ trusty-updates InRelease [64.4 kB]

Hit http://mirror.nexcess.net/ubuntu/ trusty Release.gpg

Get:3 http://mirror.nexcess.net/ubuntu/ trusty-security/main Sources [127 kB]

Get:4 http://mirror.nexcess.net/ubuntu/ trusty-security/restricted Sources [3,920 B]

Get:5 http://mirror.nexcess.net/ubuntu/ trusty-security/universe Sources [36.5 kB]

Get:6 http://mirror.nexcess.net/ubuntu/ trusty-security/multiverse Sources [2,165 B]

Get:7 http://mirror.nexcess.net/ubuntu/ trusty-security/main amd64 Packages [477 kB]

Get:8 http://mirror.nexcess.net/ubuntu/ trusty-security/restricted amd64 Packages [20.2 kB]

Get:9 http://mirror.nexcess.net/ubuntu/ trusty-security/universe amd64 Packages [156 kB]

Get:10 http://mirror.nexcess.net/ubuntu/ trusty-security/multiverse amd64 Packages [4,645 B]

Get:11 http://mirror.nexcess.net/ubuntu/ trusty-updates/main Sources [311 kB]

Get:12 http://mirror.nexcess.net/ubuntu/ trusty-updates/restricted Sources [5,219 B]

Get:13 http://mirror.nexcess.net/ubuntu/ trusty-updates/universe Sources [181 kB]

Get:14 http://mirror.nexcess.net/ubuntu/ trusty-updates/multiverse Sources [5,116 B]

Get:15 http://mirror.nexcess.net/ubuntu/ trusty-updates/main amd64 Packages [836 kB]

Get:16 http://mirror.nexcess.net/ubuntu/ trusty-updates/restricted amd64 Packages [23.4 kB]

Get:17 http://mirror.nexcess.net/ubuntu/ trusty-updates/universe amd64 Packages [427 kB]

Get:18 http://mirror.nexcess.net/ubuntu/ trusty-updates/multiverse amd64 Packages [14.1 kB]

Hit http://mirror.nexcess.net/ubuntu/ trusty Release

Get:19 http://mirror.nexcess.net/ubuntu/ trusty/main Sources [1,335 kB]

*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...

*** Running /etc/my_init.d/10_add_user_abc.sh...

*** Running /etc/my_init.d/20_apt_update.sh...

W: Size of file /var/lib/apt/lists/mirrors.ubuntu.com_mirrors.txt_dists_trusty-security_multiverse_binary-amd64_Packages.gz is not what the server reported 4645 4647

W: Size of file /var/lib/apt/lists/mirrors.ubuntu.com_mirrors.txt_dists_trusty-updates_multiverse_binary-amd64_Packages.gz is not what the server reported 14086 14091

E: Method gave invalid 103 Redirect message

*** Running /etc/my_init.d/30_set_config.sh...

*** Running /etc/rc.local...

*** Booting runit daemon...

*** Runit started as PID 40

Share this post


Link to post

And here it is from a different location, bouncing through different servers. I know you can not do anything about it, but very weird to say the least.

 

-----------------------------------

GID/UID

-----------------------------------

User uid:    99

User gid:    100

-----------------------------------

 

Hit http://ppa.launchpad.net trusty InRelease

Ign http://mirror.nexcess.net/ubuntu/ trusty InRelease

Hit http://ppa.launchpad.net trusty/main amd64 Packages

Get:1 http://mirror.nexcess.net/ubuntu/ trusty-security InRelease [64.4 kB]

Get:2 http://mirror.nexcess.net/ubuntu/ trusty-updates InRelease [64.4 kB]

Hit http://mirror.nexcess.net/ubuntu/ trusty Release.gpg

Get:3 http://mirror.nexcess.net/ubuntu/ trusty-security/main Sources [127 kB]

Get:4 http://mirror.nexcess.net/ubuntu/ trusty-security/restricted Sources [3,920 B]

Get:5 http://mirror.nexcess.net/ubuntu/ trusty-security/universe Sources [36.5 kB]

Get:6 http://mirror.nexcess.net/ubuntu/ trusty-security/multiverse Sources [2,165 B]

Get:7 http://mirror.nexcess.net/ubuntu/ trusty-security/main amd64 Packages [477 kB]

Get:8 http://mirror.nexcess.net/ubuntu/ trusty-security/restricted amd64 Packages [20.2 kB]

Get:9 http://mirror.nexcess.net/ubuntu/ trusty-security/universe amd64 Packages [156 kB]

Get:10 http://mirror.nexcess.net/ubuntu/ trusty-security/multiverse amd64 Packages [4,645 B]

Get:11 http://mirror.nexcess.net/ubuntu/ trusty-updates/main Sources [311 kB]

Get:12 http://mirror.nexcess.net/ubuntu/ trusty-updates/restricted Sources [5,219 B]

Get:13 http://mirror.nexcess.net/ubuntu/ trusty-updates/universe Sources [181 kB]

Get:14 http://mirror.nexcess.net/ubuntu/ trusty-updates/multiverse Sources [5,116 B]

Get:15 http://mirror.nexcess.net/ubuntu/ trusty-updates/main amd64 Packages [836 kB]

Get:16 http://mirror.nexcess.net/ubuntu/ trusty-updates/restricted amd64 Packages [23.4 kB]

Get:17 http://mirror.nexcess.net/ubuntu/ trusty-updates/universe amd64 Packages [427 kB]

Get:18 http://mirror.nexcess.net/ubuntu/ trusty-updates/multiverse amd64 Packages [14.1 kB]

Hit http://mirror.nexcess.net/ubuntu/ trusty Release

Get:19 http://mirror.nexcess.net/ubuntu/ trusty/main Sources [1,335 kB]

*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...

*** Running /etc/my_init.d/10_add_user_abc.sh...

*** Running /etc/my_init.d/20_apt_update.sh...

W: Size of file /var/lib/apt/lists/mirrors.ubuntu.com_mirrors.txt_dists_trusty-security_multiverse_binary-amd64_Packages.gz is not what the server reported 4645 4647

W: Size of file /var/lib/apt/lists/mirrors.ubuntu.com_mirrors.txt_dists_trusty-updates_multiverse_binary-amd64_Packages.gz is not what the server reported 14086 14091

E: Method gave invalid 103 Redirect message

*** Running /etc/my_init.d/30_set_config.sh...

*** Running /etc/rc.local...

*** Booting runit daemon...

*** Runit started as PID 40

 

It's not weird, ubuntu mirrors are often problematic.  You're not the only one.  See here.

 

EDIT: Here's my log from just a minute ago...

-----------------------------------
GID/UID
-----------------------------------
User uid: 99
User gid: 100
-----------------------------------

Hit http://ppa.launchpad.net trusty InRelease
Hit http://ppa.launchpad.net trusty/main amd64 Packages
Ign http://mirror.ox.ac.uk/sites/archive.ubuntu.com/ubuntu/ trusty InRelease
Get:1 http://mirror.ox.ac.uk/sites/archive.ubuntu.com/ubuntu/ trusty-security InRelease [64.4 kB]
Get:2 http://mirror.ox.ac.uk/sites/archive.ubuntu.com/ubuntu/ trusty-updates InRelease [64.4 kB]
Hit http://mirror.ox.ac.uk/sites/archive.ubuntu.com/ubuntu/ trusty Release.gpg
Get:3 http://mirror.ox.ac.uk/sites/archive.ubuntu.com/ubuntu/ trusty-security/main Sources [127 kB]
Get:4 http://mirror.ox.ac.uk/sites/archive.ubuntu.com/ubuntu/ trusty-security/restricted Sources [3,920 B]
Get:5 http://mirror.ox.ac.uk/sites/archive.ubuntu.com/ubuntu/ trusty-security/universe Sources [36.5 kB]
Get:6 http://mirror.ox.ac.uk/sites/archive.ubuntu.com/ubuntu/ trusty-security/multiverse Sources [2,165 B]
Get:7 http://mirror.ox.ac.uk/sites/archive.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages [477 kB]
Get:8 http://mirror.ox.ac.uk/sites/archive.ubuntu.com/ubuntu/ trusty-security/restricted amd64 Packages [20.2 kB]
Get:9 http://mirror.ox.ac.uk/sites/archive.ubuntu.com/ubuntu/ trusty-security/universe amd64 Packages [156 kB]
Get:10 http://mirror.ox.ac.uk/sites/archive.ubuntu.com/ubuntu/ trusty-security/multiverse amd64 Packages [4,647 B]
Get:11 http://mirror.ox.ac.uk/sites/archive.ubuntu.com/ubuntu/ trusty-updates/main Sources [311 kB]
Get:12 http://mirror.ox.ac.uk/sites/archive.ubuntu.com/ubuntu/ trusty-updates/restricted Sources [5,219 B]
Get:13 http://mirror.ox.ac.uk/sites/archive.ubuntu.com/ubuntu/ trusty-updates/universe Sources [181 kB]
Get:14 http://mirror.ox.ac.uk/sites/archive.ubuntu.com/ubuntu/ trusty-updates/multiverse Sources [5,111 B]
Get:15 http://mirror.ox.ac.uk/sites/archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages [836 kB]
Get:16 http://mirror.ox.ac.uk/sites/archive.ubuntu.com/ubuntu/ trusty-updates/restricted amd64 Packages [23.4 kB]
Get:17 http://mirror.ox.ac.uk/sites/archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages [427 kB]
Get:18 http://mirror.ox.ac.uk/sites/archive.ubuntu.com/ubuntu/ trusty-updates/multiverse amd64 Packages [14.1 kB]
Hit http://mirror.ox.ac.uk/sites/archive.ubuntu.com/ubuntu/ trusty Release
Hit http://mirror.ox.ac.uk/sites/archive.ubuntu.com/ubuntu/ trusty/main Sources
Hit http://mirror.ox.ac.uk/sites/archive.ubuntu.com/ubuntu/ trusty/restricted Sources
Hit http://mirror.ox.ac.uk/sites/archive.ubuntu.com/ubuntu/ trusty/universe Sources
Hit http://mirror.ox.ac.uk/sites/archive.ubuntu.com/ubuntu/ trusty/multiverse Sources
Hit http://mirror.ox.ac.uk/sites/archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
Hit http://mirror.ox.ac.uk/sites/archive.ubuntu.com/ubuntu/ trusty/restricted amd64 Packages
Hit http://mirror.ox.ac.uk/sites/archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages
Hit http://mirror.ox.ac.uk/sites/archive.ubuntu.com/ubuntu/ trusty/multiverse amd64 Packages
Fetched 2,759 kB in 2s (1,110 kB/s)
Reading package lists...
Dec 9 00:39:41 8f0dd4ac58d1 syslog-ng[59]: syslog-ng starting up; version='3.5.3'

 

As you can see I'm hitting different mirrors and they happen to be working, this is not always the case.

Share this post


Link to post

Thanks CHBMB, I'll keep trying. ;)

 

I've been giving this a lot of thought over the last couple of days....

 

Due to being mobile your connection, I imagine is a little less in your locus of control than the connections of most of our users.  So that leaves you with a conundrum....

 

You could accept that sometimes you aren't going to be running the most up to date version, which most of the time won't be a problem.  TBH I don't even look at the versions unless I notice a problem (which is very rarely)  or you could consider a "set" container which doesn't update automatically.  This would be stable, but if there's a problem then the docker author would need to generate a new build with the fixes applied, and when there is an update again you'd have to wait for the author to apply the update, a situation not dissimilar to the position you currently find yourself in.

 

I, and, I presume most of our users, like the idea of being completely up to date, but we know that if there is a problem we have definite access to fixed broadband infrastructure.  Your use case is somewhat an anomaly in today's society and it may be that would be a good argument for favouring a stable docker, rather than the dynamic containers we offer. 

 

Like I say, there's not really a right or wrong answer but it's food for thought.

 

Don't take this the wrong way, but we're all volunteers, doing this for fun, but it does take up a lot of our time, and whilst we don't mind providing support for container issues or even docker configuration, we cannot help with areas that are outside of our control, we're good but not that good.  ;)

 

ATB

 

CHBMB

Share this post


Link to post

Thanks for the thoughts

 

I do understand where you are coming from on this. The strange this is I really do not have issues connection wise.  Heck, I have a full time VPN running that is streaming a live video stream. (http://www.outsideourbubble.com/live-coach-cam) I use a VPN to get around Verizon's private IP so I can get in and out of our coaches network.  Also, remember I mentioned I also tried a local connection, thus a totally different ISP with the same results.  Attached is a graph showing my VPN connection to the camera over the last 48 hours. You can see that the connection remains solid and you can tell when we travel as we have a lot of people join along. You can even see the area we went through today along I-10 that has no internet. ;) (The time is not set on the graph, it is ahead.)

 

All in all, been traveling for a long time and we live on the Internet and make our living on it as I still own a few other communities. I really only run into issues when are a in a far out area with poor service (then I have boosters and directional antennas to try to correct) or when we get on a crowded tower. Like this past weekend.

 

But with all that said...Yup, something surely is weird with trying to get an update.  Guess I am just unlikely.  And yes, totally agree that if it is working, don't touch it.  And I usually do not upgrade unless a new feature comes out or something stops working with some service. That is why I was a little concerned with the auto update. But at the same time while I have run into issues with other software updates, but could revert back, I really have never had an issue with Sonorr, SickBeard (When I was running it before it was dropped.) and SABnzdb updates, thus was not totally worries but would like the current beta. :)

 

Oh, in regards to it's working so don't tough it and then why did I choose to do this vs using the windows machine that has always just worked?  Well, I ran into an issue where the that machine, running SSD's, I do not turn off when traveling.  Well Sonorr found some new files and brought them down and I never knew it as they could not be processed out to the server for it was off.  So over time, they collected, and collected...  So I said Hey, that server is just sitting doing nothing most of the time...so lets use it.  So when we travel, I shut it down so no more issues.  So, here we are. :)

 

Thanks again.  Come this Sunday we were be a a park were I will have access to 75Mbps off a fiber line right into our coach.  I have a port on the back of the coach where I can plug right in and it runs to the front to feed the router. All devices flow though the router (Asus RT-N66U) which is either wired to a hard line to the net or is connected via ethernet to a Raspberry Pi that handles the Internet via USB from a JetPack. (It also handles the VPN.)

 

Thanks again for the support.

 

 

screenshot_1116.png.2ce3bb571413be582c3553a46bcdf365.png

Share this post


Link to post

Hi...

 

Still have the upgrade issue I am sorry to say.  In asking Goggle about "E: Method gave invalid 103 Redirect message" what comes back seems to be something Ubuntu related with there being a recent bug in it introduced.  I do not know, just just asking, does UnRaid use Ubuntu or does Docker?  If so, then that bring up the question of was it recently updated in the last release of UnRaid?  Asking for I am on the most current version of UnRaid and maybe, for those that have no issues with the auto updates, they are not on the current release. (Just a thought I wanted to toss out just to check.)

 

https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1479045

 

https://goo.gl/x7aGiI

 

I have tried... 3 different ISP's, several DNS's, used different locations using a VPN, hard wired the network to a cable modem vs using Verizon. I have moved through 3 states on Verizon. :)  All in all, same result keep happening and this has been over a number of days.

 

So, just asking about the above just in case.

 

Thanks.

Share this post


Link to post

Hi...

 

Still have the upgrade issue I am sorry to say.  In asking Goggle about "E: Method gave invalid 103 Redirect message" what comes back seems to be something Ubuntu related with there being a recent bug in it introduced.  I do not know, just just asking, does UnRaid use Ubuntu or does Docker?  If so, then that bring up the question of was it recently updated in the last release of UnRaid?  Asking for I am on the most current version of UnRaid and maybe, for those that have no issues with the auto updates, they are not on the current release. (Just a thought I wanted to toss out just to check.)

 

https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1479045

 

https://goo.gl/x7aGiI

 

I have tried... 3 different ISP's, several DNS's, used different locations using a VPN, hard wired the network to a cable modem vs using Verizon. I have moved through 3 states on Verizon. :)  All in all, same result keep happening and this has been over a number of days.

 

So, just asking about the above just in case.

 

Thanks.

 

Unraid is Slackware not Ubuntu, however our docker containers are based on phusion which is a Ubuntu base.  So there is no need to update Unraid, I suspect this is something that'll need to be fixed in Ubuntu before we can do 'owt about it...

Share this post


Link to post

First off, thank you greatly for the linuxserver.io dockers, each of the ones I've enabled are able to start without much configuration whatsoever.

 

Although after running through this setup I have a quick question for the guru's about how I have my system setup with this docker.

 

System is running unraid 6.1.6 , SAB 0.8.0Beta3 [0b6395f], I've mapped the folders to a 256Gb SSD formatted with xfs I've mounted using unassigned devices outside of my array with some basic folder structure in the root (/SAB/downloads/ and /SAB/incomplete/ etc for example) to keep each docker separate for basic house keeping. According to Unassigned devices the SSD has a total used of 9.1GB out of the 256Gb (for some reason it's also reporting that it has 253Tb free which I'm guessing has more to do with how the drive is reporting to unassigned devices but that's another issue to track down at a later time)

 

My issue is that even when I've mapped the folders correctly, SAB is reporting only 7.1Gb free space, even though the SSD has more than that free. Is this something that I should be concerned with? I have yet to initiate a download but wanted to confirm if what SAB is reporting is the correct amount of free space for the download/temp folder.

 

Share this post


Link to post

First off, thank you greatly for the linuxserver.io dockers, each of the ones I've enabled are able to start without much configuration whatsoever.

 

Although after running through this setup I have a quick question for the guru's about how I have my system setup with this docker.

 

System is running unraid 6.1.6 , SAB 0.8.0Beta3 [0b6395f], I've mapped the folders to a 256Gb SSD formatted with xfs I've mounted using unassigned devices outside of my array with some basic folder structure in the root (/SAB/downloads/ and /SAB/incomplete/ etc for example) to keep each docker separate for basic house keeping. According to Unassigned devices the SSD has a total used of 9.1GB out of the 256Gb (for some reason it's also reporting that it has 253Tb free which I'm guessing has more to do with how the drive is reporting to unassigned devices but that's another issue to track down at a later time)

 

My issue is that even when I've mapped the folders correctly, SAB is reporting only 7.1Gb free space, even though the SSD has more than that free. Is this something that I should be concerned with? I have yet to initiate a download but wanted to confirm if what SAB is reporting is the correct amount of free space for the download/temp folder.

 

Hmmm, I don't use SABnzbd myself, but you're right that does sound a bit odd.  Can you post me screenshots of your SABNzbd mappings and your unassigned devices page with the disks expanded to show the partitions like this:

 

HPGcPNN.jpg

Share this post


Link to post

Here you go. Aside from the full mapping being shown that is. Naming is too long to show all at once with the drop down.

 

Should also mention that this does affect the ability to download files larger than the 7.1Gb that are showing as free.

device.png.4684bd18c1be02d5533433722a9c8567.png

mapping.png.6fd53a5c6f4f13542501cb2ea6aec2c3.png

Share this post


Link to post

Here you go. Aside from the full mapping being shown that is. Naming is too long to show all at once with the drop down.

 

Should also mention that this does affect the ability to download files larger than the 7.1Gb that are showing as free.

Ok that looks good, now can you post me a screenshot of your sabnzbd webui config where you've setup your download locations.  And do you have a 10GB docker image by any chance?

Share this post


Link to post

Yes I do have a 10.7Gb docker image, located on the cache drive of the array but it's cache only so it won't be moved.

 

So to recap, docker image is on the cache drive of my array, folders are mapped to folders outside of array. Would this be the issue? If so, is there a simple way to move the docker image from the cache drive to the unassigned drive as that's where I'll be keeping the additional folders.

 

Here's the details.

docker.png.c85d261a35005eaee3f6a195d15367cf.png

webgui.png.48e5f6bbc4beb26d4214dc230dd8d3cb.png

Share this post


Link to post

Another interesting situation occurred.

 

I stopped the array to see if there was a simple way to move the docker image which was no real help since docker can only be managed when the array is running but when I restarted the array the newly added dockers (Couchpotato, SAB and Sonarr) all reverted back to fresh installs. I'm assuming that is due to the /config folders being blank as they're all mapped to the same drive.

Share this post


Link to post

OK, I've installed sabnzbd on my machine and I can't reproduce this.

 

Essentially what is happening is that sabnzbd instead of using the paths you've set is downloading inside the docker.img one thought I've had is when you power on your machine, it could be that a race condition occurs so that docker service starts and sabnzbd starts before your SSD is mounted in Unassigned Devices.  As sabnzbd can't find the mappings you've set, it doesn't map them at all and leaves /downloads and /incomplete-downloads inside the container and therefore inside the docker.img...

 

This should be fixed by restarting the container, however if this is the case then the problem will start again on reboot as it will face the race conditions again..

Share this post


Link to post

I appreciate the detailed response, I'm pretty certain that I restarted the container with no change but I'll try again after work.

 

Yeah, I thought you may have, any chance the path in the docker mappings is wrong?  You know you can change that in Unassigned Devices to make it a little easier don't you? For instance I've changed my mapping to /mnt/virtualisation for my SSD.

 

 

Share this post


Link to post

Hi,

 

I too am stuck on beta1. It never updates for me. I have had this running for a month and I started/stopped just about every other day as I have been using this as an on demand backup.

 

Here's my log:

Dec 9 20:34:12 aa4ad93732b5 syslog-ng[47]: syslog-ng starting up; version='3.5.3'

-----------------------------------
GID/UID
-----------------------------------
User uid: 99
User gid: 100
-----------------------------------

Hit http://ppa.launchpad.net trusty InRelease
Ign http://mirrordenver.fdcservers.net/ubuntu/ trusty InRelease
Hit http://ppa.launchpad.net trusty/main amd64 Packages
Get:1 http://mirrordenver.fdcservers.net/ubuntu/ trusty-security InRelease [64.4 kB]
Get:2 http://mirrordenver.fdcservers.net/ubuntu/ trusty-updates InRelease [64.4 kB]
Hit http://mirrordenver.fdcservers.net/ubuntu/ trusty Release.gpg
Get:3 http://mirrordenver.fdcservers.net/ubuntu/ trusty-security/main Sources [127 kB]
Get:4 http://mirrordenver.fdcservers.net/ubuntu/ trusty-security/restricted Sources [3,920 B]
Get:5 http://mirrordenver.fdcservers.net/ubuntu/ trusty-security/universe Sources [36.5 kB]
Get:6 http://mirrordenver.fdcservers.net/ubuntu/ trusty-security/multiverse Sources [2,165 B]
Get:7 http://mirrordenver.fdcservers.net/ubuntu/ trusty-security/main amd64 Packages [477 kB]
Get:8 http://mirrordenver.fdcservers.net/ubuntu/ trusty-security/restricted amd64 Packages [20.2 kB]
Get:9 http://mirrordenver.fdcservers.net/ubuntu/ trusty-security/universe amd64 Packages [156 kB]
Get:10 http://mirrordenver.fdcservers.net/ubuntu/ trusty-security/multiverse amd64 Packages [4,645 B]
Get:11 http://mirrordenver.fdcservers.net/ubuntu/ trusty-updates/main Sources [311 kB]
Get:12 http://mirrordenver.fdcservers.net/ubuntu/ trusty-updates/restricted Sources [5,219 B]
Get:13 http://mirrordenver.fdcservers.net/ubuntu/ trusty-updates/universe Sources [183 kB]
Get:14 http://mirrordenver.fdcservers.net/ubuntu/ trusty-updates/multiverse Sources [5,116 B]
Get:15 http://mirrordenver.fdcservers.net/ubuntu/ trusty-updates/main amd64 Packages [836 kB]
Get:16 http://mirrordenver.fdcservers.net/ubuntu/ trusty-updates/restricted amd64 Packages [23.4 kB]
Get:17 http://mirrordenver.fdcservers.net/ubuntu/ trusty-updates/universe amd64 Packages [431 kB]
Get:18 http://mirrordenver.fdcservers.net/ubuntu/ trusty-updates/multiverse amd64 Packages [14.1 kB]
Hit http://mirrordenver.fdcservers.net/ubuntu/ trusty Release
Dec 14 14:32:36 aa4ad93732b5 syslog-ng[49]: syslog-ng starting up; version='3.5.3'

 

When I docker exec in and do apt-get update, I get the following:

 

root@aa4ad93732b5:/etc/my_init.d# apt-get update
Hit http://ppa.launchpad.net trusty InRelease
Ign http://mirrordenver.fdcservers.net/ubuntu/ trusty InRelease
Hit http://ppa.launchpad.net trusty/main amd64 Packages
Hit http://mirrordenver.fdcservers.net/ubuntu/ trusty-security InRelease
Hit http://mirrordenver.fdcservers.net/ubuntu/ trusty-updates InRelease
Get:1 http://mirrordenver.fdcservers.net/ubuntu/ trusty Release.gpg [933 B]
Hit http://mirrordenver.fdcservers.net/ubuntu/ trusty-security/main Sources
Hit http://mirrordenver.fdcservers.net/ubuntu/ trusty-security/restricted Sources
E: Method gave invalid 103 Redirect message

 

I get the same result when I use the command that linuxserver team's baseimage has:

apt-get update && apt-get --only-upgrade install -yqq $APTLIST

 

I believe that is why it fails to update sab. I don't have this issue with any other containers.

 

I tested duckdns, another phusion based container and there are no issues with apt-get update there.

 

I then did apt-get upgrade in sab and it went ahead and updated to beta 3. It still fails on apt-get update.

 

Do you think there might be an issue with the sources.list provided in the baseimage?

 

Thanks

Share this post


Link to post

Hi,

 

I too am stuck on beta1. It never updates for me. I have had this running for a month and I started/stopped just about every other day as I have been using this as an on demand backup.

 

Here's my log:

Dec 9 20:34:12 aa4ad93732b5 syslog-ng[47]: syslog-ng starting up; version='3.5.3'

-----------------------------------
GID/UID
-----------------------------------
User uid: 99
User gid: 100
-----------------------------------

Hit http://ppa.launchpad.net trusty InRelease
Ign http://mirrordenver.fdcservers.net/ubuntu/ trusty InRelease
Hit http://ppa.launchpad.net trusty/main amd64 Packages
Get:1 http://mirrordenver.fdcservers.net/ubuntu/ trusty-security InRelease [64.4 kB]
Get:2 http://mirrordenver.fdcservers.net/ubuntu/ trusty-updates InRelease [64.4 kB]
Hit http://mirrordenver.fdcservers.net/ubuntu/ trusty Release.gpg
Get:3 http://mirrordenver.fdcservers.net/ubuntu/ trusty-security/main Sources [127 kB]
Get:4 http://mirrordenver.fdcservers.net/ubuntu/ trusty-security/restricted Sources [3,920 B]
Get:5 http://mirrordenver.fdcservers.net/ubuntu/ trusty-security/universe Sources [36.5 kB]
Get:6 http://mirrordenver.fdcservers.net/ubuntu/ trusty-security/multiverse Sources [2,165 B]
Get:7 http://mirrordenver.fdcservers.net/ubuntu/ trusty-security/main amd64 Packages [477 kB]
Get:8 http://mirrordenver.fdcservers.net/ubuntu/ trusty-security/restricted amd64 Packages [20.2 kB]
Get:9 http://mirrordenver.fdcservers.net/ubuntu/ trusty-security/universe amd64 Packages [156 kB]
Get:10 http://mirrordenver.fdcservers.net/ubuntu/ trusty-security/multiverse amd64 Packages [4,645 B]
Get:11 http://mirrordenver.fdcservers.net/ubuntu/ trusty-updates/main Sources [311 kB]
Get:12 http://mirrordenver.fdcservers.net/ubuntu/ trusty-updates/restricted Sources [5,219 B]
Get:13 http://mirrordenver.fdcservers.net/ubuntu/ trusty-updates/universe Sources [183 kB]
Get:14 http://mirrordenver.fdcservers.net/ubuntu/ trusty-updates/multiverse Sources [5,116 B]
Get:15 http://mirrordenver.fdcservers.net/ubuntu/ trusty-updates/main amd64 Packages [836 kB]
Get:16 http://mirrordenver.fdcservers.net/ubuntu/ trusty-updates/restricted amd64 Packages [23.4 kB]
Get:17 http://mirrordenver.fdcservers.net/ubuntu/ trusty-updates/universe amd64 Packages [431 kB]
Get:18 http://mirrordenver.fdcservers.net/ubuntu/ trusty-updates/multiverse amd64 Packages [14.1 kB]
Hit http://mirrordenver.fdcservers.net/ubuntu/ trusty Release
Dec 14 14:32:36 aa4ad93732b5 syslog-ng[49]: syslog-ng starting up; version='3.5.3'

 

When I docker exec in and do apt-get update, I get the following:

 

root@aa4ad93732b5:/etc/my_init.d# apt-get update
Hit http://ppa.launchpad.net trusty InRelease
Ign http://mirrordenver.fdcservers.net/ubuntu/ trusty InRelease
Hit http://ppa.launchpad.net trusty/main amd64 Packages
Hit http://mirrordenver.fdcservers.net/ubuntu/ trusty-security InRelease
Hit http://mirrordenver.fdcservers.net/ubuntu/ trusty-updates InRelease
Get:1 http://mirrordenver.fdcservers.net/ubuntu/ trusty Release.gpg [933 B]
Hit http://mirrordenver.fdcservers.net/ubuntu/ trusty-security/main Sources
Hit http://mirrordenver.fdcservers.net/ubuntu/ trusty-security/restricted Sources
E: Method gave invalid 103 Redirect message

 

I get the same result when I use the command that linuxserver team's baseimage has:

apt-get update && apt-get --only-upgrade install -yqq $APTLIST

 

I believe that is why it fails to update sab. I don't have this issue with any other containers.

 

I tested duckdns, another phusion based container and there are no issues with apt-get update there.

 

I then did apt-get upgrade in sab and it went ahead and updated to beta 3. It still fails on apt-get update.

 

Do you think there might be an issue with the sources.list provided in the baseimage?

 

Thanks

 

root@9675c48f5c2b:/etc/my_init.d# apt-get update
Hit http://ppa.launchpad.net trusty InRelease
Hit http://ppa.launchpad.net trusty/main amd64 Packages
Ign http://ubuntu.mirrors.uk2.net/ubuntu/ trusty InRelease
Hit http://ubuntu.mirrors.uk2.net/ubuntu/ trusty-security InRelease
Hit http://ubuntu.mirrors.uk2.net/ubuntu/ trusty-updates InRelease
Hit http://ubuntu.mirrors.uk2.net/ubuntu/ trusty Release.gpg
Hit http://ubuntu.mirrors.uk2.net/ubuntu/ trusty-security/main Sources
Hit http://ubuntu.mirrors.uk2.net/ubuntu/ trusty-security/restricted Sources
Hit http://ubuntu.mirrors.uk2.net/ubuntu/ trusty-security/universe Sources
Hit http://ubuntu.mirrors.uk2.net/ubuntu/ trusty-security/multiverse Sources
Hit http://ubuntu.mirrors.uk2.net/ubuntu/ trusty-security/main amd64 Packages
Hit http://ubuntu.mirrors.uk2.net/ubuntu/ trusty-security/restricted amd64 Packages
Hit http://ubuntu.mirrors.uk2.net/ubuntu/ trusty-security/universe amd64 Packages
Hit http://ubuntu.mirrors.uk2.net/ubuntu/ trusty-security/multiverse amd64 Packages
Hit http://ubuntu.mirrors.uk2.net/ubuntu/ trusty Release
Hit http://ubuntu.mirrors.uk2.net/ubuntu/ trusty-updates/main Sources
Hit http://ubuntu.mirrors.uk2.net/ubuntu/ trusty-updates/restricted Sources
Hit http://ubuntu.mirrors.uk2.net/ubuntu/ trusty-updates/universe Sources
Hit http://ubuntu.mirrors.uk2.net/ubuntu/ trusty-updates/multiverse Sources
Hit http://ubuntu.mirrors.uk2.net/ubuntu/ trusty-updates/main amd64 Packages
Hit http://ubuntu.mirrors.uk2.net/ubuntu/ trusty-updates/restricted amd64 Packages
Hit http://ubuntu.mirrors.uk2.net/ubuntu/ trusty-updates/universe amd64 Packages
Hit http://ubuntu.mirrors.uk2.net/ubuntu/ trusty-updates/multiverse amd64 Packages
Hit http://ubuntu.mirrors.uk2.net/ubuntu/ trusty/main Sources
Hit http://ubuntu.mirrors.uk2.net/ubuntu/ trusty/restricted Sources
Hit http://ubuntu.mirrors.uk2.net/ubuntu/ trusty/universe Sources
Hit http://ubuntu.mirrors.uk2.net/ubuntu/ trusty/multiverse Sources
Hit http://ubuntu.mirrors.uk2.net/ubuntu/ trusty/main amd64 Packages
Hit http://ubuntu.mirrors.uk2.net/ubuntu/ trusty/restricted amd64 Packages
Hit http://ubuntu.mirrors.uk2.net/ubuntu/ trusty/universe amd64 Packages
Hit http://ubuntu.mirrors.uk2.net/ubuntu/ trusty/multiverse amd64 Packages
Reading package lists... Done

 

 

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.