Pfsense on watchguard XTM 5 Series black LCD and only Power LED is turn Green
-
Thanks for the reply. I got figure it out. Turns out one of my watchguard RAM not working properly. After i remove it i can install pfsense without any problem.
But....After a while running pfsense let's say about 1 hour. The pfsense reboot it self over and over again. I have to unplug the power cable. Does anyone have facing the same problem? Thanks
-
You have any logs from the console showing when it first rebooted? That would be most likely to indicate a problem.
It sounds like a hardware issue though.
Steve
-
can the log show which hardware got the problem?
this is full system log
and for today boot loop i believe this is the log
Dec 18 11:21:54 pfSense check_reload_status: Syncing firewall
Dec 18 12:05:35 pfSense php: /usr/local/pkg/snort/snort_check_for_rule_updates.p hp: [Snort] Snort GPLv2 Community Rules md5 download failed...
Dec 18 12:05:35 pfSense php: /usr/local/pkg/snort/snort_check_for_rule_updates.p hp: [Snort] Server returned error code 503...
Dec 18 12:05:35 pfSense php: /usr/local/pkg/snort/snort_check_for_rule_updates.p hp: [Snort] The Rules update has finished.
Dec 18 13:49:38 pfSense syslogd: kernel boot file is /boot/kernel/kernel
Dec 18 13:49:38 pfSense kernel: Copyright (c) 1992-2018 The FreeBSD Project.
Dec 18 13:49:38 pfSense kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989 , 1991, 1992, 1993, 1994
Dec 18 13:49:38 pfSense kernel: The Regents of the University of California. All rights reserved.
Dec 18 13:49:38 pfSense kernel: FreeBSD is a registered trademark of The FreeBSD Foundation.
Dec 18 13:49:38 pfSense kernel: FreeBSD 11.2-RELEASE-p10 #9 4a2bfdce133(RELENG_2 _4_4): Wed May 15 18:54:42 EDT 2019
Dec 18 13:49:38 pfSense kernel: root@buildbot1-nyi.netgate.com:/build/ce-crossbu ild-244/obj/amd64/ZfGpH5cd/build/ce-crossbuild-244/pfSense/tmp/FreeBSD-src/sys/p fSense amd64
Dec 18 13:49:38 pfSense kernel: FreeBSD clang version 6.0.0 (tags/RELEASE_600/fi nal 326565) (based on LLVM 6.0.0)
Dec 18 13:49:38 pfSense kernel: VT(vga): resolution 640x480
Dec 18 13:49:38 pfSense kernel: CPU: Intel(R) Celeron(R) CPU E3400 @ 2.6 0GHz (2593.55-MHz K8-class CPU)
Dec 18 13:49:38 pfSense kernel: Origin="GenuineIntel" Id=0x1067a Family=0x6 M odel=0x17 Stepping=10
Dec 18 13:49:38 pfSense kernel: Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,M CE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,S S,HTT,TM,PBE>
Dec 18 13:49:38 pfSense kernel: Features2=0xc00e3bd<SSE3,DTES64,MON,DS_CPL,VMX,E ST,TM2,SSSE3,CX16,xTPR,PDCM,XSAVE,OSXSAVE>
Dec 18 13:49:38 pfSense kernel: AMD Features=0x20100800<SYSCALL,NX,LM>
Dec 18 13:49:38 pfSense kernel: AMD Features2=0x1<LAHF>
Dec 18 13:49:38 pfSense kernel: VT-x: HLT,PAUSE
Dec 18 13:49:38 pfSense kernel: TSC: P-state invariant, performance statistics
Dec 18 13:49:38 pfSense kernel: real memory = 2147483648 (2048 MB)
Dec 18 13:49:38 pfSense kernel: avail memory = 1985601536 (1893 MB)
Dec 18 13:49:38 pfSense kernel: Event timer "LAPIC" quality 100
Dec 18 13:49:38 pfSense kernel: ACPI APIC Table: <042610 APIC1157>
Dec 18 13:49:38 pfSense kernel: FreeBSD/SMP: Multiprocessor System Detected: 2 C PUs
Dec 18 13:49:38 pfSense kernel: FreeBSD/SMP: 1 package(s) x 2 core(s)
Dec 18 13:49:38 pfSense kernel: ioapic0 <Version 2.0> irqs 0-23 on motherboard
Dec 18 13:49:38 pfSense kernel: SMP: AP CPU #1 Launched!at 13:49 pfsense start running again after i unplugged the power cable. and at 12:05 is last known log before it start boot loop. note that i check at 12:50 and the pfsense still running well. so i am not sure the exact time it start boot loop.
-
Nope you would need the output from the serial console. The system log stops logging usually when this happens.
Do you see a crash report when it reboots?
Steve
-
this is what i get from console when it first reboot after 2 hour 30 minute running...
-
It looks like that have overwritten itself to an extent there. That 'login as admin' line can't possibly be before the kernel loads.
If it's doing it that quickly I would connect to the console with, for example, putty and enable logging. The only place you might see any output indicating the cause is immediately before it reboots so you need to be logging that output before it happens.
Steve
-
@stephenw10 how can i enable the logging? is there any step by step reference. because all i got in the web is logging in the web management (ex. logging Firewall)
-
The logging you need is in putty, it logs all the serial output so we can see anything shown there before it reboots. Enabling logging is a setting in putty. Assuming you're using putty. Other terminal clients usually also have logging.
Steve
-
@stephenw10 oh i see. i understand now. i think pfsense is running stable now after i change the Sata Port. thank you very much
-
Ah, nice result then.