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

Getting started - errors on first time run #339

Open
alternaterealben opened this issue Dec 9, 2024 · 0 comments
Open

Getting started - errors on first time run #339

alternaterealben opened this issue Dec 9, 2024 · 0 comments

Comments

@alternaterealben
Copy link

Hi,
I'm trying to use SecGen but it's having issues. The project builds correctly in Ubuntu 20.04, but running the command ruby secgen.rb run fails with the following error. It's the most recent version of SecGen, and a clean system with nothing else installed.

I can see that there is a similar existing issue, but it seems to be different? I don't want to co-opt it.

Any help would be appreciated. Thanks.

==> escalation: Warning: Facter: Error loading fact /tmp/vagrant-puppet/modules-9dcc879867d0e2c52497c5d5f21bacd0/stdlib/lib/facter/root_home.rb: /tmp/vagrant-puppet/modules-9dcc879867d0e2c52497c5d5f21bacd0/stdlib/lib/facter/root_home.rb:6: syntax error, unexpected keyword_rescue, expecting keyword_end
==> escalation:   rescue LoadError
==> escalation:         ^
==> escalation: Notice: Compiled catalog for ****************** in environment production in 0.11 seconds
==> escalation: Notice: /Stage[main]/Unix_update::Unix/Exec[update]/returns: Ign:1 http://security.debian.org/debian-security stretch/updates InRelease
==> escalation: Notice: /Stage[main]/Unix_update::Unix/Exec[update]/returns: Err:3 http://security.debian.org/debian-security stretch/updates Release
==> escalation: Notice: /Stage[main]/Unix_update::Unix/Exec[update]/returns:   404  Not Found [IP: 151.101.30.132 80]
==> escalation: Notice: /Stage[main]/Unix_update::Unix/Exec[update]/returns: Ign:2 http://deb.debian.org/debian stretch InRelease
==> escalation: Notice: /Stage[main]/Unix_update::Unix/Exec[update]/returns: Ign:4 http://deb.debian.org/debian stretch-updates InRelease
==> escalation: Notice: /Stage[main]/Unix_update::Unix/Exec[update]/returns: Err:5 http://deb.debian.org/debian stretch Release
==> escalation: Notice: /Stage[main]/Unix_update::Unix/Exec[update]/returns:   404  Not Found [IP: 151.101.30.132 80]
==> escalation: Notice: /Stage[main]/Unix_update::Unix/Exec[update]/returns: Err:6 http://deb.debian.org/debian stretch-updates Release
==> escalation: Notice: /Stage[main]/Unix_update::Unix/Exec[update]/returns:   404  Not Found [IP: 151.101.30.132 80]
==> escalation: Notice: /Stage[main]/Unix_update::Unix/Exec[update]/returns: Reading package lists...
==> escalation: Notice: /Stage[main]/Unix_update::Unix/Exec[update]/returns: E: The repository 'http://security.debian.org/debian-security stretch/updates Release' does no longer have a Release file.
==> escalation: Notice: /Stage[main]/Unix_update::Unix/Exec[update]/returns: E: The repository 'http://http.debian.net/debian stretch Release' does no longer have a Release file.
==> escalation: Notice: /Stage[main]/Unix_update::Unix/Exec[update]/returns: E: The repository 'http://http.debian.net/debian stretch-updates Release' does no longer have a Release file.
==> escalation: Error: /usr/bin/apt-get update --fix-missing returned 100 instead of one of [0]
==> escalation: Error: /Stage[main]/Unix_update::Unix/Exec[update]/returns: change from notrun to 0 failed: /usr/bin/apt-get update --fix-missing returned 100 instead of one of [0]
==> escalation: Notice: Applied catalog in 154.13 seconds
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
Non-zero exit status...
Error provisioning VMs, destroying VMs and exiting SecGen.
Loading vagrant (destroy -f) in /home/user1/SecGen/projects/SecGen20241209_115013
==> escalation: Forcing shutdown of VM...
==> escalation: Destroying VM and associated drives...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant