unable to get UI/SSH/Term
-
This has been going on for a while and I have not been able to figure out whats going on.
The firewall works I get internet/dhcp/spi/ everything... But I can t ssh in nor get to the web ui.... Not even terminal via usb.
I can only get to the Web ui for a few min on every reboot.Terminsal does not respond at all. I can see evertyhing and even the menu but when I try to do a selection it wont take it.....
SSH just plain hangs.I got a small window where I was able to upgrade but it made no difference....
I am running pfsense 2.4.5 on a Netgate SG-3100 -
Something is definitely locking any access to the firewall and is not a rule because this has been working for month.. This just started happening a few weeks now.
Please help.
-
I see this from console: resizewin: timeout reading from terminal
-
So I came back this AM and lo and behold the UI was accessible, During troubleshooting, I removed several pkgs. I went to try and re install them and BAM, damn things again locks up and I cant access the UI...
Internet works... everything works... DHCP, etc.... But no UI/SSH/or console. -
Hello:
Maybe you don't want to read this but...
To me, in order to test if the problem is your config or the SG-3100 is to do the following:
-
MOST IMPORTANT! - Do you have a backup of your configuration?
A - If yes, go to step #4
B - If no, go to step #2 -
Wait until you regain full control of your system (maybe overnight per your above post).
-
Make a backup of your system, then go to step #4.
-
Get a copy of 2.4.5 and verify its SHA256 checksum (if not done already).
-
Install fresh copy of pfSense.
-
After install, attempt login WITHOUT using your backup config/copy.
-
Does pfSense respond to your request?
A - If no, problem maybe SG-3100 (contact Netgate support possibly).
B - If yes, problem maybe your config file and/or a package you are trying to install -
If 7B - Restart at step #5
-
Add 1 rule (if applicable) at a time to see if problem occurs. Let system stabilize. You get the idea from here
-
If all rules applied without problem, then add 1 package at a time to see if problem occurs. Let system stabilize. You get the idea from here.
To me this is the ONLY way to determine if it is a config/package problem or a SG-3100 problem.
Hope it helps.
-
-
@pfSense4ME , The only problem with this and or your quest is that it has been working for months till a couple of weeks...
So..... I did notice one thing. From day one I had problems with squid when I reloaded from my backup back in December, I remember that I disable it and my issues went away... Guess what? squid enable it self some how.... Now I uninstalled it and issue is gone and should not come back.I think squid is causing some sort of IO that is killing the unit.
Issue resolved.
-
Hello:
That is GREAT you have resolved your issue! Good catch!
I'm curious about the statement you made about squid, "I think squid is causing some sort of IO that is killing the unit.". My curiosity is; I wonder if some of the problems (after going to 2.4.5) being described by others (either on a VM or physical machine) is if squid is the common denominator (if problem system are utilizing squid - HUGE if)? I don't use squid so I can't say for sure. I'm also not saying squid IS the problem. Only the users that are experiencing the problem (long delays, lockups, etc.) can say for sure. Maybe you're on to something and what worked for you "might" work for someone else. Not saying yes or no. To me, if someone who is experiencing a problem AND is utilizing squid, THEN disables (or removes) squid and problem disappears... Who knows, until more info as to the problem is acquired it's all pure conjecture.
-
@pfSense4ME Got cha.... My squid issue comes from before and I think is a config issue in my case, I do wonder though, are others with issue also using squid? Which than can explain my other issues I was having and now that you mention it, it might be the same as others...
I was very excited about this update, I was thinking that my issue was related to this:
https://github.com/pfsense/pfsense/pull/4170
BUT it is obvious that is not. I now ponder...
This all started with very slow UI response....
-
Hello:
@ffuentes, You stated "My squid issue comes from before and I think is a config issue in my case...", a squid config issue or a pfSense config issue? Fist and foremost any kind of config issue would drive me insane! I would hunt it down and fix whatever was wrong. If that meant starting fresh until it worked (correctly) then that's what I would do (and have done in the past). Total PITA, but, I then know I don't have to play that "well maybe because I did/didn't do something and now that might be what's causing this new problem." SO FRUSTRATING!!!! Problem with this approach is obviously time (and money).
Either way, you might want to consider fixing the issue so as to avoid a future headache. I'm guessing this unit is a unit in production so fixing may require doing it when the impact is at a minimal. Always hated that, but no greater joy than knowing the config is perfect and possible future headaches will be avoided (well at least that's how I felt).
As stated previously, I don't use squid (not that I haven't experimented with it in the past and decided it wasn't necessary for my needs). My setup is very vanilla with a dash of a few VLANs thrown in. My conversion to 2.4.5 was easy peasy! No problems, less than 5 minutes total. But then again, I'm not utilizing pfSense to it's full potential.
I just hope whatever issue(s) it is, it's found quickly and COMPLETELY resolves the problem for everyone. Feel so sorry for anyone going through this as pfSense is an awesome product!