Error: Command "start" not found

Questions
,
1

Hi guys,

I am running the latest N8N docker compose on portainer OMV NAS, and I got this error. I asked ChatGPT and it said that the new version does not have the command start. Any advice?

Edit, I am running Queue mode and I have 2 workers on it.

error | Error: Command “start” not found {“file”:“command-registry.js”,“function”:“execute”}

2

Where did you get this error? What did you do to get this error? How often does this error happen? Which version of n8n are you running? What are you trying to do? Can you share the workflow?

3

Hi @jabbson, thank you for your response.

I got this error in the docker logs. I just pulled the latest docker image, and went through the normal update process, then suddenly N8N is not working. I then went to check the docker logs, and that’s error. I could not access to the N8N interface, so I did not know what the version is

4

When you say “the latest” do you mean the tag :latest or the tag :next?

5

it’s the :latest tag in the docker compose file

6

If you haven’t deleted the old image, does changing back to the old one fixes the problem? At least for you to export the workflows and credentials?

7

Hi @jabbson, I have tried your suggestion, still have the same error. Even with the one before the previous one.

8

Hi guys,

I got a solution for the issue. It turns out that I did not give the right permission for subfolder. I should have given them the recursive -R when I do chmod command, lol.

4 Likes
9

I thought you only updated the image? How did your subfolder have different set of permissions after you pulled a new image?

10

HI @jabbson, I am not sure what happened, but I did mess around permission for other apps, not N8N specifically because it is running some important workflows.

I am using OMV NAS, so my guess is that I accidentally messed up the permission for N8N, but it had not got affected yet, and when I updated the image to the latest version (need set the container down), the new permission took effective. I need to document this issue for future use.

11

what are the desired permissions? I am getting the same issue and I have the folder permissions the same as my other container.

12

I ended up just adding --user root to the docker run command I was using.

13

I give user:group-user permission to the N8N folders. Any user that has root privilege works, and the group is the user group on my NAS. OMV behaves a little bit strange to me. Even though I assign a user to the container, it appears that the delegation does not work accordingly.

14

I have tried a few different permission models and can’t see to get this to stand up. It’s definitely not a standard container.

15

Did you also do -R recursive the whole N8N folder when you set permission?

16

yes, I did

17

This is the correct solution

18

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