MeshCentral: MeshCentral Service can no longer be started!!
Describe the bug After the automatic restart of the Windows Server, the MeshCentral service can no longer be started! We have not changed anything in MeshCentral. Please help.
“C:\Program Files\Open Source\MeshCentral\meshcentral-data\mesherrors.txt”
-------- 9/1/2024, 10:25:03 PM ---- 1.1.24 --------
node:fs:1688
handleErrorFromBinding(ctx);
^
Error: ENOENT: no such file or directory, stat 'C:\Program Files\Open Source\MeshCentral\node_modules\meshcentral\agents\MeshCentralAssistant.exe'
at Object.statSync (node:fs:1688:3)
at module.exports.hashExecutableFile (C:\Program Files\Open Source\MeshCentral\node_modules\meshcentral\exeHandler.js:264:79)
at CreateMeshCentralServer.obj.updateMeshTools (C:\Program Files\Open Source\MeshCentral\node_modules\meshcentral\meshcentral.js:2917:32)
at CreateMeshCentralServer.obj.StartEx4 (C:\Program Files\Open Source\MeshCentral\node_modules\meshcentral\meshcentral.js:1700:13)
at CreateMeshCentralServer.obj.StartEx3 (C:\Program Files\Open Source\MeshCentral\node_modules\meshcentral\meshcentral.js:1676:17)
at C:\Program Files\Open Source\MeshCentral\node_modules\meshcentral\meshcentral.js:1588:21
at obj.GetMeshServerCertificate (C:\Program Files\Open Source\MeshCentral\node_modules\meshcentral\certoperations.js:1091:38)
at CreateMeshCentralServer.obj.StartEx2 (C:\Program Files\Open Source\MeshCentral\node_modules\meshcentral\meshcentral.js:1585:35)
at C:\Program Files\Open Source\MeshCentral\node_modules\meshcentral\meshcentral.js:1577:21
at C:\Program Files\Open Source\MeshCentral\node_modules\meshcentral\db.js:2818:25 {
errno: -4058,
syscall: 'stat',
code: 'ENOENT',
path: 'C:\\Program Files\\Open Source\\MeshCentral\\node_modules\\meshcentral\\agents\\MeshCentralAssistant.exe'
}
Node.js v18.19.0
Server Software (please complete the following information):
- OS: Windows Server 2022
- Version: 1.1.24
- Node: 18.19.0
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 20 (12 by maintainers)
It might be it could finally update for a split second, so it took the chance! Which then, in turn, goofed things up! And the service was also broken so normally an uninstall_install of the service fixes the issue Happened to someone else only the other day