@gertjan Sometimes it is worth mentioning the source, to get feedback from people having the same issues. We mention it happens to all the hardware from this supplier to let you guys know that it isn't a single one with a disk error or problem. Thanks in advance for constructive feedback ;)

I personally wouldn't open gui on the wan, unless you have a way to lock it down to your source IP... You prob be better VPN to pfsense, then hit the gui.. Problem with that is if problem with vpn you can not access gui to fix it ;)

If you know the source IP(s) that you will admin from, then you can allow access to gui port via a rule on your wan limiting it to these source IP(s).

This is why I put the worst case in quotes. ;-)

-Rico

Here is A example of some bad states. Notice how the states expires in 00:00:00
0_1547741022342_states6.PNG

Looking a bit more in detail, it's heavy disk write processes which seems to happen periodically since the update:

0_1547728757106_329fcc9c-0cd9-471f-98d3-8d1c4dfd7181-image.png

During the highly busy cycles it seems the writes are caused by the "php" process. Is there any way to track down which task causes php to perform these heavy writes?

Well, another factory reset and reinstall and ix3 has returned. Not entirely sure what that was all about.

Yes, we have a document for that:

https://www.netgate.com/docs/pfsense/solutions/sg-4860-1u/msata-installation.html

@rico
Yes, I've reinstalled it, the problem is still here.

No, that patch doesn't work. I haven't looked into turning that on in recent versions, that patch is super old.

A packet capture of the exchange should show you the certificates being sent between client and server.

@wgstarks said in Notification if update is available?:

There is also a script you can try-
https://forum.netgate.com/topic/137707/auto-update-check-checks-for-updates-to-base-system-packages-and-sends-email-alerts/1

Will send notifications for all pending updates. Not just the OS.

great, will have a look at that! thanks :-)

Which is why you really should list any and all packages you have installed in your OP...

@megs said in Consolmessage: Calcru : runtinme went backwards from 692usec to 494 usec for pid 0(kernel):

Calcru : runtinme went backwards from ....

It's a kernel issue (FreeBSD) : more info here : Calcru : runtime went backwards from kernel.

Chech your time settings, NTP, BIOS, VM, etc.

Btw : pfSense uses the FreeBSD kernel. This kernel is not developed here, but here.

OK, here's I fixed it.

From loader prompt, I used the command(s)

set kern.vty=sc
boot

note, using the set command is a temporary solution, read on...
this got me to the pfsense console

from there I accessed the shell and used the built in editor, vi, to edit the file located at /boot/loader.conf.local and added the line

set kern.vty=sc

which ensures this command is executed at each boot
saved my changes, rebooted

same to me...
wrong version in GUI after update to 2.4.4_2.
ssh --> 13 --> now everything is ok (2.4.4-RELEASE-p2)

I can confirm that with 2.4.4._2, it's now showing swap space again for me, whereas it had disappeared prior. I have 32G of ram, and thought that maybe it didn't need it, and/or I was losing my mind as to why it wasn't there. I could of sworn it was there in 2.4.3. :)

@teamits said in Change IP:

@pama said in Change IP:

The local IT has disconnected pfsense nics from vsphere

OK but then the symptom of slow web GUI and inability to access updates is to be expected. The slow GUI happens because DNS isn't working and each try must time out on all DNS servers before the GUI moves on.

I was assuming the NICs were being reconnected after the IP change.

Not sure where to go from here. The only issue I've had with changing IPs is the rebinding check not allowing the new LAN IP but I think that bug was fixed a while ago.

pfsense can query the dns without any problem...

Will install again then, just for sure, thanks!