ScorpionSting Absent Member.
Absent Member.
936 views

4.5 MAG Appliance

Anyone else have this problem?


MAG:~ # cat activemq.stdout
bash: /opt/novell/activemq/bin/activemq: No such file or directory
bash: /opt/novell/activemq/bin/activemq: No such file or directory
bash: /opt/novell/activemq/bin/activemq: No such file or directory
MAG:~ # la /opt/novell/activemq/bin/
total 16
drwxr-xr-x 2 root root 4096 Apr 13 09:45 .
drwxr-xr-x 3 root root 4096 Apr 4 17:03 ..
-rwxr-x--- 1 root root 3304 Apr 4 15:21 novell-activemq
-rwxr-x--- 1 root root 2412 Apr 4 15:21 novell-activemq.redhat


That and the fact that several directories did not exist:


MAG:~ # mkdir -p /opt/novell/nam/mag/logs/
MAG:~ # mkdir -p /var/opt/novell/amlogging/logs/
MAG:~ # touch /var/opt/novell/amlogging/logs/ags_error.log
MAG:~ # chown novlwww:novlwww /opt/novell/nam/mag/logs/


I'm sorry, but this 4.5 release is riddled with basic issues....its not fit for purpose.

Visit my Website for links to Cool Solution articles.
0 Likes
12 Replies
Knowledge Partner
Knowledge Partner

Re: 4.5 MAG Appliance

On 13-04-2019 9:54 AM, ScorpionSting wrote:
>
> Anyone else have this problem?
>
>
> Code:
> --------------------
>
> MAG:~ # cat activemq.stdout
> bash: /opt/novell/activemq/bin/activemq: No such file or directory
> bash: /opt/novell/activemq/bin/activemq: No such file or directory
> bash: /opt/novell/activemq/bin/activemq: No such file or directory
> MAG:~ # la /opt/novell/activemq/bin/
> total 16
> drwxr-xr-x 2 root root 4096 Apr 13 09:45 .
> drwxr-xr-x 3 root root 4096 Apr 4 17:03 ..
> -rwxr-x--- 1 root root 3304 Apr 4 15:21 novell-activemq
> -rwxr-x--- 1 root root 2412 Apr 4 15:21 novell-activemq.redhat
>
> --------------------
>
>
> That and the fact that several directories did not exist:
>
>
> Code:
> --------------------
>
> MAG:~ # mkdir -p /opt/novell/nam/mag/logs/
> MAG:~ # mkdir -p /var/opt/novell/amlogging/logs/
> MAG:~ # touch /var/opt/novell/amlogging/logs/ags_error.log
> MAG:~ # chown novlwww:novlwww /opt/novell/nam/mag/logs/
>
> --------------------
>
>
> I'm sorry, but this 4.5 release is riddled with basic issues....its not
> fit for purpose.
>
>


I've only upgraded my IDP and AMC yet on RHEL. Yet to do my appliance.

--
Cheers,
Edward
0 Likes
ScorpionSting Absent Member.
Absent Member.

Re: 4.5 MAG Appliance

edmaa;2498307 wrote:
On 13-04-2019 9:54 AM, ScorpionSting wrote:
>
> Anyone else have this problem?
>
>
> Code:
> --------------------
>
> MAG:~ # cat activemq.stdout
> bash: /opt/novell/activemq/bin/activemq: No such file or directory
> bash: /opt/novell/activemq/bin/activemq: No such file or directory
> bash: /opt/novell/activemq/bin/activemq: No such file or directory
> MAG:~ # la /opt/novell/activemq/bin/
> total 16
> drwxr-xr-x 2 root root 4096 Apr 13 09:45 .
> drwxr-xr-x 3 root root 4096 Apr 4 17:03 ..
> -rwxr-x--- 1 root root 3304 Apr 4 15:21 novell-activemq
> -rwxr-x--- 1 root root 2412 Apr 4 15:21 novell-activemq.redhat
>
> --------------------
>
>
> That and the fact that several directories did not exist:
>
>
> Code:
> --------------------
>
> MAG:~ # mkdir -p /opt/novell/nam/mag/logs/
> MAG:~ # mkdir -p /var/opt/novell/amlogging/logs/
> MAG:~ # touch /var/opt/novell/amlogging/logs/ags_error.log
> MAG:~ # chown novlwww:novlwww /opt/novell/nam/mag/logs/
>
> --------------------
>
>
> I'm sorry, but this 4.5 release is riddled with basic issues....its not
> fit for purpose.
>
>


I've only upgraded my IDP and AMC yet on RHEL. Yet to do my appliance.

--
Cheers,
Edward


Be interested to see if you see the same thing...

Visit my Website for links to Cool Solution articles.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: 4.5 MAG Appliance

On 13/04/2019 00:54, ScorpionSting wrote:
>
> Anyone else have this problem?
>
>
> Code:
> --------------------
>
> MAG:~ # cat activemq.stdout
> bash: /opt/novell/activemq/bin/activemq: No such file or directory
> bash: /opt/novell/activemq/bin/activemq: No such file or directory
> bash: /opt/novell/activemq/bin/activemq: No such file or directory
> MAG:~ # la /opt/novell/activemq/bin/
> total 16
> drwxr-xr-x 2 root root 4096 Apr 13 09:45 .
> drwxr-xr-x 3 root root 4096 Apr 4 17:03 ..
> -rwxr-x--- 1 root root 3304 Apr 4 15:21 novell-activemq
> -rwxr-x--- 1 root root 2412 Apr 4 15:21 novell-activemq.redhat
>
> --------------------
>
>
> That and the fact that several directories did not exist:
>
>
> Code:
> --------------------
>
> MAG:~ # mkdir -p /opt/novell/nam/mag/logs/
> MAG:~ # mkdir -p /var/opt/novell/amlogging/logs/
> MAG:~ # touch /var/opt/novell/amlogging/logs/ags_error.log
> MAG:~ # chown novlwww:novlwww /opt/novell/nam/mag/logs/
>
> --------------------
>
>
> I'm sorry, but this 4.5 release is riddled with basic issues....its not
> fit for purpose.
>
>

I don't seem to have this problem on the test Mag Appliance I created on
a fresh address. All these folders exist.

However, I had no joy in following the instructions for making a new
appliance with the same IP as the 4.4 appliance. I shut down the
existing one and basically just ran up a 4.5 one with the same hostname
and IP as the manual suggests. It failed to import into the Admin
console: I tried 3 times so far, and waited a long time. I even
manually triggered the reimport a couple of times. I guess this upgrade
is supposed to find the ID of the old appliance registered on its
address and assume this. If so I'm not convinced it works as yet.

My Admin/IDP upgrade threw the same schema error as you describe in
another thread, though I hadn't noticed anything else not working.

PaulK
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: 4.5 MAG Appliance

Actually I spoke too soon. Tried this again. This time I waited until
I saw:
INFO: Register alert action completed
in the /opt/novell/devman/jcc/logs/jcc-0.log.0

The MAG showed as unreachable still in the admin console which is what I
gave up on before, so since there was no more activity I rebooted the
MAG (and for luck restarted the novell-ac as well!).

When it settled down I saw the migrated MAG show (with the old MAG's ID)
but with a halted status - the Embedded Service Provider's Trusted
Identity Provider said the truststore could not be read. This was true,
the /opt/novell/devman/jcc/certs/esp/[old mag id]/ folder had connector,
encryption and signing keystores but no truststore.keystore. So I just
went into troubleshooting/certificates and repushed the MAG truststore.
Now I appear to have a functional 4.5 MAG Appliance with the old IP, and
old ID.

PaulK

> I don't seem to have this problem on the test Mag Appliance I created on
> a fresh address.  All these folders exist.
>
> However, I had no joy in following the instructions for making a new
> appliance with the same IP as the 4.4 appliance.  I shut down the
> existing one and basically just ran up a 4.5 one with the same hostname
> and IP as the manual suggests.  It failed to import into the Admin
> console: I tried 3 times so far, and waited a long time.  I even
> manually triggered the reimport a couple of times.  I guess this upgrade
> is supposed to find the ID of the old appliance registered on its
> address and assume this.  If so I'm not convinced it works as yet.
>
> My Admin/IDP upgrade threw the same schema error as you describe in
> another thread, though I hadn't noticed anything else not working.
>
> PaulK


0 Likes
ScorpionSting Absent Member.
Absent Member.

Re: 4.5 MAG Appliance

PaulK;2498330 wrote:
Actually I spoke too soon. Tried this again. This time I waited until
I saw:
INFO: Register alert action completed
in the /opt/novell/devman/jcc/logs/jcc-0.log.0

The MAG showed as unreachable still in the admin console which is what I
gave up on before, so since there was no more activity I rebooted the
MAG (and for luck restarted the novell-ac as well!).

When it settled down I saw the migrated MAG show (with the old MAG's ID)
but with a halted status - the Embedded Service Provider's Trusted
Identity Provider said the truststore could not be read. This was true,
the /opt/novell/devman/jcc/certs/esp/[old mag id]/ folder had connector,
encryption and signing keystores but no truststore.keystore. So I just
went into troubleshooting/certificates and repushed the MAG truststore.
Now I appear to have a functional 4.5 MAG Appliance with the old IP, and
old ID.

PaulK

> I don't seem to have this problem on the test Mag Appliance I created on
> a fresh address.Â* All these folders exist.
>
> However, I had no joy in following the instructions for making a new
> appliance with the same IP as the 4.4 appliance.Â* I shut down the
> existing one and basically just ran up a 4.5 one with the same hostname
> and IP as the manual suggests.Â* It failed to import into the Admin
> console: I tried 3 times so far, and waited a long time.Â* I even
> manually triggered the reimport a couple of times.Â* I guess this upgrade
> is supposed to find the ID of the old appliance registered on its
> address and assume this.Â* If so I'm not convinced it works as yet.
>
> My Admin/IDP upgrade threw the same schema error as you describe in
> another thread, though I hadn't noticed anything else not working.
>
> PaulK


Interesting....thanks PaulK for your observations.... I was doing the latter option as well (OVF => same host/ip)... I will try again over easter, leave it for more than the 30 minutes I tried last time *big rolling eyes*....

Visit my Website for links to Cool Solution articles.
0 Likes
Knowledge Partner
Knowledge Partner

Re: 4.5 MAG Appliance

On 13-04-2019 9:54 AM, ScorpionSting wrote:
>
> Anyone else have this problem?
>
>
> Code:
> --------------------
>
> MAG:~ # cat activemq.stdout
> bash: /opt/novell/activemq/bin/activemq: No such file or directory
> bash: /opt/novell/activemq/bin/activemq: No such file or directory
> bash: /opt/novell/activemq/bin/activemq: No such file or directory
> MAG:~ # la /opt/novell/activemq/bin/
> total 16
> drwxr-xr-x 2 root root 4096 Apr 13 09:45 .
> drwxr-xr-x 3 root root 4096 Apr 4 17:03 ..
> -rwxr-x--- 1 root root 3304 Apr 4 15:21 novell-activemq
> -rwxr-x--- 1 root root 2412 Apr 4 15:21 novell-activemq.redhat
>
> --------------------
>
>
> That and the fact that several directories did not exist:
>
>
> Code:
> --------------------
>
> MAG:~ # mkdir -p /opt/novell/nam/mag/logs/
> MAG:~ # mkdir -p /var/opt/novell/amlogging/logs/
> MAG:~ # touch /var/opt/novell/amlogging/logs/ags_error.log
> MAG:~ # chown novlwww:novlwww /opt/novell/nam/mag/logs/
>
> --------------------
>
>
> I'm sorry, but this 4.5 release is riddled with basic issues....its not
> fit for purpose.
>
>


appliance:~/NAM-singlebox-4.5.0.0-189 # ll /opt/novell/activemq/bin/
total 140
-rwxr-xr-x 1 root root 5091 Jan 12 08:06 activemq
-rw-r--r-- 1 root root 5078 Jan 12 08:06 activemq-admin
drwxr-xr-x 2 root root 4096 Jan 12 08:06 linux-x86-32
drwxr-xr-x 2 root root 4096 Jan 12 08:06 linux-x86-64
drwxr-xr-x 2 root root 4096 Jan 12 08:06 macosx
-rwxr-x--- 1 root root 3304 Apr 4 15:21 novell-activemq
-rwxr-x--- 1 root root 2412 Apr 4 15:21 novell-activemq.redhat
-rw-r--r-- 1 root root 14014 Jan 12 08:06 run.jar
-rw-r--r-- 1 root root 83820 Jan 12 08:06 wrapper.jar
appliance:~/NAM-singlebox-4.5.0.0-189 #

This is an upgrade tho, not a plain install

--
Cheers,
Edward
0 Likes
Knowledge Partner
Knowledge Partner

Re: 4.5 MAG Appliance

On 16-04-2019 7:34 AM, Edward van der Maas wrote:
> On 13-04-2019 9:54 AM, ScorpionSting wrote:
>>
>> Anyone else have this problem?
>>
>>
>> Code:
>> --------------------
>>    MAG:~ # cat activemq.stdout
>>    bash: /opt/novell/activemq/bin/activemq: No such file or directory
>>    bash: /opt/novell/activemq/bin/activemq: No such file or directory
>>    bash: /opt/novell/activemq/bin/activemq: No such file or directory
>>    MAG:~ # la /opt/novell/activemq/bin/
>>    total 16
>>    drwxr-xr-x 2 root root 4096 Apr 13 09:45 .
>>    drwxr-xr-x 3 root root 4096 Apr  4 17:03 ..
>>    -rwxr-x--- 1 root root 3304 Apr  4 15:21 novell-activemq
>>    -rwxr-x--- 1 root root 2412 Apr  4 15:21 novell-activemq.redhat
>> --------------------
>>
>>
>> That and the fact that several directories did not exist:
>>
>>
>> Code:
>> --------------------
>>    MAG:~ # mkdir -p /opt/novell/nam/mag/logs/
>>    MAG:~ # mkdir -p /var/opt/novell/amlogging/logs/
>>    MAG:~ # touch /var/opt/novell/amlogging/logs/ags_error.log
>>    MAG:~ # chown novlwww:novlwww /opt/novell/nam/mag/logs/
>> --------------------
>>
>>
>> I'm sorry, but this 4.5 release is riddled with basic issues....its not
>> fit for purpose.
>>
>>

>
> appliance:~/NAM-singlebox-4.5.0.0-189 # ll /opt/novell/activemq/bin/
> total 140
> -rwxr-xr-x 1 root root  5091 Jan 12 08:06 activemq
> -rw-r--r-- 1 root root  5078 Jan 12 08:06 activemq-admin
> drwxr-xr-x 2 root root  4096 Jan 12 08:06 linux-x86-32
> drwxr-xr-x 2 root root  4096 Jan 12 08:06 linux-x86-64
> drwxr-xr-x 2 root root  4096 Jan 12 08:06 macosx
> -rwxr-x--- 1 root root  3304 Apr  4 15:21 novell-activemq
> -rwxr-x--- 1 root root  2412 Apr  4 15:21 novell-activemq.redhat
> -rw-r--r-- 1 root root 14014 Jan 12 08:06 run.jar
> -rw-r--r-- 1 root root 83820 Jan 12 08:06 wrapper.jar
> appliance:~/NAM-singlebox-4.5.0.0-189 #
>
> This is an upgrade tho, not a plain install
>


Oh...duh...this is not just a MAG, this is the appliance...

--
Cheers,
Edward
0 Likes
ScorpionSting Absent Member.
Absent Member.

Re: 4.5 MAG Appliance

edmaa;2498381 wrote:
On 16-04-2019 7:34 AM, Edward van der Maas wrote:
> On 13-04-2019 9:54 AM, ScorpionSting wrote:
>>
>> Anyone else have this problem?
>>
>>
>> Code:
>> --------------------
>> Â*Â* MAG:~ # cat activemq.stdout
>> Â*Â* bash: /opt/novell/activemq/bin/activemq: No such file or directory
>> Â*Â* bash: /opt/novell/activemq/bin/activemq: No such file or directory
>> Â*Â* bash: /opt/novell/activemq/bin/activemq: No such file or directory
>> Â*Â* MAG:~ # la /opt/novell/activemq/bin/
>> Â*Â* total 16
>> Â*Â* drwxr-xr-x 2 root root 4096 Apr 13 09:45 .
>> Â*Â* drwxr-xr-x 3 root root 4096 AprÂ* 4 17:03 ..
>> Â*Â* -rwxr-x--- 1 root root 3304 AprÂ* 4 15:21 novell-activemq
>> Â*Â* -rwxr-x--- 1 root root 2412 AprÂ* 4 15:21 novell-activemq.redhat
>> --------------------
>>
>>
>> That and the fact that several directories did not exist:
>>
>>
>> Code:
>> --------------------
>> Â*Â* MAG:~ # mkdir -p /opt/novell/nam/mag/logs/
>> Â*Â* MAG:~ # mkdir -p /var/opt/novell/amlogging/logs/
>> Â*Â* MAG:~ # touch /var/opt/novell/amlogging/logs/ags_error.log
>> Â*Â* MAG:~ # chown novlwww:novlwww /opt/novell/nam/mag/logs/
>> --------------------
>>
>>
>> I'm sorry, but this 4.5 release is riddled with basic issues....its not
>> fit for purpose.
>>
>>

>
> appliance:~/NAM-singlebox-4.5.0.0-189 # ll /opt/novell/activemq/bin/
> total 140
> -rwxr-xr-x 1 root rootÂ* 5091 Jan 12 08:06 activemq
> -rw-r--r-- 1 root rootÂ* 5078 Jan 12 08:06 activemq-admin
> drwxr-xr-x 2 root rootÂ* 4096 Jan 12 08:06 linux-x86-32
> drwxr-xr-x 2 root rootÂ* 4096 Jan 12 08:06 linux-x86-64
> drwxr-xr-x 2 root rootÂ* 4096 Jan 12 08:06 macosx
> -rwxr-x--- 1 root rootÂ* 3304 AprÂ* 4 15:21 novell-activemq
> -rwxr-x--- 1 root rootÂ* 2412 AprÂ* 4 15:21 novell-activemq.redhat
> -rw-r--r-- 1 root root 14014 Jan 12 08:06 run.jar
> -rw-r--r-- 1 root root 83820 Jan 12 08:06 wrapper.jar
> appliance:~/NAM-singlebox-4.5.0.0-189 #
>
> This is an upgrade tho, not a plain install
>


Oh...duh...this is not just a MAG, this is the appliance...

--
Cheers,
Edward


Ha! Well, at least that looks alright 😉

Visit my Website for links to Cool Solution articles.
0 Likes
Not applicable

Re: 4.5 MAG Appliance

I ran into the same issue attempting a migration method upgrade from 4.4 to 4.5, where Gateway Appliance installed without issue however would not attach to the Access Management (waiting up to an hour to turn green). After re-deployments and checking documentation, checking logs ect.ect. I stumbled upon the forums and found your post regarding 4.5. My issue turned out to be special characters in admin password, after creating a backup admin user (or have a snapshot of virtual machine), changing admin password eliminating special characters. Once a redeploy of the Gateway Appliance and feeding in Access Manager URL/ADMIN/PASSWORD the console screen produced numerous outputs that it was restarting services and /tmp/novell_access_manager had install logs that showed successful. BTW I also ran into a similar issue with Identity Manager edirectory installer does not like Admin user with special character passwords as well, refused to upgrade the product.
0 Likes
ScorpionSting Absent Member.
Absent Member.

Re: 4.5 MAG Appliance

gw_bmitchell;2498439 wrote:
I ran into the same issue attempting a migration method upgrade from 4.4 to 4.5, where Gateway Appliance installed without issue however would not attach to the Access Management (waiting up to an hour to turn green). After re-deployments and checking documentation, checking logs ect.ect. I stumbled upon the forums and found your post regarding 4.5. My issue turned out to be special characters in admin password, after creating a backup admin user (or have a snapshot of virtual machine), changing admin password eliminating special characters. Once a redeploy of the Gateway Appliance and feeding in Access Manager URL/ADMIN/PASSWORD the console screen produced numerous outputs that it was restarting services and /tmp/novell_access_manager had install logs that showed successful. BTW I also ran into a similar issue with Identity Manager edirectory installer does not like Admin user with special character passwords as well, refused to upgrade the product.


Thanks for your inputs gw_bmitchell... I think what I'll do over Easter is try the OVF leaving the password complex with special then, if it fails again, try again with a simple password....that was I should be able to narrow down if there is a scripting problem with the OVF appliance (trying to trace it could be entertaining).

Visit my Website for links to Cool Solution articles.
0 Likes
ScorpionSting Absent Member.
Absent Member.

Re: 4.5 MAG Appliance

ScorpionSting;2498305 wrote:
Anyone else have this problem?


MAG:~ # cat activemq.stdout
bash: /opt/novell/activemq/bin/activemq: No such file or directory
bash: /opt/novell/activemq/bin/activemq: No such file or directory
bash: /opt/novell/activemq/bin/activemq: No such file or directory
MAG:~ # la /opt/novell/activemq/bin/
total 16
drwxr-xr-x 2 root root 4096 Apr 13 09:45 .
drwxr-xr-x 3 root root 4096 Apr 4 17:03 ..
-rwxr-x--- 1 root root 3304 Apr 4 15:21 novell-activemq
-rwxr-x--- 1 root root 2412 Apr 4 15:21 novell-activemq.redhat


That and the fact that several directories did not exist:


MAG:~ # mkdir -p /opt/novell/nam/mag/logs/
MAG:~ # mkdir -p /var/opt/novell/amlogging/logs/
MAG:~ # touch /var/opt/novell/amlogging/logs/ags_error.log
MAG:~ # chown novlwww:novlwww /opt/novell/nam/mag/logs/


I'm sorry, but this 4.5 release is riddled with basic issues....its not fit for purpose.


Confirmed that the issue is with a complex AC password, the behaviour is completely different.

With a complex password, the "Access Gateway Configuration" comes back reasonably quickly with the success message, but nothing happens and the appliance is stuffed.

With a simple password, the "Access Gateway Configuration" takes time to respond and the console shows the import has begun.

Visit my Website for links to Cool Solution articles.
0 Likes
Knowledge Partner
Knowledge Partner

Re: 4.5 MAG Appliance

On 22-04-2019 12:44 PM, ScorpionSting wrote:
>


> Confirmed that the issue is with a complex AC password, the behaviour is
> completely different.
>
> With a complex password, the "Access Gateway Configuration" comes back
> reasonably quickly with the success message, but nothing happens and the
> appliance is stuffed.
>
> With a simple password, the "Access Gateway Configuration" takes time to
> respond and the console shows the import has begun.
>
>


Any complex string and bash is always a PITA to be honest.

--
Cheers,
Edward
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.