Ubuntu 20.04 LTS w/Remnux - update fails #67
Comments
|
Hi @Duocast , did you happen to attempt to install or uninstall SaltStack prior to running the remnux CLI? This looks curious as it seems to suggest part of the required salt components are missing. Also, with the SaltStack log results, is that the entirety of the log file, or just the error? If it's just a part of the log, can you upload the whole thing? There might be more hints in there. Cheers! |
|
No attempt to uninstall or reinstall Saltstack. |
|
Looks like a recently reported SaltStack issue. @digitalsleuth, any chance you'd be able to look into it for a workaround? |
|
Sure thing, I'm on it! |
|
It looks like Saltstack has updated their version about an hour ago to 3004.1 which includes the pinning of pre-reqs for jinja to 3.0.3. I'm going to test against the newest version to confirm everything works, then I would probably recommend we upgrade the CLI to 3004.1. More to follow. |
|
Looks like it didn't work, I'll keep working on a workaround :) |
|
Hello everyone. I am new here but I ran into this same issue while trying to do a remnux-cli install in add-on mode for a recently built SIFT on Ubuntu 20.04 VM. I just figured out a workaround a few minutes ago and was trying to figure out how to reach out to share what I found in case that helps the broader effort. From what I have found the issue was apparently caused by the changes in Jinja 2 3.1.x builds (my VM had been on Jinja 2 version 3.1.1). I found some suggestions to back rev Jinja 2 to the older 3.0.x version (I used 3.0.3). I was able to use PIP to remove Jinja 2 version 3.1.1 and instead install Jinja 2 version 3.0.3. After I did this, the remnux-cli installer started working for me. Here are some of the URL's I found in my research if they help at all: sphinx-doc/sphinx#10291 Hope this helps! |
|
Hi @phos2lampsei , thank you for providing your feedback! We actually just released a new version 2 days ago which addresses the issue going forward, but existing systems having the issue should do just what you mentioned; install jinja2==3.0.3 and start from there. |
|
Wow...that was fast! Thanks! Yeah I saw the other note but in my case I think either the SIFT install or standard Apt-Get updates had already broken me by upgrading me to Jinja 2 3.1.1 so I was stuck until I did the manual forced downgrade. Been a learning experience for me since this broke on me last night trying to get this done. Not sure if there is a way to make the installer do a downgrade for unfortunate souls like me who got upgraded to the bum build? I just built the VM yesterday with a fresh download of the Remnux-CLI installer so I think in my case because I was in add-on mode I was broken by the existing presence of the newer jinja2 that my VM already had. |
So I think I spoke too soon. After fixing the Jinja 2 issues by the forced downgrade to Jina2 3.0.3 things were humming along with my Remnux addon mode install but it still failed on me. I ran into several more package failures. While trying to debug those I noticed apt-get update was referring to a non-existent https://repo.saltproject.io/py3/ubuntu/20.04/amd64/3001/ directory. I was able to fix this manually in my apt-get config but pointing the path to a newer version and get Apt-Get update happy again. However I downloaded a fresh copy of remnux-cli (per the instructions at https://docs.remnux.org/install-distro/add-to-existing-system) to be sure and retried my install but it seems it is hardcoded to look for the non-existent https://repo.saltproject.io/py3/ubuntu/20.04/amd64/3001/ directory. So it appears that not only has salt project been upgraded several times in the last few days but that the old 3001 folder referenced by the REMnux installer no longer even exists. I think I am stuck at this point but would be happy to help test any changes when they are ready. |
|
@phos2lampsei We were just made aware that the saltstack repo has removed support for 3001, so we're preparing a new CLI tool to support 3004. Currently running tests so we can confirm no breakage, then the changes will be applied. We'll keep you, and everyone, posted! |
|
Sounds like you all are already on top of it! Thanks a lot!! |
|
@phos2lampsei, this should be fixed now. Please give it a a try! |
|
With all that have been written here , still encoutering the problem :( |
|
Hi @Y8765 Can you possibly paste us your error, or upload the saltstack.log file, if applicable? |
|
Just had a chance to circle back on this. I pulled down a fresh copy of the remnux-cli, verified the hash and confirmed it was the newer version. While attempting to run it, there was an immediate "unable to locate package salt-minion" failure trying to remove salt-common and salt-minion. I dropped out and confirmed that these packages were not installed. Re-ran another apt-get update and noticed the failure again for the non-existent saltproject /3001 subdirectory (even though I had manually fixed that before). I went back in and manually fixed the /etc/apt/sources.list.d/saltstack.list file again to point it to the /3004 directory again and then made sure apt-get update was happy again. After doing this I was then able to get the new remnux-cli installer to run. I don't know if my system had just been missed up by the prior testing and workaround attempts but I wonder if for those who tried the install before (either successfully when the /3001 saltproject directory still existed or during the failure period after that /3001 directory went away) that there may also be inconsistent machine artifacts that require a bit of cleanup before things will be happy again. Personally I think I may be finally fixed but raising this for awareness in case artifacts from the old /3001 saltstack repo cause other users install issues that may warrant a bit of automated cleanup in the install script. Thanks again for your speedy attention in updating the installer! |
|
HI ! |
i've deleted that machine so log source isnt available :( |
|
now encountering this issue - Fresh installation
|
|
Hi @Y8765 It looks like Network Miner has been updated and the hash will have to be updated as well. We'll get that done today, but as for your install, everything except for Network Miner installed properly. |
Yeh, i saw that the system backround has been changed to remnux etc |
|
Hi @muawyah , the log file shows that everything except NetworkMiner installed correctly, and the background should change once you reboot. Please give that a shot and let us know how it goes! |
|
You can try running the following script to see if that will work for you: |
|
Can you paste the command you used, and the first few lines which follows, for the remnux upgrade command?
…________________________________
From: muawyah ***@***.***>
Sent: Tuesday, April 12, 2022 7:26:39 AM
To: REMnux/remnux-cli ***@***.***>
Cc: Corey Forman ***@***.***>; Mention ***@***.***>
Subject: Re: [REMnux/remnux-cli] Ubuntu 20.04 LTS w/Remnux - update fails (Issue #67)
I ran the above script but the background did not change
I ran the following commands, then I got the success message for the upgrade, but the back ground is the same
curl -Lo remnux-cli-linux https://github.com/REMnux/remnux-cli/releases/download/v1.3.4/remnux-cli-linux
chmod +x remnux-cli-linux
sudo mv remnux-cli-linux /usr/local/bin/remnux
—
Reply to this email directly, view it on GitHub<#67 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AO7OHXR44DVJUIQIJIWC53LVEVMW7ANCNFSM5RYLSS6A>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
@muawyah I think I see the issue. Try running the command as |
|
I'm not sure what change you might be looking for, but the background I can see in the screenshot you provided is the actual background that's supposed to be configured. Are you expecting a different background? |
|
@muawyah I'm afraid I still don't quite understand what you mean, however the end result you have from the image above is the correct output. |
Error occures after running remnux update ("remnux upgrade" works verifying I am on v2022.11.1).
The terminal error shows as
Update returned exit code not zero
Error: Update returned exit code not zero
at ChildProcess. (/snapshot/remnux-cli/remnux-cli.js:569:23)
at ChildProcess.emit (events.js:315:20)
at maybeClose (internal/child_process.js:1021:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
saltstack.log results:
Traceback (most recent call last):
File "/usr/bin/salt-call", line 11, in
load_entry_point('salt==3001.8', 'console_scripts', 'salt-call')()
File "/usr/lib/python3/dist-packages/salt/scripts.py", line 439, in salt_call
import salt.cli.call
File "/usr/lib/python3/dist-packages/salt/call.py", line 6, in
import salt.cli.caller
File "/usr/lib/python3/dist-packages/salt/caller.py", line 19, in
import salt.minion
File "/usr/lib/python3/dist-packages/salt/minion.py", line 42, in
import salt.pillar
File "/usr/lib/python3/dist-packages/salt/pillar/init.py", line 19, in
import salt.fileclient
File "/usr/lib/python3/dist-packages/salt/fileclient.py", line 32, in
import salt.utils.templates
File "/usr/lib/python3/dist-packages/salt/utils/templates.py", line 27, in
import salt.utils.jinja
File "/usr/lib/python3/dist-packages/salt/utils/jinja.py", line 31, in
from jinja2 import BaseLoader, Markup, TemplateNotFound, nodes
ImportError: cannot import name 'Markup' from 'jinja2' (/usr/local/lib/python3.8/dist-packages/jinja2/init.py)
Looks to be related to python? Any guidance would be helpful. Thanks!
(This is on a fresh installation of Ubuntu 20.04 LTS and a fresh Remnux install following the guidance of the Remnux documentation).
Note: The post doesn't allow <>. Everything following an "in" on a line is "module" surrounded in arrow brackets.
The text was updated successfully, but these errors were encountered: