When I try to run the login command with my credentials, I get the error message “Not logged in”. I take it that’s to mean an authentication failure. The email and password are exactly as I enter them when signing into the topaz website.
$ /opt/TopazVideoAIALPHA/bin/login '<topaz-email>' '<password>'; echo "rc=$?"
ERROR|Not logged in
rc=1
When I copy the auth.tpz file from windows (%PROGRAMDATA%\Topaz Labs LLC\Topaz Video AI\models) to the ${TVAI_MODEL_DIR}, I get a silent output, with a different non-zero exit code
> scp auth.tpz machine:/opt/TopazVideoAIALPHA/models/
$ /opt/TopazVideoAIALPHA/bin/login '<topaz-email>' '<password>'; echo "rc=$?"
rc=12
Any idea what may be wrong, why the login fails using the login CLI binary on linux?
System details where the login command was run:
- Distribution: Ubuntu 22.04.1 LTS
- Kernel: Linux 5.15.0-70-generic #77-Ubuntu SMP Tue Mar 21 14:02:37 UTC 2023 x86_64
- nVidia driver: 525.105.17
- CUDA version: 12.0
- GPU: GA102 [GeForce RTX 3090]
- CPU: AMD Ryzen 9 5950X
- RAM: 128GB
PS. I have an email address with a + sign in the part before the @domain delimiter, if that matters (e.g. invalid parsing assumptions for the login CLI wrt email-extraction from argv).
EDIT: I’m getting the same ERROR|Not logged in on windows when I run the login.exe command without an auth.tpz file in the models directory. However, on windows I do get output when the auth.tpz file resides in the models directory, while on linux, nothing is printed at all.
> login.exe <email> <password>
INFO: Windows DisplayVersion: 22H2
INFO: WINDOWS VERSION IS 10.22
INFO: VNNI: 0 AVX: 1 CPUName: Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz Thread Count: 8
INFO: MEM TOTAL: 31.94 AVAIL: 14.9868
INFO: Machine Id: 00000000-0000-0000-0000-000000000000
INFO: Available GPU LIST
So the behavior of the linux version and windows version is definitely different, but both fail to log me in when the auth file is not present. If no-one else has this problem, then I strongly suspect it may be email addresses with + characters in them, as noted initially.
Anyone from Topaz that knows what may be up, or can take a look at the argument parsing and what happens to it all the way to the HTTP POST?
Clearly the website backend is able to handle this credential perfectly, so the problem seems to be with the login client program.
