syslogd 100% cpu usage on recent FreeBSD version
Probably after https://svnweb.freebsd.org/base?view=revision=310494, syslogd eat 100% cpu with follow messages: Dec 24 14:19:15 samson syslogd: select: Bad file descriptor Dec 24 14:19:45 samson last message repeated 464140 times Dec 24 14:20:38 samson last message repeated 835899 times truss -f for syslogd -ss: http://pastebin.com/6XxmX89q ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
syslogd: select: Bad File descriptor
latest changes is causing cpu load and ‘last message repeated times, I guess the eggnog is affecting too early cheers, danny ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: syslogd: select: Bad File descriptor
> On Dec 24, 2016, at 04:16, Daniel Branisswrote: > > latest changes is causing cpu load and ‘last message repeated times, > I guess the eggnog is affecting too early Fixed in r310504. Thanks, -Ngie signature.asc Description: Message signed with OpenPGP using GPGMail
Re: syslogd 100% cpu usage on recent FreeBSD version
On 12/24/16 13:14, Subbsd wrote: Probably after https://svnweb.freebsd.org/base?view=revision=310494, syslogd eat 100% cpu with follow messages: Dec 24 14:19:15 samson syslogd: select: Bad file descriptor Dec 24 14:19:45 samson last message repeated 464140 times Dec 24 14:20:38 samson last message repeated 835899 times I'm sseeing this too. just upgraded one machine to r310496. -- Guido Falsi___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: syslogd 100% cpu usage on recent FreeBSD version
> On Dec 24, 2016, at 04:14, Subbsdwrote: > > Probably after https://svnweb.freebsd.org/base?view=revision=310494, > syslogd eat 100% cpu with follow messages: > > Dec 24 14:19:15 samson syslogd: select: Bad file descriptor > Dec 24 14:19:45 samson last message repeated 464140 times > Dec 24 14:20:38 samson last message repeated 835899 times Fixed in r310504. Thanks, -Ngie signature.asc Description: Message signed with OpenPGP using GPGMail
syslogd: select: Bad File descriptor
> latest changes is causing cpu load and ‘last message repeated times, > I guess the eggnog is affecting too early > > cheers, > danny Having the issue as well. -- Best regards, Domagoj Stolfa. signature.asc Description: PGP signature
Re: syslogd: select: Bad File descriptor
> On 24 Dec 2016, at 2:51 PM, Ngie Cooper (yaneurabeya)> wrote: > > >> On Dec 24, 2016, at 04:16, Daniel Braniss wrote: >> >> latest changes is causing cpu load and ‘last message repeated >> times, I guess the eggnog is affecting too early > > Fixed in r310504. > Thanks, > -Ngie thanks! Season Greetings, danny ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: syslogd 100% cpu usage on recent FreeBSD version
On 12/24/16 13:50, Ngie Cooper (yaneurabeya) wrote: On Dec 24, 2016, at 04:14, Subbsdwrote: Probably after https://svnweb.freebsd.org/base?view=revision=310494, syslogd eat 100% cpu with follow messages: Dec 24 14:19:15 samson syslogd: select: Bad file descriptor Dec 24 14:19:45 samson last message repeated 464140 times Dec 24 14:20:38 samson last message repeated 835899 times Fixed in r310504. Thanks to you! -- Guido Falsi ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: A quick question
On Wed, 21 Dec 2016, at 06:39, blubee blubeeme wrote: > Can I bump this issue one more time? > > On Sun, Dec 18, 2016, 18:38 Dave Cottlehuberwrote: > > > On Sun, 18 Dec 2016, at 10:07, blubee blubeeme wrote: > > > Hi > > > > > > I am on a Macbook pro 11,3 and I wanted to start trying to help sort out > > > some problems that might be too small for the overall team but might help > > > others in the future. > > > > \o/ there are a few of us about, I'm using a MacBookPro 11,2. > > > > > Anyways I am on 12-CURRENT but when I installed from the USB stick I > > > didn't > > > check the docs and 32 bit binaries. > > > > > > svn checkout svn://svn.freebsd.org/base/head /usr/src > > > svn checkout svn://svn.freebsd.org/ports/head /usr/ports > > > svn checkout svn://svn.freebsd.org/doc/head /usr/doc > > > > > > once I do the above steps, do I have to rebuild the entire world? > > > Currently > > > all I am missing is the 32 bit binaries, could I just rebuild those > > > instead > > > of building the entire system? > > > > > > > > > Best, > > > Owen > > > > Hi Owen > > > > You probably only need to unpack > > http://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/12.0-CURRENT/*.txz ; > > I'm assuming this snapshot is still from the same date as your > > installer. If your USB stick has the txz on it, then you can extract > > them from there as well. Something like > > > > tar -xf docs.txz -C / > > > > is probably all you need. NB not tested, viz xkcd.com/1168 > > > > A+ > > Dave > another question to make sure. > > looking at the url: > http://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/12.0-CURRENT/ > > I see the MANIFEST along with > > base-dbg.txz > base.. > doc.. > kernel-dbg... > etc. > > so when I install FreeBSD based on the installation items that I select, it > just unpacks > one of the above listed file right into the / directory on the hdd? Sorry Christmas got in the way of emails. Yes, you can see here in pc-sysinstall: https://svnweb.freebsd.org/base/release/11.0.0/usr.sbin/pc-sysinstall/backend/functions-extractimage.sh?view=markup#l57 the excellent 3rd party mfsbsd tool does the same thing to install FreeBSD: https://github.com/mmatuska/mfsbsd/blob/master/tools/zfsinstall#L354-L356 A+ Dave ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"