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

BUG: On Ubuntu 14.04.5 LTS | systemctl daemon-reload | bash: line 4: systemctl: command not found #229

Open
MaxPeal opened this issue Sep 20, 2020 · 1 comment
Assignees

Comments

@MaxPeal
Copy link

MaxPeal commented Sep 20, 2020

git clone https://github.com/RackHD/voyager-release
cd voyager-release\vagrant\voyager
D:\voyager-release\vagrant\voyager>vagrant up
+ set http/s proxy via ENV to http_proxy: http://proxy:3128
proxyconf...
find proxyconf plugin and get proxy via ENV!
http_proxy: http://proxy:3128
https_proxy: http://proxy:3128
ftp_proxy: http://proxy:3128
no_proxy: localhost,127.0.0.1,.example.com
set config.putty.ssh_client to C:/Program Files/PuTTY/putty.exe
Bringing machine 'vagrant' up with 'virtualbox' provider...
==> vagrant: Cloning VM...
==> vagrant: Matching MAC address for NAT networking...
==> vagrant: Checking if box 'voyager/AcceptanceBase' version '1.4.1' is up to date...
==> vagrant: Setting the name of the VM: voyager_vagrant_1600633986138_40009
==> vagrant: Clearing any previously set network interfaces...
==> vagrant: Preparing network interfaces based on configuration...
    vagrant: Adapter 1: nat
    vagrant: Adapter 2: hostonly
==> vagrant: Forwarding ports...
    vagrant: 15672 (guest) => 15672 (host) (adapter 1)
    vagrant: 22 (guest) => 2222 (host) (adapter 1)
==> vagrant: Running 'pre-boot' VM customizations...
==> vagrant: Booting VM...
==> vagrant: Waiting for machine to boot. This may take a few minutes...
    vagrant: SSH address: 127.0.0.1:2222
    vagrant: SSH username: vagrant
    vagrant: SSH auth method: private key
    vagrant: Warning: Connection reset. Retrying...
==> vagrant: Machine booted and ready!
==> vagrant: Checking for guest additions in VM...
    vagrant: The guest additions on this VM do not match the installed version of
    vagrant: VirtualBox! In most cases this is fine, but in rare cases it can
    vagrant: prevent things such as shared folders from working properly. If you see
    vagrant: shared folder errors, please make sure the guest additions within the
    vagrant: virtual machine match the version of VirtualBox you have installed on
    vagrant: your host and reload your VM.
    vagrant:
    vagrant: Guest Additions Version: 4.3.36
    vagrant: VirtualBox Version: 6.1
==> vagrant: Configuring proxy for Apt...
==> vagrant: Configuring proxy for Docker...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

systemctl daemon-reload

Stdout from the command:



Stderr from the command:

bash: line 4: systemctl: command not found

D:\voyager-release\vagrant\voyager>
@MaxPeal
Copy link
Author

MaxPeal commented Sep 20, 2020

possible fix #228

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

2 participants