back-version gslist -v results in error messages in log files
When running an older version of gslist with the -v argument, gslist attempts to connect to server processes to verify they are responsive. gslist -v (without a specific process name) will attempt to connect to all GemStone processes running on that host machine, regardless of the version.
When using a much older version of gslist, the -v connection attempt fails against the latest server version processes. This results in errors in the log file of the form:
NetAcceptReadClientIdent failed, peer localhost, reason numread 0 < length 114, timeout
There is no problem for the server, other than some clutter in the log file.
Workaround
You can ignore the error messages. Otherwise, avoid using old version gslist with the -v argument on a host machine that is also running a system on the most recent GemStone versions. You can verify a specific process, rather than all processes on the host machine, using gslist -v stonename.
Last updated: 10/15/21