Hello Stefan,

There was no file in the location.So, I created qemu.jinja2 and updated the ownership.

root@debian:/etc/apache2/sites-available# cat /etc/lava-server/dispatcher-config/device-types/qemu.jinja2
{% extends 'qemu.jinja2' %}
root@debian:/etc/apache2/sites-available#

Thanks,
Sweta
From: Stefan <lists.lavasoftware.org_23@green-sparklet.de>
Sent: Tuesday, July 2, 2024 7:22 PM
To: lava-users@lists.lavasoftware.org <lava-users@lists.lavasoftware.org>
Subject: [lava-users] Re: RecursionError: maximum recursion depth exceeded on lava-scheduler service
 
[Email from a non-Nagarro source: please exercise caution with links and attachments]

Hi sweta.ghosh,

have you maybe edited qemu.jinja2 directly and put a "{% extends 'qemu.jinja2' %}" into it, instead of creating a new file (and using this) for your device? Can you please show us your device type template? Thank in advance Stefan
On 2024-07-02 15:34, sweta.ghosh@nagarro.com wrote:
Hi ,
I am trying to setup LAVA on Single Master Worker node.
When i am trying to submit job it is running but no device is getting selected nor I am getting any output on UI. When I checked the lava-scheduler it is failing with below error:
root@debian:/etc/apache2/sites-available# systemctl status lava-scheduler
× lava-scheduler.service - LAVA scheduler
     Loaded: loaded (/lib/systemd/system/lava-scheduler.service; enabled; preset: enabled)
     Active: failed (Result: start-limit-hit) since Tue 2024-07-02 18:52:36 IST; 7min ago
   Duration: 1.472s
    Process: 10345 ExecStart=/usr/bin/lava-server manage lava-scheduler --level $LOGLEVEL --log-file $LOGFILE $EVENT_URL $IPV6 (code=exited, status=0/SUCCES>
   Main PID: 10345 (code=exited, status=0/SUCCESS)
        CPU: 1.431s

Jul 02 18:52:35 debian systemd[1]: lava-scheduler.service: Deactivated successfully.
Jul 02 18:52:35 debian systemd[1]: lava-scheduler.service: Consumed 1.431s CPU time.
Jul 02 18:52:36 debian systemd[1]: lava-scheduler.service: Scheduled restart job, restart counter is at 5.
Jul 02 18:52:36 debian systemd[1]: Stopped lava-scheduler.service - LAVA scheduler.
Jul 02 18:52:36 debian systemd[1]: lava-scheduler.service: Consumed 1.431s CPU time.
Jul 02 18:52:36 debian systemd[1]: lava-scheduler.service: Start request repeated too quickly.
Jul 02 18:52:36 debian systemd[1]: lava-scheduler.service: Failed with result 'start-limit-hit'.
Jul 02 18:52:36 debian systemd[1]: Failed to start lava-scheduler.service - LAVA scheduler.
root@debian:/etc/apache2/sites-available# tail -f /var/log/lava-server/lava-scheduler.log
    {% extends 'qemu.jinja2' %}
    ^^^^^^^^^^^^^^^^^^^^^^^^^
  [Previous line repeated 977 more times]
  File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 1494, in is_up_to_date
    return self._uptodate()
           ^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/jinja2/loaders.py", line 212, in uptodate
    return os.path.getmtime(filename) == mtime
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
RecursionError: maximum recursion depth exceeded


Also when I am accessing /admin/lava_scheduler_app/device/ I am getting " 500 Internal Server Error
maximum recursion depth exceeded"

I have registered my worker node as debian,hostname as debian and device type is qemu. Could you please what I am missing.
_______________________________________________
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