Re: [pfSense] pfSense 2.3_1 ntpd isn't restarting
Hi, it doesn't matter if i restart via WebGUI or directly in Terminal. Logs say ntpd is starting but nothing happens, and on cli it just says nothing, no error, no warning. Greetings Juergen Am 06.05.2016 um 23:34 schrieb WebDawg: > I would try running ntpd from shell and see what happens. > > On Fri, May 6, 2016 at 3:45 PM, J. Echter >wrote: >> Am 06.05.2016 um 22:43 schrieb WebDawg: >>> Anything in the logs? >>> >>> On Fri, May 6, 2016 at 3:42 PM, J. Echter >>> wrote: Hi, i did the 2.3_1 update and all seemed fine, but my ntpd service isn't coming back up. I even rebooted the machine and it still doesn't start. There's also nothing in the logs. sockstat -l | grep 123 shows nothing. Where is the ntpd binary located? I found nothing. Where should i look at next? Thanks Juergen ___ 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 >>> >> >> No, theres nothing, only gui says ntpd is restarted, nothing else. >> >> >> ___ >> 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 > ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] pfSense 2.3_1 ntpd isn't restarting
I would try running ntpd from shell and see what happens. On Fri, May 6, 2016 at 3:45 PM, J. Echterwrote: > Am 06.05.2016 um 22:43 schrieb WebDawg: >> Anything in the logs? >> >> On Fri, May 6, 2016 at 3:42 PM, J. Echter >> wrote: >>> Hi, >>> >>> i did the 2.3_1 update and all seemed fine, but my ntpd service isn't >>> coming back up. >>> >>> I even rebooted the machine and it still doesn't start. >>> >>> There's also nothing in the logs. >>> >>> sockstat -l | grep 123 shows nothing. >>> >>> Where is the ntpd binary located? I found nothing. >>> >>> Where should i look at next? >>> >>> Thanks >>> >>> Juergen >>> ___ >>> 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 >> > > No, theres nothing, only gui says ntpd is restarted, nothing else. > > > ___ > 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_1 ntpd isn't restarting
Am 06.05.2016 um 22:43 schrieb WebDawg: > Anything in the logs? > > On Fri, May 6, 2016 at 3:42 PM, J. Echter >wrote: >> Hi, >> >> i did the 2.3_1 update and all seemed fine, but my ntpd service isn't >> coming back up. >> >> I even rebooted the machine and it still doesn't start. >> >> There's also nothing in the logs. >> >> sockstat -l | grep 123 shows nothing. >> >> Where is the ntpd binary located? I found nothing. >> >> Where should i look at next? >> >> Thanks >> >> Juergen >> ___ >> 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 > No, theres nothing, only gui says ntpd is restarted, nothing else. ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] pfSense 2.3_1 ntpd isn't restarting
Anything in the logs? On Fri, May 6, 2016 at 3:42 PM, J. Echterwrote: > Hi, > > i did the 2.3_1 update and all seemed fine, but my ntpd service isn't > coming back up. > > I even rebooted the machine and it still doesn't start. > > There's also nothing in the logs. > > sockstat -l | grep 123 shows nothing. > > Where is the ntpd binary located? I found nothing. > > Where should i look at next? > > Thanks > > Juergen > ___ > 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
[pfSense] pfSense 2.3_1 ntpd isn't restarting
Hi, i did the 2.3_1 update and all seemed fine, but my ntpd service isn't coming back up. I even rebooted the machine and it still doesn't start. There's also nothing in the logs. sockstat -l | grep 123 shows nothing. Where is the ntpd binary located? I found nothing. Where should i look at next? Thanks Juergen ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] 2.3_1 ?
On 2016-05-07 03:49, Jeppe Øland wrote: The only thing not done for me as far as I can tell is to change the version number to 2.3_1 ... but maybe that will change if I reboot the firewall. Also as per the release notes: Note for this update, your version number will remain the same afterwards, still showing as 2.3-RELEASE. ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] 2.3_1 ?
The release notes actually says "The NTP service needs to be manually restarted under Status>Services afterwards". To me that implies that the old one keeps running, and you have to restart it for the new version to take effect. What in fact happens is that the old one is stopped, and no NTP service will be running until you start the new one. Still doesn't address the bug I was experiencing - all package install/uninstalls fail, but actually do everything(?) they should. The only thing not done for me as far as I can tell is to change the version number to 2.3_1 ... but maybe that will change if I reboot the firewall. On Fri, May 6, 2016 at 8:04 AM, Oliver Hansenwrote: > On May 6, 2016 6:01 AM, "Vick Khera" wrote: > > > > On Thu, May 5, 2016 at 3:05 PM, Jim Thompson wrote: > > > > > it’s documented that you need to (re)start NTP manually. > > > > > > > Where would one learn this? The update page doesn't say anything about > > "after applying this update, do XYZ". That would be the ideal place, IMO. > > I don't recall if there's a link from the update page but the release notes > have it which are in the usual place. https://blog.pfsense.org/?cat=53 > ___ > 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] 2.3_1 ?
Common senses says check all services and settings after an upgrade of anything. Why would you depend on the provider to give you that information when its best policy to go it anyway. -- Jason Hellenthal JJH48-ARIN On May 6, 2016, at 08:01, Vick Kherawrote: On Thu, May 5, 2016 at 3:05 PM, Jim Thompson wrote: > it’s documented that you need to (re)start NTP manually. Where would one learn this? The update page doesn't say anything about "after applying this update, do XYZ". That would be the ideal place, IMO. ___ 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] 2.3_1 ?
On Thu, May 5, 2016 at 3:05 PM, Jim Thompsonwrote: > it’s documented that you need to (re)start NTP manually. > Where would one learn this? The update page doesn't say anything about "after applying this update, do XYZ". That would be the ideal place, IMO. ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] 2.3_1 ?
It will restart on its own Sent from my Sprint Samsung Galaxy S7. Original message From: Bob Gustafson <bob...@rcn.com> Date: 5/5/16 4:36 PM (GMT-06:00) To: Larry Rosenman <l...@lerctr.org> Cc: pfSense Support and Discussion Mailing List <list@lists.pfsense.org> Subject: Re: [pfSense] 2.3_1 ? On 05/05/2016 03:13 PM, Larry Rosenman wrote: > On 2016-05-05 15:11, Bob Gustafson wrote: >> On 05/05/2016 02:35 PM, Larry Rosenman wrote: >> >>> On 2016-05-05 14:23, Bob Gustafson wrote: >>>> On 05/05/2016 02:05 PM, Jim Thompson wrote: >>>>>> On May 5, 2016, at 6:26 AM, Paul Mather <p...@gromit.dlib.vt.edu> >>>>>> wrote: >>>>>> >>>>>> On May 5, 2016, at 9:13 AM, Vick Khera <vi...@khera.org> wrote: >>>>>> >>>>>>> On Tue, May 3, 2016 at 11:24 AM, Jeppe Øland <jol...@gmail.com> >>>>>>> wrote: >>>>>>> >>>>>>>> Does this update actually work? >>>>>>>> >>>>>>>> After hitting install and crunching for a while, it showed >>>>>>>> "firmware >>>>>>>> installation failed!" at the top. >>>>>>>> >>>>>>> I just did the upgrade and it succeeded. However, ntpd was not >>>>>>> restarted on >>>>>>> either of the two systems upgraded. I had to manually restart ntpd. >>>>>> >>>>>> Same here. In fact, in my case, ntpd ended up in the stopped >>>>>> state, and I had to start it manually. >>>>> it’s documented that you need to (re)start NTP manually. >>>>> >>>> I haven't yet upgraded to 2.3+ >>>> >>>> My question is whether ntpd is dead on every reboot of pfSense, or >>>> just the one after upgrading? >>> 2.3 to 2.3_1 is NO reboot. >>> >> What does "2.3 to 2.3_1 is NO reboot" mean? >> >> Does it mean that even through power failures, the little pfSense >> soldiers on - pinging ntp even without power? > No, the upgrade from 2.3 to 2.3_1 does *NOT* force a reboot. > > You just need to restart the ntpd service. I'm sorry to be so dense on this subject... My question assumes that the box *has been upgraded* to 2.3_1 - perhaps yesterday. And nptd has been started just after the upgrade. Along comes a power failure. Then the power is restored to the box. When the pfSense within the box is running, is the ntpd running, or does it (again) need to be restarted manually? ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] 2.3_1 ?
On 05/05/2016 03:13 PM, Larry Rosenman wrote: On 2016-05-05 15:11, Bob Gustafson wrote: On 05/05/2016 02:35 PM, Larry Rosenman wrote: On 2016-05-05 14:23, Bob Gustafson wrote: On 05/05/2016 02:05 PM, Jim Thompson wrote: On May 5, 2016, at 6:26 AM, Paul Matherwrote: On May 5, 2016, at 9:13 AM, Vick Khera wrote: On Tue, May 3, 2016 at 11:24 AM, Jeppe Øland wrote: Does this update actually work? After hitting install and crunching for a while, it showed "firmware installation failed!" at the top. I just did the upgrade and it succeeded. However, ntpd was not restarted on either of the two systems upgraded. I had to manually restart ntpd. Same here. In fact, in my case, ntpd ended up in the stopped state, and I had to start it manually. it’s documented that you need to (re)start NTP manually. I haven't yet upgraded to 2.3+ My question is whether ntpd is dead on every reboot of pfSense, or just the one after upgrading? 2.3 to 2.3_1 is NO reboot. What does "2.3 to 2.3_1 is NO reboot" mean? Does it mean that even through power failures, the little pfSense soldiers on - pinging ntp even without power? No, the upgrade from 2.3 to 2.3_1 does *NOT* force a reboot. You just need to restart the ntpd service. I'm sorry to be so dense on this subject... My question assumes that the box *has been upgraded* to 2.3_1 - perhaps yesterday. And nptd has been started just after the upgrade. Along comes a power failure. Then the power is restored to the box. When the pfSense within the box is running, is the ntpd running, or does it (again) need to be restarted manually? ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] 2.3_1 ?
On 2016-05-05 15:11, Bob Gustafson wrote: On 05/05/2016 02:35 PM, Larry Rosenman wrote: On 2016-05-05 14:23, Bob Gustafson wrote: On 05/05/2016 02:05 PM, Jim Thompson wrote: On May 5, 2016, at 6:26 AM, Paul Matherwrote: On May 5, 2016, at 9:13 AM, Vick Khera wrote: On Tue, May 3, 2016 at 11:24 AM, Jeppe Øland wrote: Does this update actually work? After hitting install and crunching for a while, it showed "firmware installation failed!" at the top. I just did the upgrade and it succeeded. However, ntpd was not restarted on either of the two systems upgraded. I had to manually restart ntpd. Same here. In fact, in my case, ntpd ended up in the stopped state, and I had to start it manually. it’s documented that you need to (re)start NTP manually. I haven't yet upgraded to 2.3+ My question is whether ntpd is dead on every reboot of pfSense, or just the one after upgrading? 2.3 to 2.3_1 is NO reboot. What does "2.3 to 2.3_1 is NO reboot" mean? Does it mean that even through power failures, the little pfSense soldiers on - pinging ntp even without power? No, the upgrade from 2.3 to 2.3_1 does *NOT* force a reboot. You just need to restart the ntpd service. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] 2.3_1 ?
On Thu, May 5, 2016 at 3:11 PM, Bob Gustafsonwrote: > On 05/05/2016 02:35 PM, Larry Rosenman wrote: > >> On 2016-05-05 14:23, Bob Gustafson wrote: >>> >>> On 05/05/2016 02:05 PM, Jim Thompson wrote: > > On May 5, 2016, at 6:26 AM, Paul Mather > wrote: > > On May 5, 2016, at 9:13 AM, Vick Khera wrote: > >> On Tue, May 3, 2016 at 11:24 AM, Jeppe Øland wrote: >> >>> Does this update actually work? >>> >>> After hitting install and crunching for a while, it showed "firmware >>> installation failed!" at the top. >>> >> I just did the upgrade and it succeeded. However, ntpd was not >> restarted on >> either of the two systems upgraded. I had to manually restart ntpd. > > > Same here. In fact, in my case, ntpd ended up in the stopped state, > and I had to start it manually. it’s documented that you need to (re)start NTP manually. >>> I haven't yet upgraded to 2.3+ >>> >>> My question is whether ntpd is dead on every reboot of pfSense, or >>> just the one after upgrading? >> >> 2.3 to 2.3_1 is NO reboot. >> > What does "2.3 to 2.3_1 is NO reboot" mean? > That doing the upgrade from 2.3 to 2.3_1 doesn't reboot the system. ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] 2.3_1 ?
On 05/05/2016 02:35 PM, Larry Rosenman wrote: On 2016-05-05 14:23, Bob Gustafson wrote: On 05/05/2016 02:05 PM, Jim Thompson wrote: On May 5, 2016, at 6:26 AM, Paul Matherwrote: On May 5, 2016, at 9:13 AM, Vick Khera wrote: On Tue, May 3, 2016 at 11:24 AM, Jeppe Øland wrote: Does this update actually work? After hitting install and crunching for a while, it showed "firmware installation failed!" at the top. I just did the upgrade and it succeeded. However, ntpd was not restarted on either of the two systems upgraded. I had to manually restart ntpd. Same here. In fact, in my case, ntpd ended up in the stopped state, and I had to start it manually. it’s documented that you need to (re)start NTP manually. I haven't yet upgraded to 2.3+ My question is whether ntpd is dead on every reboot of pfSense, or just the one after upgrading? 2.3 to 2.3_1 is NO reboot. What does "2.3 to 2.3_1 is NO reboot" mean? Does it mean that even through power failures, the little pfSense soldiers on - pinging ntp even without power? ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] 2.3_1 ?
On 2016-05-05 14:23, Bob Gustafson wrote: On 05/05/2016 02:05 PM, Jim Thompson wrote: On May 5, 2016, at 6:26 AM, Paul Matherwrote: On May 5, 2016, at 9:13 AM, Vick Khera wrote: On Tue, May 3, 2016 at 11:24 AM, Jeppe Øland wrote: Does this update actually work? After hitting install and crunching for a while, it showed "firmware installation failed!" at the top. I just did the upgrade and it succeeded. However, ntpd was not restarted on either of the two systems upgraded. I had to manually restart ntpd. Same here. In fact, in my case, ntpd ended up in the stopped state, and I had to start it manually. it’s documented that you need to (re)start NTP manually. I haven't yet upgraded to 2.3+ My question is whether ntpd is dead on every reboot of pfSense, or just the one after upgrading? 2.3 to 2.3_1 is NO reboot. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] 2.3_1 ?
On 05/05/2016 02:05 PM, Jim Thompson wrote: On May 5, 2016, at 6:26 AM, Paul Matherwrote: On May 5, 2016, at 9:13 AM, Vick Khera wrote: On Tue, May 3, 2016 at 11:24 AM, Jeppe Øland wrote: Does this update actually work? After hitting install and crunching for a while, it showed "firmware installation failed!" at the top. I just did the upgrade and it succeeded. However, ntpd was not restarted on either of the two systems upgraded. I had to manually restart ntpd. Same here. In fact, in my case, ntpd ended up in the stopped state, and I had to start it manually. it’s documented that you need to (re)start NTP manually. I haven't yet upgraded to 2.3+ My question is whether ntpd is dead on every reboot of pfSense, or just the one after upgrading? ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] 2.3_1 ?
> On May 5, 2016, at 6:26 AM, Paul Matherwrote: > > On May 5, 2016, at 9:13 AM, Vick Khera wrote: > >> On Tue, May 3, 2016 at 11:24 AM, Jeppe Øland wrote: >> >>> Does this update actually work? >>> >>> After hitting install and crunching for a while, it showed "firmware >>> installation failed!" at the top. >>> >> >> I just did the upgrade and it succeeded. However, ntpd was not restarted on >> either of the two systems upgraded. I had to manually restart ntpd. > > > Same here. In fact, in my case, ntpd ended up in the stopped state, and I > had to start it manually. it’s documented that you need to (re)start NTP manually. ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] 2.3_1 ?
On Thu, May 5, 2016 at 9:47 AM, Jeppe Ølandwrote: > This install is running a 4G NANO image ... maybe there's a problem with > that? > I just did the update on a nano image system (netgate, not vanilla pfsense) and had success other than having to manually restart ntpd. ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] 2.3_1 ?
On May 5, 2016, at 9:47 AM, Jeppe Ølandwrote: > So the update failed, and pfSense still says 2.3 - but NTP was indeed > updated (but not restarted). > > I then tried installing the RRD_Summary package. > That one also said it failed, but still completed enough that the menu > appeared and worked. > > I forget if it said "failed" when I uninstalled it again ... probably did. > > This install is running a 4G NANO image ... maybe there's a problem with > that? FWIW, the system I updated is a 4G NANO install (amd64). The update status shows it is at version 2.3_1 after the update. The only issue I encountered is ntpd being stopped and having to start it manually. Cheers, Paul. > > Regards, > -Jeppe > > On Thu, May 5, 2016 at 6:26 AM, Paul Mather wrote: > >> On May 5, 2016, at 9:13 AM, Vick Khera wrote: >> >>> On Tue, May 3, 2016 at 11:24 AM, Jeppe Øland wrote: >>> Does this update actually work? After hitting install and crunching for a while, it showed "firmware installation failed!" at the top. >>> >>> I just did the upgrade and it succeeded. However, ntpd was not restarted >> on >>> either of the two systems upgraded. I had to manually restart ntpd. >> >> >> Same here. In fact, in my case, ntpd ended up in the stopped state, and I >> had to start it manually. >> >> Cheers, >> >> Paul. >> >> ___ >> 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 ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] 2.3_1 ?
So the update failed, and pfSense still says 2.3 - but NTP was indeed updated (but not restarted). I then tried installing the RRD_Summary package. That one also said it failed, but still completed enough that the menu appeared and worked. I forget if it said "failed" when I uninstalled it again ... probably did. This install is running a 4G NANO image ... maybe there's a problem with that? Regards, -Jeppe On Thu, May 5, 2016 at 6:26 AM, Paul Matherwrote: > On May 5, 2016, at 9:13 AM, Vick Khera wrote: > > > On Tue, May 3, 2016 at 11:24 AM, Jeppe Øland wrote: > > > >> Does this update actually work? > >> > >> After hitting install and crunching for a while, it showed "firmware > >> installation failed!" at the top. > >> > > > > I just did the upgrade and it succeeded. However, ntpd was not restarted > on > > either of the two systems upgraded. I had to manually restart ntpd. > > > Same here. In fact, in my case, ntpd ended up in the stopped state, and I > had to start it manually. > > Cheers, > > Paul. > > ___ > 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] 2.3_1 ?
On May 5, 2016, at 9:13 AM, Vick Kherawrote: > On Tue, May 3, 2016 at 11:24 AM, Jeppe Øland wrote: > >> Does this update actually work? >> >> After hitting install and crunching for a while, it showed "firmware >> installation failed!" at the top. >> > > I just did the upgrade and it succeeded. However, ntpd was not restarted on > either of the two systems upgraded. I had to manually restart ntpd. Same here. In fact, in my case, ntpd ended up in the stopped state, and I had to start it manually. Cheers, Paul. ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] 2.3_1 ?
On Tue, May 3, 2016 at 11:24 AM, Jeppe Ølandwrote: > Does this update actually work? > > After hitting install and crunching for a while, it showed "firmware > installation failed!" at the top. > I just did the upgrade and it succeeded. However, ntpd was not restarted on either of the two systems upgraded. I had to manually restart ntpd. My guess on the "pfSense" package is all that does is bump the displayed release number. ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] 2.3_1 ?
Does this update actually work? After hitting install and crunching for a while, it showed "firmware installation failed!" at the top. Log window showed: firmware installation failed! >>> Updating repositories metadata... Updating pfSense-core repository catalogue... pfSense-core repository is up-to-date. Updating pfSense repository catalogue... pfSense repository is up-to-date. All repositories are up-to-date. >>> Unlocking package pfSense-kernel-pfSense... done. >>> Downloading upgrade packages... Updating pfSense-core repository catalogue... pfSense-core repository is up-to-date. Updating pfSense repository catalogue... pfSense repository is up-to-date. All repositories are up-to-date. Checking for upgrades (5 candidates): . done Processing candidates (5 candidates): ... done The following 2 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: pfSense: 2.3 -> 2.3_1 [pfSense] ntp: 4.2.8p6 -> 4.2.8p7 [pfSense] The process will require 2 KiB more space. 493 KiB to be downloaded. Fetching pfSense-2.3_1.txz: . done Fetching ntp-4.2.8p7.txz: .. done Checking integrity... done (0 conflicting) >>> Upgrading necessary packages... Updating pfSense-core repository catalogue... pfSense-core repository is up-to-date. Updating pfSense repository catalogue... pfSense repository is up-to-date. All repositories are up-to-date. Checking for upgrades (5 candidates): . done Processing candidates (5 candidates): ... done Checking integrity... done (0 conflicting) The following 2 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: pfSense: 2.3 -> 2.3_1 [pfSense] ntp: 4.2.8p6 -> 4.2.8p7 [pfSense] The process will require 2 KiB more space. [1/2] Upgrading ntp from 4.2.8p6 to 4.2.8p7... [1/2] Extracting ntp-4.2.8p7: .. done [2/2] Upgrading pfSense from 2.3 to 2.3_1... [2/2] Extracting pfSense-2.3_1: ... done >>> Removing unnecessary packages... done. >>> Cleanup pkg cache... done. >>> Locking package pfSense-kernel-pfSense... done. On Mon, May 2, 2016 at 8:24 AM, Olivier Mascia <o...@integral.be> wrote: > > > Le 2 mai 2016 à 16:19, Jason Hellenthal <jhellent...@dataix.net> a > écrit : > > > > Signé partie PGP > > _1 would not be a development release. That would be a patch or an > addendum which I would assume handles the ntp security flaw patched in > recent FreeBSD security release. > > > > https://www.freebsd.org/security/advisories/FreeBSD-SA-16:16.ntp.asc > > > > On May 2, 2016, at 08:54, Olivier Mascia <o...@integral.be> wrote: > > > > The update check on 2.3-REL GUI offers me 2.3_1, yet I don't see mention > of it on pfsense.org. > > Could it be that my system polls for dev branch releases and not only > released builds? > > Or that the auto-update only revealed the beast before the blog on > pfsense.org? > > Indeed. > > Installed packages to be UPGRADED: > pfSense: 2.3 -> 2.3_1 [pfSense] > ntp: 4.2.8p6 -> 4.2.8p7 [pfSense] > > -- > Meilleures salutations, Met vriendelijke groeten, Best Regards, > Olivier Mascia, integral.be/om > > > ___ > 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] 2.3_1 ?
> Le 2 mai 2016 à 16:19, Jason Hellenthala écrit : > > Signé partie PGP > _1 would not be a development release. That would be a patch or an addendum > which I would assume handles the ntp security flaw patched in recent FreeBSD > security release. > > https://www.freebsd.org/security/advisories/FreeBSD-SA-16:16.ntp.asc > > On May 2, 2016, at 08:54, Olivier Mascia wrote: > > The update check on 2.3-REL GUI offers me 2.3_1, yet I don't see mention of > it on pfsense.org. > Could it be that my system polls for dev branch releases and not only > released builds? > Or that the auto-update only revealed the beast before the blog on > pfsense.org? Indeed. Installed packages to be UPGRADED: pfSense: 2.3 -> 2.3_1 [pfSense] ntp: 4.2.8p6 -> 4.2.8p7 [pfSense] -- Meilleures salutations, Met vriendelijke groeten, Best Regards, Olivier Mascia, integral.be/om ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] 2.3_1 ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 _1 would not be a development release. That would be a patch or an addendum which I would assume handles the ntp security flaw patched in recent FreeBSD security release. https://www.freebsd.org/security/advisories/FreeBSD-SA-16:16.ntp.asc On May 2, 2016, at 08:54, Olivier Masciawrote: The update check on 2.3-REL GUI offers me 2.3_1, yet I don't see mention of it on pfsense.org. Could it be that my system polls for dev branch releases and not only released builds? Or that the auto-update only revealed the beast before the blog on pfsense.org? - -- Meilleures salutations, Met vriendelijke groeten, Best Regards, Olivier Mascia, integral.be/om ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold - -- Jason Hellenthal JJH48-ARIN -BEGIN PGP SIGNATURE- iQEcBAEBCAAGBQJXJ2HxAAoJEDLu+wRc4KcIH7YH/0CI/esLfieYjH/n8JPAbOFg yeGf2hObYF8e3ygtWNTgYcdWZim9QjNW06YL+l3bMih7I9Fb0z/EHDud0IZG+c11 XLJy1CiBOWNbSfgbqt2ToYdneFaMZEqZH4sIMviFyCH5rJmV+ovjDBDlZh6tYiUO CrGnEW/4WORQpZ2rUwPHvYO69z133gE2X9vU3pPxA6rEXGfh6LtECFAntMea7lBh dYtathaKzLSbWDWywSqOJ5iJ1UdMKNt5NY+zagHLj+7KqfC/8AF40UYEusVooL5M 6ughJbFqR+4sh/R/nahHz1568L16j9ZjVwCv38SE3+k+qiaG7W+obsTUqUmoivw= =NsJm -END PGP SIGNATURE- ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
[pfSense] 2.3_1 ?
The update check on 2.3-REL GUI offers me 2.3_1, yet I don't see mention of it on pfsense.org. Could it be that my system polls for dev branch releases and not only released builds? Or that the auto-update only revealed the beast before the blog on pfsense.org? -- Meilleures salutations, Met vriendelijke groeten, Best Regards, Olivier Mascia, integral.be/om ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold