Jesus tapdancing Christ! With the net-snmp update you get disk drive temperatures via SNMP!
5 Likes
Re: VNC problems …
So yesterday I learned that you cannot open just any TCP socket from a JS application running in a browser. So a browser based “VNC client” needs to open a websocket connection to some sort of websocket to TCP proxy.
This is consistent with the debug output I got from DTrace - lots of “websockify” calls going on, when you start a VM.
Which still does not quite explain why the extra “vncserver” option had to be added to bhyve instead of sticking to plain “tcp” in that part of the entire stack.
I’ll try to find and study the source code next.
1 Like
iocage upgrade **jailname** -r 13.3-RELEASE
is this the correct way to upgrade the jail? I have tried on a simple caddy jail and tooks a lot of time, continuily asking for “reasonable” things 
im kinda worried when gonna upgrade more complex jails.
Sorry if is a newbie question, but is the first time had to perform this action
If 13.3-RELEASE was already “fetched”, you should technically be good to go. I would create a recursive snapshot of <poolname>/iocage/jails/<jailname> before proceeding. Although, I believe it automatically creates a snapshot for you when invoking the “upgrade” command.
Was this originally created as a “base jail” or “clone jail”?
1 Like
13.3-RELEASE already fetched, and got backup on another disk plus replicated the jails pool on external disk 
Was this originally created as a “base jail” or “clone jail”?
Good question, i really dont remember (most of the jail i have are build from scripts), there is a way to know? How it impact on upgrade?
Because im stuck there:
I suggest opening a linked thread (but there are dedicated threads on the old forum).
iocage list -l
“Base jails” are much easier to maintain and upgrade. They are not tethered to the original release in which they were created.
What is “stuck”?
root@truenas[~]# iocage list -l
+------+---------------+------+-------+------+-----------------+------------------------+-----+----------+----------+
| JID | NAME | BOOT | STATE | TYPE | RELEASE | IP4 | IP6 | TEMPLATE | BASEJAIL |
+======+===============+======+=======+======+=================+========================+=====+==========+==========+
| 34 | Gotenberg | off | up | jail | 13.3-RELEASE-p4 | vnet0|192.168.1.63 | - | - | no |
+------+---------------+------+-------+------+-----------------+------------------------+-----+----------+----------+
| 1 | Heimdallv3 | on | up | jail | 13.2-RELEASE-p9 | vnet0|192.168.1.79/24 | - | - | no |
+------+---------------+------+-------+------+-----------------+------------------------+-----+----------+----------+
| None | JDownloader | off | down | jail | 13.2-RELEASE-p9 | 192.168.1.172 | - | - | no |
+------+---------------+------+-------+------+-----------------+------------------------+-----+----------+----------+
| 2 | NextCloud | on | up | jail | 13.2-RELEASE-p9 | vnet0|192.168.1.200/24 | - | - | no |
+------+---------------+------+-------+------+-----------------+------------------------+-----+----------+----------+
| 24 | Paperless-NGX | off | up | jail | 13.3-RELEASE-p4 | vnet0|192.168.1.65 | - | - | no |
+------+---------------+------+-------+------+-----------------+------------------------+-----+----------+----------+
| 23 | Tika | off | up | jail | 13.3-RELEASE-p4 | vnet0|192.168.1.64 | - | - | no |
+------+---------------+------+-------+------+-----------------+------------------------+-----+----------+----------+
| 9 | Wireguard | off | up | jail | 13.2-RELEASE-p9 | vnet0|172.16.0.2/30 | - | - | no |
+------+---------------+------+-------+------+-----------------+------------------------+-----+----------+----------+
| None | caddy | on | down | jail | 13.2-RELEASE-p9 | vnet0|192.168.1.151/24 | - | - | no |
+------+---------------+------+-------+------+-----------------+------------------------+-----+----------+----------+
| 4 | navidrome | on | up | jail | 13.2-RELEASE-p9 | vnet0|192.168.1.135 | - | - | no |
+------+---------------+------+-------+------+-----------------+------------------------+-----+----------+----------+
| 5 | photoprism | on | up | jail | 13.2-RELEASE-p9 | vnet0|192.168.1.130/24 | - | - | no |
+------+---------------+------+-------+------+-----------------+------------------------+-----+----------+----------+
| 6 | pms | on | up | jail | 13.2-RELEASE-p9 | vnet0|192.168.1.75/24 | - | - | yes |
+------+---------------+------+-------+------+-----------------+------------------------+-----+----------+----------+
| 7 | tautulli | on | up | jail | 13.2-RELEASE-p9 | vnet0|192.168.1.76/24 | - | - | no |
+------+---------------+------+-------+------+-----------------+------------------------+-----+----------+----------+
| 8 | vaultwarden | on | up | jail | 13.2-RELEASE-p9 | vnet0|192.168.1.152/24 | - | - | no |
+------+---------------+------+-------+------+-----------------+------------------------+-----+----------+----------+
i will have hard time
i mean blocked
I meant as in “What’s wrong with the screenshot?” I don’t see any errors. Just a list of files.
no progress on installation after that point, just that END (and the jail go up again, same 13-2 release)
Command is actually iocage upgrade -r 13.3-RELEASE jailname
Don’t forget “y” and the prompts, and “q” at some point at the end.
2 Likes
Good catch! Assuming it’s not a typo in the forums.
The system is just displaying you a bit of information using a pager utility like “more” or GNU equivalent “less”.
Just hit the Q key to leave that and let the upgrade continue.
1 Like
Just updated and ran into the issue with mpr0: Out of chain frames, consider increasing hw.mpr.max_chains. turning off the power supply for 30 seconds allowed the update to proceed though and it seems to be running alright now. @kris is this anything that you guys have seen before?
Not run into that before. Might be a tuning we need to consider adjusting, but offhand I’m not sure what chain frames settings will impact. Has anybody investigated this on the driver side to see what the impact is of adjusting this value from its defaults?
A bit of archeology dug up the following:
And a bit more dug up the following which sounds like what I am experiencing:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243225
Updated apparently withouth any issues. Will now try to update my jails… if I remember how, maybe I need to go search on the old forum yup, I love iocage.
No issue whatsoever, updated all my jails to 13.3-RELEASE-p4.
1 Like
Do you need to keep the old versions in the download folder under iocage after you upgrade the jails and all is working fine?
Nope.
1 Like