How to solve the issue.node block appears to be neither running nor scheduled
I think that you’ll need to provide much more context so that others can understand how to see the issue that you are seeing. I don’t recall ever seeing a message that indicating that a Pipeline step was neither running nor scheduled.
The message is from workflow-durable-task-step and indicates some sort of corruption of Pipeline metadata: a node step was started, but does not appear to be running its block on any executor, nor does there appear to be an outstanding queue item associated with it.
Assuming you are running a current version (at least 1398.vf6c9e89e5988), this could be solved by Jenkins developers only if you know how to reproduce the problem from scratch in a clean environment.
The same jenkin job is running fine in existing ec2 instance node server, but while I just changed the node server i.e one more ec2 instance, I am getting this error
The old lockfile The package -,lock.json file was created with an old version of npm,
Old lockfile suplimental metadata must be fetched from the registry
This is one time fix pls be patient
After that getting this message as
Error: node block appears to be neither running nor scheduled , will cancel if the condition persists.
Still I am getting the same error message, after deleting the package -lock.json file
Please suggest how to fix this issue
From the mentioning of package-lock, are you confusing a jenkins node block with running node.js in your step?