Hi Ketan, Thank you for your reply.
I tried what you suggested (including removing the new line from the end of the file) but we are still getting the same error. Any other suggestions? If it's relevant, running a script directly against a copy of the database is a viable option. Cheers, Jason On Thursday, 18 April 2019 12:02:41 UTC-4, Ketan Padegaonkar wrote: > > Try: > > cat guid.txt | openssl dgst -sha256 -hmac > "TOKEN_GENERATION_KEY_FROM_CONFIG_XML" -binary | base64 > token > > You may need to remove the newline from the generated `token` file. > > - Ketan > > > > On Thu, Apr 18, 2019 at 8:48 PM Jason Smyth <jsm...@scimarketview.com > <javascript:>> wrote: > >> Hello, >> >> For some unknown reason one of our agents re-registered with a new GUID. >> We would like to revert it to its original GUID so that its history is >> maintained but we do not have a backup copy of the token. >> >> We restored the original GUID but now see token errors in the log when we >> try to bring the agent online: >> >> A token has already been issued for this agent. >> >> Is there a way we can recover the original token from the server or do we >> need to just accept the loss of agent history? >> >> Thanks in advance, >> Jason >> >> -- >> You received this message because you are subscribed to the Google Groups >> "go-cd" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to go...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to go-cd+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
