Fwd: freebsd-update(8) upgrade, install, install: files not found

[Graham Perrin]

 Forwarded Message 

Subject:freebsd-update(8) upgrade, install, install: files not found
Date:   Sat, 2 Apr 2022 15:28:33 +0100
From:   Graham Perrin 
To: questi...@freebsd.org



With the second run of /usr/sbin/freebsd-update install (after 
restarting the system), is it sometimes normal for freebsd-update to 
report files not found?


Screenshot:  ‒ the tail end of an 
upgrade from 13.0-RELEASE-p8 (userland p10) to 13.1-RC1.


The four files not found, including /etc/rc.d/zfskeys (more 
specifically: ///var/db/etcupdate/current/etc/rc.d/zfskeys) were files 
that did not exist prior to the upgrade.

Re: Fwd: freebsd-update(8) upgrade, install, install: files not found

[Glen Barber]

On Mon, Apr 04, 2022 at 06:14:27PM +0100, Graham Perrin wrote:
> With the second run of /usr/sbin/freebsd-update install (after restarting
> the system), is it sometimes normal for freebsd-update to report files not
> found?
> 
> Screenshot:  ‒ the tail end of an upgrade
> from 13.0-RELEASE-p8 (userland p10) to 13.1-RC1.
> 
> The four files not found, including /etc/rc.d/zfskeys (more specifically:
> ///var/db/etcupdate/current/etc/rc.d/zfskeys) were files that did not exist
> prior to the upgrade.

This seems normal, since the zfskeys script did not exist prior to RC1.

Glen



signature.asc
Description: PGP signature

FreeBSD on KVM, Q35 and kernel structure leak

[Eugene M. Zheganin]

Hello,

I'm trying to run FreeBSD 13.1-RC1 (releng/13.1-n250066-aef190f298a) on 
KVM/Qemu, presumably Q35 type VM in Hetzner.


After some uptime and considerable amount of connections, VM leaks 
tcp_inpcb to the limit:



ITEM   SIZE  LIMIT USED FREE  REQ FAILSLEEP 
XDOMAIN
tcp_inpcb:  496, 510671,  510281, 391, 617269,11530,   
0,   0



Causing multiple dmesg errors

sonewconn: pcb 0xf8001ac8bd90: pru_attach() failed
sonewconn: pcb 0xf8000ab625d0: pru_attach() failed
sonewconn: pcb 0xf8000af999b0: pru_attach() failed
sonewconn: pcb 0xf8000ab621f0: pru_attach() failed
sonewconn: pcb 0xf8000ab62000: pru_attach() failed
sonewconn: pcb 0xf8000ab625d0: pru_attach() failed
sonewconn: pcb 0xf8000af999b0: pru_attach() failed
sonewconn: pcb 0xf8000af999b0: pru_attach() failed
sonewconn: pcb 0xf8000af993e0: pru_attach() failed
sonewconn: pcb 0xf8000af999b0: pru_attach() failed
sonewconn: pcb 0xf8000ab627c0: pru_attach() failed


console errors (even on low number of kern.ipc.numopensockets: 1447)


[zone: tcp_inpcb] kern.ipc.maxsockets limit reached
[zone: tcp_inpcb] kern.ipc.maxsockets limit reached
[zone: tcp_inpcb] kern.ipc.maxsockets limit reached
[zone: tcp_inpcb] kern.ipc.maxsockets limit reached
[zone: tcp_inpcb] kern.ipc.maxsockets limit reached
[zone: tcp_inpcb] kern.ipc.maxsockets limit reached
[zone: tcp_inpcb] kern.ipc.maxsockets limit reached
[zone: tcp_inpcb] kern.ipc.maxsockets limit reached
[zone: tcp_inpcb] kern.ipc.maxsockets limit reached
[zone: tcp_inpcb] kern.ipc.maxsockets limit reached


and inability to connect to just anything:


# telnet 127.0.0.1 4080
Trying 127.0.0.1...
telnet: socket: No buffer space available


Even when the number of connections id dropped (for instance I remove 
this VM from balancing) it cannot recover (not freeing tcp_inpcb).



is there any hope considering this ?


Thanks.

Eugene.