MeshCentral: Windows Server 2016 Crash

Describe the bug When logging off a Windows Server 2016 machine with the Mesh Agent installed, the server crashes and reboots.

I had this happen on multiple machines for several customers now. The common denominator appears to be all running Windows Server 2016.

To Reproduce Steps to reproduce the behavior: Log off Windows Server 2016 machine and click disconnect button and within a few seconds, server (agent) crashes and reboots.

Expected behavior The remote machine shouldn’t crash.

Screenshots If applicable, add screenshots to help explain your problem.

Server Software (please complete the following information):

  • OS: Ubuntu
  • Virtualization: No
  • Network: WAN
  • Version: 1.0.97
  • Node: v10.19.0

Client Device (please complete the following information):

  • Device: Any machine
  • OS: MacOs and Windows
  • Network: Remote over WAN
  • Browser: Safari / Chrome
  • MeshCentralRouter Version: N/A

Remote Device (please complete the following information):

  • Device: Server
  • OS: Windows Server 2016
  • Network: Remote over WAN
  • Current Core Version (if known):
  • Current Core: Aug 25 2022, 143332014 Agent Time: 2022-11-14 15:58:34.664-05:00. User Rights: 0xffffffff. Platform: win32. Capabilities: 15. OS: Microsoft Windows Server 2016 Standard - 14393. Modules: amt-apfclient, amt-lme, amt-manage, amt-mei, monitor-border, smbios, sysinfo, util-agentlog, wifi-scanner-windows, wifi-scanner, win-console, win-deskutils, win-info, win-securitycenter, win-terminal, win-virtual-terminal, win-volumes. Server Connection: true, State: 1.

Additional context Add any other context about the problem here.

Your config.json file

{
  "$schema": "http://info.meshcentral.com/downloads/meshcentral-config-schema.json",
  "__comment1__": "This is a simple configuration file, all values and sections that start with underscore (_) are ignored. Edit a section and remove the _ in front of the name. Refer to the user's guide for details.",
  "__comment2__": "See node_modules/meshcentral/sample-config-advanced.json for a more advanced example.",
  "settings": {
    "_cert": "myserver.mydomain.com",
    "_WANonly": true,
    "_LANonly": true,
    "_sessionKey": "MyReallySecretPassword1",
    "_port": 443,
    "_aliasPort": 443,
    "_redirPort": 80,
    "_redirAliasPort": 80
  },
  "domains": {
    "": {
      "_title": "MyServer",
      "_title2": "Servername",
      "_minify": true,
      "_newAccounts": true,
      "_userNameIsEmail": true
    }
  },
  "_letsencrypt": {
    "__comment__": "Requires NodeJS 8.x or better, Go to https://letsdebug.net/ first before trying Let's Encrypt.",
    "email": "myemail@mydomain.com",
    "names": "myserver.mydomain.com",
    "production": false
  }
}

About this issue

  • Original URL
  • State: open
  • Created 2 years ago
  • Comments: 20 (3 by maintainers)

Most upvoted comments

There’s a memory leak on 2016 I believe, monitor memory and see if it’s crashing because of resource exhaustion.

The wording is a little confusing. Are you saying the agent is crashing or the server is crashing?

Not the MeshCentral Server, it’s the Windows Server 2016 machine running the agent that crashes, crashes and reboots.