12.1.1 Unable To Rescan Certain Linux Machines - Cannot find a compatible console test instruction.

[JGM2023]

Hello,

We are receiving the following error when trying to rescan certain Linux machines: Cannot find a compatible console test instruction. All known instructions are not available or executed with errors.

For some of the machines the backup still works successfully even with this error showing, But others it fails In the Backup Job with Error: Failed to connect to the host. The transport service is not responding or an SSH connection was not established. We have verified the service Is running and SSH Is contactable.

Thanks

Case ID: 07106111
VBR Version: 12.1.1.56
Agent Version: 6.1.0.1498

[rovshan.pashayev]

Hello Jacob,

Please maintain ongoing collaboration with our support team to ensure continued assistance for your specific situation.

Rovshan.

[ChristianJensen]

Hello,
we have a very similar error when trying to backup our HANA Servers. We use an active directory user which connects over SSH to the servers. Since 1 of march 00:00 h no more connections where able. But only the HANA Servers are effected. Other system backup with the same user are still working. On the HANA Serversite no changes where made at this time and as the user is not a local one no user credentials are defined. The exact error message is as follows:

Validating SSH credentials error: Cannot find a compatible console test instruction

Did you find a solution for your problem?

Best regards
Christian

[Mildur]

Hello Christian

The case mentioned by JGM doesn't have a solution yet.
It would be helpful to us if you can provide your own case number. The cause may be the same or a completely different one.
Therefore it is important that our support team has the chance to investigate your log files as well.

Thank you
Fabian

[ChristianJensen]

Hello to all,
we solved the problem. Our User Administration removed the priviledge of "remote login" form the veeam user. Therefore ssh login didn't function any more. It is still unclear, why other ssh logins were still working. We added the priviledge again and all is fine.
Best regards
Christian