(ipfw, natd, sendmail) FreeBSD 6.1 виснет ??? какое-то время (от 1-го часа до 2-х день) работает и напроч виснет, на экране останавливается заставка, на клаву не реагирует.
что может быть?
как проверить из за чего?
да кстати, железка старая,
celeron 466
RAM 256я кода все поставил две недели поработало и этот феерверг начался
плиз помогите, мож кто знает что делать?
>(ipfw, natd, sendmail) FreeBSD 6.1 виснет ??? какое-то время (от 1-го часа
>до 2-х день) работает и напроч виснет, на экране останавливается заставка,
>на клаву не реагирует.
>что может быть?
>как проверить из за чего?Как насчёт заполнености раздела /tmp.
Была подобная ситауция. Очень было неприятно.
>Как насчёт заполнености раздела /tmp.
>Была подобная ситауция. Очень было неприятно.Размер 496 MB / Свободно 457 MB
вроде с местом свободным ок!
>
>>Как насчёт заполнености раздела /tmp.
>>Была подобная ситауция. Очень было неприятно.
>
>Размер 496 MB / Свободно 457 MB
>
>вроде с местом свободным ок!
А что логи говорять, а??
>(ipfw, natd, sendmail) FreeBSD 6.1 виснет ??? какое-то время (от 1-го часа
>до 2-х день) работает и напроч виснет, на экране останавливается заставка,
>на клаву не реагирует.
>что может быть?
>как проверить из за чего?Вероятно проблема с железом. После загрузки посмотри dmesg -a на наличие подозрительных строк о неработающем или сбойном оборудовании или отсутствии драйверов. А также просмотри /var/log/messages
Если же с оборудование всё нормально, то возможно ядро собрано с неверными или лишними настройками, или же сбоит какой-либо KLD-модуль.
Ну или на крайний случай ошибка в каком либо софте. Хотя трудно себе представить такую ошибку, которая просто намертво вешает фряху из юзерленда. Ну по крайней мере в моей практике такие бывали нечасто и практически все они были связаны с X-ами.
>
>Вероятно проблема с железом. После загрузки посмотри dmesg -a на наличие подозрительных
>строк о неработающем или сбойном оборудовании или отсутствии драйверов. А также
>просмотри /var/log/messages
>Если же с оборудование всё нормально, то возможно ядро собрано с неверными
>или лишними настройками, или же сбоит какой-либо KLD-модуль.
>Ну или на крайний случай ошибка в каком либо софте. Хотя трудно
>себе представить такую ошибку, которая просто намертво вешает фряху из юзерленда.
>Ну по крайней мере в моей практике такие бывали нечасто и
>практически все они были связаны с X-ами.------------------------------------------------------------
ЯДРО
------------------------------------------------------------
machine i386
cpu I486_CPU
cpu I586_CPU
cpu I686_CPU
ident FIRST# To statically compile in device wiring instead of /boot/device.hints
#hints "GENERIC.hints" # Default places to look for devices.makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols
#options SCHED_ULE # ULE scheduler
options SCHED_4BSD # 4BSD scheduler
options PREEMPTION # Enable kernel thread preemption
options INET # InterNETworking
options INET6 # IPv6 communications protocols
options FFS # Berkeley Fast Filesystem
options SOFTUPDATES # Enable FFS soft updates support
options UFS_ACL # Support for access control lists
options UFS_DIRHASH # Improve performance on big directories
options MD_ROOT # MD is a potential root device
options NFSCLIENT # Network Filesystem Client
options NFSSERVER # Network Filesystem Server
options NFS_ROOT # NFS usable as /, requires NFSCLIENT
options MSDOSFS # MSDOS Filesystem
options CD9660 # ISO 9660 Filesystem
options PROCFS # Process filesystem (requires PSEUDOFS)
options PSEUDOFS # Pseudo-filesystem framework
options GEOM_GPT # GUID Partition Tables.
options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!]
options COMPAT_FREEBSD4 # Compatible with FreeBSD4
options COMPAT_FREEBSD5 # Compatible with FreeBSD5
options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI
options KTRACE # ktrace(1) support
options SYSVSHM # SYSV-style shared memory
options SYSVMSG # SYSV-style message queues
options SYSVSEM # SYSV-style semaphores
options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions
options KBD_INSTALL_CDEV # install a CDEV entry in /dev
options AHC_REG_PRETTY_PRINT # Print register bitfields in debug
# output. Adds ~128k to driver.
options AHD_REG_PRETTY_PRINT # Print register bitfields in debug
# output. Adds ~215k to driver.
options ADAPTIVE_GIANT # Giant mutex is adaptive.device apic # I/O APIC
# Bus support.
device eisa
device pci# Floppy drives
device fdc# ATA and ATAPI devices
device ata
device atadisk # ATA disk drives
device ataraid # ATA RAID drives
device atapicd # ATAPI CDROM drives
device atapifd # ATAPI floppy drives
device atapist # ATAPI tape drives
options ATA_STATIC_ID # Static device numbering# SCSI Controllers
device ahb # EISA AHA1742 family
device ahc # AHA2940 and onboard AIC7xxx devices
device ahd # AHA39320/29320 and onboard AIC79xx devices
device amd # AMD 53C974 (Tekram DC-390(T))
device isp # Qlogic family
#device ispfw # Firmware for QLogic HBAs- normally a module
device mpt # LSI-Logic MPT-Fusion
#device ncr # NCR/Symbios Logic
device sym # NCR/Symbios Logic (newer chipsets + those of `ncr')
device trm # Tekram DC395U/UW/F DC315U adaptersdevice adv # Advansys SCSI adapters
device adw # Advansys wide SCSI adapters
device aha # Adaptec 154x SCSI adapters
device aic # Adaptec 15[012]x SCSI adapters, AIC-6[23]60.
device bt # Buslogic/Mylex MultiMaster SCSI adaptersdevice ncv # NCR 53C500
device nsp # Workbit Ninja SCSI-3
device stg # TMC 18C30/18C50# SCSI peripherals
device scbus # SCSI bus (required for SCSI)
device ch # SCSI media changers
device da # Direct Access (disks)
device sa # Sequential Access (tape etc)
device cd # CD
device pass # Passthrough device (direct SCSI access)
device ses # SCSI Environmental Services (and SAF-TE)# RAID controllers interfaced to the SCSI subsystem
device amr # AMI MegaRAID
device arcmsr # Areca SATA II RAID
device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID
device ciss # Compaq Smart RAID 5*
device dpt # DPT Smartcache III, IV - See NOTES for options
device hptmv # Highpoint RocketRAID 182x
device rr232x # Highpoint RocketRAID 232x
device iir # Intel Integrated RAID
device ips # IBM (Adaptec) ServeRAID
device mly # Mylex AcceleRAID/eXtremeRAID
device twa # 3ware 9000 series PATA/SATA RAID# RAID controllers
device aac # Adaptec FSA RAID
device aacp # SCSI passthrough for aac (requires CAM)
device ida # Compaq Smart RAID
device mfi # LSI MegaRAID SAS
device mlx # Mylex DAC960 family
device pst # Promise Supertrak SX6000
device twe # 3ware ATA RAID# atkbdc0 controls both the keyboard and the PS/2 mouse
device atkbdc # AT keyboard controller
device atkbd # AT keyboard
device psm # PS/2 mousedevice kbdmux # keyboard multiplexer
device vga # VGA video card driver
device splash # Splash screen and screen saver support
# syscons is the default console driver, resembling an SCO console
device sc# Enable this for the pcvt (VT220 compatible) console driver
#device vt
#options XSERVER # support for X server on a vt console
#options FAT_CURSOR # start with block cursordevice agp # support several AGP chipsets
# Power management support (see NOTES for more options)
#device apm
# Add suspend/resume support for the i8254.
device pmtimer# PCCARD (PCMCIA) support
# PCMCIA and cardbus bridge support
device cbb # cardbus (yenta) bridge
device pccard # PC Card (16-bit) bus
device cardbus # CardBus (32-bit) bus# Serial (COM) ports
device sio # 8250, 16[45]50 based serial ports# Parallel port
device ppc
device ppbus # Parallel port bus (required)
device lpt # Printer
device plip # TCP/IP over parallel
device ppi # Parallel port interface device
#device vpo # Requires scbus and da# If you've got a "dumb" serial or parallel PCI card that is
# supported by the puc(4) glue driver, uncomment the following
# line to enable it (connects to the sio and/or ppc drivers):
#device puc# PCI Ethernet NICs.
device de # DEC/Intel DC21x4x (``Tulip'')
device em # Intel PRO/1000 adapter Gigabit Ethernet Card
device ixgb # Intel PRO/10GbE Ethernet Card
device txp # 3Com 3cR990 (``Typhoon'')
device vx # 3Com 3c590, 3c595 (``Vortex'')# PCI Ethernet NICs that use the common MII bus controller code.
# NOTE: Be sure to keep the 'device miibus' line in order to use these NICs!
device miibus # MII bus support
device bce # Broadcom BCM5706/BCM5708 Gigabit Ethernet
device bfe # Broadcom BCM440x 10/100 Ethernet
device bge # Broadcom BCM570xx Gigabit Ethernet
device dc # DEC/Intel 21143 and various workalikes
device fxp # Intel EtherExpress PRO/100B (82557, 82558)
device lge # Level 1 LXT1001 gigabit Ethernet
device nge # NatSemi DP83820 gigabit Ethernet
device nve # nVidia nForce MCP on-board Ethernet Networking
device pcn # AMD Am79C97x PCI 10/100(precedence over 'lnc')
device re # RealTek 8139C+/8169/8169S/8110S
device rl # RealTek 8129/8139
device sf # Adaptec AIC-6915 (``Starfire'')
device sis # Silicon Integrated Systems SiS 900/SiS 7016
device sk # SysKonnect SK-984x & SK-982x gigabit Ethernet
device ste # Sundance ST201 (D-Link DFE-550TX)
device ti # Alteon Networks Tigon I/II gigabit Ethernet
device tl # Texas Instruments ThunderLAN
device tx # SMC EtherPower II (83c170 ``EPIC'')
device vge # VIA VT612x gigabit Ethernet
device vr # VIA Rhine, Rhine II
device wb # Winbond W89C840F
device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'')# ISA Ethernet NICs. pccard NICs included.
device cs # Crystal Semiconductor CS89x0 NIC
# 'device ed' requires 'device miibus'
device ed # NE[12]000, SMC Ultra, 3c503, DS8390 cards
device ex # Intel EtherExpress Pro/10 and Pro/10+
device ep # Etherlink III based cards
device fe # Fujitsu MB8696x based cards
device ie # EtherExpress 8/16, 3C507, StarLAN 10 etc.
device lnc # NE2100, NE32-VL Lance Ethernet cards
device sn # SMC's 9000 series of Ethernet chips
device xe # Xircom pccard Ethernet# Wireless NIC cards
device wlan # 802.11 support
device an # Aironet 4500/4800 802.11 wireless NICs.
device awi # BayStack 660 and others
device ral # Ralink Technology RT2500 wireless NICs.
device wi # WaveLAN/Intersil/Symbol 802.11 wireless NICs.
#device wl # Older non 802.11 Wavelan wireless NIC.# Pseudo devices.
device loop # Network loopback
device random # Entropy device
device ether # Ethernet support
device sl # Kernel SLIP
device ppp # Kernel PPP
device tun # Packet tunnel.
device pty # Pseudo-ttys (telnet etc)
device md # Memory "disks"
device gif # IPv6 and IPv4 tunneling
device faith # IPv6-to-IPv4 relaying (translation)# The `bpf' device enables the Berkeley Packet Filter.
# Be aware of the administrative consequences of enabling this!
# Note that 'bpf' is required for DHCP.
device bpf # Berkeley packet filter# USB support
device uhci # UHCI PCI->USB interface
device ohci # OHCI PCI->USB interface
device ehci # EHCI PCI->USB interface (USB 2.0)
device usb # USB Bus (required)
#device udbp # USB Double Bulk Pipe devices
device ugen # Generic
device uhid # "Human Interface Devices"
device ukbd # Keyboard
device ulpt # Printer
device umass # Disks/Mass storage - Requires scbus and da
device ums # Mouse
device ural # Ralink Technology RT2500USB wireless NICs
device urio # Diamond Rio 500 MP3 player
device uscanner # Scanners
# USB Ethernet, requires miibus
device aue # ADMtek USB Ethernet
device axe # ASIX Electronics USB Ethernet
device cdce # Generic USB over Ethernet
device cue # CATC USB Ethernet
device kue # Kawasaki LSI USB Ethernet
device rue # RealTek RTL8150 USB Ethernet# FireWire support
device firewire # FireWire bus code
device sbp # SCSI over FireWire (Requires scbus and da)
device fwe # Ethernet over FireWire (non-standard!)options IPFIREWALL
options IPFIREWALL_VERBOSE
options IPFIREWALL_VERBOSE_LIMIT=10
options IPDIVERT
options IPFIREWALL_DEFAULT_TO_ACCEPT
А господи.. что в логах до зависания и после перезагрузки написано?dmesg,maessages,maillog,debug.
>А господи.. что в логах до зависания и после перезагрузки написано?
>-----------------------------------------
>dmesg,
arp: 192.168.0.75 is on rl0 but got reply from 00:0d:61:80:ff:60 on vr0
arp: 192.168.0.75 is on rl0 but got reply from 00:0d:61:80:ff:60 on vr0
arp: 192.168.0.75 is on rl0 but got reply from 00:0d:61:80:ff:60 on vr0
arp: 192.168.0.75 is on rl0 but got reply from 00:0d:61:80:ff:60 on vr0
arp: 192.168.0.75 is on rl0 but got reply from 00:0d:61:80:ff:60 on vr0
arp: 192.168.0.75 is on rl0 but got reply from 00:0d:61:80:ff:60 on vr0
arp: 192.168.0.75 is on rl0 but got reply from 00:0d:61:80:ff:60 on vr0
arp: 192.168.0.75 is on rl0 but got reply from 00:0d:61:80:ff:60 on vr0
arp: 192.168.0.75 is on rl0 but got reply from 00:0d:61:80:ff:60 on vr0
arp: 192.168.0.75 is on rl0 but got reply from 00:0d:61:80:ff:60 on vr0
arp: 192.168.0.75 is on rl0 but got reply from 00:0d:61:80:ff:60 on vr0
arp: 192.168.0.75 is on rl0 but got reply from 00:0d:61:80:ff:60 on vr0
arp: 192.168.0.75 is on rl0 but got reply from 00:0d:61:80:ff:60 on vr0и.т.д. (но это я не думаю что причина)
-------------------------------------------------в maillog тоже все в порядке
----------------------------------------------------------
debug
Sep 22 16:18:54 volgograd qpopper[1583]: (v4.0.8) Unable to get canonical name of client 192.168.0.70: hostname nor servname provided, or not known (8)
Sep 22 16:18:54 volgograd qpopper[1583]: (v4.0.8) Servicing request from "192.168.0.70" at 192.168.0.70
Sep 22 16:19:16 volgograd qpopper[1584]: (v4.0.8) Unable to get canonical name of client 192.168.0.64: hostname nor servname provided, or not known (8)
Sep 22 16:19:16 volgograd qpopper[1584]: (v4.0.8) Servicing request from "192.168.0.64" at 192.168.0.64
Sep 22 16:19:20 volgograd qpopper[1585]: (v4.0.8) Unable to get canonical name of client 192.168.0.56: hostname nor servname provided, or not known (8)
Sep 22 16:19:20 volgograd qpopper[1585]: (v4.0.8) Servicing request from "192.168.0.56" at 192.168.0.56-----------------------------------------------------------
maessages
Sep 22 14:20:15 volgograd syslogd: kernel boot file is /boot/kernel/kernel
Sep 22 14:20:15 volgograd kernel: Copyright (c) 1992-2006 The FreeBSD Project.
Sep 22 14:20:15 volgograd kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Sep 22 14:20:15 volgograd kernel: The Regents of the University of California. All rights reserved.
Sep 22 14:20:15 volgograd kernel: FreeBSD 6.1-RELEASE #0: Mon Aug 28 11:45:35 MSD 2006
Sep 22 14:20:15 volgograd kernel: root@volgograd.borodino.biz:/usr/src/sys/i386/compile/FIRST
Sep 22 14:20:15 volgograd kernel: Timecounter "i8254" frequency 1193182 Hz quality 0
Sep 22 14:20:15 volgograd kernel: CPU: Pentium II/Pentium II Xeon/Celeron (469.65-MHz 686-class CPU)
Sep 22 14:20:15 volgograd kernel: Origin = "GenuineIntel" Id = 0x665 Stepping = 5
Sep 22 14:20:15 volgograd kernel: Features=0x183f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR>
Sep 22 14:20:15 volgograd kernel: real memory = 267386880 (255 MB)
Sep 22 14:20:15 volgograd kernel: avail memory = 252182528 (240 MB)
Sep 22 14:20:15 volgograd kernel: kbd1 at kbdmux0
Sep 22 14:20:15 volgograd kernel: cpu0 on motherboard
Sep 22 14:20:15 volgograd kernel: pcib0: <Intel 82810 (i810 GMCH) Host To Hub bridge> pcibus 0 on motherboard
Sep 22 14:20:15 volgograd kernel: pir0: <PCI Interrupt Routing Table: 8 Entries> on motherboard
Sep 22 14:20:15 volgograd kernel: pci0: <PCI bus> on pcib0
Sep 22 14:20:15 volgograd kernel: agp0: <Intel 82810 (i810 GMCH) SVGA controller> mem 0xe8000000-0xebffffff,0xeff80000-0xefffffff irq 11 at device 1.0 on pci0
Sep 22 14:20:15 volgograd kernel: pcib1: <PCIBIOS PCI-PCI bridge> at device 30.0 on pci0
Sep 22 14:20:15 volgograd kernel: pci1: <PCI bus> on pcib1
Sep 22 14:20:15 volgograd kernel: rl0: <RealTek 8139 10/100BaseTX> port 0xcc00-0xccff mem 0xefdfff00-0xefdfffff irq 10 at device 11.0 on pci1
Sep 22 14:20:15 volgograd kernel: miibus0: <MII bus> on rl0
Sep 22 14:20:15 volgograd kernel: rlphy0: <RealTek internal media interface> on miibus0
Sep 22 14:20:15 volgograd kernel: rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
Sep 22 14:20:15 volgograd kernel: rl0: Ethernet address: 00:c0:26:31:cc:17
Sep 22 14:20:15 volgograd kernel: vr0: <VIA VT6105 Rhine III 10/100BaseTX> port 0xc800-0xc8ff mem 0xefdffe00-0xefdffeff irq 9 at device 15.0 on pci1
Sep 22 14:20:15 volgograd kernel: miibus1: <MII bus> on vr0
Sep 22 14:20:15 volgograd kernel: ukphy0: <Generic IEEE 802.3u media interface> on miibus1
Sep 22 14:20:15 volgograd kernel: ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
Sep 22 14:20:15 volgograd kernel: vr0: Ethernet address: 00:13:46:64:00:1b
Sep 22 14:20:15 volgograd kernel: isab0: <PCI-ISA bridge> at device 31.0 on pci0
Sep 22 14:20:15 volgograd kernel: isa0: <ISA bus> on isab0
Sep 22 14:20:15 volgograd kernel: atapci0: <Intel ICH UDMA66 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on pci0
Sep 22 14:20:15 volgograd kernel: ata0: <ATA channel 0> on atapci0
Sep 22 14:20:15 volgograd kernel: ata1: <ATA channel 1> on atapci0
Sep 22 14:20:15 volgograd kernel: pmtimer0 on isa0
Sep 22 14:20:15 volgograd kernel: orm0: <ISA Option ROM> at iomem 0xc0000-0xc7fff on isa0
Sep 22 14:20:15 volgograd kernel: atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
Sep 22 14:20:15 volgograd kernel: atkbd0: <AT Keyboard> irq 1 on atkbdc0
Sep 22 14:20:15 volgograd kernel: kbd0 at atkbd0
Sep 22 14:20:15 volgograd kernel: atkbd0: [GIANT-LOCKED]
Sep 22 14:20:15 volgograd kernel: fdc0: <Enhanced floppy controller> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
Sep 22 14:20:15 volgograd kernel: fdc0: [FAST]
Sep 22 14:20:15 volgograd kernel: ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
Sep 22 14:20:15 volgograd kernel: ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
Sep 22 14:20:15 volgograd kernel: ppbus0: <Parallel port bus> on ppc0
Sep 22 14:20:15 volgograd kernel: plip0: <PLIP network interface> on ppbus0
Sep 22 14:20:15 volgograd kernel: lpt0: <Printer> on ppbus0
Sep 22 14:20:15 volgograd kernel: lpt0: Interrupt-driven port
Sep 22 14:20:15 volgograd kernel: ppi0: <Parallel I/O> on ppbus0
Sep 22 14:20:15 volgograd kernel: sc0: <System console> at flags 0x100 on isa0
Sep 22 14:20:15 volgograd kernel: sc0: VGA <16 virtual consoles, flags=0x300>
Sep 22 14:20:15 volgograd kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
Sep 22 14:20:15 volgograd kernel: sio0: type 16550A
Sep 22 14:20:15 volgograd kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0
Sep 22 14:20:15 volgograd kernel: sio1: type 16550A
Sep 22 14:20:15 volgograd kernel: vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Sep 22 14:20:15 volgograd kernel: unknown: <PNP0c01> can't assign resources (memory)
Sep 22 14:20:15 volgograd kernel: unknown: <PNP0303> can't assign resources (port)
Sep 22 14:20:15 volgograd kernel: unknown: <PNP0501> can't assign resources (port)
Sep 22 14:20:15 volgograd kernel: unknown: <PNP0501> can't assign resources (port)
Sep 22 14:20:15 volgograd kernel: unknown: <PNP0400> can't assign resources (port)
Sep 22 14:20:15 volgograd kernel: unknown: <PNP0700> can't assign resources (port)
Sep 22 14:20:15 volgograd kernel: Timecounter "TSC" frequency 469652276 Hz quality 800
Sep 22 14:20:15 volgograd kernel: Timecounters tick every 1.000 msec
Sep 22 14:20:15 volgograd kernel: ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled, default to accept, logging limited to 10 packets/entry by default
Sep 22 14:20:15 volgograd kernel: ad0: 38203MB <SAMSUNG SP0411N TW100-13> at ata0-master UDMA66
Sep 22 14:20:15 volgograd kernel: acd0: CDROM <ATAPI-CD ROM-DRIVE-52MAX/Ver 52PP> at ata1-slave UDMA33
Sep 22 14:20:15 volgograd kernel: Trying to mount root from ufs:/dev/ad0s1a
Sep 22 14:20:15 volgograd kernel: rl0: link state changed to UP
Sep 22 14:20:15 volgograd routed[286]: sendto(rl0, 224.0.0.2): Permission denied
Sep 22 14:20:17 volgograd kernel: arp: 192.168.0.71 is on rl0 but got reply from 00:0d:61:80:ff:63 on vr0
Sep 22 14:20:18 volgograd routed[286]: sendto(rl0, 224.0.0.2): Permission denied
Sep 22 14:20:20 volgograd kernel: arp: 192.168.0.200 is on rl0 but got reply from 00:02:44:54:80:c9 on vr0
Sep 22 14:20:21 volgograd routed[286]: sendto(rl0, 224.0.0.2): Permission denied
Sep 22 14:20:34 volgograd kernel: arp: 192.168.0.79 is on rl0 but got reply from 00:c0:df:f4:dd:64 on vr0
Sep 22 14:20:41 volgograd kernel: arp: 192.168.0.65 is on rl0 but got reply from 00:c0:26:aa:2f:4a on vr0
Sep 22 14:21:10 volgograd kernel: arp: 192.168.0.70 is on rl0 but got reply from 00:0d:61:80:fd:f1 on vr0
Sep 22 14:21:28 volgograd kernel: arp: 192.168.0.56 is on rl0 but got reply from 00:0c:6e:37:0d:f9 on vr0
Sep 22 14:21:37 volgograd squid[526]: Squid Parent: child process 529 started
Sep 22 14:21:50 volgograd kernel: arp: 192.168.0.51 is on rl0 but got reply from 00:14:85:e3:ff:74 on vr0и так далее
>arp: 192.168.0.75 is on rl0 but got reply from 00:0d:61:80:ff:60 on vr0>Sep 22 16:19:20 volgograd qpopper[1585]: (v4.0.8) Unable to get canonical name of
>client 192.168.0.56: hostname nor servname provided, or not known (8)
>Sep 22 16:19:20 volgograd qpopper[1585]: (v4.0.8) Servicing request from "192.168.0.56" at 192.168.0.56
>Sep 22 14:20:15 volgograd kernel: rl0: link state changed to UP
>Sep 22 14:20:15 volgograd routed[286]: sendto(rl0, 224.0.0.2): Permission denied
>Sep 22 14:20:17 volgograd kernel: arp: 192.168.0.71 is on rl0 but got
>reply from 00:0d:61:80:ff:63 on vr0
>Sep 22 14:20:18 volgograd routed[286]: sendto(rl0, 224.0.0.2): Permission denied
>Sep 22 14:20:20 volgograd kernel: arp: 192.168.0.200 is on rl0 but got
>reply from 00:02:44:54:80:c9 on vr0
>Sep 22 14:20:21 volgograd routed[286]: sendto(rl0, 224.0.0.2): Permission denied
>Sep 22 14:20:34 volgograd kernel: arp: 192.168.0.79 is on rl0 but got
>reply from 00:c0:df:f4:dd:64 on vr0
>Sep 22 14:20:41 volgograd kernel: arp: 192.168.0.65 is on rl0 but got
>reply from 00:c0:26:aa:2f:4a on vr0
>Sep 22 14:21:10 volgograd kernel: arp: 192.168.0.70 is on rl0 but got
>reply from 00:0d:61:80:fd:f1 on vr0
>Sep 22 14:21:28 volgograd kernel: arp: 192.168.0.56 is on rl0 but got
>reply from 00:0c:6e:37:0d:f9 on vr0
>Sep 22 14:21:37 volgograd squid[526]: Squid Parent: child process 529 started
>Sep 22 14:21:50 volgograd kernel: arp: 192.168.0.51 is on rl0 but got
>reply from 00:14:85:e3:ff:74 on vr0
>
>и так далееА что находится в rc.conf по-поводу настройки сетевых интерфейсов rl0 и vr0?
Помимо логов, может что интерестное выдаётся на первую консоль в процесс работы?
В таком зоопарке любой чих может привести к неработоспособной системе.
Возьми GENERIC и оставь в нем только то, что _действительно_ соответствует
конфигурации машины и потребностям работающих на ней серверов.
Выкинь (закомментируй) все лишние драйвера, ненужные
протоколы и опции.>------------------------------------------------------------
>
>ЯДРО
>
>------------------------------------------------------------начни с определения, того какой у тебя процессор:
machine i386
#cpu I486_CPU
#cpu I586_CPU
cpu I686_CPU
ident FIRST/usr/src/sys/conf/NOTES и /usr/src/sys/i386/conf/NOTES тебе помогут
на консоли никаких ошибок, а ядро на самом деле я почищу
>на консоли никаких ошибок, а ядро на самом деле я почищуЯдро почти GENERIC, но попробовать стоит.
>на консоли никаких ошибок, а ядро на самом деле я почищуВидимых ошибок может и не быть, но что бы минимизировать поиск проблемы, надо иметь чистую систему, без лишних драйверов и опций. Со 100% вероятностью никто никогда такого ядра не запускал и не тестировал, возможны разные неизвестные науке взаимовлияния модулей.
Из шаманских плясок:
- coredump ядро делает или умирает втихушку?
- память тестировал?
- пробовал вынимать/вставлять платы, память, процессор?
- когда последний раз пылесосил машину?
- напряжения на материнке в порядке?
- температурный режим?"Электроника - наука о контактах". Если операционная система не говорит о своих проблемах, скорее всего что-то творится с железом.
Попробуйте поменять сетевуху vr0 на другую (например классическую rl0) - у меня в одном случае FreeBSD 6.1 на такой сетевухе висла при команде ifconfig vr0 down - но это был не kernel паник - просто система начинала работать оооооочень медленно :)
>Попробуйте поменять сетевуху vr0 на другую (например классическую rl0)
realtek в топку, только не его.
>(ipfw, natd, sendmail) FreeBSD 6.1 виснет ??? какое-то время (от 1-го часаЭто виснет ipfw + pf, ищи соотв. PR - кстати может до сих пор не пофиксили. Лечится убитием одного из ipfw/pf, а если честно, после 4.11 фря только разочарует :(