Re: Segmentation fault running ntpd

On Wed, 2015-11-04 at 17:49 -0800, Doug Hardie wrote: > > On 4 November 2015, at 08:15, Mark Martinec < > > mark.martinec+free...@ijs.si> wrote: > > > > Upgrading 10.2-RELEASE-p6 to 10.2-RELEASE-p7 now solved ntpd > > crashes > > (apparently fixed by: FreeBSD Errata Notice FreeBSD-EN-15:20.vm). >

Re: Segmentation fault running ntpd

> On 4 November 2015, at 08:15, Mark Martinec > wrote: > > Upgrading 10.2-RELEASE-p6 to 10.2-RELEASE-p7 now solved ntpd crashes > (apparently fixed by: FreeBSD Errata Notice FreeBSD-EN-15:20.vm). > > Thanks!!! > > Mark > ntpdc hangs when you do a peers

Re: Segmentation fault running ntpd

Upgrading 10.2-RELEASE-p6 to 10.2-RELEASE-p7 now solved ntpd crashes (apparently fixed by: FreeBSD Errata Notice FreeBSD-EN-15:20.vm). Thanks!!! Mark On 2015-11-01 10:31, Andre Albsmeier wrote: On Fri, 30-Oct-2015 at 19:47:59 +0100, Mark Martinec wrote: Not sure if it's the same issue,

Re: Segmentation fault running ntpd

On Fri, 30-Oct-2015 at 19:47:59 +0100, Mark Martinec wrote: > Not sure if it's the same issue, but it sure looks like it is. > > I have upgraded a couple of hosts (amd64) from 10.2-RELEASE-p5 > to 10.2-RELEASE-p6, i.e. the freebsd-upgrade essentially just > replaced the /usr/sbin/ntpd with a new

Re: Segmentation fault running ntpd

> On Oct 30, 2015, at 01:42, Dag-Erling Smørgrav wrote: > > David Wolfskill writes: >> ... >> bound to 172.17.1.245 -- renewal in 43200 seconds. >> pid 544 (ntpd), uid 0: exited on signal 11 (core dumped) >> Starting Network: lo0 em0 iwn0 lagg0. >> ... > >

Re: Segmentation fault running ntpd

NGie Cooper writes: > Dag-Erling Smørgrav writes: > > David Wolfskill writes: > > > pid 544 (ntpd), uid 0: exited on signal 11 (core dumped) > > Did you find a solution? [...] > https://svnweb.freebsd.org/changeset/base/287591 ? Are

Re: Segmentation fault running ntpd

David Wolfskill writes: > ... > bound to 172.17.1.245 -- renewal in 43200 seconds. > pid 544 (ntpd), uid 0: exited on signal 11 (core dumped) > Starting Network: lo0 em0 iwn0 lagg0. > ... Did you find a solution? I'm wondering if the ntpd problems people are reporting on

Re: Segmentation fault running ntpd

Franco Fichtner writes: > Well, it’s on stable/10 since September 16 and somebody reported that > this particular branch would not trigger the crash along with HEAD, > but any 10.x would. Can’t find the reference right now though. OK, we should do an EN with that patch

Re: Segmentation fault running ntpd

> On Oct 30, 2015, at 02:32, Franco Fichtner wrote: > > Well, it’s on stable/10 since September 16 and somebody reported that > this particular branch would not trigger the crash along with HEAD, > but any 10.x would. Can’t find the reference right now though. You’re

Re: Segmentation fault running ntpd

Well, it’s on stable/10 since September 16 and somebody reported that this particular branch would not trigger the crash along with HEAD, but any 10.x would. Can’t find the reference right now though. > On 30 Oct 2015, at 10:24 am, NGie Cooper wrote: > > >> On Oct 30,

Re: Segmentation fault running ntpd

On 10/30/15 09:32, Franco Fichtner wrote: > Well, it’s on stable/10 since September 16 and somebody reported that > this particular branch would not trigger the crash along with HEAD, > but any 10.x would. Can’t find the reference right now though. That was me, amongst others. There are threads

Re: Segmentation fault running ntpd

> On Oct 30, 2015, at 02:05, Dag-Erling Smørgrav wrote: > > NGie Cooper writes: >> Dag-Erling Smørgrav writes: >>> David Wolfskill writes: pid 544 (ntpd), uid 0: exited on signal 11 (core dumped) >>> Did you find a

Re: Segmentation fault running ntpd

Hi all, I did a quick test build and this seems to solve the ntpd crash issue on top of releng/10.1. Cheers, Franco > On 30 Oct 2015, at 10:09 am, NGie Cooper wrote: > > >> On Oct 30, 2015, at 02:05, Dag-Erling Smørgrav wrote: >> >> NGie Cooper

Re: Segmentation fault running ntpd

> On Oct 30, 2015, at 02:18, Franco Fichtner wrote: > > Hi all, > > I did a quick test build and this seems to solve the ntpd crash issue > on top of releng/10.1. Makes sense … looking through my email r287591 was never MFCed back to stable/9 or stable/10 :/ . HTH,

Re: Segmentation fault running ntpd

Not sure if it's the same issue, but it sure looks like it is. I have upgraded a couple of hosts (amd64) from 10.2-RELEASE-p5 to 10.2-RELEASE-p6, i.e. the freebsd-upgrade essentially just replaced the /usr/sbin/ntpd with a new one; then I restarted the ntpd. On all host but one this was

Re: Segmentation fault running ntpd

On Fri, Oct 30, 2015 at 09:42:07AM +0100, Dag-Erling Smørgrav wrote: > David Wolfskill writes: > > ... > > bound to 172.17.1.245 -- renewal in 43200 seconds. > > pid 544 (ntpd), uid 0: exited on signal 11 (core dumped) > > Starting Network: lo0 em0 iwn0 lagg0. > > ... > >

Re: Segmentation fault running ntpd

Adrian the crash we are seeing here is very easily reproducible. Grab our private ports repo and revert my most recent revert and build. It appears to show up multiple times per day somehow in our configuration. On 7/28/15 7:25 PM, Adrian Chadd wrote: On 28 July 2015 at 16:09, David

Re: Segmentation fault running ntpd

On Tue, Jul 28, 2015 at 04:05:33PM -0700, Adrian Chadd wrote: Is this still happening for you? g1-245(10.2-P)[4] ls -lT /S4/ntpd.core -rw-r--r-- 1 root wheel 13783040 Jul 28 04:56:28 2015 /S4/ntpd.core Apparently so, yes. (/S4 is where I have the head root file system mounted when

Re: Segmentation fault running ntpd

Is this still happening for you? -a On 24 July 2015 at 06:03, David Wolfskill da...@catwhisker.org wrote: On Sun, Jul 19, 2015 at 11:36:00AM -0700, David Wolfskill wrote: On Sun, Jul 19, 2015 at 10:24:11AM -0600, Ian Lepore wrote: ... Was there anything (at all) in /var/log/messages

Re: Segmentation fault running ntpd

On Tue, Jul 28, 2015 at 04:25:45PM -0700, Adrian Chadd wrote: ... Hm, is there any way you can get symbols for it? Well, I could CFLAGS+= -g in /etc/make.conf to a clean build, then try to re-create it ( point gdb at the objects in /usr/obj/obj/*) -- would that do? I don't think I can easily

Re: Segmentation fault running ntpd

WITH_DEBUG_FILES=1 (IIRC) On 7/28/15 6:35 PM, Adrian Chadd wrote: There's some way in stable/10 and -head to get it to install debug symbols for things. Maybe it's only libraries, but you'll at least want that in there so you can get stack traces through libc. -adrian

Re: Segmentation fault running ntpd

There's some way in stable/10 and -head to get it to install debug symbols for things. Maybe it's only libraries, but you'll at least want that in there so you can get stack traces through libc. -adrian ___ freebsd-current@freebsd.org mailing list

Re: Segmentation fault running ntpd

On 28 July 2015 at 16:09, David Wolfskill da...@catwhisker.org wrote: On Tue, Jul 28, 2015 at 04:05:33PM -0700, Adrian Chadd wrote: Is this still happening for you? g1-245(10.2-P)[4] ls -lT /S4/ntpd.core -rw-r--r-- 1 root wheel 13783040 Jul 28 04:56:28 2015 /S4/ntpd.core Apparently

Re: Segmentation fault running ntpd

On Sun, Jul 19, 2015 at 11:36:00AM -0700, David Wolfskill wrote: On Sun, Jul 19, 2015 at 10:24:11AM -0600, Ian Lepore wrote: ... Was there anything (at all) in /var/log/messages about ntpd? Even the routine messages (such as what interfaces it binds to) might give a bit of a clue about

Re: Segmentation fault running ntpd

On Sat, 2015-07-18 at 05:09 -0700, David Wolfskill wrote: Lousy timing (no pun intended -- it's early in the day for me), given the recent MFC, but as I was booting my laptop to yesterday's head: FreeBSD g1-245.catwhisker.org 11.0-CURRENT FreeBSD 11.0-CURRENT #127 r285652M/285652:1100077:

Re: Segmentation fault running ntpd

On Sun, Jul 19, 2015 at 10:24:11AM -0600, Ian Lepore wrote: ... Was there anything (at all) in /var/log/messages about ntpd? Even the routine messages (such as what interfaces it binds to) might give a bit of a clue about how far it got in its init before it died. Sorry; there might

Segmentation fault running ntpd

Lousy timing (no pun intended -- it's early in the day for me), given the recent MFC, but as I was booting my laptop to yesterday's head: FreeBSD g1-245.catwhisker.org 11.0-CURRENT FreeBSD 11.0-CURRENT #127 r285652M/285652:1100077: Fri Jul 17 04:30:16 PDT 2015