Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ValueError __main__ #392

Closed
jacksonw765 opened this issue Apr 18, 2023 · 3 comments · Fixed by #394
Closed

ValueError __main__ #392

jacksonw765 opened this issue Apr 18, 2023 · 3 comments · Fixed by #394
Labels
bug Something isn't working

Comments

@jacksonw765
Copy link

Got this working twice but cannot get it to run using CUDA. Running into this error when calling train.

       INFO     [17:56:38] Loaded checkpoint 'logs\44k\G_0.pth' (iteration 0)                           utils.py:257
       INFO     [17:56:38] Loaded checkpoint 'logs\44k\D_0.pth' (iteration 0)                           utils.py:257

INFO: Initializing distributed: GLOBAL_RANK: 0, MEMBER: 1/2
INFO [17:56:38] Initializing distributed: GLOBAL_RANK: 0, MEMBER: 1/2 distributed.py:244
[W ..\torch\csrc\distributed\c10d\socket.cpp:601] [c10d] The client socket has failed to connect to [kubernetes.docker.internal]:49979 (system error: 10049 - The requested address is not valid in its context.).
so-vits-svc-fork\venv\Scripts\python.exe: Error while finding module specification for 'main' (ValueError: main.spec is None)

@jacksonw765 jacksonw765 added the bug Something isn't working label Apr 18, 2023
@SouljaVR
Copy link

Was getting the same issue, happens for me if I have CUDA enabled on more than one GPU on the python process sovits is using. I made sure it was only using 1 GPU for CUDA in the Nvidia settings and it's fine now. I can't get multi GPU working though.

@jacksonw765
Copy link
Author

Great catch, that worked!

@34j 34j reopened this Apr 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants