-
-
Notifications
You must be signed in to change notification settings - Fork 491
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failure when following the documented installation instructions. #738
Comments
I've managed to get farther by removing the distro's ansible and installing the lastest version using this link: It would be very helpful to provide more explicit instructions to get the proper ansible for ansible-nas. But unfortunately the process breaks further into the playbook:
-Dale |
Hi all, A bit more clarification about why and what I'm doing. I've been running Ansible-NAS on some hardware for years. But I've always found the process of keeping in-sync with the main project error prone. So I tend to avoid it unless I really need something new that was added. So now I've built new server hardware to swap with my old system that's been working for years. I've decided to start fresh to avoid running down various issues from trying to upgrade the current older NAS before switching to the new hardware. I reasoned that the system should be able to install right from scratch with the current code and then adapt my existing setup from that using a top down approach. But I'm getting these issues with clean installs. What am I doing wrong? -Dale |
Ok... So I have the playbook finishing. I had to add This leads me to believe that no testing has occurred since then or people are just patching things when they break without sending the fixes back the repository.
I've attached a patch for the fix. 0001-Add-missing-definition-for-recordings_root.patch -Dale |
Does this project still have some legs or had it be abandoned? I hope it's still alive as I've found it's a decent solution for those of us that who ditched FreeNAS. -Dale |
The Heimdall role is broken because it's missing the code to create the heimdall user and group. I've attached a patch to fix it. 0002-Add-back-lost-code-that-creates-heimdall-user-and-gr.patch -Dale |
Hey, good spot with Regarding Ansible - I'm not seeing the same issue as you. I just ran a fresh install of Ansible (following the Ansible docs to install Python then Ansible via pip, not using the system Ansible which is ancient) and everything seems fine. Where did the system Ansible you're referring to come from? Ubuntu Server doesn't come with it installed OOTB. |
Hi, Thanks for the quick reply!
There was a version of ansible available in the repositories in the stock install of 22.04 but ansible-nas complained about it (from an earlier post in this PR):
So I went and looked more closely at your instructions and followed the ansible site link. I looked at the pip stuff etc... and felt I wasn't a much of a python expert and found the following more direct approach (for me anyway) to install the latest version: This used a ppa supplied by the Ansible project. After installing ansible from it I checked the installed version:
Ansible-nas was happy with this newer installed version of ansible. After that I ran into the other issues that I patched over. Truth be told... My first attempt was to install Ansible-nas on the latest Ubuntu 24.02LTS. On that OS ansible-nas didn't complain about the ansible version supplied with the OS distro but I ran into a missing package it was trying to install from
So I scratched that approach without much more investigation and reinstalled the latest 22.04.x server version of Ubuntu since that's the one you recommend. Anyway... I'll pick up your latest commits and remove the patches I put into my custom ansible repository I use to drive the process. FWIW...You can see it here: https://github.com/DLLarson/my-ansible-nas I basically include -Dale |
In case it's helpful, here are my instructions/notes from my last ansible-nas install, based on the issues I encountered. Note that the zfsutils and net-utils are probably not required, but helpful if you are using zfs storage like I am. And yes, I am aware many of these commands could be consolidated.
|
That's very close to the steps I took as I bumped into problems. These steps avoid confusion of putzing with python PIP, etc. There is a link to the ansible site given below that would replace steps 7-11. -Dale |
I'll note that my new Ansible-NAS machine is fully up and running with the same configuration (living on top of the latest ansible-nas commits) as my 10 year old NAS server (that started on FreeNAS and sometime later I ditched it for Ansible-NAS and never looked back.) The old machine is just sitting around until I have more confidence with the new hardware. Another great benefit of stepping up my hardware is access to 2.5Gb ethernet connections! Blazing fast compared to my old foggy ITX 16GB RAM 4 core AMD machine running WD Red Drives with a USB drive for the OS with 1Gb ethernet. My new machine runs an ATX MB that supports up to 5 NVMe SSD drives directly on the MB. My processor jumped from 4 cores to a current i7 with 20 cores--8p+12e--(28 threads). One NVMe SSD drive is 1TB and used for the OS. The remaining four are 4TB each and setup for raidz2. It's a beast. Of course I also had to buy some 2.5Gb ethernet switches but it was worth it. -Dale |
There are many ways to skin a cat, as they say. This was my list I cobbled together as I worked through the various issues I had building a new server (I now have 5 Ansible-NAS servers running for various reasons - they make great general purpose platforms with a lot of common services easily configured). From what I recall:
You'll also want to do any share drive/storage array config before you complete your yml config and run the playbook. I'm a recovered FreeNAS user as well. The second time an upgrade bricked my NAS and I had to spend hours figuring out what they did to break it, I started looking for something else. The third upgrade was going to stop supporting my hardware. Ansible-NAS doesn't have the fancy GUI, but if you can install Ubuntu, you can make it a server. If you do decide to try a refresh/rebuild - which I used to avoid as well - I recommend you write a script so you don't have to remember it from scratch. Mine is a work in progress, but right now I am using this: #!/usr/bin/env bash Again, don't remember the details, but I think I found it worked best to stop everything as some of the services would complain in the playbook run. Since I have some non-scripted docker containers running as well, that script is trying to only kill the relevant ones that will be impacted by the playbook. It still needs modification for the stats package and such. If you run into problems, I found that re-running the requirements.yml command from the initial install will usually sort it out, but most of the time it's not needed - really only if you keep putting it off. |
I'm just following the instructions step-by-step found here:
https://ansible-nas.io/docs/getting-started/installation/
I used Ubuntu Server named
ubuntu-22.04.5-live-server-amd64.iso
to create a VMWare system on Windows 11. I'm using the latest VMWare workstation and Win 11. I installedbuild-essential
andansible
packages supplied with the release.I cloned the latest (12/14/2024) ansible-nas repo from GitHub (Commit 1aec019.) for step 1.
Did step 2 verbatim.
For step 3 I changed
nas.yml
to the following:For step 4 I changed the
inventory
file to this:For step 5 I ran the
requirements.yml
install file verbatim. It had no errors.Finally I ran the playbook running the exact command as supplied. I provided my sudo password to the process. This is what resulted:
-Dale
The text was updated successfully, but these errors were encountered: