I'm a newbie, but I'm trying to figure this TrueNas thing out. I've so far installed plex and transmission, by following some of the "Resources" on this site. I have a dataset created for each of apps, and have their configs (at least I think) stored on the dataset as I heard this is the best thing to do to make recovery easier should I have to nuke a jail.
Now I couldn't find a resource to install Unifi6 on TrueNas 12. So I duct taped a solution from numerous threads on how to install other jails. This is what I came up with:
So here is where I need help:
1) Is this the right process? Did I miss anything that I needed to do in the setup of the jail?
2) The problem is the data file for unifi is never created. If I don't create the mount point the files are created and everything is fine, however, I don't have anything stored on my "app" dataset in the unifi directory. How do I fix this so that the config is created as normal, and i get a backup in my unifi dataset?
Thank you in advance.
Now I couldn't find a resource to install Unifi6 on TrueNas 12. So I duct taped a solution from numerous threads on how to install other jails. This is what I came up with:
Code:
root@TrueNAS[~]# echo '{"pkgs":["bash","unifi6"]}' > /tmp/pkg.json root@TrueNAS[~]# iocage create -n "unifi" -p /tmp/pkg.json -r 12.2-RELEASE ip4_addr="vnet0|192.168.1.200/24" defaultrouter="192.168.1.1" vnet="on" boot="on" host_hostname="uniFi" unifi successfully created! Testing Host DNS response to pkg.freebsd.org Testing unifi's SRV response to pkg.freebsd.org Testing unifi's DNSSEC response to pkg.freebsd.org Installing pkg... You may need to manually remove /usr/local/etc/pkg.conf if it is no longer needed. Installing supplied packages: - bash... - unifi6... *** Added group `cyrus' (id 60) *** Added user `cyrus' (id 60) ===> Creating groups. Creating group 'mongodb' with gid '922'. ===> Creating users Creating user 'mongodb' with uid '922'. ===> Creating homedir(s) ===> Creating groups. Creating group 'unifi' with gid '975'. ===> Creating users Creating user 'unifi' with uid '975'. ===== Message from freetype2-2.10.4: -- The 2.7.x series now uses the new subpixel hinting mode (V40 port's option) as the default, emulating a modern version of ClearType. This change inevitably leads to different rendering results, and you might change port's options to adapt it to your taste (or use the new "FREETYPE_PROPERTIES" environment variable). The environment variable "FREETYPE_PROPERTIES" can be used to control the driver properties. Example: FREETYPE_PROPERTIES=truetype:interpreter-version=35 \ cff:no-stem-darkening=1 \ autofitter:warping=1 This allows to select, say, the subpixel hinting mode at runtime for a given application. If LONG_PCF_NAMES port's option was enabled, the PCF family names may include the foundry and information whether they contain wide characters. For example, "Sony Fixed" or "Misc Fixed Wide", instead of "Fixed". This can be disabled at run time with using pcf:no-long-family-names property, if needed. Example: FREETYPE_PROPERTIES=pcf:no-long-family-names=1 How to recreate fontconfig cache with using such environment variable, if needed: # env FREETYPE_PROPERTIES=pcf:no-long-family-names=1 fc-cache -fsv The controllable properties are listed in the section "Controlling FreeType Modules" in the reference's table of contents (/usr/local/share/doc/freetype2/reference/site/index.html, if documentation was installed). ===== Message from dejavu-2.37_1: -- Make sure that the freetype module is loaded. If it is not, add the following line to the "Modules" section of your X Windows configuration file: Load "freetype" Add the following line to the "Files" section of X Windows configuration file: FontPath "/usr/local/share/fonts/dejavu/" Note: your X Windows configuration file is typically /etc/X11/XF86Config if you are using XFree86, and /etc/X11/xorg.conf if you are using X.Org. ===== Message from libinotify-20180201_2: -- Libinotify functionality on FreeBSD is missing support for - detecting a file being moved into or out of a directory within the same filesystem - certain modifications to a symbolic link (rather than the file it points to.) in addition to the known limitations on all platforms using kqueue(2) where various open and close notifications are unimplemented. This means the following regression tests will fail: Directory notifications: IN_MOVED_FROM IN_MOVED_TO Open/close notifications: IN_OPEN IN_CLOSE_NOWRITE IN_CLOSE_WRITE Symbolic Link notifications: IN_DONT_FOLLOW IN_ATTRIB IN_MOVE_SELF IN_DELETE_SELF Kernel patches to address the missing directory and symbolic link notifications are available from: https://github.com/libinotify-kqueue/libinotify-kqueue/tree/master/patches You might want to consider increasing the kern.maxfiles tunable if you plan to use this library for applications that need to monitor activity of a lot of files. ===== Message from alsa-lib-1.2.2: -- ===> NOTICE: The alsa-lib port currently does not have a maintainer. As a result, it is more likely to have unresolved issues, not be up-to-date, or even be removed in the future. To volunteer to maintain this port, please create an issue at: https://bugs.freebsd.org/bugzilla More information about port maintainership is available at: https://docs.freebsd.org/en/articles/contributing/#ports-contributing ===== Message from openjdk8-8.292.10.1: -- This OpenJDK implementation requires fdescfs(5) mounted on /dev/fd and procfs(5) mounted on /proc. If you have not done it yet, please do the following: mount -t fdescfs fdesc /dev/fd mount -t procfs proc /proc To make it permanent, you need the following lines in /etc/fstab: fdesc /dev/fd fdescfs rw 0 0 proc /proc procfs rw 0 0 ===== Message from cyrus-sasl-2.1.27_1: -- You can use sasldb2 for authentication, to add users use: saslpasswd2 -c username If you want to enable SMTP AUTH with the system Sendmail, read Sendmail.README NOTE: This port has been compiled with a default pwcheck_method of auxprop. If you want to authenticate your user by /etc/passwd, PAM or LDAP, install ports/security/cyrus-sasl2-saslauthd and set sasl_pwcheck_method to saslauthd after installing the Cyrus-IMAPd 2.X port. You should also check the /usr/local/lib/sasl2/*.conf files for the correct pwcheck_method. If you want to use GSSAPI mechanism, install ports/security/cyrus-sasl2-gssapi. If you want to use SRP mechanism, install ports/security/cyrus-sasl2-srp. If you want to use LDAP auxprop plugin, install ports/security/cyrus-sasl2-ldapdb. ===== Message from boost-libs-1.72.0_5: -- You have built the Boost library with thread support. Don't forget to add -pthread to your linker options when linking your code. No default gateway found for ipv6. * Starting unifi + Started OK + Using devfs_ruleset: 1002 (iocage generated default) + Configuring VNET OK + Using IP options: vnet + Starting services OK + Executing poststart OK root@TrueNAS[~]# rm /tmp/pkg.json root@TrueNAS[~]# iocage fstab -a unifi /mnt/tank/turret/unifi /usr/local/share/java/unifi/data/ nullfs rw 0 0 Successfully added mount to unifi's fstab root@TrueNAS[~]# iocage exec unifi sysrc unifi_enable="Yes" unifi_enable: -> Yes root@TrueNAS[~]# iocage exec unifi service unifi start Starting unifi. root@TrueNAS[~]#
So here is where I need help:
1) Is this the right process? Did I miss anything that I needed to do in the setup of the jail?
2) The problem is the data file for unifi is never created. If I don't create the mount point the files are created and everything is fine, however, I don't have anything stored on my "app" dataset in the unifi directory. How do I fix this so that the config is created as normal, and i get a backup in my unifi dataset?
Thank you in advance.