cant pull from depositry


loady

Recommended Posts

I upgraded my cache drive and i backed everything up except the actuall docker image DOH!, not so bad as the appdata folder is safe and everythings back on the cache, i cant install any dockers now, im trying to put binhex dockers on that i had and i keep getting failed error.

 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-plexpass' --net='host' --privileged=true -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e 'TRANS_DIR'='/config/transcode' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user/':'/media':'rw' -v '/mnt/cache/appdata/':'/config':'rw' 'binhex/arch-plexpass' 

Unable to find image 'binhex/arch-plexpass:latest' locally
/usr/bin/docker: Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 194.168.8.100:53: read udp 192.168.11.122:52518->194.168.8.100:53: i/o timeout.
See '/usr/bin/docker run --help'.

Link to comment
On 11/11/2018 at 4:54 PM, Squid said:

Have you tried recreating the docker.img file   Also post diags

tower-diagnostics-20181114-0102.zip

 

how would i got about trying to rebuild docker image? Thus far, the docker image was deleted anyway when i upgraded the cache, i made a new image and tried to get the dockers back via user defined templates but they return with a command failed error, i tried directly from binhex's repositry to no avail. also there is an error scrolling the log

Edited by loady
Link to comment

Looks like you've somehow managed to create a share called ":"  that's causing those errors 

 

Doing this

mv /mnt/user/: /mnt/user/unknown


 

Should fix the error and then you can figure out how that ":" folder got created (and look in the unknown share to see what's in it)

 

You actual problem is more than likely advanced buttons.plg  Delete /config/plugins/advanced.buttons.plg from the flash drive.  Reboot and hopefully everything is good to go.

 

Additionally, you've got an ancient plugin (ntfs-3g-x86_64 and powerdown)  This is more than likely not going to work at all.  I would also delete those .plg

 

Afterwards, I would install Fix Common Problems via the Apps tab (but update CA first), run a scan and do whatever else it suggests.

Edited by Squid
Link to comment
2 hours ago, Squid said:

Looks like you've somehow managed to create a share called ":"  that's causing those errors 

 

Doing this


mv /mnt/user/: /mnt/user/unknown


 

Should fix the error and then you can figure out how that ":" folder got created (and look in the unknown share to see what's in it)

 

You actual problem is more than likely advanced buttons.plg  Delete /config/plugins/advanced.buttons.plg from the flash drive.  Reboot and hopefully everything is good to go.

 

Additionally, you've got an ancient plugin (ntfs-3g-x86_64 and powerdown)  This is more than likely not going to work at all.  I would also delete those .plg

 

Afterwards, I would install Fix Common Problems via the Apps tab (but update CA first), run a scan and do whatever else it suggests.

Thanks squid, very informative, i never have trouble with unraid to be honest, a reason why i recommend it to people, however, when something does go awry (usually brought on by my own actions) i am not entirely sure where to look, what to do, I did see that that folder too but i wasn't going to delete it in case of thermo nuclear meltdown. I had an odd issue where one of the array disks had become unassigned along the way during the upgrade of ssd, i just identified it and reassigned and UNraid decided to rebuild the whole drive, is that normal ? should there have been a different procedure ?, not to worried except for the fact its a five hour task i have to wait to finish before i can reboot.

 

I have never removed anything other than plugins and dockers and just keep on upgrading UNraid every now and then, i imagine a few good things that were once plugins have become an working part of the UNraid OS itself, one of which i am curious about is cache_dirs, is this an automatic feature of UNraid now ?..should i delete the plugin if indeed its still there and is there a user interface for it ? i mainly use the server for media streaming and keeping family files and pictures, my daughters access it to keep their uni stuff and other poo on, i would like the disks not to spin up when just browsing the server. Looks like the phanton DIR is empty, i am just going to delete after i follow your instruction above.

 

Screenshot 2018-11-14 14.26.03.png

Edited by loady
added picture
Link to comment
1 minute ago, loady said:

had become unassigned along the way during the upgrade of ssd, i just identified it and reassigned and UNraid decided to rebuild the whole drive, is that normal ?

You would have jarred the sata / power cable to the drive in the course of replacing the other one.  You're now the poster child for hotswap bays being recommended

 

Some plugins as unRaid evolves no longer work and/or cause issues.  Advanced Buttons is one of them (started causing issues on 6.4)  Fix Common Problems being installed will let you know about this kind of stuff.

 

3 minutes ago, loady said:

is cache_dirs, is this an automatic feature of UNraid now

Nope.  Cache Dirs is still an optional add-on.

Link to comment
1 hour ago, loady said:

Hmmmmm...upgrade hardware, perhaps i might make the UNraid user calendar for 2019.

CSE-M35T_1B.jpg   CSE-M35T_1B_1.png

 

SuperMicro CSE-M35T-1B

 

Maybe not calendar material, but definitely *** unRAID ServerPorn ***

 

I use these, had 'em for years. Built like tanks and almost as heavy. Amazed that they're still sold everywhere, but don't pay too much for them. I think they came out before SATA3 spec, but who needs that; can't saturate a SATA3 port with spinning rust anyway. That's what SSD cache is for, right?

Edited by ClintE
Link to comment
1 hour ago, loady said:

Looks like the phanton DIR is empty, i am just going to delete after i follow your instruction above.

After looking at the edited post with the picture, I can tell you that it was created by a typo in one of your docker apps.  If it gets recreated, then check all of your apps for typos

Link to comment
1 minute ago, Squid said:

I can tell you that you do need to update CA.  Don't think that's the problem though.

 

Try resetting the router / switch.

already did, and the server again for good measure,  i only wanted to swap out the cache for a bigger one and its broke

 

Link to comment

still cant get dockers either...

 

Pulling image: binhex/arch-plexpass:latest

TOTAL DATA PULLED: 0 B



Command:
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-plexpass' --net='host' -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e 'TRANS_DIR'='/config/transcode' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user':'/media':'rw' -v '/mnt/user/appdata/binhex-plexpass':'/config':'rw' 'binhex/arch-plexpass' 
Unable to find image 'binhex/arch-plexpass:latest' locally
/usr/bin/docker: Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 194.168.8.100:53: read udp 192.168.11.122:53620->194.168.8.100:53: i/o timeout.
See '/usr/bin/docker run --help'.

The command failed.

 

Link to comment
21 minutes ago, Squid said:

I can tell you that you do need to update CA.  Don't think that's the problem though.

 

Try resetting the router / switch.

just had a thought, i took this server from my home address and brought it to another location to do the cache upgrade, i changed the network here to reflect the ip address of the server, so its on a completley different ISP...could this be an issue ?, given that the server is set with a static ip address, maybe it IS reflecting the wrong DNS as it complained about ?

Edited by loady
Link to comment
1 hour ago, Squid said:

Could be pointed at the wrong gateway in network settings.  Or the static IP address isn't on the same subnet as the gateway.

 

The actual DNS shouldn't matter as 8.8.8.8 / 8.8.4.4 are google's universal addresses

Sorted. I just went into network settings and set the IP to auto and it's working now, the ISP router here is crap so I have another one setup as a wireless bridge to which the server is plugged into, much quicker to do what I did rather then mess around with the routers, when I take it back to its home I'll set the IP back to static and all shod be well. Thanks squid, for your help, its purring like a tiger now

Link to comment

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.