Hi Milosz,

Thanks for your reply.

Today morning I have re-setup even though I delete/lost the corresponding test run log with the below steps.

1. I have reinstalled LAVA server (#sudo apt-get purge --auto-remove lava-server and #sudo apt-get install lava-server)

2. reinstalled dispatcher at worker side (#sudo apt-get purge --auto-remove lava-dispatcher and #sudo apt-get install lava-dispatcher)

3. Remove the device and corresponding execution logs.

4. Remove worker

5. Add worker and device again.

I will try to start my debug from the "lava_scheduler_app" log as you said to identify the issue when I face the issue next time.

Is this the lava_scheduler_app log you are referring to i.e "/var/log/lava-server/lava-scheduler.log" ?

Regards,

Koti

On Mon, 21 Feb 2022 at 15:31, Milosz Wasilewski <milosz.wasilewski@foundries.io> wrote:

On Mon, Feb 21, 2022 at 2:55 AM koti <kotisoftwaretest@gmail.com> wrote:
>
> Hi,
>
> My LAVA job status still shows "Running" even when the job is completed and status does not change even after 24 hours.

Status is displayed from 'server side' of LAVA.

>
> Due to that my other Job's pending from that dispatcher targets.
>
> My dispatcher shows these errors for /var/log/lava-dispatcher/lava-worker.log i.e "https://pastebin.com/46WFtAin"

Looks like your 'server side' failed for some reason. Hard to tell
without logs. Check what lava_scheduler_app is doing and this should
help identify the issue.

Best Regards,
Milosz

>
> Please can someone let me know a solution to fix this issue?
>
> Regards,
> Koti
> _______________________________________________
> Lava-users mailing list -- lava-users@lists.lavasoftware.org
> To unsubscribe send an email to lava-users-leave@lists.lavasoftware.org
> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s