SG-2100 23.01 update failed
-
@stephenw10 , haven't reinstalled it since purchase.
@netboy , just got my response from the ticket in less than 15min. Will try and follow the procedure requested soon. -
@netboy Mine was purchased from Netgate 1-18-2021 and never "reinstalled" since it was purchased.
-
@charliebrauw I’m not sure you can mount from there. The Marvell> prompt isn’t an OS per se and the “installer” on the 2100 isn’t the full/amd64 installer which has some rescue options.
Long ago I got in the habit of saving after every set of changes which also provides a history that is external to pfSense.
-
@steveits Since several are following this thread, looks like Netgate paused updates on 1100/2100: https://forum.netgate.com/post/1087901
-
@alleykat Me too...After I bought I never installed any new updates. Off course mine was bought last year
-
@stephenw10 This thread is a VERY good example of how to handle issues and customer support in the best possible way :-)
Not only are we now aware of what to lookout for, but you also get offers to help based on actual deployed hardware at different customers.
Please NEVER change your policy on issues handling so threads like these stop.I have spent to much time in my life with support from Cisco, Vmware, Microsoft and the likes on issues that do not officially exist (even though they are massively widespread), and it takes days to get eleveated high enough in support to talk to someone that might imply the product is not 100% flawless, and you might have hit an already know snag….
Keep up the good work.
-
-
I really should lock this thread...
@netboy @keyser Go read this post:
https://forum.netgate.com/topic/178049/pfsense-plus-23-01-updates-on-the-1100-and-2100-systems
-
So this happened. As discussed above, I ordered an M.2 SATA SSD to take over from the 'damaged' eMMC on my SG-2100. I installed it and started the USB recovery process with the 22.05 image, which I'd tried a few times previously, without success. It's worth noting that I'd left the router powered down for some minutes between attempts.
The process got to the point where it asked me to choose a device on which to install – mmcsd0 or ada0. I swear I meant to type ada0, as I knew the MMC isn't working. But I had a brain fart and just hit <return>, which defaulted to mmcsd0.
"Oh well," I thought. "I'll just let it fail and start again."
It didn't fail. It went right ahead and installed on the eMMC. To ensure this was what had actually happened, I removed the SSD card. Sure enough, it's working fine.
So now I have a spare SSD drive, a working (backup) SG-2100 and a new piece of advice. Before trying to reinstall firmware like this, first let the router have a nice, long lie down...
-
-
@mspeculatrix Well that's a development... However, since the MMC has already barked up the dead tree, I would not count on it going forward if uptime is important. It's very likely to croak again once you start hitting it with log writes.
And you already have the SSD now, so why not put it to good use? -
@rcoleman-netgate
Good to know netgate has stopped the update. I was not aware of this new info.
.Why close this thread?
You can keep us informed in this thread when the updates are resumed after issue has been resolved -
@netboy Why close? Because adding to it buries the important information.
We can always reopen a closed thread to put an update in -- like the one that Scott made about the 1100/2100 update freeze.
-
@mspeculatrix I would still run from the SSD. It's much faster than eMMC. It's noticable if you're doing anything that requires significant writes.
Steve
-
Referenced by S SteveITS
-
Referenced by S SteveITS
-
Referenced by S SteveITS
-
Referenced by S SteveITS
-
@stephenw10 I see the at the update Version 23.01 is available is showing up -- has this been thoroughly tested and can I go ahead and install the updates? Please advice
-
@netboy it’ll check for the small partition and stop if it can’t succeed.
There are a bunch of updates in the System Patches package released today.
-
Yes it has been tested extensively and will fail safely if it sees something that cannot be upgraded.
-
@stephenw10 said in SG-2100 23.01 update failed:
fail safely if it sees something that cannot be upgraded.
That gives me comfort! Let me try (I am scared though)
-
As with any upgrade make a backup of the config, have a plan in place to recover.
I wouldn't expect any issues though.
Steve
-
@stephenw10 Good advice. I ALWAYS backup the config file.....I am going to postpone the updates as my Daughter is doing her home work and my other half will KILL me if internet goes down....Shall try later
-
@netboy My update failed....Here is the screen shots
But it looks like if FAILED then RESTORE old is in place...because my router looks like ABORTED the updates
-
An authentication error part way through like that in unusual but could just be coincidence. I would reboot it and run the update again. It clearly passed the initial tests as it was already downloading the updates.
Steve
-
Did the following:
-
Reboot the router
-
Install 23.01 again
Then the following counter kept on counting for nearly 5 minutes or so .....
I did manual reboot Diagnostics -> Reboot
Was worried about "crash report"
Opened the link provided in the crash report and here is the screen shot: (looks benign to me - but not sure)
I then refreshed the URL and saw the notification bell icon and saw this message:
Now the screenshot looks like this
Should I be concerned?
-
-
@netboy said in SG-2100 23.01 update failed:
I did manual reboot Diagnostics -> Reboot
Don't do that, it may have been partially installed. https://redmine.pfsense.org/issues/14008. A 2100 could easily take 10-15 minutes. If you continue to have issues I suggest reinstalling clean.
-
@steveits said in SG-2100 23.01 update failed:
If you continue to have issues I suggest reinstalling clean.
OMG! What kind of issues will likely manifest ? How do I tell If I have issues....May be the message should be "explicit" and say "It might take up to 15 to 20 minutes to reboot"
Or
Do you suggest In reinstall clean by raising a ticket with the link you provided
-
@netboy said in SG-2100 23.01 update failed:
What kind of issues will likely manifest ? How do I tell If I have issues
I don't know...having booted up you must have been far enough along for it to, well, boot. 23.01 upgraded FreeBSD (12 to 14) and PHP (7 to 8) so had a lot of moving parts.
pfBlocker did have a version for 23.01 that threw an error during install but I believe that was resolved a few weeks ago. I usually follow the upgrade guide and uninstall pfBlocker before upgrading.
@netboy said in SG-2100 23.01 update failed:
say "It might take up to 15 to 20 minutes to reboot"
That was my suggestion in the Redmine. The problem with a fixed time is, it takes quite a bit longer on a slow CPU with slow/eMMC storage, than on a fast CPU with an SSD. Yet, "wait until finished" doesn't handle the new/rare case Netgate found themselves in with this version when older 1100/2100 with small EFI partitions were rendered unbootable, because it would wait forever. One can always look at the device console to see where it's at...if it's not remote.
Installing clean would be safest and is pretty easy. Burn the USB stick, copy to the 2100, and restore your config from backup.
-
That error is in the deinstall script and it's because it tries to run after php has been updated.
It was probably still reinstalling packages in the background.Once it's finished installing packages, check the system log, clear the errors and reboot. If they do not return you are good.
Steve
-
@stephenw10 said in SG-2100 23.01 update failed:
Once it's finished installing packages, check the system log, clear the errors and reboot. If they do not return you are good.
Great idea!
cleared system log and rebooted....
Here is the system log - I have masked sensitive info with xxxx otherwise to my eyes looks good. Do you see any issues?
Last 500 General Log Entries. (Maximum 500)
Mar 21 16:29:58 kernel ahci0: <AHCI SATA controller> mem 0xe0000-0xe1fff irq 26 on simplebus1
Mar 21 16:29:58 kernel ahci0: AHCI v1.30 with 1 6Gbps ports, Port Multiplier supported with FBS
Mar 21 16:29:58 kernel ahcich0: <AHCI channel> at channel 0 on ahci0
Mar 21 16:29:58 kernel armv8crypto0: <AES-CBC,AES-XTS,AES-GCM>
Mar 21 16:29:58 kernel Timecounters tick every 1.000 msec
Mar 21 16:29:58 kernel mvneta1: link state changed to UP
Mar 21 16:29:58 kernel ZFS filesystem version: 5
Mar 21 16:29:58 kernel ZFS storage pool version: features support (5000)
Mar 21 16:29:58 kernel usbus0: 5.0Gbps Super Speed USB v3.0
Mar 21 16:29:58 kernel usbus1: 480Mbps High Speed USB v2.0
Mar 21 16:29:58 kernel spibus0: <OFW SPI bus> on spi0
Mar 21 16:29:58 kernel mx25l0: <M25Pxx Flash Family> at cs 0 mode 0 on spibus0
Mar 21 16:29:58 kernel mx25l0: device type w25q32, size 4096K in 64 sectors of 64K, erase size 4K
Mar 21 16:29:58 kernel nxprtc0: registered as a time-of-day clock, resolution 0.015625s
Mar 21 16:29:58 kernel ugen1.1: <Marvell EHCI root HUB> at usbus1
Mar 21 16:29:58 kernel uhub0 on usbus1
Mar 21 16:29:58 kernel uhub0: <Marvell EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
Mar 21 16:29:58 kernel ugen0.1: <Generic XHCI root HUB> at usbus0
Mar 21 16:29:58 kernel uhub1 on usbus0
Mar 21 16:29:58 kernel uhub1: <Generic XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
Mar 21 16:29:58 kernel mmc0: Failed to set VCCQ for card at relative address 2
Mar 21 16:29:58 kernel mmcsd0: 8GB <MMCHC DG4008 0.1 SN 6FC19B20 MFG 10/2021 by 69 0x0000> at mmc0 50.0MHz/8bit/65535-block
Mar 21 16:29:58 kernel mmcsd0boot0: 4MB partition 1 at mmcsd0
Mar 21 16:29:58 kernel mmcsd0boot1: 4MB partition 2 at mmcsd0
Mar 21 16:29:58 kernel mmcsd0rpmb: 4MB partition 3 at mmcsd0
Mar 21 16:29:58 kernel CPU 0: ARM Cortex-A53 r0p4 affinity: 0
Mar 21 16:29:58 kernel Cache Type = <64 byte D-cacheline,64 byte I-cacheline,VIPT ICache,64 byte ERG,64 byte CWG>
Mar 21 16:29:58 kernel Instruction Set Attributes 0 = <CRC32,SHA2,SHA1,AES+PMULL>
Mar 21 16:29:58 kernel Instruction Set Attributes 1 = <>
Mar 21 16:29:58 kernel Instruction Set Attributes 2 = <>
Mar 21 16:29:58 kernel Processor Features 0 = <GIC,AdvSIMD,FP,EL3 32,EL2 32,EL1 32,EL0 32>
Mar 21 16:29:58 kernel Processor Features 1 = <>
Mar 21 16:29:58 kernel Memory Model Features 0 = <TGran4,TGran64,SNSMem,BigEnd,16bit ASID,1TB PA>
Mar 21 16:29:58 kernel Memory Model Features 1 = <8bit VMID>
Mar 21 16:29:58 kernel Memory Model Features 2 = <32bit CCIDX,48bit VA>
Mar 21 16:29:58 kernel Debug Features 0 = <DoubleLock,2 CTX BKPTs,4 Watchpoints,6 Breakpoints,PMUv3,Debugv8>
Mar 21 16:29:58 kernel Debug Features 1 = <>
Mar 21 16:29:58 kernel Auxiliary Features 0 = <>
Mar 21 16:29:58 kernel Auxiliary Features 1 = <>
Mar 21 16:29:58 kernel AArch32 Instruction Set Attributes 5 = <CRC32,SHA2,SHA1,AES+VMULL,SEVL>
Mar 21 16:29:58 kernel AArch32 Media and VFP Features 0 = <FPRound,FPSqrt,FPDivide,DP VFPv3+v4,SP VFPv3+v4,AdvSIMD>
Mar 21 16:29:58 kernel AArch32 Media and VFP Features 1 = <SIMDFMAC,FPHP DP Conv,SIMDHP SP Conv,SIMDSP,SIMDInt,SIMDLS,FPDNaN,FPFtZ>
Mar 21 16:29:58 kernel CPU 1: ARM Cortex-A53 r0p4 affinity: 1
Mar 21 16:29:58 kernel Release APs...done
Mar 21 16:29:58 kernel Trying to mount root from zfs:pfSense/ROOT/default []...
Mar 21 16:29:58 kernel uhub1: 2 ports with 2 removable, self powered
Mar 21 16:29:58 kernel e6000sw0port1: link state changed to DOWN
Mar 21 16:29:58 kernel e6000sw0port2: link state changed to DOWN
Mar 21 16:29:58 kernel e6000sw0port3: link state changed to DOWN
Mar 21 16:29:58 kernel e6000sw0port4: link state changed to DOWN
Mar 21 16:29:58 kernel uhub0: 1 port with 1 removable, self powered
Mar 21 16:29:58 kernel ugen1.2: <American Power Conversion Back-UPS ES 750G FW:841.I4 .D USB FW:I4> at usbus1
Mar 21 16:29:58 kernel Root mount waiting for: usbus1 CAM
Mar 21 16:29:58 kernel e6000sw0port1: link state changed to UP
Mar 21 16:29:58 kernel e6000sw0port2: link state changed to UP
Mar 21 16:29:58 kernel Root mount waiting for: CAM
Mar 21 16:29:58 kernel e6000sw0port3: link state changed to UP
Mar 21 16:29:58 kernel e6000sw0port4: link state changed to UP
Mar 21 16:29:58 kernel Root mount waiting for: CAM
Mar 21 16:29:58 kernel Root mount waiting for: CAM
Mar 21 16:29:58 kernel Root mount waiting for: CAM
Mar 21 16:29:58 kernel Root mount waiting for: CAM
Mar 21 16:29:58 kernel Root mount waiting for: CAM
Mar 21 16:29:58 kernel Root mount waiting for: CAM
Mar 21 16:29:58 kernel random: unblocking device.
Mar 21 16:29:58 kernel ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
Mar 21 16:29:58 kernel ada0: <ATP SATA III M.2 2242 SBFMB1.1> ACS-4 ATA SATA 3.x device
Mar 21 16:29:58 kernel ada0: Serial Number xxxxxxxxxxxxxxxx
Mar 21 16:29:58 kernel ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
Mar 21 16:29:58 kernel ada0: Command Queueing enabled
Mar 21 16:29:58 kernel ada0: 30533MB (62533296 512 byte sectors)
Mar 21 16:29:58 kernel lo0: link state changed to UP
Mar 21 16:29:58 check_reload_status 430 Linkup starting $e6000sw0port1
Mar 21 16:29:58 kernel e6000sw0port1: link state changed to DOWN
Mar 21 16:29:58 check_reload_status 430 Linkup starting $e6000sw0port2
Mar 21 16:29:58 kernel e6000sw0port2: link state changed to DOWN
Mar 21 16:29:58 kernel e6000sw0port3: link state changed to DOWN
Mar 21 16:29:58 check_reload_status 430 Linkup starting $e6000sw0port3
Mar 21 16:29:58 check_reload_status 430 Linkup starting $e6000sw0port4
Mar 21 16:29:58 kernel e6000sw0port4: link state changed to DOWN
Mar 21 16:29:58 php-cgi 434 rc.bootup: calling interface_dhcpv6_configure.
Mar 21 16:29:58 kernel vlan0: changing name to 'mvneta1.4084'
Mar 21 16:29:58 kernel mvneta0: link state changed to UP
Mar 21 16:29:58 check_reload_status 430 Linkup starting mvneta0
Mar 21 16:29:58 php-cgi 434 rc.bootup: Accept router advertisements on interface mvneta0
Mar 21 16:29:58 php-cgi 434 rc.bootup: Starting DHCP6 client for interfaces mvneta0 in DHCP6 without RA mode
Mar 21 16:29:58 php-cgi 434 rc.bootup: Starting rtsold process on wan(mvneta0)
Mar 21 16:29:59 sshd 14738 Server listening on :: port 22.
Mar 21 16:29:59 sshd 14738 Server listening on 0.0.0.0 port 22.
Mar 21 16:29:59 sshguard 15357 Now monitoring attacks.
Mar 21 16:30:01 kernel done.
Mar 21 16:30:01 check_reload_status 430 Linkup starting $e6000sw0port2
Mar 21 16:30:01 kernel e6000sw0port2: link state changed to UP
Mar 21 16:30:01 kernel e6000sw0port3: link state changed to UP
Mar 21 16:30:01 check_reload_status 430 Linkup starting $e6000sw0port3
Mar 21 16:30:01 php-cgi 434 rc.bootup: Resyncing OpenVPN instances.
Mar 21 16:30:01 kernel pflog0: promiscuous mode enabled
Mar 21 16:30:02 kernel ....
Mar 21 16:30:02 xinetd 29517 xinetd Version 2.3.15 started with libwrap loadavg options compiled in.
Mar 21 16:30:02 xinetd 29517 Started working: 401 available services
Mar 21 16:30:02 check_reload_status 430 Linkup starting $e6000sw0port1
Mar 21 16:30:02 kernel e6000sw0port1: link state changed to UP
Mar 21 16:30:02 kernel e6000sw0port4: link state changed to UP
Mar 21 16:30:02 check_reload_status 430 Linkup starting $e6000sw0port4
Mar 21 16:30:05 php-cgi 434 rc.bootup: Default gateway setting ISP GW as default.
Mar 21 16:30:05 php-cgi 434 rc.bootup: Gateway, none 'available' for inet6, use the first one configured. 'WAN_DHCP6'
Mar 21 16:30:05 kernel done.
Mar 21 16:30:06 php-cgi 434 rc.bootup: Unbound start waiting on dhcp6c.
Mar 21 16:30:08 php-cgi 434 rc.bootup: Unbound start waiting on dhcp6c.
Mar 21 16:30:09 php-cgi 434 rc.bootup: Unbound start waiting on dhcp6c.
Mar 21 16:30:10 php-cgi 434 rc.bootup: Unbound start waiting on dhcp6c.
Mar 21 16:30:11 php-cgi 434 rc.bootup: Unbound start waiting on dhcp6c.
Mar 21 16:30:12 php-cgi 434 rc.bootup: Unbound start waiting on dhcp6c.
Mar 21 16:30:13 php-cgi 434 rc.bootup: Unbound start waiting on dhcp6c.
Mar 21 16:30:14 php-cgi 434 rc.bootup: Unbound start waiting on dhcp6c.
Mar 21 16:30:15 php-cgi 434 rc.bootup: Unbound start waiting on dhcp6c.
Mar 21 16:30:16 php-cgi 434 rc.bootup: Unbound start waiting on dhcp6c.
Mar 21 16:30:18 php-cgi 434 rc.bootup: sync unbound done.
Mar 21 16:30:18 kernel done.
Mar 21 16:30:19 kernel done.
Mar 21 16:30:25 kernel done.
Mar 21 16:30:25 php-cgi 434 rc.bootup: NTPD is starting up.
Mar 21 16:30:25 kernel done.
Mar 21 16:30:26 kernel done.
Mar 21 16:30:27 kernel done.
Mar 21 16:30:27 check_reload_status 430 Updating all dyndns
Mar 21 16:30:28 kernel .
Mar 21 16:30:28 xinetd 29517 Starting reconfiguration
Mar 21 16:30:28 kernel ...
Mar 21 16:30:28 xinetd 29517 Swapping defaults
Mar 21 16:30:28 xinetd 29517 readjusting service 19000-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19001-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19002-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19003-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19004-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19005-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19006-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19007-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19008-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19009-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19010-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19011-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19012-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19013-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19014-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19015-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19016-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19017-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19018-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19019-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19020-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19021-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19022-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19023-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19024-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19025-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19026-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19027-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19028-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19029-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19030-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19031-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19032-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19033-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19034-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19035-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19036-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19037-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19038-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19039-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19040-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19041-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19042-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19043-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19044-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19045-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19046-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19047-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19048-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19049-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19050-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19051-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19052-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19053-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19054-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19055-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19056-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19057-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19058-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19059-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19060-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19061-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19062-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19063-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19064-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19065-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19066-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19067-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19068-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19069-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19070-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19071-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19072-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19073-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19074-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19075-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19076-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19077-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19078-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19079-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19080-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19081-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19082-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19083-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19084-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19085-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19086-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19087-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19088-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19089-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19090-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19091-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19092-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19093-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19094-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19095-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19096-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19097-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19098-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19099-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19100-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19101-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19102-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19103-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19104-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19105-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19106-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19107-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19108-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19109-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19110-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19111-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19112-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19113-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19114-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19115-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19116-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19117-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19118-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19119-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19120-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19121-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19122-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19123-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19124-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19125-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19126-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19127-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19128-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19129-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19130-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19131-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19132-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19133-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19134-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19135-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19136-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19137-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19138-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19139-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19140-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19141-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19142-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19143-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19144-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19145-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19146-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19147-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19148-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19149-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19150-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19151-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19152-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19153-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19154-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19155-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19156-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19157-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19158-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19159-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19160-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19161-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19162-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19163-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19164-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19165-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19166-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19167-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19168-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19169-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19170-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19171-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19172-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19173-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19174-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19175-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19176-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19177-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19178-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19179-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19180-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19181-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19182-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19183-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19184-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19185-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19186-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19187-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19188-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19189-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19190-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19191-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19192-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19193-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19194-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19195-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19196-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19197-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19198-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19199-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19200-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19201-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19202-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19203-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19204-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19205-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19206-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19207-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19208-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19209-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19210-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19211-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19212-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19213-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19214-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19215-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19216-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19217-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19218-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19219-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19220-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19221-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19222-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19223-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19224-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19225-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19226-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19227-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19228-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19229-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19230-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19231-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19232-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19233-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19234-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19235-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19236-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19237-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19238-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19239-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19240-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19241-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19242-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19243-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19244-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19245-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19246-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19247-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19248-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19249-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19250-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19251-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19252-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19253-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19254-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19255-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19256-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19257-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19258-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19259-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19260-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19261-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19262-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19263-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19264-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19265-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19266-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19267-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19268-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19269-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19270-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19271-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19272-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19273-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19274-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19275-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19276-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19277-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19278-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19279-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19280-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19281-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19282-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19283-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19284-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19285-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19286-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19287-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19288-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19289-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19290-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19291-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19292-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19293-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19294-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19295-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19296-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19297-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19298-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19299-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19300-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19301-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19302-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19303-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19304-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19305-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19306-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19307-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19308-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19309-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19310-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19311-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19312-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19313-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19314-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19315-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19317-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19321-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19324-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19326-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19328-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19330-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19331-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19333-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19335-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19336-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19337-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19338-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19339-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19340-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19341-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19342-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19347-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19349-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19351-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19353-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19355-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19357-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19358-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19364-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19366-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19367-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19369-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19372-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19374-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19376-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19380-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19383-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19385-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19387-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19389-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19391-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19393-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19397-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19400-tcp
Mar 21 16:30:30 php-fpm 382 /rc.dyndns.update: phpDynDNS (xxxxx): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
Mar 21 16:30:31 kernel .
Mar 21 16:30:31 php-cgi 434 rc.bootup: The command '/usr/local/sbin/strongswanrc stop' returned exit code '1', the output was 'strongswan not running? (check /var/run/daemon-charon.pid).'
Mar 21 16:30:31 kernel done.
Mar 21 16:30:32 php-fpm 383 /index.php: Successful login for user 'admin' from: 192.168.0.73 (Local Database)
Mar 21 16:30:32 sshguard 35075 Now monitoring attacks.
Mar 21 16:30:36 php-cgi 434 rc.bootup: Creating rrd update script
Mar 21 16:30:36 kernel done.
Mar 21 16:30:38 syslogd exiting on signal 15
Mar 21 16:30:39 syslogd kernel boot file is /boot/kernel/kernel
Mar 21 16:30:39 kernel done.
Mar 21 16:30:42 php-fpm 383 /rc.start_packages: Restarting/Starting all packages.
Mar 21 16:30:43 lighttpd_pfb 42463 [pfBlockerNG] DNSBL Webserver stopped
Mar 21 16:30:43 lighttpd_pfb 44255 [pfBlockerNG] DNSBL Webserver started
Mar 21 16:30:44 php-cgi 11385 notify_monitor.php: Message sent to xxxx -
Nothing there looks like a problem.
I would argue there's probably a better way to handle whatever you're doing with those 400 ports. NAT+Proxy reflection I assume?
Steve
-
@stephenw10 said in SG-2100 23.01 update failed:
400 ports. NAT+Proxy reflection I assume?
Stehenw10, This is "greek" to me :-)
When I bought netgate 2100, I knew the functionality what I wanted and you (thanks a ton) and the great folks in this forum helped me when I asked the right questions.
Can you kindly elaborate 400 ports what do you mean by stating "400 ports. NAT+Proxy reflection I assume?"
-
@netboy said in SG-2100 23.01 update failed:
Mar 21 16:30:28 xinetd 29517 readjusting service 19391-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19393-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19397-tcp
Mar 21 16:30:28 xinetd 29517 readjusting service 19400-tcpThose log lines are each a service listening on a different port. Almost certainly thats NAT reflection for a forwarded range of ports running in NAT+Proxy mode.
https://docs.netgate.com/pfsense/en/latest/nat/reflection.html#configuring-nat-reflection
It's usually better to avoid that and can almost always isn't needed. However if it's working for it's fine to use it.
Steve
