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

could not load Jenkins site locally (connection reset) #29

Open
meowsbits opened this issue Jun 19, 2020 · 0 comments
Open

could not load Jenkins site locally (connection reset) #29

meowsbits opened this issue Jun 19, 2020 · 0 comments
Labels
bug Something isn't working

Comments

@meowsbits
Copy link
Member

> git rev-parse HEAD ; lsb_release -a
6ef05e36098d81750fe35124f98c87a566c6892a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.4 LTS
Release:        18.04
Codename:       bionic
> vagrant up jenkins                                                                                                          
==> vagrant: A new version of Vagrant is available: 2.2.9 (installed version: 2.2.3)!                       
==> vagrant: To upgrade visit: https://www.vagrantup.com/downloads.html
                                                                
/tmp/.mount_vagrank7URNz/usr/gembundle/gems/vagrant-2.2.3/lib/vagrant/util/which.rb:37: warning: Insecure world writable dir /home/ia/.gem/bin in PATH, mode 040777
Bringing machine 'jenkins' up with 'virtualbox' provider...                         
==> jenkins: Clearing any previously set forwarded ports...      
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                         
==> jenkins: Clearing any previously set network interfaces...              
==> jenkins: Preparing network interfaces based on configuration...
    jenkins: Adapter 1: nat                             
    jenkins: Adapter 2: hostonly                                                               
==> jenkins: Forwarding ports...                              
    jenkins: 8080 (guest) => 8080 (host) (adapter 1)         
    jenkins: 22 (guest) => 2222 (host) (adapter 1)                        
==> jenkins: Running 'pre-boot' VM customizations...         
==> jenkins: Booting VM...                                 
==> jenkins: Waiting for machine to boot. This may take a few minutes...
    jenkins: SSH address: 127.0.0.1:2222                          
    jenkins: SSH username: vagrant                           
    jenkins: SSH auth method: private key
==> jenkins: Machine booted and ready!                     
[jenkins] GuestAdditions versions on your host (5.2.34) and guest (5.2.18) do not match.
Reading package lists...                                         
Building dependency tree...                                                                                                                                        
Reading state information...                                                              
dkms is already the newest version (2.3-3ubuntu9.2).          
linux-headers-4.15.0-29-generic is already the newest version (4.15.0-29.31).
The following packages were automatically installed and are no longer required:
  python-asn1crypto python-cffi-backend python-crypto python-cryptography
  python-enum34 python-httplib2 python-idna python-ipaddress python-jinja2
  python-markupsafe python-paramiko python-pkg-resources python-pyasn1
  python-setuptools python-six python-yaml sshpass                 
Use 'sudo apt autoremove' to remove them.      
0 upgraded, 0 newly installed, 0 to remove and 33 not upgraded.
Downloading VirtualBox Guest Additions ISO from http://download.virtualbox.org/virtualbox/5.2.34/VBoxGuestAdditions_5.2.34.iso
Copy iso file /home/ia/.vagrant.d/tmp/VBoxGuestAdditions_5.2.34.iso into the box /tmp/VBoxGuestAdditions.iso
Mounting Virtualbox Guest Additions ISO to: /mnt
mount: /mnt: WARNING: device write-protected, mounted read-only.
Installing Virtualbox Guest Additions 5.2.34 - guest version is 5.2.18
Verifying archive integrity... All good.
Uncompressing VirtualBox 5.2.34 Guest Additions for Linux........
VirtualBox Guest Additions installer
Removing installed version 5.2.18 of VirtualBox Guest Additions...
Copying additional installer modules ...
Installing additional modules ...
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel
modules.  This may take a while.
VirtualBox Guest Additions: To build modules for other installed kernels, run
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup <version>
VirtualBox Guest Additions: Building the modules for kernel 4.15.0-29-generic.
update-initramfs: Generating /boot/initrd.img-4.15.0-29-generic
VirtualBox Guest Additions: Running kernel modules will not be replaced until
the system is restarted
VirtualBox Guest Additions: Starting.
An error occurred during installation of VirtualBox Guest Additions 5.2.34. Some functionality may not work as intended.
In most cases it is OK that the "Window System drivers" installation failed.
Unmounting Virtualbox Guest Additions ISO from: /mnt
Cleaning up downloaded VirtualBox Guest Additions ISO...
Got different reports about installed GuestAdditions version:
Virtualbox on your host claims:   5.2.18
VBoxService inside the vm claims: 5.2.34
Going on, assuming VBoxService is correct...
Got different reports about installed GuestAdditions version:
Virtualbox on your host claims:   5.2.18
VBoxService inside the vm claims: 5.2.34
Going on, assuming VBoxService is correct...
==> jenkins: Checking for guest additions in VM...
==> jenkins: Setting hostname...
==> jenkins: Configuring and enabling network interfaces...
==> jenkins: Mounting shared folders...
    jenkins: /vagrant => /home/ia/dev/etclabscore/jenkins-vagrant
==> jenkins: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> jenkins: flag to force provisioning. Provisioners marked to run always will still run.

image

@meowsbits meowsbits added the bug Something isn't working label Jun 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant