Re: Reboot hangs on xeon server
Andy Reitz wrote: On Tue, 11 Apr 2006, Christopher McGee wrote: The server I have is using an Intel SE7501CW2 server board with 1 Xeon 2.0Ghz processor. It's got a Mylex AcceleRAID 170 card with 6 - 36GB scsi drives. When I reboot the machine, via ctrl-alt-del, or typing reboot, it syncs disks, then gives the messages: All buffers synced. Uptime: ##m##s At this point, it just hangs forever and has to be powercycled. I've tried installing 4.11, 5.4 and 6.0 on this box. The only version that works properly is 4.11, however, at this point I would prefer to not put another 4.x box in production. I have tried booting in safe mode and rebooting and I get the same result. I've tried disabling usb in the bios, in the kernel, and in both, and it still has the same results. Any ideas what could fix this? Hi Chris, This is not my area of expertise, but this sounds like an ACPI problem to me. You might try googling that (in conjunction with your motherboard) and see what comes up. HTH, -Andy. I have tried booting up with ACPI disabled. I still experienced the same reboot problem. I also thought that safe mode disabled acpi? I have also updated the bios on the motherboard and the bios on the raid card to see if they were the problem. Same problem persists. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Reboot hangs on xeon server
The server I have is using an Intel SE7501CW2 server board with 1 Xeon 2.0Ghz processor. It's got a Mylex AcceleRAID 170 card with 6 - 36GB scsi drives. When I reboot the machine, via ctrl-alt-del, or typing reboot, it syncs disks, then gives the messages: All buffers synced. Uptime: ##m##s At this point, it just hangs forever and has to be powercycled. I've tried installing 4.11, 5.4 and 6.0 on this box. The only version that works properly is 4.11, however, at this point I would prefer to not put another 4.x box in production. I have tried booting in safe mode and rebooting and I get the same result. I've tried disabling usb in the bios, in the kernel, and in both, and it still has the same results. Any ideas what could fix this? Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Carp and vlan issue
I am trying to use vlans with carp on some intel pro 1000mt cards with the em driver. I am running into some issues, I read somewhere there is a patch to make this work(I guess it hasn't been MFC'd or something). Does anyone know where I can get a patch for this or if the patch I've read about even really works? Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Freebsd to Sonicwall vpn tunnel
I have been searching far and wide for working examples of a site-to-site vpn tunnel from a freebsd firewall to a sonicwall appliance(Pro 2040). I can't even seem to make it work with it using anonymous in the racoon.conf, however, at some point I need it to use a specific sa for the sonicwall so tunnels connect using anon. Here are the errors I get from the various logs. From the sonicwall: IKE negotiation complete. Adding IPSec SA. (Phase 2) From racoon.log: 2006-01-11 14:21:38: INFO: isakmp.c:808:isakmp_ph1begin_i(): initiate new phase 1 negotiation: 24.153.127.112[500]=12.96.91.86[500] 2006-01-11 14:21:38: INFO: isakmp.c:813:isakmp_ph1begin_i(): begin Identity Protection mode. 2006-01-11 14:21:38: INFO: isakmp.c:2459:log_ph1established(): ISAKMP-SA established freebsd-ip[500]-sonicwall-ip[500] spi:960f1f7cdc88e2ac:b89856165f09f180 2006-01-11 14:21:39: INFO: isakmp.c:952:isakmp_ph2begin_i(): initiate new phase 2 negotiation: freebsd-ip[0]=sonicwall-ip[0] 2006-01-11 14:21:39: ERROR: isakmp_inf.c:843:isakmp_info_recv_n(): unknown notify message, no phase2 handle found. 2006-01-11 14:21:54: ERROR: pfkey.c:804:pfkey_timeover(): sonicwall-ip give up to get IPsec-SA due to time up to wait. 2006-01-11 14:22:05: INFO: isakmp.c:952:isakmp_ph2begin_i(): initiate new phase 2 negotiation: freebsd-ip[0]=sonicwall-ip[0] 2006-01-11 14:22:05: ERROR: isakmp_inf.c:843:isakmp_info_recv_n(): unknown notify message, no phase2 handle found. I have working tunnels from the sonicwall to other sonicwall. I also have working tunnels from the freebsd box to other freebsd machines. Has anyone else done what I'm trying to do successfully? Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntp problems (strata too high)
Svein Halvor Halvorsen wrote:
On 12/8/05, Michael Wynne [EMAIL PROTECTED] wrote:
The information contained in this e-mail and its attachments ('the
information) is intended only for the use of the individual or entity
to whom it is addressed, is private and confidential, may be privileged
or otherwise protected by work product immunity or other legal rules.
Access to the information by anyone else is unauthorized. [...]
Then why would you send it to a public mailinglist, that's archived
and propagated throughout the internet, and made available to anyone
through search engines and the like?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
I hate to reopen a dead thread, however, I'm having a very strange
problem I have 2 machines running ntpd. I just set this up and it is
not working. I don't think the ntpd servers are syncing properly and
ntpdate -b 192.168.1.2 doesn't work, it gives me a strata too high with
the -d flag. Here is my current config/output, this network is not
actually nat'd private ips so I changed the ips for security reasons:
server1(192.168.1.2)
/etc/ntp.conf
server 0.pool.ntp.org
server 1.pool.ntp.org
server 2.pool.ntp.org
server pool.ntp.org
peer 192.168.1.3
restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap
logconfig =syncall +clockall +sysall
ntpq -p output
remote refid st t when poll reach delay offset
jitter
==
+195.216.80.207 195.216.80.206 2 u 283 512 37 109.803 -230.38
62.815
*ipd50ad048.spee 130.149.17.8 2 u 285 512 37 101.458 -190.45
85.706
+antares.speedne 217.11.227.683 u 285 512 37 137.773 -192.71
85.431
+cheddar.halon.o 129.240.64.3 3 u 282 512 37 76.770 -276.95
62.389
192.168.1.3.STEP. 16 u1 12800.0000.000
4000.00
server2 (192.168.1.3)
/etc/ntp.conf
server 0.pool.ntp.org
server 1.pool.ntp.org
server 2.pool.ntp.org
server pool.ntp.org
peer 192.168.1.2
restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap
logconfig =syncall +clockall +sysall
ntpq -p output
remote refid st t when poll reach delay offset
jitter
==
zirkon.biophys. 134.99.128.802 u 71 1287 94.189 -77.270
27.511
oubliette.mctav .MSF.1 u 70 1287 98.417 -38.531
16.505
antares.speedne 217.11.227.683 u 70 1287 136.851 -53.314
27.989
cteha.ulp.co.il 192.114.62.249 3 u5 1287 170.650 -52.706
17.982
192.168.1.2.DROP. 16 u- 6400.0000.000
4000.00
Any help getting this to work will be appreciated.
Chris
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntp problems (strata too high)
Christopher McGee wrote:
Svein Halvor Halvorsen wrote:
On 12/8/05, Michael Wynne [EMAIL PROTECTED] wrote:
The information contained in this e-mail and its attachments ('the
information) is intended only for the use of the individual or entity
to whom it is addressed, is private and confidential, may be privileged
or otherwise protected by work product immunity or other legal rules.
Access to the information by anyone else is unauthorized. [...]
Then why would you send it to a public mailinglist, that's archived
and propagated throughout the internet, and made available to anyone
through search engines and the like?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
[EMAIL PROTECTED]
I hate to reopen a dead thread, however, I'm having a very strange
problem I have 2 machines running ntpd. I just set this up and it is
not working. I don't think the ntpd servers are syncing properly and
ntpdate -b 192.168.1.2 doesn't work, it gives me a strata too high
with the -d flag. Here is my current config/output, this network is
not actually nat'd private ips so I changed the ips for security reasons:
server1(192.168.1.2)
/etc/ntp.conf
server 0.pool.ntp.org
server 1.pool.ntp.org
server 2.pool.ntp.org
server pool.ntp.org
peer 192.168.1.3
restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap
logconfig =syncall +clockall +sysall
ntpq -p output
remote refid st t when poll reach delay offset
jitter
==
+195.216.80.207 195.216.80.206 2 u 283 512 37 109.803
-230.38 62.815
*ipd50ad048.spee 130.149.17.8 2 u 285 512 37 101.458
-190.45 85.706
+antares.speedne 217.11.227.683 u 285 512 37 137.773
-192.71 85.431
+cheddar.halon.o 129.240.64.3 3 u 282 512 37 76.770
-276.95 62.389
192.168.1.3.STEP. 16 u1 12800.0000.000
4000.00
server2 (192.168.1.3)
/etc/ntp.conf
server 0.pool.ntp.org
server 1.pool.ntp.org
server 2.pool.ntp.org
server pool.ntp.org
peer 192.168.1.2
restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap
logconfig =syncall +clockall +sysall
ntpq -p output
remote refid st t when poll reach delay offset
jitter
==
zirkon.biophys. 134.99.128.802 u 71 1287 94.189 -77.270
27.511
oubliette.mctav .MSF.1 u 70 1287 98.417 -38.531
16.505
antares.speedne 217.11.227.683 u 70 1287 136.851 -53.314
27.989
cteha.ulp.co.il 192.114.62.249 3 u5 1287 170.650 -52.706
17.982
192.168.1.2.DROP. 16 u- 6400.0000.000
4000.00
Any help getting this to work will be appreciated.
Chris
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
[EMAIL PROTECTED]
This has been resolved. I waslked away for about 7 hours and suddenly
it works. It just resolved itself.
Chris
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Pxeboot for nfs installation woes.
Hi all, I have a lot of servers on order, so I want to be able to just network boot them as a jumpstart into the installation (which will then be scripted). I am most of the way there. I have tested my NFS shares and if I boot a boxe off a cd, I can do the nfs installation without fail. I have setup pxeboot, and if I am far enough along that when I boot off the network, it tftp's the files it needs, boots through menus, loads the generic kernel, mounts an nfs root, then errors. The errors are exec /sbin/init: error 70. One error for each attempt at an init file. Then it gives me an init: not found in path /sbin/init:/sbin/oinit.. Then it panics and reboots. There is so much I've done, I'm not sure what specifics anyone might need to offer some assistance. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Pxeboot for nfs installation woes.
Erik Norgaard wrote: Christopher McGee wrote: Hi all, I have a lot of servers on order, so I want to be able to just network boot them as a jumpstart into the installation (which will then be scripted). I am most of the way there. I have tested my NFS shares and if I boot a boxe off a cd, I can do the nfs installation without fail. I have setup pxeboot, and if I am far enough along that when I boot off the network, it tftp's the files it needs, boots through menus, loads the generic kernel, mounts an nfs root, then errors. The errors are exec /sbin/init: error 70. One error for each attempt at an init file. Then it gives me an init: not found in path /sbin/init:/sbin/oinit.. Then it panics and reboots. There is so much I've done, I'm not sure what specifics anyone might need to offer some assistance. 1st: I have done it but with ftp install rather than nfs, see here: http://www.daemonsecurity.com/pxe/ I used no cd's to bootstrap or anything. 2nd: One of the first things done in the bootstrapping is to load the loader.conf, in this you can override any settings of paths to the init program. For installation usually sysinstall is used, which can be scripted - I assume you are refering to this? - you can set the path with an option in loader.conf, for example: init_path=/stand/sysinstall The option may contain a colon separated list of files and they are checked in order, the first found is run. Check the path to your init or sysinstall on the nfs-client. Cheers, Erik That is the how-to that I started with, however it jumps around a bit becaues they are also showing how to do diskless clients. Basically I have this: /tftpboot is a link to /usr/local/export/freebsd I have put the entire cd in /usr/local/export/freebsd copied pxeboot to /usr/local/export/freebsd setup nfsserver:/usr/local/export/freebsd as the root_path on the dhcp server. It appears to try to mount that share as the rootpath. the nfsserver is exporting /usr -alldirs After the kernel boots there is a line that says: NFS ROOT: 192.168.1.98:/usr/local/export/freebsd and then it errors. If that is path to the root of the cd, this should work correct? Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Anyone using blade servers???
Elliot Finley wrote: I'm looking for a blade server that will work with FreeBSD 5.x. Is anyone successfully using one? I would appreciate hearing about it. TIA Elliot ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] 3upsystems.com sales department told me yesterday they have FreeBSD support, and they can fit 12 blade servers in a 4u chassis, but they are a little hard on the wallet. Just not worth it for our company. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5 day lockup on Densitron
Richard J. Valenta wrote: First off - thank you for both your replies... The manufacturer (Densitron) has little info available, especially technological info. I'm going to continue to look for this, but do either of you or anyone else have ideas on where to look for this? Would it be called a 'watchdog' in the BIOS? Previous to this install there was a smaller hard disk and a Windows 2000 install. However, there was no regular reboot or anything else I knew of. Of course, who knows if there's some kind of base Windows 'stroker' that I'm unaware of, or if there was something in place that was part of the application it ran. Anyway - ideas on where to look, and subsequently disable, this (if its there)? Thanks again, Richard -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Clifton Royston Sent: Tuesday, May 10, 2005 12:39 AM To: RW Cc: freebsd-questions@freebsd.org Subject: Re: 5 day lockup on Densitron On Tue, May 10, 2005 at 04:30:15AM +0100, RW wrote: On Saturday 07 May 2005 02:00, Clifton Royston wrote: What you describe could conceivably be the result of a special counter or RTC chip running as a watchdog timer with a count-down from boot time, and generating some kind of special interrupt when that countdown reaches 0. Watchdog devices are sometimes set up to require the application software to stroke the timer periodically (reset it in software) with the intent to force a reset of the system (usually a reboot) after such-and-such a period of time if not stroked. Watchdog timeouts are typically a fraction of a minute, a 5 day watchdog timeout is very unlikely. Watchdogs are normally designed to be initialized at boot by the software, and as FreeBSD doesn't know about it... It's a long-shot, but less so than overheating always happening to build up and cause a reset randomly at exactly the same 5 day period of time as somebody suggested. -- Clifton I actually saw this same thing on 2 machines recently. I suggest either upgrading to 5.4(not sure if it will fix it), or reverting to 4.11. My company has not been able to justify putting any 5.3 boxes into production because they seem very unstable. In our case the lockups were random. Initially it was thought to be almost exactly every 2 days but later determined the lockups were random. I installed 4.11 on both of those machines and they have been up every since. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Stability problems with 5.3-Release
Christopher McGee wrote: Justin R. Pessa wrote: On Apr 21 05 06:22PM, Chris McGee wrote: I've got 2 identical boxes (Supermicro sys-6023P-8R) running with ZCR adaptec cards with 6 73Gig seagate scsi drives, 4 Gigs of ram, and dual 2.4 Ghz Xeons. Both of these machines are running 5.3-Release-p8. The usually run for a day, give or take, and then they crash. The just deadlock, no console response, no nothing. The get power cycled and they are fine for a little while again. These are configured to be mysql database servers. I can provide any information necessary, but i'm stumped and it's causing me a lot of heartache now. I've had similar problems as well. One thing I noticed is that a process may get hung in the D state and never returns. From there it seems the system enters a downward spiral and everything locks up. I've had this problem with p6 and p7. Attached is my dmesg output. Not sure if it's helpful... I can't offer anything in the form of a solution but figured I'd chime in so that Chris doesn't think he's the only (crazy) one with this problem! ;) Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] - j .__. | Justin R. Pessa - BOFH | www: http://jstn.sdf1.org | pgp: http://jstn.sdf1.org/pgp.html | irc: asdf @ irc.freenode.net ' Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-RELEASE-p7 #3: Thu Apr 21 13:24:51 EDT 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TWINTURBO Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 1700MHz (1707.56-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf0a Stepping = 10 Features=0x3febf9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM real memory = 268349440 (255 MB) avail memory = 257130496 (245 MB) npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: ASUS P4T on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0xe408-0xe40b on acpi0 cpu0: ACPI CPU (2 Cx states) on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82850 host to AGP bridge mem 0xf800-0xfbff at device 0.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) pcib2: ACPI PCI-PCI bridge at device 30.0 on pci0 pci2: ACPI PCI bus on pcib2 pcm0: Creative EMU10K1 port 0xd800-0xd81f irq 9 at device 6.0 on pci2 pcm0: SigmaTel STAC9708/11 AC97 Codec rl0: RealTek 8139 10/100BaseTX port 0xd000-0xd0ff mem 0xf180-0xf18000ff irq 9 at device 11.0 on pci2 miibus0: MII bus on rl0 rlphy0: RealTek internal media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:02:2a:b3:24:a0 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH2 UDMA100 controller port 0xb800-0xb80f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 uhci0: Intel 82801BA/BAM (ICH2) USB controller USB-A port 0xb400-0xb41f irq 9 at device 31.2 on pci0 uhci0: [GIANT-LOCKED] usb0: Intel 82801BA/BAM (ICH2) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ums0: KYE Genius USB Wheel Mouse, rev 1.00/0.00, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. pci0: serial bus, SMBus at device 31.3 (no driver attached) uhci1: Intel 82801BA/BAM (ICH2) USB controller USB-B port 0xb000-0xb01f irq 9 at device 31.4 on pci0 uhci1: [GIANT-LOCKED] usb1: Intel 82801BA/BAM (ICH2) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered fdc0: floppy drive controller port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: 1440-KB 3.5 drive on fdc0 drive 0 ppc0: ECP parallel printer port port 0x778-0x77a,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: Parallel port bus on ppc0 sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: 16550A-compatible COM port port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0
Re: Stability problems with 5.3-Release
Justin R. Pessa wrote: On Apr 21 05 06:22PM, Chris McGee wrote: I've got 2 identical boxes (Supermicro sys-6023P-8R) running with ZCR adaptec cards with 6 73Gig seagate scsi drives, 4 Gigs of ram, and dual 2.4 Ghz Xeons. Both of these machines are running 5.3-Release-p8. The usually run for a day, give or take, and then they crash. The just deadlock, no console response, no nothing. The get power cycled and they are fine for a little while again. These are configured to be mysql database servers. I can provide any information necessary, but i'm stumped and it's causing me a lot of heartache now. I've had similar problems as well. One thing I noticed is that a process may get hung in the D state and never returns. From there it seems the system enters a downward spiral and everything locks up. I've had this problem with p6 and p7. Attached is my dmesg output. Not sure if it's helpful... I can't offer anything in the form of a solution but figured I'd chime in so that Chris doesn't think he's the only (crazy) one with this problem! ;) Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] - j .__. | Justin R. Pessa - BOFH | www: http://jstn.sdf1.org | pgp: http://jstn.sdf1.org/pgp.html | irc: asdf @ irc.freenode.net ' Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-RELEASE-p7 #3: Thu Apr 21 13:24:51 EDT 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TWINTURBO Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 1700MHz (1707.56-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf0a Stepping = 10 Features=0x3febf9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM real memory = 268349440 (255 MB) avail memory = 257130496 (245 MB) npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: ASUS P4T on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0xe408-0xe40b on acpi0 cpu0: ACPI CPU (2 Cx states) on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82850 host to AGP bridge mem 0xf800-0xfbff at device 0.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) pcib2: ACPI PCI-PCI bridge at device 30.0 on pci0 pci2: ACPI PCI bus on pcib2 pcm0: Creative EMU10K1 port 0xd800-0xd81f irq 9 at device 6.0 on pci2 pcm0: SigmaTel STAC9708/11 AC97 Codec rl0: RealTek 8139 10/100BaseTX port 0xd000-0xd0ff mem 0xf180-0xf18000ff irq 9 at device 11.0 on pci2 miibus0: MII bus on rl0 rlphy0: RealTek internal media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:02:2a:b3:24:a0 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH2 UDMA100 controller port 0xb800-0xb80f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 uhci0: Intel 82801BA/BAM (ICH2) USB controller USB-A port 0xb400-0xb41f irq 9 at device 31.2 on pci0 uhci0: [GIANT-LOCKED] usb0: Intel 82801BA/BAM (ICH2) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ums0: KYE Genius USB Wheel Mouse, rev 1.00/0.00, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. pci0: serial bus, SMBus at device 31.3 (no driver attached) uhci1: Intel 82801BA/BAM (ICH2) USB controller USB-B port 0xb000-0xb01f irq 9 at device 31.4 on pci0 uhci1: [GIANT-LOCKED] usb1: Intel 82801BA/BAM (ICH2) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered fdc0: floppy drive controller port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: 1440-KB 3.5 drive on fdc0 drive 0 ppc0: ECP parallel printer port port 0x778-0x77a,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: Parallel port bus on ppc0 sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: 16550A-compatible COM port port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] orm0: ISA Option ROMs
pf and altq bandwidth problem.
I apologize if this is the wrong list for this, but if it is, please let
me know. Basically when queue1 on my firewall starts pushing the full
amount of bandwidth, things that use the dflt queue become unreachable
or VERY slow. The dflt queue NEVER uses it's full amount of bandwidth,
generally around 3mbit/s on average. I'm starting to think this is just
an inherent problem in FreeBSD 5.3. Maybe I just need to upgrade to 5.4
when it is released, but I don't think there were many pf updates in
that release. I'm reluctant to post too much information about the
firewall and it's configuration since it is a production firewall. But
the problem seems to be with the queues. Here's what I think is the
relevant information, let me know if more information is needed:
firewall# pfctl -s queue
queue root_fxp0 bandwidth 25Mb priority 0 cbq( wrr root ) {dflt, queue1}
queue dflt bandwidth 8Mb priority 4 qlimit 150 cbq( borrow default )
queue queue1 bandwidth 17Mb qlimit 3500
firewall# pfctl -vvsq
queue root_fxp0 bandwidth 25Mb priority 0 cbq( wrr root ) {dflt, queue1}
[ pkts: 93469435 bytes: 57111963278 dropped pkts: 0
bytes: 0 ]
[ qlength: 0/ 50 borrows: 0 suspends: 0 ]
queue dflt bandwidth 8Mb priority 4 qlimit 150 cbq( borrow default )
[ pkts: 47160837 bytes: 20420146684 dropped pkts:294 bytes:
105068 ]
[ qlength: 0/150 borrows: 2667554 suspends:237 ]
queue queue1 bandwidth 12Mb qlimit 3500
[ pkts: 46308598 bytes: 36691816594 dropped pkts: 5236343 bytes:
4887084090 ]
[ qlength: 0/3500 borrows: 0 suspends: 13971654 ]
queue root_fxp0 bandwidth 25Mb priority 0 cbq( wrr root ) {dflt, queue1}
[ pkts: 93472817 bytes: 57113671748 dropped pkts: 0
bytes: 0 ]
[ qlength: 0/ 50 borrows: 0 suspends: 0 ]
[ measured: 676.4 packets/s, 2.73Mb/s ]
queue dflt bandwidth 8Mb priority 4 qlimit 150 cbq( borrow default )
[ pkts: 47163588 bytes: 20421636153 dropped pkts:294 bytes:
105068 ]
[ qlength: 0/150 borrows: 2667640 suspends:237 ]
[ measured: 550.2 packets/s, 2.38Mb/s ]
queue queue1 bandwidth 12Mb qlimit 3500
[ pkts: 46309229 bytes: 36692035595 dropped pkts: 5236343 bytes:
4887084090 ]
[ qlength: 0/3500 borrows: 0 suspends: 13971654 ]
[ measured: 126.2 packets/s, 350.40Kb/s ]
queue root_fxp0 bandwidth 25Mb priority 0 cbq( wrr root ) {dflt, queue1}
[ pkts: 93475932 bytes: 57115159111 dropped pkts: 0
bytes: 0 ]
[ qlength: 0/ 50 borrows: 0 suspends: 0 ]
[ measured: 649.7 packets/s, 2.56Mb/s ]
queue dflt bandwidth 8Mb priority 4 qlimit 150 cbq( borrow default )
[ pkts: 47166144 bytes: 20422995656 dropped pkts:294 bytes:
105068 ]
[ qlength: 0/150 borrows: 2667788 suspends:237 ]
[ measured: 530.7 packets/s, 2.28Mb/s ]
queue queue1 bandwidth 12Mb qlimit 3500
[ pkts: 46309788 bytes: 36692163455 dropped pkts: 5236343 bytes:
4887084090 ]
[ qlength: 0/3500 borrows: 0 suspends: 13971657 ]
[ measured: 119.0 packets/s, 277.49Kb/s ]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pf and altq bandwidth problem.
Christopher McGee wrote:
I apologize if this is the wrong list for this, but if it is, please
let me know. Basically when queue1 on my firewall starts pushing the
full amount of bandwidth, things that use the dflt queue become
unreachable or VERY slow. The dflt queue NEVER uses it's full amount
of bandwidth, generally around 3mbit/s on average. I'm starting to
think this is just an inherent problem in FreeBSD 5.3. Maybe I just
need to upgrade to 5.4 when it is released, but I don't think there
were many pf updates in that release. I'm reluctant to post too much
information about the firewall and it's configuration since it is a
production firewall. But the problem seems to be with the queues.
Here's what I think is the relevant information, let me know if more
information is needed:
firewall# pfctl -s queue
queue root_fxp0 bandwidth 25Mb priority 0 cbq( wrr root ) {dflt, queue1}
queue dflt bandwidth 8Mb priority 4 qlimit 150 cbq( borrow default )
queue queue1 bandwidth 17Mb qlimit 3500
firewall# pfctl -vvsq
queue root_fxp0 bandwidth 25Mb priority 0 cbq( wrr root ) {dflt, queue1}
[ pkts: 93469435 bytes: 57111963278 dropped pkts: 0
bytes: 0 ]
[ qlength: 0/ 50 borrows: 0 suspends: 0 ]
queue dflt bandwidth 8Mb priority 4 qlimit 150 cbq( borrow default )
[ pkts: 47160837 bytes: 20420146684 dropped pkts:294 bytes:
105068 ]
[ qlength: 0/150 borrows: 2667554 suspends:237 ]
queue queue1 bandwidth 12Mb qlimit 3500
[ pkts: 46308598 bytes: 36691816594 dropped pkts: 5236343 bytes:
4887084090 ]
[ qlength: 0/3500 borrows: 0 suspends: 13971654 ]
queue root_fxp0 bandwidth 25Mb priority 0 cbq( wrr root ) {dflt, queue1}
[ pkts: 93472817 bytes: 57113671748 dropped pkts: 0
bytes: 0 ]
[ qlength: 0/ 50 borrows: 0 suspends: 0 ]
[ measured: 676.4 packets/s, 2.73Mb/s ]
queue dflt bandwidth 8Mb priority 4 qlimit 150 cbq( borrow default )
[ pkts: 47163588 bytes: 20421636153 dropped pkts:294 bytes:
105068 ]
[ qlength: 0/150 borrows: 2667640 suspends:237 ]
[ measured: 550.2 packets/s, 2.38Mb/s ]
queue queue1 bandwidth 12Mb qlimit 3500
[ pkts: 46309229 bytes: 36692035595 dropped pkts: 5236343 bytes:
4887084090 ]
[ qlength: 0/3500 borrows: 0 suspends: 13971654 ]
[ measured: 126.2 packets/s, 350.40Kb/s ]
queue root_fxp0 bandwidth 25Mb priority 0 cbq( wrr root ) {dflt, queue1}
[ pkts: 93475932 bytes: 57115159111 dropped pkts: 0
bytes: 0 ]
[ qlength: 0/ 50 borrows: 0 suspends: 0 ]
[ measured: 649.7 packets/s, 2.56Mb/s ]
queue dflt bandwidth 8Mb priority 4 qlimit 150 cbq( borrow default )
[ pkts: 47166144 bytes: 20422995656 dropped pkts:294 bytes:
105068 ]
[ qlength: 0/150 borrows: 2667788 suspends:237 ]
[ measured: 530.7 packets/s, 2.28Mb/s ]
queue queue1 bandwidth 12Mb qlimit 3500
[ pkts: 46309788 bytes: 36692163455 dropped pkts: 5236343 bytes:
4887084090 ]
[ qlength: 0/3500 borrows: 0 suspends: 13971657 ]
[ measured: 119.0 packets/s, 277.49Kb/s ]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
[EMAIL PROTECTED]
Let me add a little more information I thought might be useful. This
firewall has intel pro 100+ cards, actually 6 of them. Only 2 are in
use, the others are there for some future projects. The public
interface has 1 public IP from a /29. The private interface has 2 IP
addresses that correspond with the 2 internal class C's we have(both
publicly routable). I have tried choking queue1 to 12Mb at some point
and it seemed to alleviate some of the problems, although some internal
servers still respond VERY slowly when it peaks.
Thanks,
Chris
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Stability problems with 5.3-Release
Chad Leigh -- Shire.Net LLC wrote: On Apr 21, 2005, at 4:22 PM, Chris McGee wrote: I've got 2 identical boxes (Supermicro sys-6023P-8R) running with ZCR adaptec cards with 6 73Gig seagate scsi drives, 4 Gigs of ram, and dual 2.4 Ghz Xeons. Both of these machines are running 5.3-Release-p8. The usually run for a day, give or take, and then they crash. The just deadlock, no console response, no nothing. The get power cycled and they are fine for a little while again. These are configured to be mysql database servers. I can provide any information necessary, but i'm stumped and it's causing me a lot of heartache now. What were they running before -p8 ? And were you having similar problems? Chad Unfortunately, nothing. These were brand new boxes, installed 5.3 from cd, cvsup'd to latest 5.3-Release, and starting installing the few ports we needed. I can't go to an RC. The higher powers won't allow running anything but a full release. It was a pretty big hassle even implementing 5.3 vs 4.x. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports
Paul Schmehl wrote: - Original Message - From: Erik Norgaard [EMAIL PROTECTED] To: Paul Schmehl [EMAIL PROTECTED] Cc: Grant Peel [EMAIL PROTECTED]; freebsd-questions@freebsd.org Sent: Sunday, February 13, 2005 2:43 PM Subject: Re: Ports Taking an arbitrary post, it appears that make.conf is not always the best place since this sets options globally. But thanks, I have now learned how to get my ports compiled with support for a4 paper and _not_ letter :-) While that is true, you can also set options for individual ports. Paul Schmehl ([EMAIL PROTECTED]) Adjunct Information Security Officer The University of Texas at Dallas AVIEN Founding Member http://www.utdallas.edu/~pauls/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Could you please give some detail about setting options for individual ports in make.conf? Maybe I missed something in 'man make.conf' or 'man ports' but everything seems to refer to global options. The only example I've found is in man portmanager, but I'm still a little unsure about the how to do it properly. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Dynamic IP and pf?
I have a cable modem that provides a dynamic IP address to the outside interface of my firewall(5.3 with PF doing NAT). If my IP address changes I have to run a script to update my dynamic dns and reload my firewall rules based on the new IP address. Is there a recommended way of doing this other than having cron check to see if the IP addresss has changed? Thanks, Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dynamic IP and pf?
Saad Kadhi wrote: On 14/01/2005 20:39 Christopher McGee wrote: I have a cable modem that provides a dynamic IP address to the outside interface of my firewall(5.3 with PF doing NAT). If my IP address changes I have to run a script to update my dynamic dns and reload my firewall rules based on the new IP address. Is there a recommended way of doing this other than having cron check to see if the IP addresss has changed? the PF version integrated into 5.3 supports dynamic IPs by putting parentheses around the interface name as explained in http://www.openbsd.org/faq/pf/filter.html : excerpt The name of a network interface in parentheses ( ). This tells PF to update the rule if the IP address(es) on the named interface change. This is useful on an interface that gets its IP address via DHCP or dial-up as the ruleset doesn't have to be reloaded each time the address changes. /excerpt for example : my_if=hme0 [...] nat on $my_if proto tcp from any to any - ($my_if) [...] pass in quick on $my_if proto tcp from any to ($my_if) port domain flags S/SAFR keep state I have setup my pf ruleset using the parentheses. I didn't realize it would auto update them. I thought I would still need to reload the rules so that it re-reads the interface IP. I still have the dilemma of dynamic dns and a couple of other scripts that I run, based on the IP, that will require being run if the IP ever changes. I'm thinking there should be something I can do in /etc/dhclient.conf maybe to run them? Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
