Problems & Questions
-
Afaik going from 2.3.x to 2.4 no packages are removed.. (yes freeradius 2.x is replaced by 3.x or something.. and probably some others..)
Timezones has always been troublesome, the more generic ones usually work fine afaik, but those defined by city have their share of issues.. Best i can advice is try a few..
b.t.w. what exactly do you mean with 'its incorrect' is it off by an hour? or something else?Reboot whats shown on console? Is there perhaps a bios update for your machine?
What services are we talking about? whats in the systemlogs or specific logs for the services where applicable?
Traffic graphs.. tried a different browser? or clearing cache maybe some javascript that aint refreshing..? Does status/trafficgraph screen work?
Performance, is any background process using a lot of cpu?
Packages that wont install, what error is shown? You do have working dns and a default route on pfSense? Perhaps prefering IPv4 might help.
If the system says its going to replace something 'that' is what should happen.. unless of course there is an error is there?
What package did you try to install? What happens when you install the same package from console/ssh? -
Hello PiBa,
I'll start with what should be the easiest problem ~ Time
If I select the correct location with my city in America the time is off by (approx) 5~12 hours. I don't recall exactly because I tried so many locations which were close to my area to see if there was a difference. I then selected the CST6DST because that was pretty generic and should have put me for sure within the hour.
Nope . . .
I literally had to select etc/GMT +0 for the pfSense current time to reflect the correct time. >:(
My time zone should be Central -6 DST . . .
If you review the attachment at the upper left using the make belief time zone I placed myself in the time and date is correct. If you look at the NTP time below that is the time the system believes I'm using. For what ever reason(s) various programs seem to either reflect the make belief time I used to make it happen.
Or they will actually display times that make no sense or state the time and date are in the past?!?!
Come on its 2017 time keeping can't seriously be that difficult given all the resources and automated systems in place!! >:(
- The pfSense computer that hosts the software BIOS time is 100% correct and reflects reality.
- Every computer system in my home also reflect real world time, date, DST etc.
- Yet the pfSense software doesn't no matter what I do to compensate or correct for it.
I've scanned the forums dating back five years and there are dozens of threads about this so this is something that has never been fixed. At this point I can't trust the logs to provide me accurate details of events because they are off from 5~12 hours in the past or future. If I can't correct the time issue what's the point of moving forward with the rest of the problem(s)?!?!?
 -
Did you try this : use another browser / device that you didn't use before to connect to the GUI / pfSense ….
-
Have you selected an alternate time server?
I'm using a local one in the UK, and I select Europe London. It gets it perfectly and knows it's also BST.
-
I think reading this and your other thread(s), perhaps a clean install might help.
-
Did you try this : use another browser / device that you didn't use before to connect to the GUI / pfSense ….
Hello,
Yes I did same results.
-
@marjohn56:
Have you selected an alternate time server?
I'm using a local one in the UK, and I select Europe London. It gets it perfectly and knows it's also BST.
Just to summarize what I have done thus far:
- Added extra NTP servers - No joy
- Deleted all NTP servers but kept a local one - No joy
- Rebooted afterwards in case it was needed - No joy
- Stopped & Restarted the NTP service - No joy
- Used different computers & browsers - No joy
- Cleared broswer history, cookies, temporary data etc - No joy
- Selected other States / Provinces close to me - No joy
- Selected just a generic time zone like -6DST - No joy
- Confirmed actual computer BIOS time is correct - It is
- Confirmed user terminals date & time are accurate - They are
- Confirmed the pfsense NTP service is actually running and updating in the logs
Perhaps you're are right maybe a scratch install would help?!? At the moment I don't have the time to complete that task but it's on the to do list.
Thank you all!
-
Perhaps you're are right maybe a scratch install would help?!? At the moment I don't have the time to complete that task but it's on the to do list.
Thank you all!
It would have been quicker to do a re-install than all the messing about, that's for sure. :)
-
@marjohn56:
Perhaps you're are right maybe a scratch install would help?!? At the moment I don't have the time to complete that task but it's on the to do list.
Thank you all!
It would have been quicker to do a re-install than all the messing about, that's for sure. :)
LOL - Noted!! ;D
-
I wanted to update this post by saying the traffic graph is now working! :) Also the time has been corrected and have been able to use the actual drop down menu for my location. I have to gather this was fixed in the 2.4.2 release so that is two item off the list. Thank you to those hidden hero's who resolved this issue!
It would have been nice if someone would have chimed in as to what broke to cause these issues. I am working through the list to see if anything else is amiss.
Thank You!
