ok, thank you,
and what does this error mean
2024-01-30T07:25:07+03:00 [3:n8n2:conmon] conmon ef2bae8fe46ec74494b4 <nwarn>: Failed to open cgroups file: /sys/fs/cgroup/user.slice/user-1006.slice/user@1006.service/user.slice/user-libpod_pod_b91fad370f57b6e1522f7d1530a36e158f52ff63137b226b635d2b1d7bd4daa7.slice/libpod-ef2bae8fe46ec74494b449bc0507163c69564872400bb64e724272fda882b88f.scope/container/memory.events
Relevant to a pod but when you start and configure the services the first time it is easier to find the first error
ok,
what about these erros
2024-01-30T10:51:28+03:00 [3:n8n3:n8n-redis] 1:M 30 Jan 2024 07:51:28.255 * Ready to accept connections tcp
2024-01-30T10:51:28+03:00 [3:n8n3:runagent] Traceback (most recent call last):
2024-01-30T10:51:28+03:00 [3:n8n3:runagent] File "<frozen os>", line 574, in execvp
2024-01-30T10:51:28+03:00 [3:n8n3:runagent] File "<frozen os>", line 607, in _execvpe
2024-01-30T10:51:28+03:00 [3:n8n3:systemd] n8n-server.service: Control process exited, code=exited, status=1/FAILURE
file frozen os in execvp and in _execvpe
Just to be clear, for I am also waisting time, are you now working with a posix dev environment and NOT on a Winblows environment?
Hello Laylow, I actually deployed vscode on a Linux dev box. And that’s what am using to dev.
After Countless and Numerous Errors, and many lessons learnt as well.
I am happy to report that the N8N module is now ready for use…
Feature Announcement Here: NS8-n8n: Nodemation module - Feature - NethServer Community
