Runnable stuck in STOPPING status. Unable to kill it.

Posted by Pedro Guerrero

Posted on Mon, 03/12/2018 - 18:13 in Administration & User Management

Hello everyone.

I just noticed that our ARIS Connect instance is down. After trying to restart the runnables in the ACC console I noticed the following:

- The runnable called zoo_m is permanently in STOPPING status

- While try to kill it, got an error message (see below)

- I cannot issue a 'startall' command either because "the runnable zoo_m is STOPPED and cannot be started"

- I've restarted the machine twice but the problem persists

This is a similar issue reported on ARIS Community: http://www.ariscommunity.com/users/ambrish6/2015-10-22-runnable-apgm-starting-stage

The ARIS Basic Troubleshooting guide suggests issuing the kill command (4.8. Runnables do not start). However, it wasn't successful.

Any idea on how to address this?

Thank you in advance for your help

Regards

Pedro.

6.1k

by Runé Becker

Posted on Tue, 03/13/2018 - 10:06

Dear Pedro,

So you tried to rebooted that computer where ARIS is installed, and then found the runnable zoo_m still in status STOPPING?

That would be strange, because the status STOPPING isn't an initial status which a runnable could reach.

The error message in your screenshot "unable to write runnable configuration file". Did you change any credentials, such as the password of the ARIS Agent's account "Clous"? Or was a Windows user account's data access privilege changed?

Cheers

Rune

by Pedro Guerrero Author

Posted on Tue, 03/13/2018 - 14:32

Hello Rune

Here are my answers:

So you tried to rebooted that computer where ARIS is installed, and then found the runnable zoo_m still in status STOPPING?

Yes, I did

That would be strange, because the status STOPPING isn't an initial status which a runnable could reach.

Quite strange. Just did a reboot today, the zoo_m runnable is in state STARTING but it gets stuck:

The error message in your screenshot "unable to write runnable configuration file". Did you change any credentials, such as the password of the ARIS Agent's account "Clous"? Or was a Windows user account's data access privilege changed?

Upon further review, no password has been yet changed. I log in with the administrator user as of now.

Thank you again for your help, Rune.

Have a nice day.