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] Installation Completed with Failures #226

Closed
hackdefendr opened this issue Feb 11, 2018 · 10 comments
Closed

[CLI] Installation Completed with Failures #226

hackdefendr opened this issue Feb 11, 2018 · 10 comments

Comments

@hackdefendr
Copy link

I started with vanilla Ubuntu Server 16.04.

The installation ends with:

Completed with Failures -- Success: 517, Failure: 12

How can I find out which 12 failed? Is there a log of the installation beyond STDOUT?

@hackdefendr
Copy link
Author

So apparently the Ubuntu desktop is required. After installing that I now have this:

Completed with Failures -- Success: 525, Failure: 4

I did find where things are logged, but I do not know what to search for...I am going to trying a few things. If someone can help before I get it right...please chime in.

Thanks,

@ekristen
Copy link
Contributor

@hackdefendr basically looking for result: false in the install log. You can post it here or you can review it.

The CLI uses saltstack and we do not roll back in the face of an error, so there were 525 successes and that won't change, that means that for all intents and purposes SIFT is installed.

I've opened #230 as an issue for me to track to get better support into the CLI tool to show errors.

@milshtyn
Copy link

I had the same issue when running installation on Ubuntu Server 16.04 in AWS as @hackdefendr with the exact same number of failures. I've pulled the logs with the failures (attached here).
SIFTInstallFailures.txt
Note: One failure is missing I think. Didn't have time to figure out which one I missed.

The important thing here is that after install, running sift upgrade, I get an error saying that SIFT is not installed.

@ekristen
Copy link
Contributor

ekristen commented Feb 16, 2018 via email

@milshtyn
Copy link

milshtyn commented Feb 16, 2018 via email

@ekristen
Copy link
Contributor

ekristen commented Feb 16, 2018 via email

@MMULLINIX1
Copy link

MMULLINIX1 commented Feb 16, 2018 via email

@MMULLINIX1
Copy link

MMULLINIX1 commented Feb 16, 2018 via email

@milshtyn
Copy link

Michelle,
Despite the failures, I was still able to get some of my forensics activities done using the "partial" install. Seems most of the tools were working (e.g. log2timeline.py, fls, mactime, foremost).

@stale
Copy link

stale bot commented Apr 17, 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 Apr 17, 2018
@stale stale bot closed this as completed Apr 25, 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

4 participants