Skip to content
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

[cli] Incomplete due to Failures -- Success: 486, Failure: 53 #304

Closed
jacobiusg opened this issue Aug 29, 2018 · 25 comments
Closed

[cli] Incomplete due to Failures -- Success: 486, Failure: 53 #304

jacobiusg opened this issue Aug 29, 2018 · 25 comments

Comments

@jacobiusg
Copy link

I have re-run this install once already, updated all my packages, updated pip as it seemed to be a problem but no luck. Any assistance would be helpful.

output_sift_update.txt
saltstack_errors.txt

@ekristen
Copy link
Contributor

ekristen commented Aug 29, 2018 via email

@jacobiusg
Copy link
Author

python_output.txt

@jacobiusg jacobiusg changed the title Incomplete due to Failures -- Success: 486, Failure: 53 [cli] Incomplete due to Failures -- Success: 486, Failure: 53 Aug 29, 2018
@ekristen
Copy link
Contributor

ekristen commented Aug 29, 2018 via email

@jacobiusg
Copy link
Author

v 9.01

@ekristen
Copy link
Contributor

ekristen commented Aug 29, 2018 via email

@jacobiusg
Copy link
Author

saltcall.txt

@ekristen
Copy link
Contributor

ekristen commented Aug 29, 2018

Try running, you might need to alter the file-root, I'm going from memory at the moment, but I think that path is right.

salt-call --local --file-root=/var/cache/sift/cli/v2018.28.0 state.sls sift.python-packages.colorama

@jacobiusg
Copy link
Author

path was right i double checked

state.txt

@ekristen
Copy link
Contributor

Try ..

salt-call --local --file-root=/var/cache/sift/cli/v2018.28.0/sift-saltstack-2018.28.0 state.sls sift.python-packages.colorama

If that doesn't work look for the subfolder that has the sift folder in it.

@jacobiusg
Copy link
Author

Still seems to be a problem with pip.. I may just attempt to re-install python and pip see if that works

salt_state.txt

@ekristen
Copy link
Contributor

Add -l debug to the command.

@jacobiusg
Copy link
Author

salt_debug.txt

@ekristen
Copy link
Contributor

Try installing pip 9.0.3 if that doesn't work let me know. It looks like this might have been a bug in salt-stack, but according to everything it shouldn't behaving this way, but we can try upgrading salt-stack next (without using the sift-cli) to see if we can't get it working.

@jacobiusg
Copy link
Author

unfortunately it's still not working.

@ekristen
Copy link
Contributor

You can try and update to 2017.7.6, apt-get install sift-minion=2017.7.6 and then retry re-running the command.

@davidep
Copy link

davidep commented Aug 30, 2018

same issue here, @ekristen was the above supposed to be apt-get install salt-minion=2017.7.6 ?
if so, isn't salt-minion=2017.7.5+ds-1 the newest version?

@ekristen
Copy link
Contributor

ekristen commented Aug 30, 2018 via email

@Folii
Copy link

Folii commented Aug 30, 2018

Having the same issues.

Installing sift on a fresh VM through virtual box running Ubuntu Desktop 16.04.5. Installing it on a VM shouldn't effect anything?

I have been randomly selecting older versions and trying to install them.

When I installed v2018.26.0

Completed with Failures -- Success: 534, Failure: 5

Reinstalling v2018.28.0, but it does not list what failed below.
Sift version is listed as notinstalled regardless of it "completing"

Completed with Failures -- Success: 534, Failure: 5

I had been previously getting Success: 486, Failure: 53 before trying older versions.

@ekristen
Copy link
Contributor

ekristen commented Aug 30, 2018 via email

@Folii
Copy link

Folii commented Aug 31, 2018

I am re-installing a fresh VM from this exact image of Ubuntu found on the website (the torrent version)

ubuntu-16.04.5-desktop-amd64.iso

I apologize if I am not detailed enough I am new to this software, but let me know any specific logs you would want to have and how to obtain them. I am in the process of installing sift again, and i will keep any logs or notable errors so I can post them here.

This is the first error I receive after attempting the initial "sudo sift install"

  Incomplete due to Failures -- Success: 535, Failure: 4

 List of Failures (first 10 only)

 NOTE: First failure is generally the root cause.

 IMPORTANT: If opening a ticket, please include this information.

  - ID: sift-pdf-poster-dfir-threat-intel
    SLS: sift.config.user.pdfs
    Run#: 456
    Comment: Specified sha256 checksum for /home/shaun/Desktop/DFIR-Threat-Intel-Poster.pdf (c18b226d3d29f07136822bb5c555e8d71dae02ee4a0ba69c6a3588f95324481f) does not match actual checksum (e221bc427061602c29a1b1250ee76e3f3adb4aace5ff4f41e1d3918ad6d9abb4)
  - ID: undefined
    SLS: sift.config.user
    Run#: 489
    Comment: One or more requisite failed: sift.config.user.pdfs.sift-pdf-poster-dfir-threat-intel
  - ID: undefined
    SLS: sift.config
    Run#: 546
    Comment: One or more requisite failed: sift.config.user.sift-config-user
  - ID: undefined
    SLS: sift.vm
    Run#: 547
    Comment: One or more requisite failed: sift.config.sift-config

When attempting to run "sudo sift install" again I receive the following.
Here is the saltstack.log file through pastebin (https://pastebin.com/jaKXLp0n)

 sift-cli@1.7.1-master.f1177e4
 sift-version: notinstalled

 downloading v2018.28.0
 downloading sift-saltstack-v2018.28.0.tar.gz.asc
 downloading sift-saltstack-v2018.28.0.tar.gz.sha256
 downloading sift-saltstack-v2018.28.0.tar.gz.sha256.asc
 downloading sift-saltstack-v2018.28.0.tar.gz
 validating file sift-saltstack-v2018.28.0.tar.gz
 validating signature for sift-saltstack-v2018.28.0.tar.gz.sha256
 extracting update sift-saltstack-v2018.28.0.tar.gz
 performing update v2018.28.0
 Log file: /var/cache/sift/cli/v2018.28.0/saltstack.log

 Update returned exit code not zero
 Error: Update returned exit code not zero
     at ChildProcess.update.on (/snapshot/Users/ekristen/Development/sift/sift-cli/sift-cli.js:520:23)
     at emitTwo (events.js:106:13)
     at ChildProcess.emit (events.js:194:7)
     at maybeClose (internal/child_process.js:899:16)
     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)

I was looking around a few different posts regarding this issue and I happened upon a post suggesting I ran these commands regarding the saltstack.log.

rm -rf /usr/lib/python2.7/dist-packages/OpenSSL
rm -rf /usr/lib/python2.7/dist-packages/pyOpenSSL-0.15.1.egg-info
sudo pip install pyopenssl

This finally allowed me to run "sudo sift install" again, but after doing so it returned the same failures as originally stated above. I am not sure why I was getting 53 Failures on my previous install I may have done something in addition to what I just posted.

@davidep
Copy link

davidep commented Aug 31, 2018

my issue with salt-minion version was an hardcoded pointer to 2017.7.5 in source.list,
I changed that to latest, ran again sift upgrade, this time it ended with only 3 failed, (mainly only sift-python-package-machinae) "could not find a pip binary"

checking the /etc/apt/sources.list.d/saltstack.list now it is back to "deb http://repo.saltstack.com/apt/ubuntu/16.04/amd64/archive/2017.7.5 xenial main" so I guess that hardcoded version comes from the sift-cli script

@ekristen
Copy link
Contributor

@Folii you are 99% installed, I need to push an update to account for that poster as it's contents changed. SIFT doens't think it's installed because it wants 100% of everything to work, but you are there. Just so you know the CLI helper doesn't roll back anything in the face of failure so all the tools and such are installed.

@davidep welcome to the wonderful world of python breaking. As you can see @Folii managed to not get any python errors, but you are. The CLI is hardcoded but I will be adding an option to allow people to override it. If you got edit the source list and change the 2017.7.5 to 2017.7.7 and upgrade the salt-minion using apt, then run salt manually like

salt-call --local --file-root=/var/cache/sift/cli/v2018.28.0/sift-saltstack-2018.28.0 state.sls sift.python-packages.machinae

We can see if that fixes the issue.

@toastr
Copy link

toastr commented Aug 31, 2018

I had similar issues with updating/upgrading on a fresh VM for FOR508 which an updated copy was provided on 7/16/18. I have the VM snapshotted so I can easily roll back.

sift-cli@1.5.1-beta.0-master.154cb2f
sift-version: v2017.27.0
updating the current version (2017.27.0) presents errors as does upgrading to v2018.28.0
Attached is a log for

salt-call --local --file-root=/var/cache/sift/cli/v2018.28.0/sift-saltstack-2018.28.0 state.sls sift.packages

salt-call.log

when i issue and apt-get -f install a number of issues are resolved. After running the same salt-call command again the number of issues drops down to 5 with them revolving around python-dfvfs, python-plaso, and python3-pip

The following packages have unmet dependencies:
python3-pip : Depends: python-pip-whl (= 8.1.1-2) but 8.1.1-2ubuntu0.4 is to be installed
Recommends: python3-dev (>= 3.2) but it is not going to be installed
Recommends: python3-setuptools but it is not going to be installed
Recommends: python3-wheel but it is not going to be installed

[ERROR ] Command '['systemd-run', '--scope', 'apt-get', '-q', '-y', '-o', 'DPkg::Options::=--force-confold', '-o', 'DPkg::Options::=--force-confdef', 'install', 'python-dfvfs=latest']' failed with return code: 100
[ERROR ] stdout: Reading package lists...
Building dependency tree...
Reading state information...
[ERROR ] stderr: Running scope as unit run-r995c5fcb31a54a8e96302b552e948518.scope.
E: Version 'latest' for 'python-dfvfs' was not found
[ERROR ] retcode: 100
[ERROR ] Problem encountered installing package(s). Additional info follows:

errors:
- Running scope as unit run-r995c5fcb31a54a8e96302b552e948518.scope.
E: Version 'latest' for 'python-dfvfs' was not found

No apt-get update or upgrades have been run on this vm.

@VernMcC
Copy link

VernMcC commented Sep 1, 2018

When I install with

--mode=packages-only

sudo sift install --mode=packages-only --user=${currentUser}

I am not getting any errors and the tools I need work just fine.

I just did a base Ubuntu install and Sift install and it worked fine too, so I am not getting this error, although some of my students are. Workstation 14 Ubuntu 16.04.5 vm build

@stale
Copy link

stale bot commented Oct 31, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Oct 31, 2018
@stale stale bot closed this as completed Nov 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants