@olivierlambert I see, seems like the GPG key for NodeJS apt repo was out, I will get this sorted and then post back this evening / tomo as to if it corrected any issues.

@olivierlambert I see, seems like the GPG key for NodeJS apt repo was out, I will get this sorted and then post back this evening / tomo as to if it corrected any issues.

@olivierlambert

This is is a development/prod environment so I will have to just pull the latest later today.

I do not feel as that will be the issue as we have a several backups that take place and the one on the 25th ran without issue and saved off 500GB.

node -v v16.20.2

Good morning,

I am hoping some of you guru's here can help me figure this out we had a backup that has been running for over a year without issues just start spitting out this error:

spawn /usr/bin/node EAGAIN

Sep 27 13:42:12 orchestra xo-server[4109]: 2023-09-27T13:42:12.134Z xo:api WARN {redacted} | backupNg.runJob(...) [125ms] =!> Error: spawn /usr/bin/node EAGAIN

I have check syslog and gotten the previous string mentioned and is seems there is no verbosity with Orchestra.

If anyone would be willing to help me start the diagnosis on the issue here I would be most thankful as I don't even know where to begin as it seems like NODE.JS is broken but why would it just break?

Running the following build from source:
Xen Orchestra, commit c714b
xo-server 5.122.0
xo-web 5.124.1