Uploaded image for project: ' AGL Development'
  1. AGL Development
  2. SPEC-3998

[WAM] Sometimes WAM starts very slow/Failed to acquire lock causes systemd to wait a bit and attempt a later start

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Inactive
    • Icon: Minor Minor
    • None
    • None
    • HTML5/WAM

      Journactl says:

      Jun 29 03:06:51 raspberrypi4-64 systemd[1]: Started "WebAppMgr is responsible for running web apps and manage their lifecycle".
Jun 29 03:06:54 raspberrypi4-64 WebAppMgr[537]: ## (DEBUG)[int main(int, const char**)] ### Starting /usr/bin/WebAppMgr
Jun 29 03:06:54 raspberrypi4-64 WebAppMgr[537]: ## (DEBUG)[virtual int WebRuntimeAGL::run(int, const char**)] WebRuntimeAGL::run
Jun 29 03:06:54 raspberrypi4-64 WebAppMgr[537]: ## (DEBUG)[virtual int WebRuntimeAGL::run(int, const char**)] WebRuntimeAGL - creating SharedBrowserProcessRuntime
Jun 29 03:06:54 raspberrypi4-64 WebAppMgr[537]: ## (DEBUG)[bool WamSocketLockFile::createAndLock()] Failed to lock file 3
Jun 29 03:06:54 raspberrypi4-64 WebAppMgr[537]: ## (DEBUG)[virtual int SharedBrowserProcessRuntime::run(int, const char**)] Trying to start shared browser process but process is already run>
Jun 29 03:06:54 raspberrypi4-64 systemd[1]: WebAppMgr@1001.service: Main process exited, code=exited, status=255/EXCEPTION
Jun 29 03:06:54 raspberrypi4-64 systemd[1]: WebAppMgr@1001.service: Failed with result 'exit-code'.

      Problem is I don't have a easy way of replicating, I just boot and it is.

      The locking uses flock(), suggest using agl-netboot for booting, maybe that triggers it?

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            rogerzanoni Roger Zanoni
            mvlad Marius Vlad
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: