You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ vagrant up
Bringing machine 'ethereum' up with 'virtualbox' provider...
==> ethereum: Box 'ubuntu/xenial64' could not be found. Attempting to find and install...
ethereum: Box Provider: virtualbox
ethereum: Box Version: >= 0
==> ethereum: Loading metadata for box 'ubuntu/xenial64'
ethereum: URL: https://vagrantcloud.com/ubuntu/xenial64
==> ethereum: Adding box 'ubuntu/xenial64' (v20181106.0.0) for provider: virtualbox
ethereum: Downloading: https://vagrantcloud.com/ubuntu/boxes/xenial64/versions/20181106.0.0/providers/virtualbox.box
ethereum: Download redirected to host: cloud-images.ubuntu.com
==> ethereum: Successfully added box 'ubuntu/xenial64' (v20181106.0.0) for 'virtualbox'!
==> ethereum: Importing base box 'ubuntu/xenial64'...
==> ethereum: Matching MAC address for NAT networking...
==> ethereum: Checking if box 'ubuntu/xenial64' is up to date...
==> ethereum: Setting the name of the VM: parity_vagrant_ethereum_1541587676244_94209
Vagrant is currently configured to create VirtualBox synced folders with
the `SharedFoldersEnableSymlinksCreate` option enabled. If the Vagrant
guest is not trusted, you may want to disable this option. For more
information on this option, please refer to the VirtualBox manual:
https://www.virtualbox.org/manual/ch04.html#sharedfolders
This option can be disabled globally with an environment variable:
VAGRANT_DISABLE_VBOXSYMLINKCREATE=1
or on a per folder basis within the Vagrantfile:
config.vm.synced_folder '/host/path', '/guest/path', SharedFoldersEnableSymlinksCreate: false
==> ethereum: Clearing any previously set network interfaces...
==> ethereum: Preparing network interfaces based on configuration...
ethereum: Adapter 1: nat
ethereum: Adapter 2: hostonly
==> ethereum: Forwarding ports...
ethereum: 8545 (guest) => 8545 (host) (adapter 1)
ethereum: 30303 (guest) => 30303 (host) (adapter 1)
ethereum: 22 (guest) => 2222 (host) (adapter 1)
==> ethereum: Running 'pre-boot' VM customizations...
==> ethereum: Booting VM...
==> ethereum: Waiting for machine to boot. This may take a few minutes...
ethereum: SSH address: 127.0.0.1:2222
ethereum: SSH username: vagrant
ethereum: SSH auth method: private key
ethereum: Warning: Connection reset. Retrying...
ethereum: Warning: Remote connection disconnect. Retrying...
ethereum: Warning: Connection reset. Retrying...
ethereum: Warning: Remote connection disconnect. Retrying...
ethereum: Warning: Connection reset. Retrying...
ethereum: Warning: Remote connection disconnect. Retrying...
ethereum: Warning: Connection reset. Retrying...
ethereum:
ethereum: Vagrant insecure key detected. Vagrant will automatically replace
ethereum: this with a newly generated keypair for better security.
ethereum:
ethereum: Inserting generated public key within guest...
ethereum: Removing insecure key from the guest if it's present...
ethereum: Key inserted! Disconnecting and reconnecting using new SSH key...
==> ethereum: Machine booted and ready!
==> ethereum: Checking for guest additions in VM...
ethereum: The guest additions on this VM do not match the installed version of
ethereum: VirtualBox! In most cases this is fine, but in rare cases it can
ethereum: prevent things such as shared folders from working properly. If you see
ethereum: shared folder errors, please make sure the guest additions within the
ethereum: virtual machine match the version of VirtualBox you have installed on
ethereum: your host and reload your VM.
ethereum:
ethereum: Guest Additions Version: 5.1.38
ethereum: VirtualBox Version: 5.0
==> ethereum: Configuring and enabling network interfaces...
==> ethereum: Mounting shared folders...
ethereum: /vagrant => /Users/zulhilmi/projects/parity_vagrant
==> ethereum: Running provisioner: shell...
ethereum: Running: /var/folders/n_/gd4bz2y92l1834sjbsb6nhlr0000gn/T/vagrant-shell20181107-48510-1rwjjp5.sh
ethereum: home: /root
ethereum: user: root
ethereum: Installing parity
ethereum:
ethereum:
ethereum: %
ethereum:
ethereum: T
ethereum: o
ethereum: t
ethereum: a
ethereum: l
ethereum:
ethereum:
ethereum:
ethereum:
ethereum: %
ethereum:
ethereum: R
ethereum: e
ethereum: c
ethereum: e
ethereum: i
ethereum: v
ethereum: e
ethereum: d
ethereum:
ethereum: %
ethereum:
ethereum: X
ethereum: f
ethereum: erd Average Speed Time Time Time Current
ethereum: Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
ethereum: 1
ethereum: 0
ethereum: 0
ethereum:
ethereum:
ethereum:
ethereum: 3
ethereum: 2
ethereum: 3
ethereum:
ethereum: 0 323 0 0 925 0 --:--:-- --:--:-- --:--:-- 928
ethereum: dpkg-deb: error: '/tmp/parity.deb' is not a debian format archive
ethereum: dpkg: error processing archive /tmp/parity.deb (--install):
ethereum: subprocess dpkg-deb --control returned error exit status 2
ethereum: Errors were encountered while processing:
ethereum: /tmp/parity.deb
ethereum: address: 133e5245e3e5ab3f65e73120b34cc29f0f7ba504
Any idea how to make this working?
The text was updated successfully, but these errors were encountered:
I change the script inside configure-parity.sh from http://d1h4xl4cr1h0mo.cloudfront.net/beta/x86_64-unknown-linux-gnu/parity_1.4.0_amd64.deb to https://github.com/paritytech/parity-ethereum/releases/download/v1.4.0/parity_1.4.0_amd64.deb.
When I vagrant ssh and check the content of parity.log file, this is the content:
Hi,
I got this error:
Any idea how to make this working?
The text was updated successfully, but these errors were encountered: