parler-tts error

[hlzhangxt]

3:21AM INF Success ip=184.74.240.175 latency="23.847µs" method=GET status=200 url=/browse/job/progress/18e68788-037c-11ef-a85f-0242ac110003
3:21AM INF Success ip=184.74.240.175 latency="20.367µs" method=GET status=200 url=/browse/job/18e68788-037c-11ef-a85f-0242ac110003
3:22AM INF Success ip=127.0.0.1 latency="22.929µs" method=GET status=200 url=/readyz
3:23AM INF Success ip=127.0.0.1 latency="24.456µs" method=GET status=200 url=/readyz
3:23AM INF Loading model with backend parler-tts
3:24AM INF Success ip=127.0.0.1 latency="25.843µs" method=GET status=200 url=/readyz
3:24AM ERR failed starting/connecting to the gRPC service error="rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 127.0.0.1:39719: connect: connection refused""
3:24AM ERR Server error error="grpc service not ready" ip=184.74.240.173 latency=40.015812725s method=POST status=500 url=/v1/audio/speech
LocalAI version:

Environment, CPU architecture, OS, and Version:

Describe the bug

To Reproduce

Expected behavior

Logs

Additional context

[localai-bot]

Hello, thank you for reporting this issue in LocalAI. It seems like you've encountered a problem while using the parler-tts backend. To better assist you and resolve the issue as soon as possible, please provide the following information in your description:

1. LocalAI version: Please specify the Container Image or LocalAI tag/commit that you are using.
2. Environment, CPU architecture, OS, and Version: Please provide the output from "uname -a", Hardware specifications, and if you are using a VM, the virtualization information.
3. Describe the bug: Provide a clear and concise description of what the issue is.
4. To Reproduce: Please provide detailed steps to reproduce the behavior, including the LocalAI command used, if applicable.
5. Expected behavior: A clear and concise description of what you expected to happen.
6. Logs: If applicable, add logs while running LocalAI in debug mode (--debug or DEBUG=true) to help explain the problem.
7. Additional context: Please add any other context about the problem that might be helpful in resolving the issue.

Once you've provided this information, we will review your report and work on fixing the issue as soon as possible.

Note: This is an automated message from a bot, an experiment of @mudler.

---

evespinar (evespinar): Thanks for the prompt reply. I opened this ticket and hours after the update today (Nov 02). Here is the info requested:

1. LocalAI version: localai/localai:1.5.0-rc2-local ⬆️ Update docs version mudler/LocalAI #1517
2. Environment, CPU architecture, OS, and Version: Linux localai-laptop 5.4.0-96-generic feature: auto-build images #102-Ubuntu SMP Mon Oct 11 17:10:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
3. Describe the bug: It seems like the new update includes a parler-tts backend that is failing to start/connect to the grpc service.
4. To Reproduce: I didn't explicitly use a command to reproduce this issue, it appears to be a system-related issue after the update.
5. Expected behavior: The parler-tts backend should start and connect to the grpc service without errors.
6. Logs: Not applicable in this case.
7. Additional context: This bug seems to be related to the recent update to the parler-tts backend.

I hope this helps in reproducing the issue. Thanks for all the work on LocalAI.

Note: This is an automated message from a bot, an experiment of @mudler.