Hi there,

We recently encountered our WAS Profile stopping/shutting down by itself affecting three (3) LPARs with WAS 8.5.x running on AIX 7.2. It happened last night, around 8PM, Nov 25, 2024 and it happened again this morning, about 9AM, Nov 26, 2024.

We need to identify the root cause so we can prevent the "auto" shutdown/stop of the WAS profile.

This is affecting our production systems.

Thanks.

Bobbie

Hi, did you check the logs to see if it was an orderly shutdown or did they crash?  Is there anything in the deployment manager logs at the time?  What about the AIX system logs?  Are you sure there are no cron or other jobs to shutdown the JVMs?

Brian

Hi there,

We recently encountered our WAS Profile stopping/shutting down by itself affecting three (3) LPARs with WAS 8.5.x running on AIX 7.2. It happened last night, around 8PM, Nov 25, 2024 and it happened again this morning, about 9AM, Nov 26, 2024.

We need to identify the root cause so we can prevent the "auto" shutdown/stop of the WAS profile.

This is affecting our production systems.

Thanks.

Bobbie

Hi,

First we checked the WAS log, from there we can see the following:

"ADMN1020I: An attempt is made to stop the server1 server. (User ID = defaultWIMFileBasedRealm/wasadmin)"

On AIX, what particular log do we need to review?

B

Hi, did you check the logs to see if it was an orderly shutdown or did they crash?  Is there anything in the deployment manager logs at the time?  What about the AIX system logs?  Are you sure there are no cron or other jobs to shutdown the JVMs?

Brian

Hi there,

We recently encountered our WAS Profile stopping/shutting down by itself affecting three (3) LPARs with WAS 8.5.x running on AIX 7.2. It happened last night, around 8PM, Nov 25, 2024 and it happened again this morning, about 9AM, Nov 26, 2024.

We need to identify the root cause so we can prevent the "auto" shutdown/stop of the WAS profile.

This is affecting our production systems.

Thanks.

Bobbie

"ADMN1020I: An attempt is made to stop the server1 server. (User ID = defaultWIMFileBasedRealm/wasadmin)"

It looks like someone or a scheduled process is trying to stop the app server.  You will need to see what happened on the system at that time.

Brian

Hi,

First we checked the WAS log, from there we can see the following:

"ADMN1020I: An attempt is made to stop the server1 server. (User ID = defaultWIMFileBasedRealm/wasadmin)"

On AIX, what particular log do we need to review?

B

Hi, did you check the logs to see if it was an orderly shutdown or did they crash?  Is there anything in the deployment manager logs at the time?  What about the AIX system logs?  Are you sure there are no cron or other jobs to shutdown the JVMs?

Brian

Hi there,

We recently encountered our WAS Profile stopping/shutting down by itself affecting three (3) LPARs with WAS 8.5.x running on AIX 7.2. It happened last night, around 8PM, Nov 25, 2024 and it happened again this morning, about 9AM, Nov 26, 2024.

We need to identify the root cause so we can prevent the "auto" shutdown/stop of the WAS profile.

This is affecting our production systems.

Thanks.

Bobbie

Hi,

Thanks for the insight. Any guidance on what I should look for in the logs that can provide a clue on why the WAS shutdown?

B

"ADMN1020I: An attempt is made to stop the server1 server. (User ID = defaultWIMFileBasedRealm/wasadmin)"

It looks like someone or a scheduled process is trying to stop the app server.  You will need to see what happened on the system at that time.

Brian

Hi,

First we checked the WAS log, from there we can see the following:

"ADMN1020I: An attempt is made to stop the server1 server. (User ID = defaultWIMFileBasedRealm/wasadmin)"

On AIX, what particular log do we need to review?

B

Hi, did you check the logs to see if it was an orderly shutdown or did they crash?  Is there anything in the deployment manager logs at the time?  What about the AIX system logs?  Are you sure there are no cron or other jobs to shutdown the JVMs?

Brian

Hi there,

We recently encountered our WAS Profile stopping/shutting down by itself affecting three (3) LPARs with WAS 8.5.x running on AIX 7.2. It happened last night, around 8PM, Nov 25, 2024 and it happened again this morning, about 9AM, Nov 26, 2024.

We need to identify the root cause so we can prevent the "auto" shutdown/stop of the WAS profile.

This is affecting our production systems.

Thanks.

Bobbie

Hi,

Thanks for the insight. Any guidance on what I should look for in the logs that can provide a clue on why the WAS shutdown?

B

"ADMN1020I: An attempt is made to stop the server1 server. (User ID = defaultWIMFileBasedRealm/wasadmin)"

It looks like someone or a scheduled process is trying to stop the app server.  You will need to see what happened on the system at that time.

Brian

Hi,

First we checked the WAS log, from there we can see the following:

"ADMN1020I: An attempt is made to stop the server1 server. (User ID = defaultWIMFileBasedRealm/wasadmin)"

On AIX, what particular log do we need to review?

B

Hi, did you check the logs to see if it was an orderly shutdown or did they crash?  Is there anything in the deployment manager logs at the time?  What about the AIX system logs?  Are you sure there are no cron or other jobs to shutdown the JVMs?

Brian

Hi there,

We recently encountered our WAS Profile stopping/shutting down by itself affecting three (3) LPARs with WAS 8.5.x running on AIX 7.2. It happened last night, around 8PM, Nov 25, 2024 and it happened again this morning, about 9AM, Nov 26, 2024.

We need to identify the root cause so we can prevent the "auto" shutdown/stop of the WAS profile.

This is affecting our production systems.

Thanks.

Bobbie

Hello Bobbie,

well - obviously somewith knowing the password from user wasadmin is shutting down the systems. So it is hard to say where the request comes from. Is wasadmin this a technical user? Or is it used in daily operations for the admin console? Scripts etc.? When and how often does this happen?

Options coming to my mind (not a priority)

• Monitor the access to the WAS SOAP board at the IP level. This might give you an idea from where WAS was accessed at the time WAS what stopped
• Change the password of the wasadmin user and see which job failes / who complains?

Hi,

Thanks for the insight. Any guidance on what I should look for in the logs that can provide a clue on why the WAS shutdown?

B

"ADMN1020I: An attempt is made to stop the server1 server. (User ID = defaultWIMFileBasedRealm/wasadmin)"

It looks like someone or a scheduled process is trying to stop the app server.  You will need to see what happened on the system at that time.

Brian

Hi,

First we checked the WAS log, from there we can see the following:

"ADMN1020I: An attempt is made to stop the server1 server. (User ID = defaultWIMFileBasedRealm/wasadmin)"

On AIX, what particular log do we need to review?

B

Hi, did you check the logs to see if it was an orderly shutdown or did they crash?  Is there anything in the deployment manager logs at the time?  What about the AIX system logs?  Are you sure there are no cron or other jobs to shutdown the JVMs?

Brian

Hi there,

We recently encountered our WAS Profile stopping/shutting down by itself affecting three (3) LPARs with WAS 8.5.x running on AIX 7.2. It happened last night, around 8PM, Nov 25, 2024 and it happened again this morning, about 9AM, Nov 26, 2024.

We need to identify the root cause so we can prevent the "auto" shutdown/stop of the WAS profile.

This is affecting our production systems.

Thanks.

Bobbie