Register for the iXsystems Community to get an ad-free experience and exclusive discounts in our eBay Store.

TrueCommand 1.3 is now available!

Western Digital Drives - The Preferred Drives of FreeNAS and TrueNAS CORE

Kris Moore

VP of Engineering
Administrator
Moderator
iXsystems
Joined
Nov 12, 2015
Messages
620
FreeNAS and TrueNAS Fans,

We are pleased to announce that TrueCommand 1.3 is now available!

This is a significant update to the TrueCommand user interface, as well as adding new metrics, alerts for SMR drives, pool usage estimates, and more.

The release announcement with additional details about this update can be found here: https://www.ixsystems.com/blog/library/truecommand-1-3/

Along with TrueCommand 1.3, we are pleased to announce early-access availability of the TrueCommand Cloud Service. The cloud service requires managed TrueNAS systems to be version 12.0-BETA1 or newer, and user access requires connection to a Wireguard VPN. Please contact us if you wish to participate in this service!

To download this release:
  • Login to the TrueCommand Account Portal for downloads, documentation links, and licensing options.
  • For storage clusters with more than 50 disks, the account portal also offers a free 60-day trial license with unlimited disks.

To update to this release:
  • Docker: Re-run “docker pull ixsystems/truecommand” to fetch the latest version of TrueCommand, and then restart your docker instance.
  • VM Image: Either reboot the VM or run “systemctl restart truecommand.service”. This will automatically fetch and start the latest docker image of TrueCommand within your VM.
 

sretalla

Wizened Sage
Joined
Jan 1, 2016
Messages
3,931
Wow! that looks very different to 1.2...
Still working through it to see what's really changed, but it's a BIG surprise initially.
 

sretalla

Wizened Sage
Joined
Jan 1, 2016
Messages
3,931
A few comments:

Not sure if there's something more to do with permissions, but I wasn't able to set the autostart property of a VM like it seems I should be able to in the UI.

Also, it would be great to not make the jails and VMs red if the not started ones are not set to autostart. (I don't like seeing red if the situation is normal/expected)

The redness on the pool count doesn't carry through to the pool itself (if I have 2 pools, so pools 2 shows in red, but then only one of those pools is full... neither of them shows anything in the subsequent click-throughs... both just show a green tick).

I also saw an impact from SMART failures where on the front screen, all disks are shown to be failing SMART, but in the click through I see 2 of 8 with SMART failures shown in red and the others clean (which is the true status).

Not sure if you want to see all of these logged as Jira tickets... would be a bit of work.
 

aervin

iXsystems
iXsystems
Joined
Jun 13, 2018
Messages
68
Thanks for the feedback @sretalla ! It looks like there's a check to make sure VMs only show red if one or more of the VMs has autostart enabled and is not in the 'RUNNING' state. There is no such check for jails, and I'll create a ticket to track that fix.

The pool click-through issue sounds like a bug. Would you mind making a Jira ticket with some screenshots for that issue?
 

Patrick M. Hausen

Dedicated Sage
Joined
Nov 25, 2013
Messages
2,766
I cannot start the new version - I created a docker-compose.yml from your start instructions on Dockerhub:
Code:
version: '3.3'
services:
  truecommand:
    container_name: truecommand
    restart: always
    image: 'ixsystems/truecommand'
    ports:
      - '80:80'
      - '443:443'
    volumes:
      - '/app/ixsystems/truecommand:/data'


When I start with docker-compose up this happens:
Code:
root@docker:/app/ixsystems/truecommand# docker-compose up
Creating truecommand ... done
Attaching to truecommand
truecommand    | Starting TrueCommand: Tue Jul  7 16:57:50 UTC 2020
truecommand    | Generate SSL Certificate
truecommand    | Generating a RSA private key
truecommand    | ......+++++
truecommand    | ....................+++++
truecommand    | writing new private key to '/etc/truecommand/server.key.auto'
truecommand    | -----
truecommand    | Starting PostgreSQL 11 database server: main.
truecommand    | Stopping PostgreSQL 11 database server: main.
truecommand    | Starting Services [1/3]
truecommand    | Starting PostgreSQL 11 database server: main.
truecommand    | Starting Services [2/3]
truecommand    | Starting Services [3/3]
truecommand    | [STARTING] "Tue Jul 7 16:57:56 2020"
truecommand    | Opening Database...
truecommand    | Database Connected
truecommand    | Using SSL Library:
truecommand    |  - Version: "OpenSSL 1.1.1d  10 Sep 2019"
truecommand    |    WS server started on port number 5182
truecommand    |  HTTP server started on port number 5183


But no connections on port 80 or 443 possible from outside.
 

sretalla

Wizened Sage
Joined
Jan 1, 2016
Messages
3,931
On the VM comment (being unable to change the Autostart... I went to the GUI of that box and see that it was one which doesn't support VMs... although somehow I have a VM configured on it... so I get an error even on the local GUI when doing that... I just deleted the VM, so forget that one.

I will log a Jira ticket for the Pool click-through story.
 

sretalla

Wizened Sage
Joined
Jan 1, 2016
Messages
3,931

Patrick M. Hausen

Dedicated Sage
Joined
Nov 25, 2013
Messages
2,766
Thats what is says in the instructions here:

Code:
docker pull ixsystems/truecommand:[TAG]
docker run --detach -v "[hostdirectory]:/data" -p [portnumber]:80 -p [sslportnumber]:443 ixsystems/truecommand:[TAG]


And which used to work with the previous version ...
 

kenmoore

TrueCommand Project Lead
iXsystems
Joined
May 1, 2019
Messages
47
Yes, port 80 and 443 are the correct ports for the TrueCommand container. Those log messages are referring to the internal pre-nginx redirect ports which only accept access from localhost.

As for docker compose, you will need to check your docker compose settings then. In general, if you are already using port 80 or 443 on the host system you really should redirect the container to different ports on the host. Try a port above 8000 or within the 20k-30k range.

Example: "-p 8081:80 -p 8082:443" and then point your browser at localhost:8081
 

sretalla

Wizened Sage
Joined
Jan 1, 2016
Messages
3,931

Patrick M. Hausen

Dedicated Sage
Joined
Nov 25, 2013
Messages
2,766
No, I am not using these ports for anything but truecommand. But I guess I found the problem, entirely homemade, sorry folks.
If I use the IP address in the browser it works. Now I will have to check why Avahi doesn't do as it should ;)
 

sretalla

Wizened Sage
Joined
Jan 1, 2016
Messages
3,931
And which used to work with the previous version ...
Fair point... I have always redirected the ports as I'm using it in a Kubernetes environment (and I access via IP only). The upgrade worked smoothly (and surprisingly quickly) for me.
 

Chris Moore

Wizened Sage
Joined
May 2, 2015
Messages
10,050
FreeNAS and TrueNAS Fans,

We are pleased to announce that TrueCommand 1.3 is now available!
At work, I have a some FreeNAS systems. Total of about 200 drives. How much would it cost to get a licensed copy of this?
They live on a network that has no internet connection.
 
Top