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

vagrant stops provisioning at glassfish4 #69

Closed
edgecase1 opened this issue Dec 15, 2016 · 5 comments
Closed

vagrant stops provisioning at glassfish4 #69

edgecase1 opened this issue Dec 15, 2016 · 5 comments

Comments

@edgecase1
Copy link

edgecase1 commented Dec 15, 2016

Issue Description

vagrant stops provisioning at glassfish4 (see last output). Reprovisoning results in the output below:

vagrant.exe up --provision
...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Setting hostname...
==> default: Configuring and enabling network interfaces...
==> default: Mounting shared folders...
    default: /vagrant => C:/Users/Reinhard/Desktop/metasploitable3
==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> default: flag to force provisioning. Provisioners marked to run always will still run.
==> default: Running provisioner: shell...
    default: Running: scripts/installs/install_boxstarter.bat as c:\tmp\vagrant-shell.bat
==> default: C:\Windows\system32>net start "domain1 GlassFish Server"
==> default: The requested service has already been started.
==> default:
==> default:
==> default: More help is available by typing NET HELPMSG 2182.
The following WinRM command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

Host System

  • OS: Windows 10
  • Packer Version: 0.12.0
  • Vagrant Version: 1.9.1
  • VirtualBox Version: 5.1.10

Command Output

vagrant up
...
==> default: processed file: C:\glassfish\glassfish4\pkg\javadocs\com\sun\pkg\client\Version.html
==> default:
==> default: processed file: C:\glassfish\glassfish4\pkg\javadocs\resources\inherit.gif
==> default: processed file: C:\glassfish\glassfish4\pkg\lib\pkg-bootstrap.jar
==> default: processed file: C:\glassfish\glassfish4\pkg\lib\pkg-bootstub.bat
==> default:
==> default: processed file: C:\glassfish\glassfish4\pkg\lib\pkg-bootstub.sh
==> default: processed file: C:\glassfish\glassfish4\pkg\lib\pkg-client.jar
==> default: Successfully processed 3439 files; Failed processing 0 files
==> default: C:\Windows\system32>sc config domain1 obj= "NT Authority\LOCAL SERVICE"
==> default: [SC] ChangeServiceConfig SUCCESS
==> default: Running provisioner: shell...
    default: Running: inline PowerShell script
==> default: Running provisioner: shell...
    default: Running: scripts/installs/start_glassfish_service.bat as c:\tmp\vagrant-shell.bat
==> default: C:\Windows\system32>net start "domain1 GlassFish Server"
==> default: The service is starting or stopping.  Please try again later.
The following WinRM command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

c:\tmp\vagrant-shell.bat

Stdout from the command:



Stderr from the command:
@derhornspieler
Copy link

derhornspieler commented Dec 18, 2016

@Catmin I ended up destroying the provision and am now reinstalling with the edited .bat another member made by @Centurion89 proposed.

@jbarnett-r7
Copy link
Contributor

This should have been fixed by this commit: 5130f49

Let us know if you're still seeing issues.

@edgecase1
Copy link
Author

works for me! thanks

@TheBlindHacker
Copy link

I am having a similar issue check #115

@gearcapitan
Copy link

#112 I am having a similar issue check

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

5 participants