Re: Unable to alias IP's in 4.5
On Mon, May 06, 2002 at 12:43:38PM -0500, Erich Zigler wrote: It seems from FreeBSD version 4.5 on I am unable to alias IP addresses to a NIC card if the IP I am trying to alias has the same netmask as the previously bound IP. I get nothing but a file exists error from ifconfig. I have been doing this since 3.4 so Im wondering what has changed. Possibly the change is in the code that should have been keeping you from doing that all along. That's certainly the case if the alias IP is in the same network as the original, non-alias IP. -- Mike Andrews [EMAIL PROTECTED] Tired old sysadmin since 1964 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Support for INTEL high-end server cards
On Mon, Apr 01, 2002 at 08:37:14PM -0500, Forrest Aldrich wrote: Is there support somewhere for the high-end Intel (fxp) server optimized network cards? This one I have has the Intel i960 chip, the model number might be 687231-006. I ask because the lastest FreeBSD 4.5 snapshot installation did not pick up this card, so I used a lower-end 3com. There is indeed support. I have multiple machines at work and one at home with fxp cards; they just sit there and move data fast. I'm more than somewhat surprised that your install didn't see the fxp card out of the box, so to speak. Mine always have. -- Mike Andrews [EMAIL PROTECTED] Tired old sysadmin since 1964 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: samba make error (fwd)
On Wed, Mar 13, 2002 at 02:40:07PM +0100, Mario Pranjic wrote: ... Installing in backend... Installing in cgi-bin... Installing in filter... Installing in man... Installing in pdftops... Installing in pstoraster... Installing in scheduler... Installing in conf... Installing in data... Installing in doc... Installing in fonts... Installing in locale... Installing in ppd... Installing in templates... Installing cups-config script... Installing startup script... === Generating temporary packing list Bus error - core dumped I'm using FreeBSD 4.5 release and latest ports (updated via cvsup). The Bus error - core dumped message generally comes from a hardware failure. You may wish to do some problem determination based on that as a first approximation to the cause. -- Mike Andrews/ Michael Fenwick Namron, Ansteorra [EMAIL PROTECTED] Tired old sysadmin since 1964; Tired old music Laurel since 1986 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Machine rebooting frequently
On Mon, Mar 04, 2002 at 02:24:13PM +0100, Marcel Prisi wrote: Help !! We have a postgresql server (bi-PIII 833, 1Gb RAM, Adaptec SCSI RAID) rebooting by itself more and more frequently. I can not find any message anywhere, as if someone just presses the reboot button every now and then. It used to reboot every week or so, but it rebooted just six times today ! What can I do to fond the cause ? The machine runs 4.5-RELEASE, but used to run 4.3-PRERELEASE with the same trouble. I partially checked RAM through memtest86 (www.memtest86.com) but did not find any trouble. What might it be ? faulty processor ? Faulty power-supply ? any clues ? how to test ? The program-driven memory testers are at best rather bad at finding memory problems. Candidates, not in any particular order: o Overheated processor(s) o Overheated or faulty memory o Faulty or overloaded power supply o Faulty line power from the wall o Flaky motherbord (_Highly_ unlikely) and, inevitably, o Other Problem Determination and Isolation techniques: o Processor: run healthd or another voltage/temperature monitor to watch voltages and temperatures. Check all fans for good speed. Remove lint, cat-hair, etc., from heat sinks.[1] o Faulty or overheated memory: Check fans, etc., as above Take . memory to a store that has a hardware memory tester Remove one . SIMM at a time, reboot, wait . o Power Supply: Check DC power with voltmeter and oscilloscope. Replace PS if you _think_ there might be a problem with it or if it is anywhere near capacity. They're cheap here: about $100 will get you a very-high-capacity PS. o Faulty line power: Put the server on a known-good UPS. o Flaky motherboard: Replace motherboard (absolute last resort). [1] Cat hair in my house appears to be attracted preferentially to CPU heat sinks. -- Mike Andrews [EMAIL PROTECTED] Tired old sysadmin since 1964 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: unknown hardware address format (0x0123)
On Sun, Feb 17, 2002 at 11:40:12PM +0200, Ventsislav Velkov wrote: Hi, I have this message repeated numerous times in my message log: Feb 17 23:32:25 main /kernel: arp: unknown hardware address format (0x0123) What could be the reason ? Something visible to the receiving NIC is putting out b0rken packets on occasion. -- Mike Andrews [EMAIL PROTECTED] Tired old sysadmin since 1964 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Spontanious reboots
On Thu, Feb 14, 2002 at 09:43:53AM -0800, Kris Kennaway wrote: On Thu, Feb 14, 2002 at 05:35:27PM +, Baldur Gislason wrote: This box has been spontaniously rebooting for a while, we've replaced most of the hardware What hardware have you not tested/replaced? Consider doing so :) Have you made sure that the power supply isn't sagging under load and that the CPU(s) are not overheating? Checked all the fans? Those are two causes of spontaneous reboots that most people don't think to check. Kris, Baldur, and I, of course, check all this, having brought paranoia up from a mere art form to a true science. ;=) -- Mike Andrews [EMAIL PROTECTED] Tired old sysadmin since 1964 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Error in make buildworld
On Tue, Jan 22, 2002 at 09:34:56AM -0600, Stephen Montgomery-Smith wrote: I have recent sources (the most recent CTM delta). I do make -j4 buildworld on three different computers. It works on two of them, but on one of them (the fastest), I get: === usr.sbin/i4b/ispppcontrol rm -f .depend mkdep -f .depend -a-I/usr/obj/usr/src/i386/usr/include /usr/src/usr.sbin/i4b/ispppcontrol/ispppcontrol.c cd /usr/src/usr.sbin/i4b/ispppcontrol; make _EXTRADEPEND echo ispppcontrol: /usr/obj/usr/src/i386/usr/lib/libc.a .depend === usr.sbin/i4b/man === usr.sbin/boot0cfg rm -f .depend mkdep -f .depend -a-I/usr/obj/usr/src/i386/usr/include /usr/src/usr.sbin/boot0cfg/boot0cfg.c cd /usr/src/usr.sbin/boot0cfg; make _EXTRADEPEND echo boot0cfg: /usr/obj/usr/src/i386/usr/lib/libc.a .depend 1 error *** Error code 2 1 error *** Error code 2 1 error I didn't get this problem when I removed the -j4. This computer had a hard drive failure a few months ago, and the replacement drive is exceedingly fast. So maybe this computer is too fast for -j4 to work. As computers get faster and faster, maybe more and more people will have this problem. This is a known difficulty with multiple make threads. Note that I do _NOT_ call it a problem. It is caused by a thread that needs foo getting to the part that expects foo to have been built before the thread that actually builds foo gets to the build-foo code. I have found that I frequently can reissue the same command and foo will get built before it is required by something in another thread, and the make will run to completion the second time. It _will_ _not_ always run to completion, and if the first part of the make code cleans up, so that the make always starts from a clean set of output files, it probably won't run to completion. -- Mike Andrews [EMAIL PROTECTED] Tired old sysadmin since 1964 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: random crashes on 4.4-S - ASUS CUSL2-M mobo
On Thu, Jan 17, 2002 at 03:52:24PM -0500, Eric L. Howard wrote: I'm experiencing totally random crashes on a rackmount box. It's a PIII 750 on an ASUS CUSL2-M - onboard 3c920. The crashes are complete random and usually follow processes that die w/ SIGSEGV (a couple of SIGABRT thrown in for good measure have been found also). Syslog gives me info such as... (lines are wrapped) Jan 16 01:03:28 www /kernel: pid 692 (httpd), uid 65534: exited on signal 11 Jan 17 15:09:35 www /kernel: pid 290 (cpp0), uid 0: exited on signal 11 (core dumped) Jan 17 15:36:53 www /kernel: pid 310 (grep), uid 0: exited on signal 11 (core dumped) Jan 17 15:36:57 www /kernel: pid 252 (bash), uid 0: exited on signal 11 (core dumped) Jan 17 15:37:03 www /kernel: pid 313 (grep), uid 0: exited on signal 11 (core dumped) Dec 29 13:43:54 www /kernel: pid 1703 (cvsup), uid 0: exited on signal 6 (core dumped) I've swapped memory at least twice - each time yielding no success. Not sure about how to get anywhere debugging core files - pointers appreciated. Any and all ideas will be appreciated and checked. Thanx. 4.4-STABLE FreeBSD 4.4-STABLE #0: Fri Nov 23 23:41:12 EST 2001 Temperature? Can you run a temperature/fan-rpm/whatnot monitor, such as healthd? Totally random w.r.t. system load, or just totally random w.r.t. clock time? Or something else? -- Mike Andrews [EMAIL PROTECTED] Tired old sysadmin since 1964 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Problem with compact flash reader under -stable
On Mon, Dec 31, 2001 at 04:12:01PM -0500, Peter Radcliffe wrote: Duane H. Hesser [EMAIL PROTECTED] probably said: It appears to me, though, that the USB spec merely gives vendors a target to avoid. Apparently, they interpret it as Unspecified Serial Bus, since they all seem to go their own way. I have a Microtech Zio flash card reader which is too large for a keychain holder and too small for a paperweight. It is recognized by the ugen driver as SHUTTLE SCM Micro USBAT-02 and usbdevs -v reveals its ID as 04e6:1010, so I know it's there (but then, I knew that, as it was me that plugged it in :=). I played with one of these last night - got it recognised by umass but all I managed to do was hang my machine with any tweaks that I tried. Another SHUTTLE device is '#if 0'-ed out in umass because the ATAPI code isn't ready for primtime and I'm wondering if the other devices made by them are similar. The sandisk SDDR-31 was my answer - works just fine, shame it's not as small as some of them (at some point I'll hack on the travel flash which is at least recognised and probably just needs quirking. This is beginning to pique my interest quite strongly. I have a USB flash memory reader at home, and I just rebuilt everything to bring it all up to FreeBSD 4.5-PRERELEASE #0. I'll see what, if anything, I can coax it into doing. It certainly behaves as a removable disk drive on Win ME, and I can read and write it under that [CENSORED] OS. The results of the experiment tomorrow. -- Mike Andrews [EMAIL PROTECTED] Tired old sysadmin since 1964 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: naive security question
On Wed, Dec 05, 2001 at 05:46:54PM +, Matt Sykes wrote: My question is: how confident should I be? Is it really worthwhile for me to spend time setting up tripwire, kernel levels, etc? How many people are that really that paranoid (paranoia being a good thing)? I am a software developer (this box is at work), so the more time I spend developing software the better. Everyone's mileage varies - sometimes a lot. Is your machine inside a firewall? If so, then P(outside attack) goes down significantly for a good firewall configuration. If you are concerned about your co-workers attacking you, then you need to implement the same protections as for an outside attack -- and IMHO to go job-junting. My FreeBSD machine here at work has tripwire installed, and enough password to keep the honest people out. I certainly don't worry about kernel security levels. -- Mike Andrews [EMAIL PROTECTED] Tired old sysadmin since 1964 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Burncd errors...
On Wed, Oct 31, 2001 at 07:51:37PM -0800, Mikko Tyolajarvi wrote: In local.freebsd.stable you write: I'm trying to write a small audio file to a CD. Burncd refuses to do it... for instance... if I do something like: burncd -f /dev/acd0c -s 1 audio audio.raw fixate [...] Oct 31 21:45:18 endymion /kernel: acd0: WRITE_BIG - ILLEGAL REQUEST asc=64 ascq=00 error=00 [...] I cannot issue the msinfo or blank commands either. Any data files (data, XAmode1, mode2) are written correctly and flawlessly. The only reference I could find to errors similar to these were on NetBSD under different circumstances and with a Yamaha burner on FreeBSD. The FreeBSD reference mentioned bugs in the ATA driver that'd be fixed in 4.4-STABLE (which I'm running... cvsupped as of Sept 27th)... The burner is: acd0: CD-RW LG CD-RW CED-8080B at ata1-master using PIO4 Not that it is any help to you, but I have the same problem (data burns ok, audio does not) with an 8083B. And apparently we're not alone: http://www.freebsd.org/cgi/query-pr.cgi?pr=27893. My solution? I bought a Plextor. When I had this problem, I found that it was fixed by a cvsup/buildworld/installworld/newkernel cycle -- in the correct order. I was using a Sony CRX-140S SCSI burner at the time, and still am. Works fine now. -- Mike Andrews [EMAIL PROTECTED] Tired old sysadmin since 1964 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: network interface dies randomly - ifconfig down then up fixes
On Thu, Nov 01, 2001 at 10:39:33PM +1100, Graham Menhennitt wrote: I have a Arris Cornerstone CM200 cable modem connected to my FreeBSD stable (cvsupped last week) box via UTP into a NE2000 compatible ISA Ethernet adaptor. The connection randomly dies. I can send pings out of it and see the Activity LED flash on the modem but the FreeBSD box never sees any replies. Doing ifconfig ed1 down followed by ifconfig ed1 up fixes it. It's been happening for about the last two weeks (so it happened before the most recent cvsup also). It could be your cable provider doing things on their network. I have found that they are fond of making changes during prime time daylight, rather than in the wee hours, and most of their changes require me to reset my cablemodem (power cycle). If your /var/log/messages shows things like your upstream gateway MAC address changing (I run arpwatch, so I see that), then that has a high probability of being the problem. If not, then you may need to run tcpdump continuously on that interface to catch the ACK and SYN packets. I do that, too, so that I can trace attacks, but I do computer security for a living and hence am a professional paranoid. -- Mike Andrews [EMAIL PROTECTED] Tired old sysadmin since 1964 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: make -j4 vs -j8... 4 works, but 8 does not
On Sat, Sep 15, 2001 at 06:06:10PM -0400, Garance A Drosihn wrote: At 12:38 PM -0400 9/15/01, Mike Tancsa wrote: Should a parallel build always work ? I was just trying to stress a new series of MB we are evaluating and to my suprise, -j4 works, but not -j8 Well, in a philosophical sense, yes it should always work. Bugs creep into the process from time-to-time. I can not say that I know how to pin down such problems when they occur. I do know that earlier this year I had some problem I was checking, and as a tangent to that problem I did several fresh 'make buildworld's, going from -j2 to -j10 on my dual 650-MHz pentium machine. I then did md5 comparisons of the resulting obj-tree results, and they all came out the same. Of course, I wasn't getting any errors at build time, either. In my experience with a 2-CPU box, the problems with -j 5 or bigger are exclusively with module (or include file, etc.) A not being built by the time that process B needs it to complete a compile or link or whatever. These failures, in general, don't recur if the make is rerun from the failure point -- even with -j 8 or more. I frequently run with -j 16 when I'm doing kernel builds and buildworlds, and I haven't had any of those fail in a longish time. -- Mike Andrews [EMAIL PROTECTED] Tired old sysadmin since 1964 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: fxp SCB timeout problems, anyone have a solution?
On Thu, Aug 09, 2001 at 09:10:34PM -0400, Justin Sheehy wrote: [snip] The motherboard is an Intel 815SET Easton with onboard NIC. The relevant kernel messages at boot time are: Jul 31 17:08:17 phl /kernel: FreeBSD 4.3-RELEASE #0: Sat Apr 21 10:54:49 GMT 2001 Jul 31 17:08:17 phl /kernel: [EMAIL PROTECTED]:/usr/src/sys/compile/GENERIC Jul 31 17:08:17 phl /kernel: Timecounter i8254 frequency 1193182 Hz Jul 31 17:08:17 phl /kernel: CPU: Pentium III/Pentium III Xeon/Celeron (797.42-MHz 686-class CPU) Jul 31 17:08:17 phl /kernel: Origin = GenuineIntel Id = 0x68a Stepping = 10 Jul 31 17:08:17 phl /kernel: Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE ... Jul 31 17:08:18 phl /kernel: fxp0: Intel PLC 10/100 Ethernet port 0xdf00-0xdf3f mem 0xff8ff000-0xff8f irq 11 at device 8.0 on pci1 Jul 31 17:08:18 phl /kernel: fxp0: Ethernet address 00:03:47:a0:49:91 Whenever the machine is falling off-net, the only thing logged looks like this: Aug 9 16:27:02 phl /kernel: fxp0: SCB timeout Aug 9 16:27:02 phl last message repeated 17 times Aug 9 16:27:02 phl /kernel: fxp0: device timeout A quick Google search on fxp scb timeout yields about 30 hits. It is fairly apparent that you are not alone, and that the problem was know, (if not reported) as recently as June 2001. You _have_ submitted a PR? -- Mike Andrews [EMAIL PROTECTED] Tired old sysadmin since 1964 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: natd performance.
On Thu, Jul 26, 2001 at 11:57:26AM -0700, James Satterfield wrote: I've got a laptop running as my wireless gateway / firewall. It's got a PII 333MHz processor and 128MB ram I've only been able to pump about 4MBit/sec through it before natd is consuming nearly 100% of the cpu. Are these results what I should be expecting? Sounds pretty fishy to me. Do you have a really large ruleset or some other oddity? If not, then it would be nice to have more information. -- Mike Andrews [EMAIL PROTECTED] Tired old sysadmin since 1964 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
