Sudden lock up after reboot
-
My pf box became unresponsive after reboot.
I'm using soekris net5501. with pfsense ver. 1.2.2 running for like 2 weeks. After one reboot here is what I see in a console:
Welcome to pfSense 1.2.2 on the 'pfSense' platform…
Mounting filesystems... done.
Creating symlinks......done.
Launching PHP init system... done.
Initializing.................. done.
Starting device manager (devd)...done.
Loading configuration......done.
Updating configuration...done.
Cleaning backup cache...done.
Setting up extended sysctls...done.
Syncing user passwords...done.
Starting Secure Shell Services...done.
Setting timezone...done.
Starting syslog...done.
Configuring LAN interface...done.
Configuring WAN interface...done.
Configuring OPT interfaces...done.
Configuring CARP interfaces...done.
Starting OpenNTP time client...done.
Configuring firewall.........done.
Starting webConfigurator...done.
Starting DHCP service...done.
Starting DNS forwarder...done.
Setting up microcode and tx/rx offloading...done.
Starting FTP helpers...done.
Final filter pass.........done.
Generating RRD graphs…ERROR: unknown DS name 'qPenaltyUp'
done.
Starting DHCP service…done.
Starting CRON... done.
Executing rc.d items...
Starting /usr/local/etc/rc.d/*.sh...done.
appending output to nohup.out
Bootup completeFreeBSD/i386 (pfsense.local) (console)
*** Welcome to pfSense 1.2.2-pfSense on pfsense ***
LAN* -> vr0 -> 192.168.1.2
WAN -> vr1 -> 192.168.1.80
OPT1(OPT1) -> vr2 -> NONEpfSense console setup
0) Logout (SSH only)
1) Assign Interfaces
2) Set LAN IP address
3) Reset webConfigurator password
4) Reset to factory defaults
5) Reboot system
6) Halt system
7) Ping host
8) Shell
9) PFtop
10) Filter Logs
11) Restart webConfigurator
12) pfSense PHP shell
13) Upgrade from console
14) Enable Secure Shell (sshd)Enter an option:
Unfortunately the unit is unaccessible from the LAN interface. I will redo LAN address and DHCP and try to access it again, if this will not help then reeinstalling the system.
For this moment I would like to know what the Error in the console mean and if anyone encounter a similar problem?
I was setting up my traffic shaper before rebooting. I also recall to change default view in RRD Graphs to "Queue".
I'm not having a physical access to the box on a daily basis so I can't afford to have this kind of random lock ups.
Tomorrow I will update the thread with my effort to access the webgui to exclude hardware possible issues. -
Your LAN has a 192.168.1.0/24 - that's ok.
But you WAN shouldn't be a in the same range. It should be a 192.168.2.0/24 or a 10.0.0.0/8 if you need 'local' IP's.This : Generating RRD graphs…ERROR: unknown DS name 'qPenaltyUp' isn't really harmfull - it shouldn't blow up pfsense.
Activate syslog to a remote PC so you can follow what happens.
Status => System logs => Settings and give a local Ip at "Remote syslog server".
Put a syslogger on that PC. -
+1 to Gertjan's comment - all your interfaces must be in different subnets.
-
Well I had WAN in 255.255.255.0 subnet and LAN in 255.255.0.0
It was working well for 2 weeks with many reboots in between :-\ After changing LAN address to 192.168.2.1 the box became accessible again.Thanks for the quick reply!
-
So, your LAN network was 192.168.x.x and your WAN 192.168.1.x - that won't work either. You have to ensure that the subnets are different. If you switched your LAN to 192.168.2.1 make sure you also changed the netmask to 255.255.255.0 (aka /24).
-
So, your LAN network was 192.168.x.x and your WAN 192.168.1.x
Thats correct.
If you switched your LAN to 192.168.2.1 make sure you also changed the netmask to 255.255.255.0 (aka /24).
Why can't I keep netmask 255.255.0.0 (aka /16)?
-
Can I gently suggest you read up on how subnet masks and routing work.
192.168.1.z/24 is a subnet of 192.168.x.y/16. This means that any host on the /16 network will assume that the /24 network is local to it and will not use the default gateway.
-
That's my bad indeed.
The "knowledge" I thought having is compromised. I shouldn't take for granted informations from a person which teaches networking without checkings the validity of it… :-\No more stupid questions from me for a while.
-
The only stupid questions are the ones you don't ask. It's better to find out what you don't know than to blunder around in ignorance ;)
(Also known as, nobody knows everything and there's always something you thought you knew that you had wrong)
-
It seems that it's a bit more difficult issue than I thought.
I'm having very limited time to access the box on it's physical location so I just tried few things and it didn't seem to work very well.
I set up the LAN to 192.168.2.1/24
I could access it from my computer only when setting manually my IP within the IP range of my DHCP server on pfsense. Choosing the automatic IP configuration on the PC caused the box beeing pingable but not accessible via WebGUI. Another thing is that with the same settings on the WAN side I could not access my gateway (PPPoE modem) nor I was able to connect to the internet through the pf box. Checking the DHCP leases on the box showed that the clients had the IPs assigned but as I mentioned before they could only ping the pfsense - no connectivity with internet or with WebGUI.Tomorrow I will try from scratch with 1.2.3 version (current one is 1.2.2).
Ones it's up and running I will setup the system log so to be able to give more informations in case of further obstacles.
Thanks for the replies so far guys!
-
Do you have multiple devices doing DHCP? When you configure the client for DHCP, check to see what IP range the lease is in and what the default gateway is.
-
I replicated the same exact setup after installing pfsense 1.2.3 and it seems work well. I guess there was some error in system files since the box was shut down few times not properly - just guessing.
