bstopp/puppet-aem

Unrecognized option during Jar unpack

Closed this issue · 5 comments

Notice: /Stage[main]/Main/Aem::Instance[instance.example.com-author]/Aem::Package[instance.example.com-author]/Exec[instance.example.com-author unpack]/returns: 25.07.2016 12:14:00.799 *ERROR* [main] -b: Unrecognized option (use -h for more information)
Notice: /Stage[main]/Main/Aem::Instance[instance.example.com-author]/Aem::Package[instance.example.com-author]/Exec[instance.example.com-author unpack]/returns: 25.07.2016 12:14:00.800 *ERROR* [main] -u: Unrecognized option (use -h for more information)
Error: java -jar /opt/aem-quickstart.jar -b /opt/aem/author -unpack returned 1 instead of one of [0]
Error: /Stage[main]/Main/Aem::Instance[instance.example.com-author]/Aem::Package[instance.example.com-author]/Exec[instance.example.com-author unpack]/returns: change from notrun to 0 failed: java -jar /opt/aem-quickstart.jar -b /opt/aem/author -unpack returned 1 instead of one of [0]

Using

[root@dlmhaem02 ~]# java -version
java version "1.8.0_101"
Java(TM) SE Runtime Environment (build 1.8.0_101-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.101-b13, mixed mode)
[root@dlmhaem02 ~]# lsb_release -a
LSB Version:    :core-4.1-amd64:core-4.1-noarch
Distributor ID: CentOS
Description:    CentOS Linux release 7.2.1511 (Core)
Release:        7.2.1511
Codename:       Core
[root@dlmhaem02 ~]# uname -a
Linux dlmhaem02 3.10.0-327.22.2.el7.x86_64 #1 SMP Thu Jun 23 17:05:11 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Let me know if I can provide any other information.

Version of the AEM Jar File?

6.1

On Jul 25, 2016 1:35 PM, "Bryan" notifications@github.com wrote:

Version of the AEM Jar File?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#60 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHJ7HpB173eYuHqjYPs9ymKlBkYBx0ULks5qZQH6gaJpZM4JUWWs
.

You have a bad Jar file; I've got 10 6.1 VM's working no prob. Are you sure you're using a quickstart jar and not the standalone ?

Non-repeatable issue. Source jar probably culprit.

Confirmed.