Weaviate Startup Issue - WCS gRPC Connection error

Hi Team,

We’re using WCS 1.25.9 and experiencing issues with Weaviate in our [production/staging/development] environment. The problem started at 6/30/2024

Error message:

error WeaviateStartUpError: Weaviate startup failed with message: Weaviate failed to startup with message: Weaviate makes use of a high-speed gRPC API as well as a REST API.
      Unfortunately, the gRPC health check against Weaviate could not be completed.
      This error could be due to one of several reasons:
        - The gRPC traffic at the specified port is blocked by a firewall.
        - gRPC is not enabled or incorrectly configured on the server or the client.
            - Please check that the server address and port: [grpc-address-here].gcp.weaviate.cloud:443 are correct.
        - your connection is unstable or has a high latency. In this case you can:
            - increase init-timeout in weaviate.connectToLocal({timeout: {init: X}})'
            - disable startup checks by connecting using 'skipInitChecks=true'

Here is our code

export class WeaviateService {
  private readonly logger = new Logger(WeaviateService.name);
  private weaviateClient: WeaviateClient;
  private readonly env: string;

  constructor(private configService: ConfigService) {
    this.env = configService.get('NODE_ENV');
  }

  async onModuleInit() {
    const weaviateInstanceURL = process.env.WEAVIATE_INSTANCE_URL;
    const weaviateApiKey = process.env.WEAVIATE_API_KEY;
    const openAIApiKey = process.env.OPENAI_API_KEY;
    try {
      this.weaviateClient = await weaviate.connectToWeaviateCloud(
        weaviateInstanceURL,
        {
          authCredentials: new weaviate.ApiKey(weaviateApiKey),
          headers: {
            'X-OpenAI-Api-Key': openAIApiKey,
          },
        },
      );
    } catch (error) {
      console.log('error', error);
    }
  }
// more code...
}

Important details:

  1. No changes have been made to our application code since yesterday.
  2. The issue appeared suddenly without any apparent trigger.

Troubleshooting steps:

  1. Verified gRPC endpoints and REST endpoints are the endpoints defined in our console dashboard. They are consistent.
  2. Used ping and telnet to confirm that the address is valid

We would appreciate any guidance on resolving this gRPC connection issue. Thank you in advance for your help.

1 Like

Hi!

Can you send an email to support@weaviate.io?

That will open a support ticket. Please make sure to state the endpoints or cluster name you are facing this issue.

Thanks!

1 Like

Got it. Will do @DudaNogueira

2 Likes