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. >

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. 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 >>

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

Re: [pfSense] pfSense 2.3_1 ntpd isn't restarting

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

[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

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

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

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 Khera wrote: On Thu, May

Re: [pfSense] 2.3_1 ?

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.

Re: [pfSense] 2.3_1 ?

rg> 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 T

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

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 Mather wrote: On May 5, 2016, at 9:13 AM, Vick Khera

Re: [pfSense] 2.3_1 ?

On Thu, May 5, 2016 at 3:11 PM, 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

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 Mather wrote: On May 5, 2016, at 9:13 AM, Vick Khera wrote: On Tue, May 3, 2016

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 Mather wrote: On May 5, 2016, at 9:13 AM, Vick Khera wrote: On Tue, May 3, 2016 at 11:24 AM, Jeppe Øland

Re: [pfSense] 2.3_1 ?

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?

Re: [pfSense] 2.3_1 ?

> 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

Re: [pfSense] 2.3_1 ?

On Thu, May 5, 2016 at 9:47 AM, Jeppe Øland wrote: > 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.

Re: [pfSense] 2.3_1 ?

On May 5, 2016, at 9:47 AM, Jeppe Øland wrote: > 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 >

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

Re: [pfSense] 2.3_1 ?

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. >> > >

Re: [pfSense] 2.3_1 ?

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

Re: [pfSense] 2.3_1 ?

): 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) &

Re: [pfSense] 2.3_1 ?

> Le 2 mai 2016 à 16:19, Jason Hellenthal 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. > >

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

[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