Error: “No suitable servers found: `serverSelectionTimeoutMS` expired: [connection refused calling ismaster on 'localhost:27018']: generic server error" code: <mongodb:13053> when running backup script”

Environment Details

When server is intermittently shutting down ungracefully and customer is using documented automated backup script, the following error is exhibited in the Service logs around the time the backup is scheduled:

"No suitable servers found: `serverSelectionTimeoutMS` expired: [connection refused calling ismaster on 'localhost:27018']: generic server error" code: <mongodb:13053>

(Note that the reference to 'localhost:27018' might be different depending on the specific server configuration.)

• Product - Alteryx Server
  • all versions
• Backup script applied in customer environment

• Confirm this is not an issue with the mongod.lock file outlined in the article here as this is a separate issue.
• Confirm the customer is utilizing the three-line batch script we have documented
• Confirm below log lines. There may be unimportant log lines in between them but look for the errors shortly after the  "Stopping plugin <Logging>" line as this is the last service to be shut down.

• Here is a graceful shutdown and startup for comparison.

1. Have the customer add timeouts between the command; the updated script should look like this (with the appropriate path to the backup directory):

D:\Alteryx\bin\AlteryxService.exe stop
timeout /t 60 /nobreak
D:\Alteryx\bin\AlteryxService.exe emongodump=D:\ProgramData\Alteryx\Service\Persistence\MongoDB_backup
timeout /t 60 /nobreak
D:\Alteryx\bin\AlteryxService.exe start

The timeout command is in seconds, this may need to be adjusted up for safe measure depending on the size of the database.

• Alteryx Service will not start: No suitable servers Error found in LastStartupError.txt
• Alteryx Server Backup and Recovery Part 2: Procedures