Re: [pfSense] pfSense 2.3.2-p1 RELEASE Now Available

2016-10-10 Thread Steven Spencer
Never mind. On further inspection, we were in error. :/

On 10/10/2016 05:37 PM, Steven Spencer wrote:
> Are we the only ones here who are seeing a checksum issue with the download?
>
> On 10/10/2016 12:19 PM, Morten Christensen wrote:
>> You should consider to state clearly in such announcements, if the
>> upgrade includes a reboot of the box.
>>
>>
>>
>> Den 06-10-2016 21:29, skrev Jim Thompson:
>>> Details are here: https://blog.pfsense.org/?p=2122
>>> 
>>> ___
>>>
>> -- 
>> Morten Christensen
>> ___
>> pfSense mailing list
>> https://lists.pfsense.org/mailman/listinfo/list
>> Support the project with Gold! https://pfsense.org/gold
>>
>


-- 
-- 
Steven G. Spencer, Network Administrator
KSC Corporate - The Kelly Supply Family of Companies
Office 308-382-8764 Ext. 1131
Mobile 402-765-8010 

___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold


Re: [pfSense] pfSense 2.3.2-p1 RELEASE Now Available

2016-10-10 Thread Steven Spencer
Are we the only ones here who are seeing a checksum issue with the download?

On 10/10/2016 12:19 PM, Morten Christensen wrote:
> You should consider to state clearly in such announcements, if the
> upgrade includes a reboot of the box.
>
>
>
> Den 06-10-2016 21:29, skrev Jim Thompson:
>> Details are here: https://blog.pfsense.org/?p=2122
>> 
>> ___
>>
>
> -- 
> Morten Christensen
> ___
> pfSense mailing list
> https://lists.pfsense.org/mailman/listinfo/list
> Support the project with Gold! https://pfsense.org/gold
>


-- 
-- 
Steven G. Spencer, Network Administrator
KSC Corporate - The Kelly Supply Family of Companies
Office 308-382-8764 Ext. 1131
Mobile 402-765-8010 

___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold


Re: [pfSense] pfSense 2.3.2-p1 RELEASE Now Available

2016-10-10 Thread Steve Yates
I'm curious if you removed all packages before upgrading?  The instructions 
recommend that.  We usually have done so and not had an issue.  The packages 
we've used have a setting to keep settings, for instance Suricata's "Settings 
will not be removed during package deinstallation" and pfBlockerNG's "Keep 
settings."

I have run into an issue at one point where the DNS service on the pfSense 
wasn't working so DNS requests were failing or timing out causing lots of 
issues during downloading.  I didn't pay too much attention at the time, since 
it was solved quickly, but if DNS isn't working that could be an issue.  In 
other words if DNS is running then 127.0.0.1 will always be the first DNS 
server used.

--

Steve Yates
ITS, Inc.

-Original Message-
From: List [mailto:list-boun...@lists.pfsense.org] On Behalf Of Holger Bauer
Sent: Friday, October 7, 2016 7:58 AM
To: pfSense Support and Discussion Mailing List 
Subject: Re: [pfSense] pfSense 2.3.2-p1 RELEASE Now Available

I found an older post to the list regarding the same issues with a different 
version, however this solution worked for me on my testsystem just fine:

Run from the console (ssh or local console) Option 8 to go to the shell.
Then enter the following commands:
pkg clean
pkg update
pkg upgrade
reboot

After that the system come up fine with the new release. I'll try that on some 
production systems this evening.

Regards
Holger

2016-10-07 14:51 GMT+02:00 Pete Boyd :

> Same for me, failure first time on a full install:
>
> Fetching pfSense-kernel-pfSense-2.3.2_1.txz: . done
> pkg:
> https://pkg.pfsense.org/pfSense_v2_3_2_i386-core/All/
> pfSense-kernel-pfSense-2.3.2_1.txz:
> Operation timed out
> >>> Locking package pfSense-kernel-pfSense... done.
> Failed
>
>
>
>
> --
> Pete Boyd
>
> Open Plan IT - http://openplanit.co.uk The Golden Ear - 
> http://thegoldenear.org 
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold


Re: [pfSense] pfSense 2.3.2-p1 RELEASE Now Available

2016-10-10 Thread Jim Thompson
On Fri, Oct 7, 2016 at 5:49 AM, Holger Bauer  wrote:

>
> Are there any chances that there is something wrong with the
> upgraderepository-servers of pkg.pfsense.org or that some kind of timeout
> is too low for connecting to the updaterepository?
>

I also suspect an issue with pkg.pfsense.org, but I've not proven this.

We are working on a resolution.

Jim
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold


Re: [pfSense] pfSense 2.3.2-p1 RELEASE Now Available

2016-10-10 Thread Espen Johansen
They usually do. And with kernel updates you have to.

On Mon, Oct 10, 2016, 19:20 Morten Christensen  wrote:

> You should consider to state clearly in such announcements, if the
> upgrade includes a reboot of the box.
>
>
>
> Den 06-10-2016 21:29, skrev Jim Thompson:
> > Details are here: https://blog.pfsense.org/?p=2122 <
> https://blog.pfsense.org/?p=2122>
> > ___
> >
>
> --
> Morten Christensen
> ___
> pfSense mailing list
> https://lists.pfsense.org/mailman/listinfo/list
> Support the project with Gold! https://pfsense.org/gold
>
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold


Re: [pfSense] pfSense 2.3.2-p1 RELEASE Now Available

2016-10-10 Thread Morten Christensen
You should consider to state clearly in such announcements, if the 
upgrade includes a reboot of the box.




Den 06-10-2016 21:29, skrev Jim Thompson:

Details are here: https://blog.pfsense.org/?p=2122 

___



--
Morten Christensen
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold