Having updated to version 3.7.1 (from 3.1.0), my single Selenium node no longer starts the configuration. The Node is online according to Jenkins, and manually attempting to start the Selenium node simply refreshes the node management page.

Looking at the node itself, when this happens the new selenium-server-standalone-3.7.1.jar file is created, but is empty. Replacing this with the version from the repo has no effect, as it gets overwritten by the empty file again. The file on the Jenkins master is correct, at least in size.

Anyone any other ideas of what to try?