HEADS UP: snapshot server out of service until tomorrow

dszp

It's down again for me, though I haven't checked it since it was down earlier (haven't been home).

The impact of this most recent maintenance outage on currently active v2 installs brings a question to mind.

Is the function of the PFSense V2 software going to be degraded by, or contingent upon the operational status of non attached/remote servers? Is either the Release Candiate or the Final Version software going to be teathered to external servers?

What impact does it have on active installs? Other than the check for an upgrade version, is there something that's disabling your system while the snapshots are down? Obviously there's no pressing need to check for a daily upgrade once there's a stable release, though I do like having it there if there's a point release/upgrade available (especially if it's a security release–and 1.2.3 already had upgrade-from-GUI working). I can't possibly see any pfSense version in general release being "tied" to any external server--it's all 100% open source, nothing to hide...if they did something like that you could just delete it easily anyway, so there's no point.

mromero

Very probable it is not 100% exact as it is Sunday now and still barfing…...whatever happened to the mirror backup? :P

@jimp:

@bertolo:

5PM…ok... In what State? What time zone? GTM -XX:XX ?
Thanks

5PM Eastern Standard Time (EST) in the US, so GMT-5.
But that's just a general time frame. Probably not 100% exact.

jimp

There are mirrors for the official release, but not for snapshots.

Though the update check could stand to fail a bit more gracefully.

mromero

It is totally screwed up as when I open PFSENSE dashboard it cannot connect to the server and just keeps trying forever.

I suggest you disable this in the RC1 if you have no plans for an update mirror ;)

@jimp:

There are mirrors for the official release, but not for snapshots.

Though the update check could stand to fail a bit more gracefully.

@mromero:

It is totally screwed up as when I open PFSENSE dashboard it cannot connect to the server and just keeps trying forever.

I suggest you disable this in the RC1 if you have no plans for an update mirror ;)

@jimp:

There are mirrors for the official release, but not for snapshots.

Though the update check could stand to fail a bit more gracefully.

Or you could remove the system information widget during the outages? Works for me.

liontaur

Oh sure, here I am in the middle of a pretty wicked wind storm and I thought "hmmm, let's update the firewall's firmware." But I can't… Guess this means the power won't go out though as i'm doing nothing "mission critical" haha.

mromero

What outages?

We are in the middle of five days of torrential rains / cold snaps and have backup diesel and LPG generators / sat uplinks.

Short of being swept away from a mountain top elevation fortress no outages for we humble folk…...now if PFSENSE had the sense :P

@heavy1metal:

@mromero:

It is totally screwed up as when I open PFSENSE dashboard it cannot connect to the server and just keeps trying forever.

I suggest you disable this in the RC1 if you have no plans for an update mirror ;)

@jimp:

There are mirrors for the official release, but not for snapshots.

Though the update check could stand to fail a bit more gracefully.

Or you could remove the system information widget during the outages? Works for me.

Is the pfsense GUI all slowed down for you guys because of this? Mine is going super slow. Beta 5, Jan 29 build amd64.

ericab

@jigglywiggly:

Is the pfsense GUI all slowed down for you guys because of this? Mine is going super slow. Beta 5, Jan 29 build amd64.

nope not here

mromero

Is the snapshot server still down or has it changed I.P. - still dead more than a day now…..... :-\

rugby

Seems like the Bios and CPU upgrade went badly. Still down for me too.

jimp

I added some extra code to handle a slow/timed out box a bit more gracefully, and it should also not keel over if it gets a 404 for the response. Yesterday when the snapshot server was down and pointed at a varnish box so it could display a maintenance page, the actual update version file was returning 404.

If you want to try the code out without updating to a new snapshot (since it's offline again, apparently…) you can always use gitsync:
http://doc.pfsense.org/index.php/Updating_pfSense_code_between_snapshots

I don't think there have been any changes that require a binary update except for a couple things like upnp that needed recompiled.

Cino

@jimp:

If you want to try the code out without updating to a new snapshot (since it's offline again, apparently…) you can always use gitsync:
http://doc.pfsense.org/index.php/Updating_pfSense_code_between_snapshots

Jim, thank you!! I just gitsync with the mainline and smos git.. Dashboard seems to be very responsive again.

mromero

Went there and saw a lot of radioactive warning signs thus will wait until you guys get your act together with the snapshot SERVERS ::)

@jimp:

If you want to try the code out without updating to a new snapshot (since it's offline again, apparently…) you can always use gitsync:
http://doc.pfsense.org/index.php/Updating_pfSense_code_between_snapshots

jimp

@mromero:

Went there and saw a lot of radioactive warnings signs thus will wait until you guys get your act together with the snapshot SERVERS ::)

Those are just requisite rear-coverings. It's only moderately more dangerous than running a snapshot, in all honesty. You only have to worry if you are on an older snapshot and you need binary changes between the snap you have and the current snap. If you just need to update the pfSense code, gitsync is fine.

mromero

The snapshot server is up but has three day old stuff - what gives :-\

Cino

Jim,

Now that the snapshot server is up, i'm getting this error on the dashboard page:

Warning: curl_exec(): Could not call the CURLOPT_WRITEFUNCTION in /etc/inc/pfsense-utils.inc on line 1470

Unable to check for updates.

jimp

Yeah that'll be fixed on the next new snap. (Or if you gitsync again)

The snaps are building now, when they're done and uploaded it should be all good again.

Cino

@jimp:

Yeah that'll be fixed on the next new snap. (Or if you gitsync again)

The snaps are building now, when they're done and uploaded it should be all good again.

I just gitsync and the error went away. Thank you again!! I noticed something on the rcs.pfsense.org site and my dashboard…. :-) still need a new build since upnp is shot, but then my box will be official....

Good luck tomorrow and congrats!!

jimp

Actaully one more gitsync will have the real fix. I found a bug in my earlier fix. :-)