Could not start runnable loadbalancer_m on node localhost: Ant start exited with 1

Posted by Eka Widhi

Posted on Fri, 08/27/2021 - 11:16 in Professional ARIS

Hello,

I'm having trouble when I want to turn on loadbalancer_m in ARIS10, a message appears: "Could not start runnable loadbalancer_m on node localhost: Ant start exited with 1"

How to solve it.

Thank you.

503

by Veronika Ellermann

Posted on Mon, 08/30/2021 - 13:13

Hi Eka,

I would raise a ticket with the SAG support. Maybe they have a solution to your problem.
I also assume that they require a bit more context, like: did you change anything prior to restarting the runnable, etc.

Best,

Veronika

by Eka Widhi Author

Posted on Tue, 08/31/2021 - 09:08

Hi Veronica,

Thank you for the help. As detailed info, I didn't make any changes before restarting the runnable. This condition occurs when all services are in the started position, then the Aris Agent 10.0 service is turned off directly through administrative tools in Windows.

Thanks.

Eka Widhi

by Alexander Cherednichenko

Posted on Wed, 09/01/2021 - 12:58

Hi,

this runnable loadbalancer_m usually starts as an old car, you need to push it several times. So your issue is not a news )

I suppose, it depends on your server resources, so if your server has e.g. less than 32 Gb of memory, you'd probably face this.

How I fight it ) On your server start your Cloud controller, then perform the command >start loadbalancer_m

As you see on my screenshot, sometimes you need to repeat the command several times before it starts. Sometimes, I use prays before the second starts. Sacrifices are also helpful )

File attachments

Screenshot1.jpg

by Eka Widhi Author

Posted on Thu, 09/02/2021 - 10:17

Hi Alexander,

Thank you for the advice. I've tried the suggestions you gave, but the result is still the same.

Maybe there is another solution that can be given. Thank you.

File attachments

ARIS.jpg

by Alexander Cherednichenko

Posted on Thu, 09/02/2021 - 15:24

You also could try the sequence of commands, sometimes it helps:

> stopall

> killall

> startall

by Eka Widhi Author

Posted on Fri, 09/03/2021 - 03:10

Ok, I'll try it.

by Runé Becker

Posted on Mon, 09/06/2021 - 16:07

Did you already check whether that there is no other web server started up, such IIS, on the same computer on which ARIS is running?

Most common reason for not starting load balancer is that it's port 80 or any other configured port is blocked by a service or program. An instability isn't known to me. Either it's starting or not. There's no "old card behavior" known.

Cheers
Rune

by Alexander Cherednichenko

Posted on Tue, 09/07/2021 - 15:13

For octopus_m is a very frequent case when it starts not from the first time, you can see the screen I've attached above, just recent case with SR10.0.14 So it really starts from the third time ))

Btw IIS really could cause this as well.

by Dipesh Dedhia

Posted on Tue, 07/26/2022 - 14:26

Hi,

As said well by Mr. Rune Becker, You need to check port 80 on windows server, sometimes system holds 80 port, you need to kill that PID and release port.

Once port 80 is released on server, loadbalancer runnable will start for sure.

Experienced same issue and resolved as stated above.

Regards,

Dipesh Dedhia

ARIS ROCKS