Authentication tried for XXX with correct key but not from a permitted host
This is more for the record than asking a specific question. Today I upgraded a system to FreeBSD 8.1-PRERELEASE. Then I started seeing these messages when I ssh to said box with an ssh-agent enabled connection: Jul 11 03:43:06 ngaio sshd[30290]: Authentication tried for dan with correct key but not from a permitted host (host=laptop.example.org, ip=10.0.0.100). Jul 11 03:43:07 ngaio sshd[30290]: Authentication tried for dan with correct key but not from a permitted host (host=laptop.example.org, ip=10.0.0.100). Jul 11 03:43:07 ngaio sshd[30290]: Accepted publickey for dan from 10.0.0.100 port 53525 ssh2 My questions were: 1 - how do I set a permitted host? 2 - why is the message logged twice? That asked, I know if I move the key to the top of the ~/.ssh/authorized_keys file, the message is no longer logged. Further investigation reveals that if a line of the form: from="10..etc" appears before the key being used to log in, the message will appear. Solution: move the from= line to the bottom of the file. Ugly, but it works. -- Dan Langille - http://langille.org/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 8.1-PRE Throwing Traps Going Multiuser
On 7/5/2010 4:10 PM, Kostik Belousov wrote: > On Mon, Jul 05, 2010 at 03:29:29PM -0500, Tim Daneliuk wrote: >> Is this a known problem (I've submitted a PR just in case it is not)? >> >> I am seeing this consistently when I try to do a build/installworld/kernel >> with daily sources from the master tree: >> >> http://www.mediafire.com/imageview.php?quickkey=qmhizdtnhyo&thumb=4 >> >> The system boots fine single-user. Problem is repeatable with both >> my kernel AND GENERIC. (My config file at end of this msg.) >> >> Attempting to enter multi-user causes the problem. This >> occurs whether or not anything is enabled in /etc/rc.conf. >> >> Falling back to my 6-18-2010 system image makes everything right again. >> >> MOBO is an Intel D946GZIS with a single SATA drive and one additional >> 3Com 3c905 NIC in addition to the onboard Intel NIC. >> >> >> My Kernel Config >> = >> >> include GENERIC >> >> ident MACHINENAME >> >> options IPFIREWALL >> options IPDIVERT >> >> options VESA >> >> # System console options >> >> options SC_DISABLE_REBOOT # disable reboot key sequence >> options SC_HISTORY_SIZE=200 # number of history buffer lines >> options SC_PIXEL_MODE # add support for the raster text >> mode >> >> # The following options will change the default colors of syscons. >> >> options SC_NORM_ATTR="(FG_GREEN|BG_BLACK)" >> options SC_NORM_REV_ATTR="(FG_YELLOW|BG_GREEN)" >> options SC_KERNEL_CONS_ATTR="(FG_RED|BG_BLACK)" >> options SC_KERNEL_CONS_REV_ATTR="(FG_BLACK|BG_RED)" > > Add DDB to your kernel, or specify the dump device. Then obtain a > backtrace for the trap. As of this morning's build (0700 CDT) this problem seems resolved. -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 8.1-RC2 - PCI fatal error or MCE triggered by USB/ehci on Sun X4100M2?
On Fri, Jul 9, 2010 at 6:53 PM, Markus Gebert wrote: [snip] > > Yes, this hardware comes from Sun directly, but getting Sun (/Oracle) > support for this issue is gonna be tough. FreeBSD is unsupported, and in a > short test we couldn't reproduce the problem with a Linux kernel. While I > agree that a hardware issue has always been and still is a possibility to be > considered, the fact that we tested this on two machines remains as well as > the fact that 6.x, 7.x do not show the behavior. Another possibility is of > course, that the X4100 is prone to such issues and somehow 6.x and 7.x have > workarounds we're not aware of or just do something different in way so that > this issue does not get triggered. > > 8.1 is our first release to have the driver for configuring and reporting machine check exceptions enabled by default. Prior to 8.1, you had to explicitly enable the driver at boot time. Alan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Sudden mbuf demand increase and shortage under the load
On Tue, Feb 16, 2010 at 7:23 PM, Maxim Sobolev wrote: > Miroslav Lachman wrote: >> >> Can it be related to this issue somehow? >> >> http://lists.freebsd.org/pipermail/freebsd-current/2009-August/011013.html >> http://lists.freebsd.org/pipermail/freebsd-current/2009-August/010740.html >> >> It was tested on FreeBSD 8 and high UDP traffic on igb interfaces emits >> messages "GET BUF: dmamap load failure - 12" and later results in kernel >> panic. >> We have not received any response to this report. > > Could be the issue, however in our case there is no panic, just that all > userland activity in the system ceases for 2 minutes after it reaches > certain network load level. Sorry for digging into this old thread, but I'm seeing similar symptoms with today's RELENG_8 and bge(4) attached to BCM5721, on an UP system. kern.ipc.nmbclusters is 65536, but what strikes me odd is this: 0/115446003/57722999 requests for mbufs denied (mbufs/clusters/mbuf+clusters) vmstat -i shows a rate of 1100 for the adapter. The machine runs a fairly small PF configuration, but I've already ruled it out, the symptoms appear when PF is disabled as well. I'll happily provide more info. Regards, Vlad -- Good, fast & cheap. Pick any two. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
8.1-RC2: mvs/ZFS Fatal trap 19: non-maskable interrupt trap while in kernel mode
Hi, a few days ago i installed a server with the latest RC. It has an mvs based controller, attached to it are 6 disks in a RAIDZ, the server has 8GB of RAM and is running amd64. The CPU is a single core Xeon with HT turned on. This morning it hanged for the 2nd time, this time i managed to capture the panic massage: Fatal trap 19: non-maskable interrupt trap while in kernel mode Fatal trap 19: non-maskable interrupt trap while in kernel mode cpuid = 1; cpuid = 0; apic id = 01 apic id = 00 instruction pointer = 0x20:0x80e75c65 instruction pointer = 0x20:0x80870f94 stack pointer = 0x28:0xff822fe0 stack pointer = 0x28:0x80ca9740 frame pointer = 0x28:0xff8abb40 frame pointer = 0x28:0xff80ee2108b0 code segment= base 0x0, limit 0xf, type 0x1b code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= processor eflags = interrupt enabled, IOPL = 0 IOPL = 0 current process = current process = 0 (spa_zio) 12 (irq48: mvs0) trap number = 19 trap number = 19 panic: non-maskable interrupt trap cpuid = 0 Here are some details about the controller. m...@pci0:6:1:0: class=0x01 card=0x11ab11ab chip=0x608111ab rev=0x09 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' device = 'MV88SX6081 8-port SATA II PCI-X Controller' class = mass storage subclass = SCSI After the panic the server just hangs, so i was not able to get a dump or get a backtrace. I'm just building a custom kernel with debugging turned on. Anything i could do in the meantime? Thanks, Florian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
