Backup failing due to failing to read the license ID


#1

My backups which have been running fine out of cron for several months now have suddenly started failing, indicating it was failing to read the license ID. I logged into the server and hand-ran the backup and got the following output:

[root@landroval:/var/spool/cron/crontabs] /vmfs/volumes/5d0cc0a3-b22da97c-5c0d-   b083fed617c2/verticalbackup/vertical backup \* --email
2019-08-26 16:58:24.905564 INFO PROGRAM_VERSION Vertical Backup 1.3.2
Failed to login: HTTP error response: Service Unavailable
2019-08-26 17:00:11.878195 ERROR LICENSE_FAILURE Failed to read the license ID
2019-08-26 17:00:15.020410 INFO EMAIL_SEND A notification email has been sent to jim@XXX.com

I assumed it was an issue with the license, so did a verification:

[root@landroval:/var/spool/cron/crontabs] /vmfs/volumes/5d0cc0a3-b22da97c-5c0d-b083fed617c2/verticalbackup/vertical license show
Vertical Backup 1.3.2
Failed to login: HTTP error response: Service Unavailable
Failed to read the license ID

So this looks like an availability or reachability issue towards the license server.

Are there any known issues? If not, is it possible to get details (address) for the server so I can look into potential reachability issues? (Yes, I could tcpdump the network connection or get a system trace of the vertical process to get the address, but I’m being lazy and asking :wink: )

Thanks!

  • Jim

#2

This looks like something wrong with vim-cmd. Can you run this command manually, such as vim-cmd vmsvc/getallvms?