Bug 1458672 - DV 6.4 installation on windows fails during the EAP patch step
Summary: DV 6.4 installation on windows fails during the EAP patch step
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Installer
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: DR4
: 6.4.0
Assignee: Thomas Hauser
QA Contact: Jan Stastny
URL:
Whiteboard:
Depends On: 1408961
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-05 07:48 UTC by Andrej Smigala
Modified: 2018-02-13 17:36 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-13 17:36:59 UTC
Type: Bug


Attachments (Terms of Use)

Description Andrej Smigala 2017-06-05 07:48:28 UTC
When running the DR3 installer on windows, it fails during the step which patches EAP 6.4.9 to 6.4.15

This is logged in the console:

IzPack variable state written to C:\Users\Administrator\DV-6.4.0-DR3\installation\InstallationLog.txt
Running command:[C:\Users\Administrator\DV-6.4.0-DR3\bin\jboss-cli.bat, "patch apply C:\Users\Administrator\DV-6.4.0-DR3\jboss-eap-6.4.9-patch.zip"]
{
    "outcome" : "success",
    "result" : {}
}
Exit code: 0
Command success: [C:\Users\Administrator\DV-6.4.0-DR3\bin\jboss-cli.bat, "patch apply C:\Users\Administrator\DV-6.4.0-DR3\jboss-eap-6.4.9-patch.zip"] completed successfully.
Running command:[C:\Users\Administrator\DV-6.4.0-DR3\bin\jboss-cli.bat, "patch apply C:\Users\Administrator\DV-6.4.0-DR3\jboss-eap-6.4.15-patch.zip"]
{
    "outcome" : "success",
    "result" : {}
}
patching exception
Exit code: 1
Command failure: [C:\Users\Administrator\DV-6.4.0-DR3\bin\jboss-cli.bat, "patch apply C:\Users\Administrator\DV-6.4.0-DR3\jboss-eap-6.4.15-patch.zip"] failed with exit code: 1
Running on-fail server check.
Server startup not recorded. No need to shut it down.
Shutting server down.
Trying to connect to Management Interface...(1/5).
Trying to connect to Management Interface...(2/5).
Trying to connect to Management Interface...(3/5).
Trying to connect to Management Interface...(4/5).
Trying to connect to Management Interface...(5/5).
Failed to connect to Management Interface after 5 attempts.
{"outcome" => "failed","failure-description" => "No ModelControllerClient was available to execute the request.","command" => ":shutdown"}
The configured source file: C:\Users\Administrator\DV-6.4.0-DR3\standalone\log\server.log doesn't exist.
The configured source file: C:\Users\Administrator\DV-6.4.0-DR3\domain\log\host-controller.log doesn't exist.
The configured source file: C:\Users\Administrator\DV-6.4.0-DR3\domain\log\process-controller.log doesn't exist.


Note You need to log in before you can comment on or make changes to this bug.