Build internal repo to upgrade from 9.3-stable to 11.1-u7

[fds09w4jih4r]

Seems this is a known issue:

https://www.ixsystems.com/community/threads/cannot-reach-update-server-9-3-upgrade.74971/

We do know we can pull that file now from:

http://update-master.ixsystems.com/updates/ix_crl.pem

 

[Chris Moore]

Ok so my issue isn't the company proxy but rather that https://web.ixsystems.com/updates/ix_crl.pem is broken for everyone in the world.... who can fix that.. ? :)

This is something that iXsystems will need to figure out. They probably thought that everyone had upgraded and turned off the old server.
Did you submit a bug report on this?

 

[jgreco]

Ok so my issue isn't the company proxy but rather that https://web.ixsystems.com/updates/ix_crl.pem is broken for everyone in the world.... who can fix that.. ? :)

This seems to be a holdover of when iX tried to do their own software updates. "web.ixsystems.com" resolves to a HE IP address and isn't answering on 80/443/ICMP. I suspect the thing was just turned off after the transition to a CDN without sufficient consideration of the side effects.

 

[Yorick]

Oh well done! So - there’s a resource used in the 9.3 upgrade but, clearly, not in later versions, and that resource is now down. That’s what it sounds like, right?

Here’s to ixsystems fixing that.

In the meantime - try adding a hosts entry that points web.ixsystems to the IP for update-master.ixsystems? Ugly but might just work.

 

[fds09w4jih4r]

Guys, so even in version 11 of freenas, this file is trying to be pulled... I think our core issue is the following with manifest file:

Apr 25 04:46:56 n32c01nas008 alert.py: [freenasOS.Update:1375] Could not load cached manifest file: <urlopen error [Errno
61] Connection refused>

 

[fds09w4jih4r]

This seems to be a holdover of when iX tried to do their own software updates. "web.ixsystems.com" resolves to a HE IP address and isn't answering on 80/443/ICMP. I suspect the thing was just turned off after the transition to a CDN without sufficient consideration of the side effects.

So I have now gone ahead and installed a new 9.3 on my home machine off the corp network.. It also can't update check when the train is changed to 11. Or check any train for that matter......

I can try a host key entry to see what would happen...

 

[fds09w4jih4r]

Oh well done! So - there’s a resource used in the 9.3 upgrade but, clearly, not in later versions, and that resource is now down. That’s what it sounds like, right?

Here’s to ixsystems fixing that.

In the meantime - try adding a hosts entry that points web.ixsystems to the IP for update-master.ixsystems? Ugly but might just work.

That didn't seem to help.. I confirmed with a ping test it was picking up the new IP of course, which it is... Simply put, 9.3 upgrade to anything is borked... Unless I hand ISO upgrade... We're looking at just automating the new deployment of 11.2 as fresh onto these hosts instead. We've got nothing to preserve data wise, so this seems like a good way forward also...

 

[Yorick]

Oh right of course, once you put the hosts entry in the cert no longer matches, no dice.

You can still grab the file from update-master and stick it onto your own system pretending to be web, complete with cert. At some point the effort seems hardly worth it though, agreed.

 

[fds09w4jih4r]

Oh right of course, once you put the hosts entry in the cert no longer matches, no dice.

You can still grab the file from update-master and stick it onto your own system pretending to be web, complete with cert. At some point the effort seems hardly worth it though, agreed.

I think ixsystems just needs to fix it so that we can still update properly or give up on the whole thing.. :)

 

[fds09w4jih4r]

Is there automation done by someone to deploy freenas 11.2 or 11?

 

[Kris Moore]

We've fixed it on our end. Should be up in the next hour once DNS settles down.

 

[fds09w4jih4r]

We've fixed it on our end. Should be up in the next hour once DNS settles down.

Fantastic beyond belief! I will test in a couple of hours.. :)

 

[fds09w4jih4r]

The following command is now working from shell, GUI still not, which is fine but something you may wish to check:

freenas-update -v -T FreeNAS-11-STABLE check

Testing a update afterwards...

 

[fds09w4jih4r]

We've fixed it on our end. Should be up in the next hour once DNS settles down.

Hey Kris, I think its broken again.. Or it feels like it based on my tests... I can pick the train 11.1 but then update failed when trying to check. I tried with and without proxy...

 

[fds09w4jih4r]

We've fixed it on our end. Should be up in the next hour once DNS settles down.

So seems I am able to update, but only via commandline and not gui.. I ran these commands in sequence:

freenas-update -T FreeNAS-11-STABLE -v check <<< this first!
freenas-update -T FreeNAS-11-STABLE -v update << to update

I will try now to go from 11.1 to the latest build of 11.2

 

[fds09w4jih4r]

From 11.1 u7 its updating to 11.2 fine... So clearly there is something blocking in the GUI again..