/etc ran out of space

[JohnFLi]

I am trying to install a commvault client. (It was there before when it was version 12.x
I currently am running
Version:
TrueNAS-13.0-U5.3

ANyway, the install fails due to "
No space left on device: '/etc/CommVa
ultRegistry/Galaxy'
"

Commvault says i need about 100 meg of space. how do I give /etc more space?

 

[somethingweird]

Don't know if it's a good idea. - symbolic link?

 

[winnielinnie]

Are you trying to do this on the host itself, not in a jail?

Install / configure it in its own jail. Don't do anything to the host system, except for what TrueNAS provides via its GUI.

 

[JohnFLi]

Are you trying to do this on the host itself, not in a jail?

Install / configure it in its own jail. Don't do anything to the host system, except for what TrueNAS provides via its GUI.

And how would I do that? when trying to install, it doesn't say anything other than wanting to install in /opt. It was commvault support that saw that /etc is out of space

 

[winnielinnie]

And how would I do that?

That's a whole new topic. You need to have some level of creating, using, and managing jails. To try to walk you through every step and every concept might end up in vain.

With Core (FreeBSD-based), you use the "Jails" page and "iocage" commands to create, configure, and manage your jails. Think of jails as "isolated, contained environments." They have their own filesystem hierarchy, packages, and services, and are managed as if they were each their own individual FreeBSD server. (Sort of like "VMs", except without the overhead, as nothing needs to be virtualized, and it runs with the host's kernel and modules.)

So for Core, you leave the NAS host system alone. Only use it as it was meant to be used, with the tools and GUI it provides. Don't go messing with the directories or packages or installing anything from outside. That's what jails are for.

(With SCALE (Linux-based), you use their "Apps" feature (i.e, K3s) to run and manage third-party applications.)



It's actually concerning that you might have already messed around with your host system and boot-pool in the meantime, which makes future headaches unpredictable.

it doesn't say anything other than wanting to install in /opt. It was commvault support that saw that /etc is out of space

The CommVault instructions for FreeBSD are not for TrueNAS. If you want to follow their instructions, you need to do it in a FreeBSD 13.2 Basejail, which is essentially a "vanilla" FreeBSD environment.

 

[JohnFLi]

That's a whole new topic. You need to have some level of creating, using, and managing jails. To try to walk you through every step and every concept might end up in vain.

With Core (FreeBSD-based), you use the "Jails" page and "iocage" commands to create, configure, and manage your jails. Think of jails as "isolated, contained environments." They have their own filesystem hierarchy, packages, and services, and are managed as if they were each their own individual FreeBSD server. (Sort of like "VMs", except without the overhead, as nothing needs to be virtualized, and it runs with the host's kernel and modules.)

So for Core, you leave the NAS host system alone. Only use it as it was meant to be used, with the tools and GUI it provides. Don't go messing with the directories or packages or installing anything from outside. That's what jails are for.

(With SCALE (Linux-based), you use their "Apps" feature (i.e, K3s) to run and manage third-party applications.)



It's actually concerning that you might have already messed around with your host system and boot-pool in the meantime, which makes future headaches unpredictable.




The CommVault instructions for FreeBSD are not for TrueNAS. If you want to follow their instructions, you need to do it in a FreeBSD 13.2 Basejail, which is essentially a "vanilla" FreeBSD environm

 

[JohnFLi]

If i was to install commvault in a jail...... would it still have access to /mnt ? the purpose of caommvault is to backup the storage pools

 

[winnielinnie]

If i was to install commvault in a jail...... would it still have access to /mnt ? the purpose of caommvault is to backup the storage pools

That's what "mountpoints" are for. You can configure mountpoints (while the jail is "off") by visiting Jails -> expand your jail -> Mount Points

So for example, in the jail's filesystem, /mnt/Data would point to the real (host) path of /mnt/myPool/mydata

Which means any actions done within the jail by the CommVault software against what it perceives as "/mnt/Data" (within its own hierarchy), has access to the host's path of "/mnt/myPool/mydata"

There is no abstraction layer. The permissions and ownership of the real path (in the host filesystem) is exactly the same as within the jail. So you need to create / assign usernames and groups accordingly, in both the host and jail, with the same UID/GID.

 

[JohnFLi]

I cre

That's what "mountpoints" are for. You can configure mountpoints (while the jail is "off") by visiting Jails -> expand your jail -> Mount Points

So for example, in the jail's filesystem, /mnt/Data would point to the real (host) path of /mnt/myPool/mydata

Which means any actions done within the jail by the CommVault software against what it perceives as "/mnt/Data" (within its own hierarchy), has access to the host's path of "/mnt/myPool/mydata"

There is no abstraction layer. The permissions and ownership of the real path (in the host filesystem) is exactly the same as within the jail. So you need to create / assign usernames and groups accordingly, in both the host and jail, with the same UID/GID.

I created a volume to use for a jail.
I go to the Jail to set it up (using the gui) and I instantly get the following error:

Code:

HTTPSConnectionPool(host='www.freebsd.org', port=443): Max retries exceeded with url: /security/unsupported.html (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate in certificate chain (_ssl.c:1134)')))

Then it doesn't matter If I select clone jail or base jail, The Release box is empty so it will not let me proceed

 

[winnielinnie]

I created a volume to use for a jail.

What do you mean by this?

Upon creating your first jail. the "iocage" dataset is automatically created and populated on your storage pool. Why are you creating volumes?

The problem is, you apparently already filled up your boot-pool. So now you're dealing with more issues. You might have to rollback to an earlier boot environment, before you started to mess with the host's filesystem.

 

[JohnFLi]

What do you mean by this?

Upon creating your first jail. the "iocage" dataset is automatically created and populated on your storage pool. Why are you creating volumes?

The problem is, you apparently already filled up your boot-pool. So now you're dealing with more issues. You might have to rollback to an earlier boot environment, before you started to mess with the host's filesystem.

created a volume for the jail.
First step when creating a jail, it asks were you want it and the dropdown box is the storage Volumes

 

[JohnFLi]

What do you mean by this?

Upon creating your first jail. the "iocage" dataset is automatically created and populated on your storage pool. Why are you creating volumes?

The problem is, you apparently already filled up your boot-pool. So now you're dealing with more issues. You might have to rollback to an earlier boot environment, before you started to mess with the host's filesystem.

Also, the truenas install was a fresh install. host file system never got changed as commvault wouldn't install..

 

[winnielinnie]

host file system never got changed as commvault wouldn't install..

Anyway, the install fails due to "No space left on device: '/etc/CommVaultRegistry/Galaxy'"

Something indeed happened...

I think you either need to truly understand a NAS appliance, and its uses, or switch over to a "roll your own" setup with FreeBSD or Linux, and use CommVault this way.

 

[danb35]

Let's see where the issue is. What's the output of zpool list? And if it does show the boot pool is full, do cd / followed by du -sh *, and post the output of that.

 

[JohnFLi]

Let's see where the issue is. What's the output of zpool list? And if it does show the boot pool is full, do cd / followed by du -sh *, and post the output of that.

CommvaultJail is the pool I made for the jail

Code:

# zpool list
NAME            SIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAG    CAP  DEDUP    HEALTH  ALTROOT
Archive        36.4T  12.4T  24.0T        -         -     0%    34%  1.00x    ONLINE  /mnt
CommvaultJail  9.08T   897M  9.08T        -         -     0%     0%  1.00x    ONLINE  /mnt
VideoStorage   72.5T  58.3T  14.2T        -         -     7%    80%  1.00x    ONLINE  /mnt
boot-pool       103G  1.34G   102G        -         -     0%     1%  1.00x    ONLINE  -

Code:

root@G1PPFREENAS01[~]# cd /
root@G1PPFREENAS01[/]# du -sh *
827K    bin
233M    boot
2.0K    compat
 15M    conf
4.0K    COPYRIGHT
7.5M    data
 13K    dev
4.5K    entropy
 10M    etc
5.6M    lib
 98K    libexec
512B    media

 

[danb35]

So no, the boot device (and therefore /etc) isn't full--there's over 100 GB available there. So whatever your problem is, it isn't that there's no space available in /etc.

CommvaultJail is the pool I made for the jail

It's pretty unusual to make a pool just for a jail, but whatever, I guess.

 

[JohnFLi]

So no, the boot device (and therefore /etc) isn't full--there's over 100 GB available there. So whatever your problem is, it isn't that there's no space available in /etc.

It's pretty unusual to make a pool just for a jail, but whatever, I guess.

it was either make a new pool, or pick an existing one.
I did get a jail installed, selected for it to be 12.4-RELEASE

Gave it an IP address, set the mount points and started it up.
Don't know whatever root password it gave it, nor does it let me change it. no error, seems like it took the new password, but can't ssh into it.
ANYWAY
i use the SHELL in the jail gui. I navigate to the mount points....but it doesn't show anything thing, files/folders nothing.

 

[danb35]

can't ssh into it.

sshd isn't installed in a jail by default, and if you've installed it, you'll also need to configure it to permit root logins.

 

[JohnFLi]

Not to go too much off topic, but is this all virtualized? The way you're able to ad-hoc create new pools without hardware or disk upgrades makes it feel like you're using virtual disks...

nope, this is all physical hardware. approx. 40 10 tb hard drives

 

[JohnFLi]

I got ssh running, got root access running, even got commvault client installed and running..........

But, now the get mount points working. I see the mnt points, but no files and folders.
I must have created them incorrectly