pfsense log error
-
Hİ,
I reinstalled the pfsense environment and reverted to the config via the old full backup. After that, these errors are repeated in the log file.
15:40:04 pf root[35361]: /usr/sbin/service: WARNING: $expiretable_enable is not set properly - see rc.conf(5).
Apr 9 15:40:04 pf root[52858]: /usr/sbin/service: WARNING: $microcode_update_enable is not set properly - see rc.conf(5).
Apr 9 15:40:05 pf root[72074]: /usr/sbin/service: WARNING: $mpd_enable is not set properly - see rc.conf(5).
Apr 9 15:40:06 pf root[74298]: /usr/sbin/service: WARNING: $dhcp6c_enable is not set properly -What can I do about this
Thanks. -
@SpaceXTexnologiya said in pfsense log error:
expiretable_enable
These messages show up after you imported your own config.xml ?
If so (although I doubt) : reset back to default, don't use that file anymore.@SpaceXTexnologiya said in pfsense log error:
Apr 9 15:40:04 pf root[52858]: /usr/sbin/service: WARNING: $microcode_update_enable is not set properly - see rc.conf(5)
Check for yourself the file /usr/local/etc/rc.d/microcode_update
The value "$$microcode_update_enable" is set : line 72 :: ${microcode_update_enable="NO"}Same for expiretable_enable, $mpd_enable and $dhcp6c_enable : these are not used at all by pfSense at all. pfSEnse doesn't 'use' rc.conf.
Where did you get your pfSense installer from ?
-
@Gertjan hi,
thanks for replyI didn't check before but I noticed these errors after returning to my config file. I was using the same config file before and I didn't get these errors.
Where did you get your pfSense installer from ?
downloaded from this address : https://repo.ialab.dsu.edu/pfsense/ -
@Gertjan
Check for yourself the file /usr/local/etc/rc.d/microcode_update
The value "$$microcode_update_enable" is set : line 72 :the value was set this way, I did not change it;
: ${microcode_update_enable="NO"}
: ${microcode_update_datadir="/usr/local/share/cpucontrol"}
: ${microcode_update_cpus="ALL"}
: ${microcode_update_flags=""} -
You might see those after upgrading because pfSense doesn't use the FreeBSD RC system.
-
@stephenw10 said in pfsense log error:
BSD RC system.
Hi @stephenw10
Should I ignore these errors?
After reinstalling, the interruptions continue on pfsense. I'm really tired of not being able to solve this. It gets better after a restart but then it cuts out again and I have to restart pfsense again -
Those warnings are expected after installing pkgs which is what happens at upgrade or a clean install with the net installer. They are unrelated to the connection issues.
-
@SpaceXTexnologiya said in pfsense log error:
Where did you get your pfSense installer from ?
downloaded from this address : https://repo.ialab.dsu.edu/pfsense/What I wouldn’t do is download it from some place on the Internet.
https://docs.netgate.com/pfsense/en/latest/install/index.html -
-
No AI or card needed : Google : pfSense download
The very first link is the official answer.
-
@Gertjan said in pfsense log error:
No AI or card needed : Google : pfSense download
The very first link is the official answer.
Card information requested
-
@SpaceXTexnologiya nope, you'll need an Netgate store account but since the cost is 0.- you won't need to enter any card information.
Login, add to card, checkout and download.
-
Or, for now at least, just use the legacy installer for CE.
-
@SpaceXTexnologiya said in pfsense log error:
Card information requested
I added 2.7.2 to the list, and checked out.
I reached :
and could summit here to finalize the transaction.
Was somewhat 'hoping' to see the question "Give your Visa number of the 0 $ transaction .." but didn't saw it
That is, This was valid for me, ordering from France. -
@Gertjan @stephenw10 @patient0
I made the download.
Thank you for your help.
I have installed Pfsense but these errors persist, Pfsense cuts off access for no reason, it only recovers after a reboot.
Unfortunately I have not found a solution to this problem. Does anyone have the same problem?
version 2.7.2 -
@SpaceXTexnologiya said in pfsense log error:
these errors persist, Pfsense cuts off access for no reason ...
That's not much to work with.
Remember : we don't see the screen you're looking at. Neither how you install, on what hardware, etc. -
Yes we need more information to diagnose this. Still this? https://forum.netgate.com/topic/189542/pfsense-access-interruption
If so I suggest continuing there.
But if you're running in hyper-V still check for the reported hveventX issue: https://forum.netgate.com/post/1207821
