Post DR package repo not available in 2.7.2
-
If you put the backup on the root of a fat32 formatted USB driev and name it config.xml it will be found by the installer.
For backwards compatibility it also looks in /conf on the USB drive.
https://docs.netgate.com/pfsense/en/latest/backup/restore-during-install.html#restore-configuration-from-usb-during-installRemember to remove the USB drive because it will also look for configs there at every boot via the ECL:
https://docs.netgate.com/pfsense/en/latest/backup/restore-during-install.html#restore-using-the-external-configuration-locator-ecl -
The config section for installed packages should just be:
<installedpackages>
</installedpackages>correct?
the pkg-repoc command is finally returning something now:
/root: pfSense-repoc pfSense-repoc: failed to fetch the repo data failed to read the repo data. -
Hmm, that seems like a general connectivity failure. Other systems behind pfSense are not seeing any issues?
-
No connection issues that I can determine.
Email is slower than I'd like, but ...I'm connecting through it right now.
-
Hmm, if there's nothing in the system log check the nginx logs then. There must be something erroring out.
-
@stephenw10
Quick run through the logs doesn't show anything odd other than sshguard going up and down extremely frequently, and ntp logs showing an out of sync condition when I don't think it should.I did tar up /var/log for a closer look later.
-
If ssh guard is being restarted very often that means at least one of the logs is being rotated often. And that implies something is happening that's generating a lot of logs.
Check the logs (
ls -ls /var/log) so see which log is rotating and what's in it.Steve
-
@stephenw10
nginx, filter and gateways logs have rotated more than others but the filter log looks like it does so more frequently.rw------- 1 root wheel 144457 Feb 1 07:36 auth.log -rw-r--r-- 1 root wheel 44790 Jan 29 08:39 bsdinstall_log -rw------- 1 root wheel 410497 Feb 1 07:35 dhcpd.log -rw------- 1 root wheel 14347 Jan 31 17:00 dhcpd.log.0.bz2 -rw------- 1 root wheel 16915 Jan 30 20:35 dhcpd.log.1.bz2 -rw-r--r-- 1 root wheel 15164 Jan 31 05:46 dmesg.boot -rw------- 1 root wheel 437599 Feb 1 07:36 filter.log -rw------- 1 root wheel 23772 Feb 1 07:34 filter.log.0.bz2 -rw------- 1 root wheel 23153 Feb 1 07:31 filter.log.1.bz2 -rw------- 1 root wheel 23168 Feb 1 07:28 filter.log.2.bz2 -rw------- 1 root wheel 23363 Feb 1 07:25 filter.log.3.bz2 -rw------- 1 root wheel 23705 Feb 1 07:22 filter.log.4.bz2 -rw------- 1 root wheel 23334 Feb 1 07:19 filter.log.5.bz2 -rw------- 1 root wheel 23087 Feb 1 07:16 filter.log.6.bz2 -rw------- 1 root wheel 503608 Feb 1 07:11 gateways.log -rw------- 1 root wheel 8957 Jan 30 03:44 gateways.log.0.bz2 -rw------- 1 root wheel 8032 Jan 30 02:44 gateways.log.1.bz2 -rw------- 1 root wheel 8120 Jan 30 01:46 gateways.log.2.bz2 -rw------- 1 root wheel 8103 Jan 30 00:48 gateways.log.3.bz2 -rw------- 1 root wheel 7979 Jan 29 23:50 gateways.log.4.bz2 -rw------- 1 root wheel 7617 Jan 29 22:52 gateways.log.5.bz2 -rw------- 1 root wheel 7791 Jan 29 21:54 gateways.log.6.bz2 -rw------- 1 root wheel 0 Jan 31 05:45 ipsec.log -rw------- 1 root wheel 0 Jan 31 05:45 l2tps.log -rw-r--r-- 1 root wheel 0 Jan 29 10:53 lastlog drwxr-xr-x 2 root wheel 3 Jan 29 09:18 nginx -rw------- 1 root wheel 334891 Feb 1 07:33 nginx.log -rw------- 1 root wheel 10109 Jan 31 19:53 nginx.log.0.bz2 -rw------- 1 root wheel 10127 Jan 31 19:21 nginx.log.1.bz2 -rw------- 1 root wheel 10021 Jan 31 18:49 nginx.log.2.bz2 -rw------- 1 root wheel 10032 Jan 31 18:17 nginx.log.3.bz2 -rw------- 1 root wheel 10079 Jan 31 17:45 nginx.log.4.bz2 -rw------- 1 root wheel 10014 Jan 31 17:13 nginx.log.5.bz2 -rw------- 1 root wheel 10562 Jan 31 16:41 nginx.log.6.bz2 drwxr-xr-x 2 root wheel 2 Jan 29 09:18 ntp -rw------- 1 root wheel 351580 Jan 31 06:43 ntpd.log -rw------- 1 root wheel 0 Jan 31 05:45 openvpn.log -rw------- 1 root wheel 0 Jan 31 05:45 poes.log -rw------- 1 root wheel 0 Jan 31 05:45 portalauth.log -rw------- 1 root wheel 0 Jan 31 05:45 ppp.log -rw------- 1 root wheel 265790 Feb 1 07:33 resolver.log -rw------- 1 root wheel 11140 Jan 30 08:02 resolver.log.0.bz2 -rw------- 1 root wheel 0 Jan 31 05:45 routing.log -rw------- 1 root wheel 41041 Feb 1 07:36 system.log -rw------- 1 root wheel 35445 Jan 31 21:00 system.log.0.bz2 -rw------- 1 root wheel 6318 Jan 31 05:46 userlog -rw-r--r-- 1 root wheel 394 Feb 1 07:36 utx.lastlogin -rw------- 1 root wheel 1555 Feb 1 07:36 utx.log -rw------- 1 root wheel 0 Jan 31 05:45 vpn.log -rw------- 1 root wheel 0 Jan 31 05:45 wireless.log -
I have two gateways for this firewall -- the default to the WAN and another interface that routes to another pfsense firewall in another building.
It's a 10G link between buildings for backups and access to the private network there.This hopefully doesn't affect anything as it worked without issues with 2.6.x virtualized -- maybe some logging setting is wrong for the private gateway?
-
I see a lot of this in the firewall logs:
-
Yeah that's rotating every few minutes. Unless you have very limited disk space I would set the firewall log larger so it rotates less frequetly and disable log compression so it isn't taxing the CPU each time.
You might also consider changing the ruleset to log less depending on what it's logging.
-
I'll do that and pursue the question of why the firewall is being flooded from that private IP range with the ISP ...
I've got overly large disk space for this firewall so I bumped log size from 512000 to 5120000 an turned off compression.
Filesystem Size Used Avail Capacity Mounted on pfSense/var/log 729G 825K 729G 0% /var/log -
Ah, nice. Well it would be trivial to add a block rule for just UDP port 10002 without logging enabled. That traffic is odd though I agree.
-
@stephenw10
I reinstalled, but the recovery of the configuration via config.xml in either the root or a copy on /conf (of a fat32 formatted USB stick) doesn't work.
I had to configure wan and lan, connect an restore through the GUI.
back to not being able to even get a list of available packages in the GUI. :/I just saw a noticed the little alarm bell is lit up:
The config file I restored had this for packages:
<installedpackages>
</installedpackages>What could have possibly re-installed?
-
pfSense-repoc
pfSense-repoc: failed to fetch the repo data
failed to read the repo data.I really used to like pfsense but I really am starting to get discouraged.
-
@MakOwner
Speaking of disappointments, where do you file bugs?
You can't position widgets on the dashboard at the bottom of a column.
Widgets will only "stick" in a column above another widget. -
@MakOwner
I should probably start another thread over this...
I installed apcupsd using the cli.
Installed nice and quick.Getting it to work on the other hand ...
What's the magic?I have an APC RM 2200 connected via USB.
I have no issues with USB connection (using the same cable) to linux desktop...
I miss the good old days when things worked :/
-
What does
pkg-static -d updateshow?Does the config actually contain any installed packages? I've never seen that report success when it couldn't reach the package server.
How did you format the USB drive? I've noticed Windows will try to use some proprietary format if you're not careful.
Steve
-
We use redmine for bug reports: https://redmine.pfsense.org/
-
This post is deleted!
