Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    [Resolvido] Pfsense travando

    Scheduled Pinned Locked Moved Portuguese
    13 Posts 4 Posters 10.4k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      madrugaaa
      last edited by

      Boa tarde, meu pfsense a cada 2 dias mais ou menos trava,a luz laranja na cpu fica acesa parada. Tenho q reiniciar no dedo,ai funciona uns 2 dias mais ou menos e volta a travar. Qual log tenho que verificar? vi o log do sistema mais ele guarda somente os 50 ultimos registros, e ao ligar os registros de inicialização do sistema substitui os antigos e n da pra visualizar. Alguém me ajuda?
      Att

      1 Reply Last reply Reply Quote 0
      • J
        johnnybe
        last edited by

        Alguém poderia ajudar mais rapidamente se você especificasse detalhadamente seu hardware e o tipo de ambiente onde ele se encontra. Já vi casos onde a temperatura da CPU subiu muito (ambiente mal refrigerado), ou por falta de limpeza do cooler, ou mesmo por problemas de refrigeração na fonte.
        Em um dos casos, o gabinete com o pfSense estava colocado num pequeno armário de madeira fechado, junto com mais dois outros servidores Win 2008 que mal cabiam naquele espaço e sem nenhuma abertura externa para refrigeração.
        Em outro caso, a entrada de refrigeração da fonte num gabinete de rack 1U estava obstruída por poeira. Tanta poeira que parecia um carpete na entrada dela. :)

        you would not believe the view up here

        1 Reply Last reply Reply Quote 0
        • M
          madrugaaa
          last edited by

          johnnybe,
          obrigado pela ajuda, tenho um IBM x226 com processador Intel(R) Xeon(TM) CPU 3.20GHz , memória 3gb, o problema de calor não é,olhei a temperatura do processador hd e tudo ok,tenho mais 4 servidores ibm ligados na mesma sala, e tem um bom ar condicionado.
          Essa máquina até 2 semanas atrás tava rodando um windows server 2008 sem problema algum, creio que seja mesmo algum problema no pfsense, ou incompatibilidade de algum hardware não sei, porém fui verificar os logs do Sistema agora, e o mesmo só grava os ultimos 50 registros, deparei somente com 1 erro: php: : The command '/usr/local/sbin/squid -k reconfigure' returned exit code '1', the output was 'squid: ERROR: No running copy'
          Não sei se esse erro pode ser a causa do travamento, e se souber como solucionar fico grato.
          De qualquer forma obrigado pelo help.
          Att

          1 Reply Last reply Reply Quote 0
          • J
            johnnybe
            last edited by

            @madrugaaa:

            … tenho um IBM x226 com processador Intel(R) Xeon(TM) CPU 3.20GHz , memória 3gb, o problema de calor não é,olhei a temperatura do processador hd e tudo ok,tenho mais 4 servidores ibm ligados na mesma sala, e tem um bom ar condicionado.

            O hardware parece ser adequado e o ambiente também. Resta saber quanto hosts estão por tras do pfSense.

            @madrugaaa:

            … creio que seja mesmo algum problema no pfsense, ou incompatibilidade de algum hardware não sei,...

            Incompatibilidade de hardware não é, do contrário, nem teria instalado. Pode ser gargalo, pela razão que eu disse acima. Muitos hosts, com muitos acessos simultâneos podem esgotar a memória RAM e sua tabela de alocação em State table size: cada estado de conexão consome 1KB da RAM. Pode parecer pouco, mas quando se utiliza pacotes como Squid e Snort, que consomem muita memória, se mal configurados, a utilização muito alta da memória pode travar o sitema.

            @madrugaaa:

            … porém fui verificar os logs do Sistema agora, ..., deparei somente com 1 erro: php: : The command '/usr/local/sbin/squid -k reconfigure' returned exit code '1', the output was 'squid: ERROR: No running copy'
            Não sei se esse erro pode ser a causa do travamento, e se souber como solucionar fico grato.

            Esse erro, segundo seus logs, "squid: ERROR: No running copy", pode ser causa de travamento, sim. Ou o Squid está mal configurado ou corrompido por alguma queda de energia. Na configuração de cache do Squid, em Memory cache size, está claro que "This value should not exceed more than 50% of the installed RAM". Verifique isso.

            @madrugaaa:

            … fui verificar os logs do Sistema agora, e o mesmo só grava os ultimos 50 registros...

            Só grava os 50 registros porque você não configurou para gravar mais que isso. Vá em Status: System logs: Settings e na opção Number of log entries to show aumente o valor conforme sua necessidade. Mas não abuse, ok? Conheço configurações que aceitam bem 550 registros. Sei lá o que vai acontecer se você colocar 1.500, por exemplo.  ;D

            you would not believe the view up here

            1 Reply Last reply Reply Quote 0
            • M
              madrugaaa
              last edited by

              Esse pfsense ainda está em implantação, em testes e só tenho 1 máquina conectada a ele para testar. Minhas configurações do squid estava padrão, não tinha feito alteração ainda, porém agora ajustei da seguinte forma(em anexo).
              Mudei os logs para 300 registros. Visto que minhas configurações do squid estava padrão, mesmo com 1 usuário conectado no pfsense pode ser a causa do problema né? Para limpar o cache do squid é o seguinte?
              1 - Parar o serviço do Squid
              2 - # rm -r /var/squid/cache/* Aguarde alguns minutos ate que efetue a limpeza…
              3 - # squid -z
              4 -Iniciar o serviço do Squid

              Algo mais em que possa tá fazendo ou a princípio é isso mesmo?

              Segue abaixo o log do system logs.

              Oct 26 20:38:16	syslogd: kernel boot file is /boot/kernel/kernel
Oct 26 20:38:16	kernel: Copyright (c) 1992-2010 The FreeBSD Project.
Oct 26 20:38:16	kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Oct 26 20:38:16	kernel: The Regents of the University of California. All rights reserved.
Oct 26 20:38:16	kernel: FreeBSD is a registered trademark of The FreeBSD Foundation.
Oct 26 20:38:16	kernel: FreeBSD 8.1-RELEASE-p6 #0: Mon Dec 12 18:15:35 EST 2011
Oct 26 20:38:16	kernel: root@FreeBSD_8.0_pfSense_2.0-AMD64.snaps.pfsense.org:/usr/obj./usr/pfSensesrc/src/sys/pfSense_SMP.8 amd64
Oct 26 20:38:16	kernel: Timecounter "i8254" frequency 1193182 Hz quality 0
Oct 26 20:38:16	kernel: CPU: Intel(R) Xeon(TM) CPU 3.20GHz (3200.13-MHz K8-class CPU)
Oct 26 20:38:16	kernel: Origin = "GenuineIntel" Id = 0xf43 Family = f Model = 4 Stepping = 3
Oct 26 20:38:16	kernel: Features=0xbfebfbff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe>Oct 26 20:38:16	kernel: Features2=0x641d <sse3,dtes64,mon,ds_cpl,cnxt-id,cx16,xtpr>Oct 26 20:38:16	kernel: AMD Features=0x20100800 <syscall,nx,lm>Oct 26 20:38:16	kernel: TSC: P-state invariant
Oct 26 20:38:16	kernel: real memory = 3221225472 (3072 MB)
Oct 26 20:38:16	kernel: avail memory = 3048640512 (2907 MB)
Oct 26 20:38:16	kernel: ACPI APIC Table: <ptltd apic="">
Oct 26 20:38:16	kernel: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
Oct 26 20:38:16	kernel: FreeBSD/SMP: 1 package(s) x 1 core(s) x 2 HTT threads
Oct 26 20:38:16	kernel: cpu0 (BSP): APIC ID: 0
Oct 26 20:38:16	kernel: cpu1 (AP/HT): APIC ID: 1
Oct 26 20:38:16	kernel: ioapic0 <version 2.0=""> irqs 0-23 on motherboard
Oct 26 20:38:16	kernel: ioapic1 <version 2.0=""> irqs 24-47 on motherboard
Oct 26 20:38:16	kernel: ioapic2 <version 2.0=""> irqs 48-71 on motherboard
Oct 26 20:38:16	kernel: netisr_init: forcing maxthreads to 1 and bindthreads to 0 for device polling
Oct 26 20:38:16	kernel: wlan: mac acl policy registered
Oct 26 20:38:16	kernel: ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
Oct 26 20:38:16	kernel: ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
Oct 26 20:38:16	kernel: module_register_init: MOD_LOAD (ipw_monitor_fw, 0xffffffff80470e10, 0) error 1
Oct 26 20:38:16	kernel: wpi: You need to read the LICENSE file in /usr/share/doc/legal/intel_wpi/.
Oct 26 20:38:16	kernel: wpi: If you agree with the license, set legal.intel_wpi.license_ack=1 in /boot/loader.conf.
Oct 26 20:38:16	kernel: module_register_init: MOD_LOAD (wpi_fw, 0xffffffff806548d0, 0) error 1
Oct 26 20:38:16	kernel: ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
Oct 26 20:38:16	kernel: ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
Oct 26 20:38:16	kernel: module_register_init: MOD_LOAD (ipw_bss_fw, 0xffffffff80470cd0, 0) error 1
Oct 26 20:38:16	kernel: ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
Oct 26 20:38:16	kernel: ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
Oct 26 20:38:16	kernel: module_register_init: MOD_LOAD (ipw_ibss_fw, 0xffffffff80470d70, 0) error 1
Oct 26 20:38:16	kernel: kbd1 at kbdmux0
Oct 26 20:38:16	kernel: cryptosoft0: <software crypto=""> on motherboard
Oct 26 20:38:16	kernel: padlock0: No ACE support.
Oct 26 20:38:16	kernel: acpi0: <ptltd rsdt=""> on motherboard
Oct 26 20:38:16	kernel: acpi0: [ITHREAD]
Oct 26 20:38:16	kernel: acpi0: Power Button (fixed)
Oct 26 20:38:16	kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
Oct 26 20:38:16	kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
Oct 26 20:38:16	kernel: cpu0: <acpi cpu=""> on acpi0
Oct 26 20:38:16	kernel: cpu1: <acpi cpu=""> on acpi0
Oct 26 20:38:16	kernel: pcib0: <acpi host-pci="" bridge=""> port 0xcf8-0xcff on acpi0
Oct 26 20:38:16	kernel: pci0: <acpi pci="" bus=""> on pcib0
Oct 26 20:38:16	kernel: pcib1: <acpi pci-pci="" bridge=""> irq 16 at device 2.0 on pci0
Oct 26 20:38:16	kernel: pci1: <acpi pci="" bus=""> on pcib1
Oct 26 20:38:16	kernel: bge0: <broadcom netxtreme="" gigabit="" ethernet="" controller,="" asic="" rev.="" 0x004101=""> mem 0xb0100000-0xb010ffff irq 16 at device 0.0 on pci1
Oct 26 20:38:16	kernel: miibus0: <mii bus=""> on bge0
Oct 26 20:38:16	kernel: brgphy0: <bcm5750 10="" 100="" 1000basetx="" phy=""> PHY 1 on miibus0
Oct 26 20:38:16	kernel: brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
Oct 26 20:38:16	kernel: bge0: [ITHREAD]
Oct 26 20:38:16	kernel: pcib2: <acpi pci-pci="" bridge=""> at device 3.0 on pci0
Oct 26 20:38:16	kernel: pci2: <acpi pci="" bus=""> on pcib2
Oct 26 20:38:16	kernel: pcib3: <acpi pci-pci="" bridge=""> at device 0.0 on pci2
Oct 26 20:38:16	kernel: pci3: <acpi pci="" bus=""> on pcib3
Oct 26 20:38:16	kernel: ahd0: <adaptec aic7902="" ultra320="" scsi="" adapter=""> port 0x2400-0x24ff,0x2000-0x20ff mem 0xb0300000-0xb0301fff irq 30 at device 3.0 on pci3
Oct 26 20:38:16	kernel: ahd0: [ITHREAD]
Oct 26 20:38:16	kernel: aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100MHz, 512 SCBs
Oct 26 20:38:16	kernel: ahd1: <adaptec aic7902="" ultra320="" scsi="" adapter=""> port 0x2c00-0x2cff,0x2800-0x28ff mem 0xb0302000-0xb0303fff irq 31 at device 3.1 on pci3
Oct 26 20:38:16	kernel: ahd1: [ITHREAD]
Oct 26 20:38:16	kernel: aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X 67-100MHz, 512 SCBs
Oct 26 20:38:16	kernel: pcib4: <acpi pci-pci="" bridge=""> at device 0.2 on pci2
Oct 26 20:38:16	kernel: pci4: <acpi pci="" bus=""> on pcib4
Oct 26 20:38:16	kernel: re0: <realtek 8169="" 8169s="" 8169sb(l)="" 8110s="" 8110sb(l)="" gigabit="" ethernet=""> port 0x3000-0x30ff mem 0xb0400000-0xb04000ff irq 48 at device 1.0 on pci4
Oct 26 20:38:16	kernel: re0: Chip rev. 0x00800000
Oct 26 20:38:16	kernel: re0: MAC rev. 0x00000000
Oct 26 20:38:16	kernel: miibus1: <mii bus=""> on re0
Oct 26 20:38:16	kernel: rgephy0: <rtl8169s 8110s="" 8211b="" media="" interface=""> PHY 1 on miibus1
Oct 26 20:38:16	kernel: rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
Oct 26 20:38:16	kernel: re0: [FILTER]
Oct 26 20:38:16	kernel: pcib5: <acpi pci-pci="" bridge=""> irq 16 at device 4.0 on pci0
Oct 26 20:38:16	kernel: pci5: <acpi pci="" bus=""> on pcib5
Oct 26 20:38:16	kernel: vgapci0: <vga-compatible display=""> port 0x4000-0x407f mem 0xb1000000-0xb1ffffff,0xc0000000-0xcfffffff,0xb2000000-0xb3ffffff irq 16 at device 0.0 on pci5
Oct 26 20:38:16	kernel: uhci0: <intel 82801eb="" (ich5)="" usb="" controller="" usb-a=""> port 0x1400-0x141f irq 16 at device 29.0 on pci0
Oct 26 20:38:16	kernel: uhci0: [ITHREAD]
Oct 26 20:38:16	kernel: usbus0: <intel 82801eb="" (ich5)="" usb="" controller="" usb-a=""> on uhci0
Oct 26 20:38:16	kernel: uhci1: <intel 82801eb="" (ich5)="" usb="" controller="" usb-b=""> port 0x1420-0x143f irq 19 at device 29.1 on pci0
Oct 26 20:38:16	kernel: uhci1: [ITHREAD]
Oct 26 20:38:16	kernel: usbus1: <intel 82801eb="" (ich5)="" usb="" controller="" usb-b=""> on uhci1
Oct 26 20:38:16	kernel: uhci2: <intel 82801eb="" (ich5)="" usb="" controller="" usb-c=""> port 0x1440-0x145f irq 18 at device 29.2 on pci0
Oct 26 20:38:16	kernel: uhci2: [ITHREAD]
Oct 26 20:38:16	kernel: usbus2: <intel 82801eb="" (ich5)="" usb="" controller="" usb-c=""> on uhci2
Oct 26 20:38:16	kernel: uhci3: <intel 82801eb="" (ich5)="" usb="" controller="" usb-d=""> port 0x1460-0x147f irq 16 at device 29.3 on pci0
Oct 26 20:38:16	kernel: uhci3: [ITHREAD]
Oct 26 20:38:16	kernel: usbus3: <intel 82801eb="" (ich5)="" usb="" controller="" usb-d=""> on uhci3
Oct 26 20:38:16	kernel: ehci0: <intel 82801eb="" r="" (ich5)="" usb="" 2.0="" controller=""> mem 0xb0000000-0xb00003ff irq 23 at device 29.7 on pci0
Oct 26 20:38:16	kernel: ehci0: [ITHREAD]
Oct 26 20:38:16	kernel: usbus4: EHCI version 1.0
Oct 26 20:38:16	kernel: usbus4: <intel 82801eb="" r="" (ich5)="" usb="" 2.0="" controller=""> on ehci0
Oct 26 20:38:16	kernel: pcib6: <acpi pci-pci="" bridge=""> at device 30.0 on pci0
Oct 26 20:38:16	kernel: pci6: <acpi pci="" bus=""> on pcib6
Oct 26 20:38:16	kernel: rl0: <realtek 10="" 8139="" 100basetx=""> port 0x5000-0x50ff mem 0xb4000000-0xb40000ff irq 16 at device 1.0 on pci6
Oct 26 20:38:16	kernel: miibus2: <mii bus=""> on rl0
Oct 26 20:38:16	kernel: rlphy0: <realtek internal="" media="" interface=""> PHY 0 on miibus2
Oct 26 20:38:16	kernel: rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
Oct 26 20:38:16	kernel: rl0: [ITHREAD]
Oct 26 20:38:16	kernel: re1: <realtek 8169="" 8169s="" 8169sb(l)="" 8110s="" 8110sb(l)="" gigabit="" ethernet=""> port 0x5400-0x54ff mem 0xb4000400-0xb40004ff irq 17 at device 2.0 on pci6
Oct 26 20:38:16	kernel: re1: Chip rev. 0x00800000
Oct 26 20:38:16	kernel: re1: MAC rev. 0x00000000
Oct 26 20:38:16	kernel: miibus3: <mii bus=""> on re1
Oct 26 20:38:16	kernel: rgephy1: <rtl8169s 8110s="" 8211b="" media="" interface=""> PHY 1 on miibus3
Oct 26 20:38:16	kernel: rgephy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
Oct 26 20:38:16	kernel: re1: [FILTER]
Oct 26 20:38:16	kernel: vgapci1: <vga-compatible display=""> port 0x5800-0x58ff mem 0xd0000000-0xd7ffffff,0xb4010000-0xb401ffff irq 22 at device 4.0 on pci6
Oct 26 20:38:16	kernel: isab0: <pci-isa bridge=""> at device 31.0 on pci0
Oct 26 20:38:16	kernel: isa0: <isa bus=""> on isab0
Oct 26 20:38:16	kernel: atapci0: <intel ich5="" udma100="" controller=""> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x14a0-0x14af at device 31.1 on pci0
Oct 26 20:38:16	kernel: ata0: <ata 0="" channel=""> on atapci0
Oct 26 20:38:16	kernel: ata0: [ITHREAD]
Oct 26 20:38:16	kernel: ata1: <ata 1="" channel=""> on atapci0
Oct 26 20:38:16	kernel: ata1: [ITHREAD]
Oct 26 20:38:16	kernel: pci0: <serial bus,="" smbus=""> at device 31.3 (no driver attached)
Oct 26 20:38:16	kernel: acpi_button0: <power button=""> on acpi0
Oct 26 20:38:16	kernel: atrtc0: <at realtime="" clock=""> port 0x70-0x71 irq 8 on acpi0
Oct 26 20:38:16	kernel: fdc0: <floppy drive="" controller=""> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
Oct 26 20:38:16	kernel: fdc0: [FILTER]
Oct 26 20:38:16	kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0
Oct 26 20:38:16	kernel: ppc0: <parallel port=""> port 0x378-0x37f,0x778-0x77f irq 7 drq 4 on acpi0
Oct 26 20:38:16	kernel: ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
Oct 26 20:38:16	kernel: ppc0: FIFO with 16/16/8 bytes threshold
Oct 26 20:38:16	kernel: ppc0: [ITHREAD]
Oct 26 20:38:16	kernel: ppbus0: <parallel port="" bus=""> on ppc0
Oct 26 20:38:16	kernel: plip0: <plip network="" interface=""> on ppbus0
Oct 26 20:38:16	kernel: plip0: [ITHREAD]
Oct 26 20:38:16	kernel: lpt0: <printer> on ppbus0
Oct 26 20:38:16	kernel: lpt0: [ITHREAD]
Oct 26 20:38:16	kernel: lpt0: Interrupt-driven port
Oct 26 20:38:16	kernel: ppi0: <parallel i="" o=""> on ppbus0
Oct 26 20:38:16	kernel: uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
Oct 26 20:38:16	kernel: uart0: [FILTER]
Oct 26 20:38:16	kernel: uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
Oct 26 20:38:16	kernel: uart1: [FILTER]
Oct 26 20:38:16	kernel: atkbdc0: <keyboard controller="" (i8042)=""> port 0x60,0x64 irq 1 on acpi0
Oct 26 20:38:16	kernel: atkbd0: <at keyboard=""> irq 1 on atkbdc0
Oct 26 20:38:16	kernel: kbd0 at atkbd0
Oct 26 20:38:16	kernel: atkbd0: [GIANT-LOCKED]
Oct 26 20:38:16	kernel: atkbd0: [ITHREAD]
Oct 26 20:38:16	kernel: sc0: <system console=""> at flags 0x100 on isa0
Oct 26 20:38:16	kernel: sc0: VGA <16 virtual consoles, flags=0x300>
Oct 26 20:38:16	kernel: vga0: <generic isa="" vga=""> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Oct 26 20:38:16	kernel: p4tcc0: <cpu frequency="" thermal="" control=""> on cpu0
Oct 26 20:38:16	kernel: p4tcc1: <cpu frequency="" thermal="" control=""> on cpu1
Oct 26 20:38:16	kernel: Timecounters tick every 1.000 msec
Oct 26 20:38:16	kernel: IPsec: Initialized Security Association Processing.
Oct 26 20:38:16	kernel: usbus0: 12Mbps Full Speed USB v1.0
Oct 26 20:38:16	kernel: usbus1: 12Mbps Full Speed USB v1.0
Oct 26 20:38:16	kernel: usbus2: 12Mbps Full Speed USB v1.0
Oct 26 20:38:16	kernel: usbus3: 12Mbps Full Speed USB v1.0
Oct 26 20:38:16	kernel: usbus4: 480Mbps High Speed USB v2.0
Oct 26 20:38:16	kernel: acd0: CDRW <tsstcorpcd-r rw="" ts-h292a="" ts02=""> at ata0-master UDMA33
Oct 26 20:38:16	kernel: ugen0.1: <intel> at usbus0
Oct 26 20:38:16	kernel: uhub0: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr=""> on usbus0
Oct 26 20:38:16	kernel: ugen1.1: <intel> at usbus1
Oct 26 20:38:16	kernel: uhub1: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr=""> on usbus1
Oct 26 20:38:16	kernel: ugen2.1: <intel> at usbus2
Oct 26 20:38:16	kernel: uhub2: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr=""> on usbus2
Oct 26 20:38:16	kernel: ugen3.1: <intel> at usbus3
Oct 26 20:38:16	kernel: uhub3: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr=""> on usbus3
Oct 26 20:38:16	kernel: ugen4.1: <intel> at usbus4
Oct 26 20:38:16	kernel: uhub4: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr=""> on usbus4
Oct 26 20:38:16	kernel: uhub0: 2 ports with 2 removable, self powered
Oct 26 20:38:16	kernel: uhub1: 2 ports with 2 removable, self powered
Oct 26 20:38:16	kernel: uhub2: 2 ports with 2 removable, self powered
Oct 26 20:38:16	kernel: uhub3: 2 ports with 2 removable, self powered
Oct 26 20:38:16	kernel: uhub4: 8 ports with 8 removable, self powered
Oct 26 20:38:16	kernel: ugen0.2: <chicony> at usbus0
Oct 26 20:38:16	kernel: ukbd0: <chicony 0="" 2="" usb="" netvista="" full="" width="" keyboard,="" class="" 0,="" rev="" 1.10="" 1.02,="" addr=""> on usbus0
Oct 26 20:38:16	kernel: kbd2 at ukbd0
Oct 26 20:38:16	kernel: (probe22:ahd1:0:8:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
Oct 26 20:38:16	kernel: (probe22:ahd1:0:8:0): CAM status: SCSI Status Error
Oct 26 20:38:16	kernel: (probe22:ahd1:0:8:0): SCSI status: Check Condition
Oct 26 20:38:16	kernel: (probe22:ahd1:0:8:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
Oct 26 20:38:16	kernel: ses0 at ahd1 bus 0 scbus1 target 8 lun 0
Oct 26 20:38:16	kernel: ses0: <ibm 1="" 02r0980a="" s320=""> Fixed Processor SCSI-2 device
Oct 26 20:38:16	kernel: ses0: 3.300MB/s transfers
Oct 26 20:38:16	kernel: ses0: SAF-TE Compliant Device
Oct 26 20:38:16	kernel: SMP: AP CPU #1 Launched!da0 at ahd1 bus 0 scbus1 target 3 lun 0
Oct 26 20:38:16	kernel:
Oct 26 20:38:16	kernel: da0: <ibm-esxs pyh146c3-ets10fn="" rxqk=""> Fixed Direct Access SCSI-4 device
Oct 26 20:38:16	kernel: da0: 320.000MB/s transfers (160.000MHz DT, offset 80, 16bit)
Oct 26 20:38:16	kernel: da0: Command Queueing enabled
Oct 26 20:38:16	kernel: da0: 140013MB (286748000 512 byte sectors: 255H 63S/T 17849C)
Oct 26 20:38:16	kernel: Trying to mount root from ufs:/dev/da0s1a
Oct 26 20:38:16	kernel: pflog0: promiscuous mode enabled
Oct 26 20:38:17	php: : Removing static route for monitor 200.202.17.1 and adding a new route through 192.168.25.1
Oct 26 20:38:17	php: : Removing static route for monitor 200.202.7.3 and adding a new route through 192.168.25.5
Oct 26 20:38:17	check_reload_status: Reloading filter
Oct 26 20:38:17	apinger: Starting Alarm Pinger, apinger(53598)
Oct 26 20:38:19	php: : ROUTING: setting default route to 192.168.25.1
Oct 26 20:38:19	check_reload_status: Updating all dyndns
Oct 26 20:38:20	dnsmasq[348]: started, version 2.55 cachesize 10000
Oct 26 20:38:20	dnsmasq[348]: compile time options: IPv6 GNU-getopt no-DBus I18N DHCP TFTP
Oct 26 20:38:20	dnsmasq[348]: reading /etc/resolv.conf
Oct 26 20:38:20	dnsmasq[348]: using nameserver 192.168.25.5#53
Oct 26 20:38:20	dnsmasq[348]: using nameserver 192.168.25.1#53
Oct 26 20:38:20	dnsmasq[348]: ignoring nameserver 127.0.0.1 - local interface
Oct 26 20:38:20	dnsmasq[348]: ignoring nameserver 127.0.0.1 - local interface
Oct 26 20:38:20	dnsmasq[348]: read /etc/hosts - 2 addresses
Oct 26 20:38:21	php: : OpenNTPD is starting up.
Oct 26 20:38:21	php: : rc.newwanip: Informational is starting rl0.
Oct 26 20:38:21	php: : rc.newwanip: on (IP address: 192.168.25.6) (interface: opt1) (real interface: rl0).
Oct 26 20:38:21	php: : Removing static route for monitor 200.202.17.1 and adding a new route through 192.168.25.1
Oct 26 20:38:21	php: : Removing static route for monitor 200.202.7.3 and adding a new route through 192.168.25.5
Oct 26 20:38:21	apinger: Exiting on signal 15.
Oct 26 20:38:22	dnsmasq[348]: reading /etc/resolv.conf
Oct 26 20:38:22	dnsmasq[348]: using nameserver 192.168.25.5#53
Oct 26 20:38:22	dnsmasq[348]: using nameserver 192.168.25.1#53
Oct 26 20:38:22	dnsmasq[348]: ignoring nameserver 127.0.0.1 - local interface
Oct 26 20:38:22	dnsmasq[348]: ignoring nameserver 127.0.0.1 - local interface
Oct 26 20:38:22	check_reload_status: Reloading filter
Oct 26 20:38:22	apinger: Starting Alarm Pinger, apinger(28693)
Oct 26 20:38:23	php: : Gateways status could not be determined, considering all as up/active.
Oct 26 20:38:23	check_reload_status: Restarting ipsec tunnels
Oct 26 20:38:26	php: : Creating rrd update script
Oct 26 20:38:26	php: : Restarting/Starting all packages.
Oct 26 20:38:27	php: : Starting Squid
Oct 26 20:38:27	squid[7365]: Squid Parent: child process 7581 started
Oct 26 20:38:27	check_reload_status: Reloading filter
Oct 26 20:38:27	php: : Reloading Squid for configuration sync
Oct 26 20:38:27	php: : The command '/usr/local/sbin/squid -k reconfigure' returned exit code '1', the output was 'squid: ERROR: No running copy'
Oct 26 20:38:27	php: : Reloading Squid for configuration sync
Oct 26 20:38:27	php: : The command '/usr/local/sbin/squid -k reconfigure' returned exit code '1', the output was 'squid: ERROR: No running copy'
Oct 26 20:38:28	php: : Not calling package sync code for dependency squid of squid because some include files are missing.
Oct 26 20:38:28	php: : Reloading Squid for configuration sync
Oct 26 20:38:28	php: : The command '/usr/local/sbin/squid -k reconfigure' returned exit code '1', the output was 'squid: ERROR: No running copy'
Oct 26 20:38:28	php: : Reloading Squid for configuration sync
Oct 26 20:38:29	php: : Reloading Squid for configuration sync
Oct 26 20:38:30	php: : Reloading Squid for configuration sync
Oct 26 20:38:34	squid[7365]: Squid Parent: child process 7581 exited with status 0
Oct 26 20:38:42	check_reload_status: Syncing firewall
Oct 26 20:38:43	php: : Starting Squid
Oct 26 20:38:43	squid[20337]: Squid Parent: child process 20933 started
Oct 26 20:38:43	check_reload_status: Reloading filter
Oct 26 20:38:43	check_reload_status: Syncing firewall
Oct 26 20:38:43	squid[20933]: The url_rewriter helpers are crashing too rapidly, need help!
Oct 26 20:38:43	kernel: pid 20933 (squid), uid 62: exited on signal 6
Oct 26 20:38:43	squid[20337]: Squid Parent: child process 20933 exited due to signal 6
Oct 26 20:38:46	php: : IPSEC: One or more IPsec tunnel endpoints has changed its IP. Refreshing.
Oct 26 20:38:46	squid[20337]: Squid Parent: child process 28679 started
Oct 26 20:38:47	login: login on ttyv0 as root
Oct 26 20:38:47	sshlockout[31267]: sshlockout/webConfigurator v3.0 starting up
Oct 26 20:38:48	check_reload_status: Reloading filter</ibm-esxs></ibm></chicony></chicony></intel></intel></intel></intel></intel></intel></intel></intel></intel></intel></tsstcorpcd-r></cpu></cpu></generic></system></at></keyboard></parallel></printer></plip></parallel></parallel></floppy></at></power></serial></ata></ata></intel></isa></pci-isa></vga-compatible></rtl8169s></mii></realtek></realtek></mii></realtek></acpi></acpi></intel></intel></intel></intel></intel></intel></intel></intel></intel></intel></vga-compatible></acpi></acpi></rtl8169s></mii></realtek></acpi></acpi></adaptec></adaptec></acpi></acpi></acpi></acpi></bcm5750></mii></broadcom></acpi></acpi></acpi></acpi></acpi></acpi></ptltd></software></version></version></version></ptltd></syscall,nx,lm></sse3,dtes64,mon,ds_cpl,cnxt-id,cx16,xtpr></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe>

              Gratoo

              cachemgt.jpg
              cachemgt.jpg_thumb

              1 Reply Last reply Reply Quote 0
              • marcellocM
                marcelloc
                last edited by

                O squid não costuma travar máquinas, e o log pode configurar até 2000 sem problema ;)

                instalou a versão 2.0.1 amd64?

                Treinamentos de Elite: http://sys-squad.com

                Help a community developer! ;D

                1 Reply Last reply Reply Quote 0
                • M
                  madrugaaa
                  last edited by

                  marcelloc,

                  Versão 2.0.1-RELEASE (amd64)  instalada.
                  Passou o final de semana sem travar com as alterações que fiz, agora é esperar pra ver se trava novamente.
                  Obrigado

                  1 Reply Last reply Reply Quote 0
                  • M
                    madrugaaa
                    last edited by

                    boa tarde, realmente meu pfsense continua travando, hoje cheguei ao trampo e tava a seguinte mensagem no console. NMI …. going to debugger
                    NMI .... going to debugger

                    Alguém faz idéia do que seja?

                    1 Reply Last reply Reply Quote 0
                    • M
                      madrugaaa
                      last edited by

                      Pessoal, rodei o memtest +86 para verificar os módulos de memória e não foi encontrado nenhum erro, meu pfsense continua travando dando a seguinte mensagem: NMI…Going to Debugger.
                      Alguém pra me ajudar?
                      Grato

                      1 Reply Last reply Reply Quote 0
                      • N
                        nofault
                        last edited by

                        Verifique nos logs algum erro de O/I  , poder ser erro de leitura no disco isso pode acontecer.

                        1 Reply Last reply Reply Quote 0
                        • N
                          nofault
                          last edited by

                          Esse tópico o pessoal teve o mesmo problema aparentemente a solução foi remoção manual do squid 64 bits e instalação do squid 32 bits

                          http://forum.pfsense.org/index.php?topic=27536.15

                          se possível na versão mais atual , acredito que vale a pena efetuar o teste para verificar.

                          1 Reply Last reply Reply Quote 0
                          • M
                            madrugaaa
                            last edited by

                            Resolvido o problema trocando as placas de rede.

                            1 Reply Last reply Reply Quote 0
                            • marcellocM
                              marcelloc
                              last edited by

                              @madrugaaa:

                              Resolvido o problema trocando as placas de rede.

                              Valeu pelo feedback  :)

                              Treinamentos de Elite: http://sys-squad.com

                              Help a community developer! ;D

                              1 Reply Last reply Reply Quote 0
                              • First post
                                Last post
                              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.