AAUTH Version: 6.4.2.1, Framework: 2.2.1.3 high cpu

Falk Heiland 10 months ago

today i updated to 6.4.2.1 and now i am having a very high cpu usage on the active node:

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
15856 vaadmin 20 0 4181588 1.388g 178832 S 285.1 8.867 0:08.89 java

if i try to add a metric to the dashbard i get this error:

ConnectionError ConnectionError(: Failed to establish a new connection: [Errno 111] Connection refused) caused by: NewConnectionError(: Failed to establish a new connection: [Errno 111] Connection refused) (Internal Server Error)

Verified Answer

0 Luciano Testa OpenText Employee

10 months ago

Hello Falk,

Based on that error it could be caused by this. See the notes in the AAF 6.4 SP 2 Release Notes:

IMPORTANT: Before attempting to upgrade from Advanced Authentication 6.4.x to 6.4.2, it is recommended to verify that the server has minimum of 40% free disk space for seamless upgrade and performance.

Use the following command in the appliance console to verify the free disk space:

df -h /dev/sda1

Please check this first and let us know.

Thanks.

Regards,

Luciano Testa

0 Falk Heiland 10 months ago in reply to Luciano Testa

the update did succeed btw, i get the error afterwards.

diskspace should not be an issue

xyz:~ # df -h /dev/sda1
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 59G 20G 37G 35% /
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Falk Heiland 10 months ago in reply to Luciano Testa
if i try and connect to the "Enrollment" -Page via servadmin portal (9443) i get :

{"status": "error", "errors": [{"location": "server", "name": "AuError", "msgid": null, "description": "Configured host name doesn't match provided hostname. The Administrator should verify that the Public External URL is set properly."}], "reason": "NOT_CONFIGURED"}

i guess there has been a change to the public url - idk if this was even a thing back when i first configured that software. let me see if i even find such a setting.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Luciano Testa 10 months ago in reply to Falk Heiland

There are two things to validate that are set correctly:

1. Policies | Web Authentication | Identity Provider URL
This is used by the OSP.

2. Policies | Public external URLs (load balancers)
Site <default> should be set to a valid DNS name.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Menu

Advanced Authentication Discussions

AAUTH Version: 6.4.2.1, Framework: 2.2.1.3 high cpu

Verified Answer

Resources