./webodm.sh start run error

Hi guys.
Has anyone else experienced this error?

webapp | Checking for celery… OK
webapp | Scheduler is not running.
webapp | /webodm/start.sh: line 117: syntax error near unexpected token }' webapp | /webodm/start.sh: line 117: }’
webapp exited with code 2

2 Likes

Welcome!

Sorry for the trouble.

No, this seems new.

Have you modified anything in your install?

No. I just run ./webodm.sh update

1 Like

Hmm…

Could you please start with giving me a bit more information about your system?

Operating System and Version
eg: Windows 11, MacOS 12.4, Ubuntu Linux 22.04LTS, etc…
Hardware Specifications
eg: 32GB RAM, i7-6700k, NVIDIA GTX 1050TI OC, 1TB SSD, etc…
WebODM Install Method
eg: Native installer, Docker, Snap, GitHub download, compiled from source
WebODM/ODM Version
eg: WebODM v1.9.14 Build 64, ODM v2.8.7, etc…
Procesing Node
eg: Automatic, Lightning, local (node-odm-1), etc…
Screenshots demonstrating the issue/behavior/error messages

Operating System and Version
Windows 10

Hardware Specifications
32GB RAM, Intel(R) Xeon(R) CPU E5-2666 v3 @ 2.90GHz, AMD Radeon RX 6400, 1TB SSD

WebODM Install Method
Docker

WebODM/ODM Version
I don’t know how to confirm this information without being able to run the application

Procesing Node
Local (node-odm-1)

1 Like

I am just running into the same trouble … at the moment I do not manage to start WebODM.
Happened right after updating …

Syntax of start.sh seems to be broken …

And then it loops exactly like in the screenshot above.

Running latest WebODM scripts from Github on Linux Mint 21.1 with Docker CE.

1 Like
2 Likes

We made a whoopsie :rofl:

1 Like

Even with the change, the error persists
Has been changed both manually and with ./webodm.sh update run

2 Likes

Hmm, again: same here.

I first thought it might take a moment to sync the commit, but at the moment the error is still the same.

1 Like

Okay, it works again :sweat_smile:
I only pulled the WebODM scripts from Github, but running a ./webodm.sh update fixed the issue.

Thx for the quick response @pierotofy

3 Likes

Working here too.
Thks guys.

3 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.