Getting kernel messages using syslog-ng 3.x
I'm in need of getting help using syslog-ng 3 on FreeBSD 8.0-RELEASE.
I'm having trouble getting kernel messages. I've made a very small
config file, and this isn't working either.
@version:3.0
source local { internal(); file(/dev/klog); unix-dgram(/var/run/log); };
destination all { file(/var/log/all.log); };
log { source(local); destination(all); };
The /etc/rc.conf.local has the following options in it.
syslogd_enable=NO
syslog_ng_enable=YES
syslog_ng_pid=/var/run/syslog-ng.pid
This picks up other things, but not the kernel messages. I assume it's
a small configuration issue. Using file /dev/klog works using
syslog-ng 2.x on FreeBSD 8.0, but not using syslog-ng 3.x. Let me
know. Thanks.
Phusion
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 7.2-p4 serial console not showing kernel messages?
Sven Hazejager s...@hazejager.nl writes: I'm having trouble getting 7.2-p4 to run. I'm using nanoBSD, either under VMware using a virtual serial null-modem or on an Alix Soekris-like serial-only CF-based device, both show this problem: my serial console does not display kernel messages, they all go to the VGA console! I'm using the nanoBSD cust_comsole function to enable the console. Relevant files are shown here: /boot.config: -h -S57600 /etc/ttys, only one line is on: ttyd0 /usr/libexec/getty std.57600 xterm on secure These are still in my kernel conf, if I remove these I get no kernel messages at all (kernel boots fine with this though): device atkbdc # AT keyboard controller device atkbd # AT keyboard device kbdmux # keyboard multiplexer device vga # VGA video card driver I have also tried to set this in the loader, no luck: hint.sio.0.flags=0x30 On the serial console, I see the boot manager (boot0) and the loader just fine. show in the loader says console=comconsole so that seems to be fine. However all kernel output goes to the VGA console. I *do* get a login prompt after a while on the serial console though. If I boot the same kernel over PXE on the ALIX, the kernel messages *do* go to the serial console... What am I overlooking? Checking the obvious: syslog.conf is configured to send the messages to the console? -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 7.2-p4 serial console not showing kernel messages?
On Mon, Nov 9, 2009 at 17:52, Lowell Gilbert freebsd-questions-lo...@be-well.ilk.org wrote: Checking the obvious: syslog.conf is configured to send the messages to the console? Haven't touched syslog.conf but this all happens before syslog is even starting. The problem is that the console is VGA, even though I have console=comconsole AND boot.config containing -h AND sio.0.flags 0x30. Has anyone actually gotten a serial console to work with FreeBSD 7.2-release? I'm having the same problems with 7-STABLE. Sven ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 7.2-p4 serial console not showing kernel messages?
On 11/9/09, Sven Hazejager s...@hazejager.nl wrote: On Mon, Nov 9, 2009 at 17:52, Lowell Gilbert freebsd-questions-lo...@be-well.ilk.org wrote: Checking the obvious: syslog.conf is configured to send the messages to the console? Haven't touched syslog.conf but this all happens before syslog is even starting. The problem is that the console is VGA, even though I have console=comconsole AND boot.config containing -h AND sio.0.flags 0x30. Has anyone actually gotten a serial console to work with FreeBSD 7.2-release? I'm having the same problems with 7-STABLE. FWIW, I do lots of serial consoles. Biggest issue I have is the boot.config options. Personally, the switches to detect (-P) and switch (-h) don't always seem to work (for me). If I have to see anything at the console, not only do I setup /boot/loader.conf but I will always use -D in /boot.config -- Dual setup. It pushes to both COM1 and VGA. Please try that. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
7.2-p4 serial console not showing kernel messages?
All, I'm having trouble getting 7.2-p4 to run. I'm using nanoBSD, either under VMware using a virtual serial null-modem or on an Alix Soekris-like serial-only CF-based device, both show this problem: my serial console does not display kernel messages, they all go to the VGA console! I'm using the nanoBSD cust_comsole function to enable the console. Relevant files are shown here: /boot.config: -h -S57600 /etc/ttys, only one line is on: ttyd0 /usr/libexec/getty std.57600 xterm on secure These are still in my kernel conf, if I remove these I get no kernel messages at all (kernel boots fine with this though): device atkbdc # AT keyboard controller device atkbd # AT keyboard device kbdmux # keyboard multiplexer device vga # VGA video card driver I have also tried to set this in the loader, no luck: hint.sio.0.flags=0x30 On the serial console, I see the boot manager (boot0) and the loader just fine. show in the loader says console=comconsole so that seems to be fine. However all kernel output goes to the VGA console. I *do* get a login prompt after a while on the serial console though. If I boot the same kernel over PXE on the ALIX, the kernel messages *do* go to the serial console... What am I overlooking? Thanks, Sven ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Serial console trouble: loader and login works, but no kernel messages
On Aug 23, 2009, at 14:18, Thomas Backman wrote: First off: Not subscribed to this list, please make sure to Cc me if you don't reply directly. :) Anyway, I finally got my null modem cable, and plugged in in between a machine running 8.0-BETA2 and one running WinXP using Hyperterminal. My settings: /boot/loader.conf: boot_multicons=YES boot_serial=YES comconsole_speed=115200 console=comconsole,vidconsole /etc/ttys: # Serial terminals # The 'dialup' keyword identifies dialin lines to login, fingerd etc. ttyu0 /usr/libexec/getty std.115200 vt100 on secure /boot.config (which is read properly): -Dh -S115200 Anything wrong in the above? Hyperterminal is set to 115200 bps, 8 bits, no parity, 1 stop bit, and no flow control (if that's the correct translation to English). On the serial console, I go from the screen with the FreeBSD logo, with single-user options etc. (which works fine), and then nothing, until a login tty pops up (which also works fine). The main, if not only, reason I want a serial console is to be able to use it for single user mode, DDB, and so on. All kernel messages, and all rc messages are seen only on the graphics card; the serial console receives nothing but the / boot.config: -Dh ..., the logo screen, and then the login screen, during startup and *nothing* at all during shutdown. Also, I'm able to login and use the system both via the serial console and via the graphics card/keyboard... Is this supposed to be? I'm not complaining, I just got the impression it was one or the other. Any advice on how to get the kernel/rc messages etc. to the serial console (only or as well)? Regards, Thomas OK, so to rule out any installation-related problems, I booted from a bootonly install CD (a May ~5th snapshot of 8.0-CURRENT), with boot - h -S115200. Same thing: bootloader stuff on the serial console, kernel messages on the local computer only - and very slowly, at that, I'd say about one line a second. You could very easily see the characters being written to the screen. Am I the only one having these problems? It'd suck to buy a rather expensive (probably because they're pretty rare these days, plus I had to order from abroad) null modem cable and have it be completely useless. Regards, Thomas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Serial console trouble: loader and login works, but no kernel messages
On Aug 26, 2009, at 18:04, Danny Braniss wrote: you need to set hint.uart.0.flags=0x10 danny I already tried that (in /boot/loader.conf); it shows up in dmesg (and didn't before), but still no luck. Regards/thanks, Thomas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Serial console trouble: loader and login works, but no kernel messages
At 12:10 PM 8/26/2009, Thomas Backman wrote: danny I already tried that (in /boot/loader.conf); it shows up in dmesg (and didn't before), but still no luck. Try adding it to /boot/device.hints eg hint.uart.0.at=isa hint.uart.0.port=0x3F8 hint.uart.0.flags=0x10 hint.uart.0.irq=4 hint.uart.1.at=isa hint.uart.1.port=0x2F8 Or, if you want to use loader.conf, try hw.uart.console=io:0x3f8 ---Mike Regards/thanks, Thomas ___ freebsd-curr...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org Mike Tancsa, tel +1 519 651 3400 Sentex Communications,m...@sentex.net Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Serial console trouble: loader and login works, but no kernel messages
On Aug 26, 2009, at 18:16, Mike Tancsa wrote: Or, if you want to use loader.conf, try hw.uart.console=io:0x3f8 ---Mike That solved it! Thanks a lot!! :) Regards, Thomas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Serial console trouble: loader and login works, but no kernel messages
On Aug 23, 2009, at 23:18, Carl Chave wrote: Did you try booting with the keyboard disconnected from the FreeBSD machine? Perhaps the vidconsole is favored when a keyboard is detected? On a linux box I had, I would get serial output from Grub, lose it during kernel load and then get a login once the OS was up, much like what you describe. I had to add a kernel argument to my Grub config so the kernel would output to the serial port. Did you look here: http://www.freebsd.org/doc/en/articles/console-server/freebsd.html I think 7.2 might be what you are missing but I can't check it myself. On Sun, Aug 23, 2009 at 3:13 PM, Thomas Backmanseren...@exscape.org wrote: On Aug 23, 2009, at 20:25, Tim Judd wrote: On 8/23/09, Thomas Backman seren...@exscape.org wrote: First off: Not subscribed to this list, please make sure to Cc me if you don't reply directly. :) Anyway, I finally got my null modem cable, and plugged in in between a machine running 8.0-BETA2 and one running WinXP using Hyperterminal. My settings: /boot/loader.conf: boot_multicons=YES boot_serial=YES comconsole_speed=115200 console=comconsole,vidconsole /etc/ttys: # Serial terminals # The 'dialup' keyword identifies dialin lines to login, fingerd etc. ttyu0 /usr/libexec/getty std.115200 vt100 on secure /boot.config (which is read properly): -Dh -S115200 Anything wrong in the above? Hyperterminal is set to 115200 bps, 8 bits, no parity, 1 stop bit, and no flow control (if that's the correct translation to English). On the serial console, I go from the screen with the FreeBSD logo, with single-user options etc. (which works fine), and then nothing, until a login tty pops up (which also works fine). The main, if not only, reason I want a serial console is to be able to use it for single user mode, DDB, and so on. All kernel messages, and all rc messages are seen only on the graphics card; the serial console receives nothing but the /boot.config: - Dh ..., the logo screen, and then the login screen, during startup and *nothing* at all during shutdown. Also, I'm able to login and use the system both via the serial console and via the graphics card/ keyboard... Is this supposed to be? I'm not complaining, I just got the impression it was one or the other. Any advice on how to get the kernel/rc messages etc. to the serial console (only or as well)? Regards, Thomas Do you use the VGA/vidconsole at all? A serial-only device (think soekris, ALIX/WRAP boards) that has no VGA will have different requirements than a serial-only device will. Your loader.conf statements are different than mine in the definition that you have more than I do to enable serial. My loader.conf just has one statement: console=comconsole - to feed ALL bootloaders, kernel probing, rc startup on the serial device. /etc/ttys defines the login lines. Though trial and error, I found when you use a dual-setup: comconsole,vidconsole, the first one (comconsole) will get rc output, and vidconsole won't. Of course, you're on 8.0 and I don't run BETAs. So the 8.0 BETA might still be having com port oddities, plus I noticed your ttys line is ttyu0, not ttyd0. Did 8.0 change the serial line device? To enable a serial-only device in my setups: /boot/loader.conf: console=comconsole /boot.config: -D /etc/ttys: # enable serial line, cons25 or vt100, depending if I'm originating from a bsd or windows box. Enabling dual-setups should be just the loader.conf change to dual console. HTH (Sorry for the lack of inline replies.) I do have a graphics card, and ideally I'd like to be able to use both, but serial has higher priority (with serial access, I can use minicom on another *nix box and essentially ssh into DDB, and stuff like that - right now I have to borrow a monitor, and write info down manually if needed, turning my head back and forth). I've tried lots of combinations of console=, including simply 'console=comconsole' and/or combinations of that and -D, -h- -Dh and -P in /boot.config. The extra lines in loader.conf are from the handbook, which says they're needed to use comconsole_speed. It seems they do the same thing as - D and -h, though. Oh, and re: /etc/ttys: Yup, it's ttyuX when using uart(4) which seems to be the default now. Actually, since my last buildworld half an hour ago I'm on 9.0-CURRENT. ;) Also, I made sure to set flags to 0x10 for the serial port as per the handbook (although I did it using loader.conf, not the kernel config); before the change, dmesg didn't mention any flags, but it now does. Didn't help squat, though. Though trial and error, I found when you use a dual-setup: comconsole,vidconsole, the first one (comconsole) will get rc output, and vidconsole won't. This doesn't mirror my experience; comconsole and comconsole,vidconsole appears to be just the same for me. I've never gotten anything except the boot loader and a login prompt over to the serial
Serial console trouble: loader and login works, but no kernel messages
First off: Not subscribed to this list, please make sure to Cc me if you don't reply directly. :) Anyway, I finally got my null modem cable, and plugged in in between a machine running 8.0-BETA2 and one running WinXP using Hyperterminal. My settings: /boot/loader.conf: boot_multicons=YES boot_serial=YES comconsole_speed=115200 console=comconsole,vidconsole /etc/ttys: # Serial terminals # The 'dialup' keyword identifies dialin lines to login, fingerd etc. ttyu0 /usr/libexec/getty std.115200 vt100 on secure /boot.config (which is read properly): -Dh -S115200 Anything wrong in the above? Hyperterminal is set to 115200 bps, 8 bits, no parity, 1 stop bit, and no flow control (if that's the correct translation to English). On the serial console, I go from the screen with the FreeBSD logo, with single-user options etc. (which works fine), and then nothing, until a login tty pops up (which also works fine). The main, if not only, reason I want a serial console is to be able to use it for single user mode, DDB, and so on. All kernel messages, and all rc messages are seen only on the graphics card; the serial console receives nothing but the /boot.config: - Dh ..., the logo screen, and then the login screen, during startup and *nothing* at all during shutdown. Also, I'm able to login and use the system both via the serial console and via the graphics card/ keyboard... Is this supposed to be? I'm not complaining, I just got the impression it was one or the other. Any advice on how to get the kernel/rc messages etc. to the serial console (only or as well)? Regards, Thomas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Serial console trouble: loader and login works, but no kernel messages
On 8/23/09, Thomas Backman seren...@exscape.org wrote: First off: Not subscribed to this list, please make sure to Cc me if you don't reply directly. :) Anyway, I finally got my null modem cable, and plugged in in between a machine running 8.0-BETA2 and one running WinXP using Hyperterminal. My settings: /boot/loader.conf: boot_multicons=YES boot_serial=YES comconsole_speed=115200 console=comconsole,vidconsole /etc/ttys: # Serial terminals # The 'dialup' keyword identifies dialin lines to login, fingerd etc. ttyu0 /usr/libexec/getty std.115200 vt100 on secure /boot.config (which is read properly): -Dh -S115200 Anything wrong in the above? Hyperterminal is set to 115200 bps, 8 bits, no parity, 1 stop bit, and no flow control (if that's the correct translation to English). On the serial console, I go from the screen with the FreeBSD logo, with single-user options etc. (which works fine), and then nothing, until a login tty pops up (which also works fine). The main, if not only, reason I want a serial console is to be able to use it for single user mode, DDB, and so on. All kernel messages, and all rc messages are seen only on the graphics card; the serial console receives nothing but the /boot.config: - Dh ..., the logo screen, and then the login screen, during startup and *nothing* at all during shutdown. Also, I'm able to login and use the system both via the serial console and via the graphics card/ keyboard... Is this supposed to be? I'm not complaining, I just got the impression it was one or the other. Any advice on how to get the kernel/rc messages etc. to the serial console (only or as well)? Regards, Thomas Do you use the VGA/vidconsole at all? A serial-only device (think soekris, ALIX/WRAP boards) that has no VGA will have different requirements than a serial-only device will. Your loader.conf statements are different than mine in the definition that you have more than I do to enable serial. My loader.conf just has one statement: console=comconsole - to feed ALL bootloaders, kernel probing, rc startup on the serial device. /etc/ttys defines the login lines. Though trial and error, I found when you use a dual-setup: comconsole,vidconsole, the first one (comconsole) will get rc output, and vidconsole won't. Of course, you're on 8.0 and I don't run BETAs. So the 8.0 BETA might still be having com port oddities, plus I noticed your ttys line is ttyu0, not ttyd0. Did 8.0 change the serial line device? To enable a serial-only device in my setups: /boot/loader.conf: console=comconsole /boot.config: -D /etc/ttys: # enable serial line, cons25 or vt100, depending if I'm originating from a bsd or windows box. Enabling dual-setups should be just the loader.conf change to dual console. HTH ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Serial console trouble: loader and login works, but no kernel messages
On Aug 23, 2009, at 20:25, Tim Judd wrote: On 8/23/09, Thomas Backman seren...@exscape.org wrote: First off: Not subscribed to this list, please make sure to Cc me if you don't reply directly. :) Anyway, I finally got my null modem cable, and plugged in in between a machine running 8.0-BETA2 and one running WinXP using Hyperterminal. My settings: /boot/loader.conf: boot_multicons=YES boot_serial=YES comconsole_speed=115200 console=comconsole,vidconsole /etc/ttys: # Serial terminals # The 'dialup' keyword identifies dialin lines to login, fingerd etc. ttyu0 /usr/libexec/getty std.115200 vt100 on secure /boot.config (which is read properly): -Dh -S115200 Anything wrong in the above? Hyperterminal is set to 115200 bps, 8 bits, no parity, 1 stop bit, and no flow control (if that's the correct translation to English). On the serial console, I go from the screen with the FreeBSD logo, with single-user options etc. (which works fine), and then nothing, until a login tty pops up (which also works fine). The main, if not only, reason I want a serial console is to be able to use it for single user mode, DDB, and so on. All kernel messages, and all rc messages are seen only on the graphics card; the serial console receives nothing but the /boot.config: - Dh ..., the logo screen, and then the login screen, during startup and *nothing* at all during shutdown. Also, I'm able to login and use the system both via the serial console and via the graphics card/ keyboard... Is this supposed to be? I'm not complaining, I just got the impression it was one or the other. Any advice on how to get the kernel/rc messages etc. to the serial console (only or as well)? Regards, Thomas Do you use the VGA/vidconsole at all? A serial-only device (think soekris, ALIX/WRAP boards) that has no VGA will have different requirements than a serial-only device will. Your loader.conf statements are different than mine in the definition that you have more than I do to enable serial. My loader.conf just has one statement: console=comconsole - to feed ALL bootloaders, kernel probing, rc startup on the serial device. /etc/ttys defines the login lines. Though trial and error, I found when you use a dual-setup: comconsole,vidconsole, the first one (comconsole) will get rc output, and vidconsole won't. Of course, you're on 8.0 and I don't run BETAs. So the 8.0 BETA might still be having com port oddities, plus I noticed your ttys line is ttyu0, not ttyd0. Did 8.0 change the serial line device? To enable a serial-only device in my setups: /boot/loader.conf: console=comconsole /boot.config: -D /etc/ttys: # enable serial line, cons25 or vt100, depending if I'm originating from a bsd or windows box. Enabling dual-setups should be just the loader.conf change to dual console. HTH (Sorry for the lack of inline replies.) I do have a graphics card, and ideally I'd like to be able to use both, but serial has higher priority (with serial access, I can use minicom on another *nix box and essentially ssh into DDB, and stuff like that - right now I have to borrow a monitor, and write info down manually if needed, turning my head back and forth). I've tried lots of combinations of console=, including simply 'console=comconsole' and/or combinations of that and -D, -h- -Dh and -P in /boot.config. The extra lines in loader.conf are from the handbook, which says they're needed to use comconsole_speed. It seems they do the same thing as -D and -h, though. Oh, and re: /etc/ttys: Yup, it's ttyuX when using uart(4) which seems to be the default now. Actually, since my last buildworld half an hour ago I'm on 9.0-CURRENT. ;) Also, I made sure to set flags to 0x10 for the serial port as per the handbook (although I did it using loader.conf, not the kernel config); before the change, dmesg didn't mention any flags, but it now does. Didn't help squat, though. Though trial and error, I found when you use a dual-setup: comconsole,vidconsole, the first one (comconsole) will get rc output, and vidconsole won't. This doesn't mirror my experience; comconsole and comconsole,vidconsole appears to be just the same for me. I've never gotten anything except the boot loader and a login prompt over to the serial line - at least not at speed/settings that the client is set up to receive. I'm gonna try 9600 bps soon just to be sure it isn't that, but seeing how many others have mentioned using -S115200 I doubt it'll help. Thanks/regards, Thomas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Serial console trouble: loader and login works, but no kernel messages
Did you try booting with the keyboard disconnected from the FreeBSD machine? Perhaps the vidconsole is favored when a keyboard is detected? On a linux box I had, I would get serial output from Grub, lose it during kernel load and then get a login once the OS was up, much like what you describe. I had to add a kernel argument to my Grub config so the kernel would output to the serial port. Did you look here: http://www.freebsd.org/doc/en/articles/console-server/freebsd.html I think 7.2 might be what you are missing but I can't check it myself. On Sun, Aug 23, 2009 at 3:13 PM, Thomas Backmanseren...@exscape.org wrote: On Aug 23, 2009, at 20:25, Tim Judd wrote: On 8/23/09, Thomas Backman seren...@exscape.org wrote: First off: Not subscribed to this list, please make sure to Cc me if you don't reply directly. :) Anyway, I finally got my null modem cable, and plugged in in between a machine running 8.0-BETA2 and one running WinXP using Hyperterminal. My settings: /boot/loader.conf: boot_multicons=YES boot_serial=YES comconsole_speed=115200 console=comconsole,vidconsole /etc/ttys: # Serial terminals # The 'dialup' keyword identifies dialin lines to login, fingerd etc. ttyu0 /usr/libexec/getty std.115200 vt100 on secure /boot.config (which is read properly): -Dh -S115200 Anything wrong in the above? Hyperterminal is set to 115200 bps, 8 bits, no parity, 1 stop bit, and no flow control (if that's the correct translation to English). On the serial console, I go from the screen with the FreeBSD logo, with single-user options etc. (which works fine), and then nothing, until a login tty pops up (which also works fine). The main, if not only, reason I want a serial console is to be able to use it for single user mode, DDB, and so on. All kernel messages, and all rc messages are seen only on the graphics card; the serial console receives nothing but the /boot.config: - Dh ..., the logo screen, and then the login screen, during startup and *nothing* at all during shutdown. Also, I'm able to login and use the system both via the serial console and via the graphics card/ keyboard... Is this supposed to be? I'm not complaining, I just got the impression it was one or the other. Any advice on how to get the kernel/rc messages etc. to the serial console (only or as well)? Regards, Thomas Do you use the VGA/vidconsole at all? A serial-only device (think soekris, ALIX/WRAP boards) that has no VGA will have different requirements than a serial-only device will. Your loader.conf statements are different than mine in the definition that you have more than I do to enable serial. My loader.conf just has one statement: console=comconsole - to feed ALL bootloaders, kernel probing, rc startup on the serial device. /etc/ttys defines the login lines. Though trial and error, I found when you use a dual-setup: comconsole,vidconsole, the first one (comconsole) will get rc output, and vidconsole won't. Of course, you're on 8.0 and I don't run BETAs. So the 8.0 BETA might still be having com port oddities, plus I noticed your ttys line is ttyu0, not ttyd0. Did 8.0 change the serial line device? To enable a serial-only device in my setups: /boot/loader.conf: console=comconsole /boot.config: -D /etc/ttys: # enable serial line, cons25 or vt100, depending if I'm originating from a bsd or windows box. Enabling dual-setups should be just the loader.conf change to dual console. HTH (Sorry for the lack of inline replies.) I do have a graphics card, and ideally I'd like to be able to use both, but serial has higher priority (with serial access, I can use minicom on another *nix box and essentially ssh into DDB, and stuff like that - right now I have to borrow a monitor, and write info down manually if needed, turning my head back and forth). I've tried lots of combinations of console=, including simply 'console=comconsole' and/or combinations of that and -D, -h- -Dh and -P in /boot.config. The extra lines in loader.conf are from the handbook, which says they're needed to use comconsole_speed. It seems they do the same thing as -D and -h, though. Oh, and re: /etc/ttys: Yup, it's ttyuX when using uart(4) which seems to be the default now. Actually, since my last buildworld half an hour ago I'm on 9.0-CURRENT. ;) Also, I made sure to set flags to 0x10 for the serial port as per the handbook (although I did it using loader.conf, not the kernel config); before the change, dmesg didn't mention any flags, but it now does. Didn't help squat, though. Though trial and error, I found when you use a dual-setup: comconsole,vidconsole, the first one (comconsole) will get rc output, and vidconsole won't. This doesn't mirror my experience; comconsole and comconsole,vidconsole appears to be just the same for me. I've never gotten anything except the boot loader and a login prompt over to the serial line - at least not at speed
Help logging kernel messages after failed resume
OK, it goes like this: Dell Inspiron 1318, boot -v can be found in here: http://pastebin.com/f3a1c204a sysctl -a | grep hw.acpi | sort can be found in here: http://pastebin.com/fcfc0035 First shot: Try the Livefs CD, myhost# acpiconf -s 3 WORKS !!! The machine goes into suspend state and resumes_from_it_without_any_problems !! Second shot: Install ... myhost# acpiconf -s 3 does not work anymore ... I issue a myhost# acpiconf -s 3 and then I get a kernel message: fwohci0: fwohci_acpi_suspend ... The machine enters suspend state ... so far so good. Now, when I try yo resume from suspend, the machine spouts a plethora of kernel errors .. most notable ones beign bge0 errors, fwohci0 errors and the following ...: ad4: WARNING - SETFEATURES SET TRANSFERMODE taskqueue timeout - completing request directly ad4: WARNING - SETFEATURES SET TRANSFERMODE taskqueue timeout - completing request directly ad4: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly ad4: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly ad4: WARNING - SET_MULTI taskqueue timeout - completing request directly ata3: port not implemented ad4: WARNING - SETFEATURES SET TRANSFERMODE taskqueue timeout - completing request directly ad4: WARNING - SETFEATURES SET TRANSFERMODE taskqueue timeout - completing request directly ad4: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly ad4: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly ad4: WARNING - SET_MULTI taskqueue timeout - completing request directly ad4: TIMEOUT - WRITE_DMA48 retryng (1 retry left) LBA=272675445 As you can tell by now, the machine never recovers from -s 3 (or suspend to ram). The thing is, ad4 never gets back to life ... as a consecuence, even if the kernel trows its messages to stdout, they never get logged ! Is there a way to record those messages so I can post them on the corresponding list and file all the PRs I'm about to file?? Note: I can ssh into the notebook, then su - and issue acpiconf -s 3, but I can't get the notebook to WOL .. so .. I have to press the power button on the notebook to get it to resume and as a consecuence, those messages are sent to stdout (notebook screen) and I can't get them on the ssh client. SCRIPT(1) it's not a solution either .. because ad4 never gets back to life .. so script can't record a thing after it went into suspend :( Any help will be greatly appreciated. Just in case you are wondering what happens if I boot with ACPI disabled: Fatal trap 9 http://lists.freebsd.org/pipermail/freebsd-acpi/2009-May/005734.html Best Regards -- Blessings Gonzalo Nemmi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Help logging kernel messages after failed resume
On Thursday 28 May 2009 00:43:56 Gonzalo Nemmi wrote: Note: I can ssh into the notebook, then su - and issue acpiconf -s 3, but I can't get the notebook to WOL .. so .. I have to press the power button on the notebook to get it to resume and as a consecuence, those messages are sent to stdout (notebook screen) and I can't get them on the ssh client. SCRIPT(1) it's not a solution either .. because ad4 never gets back to life .. so script can't record a thing after it went into suspend :( Any help will be greatly appreciated. Just to debug this issue, make /var/log and /var/run memory disks. /var/run too cause of the socket that syslog uses. That at least will give you the ability to manually transcribe the logs in worst case, best case being to save them to an USB stick you plug in after resume or copy of the network if bge ever comes back up. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Kernel messages redirection
hi Does anyone know howto redirect/stop kernel messages from displaying on ttyv0? eg when you plug in a usb disk you get a load of messages to the 1st screen console I am writing a custom installer and its a pain as every time I label and geom provider it spams a load of stuff and messes up my nice display. This is nothing to do with syslog as I have already turned off logging to /dev/console, ive tried a few curious looking sysctl varibles but not found anything that works yet. k ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Kernel messages redirection
On Wed, Jan 7, 2009 at 10:52 AM, chris.scott k...@snaffler.net wrote: hi Does anyone know howto redirect/stop kernel messages from displaying on ttyv0? Look at conscontrol(8) as one option. ( There may be other ways that work better for your case, but I have used conscontrol on my 7.0-RELEASE machine before with success ) You can use conscontrol(8) to either mute, or redirect kernel messages to another virtual console. Good Luck. ---Dave Horn eg when you plug in a usb disk you get a load of messages to the 1st screen console I am writing a custom installer and its a pain as every time I label and geom provider it spams a load of stuff and messes up my nice display. This is nothing to do with syslog as I have already turned off logging to /dev/console, ive tried a few curious looking sysctl varibles but not found anything that works yet. k ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Kernel messages redirection
typical, after hunting around for a few days and not no luck, i get luck just after giving in and posting to this list 8/ $ sysctl -a| grep mute kern.consmute: 0 does the job setting it in boot/loader.conf makes the kernel silently boot but im setting in in /etc/sysctl.conf so it set at userland. This way i can see the kernel boot normally rather than looking like its hung, no anoying geom messages now hmm, now to tidy up stuff that looked like it was working nicely before i ran it in the root console David Horn wrote: On Wed, Jan 7, 2009 at 10:52 AM, chris.scott k...@snaffler.net wrote: hi Does anyone know howto redirect/stop kernel messages from displaying on ttyv0? Look at conscontrol(8) as one option. ( There may be other ways that work better for your case, but I have used conscontrol on my 7.0-RELEASE machine before with success ) You can use conscontrol(8) to either mute, or redirect kernel messages to another virtual console. Good Luck. ---Dave Horn eg when you plug in a usb disk you get a load of messages to the 1st screen console I am writing a custom installer and its a pain as every time I label and geom provider it spams a load of stuff and messes up my nice display. This is nothing to do with syslog as I have already turned off logging to /dev/console, ive tried a few curious looking sysctl varibles but not found anything that works yet. k ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Changing default colors of syscons / kernel messages
On Sun, 23 Nov 2008 17:42:03 +0100, [EMAIL PROTECTED] wrote: hey again ... ive asked, if somebody could help me with making the bootmanager, the kernel.-booting and shutdown-process green/black colored (like netbsd) ive get no answer yet, i hope, you can still help me ... It isn't the answer to your question, but: 1. Try do use a subject that is in relationship to your question. 2. Try to wrap your lines at approx. column 70, this makes correct quoting easier. I was free to correct them both. :-) Now regarding your question: It is possible to change the color attributes for the kernel messages which FreeBSD usually displays white on black, and OpenBSD grey on blue. As far as I remember - I tried it once -, there are makeoptions in the kernel configuration file to be set. See the handbook section about how to build a custom kernel for the correct procedures. The correct settings are mentioned in /usr/src/sys/conf/NOTES, lines 1339 cont. (1343 cont): # The following options will let you 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) But I'm not sure you can change the settings for the boot manager itself in an easy way. Maybe a modification of the boot loader's source code makes it possible... -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing default colors of syscons / kernel messages
On Sun, 23 Nov 2008 17:42:03 +0100, [EMAIL PROTECTED] wrote: hey again ... ive asked, if somebody could help me with making the bootmanager, the kernel.-booting and shutdown-process green/black colored (like netbsd) ive get no answer yet, i hope, you can still help me ... It isn't the answer to your question, but: 1. Try do use a subject that is in relationship to your question. 2. Try to wrap your lines at approx. column 70, this makes correct quoting easier. I was free to correct them both. :-) Now regarding your question: It is possible to change the color attributes for the kernel messages which FreeBSD usually displays white on black, and OpenBSD grey on blue. As far as I remember - I tried it once -, there are makeoptions in the kernel configuration file to be set. See the handbook section about how to build a custom kernel for the correct procedures. The correct settings are mentioned in /usr/src/sys/conf/NOTES, lines 1339 cont. (1343 cont): # The following options will let you 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) But I'm not sure you can change the settings for the boot manager itself in an easy way. Maybe a modification of the boot loader's source code makes it possible... yours Pt! Schon vom neuen WEB.DE MultiMessenger gehört? Der kann`s mit allen: http://www.produkte.web.de/messenger/?did=3123 -- Die Rechtschreibreform ist völlig in Ordnung, wenn man weder lesen noch schreiben kann. (Loriot) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel messages
On Sunday 28 September 2008 07:37:31 Sasa Stupar wrote: Runing FBSD 7 amd64. I have noticed in my cron security output: +rtfree: 0xff0001424c30 has 1 refs There are sometimes only a few lines, but sometimes there are 100 lines or more (all exactly the same). I didn't find anything on the net (google) so I am asking here. Really? http://www.google.com/bsd?num=30hl=ensafe=offq=rtfree In short it's a driver bug, a driver doesn't use proper macros to manage routing tables and the refcount goes bad. Report the error on -net and/or do a send-pr with netstat -r output. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Kernel messages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Runing FBSD 7 amd64. I have noticed in my cron security output: +rtfree: 0xff0001424c30 has 1 refs There are sometimes only a few lines, but sometimes there are 100 lines or more (all exactly the same). I didn't find anything on the net (google) so I am asking here. Regards, Sasa -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkjfGBsACgkQNT6IH6ilQwitOQCfdsVRKaVyyhPp67WOcMpk8mxs 1nEAn1GvrTvKp7RabfJLFZj+70mIySgF =sZsQ -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: No kernel messages displayed during boot
Le 16/11/2007 à 19:02:01+0100, Dmitry Karasik a écrit Hello, My 6.2-STABLE crashed today, and when I rebooted it, a very strange effect appeared: from the second the kernel took over, immediately after loading all .ko files, no text was printed in the console. The system booted though, and the next text was printed to the console was the login prompt. The screen didn't went blank, just all kernel messages and output of /etc/rc* wasn't there -- all was printed on the screen was FreeBSD boot menu, and login prompt. I don't known if my experience is the same as your. But when I have two KVM with a HP Proliant DL 380 G5 I've got exact same problem. but when I connect the screen directly to the server the problem disapear. Don't known if this message can help you. Regards. JAS -- Albert SHIH Observatoire de Paris Meudon SIO batiment 15 Téléphone : 01 45 07 76 26 Heure local/Local time: Ven 16 nov 2007 19:45:31 CET ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
No kernel messages displayed during boot
Hello, My 6.2-STABLE crashed today, and when I rebooted it, a very strange effect appeared: from the second the kernel took over, immediately after loading all .ko files, no text was printed in the console. The system booted though, and the next text was printed to the console was the login prompt. The screen didn't went blank, just all kernel messages and output of /etc/rc* wasn't there -- all was printed on the screen was FreeBSD boot menu, and login prompt. I've re-run 'make installworld' and 'make installkernel' (as I had leftovers from recent buildworld), - didn't help. I've tried to power down the machine (suspecied video card trouble), I've resetted BIOS, I've even disabled com port in BIOS (because the behavior looks like booting on serial console) -- nothing, absolutely nothing changes it. When I tried to boot in single-user mode, the prompt was never displayed at all, which fact indeed makes me think alogn the path of the wrong boot console. I've removed /boot/loader.conf, and double-checked that /boot.config isn't present - didn't help. My question is therefore, what cause of this effect might be? Or, if noone would be able to answer this, how I would print messages from kernel (I'd recompile it for that purpose) to identify which device it picked up for console IO -- and especially, how I print that either to a file, or directly to /dev/console? -- Thank you, Dmitry Karasik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
kernel messages question
Hi Freebsd When there is messages in /var/log/messages as seen below # bzip2 -d -c messages.0.bz2|grep sio4 Jan 12 22:32:42 DAK kernel: sio4: Sierra Wireless AC860 at port 0x3e8-0x3ee irq 22 function 0 config 32 on pccard0 Jan 12 22:32:42 DAK kernel: sio4: type 8250 or not responding Jan 12 22:32:42 DAK kernel: sio4: unable to activate interrupt in fast mode - using normal mode Does that mean that pccard0 is the device driver for thsi Sierra Wireless card ? If yes how can I probe that to make sure it responds with hat driver. Thanks DAk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
6.1 kernel messages
Having just migrated a server from 4.10-STABLE to 6.1-STABLE, I'm curious about some kernel messages in dmesg that I hadn't seen before: asr0: [GIANT-LOCKED] (adaptec RAID adapter) uhci0: [GIANT-LOCKED] (USB driver) atkbd0: [GIANT-LOCKED] (keyboard driver) I'm running SMP with 2 CPUs...a quick google shows that some people think it may be cause for concern but others do not. Is it? Then there's this: acpi0: PTLTD RSDT on motherboard acpi0: Power Button (fixed) acpi: bad write to port 0x070 (8), val 0x43 acpi: bad read from port 0x071 (8) That driver isn't in my kernel which is derived from GENERIC; I found info on it in PAE: # Compile acpi in statically since the module isn't built properly. Most # machines which support large amounts of memory require acpi. device acpi I only have 1GB of RAM in this server, so can I simply ignore this? James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am = ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.1 kernel messages
[EMAIL PROTECTED] wrote: Having just migrated a server from 4.10-STABLE to 6.1-STABLE, I'm curious about some kernel messages in dmesg that I hadn't seen before: asr0: [GIANT-LOCKED] (adaptec RAID adapter) uhci0: [GIANT-LOCKED] (USB driver) atkbd0: [GIANT-LOCKED] (keyboard driver) I'm running SMP with 2 CPUs...a quick google shows that some people think it may be cause for concern but others do not. Is it? I don't think it's a problem - at least not a major problem that you need to lose sleep over, unless you're a kernel hacker. It just means that those particular drivers have not yet been updated to support fine-grained kernel locking and so the Giant lock is acquired on the entire kernel when these drivers run - meaning that other processes can't be serviced by the kernel at the same time. In FreeBSD 4.x this kind of message didn't exist because having only one process accessing the kernel at any one time was the *only* possibility back then. Then there's this: acpi0: PTLTD RSDT on motherboard acpi0: Power Button (fixed) acpi: bad write to port 0x070 (8), val 0x43 acpi: bad read from port 0x071 (8) AFAIK this is FreeBSD telling you that your machine's BIOS is trying to access memory areas where it has no business going. I started seeing those messages on my 6.1-STABLE home box sometime in June this year and have been ignoring them. So far, nothing bad seems to have happened. Sorry for somewhat vague answers, but seeing as nobody has offered anything more scientific... -- Toomas Aas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel messages
On Apr 20, 2006, at 7:50 PM, Kevin Kinsey wrote: jekillen wrote: Hello; I have a question about a disconcerting event relayed to me from my kernel. there are eight entries regarding network interface status: rl0 link changed to DOWN UP DOWN UP sis0 promiscuous mode enabled disabled enabled disabled The disconcerting entries are re sis0 promiscuous mode enabled. Is the kernel trying to eaves drop on someone? Not without assistance, most likely ;-). One link is to the inside network and the other is to static ip address that is assigned but as yet has not been configured on the router to receive requests from outside. I admit, I am learning at this point. I've been watching the router security log and have seen just in the last week (as long as it has had the static ip's assigned) several hundred broadcast amplification attempts blocked. And I have been reading my root mail and am now interested in a tutorial or some published specifics about how to interpret these messages. I'm running v6 release on AMD64. I'm setting up to host a web site. thanks in advance. JK PS in the mean time I will be going through what I have already. Generally, promiscuous mode is pretty much what you have guessed ... used in network analysis. Software such as bpf(4), and higher level apps such as netgraph, tcpdump, ethereal, etc. use promiscuous mode to grab network traffic. So, the first thing you ask yourself is, have I (or anyone allowed to be root) used any of this type of software? There might be other explanations, but I'm not suitably prepared to address them. Kevin Kinsey There are 2 factors that bear directly on this situation: I am the only one who uses these machines on the inside network. I have not been able to get into the web site from out side (so I presume no one else can either) For this reason it appears that the kernel may be doing security audits based on, possibly, suspicious events. But sis0 is the inside network interface. If I read the time correctly, I.E. 03 being 3 o'clock in the morning, this machine is the only one beside the router and a n.a.s device that are running. And this is the first time in the eight weeks total that this machine has been operational, that I have seen this message. Could the phone co be 'phishing' around? (SBC). Anyhow that's why I questioned the phone co's $250 installation charge, I told them I know how to set up the network and DNS stuff and was concerned about the possibility of a technician putting a root kit on my system. As it turned out, I had to let him install their router because he couldn't get mine to work (Zoom xv5) I have a Mac OSX machine that has been assigned one of the initial static ip's. It also has 2 interfaces the inside interface connects to the same network the web server is on. But I don't leave the Mac on continuously. When the technician set up the router it was using DCHP to assign the ip. I noticed it change the host name as reflected in the bash shell command line prompt. So as to their scruples I can only hope that there isn't some proprietary gadget running on the router that sniffs around on remote provocation. This might serve as a heads up to anyone with a similar situation. JK -- The idle mind knows not what it is it wants. -- Quintus Ennius ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel messages
jekillen writes: . When the technician set up the router it was using DCHP to assign the ip. I noticed it change the host name as reflected in the bash shell command line prompt. DHCP requires bpf(4). bpf(4) uses promiscuous mode by default. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel messages
On Apr 20, 2006, at 7:50 PM, Kevin Kinsey wrote: jekillen wrote: (cut) Not without assistance, most likely ;-). One link is to the inside network and the other is to static ip address that is assigned but as yet has not been configured on the router to receive requests from outside. I admit, I am learning at this point. I've been watching the router security log and have seen just in the last week (as long as it has had the static ip's assigned) several hundred broadcast amplification attempts blocked. And I have been reading my root mail and am now interested in a tutorial or some published specifics about how to interpret these messages. I'm running v6 release on AMD64. I'm setting up to host a web site. thanks in advance. JK PS in the mean time I will be going through what I have already. Generally, promiscuous mode is pretty much what you have guessed ... used in network analysis. Software such as bpf(4), and higher level apps such as netgraph, tcpdump, ethereal, etc. use promiscuous mode to grab network traffic. So, the first thing you ask yourself is, have I (or anyone allowed to be root) used any of this type of software? There might be other explanations, but I'm not suitably prepared to address them. Kevin Kinsey Actually I neglected to mention that I had used tcpdump on this machine but not a 3 AM in the morning. But that is probably what it is all about. JK -- The idle mind knows not what it is it wants. -- Quintus Ennius ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Kernel messages
Hello; I have a question about a disconcerting event relayed to me from my kernel. there are eight entries regarding network interface status: rl0 link changed to DOWN UP DOWN UP sis0 promiscuous mode enabled disabled enabled disabled The disconcerting entries are re sis0 promiscuous mode enabled. Is the kernel trying to eaves drop on someone? One link is to the inside network and the other is to static ip address that is assigned but as yet has not been configured on the router to receive requests from outside. I admit, I am learning at this point. I've been watching the router security log and have seen just in the last week (as long as it has had the static ip's assigned) several hundred broadcast amplification attempts blocked. And I have been reading my root mail and am now interested in a tutorial or some published specifics about how to interpret these messages. I'm running v6 release on AMD64. I'm setting up to host a web site. thanks in advance. JK PS in the mean time I will be going through what I have already. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel messages
jekillen wrote: Hello; I have a question about a disconcerting event relayed to me from my kernel. there are eight entries regarding network interface status: rl0 link changed to DOWN UP DOWN UP sis0 promiscuous mode enabled disabled enabled disabled The disconcerting entries are re sis0 promiscuous mode enabled. Is the kernel trying to eaves drop on someone? Not without assistance, most likely ;-). One link is to the inside network and the other is to static ip address that is assigned but as yet has not been configured on the router to receive requests from outside. I admit, I am learning at this point. I've been watching the router security log and have seen just in the last week (as long as it has had the static ip's assigned) several hundred broadcast amplification attempts blocked. And I have been reading my root mail and am now interested in a tutorial or some published specifics about how to interpret these messages. I'm running v6 release on AMD64. I'm setting up to host a web site. thanks in advance. JK PS in the mean time I will be going through what I have already. Generally, promiscuous mode is pretty much what you have guessed ... used in network analysis. Software such as bpf(4), and higher level apps such as netgraph, tcpdump, ethereal, etc. use promiscuous mode to grab network traffic. So, the first thing you ask yourself is, have I (or anyone allowed to be root) used any of this type of software? There might be other explanations, but I'm not suitably prepared to address them. Kevin Kinsey -- The idle mind knows not what it is it wants. -- Quintus Ennius ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Kernel messages
jekillen writes: I have a question about a disconcerting event relayed to me from my kernel. there are eight entries regarding network interface status: rl0 link changed to DOWN UP DOWN UP I've been getting similar entries from a card (Linksys EG-1032) using re() in -CURRENT. I've ignored it. because it doesn't seen to affect the eventual operation, but it would be interesting to know why. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Numeric kernel messages
I'm suddenly getting kernel messages like I've never seen, usually nothing more than a number, although I've seen other characters. But nothing informational. For example ... Message from [EMAIL PROTECTED] at Wed Sep 21 08:19:52 2005 ... hypervoxel kernel: 92 and Message from [EMAIL PROTECTED] at Wed Sep 21 09:05:23 2005 ... hypervoxel kernel: :1 Note that the : :1 is not a typo. Running 5.3R, syslog.conf below *.err;kern.debug;auth.notice;mail.crit/dev/console *.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err /var/log/messages security.* /var/log/security auth.info;authpriv.info /var/log/auth.log mail.info /var/log/maillog ftp.info /var/log/xferlog cron.* /var/log/cron *.=debug /var/log/debug.log *.emerg * console.info /var/log/console.log *.* /var/log/fullset.log local7.* /var/log/pop.log __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange kernel messages
Colin J. Raven wrote: Hi all! I occasionally get these in my daily security run output (which is worrying in itself) Limiting closed port RST response from 1629 to 200 packets per second the number of these can range from one or two, to sometimes 25 - 30 although the latter case is rarer. Usually there's about six or so. These don't arrive every day, usually about once per week on average. You get those when someone nmaps you. What I do aside from FreeBSD's builtin anti-DOS stuff is; 1. Blackholeing 2.portsentry (it is kinda a honey pot but has some pretty neat features) Is this an OS response to an attempted attack, limiting potential DDOS damage? yes it is. How heavily loaded is your server? That's how I'm reading it, but of course I'm guessing. If that *is* so, what mechanism is doing this? Others have answered this question allready ;) FreeBSD 4.11 STABLE Regards TIA -Colin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Strange kernel messages
Hi all! I occasionally get these in my daily security run output (which is worrying in itself) Limiting closed port RST response from 1629 to 200 packets per second the number of these can range from one or two, to sometimes 25 - 30 although the latter case is rarer. Usually there's about six or so. These don't arrive every day, usually about once per week on average. Is this an OS response to an attempted attack, limiting potential DDOS damage? That's how I'm reading it, but of course I'm guessing. If that *is* so, what mechanism is doing this? FreeBSD 4.11 STABLE Regards TIA -Colin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange kernel messages
Hello Colin, Saturday, May 14, 2005, 9:14:20 AM, you thoughtfully wrote the following: Hi all! I occasionally get these in my daily security run output (which is worrying in itself) Limiting closed port RST response from 1629 to 200 packets per second the number of these can range from one or two, to sometimes 25 - 30 although the latter case is rarer. Usually there's about six or so. These don't arrive every day, usually about once per week on average. Is this an OS response to an attempted attack, limiting potential DDOS damage? That's how I'm reading it, but of course I'm guessing. If that *is* so, what mechanism is doing this? your kernel is limitting number of icmp ping requests to 200, someone is possibly trying to ping -f you. You can also decrease/increase this limit with net.inet.icmp.icmplim FreeBSD 4.11 STABLE Regards TIA -Colin -- Best Regards, DanGer, ICQ: 261701668 | e-mail protecting at: http://www.2pu.net/ http://danger.rulez.sk | proxy list at:http://www.proxy-web.com/ | FreeBSD - The Power to Serve! [ i locked the door to my own cell, and i lost the key ]
Re: Strange kernel messages
On Sat, May 14, 2005 at 09:14:20AM +0200, Colin J. Raven wrote: Hi all! I occasionally get these in my daily security run output (which is worrying in itself) Limiting closed port RST response from 1629 to 200 packets per second the number of these can range from one or two, to sometimes 25 - 30 although the latter case is rarer. Usually there's about six or so. These don't arrive every day, usually about once per week on average. Is this an OS response to an attempted attack, limiting potential DDOS damage? That's how I'm reading it, but of course I'm guessing. If that *is* so, what mechanism is doing this? FreeBSD 4.11 STABLE See the FAQ: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/networking.html#ICMP-RESPONSE-BW-LIMIT -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange kernel messages
On May 14 at 09:19, Daniel Gerzo responded helpfully: Limiting closed port RST response from 1629 to 200 packets per second your kernel is limitting number of icmp ping requests to 200, someone is possibly trying to ping -f you. You can also decrease/increase this limit with net.inet.icmp.icmplim and: On May 14 at 09:35, Erik Trulsson also launched this into the bitstream: See the FAQ: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/networking.html#ICMP-RESPONSE-BW-LIMIT Daniel Erik; many thanks for your responses! Most helpful and illuminating. I'm glad to know the cause/cure for this Regards Thanks, -Colin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
strange kernel messages..
Hello. Please send replies also to my mailbox, as I'm not on this list. Can anybody tell me what are these messages about? Are them just informational or do I have to worry? Aug 2 18:23:59 web kernel: lock order reversal Aug 2 18:23:59 web kernel: 1st 0xc07066e0 UMA lock (UMA lock) @ /usr/src/sys/vm/uma_core.c:1200 Aug 2 18:23:59 web kernel: 2nd 0xc0c31100 system map (system map) @ /usr/src/sys/vm/vm_map.c:2210 Aug 2 19:12:21 web kernel: lock order reversal Aug 2 19:12:21 web kernel: 1st 0xc8c1c39c vm object (vm object) @ /usr/src/sys/vm/swap_pager.c:1323 Aug 2 19:12:21 web kernel: 2nd 0xc0705b80 swap_pager swhash (swap_pager swhash) @ /usr/src/sys/vm/swap_pager.c:1838 Aug 2 19:12:21 web kernel: 3rd 0xc6853108 vm object (vm object) @ /usr/src/sys/vm/uma_core.c:873 They started showing up after last world upgrade web.dti.supsi.ch# uname -a FreeBSD web.dti.supsi.ch 5.2.1-RELEASE-p9 FreeBSD 5.2.1-RELEASE-p9 #2: Fri Jul 30 17:35:55 CEST 2004 root@:/usr/obj/usr/src/sys/WEB i386 Thank you. -- Roberto Nunnari -software engineer- mailto:[EMAIL PROTECTED] Scuola Universitaria Professionale della Svizzera Italiana Dipartimento Tecnologie Innovative http://www.dti.supsi.ch SUPSI-DTI Via Cantonaletel: +41-91-6108561 6928 Mannofax: +41-91-6108570 Switzerland (o o) ===oOO==(_)==OOo ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: strange kernel messages..
Roberto Nunnari wrote: Hello. Please send replies also to my mailbox, as I'm not on this list. Can anybody tell me what are these messages about? Are them just informational or do I have to worry? Aug 2 18:23:59 web kernel: lock order reversal Aug 2 18:23:59 web kernel: 1st 0xc07066e0 UMA lock (UMA lock) @ /usr/src/sys/vm/uma_core.c:1200 Aug 2 18:23:59 web kernel: 2nd 0xc0c31100 system map (system map) @ /usr/src/sys/vm/vm_map.c:2210 Aug 2 19:12:21 web kernel: lock order reversal Aug 2 19:12:21 web kernel: 1st 0xc8c1c39c vm object (vm object) @ /usr/src/sys/vm/swap_pager.c:1323 Aug 2 19:12:21 web kernel: 2nd 0xc0705b80 swap_pager swhash (swap_pager swhash) @ /usr/src/sys/vm/swap_pager.c:1838 Aug 2 19:12:21 web kernel: 3rd 0xc6853108 vm object (vm object) @ /usr/src/sys/vm/uma_core.c:873 This is a so-called lock order reversal (LOR). To learn more about LORs in general and specifically about the one you are seeing, please see here: http://sources.zabbadoz.net/freebsd/lor.html -- # 007 Simon signature.asc Description: Digital signature
Re: strange kernel messages..
Thank you Simon. Simon Barner wrote: Roberto Nunnari wrote: Hello. Please send replies also to my mailbox, as I'm not on this list. Can anybody tell me what are these messages about? Are them just informational or do I have to worry? Aug 2 18:23:59 web kernel: lock order reversal Aug 2 18:23:59 web kernel: 1st 0xc07066e0 UMA lock (UMA lock) @ /usr/src/sys/vm/uma_core.c:1200 Aug 2 18:23:59 web kernel: 2nd 0xc0c31100 system map (system map) @ /usr/src/sys/vm/vm_map.c:2210 Aug 2 19:12:21 web kernel: lock order reversal Aug 2 19:12:21 web kernel: 1st 0xc8c1c39c vm object (vm object) @ /usr/src/sys/vm/swap_pager.c:1323 Aug 2 19:12:21 web kernel: 2nd 0xc0705b80 swap_pager swhash (swap_pager swhash) @ /usr/src/sys/vm/swap_pager.c:1838 Aug 2 19:12:21 web kernel: 3rd 0xc6853108 vm object (vm object) @ /usr/src/sys/vm/uma_core.c:873 This is a so-called lock order reversal (LOR). To learn more about LORs in general and specifically about the one you are seeing, please see here: http://sources.zabbadoz.net/freebsd/lor.html -- # 007 Simon -- Roberto Nunnari -software engineer- mailto:[EMAIL PROTECTED] Scuola Universitaria Professionale della Svizzera Italiana Dipartimento Tecnologie Innovative http://www.dti.supsi.ch SUPSI-DTI Via Cantonaletel: +41-91-6108561 6928 Mannofax: +41-91-6108570 Switzerland (o o) ===oOO==(_)==OOo ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Signal-related kernel messages on threaded processes?
So, I'm working on a small threaded program here, and I get these: Mar 9 07:39:53 mortis kernel: failed to set signal flags properly for ast() Mar 9 07:39:53 mortis kernel: failed to set signal flags properly for ast() Mar 9 07:42:21 mortis last message repeated 3 times Mar 9 07:51:00 mortis last message repeated 26 times I _think_ (based on times) they're related to running the programs in gdb, though it's possible I got some when I was running it by itself. My system is: FreeBSD 5.0-CURRENT #0: Wed Jan 8 18:46:11 CST 2003 I've tracked it down to sys/kern/subr_trap.c:87, which looks like: if (SIGPENDING(p) ((p-p_sflag PS_NEEDSIGCHK) == 0 || (td-td_kse-ke_flags KEF_ASTPENDING) == 0)) printf(failed to set signal flags properly for ast()\n); inside #ifdef INVARIANTS, but that starts to lose me in details of housekeeping structs for procs/threads. This _is_ just using libc_r, not libkse, so the KSE tests wouldn't apply, right? What should I be doing in the program that I'm not to avoid that message? Or does it actually not really mean anything for my process, and is all kernel-related? -- Matthew Fuller (MF4839) | [EMAIL PROTECTED] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Signal-related kernel messages on threaded processes?
On Sun, Mar 09, 2003 at 08:25:02AM -0600, Matthew D. Fuller wrote: What should I be doing in the program that I'm not to avoid that message? Or does it actually not really mean anything for my process, and is all kernel-related? It's a bug in the kernel, for which there is insufficient debugging information provided for it to be useful in locating the bug. bde posted a patch to current which improves the debugging information. Kris pgp0.pgp Description: PGP signature
Re: Bazillion kernel messages?
[EMAIL PROTECTED] wrote: From: Steve Warwick [EMAIL PROTECTED] I have a bazillion of these kernel messages showing up in my logs... Jan 9 13:53:30 la last message repeated 7 times Jan 9 13:59:21 la /kernel: arp: 00:05:32:0e:64:12 attempts to modify permanententry for 12.158.234.65 on rl0 I know rl0 is my ethernet but I don't host the .65 address. I have not seen these before - does anyone know what these messages mean? As always, advice and suggestions gratefully received. Thanks Steve No help here, but I get this (alot) and I've seen it discussed, but no resolution (if one is needed): ./kernel: arp: [address] has moved to [different] address on [cable modem mac address] I'd be interested in any suggestions, as well. These are two different issues. The [address] has moved to [different] ... message is simply caused by DHCP giving different addys to different computer as they turn on and off on the cable network. It's not really anything to be concerned with. I'm not sure what Steve's problem is, but it sounds like a something's wrong. If I were you, I'd do a little research to find out what computer has 00:05:32:0e:64:12 and see what software is running on it. That may get you pointed toward the cause/solution of the problem. -- Bill Moran Potential Technologies http://www.potentialtech.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Bazillion kernel messages?
[Format recovered--see http://www.lemis.com/email/email-format.html] On Friday, 10 January 2003 at 9:37:02 -0500, Bill Moran wrote: [EMAIL PROTECTED] wrote: From: Steve Warwick [EMAIL PROTECTED] I have a bazillion of these kernel messages showing up in my logs... Jan 9 13:53:30 la last message repeated 7 times Jan 9 13:59:21 la /kernel: arp: 00:05:32:0e:64:12 attempts to modify permanententry for 12.158.234.65 on rl0 I know rl0 is my ethernet but I don't host the .65 address. I have not seen these before - does anyone know what these messages mean? No help here, but I get this (alot) and I've seen it discussed, but no resolution (if one is needed): ./kernel: arp: [address] has moved to [different] address on [cable modem mac address] I'd be interested in any suggestions, as well. These are two different issues. The [address] has moved to [different] ... message is simply caused by DHCP giving different addys to different computer as they turn on and off on the cable network. It's not really anything to be concerned with. That's not the only possibility. It could be two machines both insisting that the address is theirs. That *is* an issue to be concerned with. I'm not sure what Steve's problem is, but it sounds like a something's wrong. If I were you, I'd do a little research to find out what computer has 00:05:32:0e:64:12 and see what software is running on it. That may get you pointed toward the cause/solution of the problem. You could also try connecting to it with ssh or rlogin or some such. That should help you identify which machine it is more easily. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Bazillion kernel messages?
I have a bazillion of these kernel messages showing up in my logs... Jan 9 13:53:30 la last message repeated 7 times Jan 9 13:59:21 la /kernel: arp: 00:05:32:0e:64:12 attempts to modify permanententry for 12.158.234.65 on rl0 I know rl0 is my ethernet but I don't host the .65 address. I have not seen these before - does anyone know what these messages mean? As always, advice and suggestions gratefully received. Thanks Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Bazillion kernel messages?
- Original Message - From: Steve Warwick [EMAIL PROTECTED] Date: Thu, 09 Jan 2003 16:52:02 -0800 To: [EMAIL PROTECTED] Subject: Bazillion kernel messages? I have a bazillion of these kernel messages showing up in my logs... Jan 9 13:53:30 la last message repeated 7 times Jan 9 13:59:21 la /kernel: arp: 00:05:32:0e:64:12 attempts to modify permanententry for 12.158.234.65 on rl0 I know rl0 is my ethernet but I don't host the .65 address. I have not seen these before - does anyone know what these messages mean? As always, advice and suggestions gratefully received. Thanks Steve No help here, but I get this (alot) and I've seen it discussed, but no resolution (if one is needed): ./kernel: arp: [address] has moved to [different] address on [cable modem mac address] I'd be interested in any suggestions, as well. -- bsdaemon freebsd: the power to serve http://www.freebsd.org [EMAIL PROTECTED] -- __ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup Meet Singles http://corp.mail.com/lavalife To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
