Indexing Error Messages

Sometimes you may receive an error message when indexing your product Data Feed. These errors do not affect the normal functioning of the search function on your site, they only affect the updating of the products. However, we have put together this guide with the most common errors and their solutions to help you fix them as soon as possible and ensure the correct functioning of the indexing process.

1. Connection Issues

1.1 Invalid authentication (401)

HTTP error code 401 indicates that the request has not been executed because it lacks valid authentication credentials for the requested resource.

1.2 Server is blocking the Request (>= 400 or <500 or econnrefused)

This error indicates that the request sent to the server has been blocked for various reasons, depending on the specific error code. The most common reasons include:

1. Client Errors (4xx): These HTTP status codes indicate that there was an issue with the request sent by the client. Common errors include:

   • 400 Bad Request: The request is malformed or contains incorrect syntax.
   • 401 Unauthorized: Authentication is required and has either failed or not been provided.
   • 403 Forbidden: The server understands the request but refuses to authorize it.
   • 404 Not Found: The requested resource could not be found on the server.

2. Connection Refused (econnrefused): This error occurs when the client attempts to establish a connection with the server, but the server actively refuses the connection. This can be due to:

   • The server is not listening on the requested port.
   • The server is blocking the connection for security or configuration reasons.
   • The server is unavailable or down.

It is important to review the specific error code details and the server configuration to identify and resolve the exact cause of the problem.

1.3 Server is not available (500 errors)

Server Errors (5xx): These HTTP status codes indicate that there was an issue on the server side. Common errors include:

• 500 Internal Server Error: The server encountered an unexpected condition that prevented it from fulfilling the request.
• 502 Bad Gateway: The server, acting as a gateway or proxy, received an invalid response from the upstream server.
• 503 Service Unavailable: The server is currently unable to handle the request due to temporary overload or maintenance.
• 504 Gateway Timeout: The server, acting as a gateway or proxy, did not receive a timely response from the upstream server.

1.4 Server responds too slow

This error indicates that the server is taking too long to respond to a client's request. This can lead to timeouts and performance issues for users. Common reasons for a slow server response include:

• High Server Load: The server may be overwhelmed with too many requests, leading to delayed responses.
• Inefficient Code or Queries: Poorly optimized code or database queries can cause the server to take longer to process requests.
• Network Issues: Latency or bandwidth limitations on the server's network can slow down response times. Resource Limitations: Insufficient CPU, memory, or disk resources on the server can hinder its ability to respond quickly.
• External Dependencies: Delays in responses from third-party services or APIs that the server relies on can slow down the overall response time.
• Configuration Issues: Improper server or application configuration can contribute to slow responses.

1.5 Server Timeout

This error indicates that the server did not respond to the client's request within the expected timeframe, resulting in a timeout. Common causes of server timeouts include:

• High Server Load: The server may be handling too many requests simultaneously, causing delays and timeouts.
• Inefficient Code or Queries: Poorly optimized code or database queries can cause the server to take too long to process requests.
• Network Issues: Latency, packet loss, or other network-related problems can lead to delays in communication between the client and server.
• Resource Limitations: Insufficient CPU, memory, or disk resources on the server can prevent it from processing requests in a timely manner.
• External Dependencies: Dependencies on third-party services or APIs that are slow to respond can result in overall request timeouts.
• Configuration Issues: Incorrect server or application configuration settings, such as low timeout thresholds, can cause premature timeouts.

1.6 Store Domain not found (nxdomain)

This error indicates that the domain name specified in the request cannot be resolved to an IP address by the DNS (Domain Name System). The term "nxdomain" stands for "Non-Existent Domain" and signifies that the domain name does not exist or cannot be found in the DNS. Common causes of this error include:

• Incorrect Domain Name: The domain name provided may be misspelled or incorrectly formatted.
• Domain Not Registered: The domain name may not be registered or may have expired.
• DNS Propagation: Recent changes to the DNS records for the domain may not have fully propagated across the DNS network.
• DNS Configuration Issues: Problems with the DNS configuration, such as missing or incorrect DNS records, can prevent the domain from being resolved.
• Network Issues: Issues with the network or DNS servers used by the client or server can result in the inability to resolve the domain name.

To resolve the "Store Domain Not Found (nxdomain)" error, verify that the domain name is correct, ensure that it is properly registered and configured, and check for any network or DNS server issues.

1.7 Downloaded content format is invalid

This error indicates that the content downloaded from a server or another source does not conform to the expected format. This can occur in various scenarios, such as downloading a file, receiving a response from an API, or fetching resources from a server. Common causes of this error include:

• Incorrect File Type: The content downloaded is not of the expected file type (e.g., expecting a JSON file but receiving an HTML file).
• Corrupted Content: The downloaded content may be incomplete or corrupted during the transfer process.
• Mismatched Encoding: The content may use an encoding format that is different from what was anticipated.
• Invalid Data Structure: The data structure within the content may not match the expected schema or format (e.g., malformed JSON or XML).
• Server Errors: The server may return an incorrect or unexpected response due to misconfiguration or errors in handling the request.

To resolve the "Downloaded Content Format is Invalid" error, ensure that the content being downloaded matches the expected format and structure. Verify the integrity of the content, check for proper encoding, and ensure that the server is correctly configured to serve the expected content.

1.8 Plugin Endpoint issue

This error indicates that there is a problem with the endpoint used by a plugin to communicate with a server or external service. This can occur in various scenarios, such as when a plugin tries to fetch data, send data, or perform an operation through an API endpoint. Common causes of this error include:

• Incorrect Endpoint URL: The URL specified for the endpoint is incorrect or misspelled.
• Endpoint Unavailability: The server or service hosting the endpoint is down or unavailable.
• Authentication Issues: The endpoint requires authentication, and the plugin is not providing the correct credentials or tokens.
• Configuration Errors: The plugin or the endpoint configuration may be incorrect, leading to failed requests. Network Issues: Network connectivity problems can prevent the plugin from reaching the endpoint.
• CORS Issues: Cross-Origin Resource Sharing (CORS) policies may block the plugin's requests to the endpoint.
• Server Errors: The server hosting the endpoint may return errors due to internal issues or misconfigurations.

To resolve the "Plugin Endpoint Issue" error, verify the endpoint URL, ensure the endpoint is available and properly configured, check authentication credentials, and troubleshoot any network or CORS issues. Additionally, review server logs for any error messages that can provide more insight into the problem.

1.9 Feed URL is incorrectly defined on the Index page

This error indicates that the URL for a feed (such as an RSS or Atom feed) is incorrectly specified on the index page of a website. This can prevent users and feed readers from correctly accessing and subscribing to the feed. Common causes of this error include:

• Incorrect URL Syntax: The feed URL may be malformed or contain syntax errors.
• Broken Links: The feed URL points to a non-existent or broken link.
• Relative URLs: The feed URL may be specified as a relative URL instead of an absolute URL, causing issues when accessed from different locations.
• Typographical Errors: Simple typos in the feed URL can prevent correct access to the feed.
• Outdated URLs: The feed URL may have changed, but the index page has not been updated to reflect the new URL.
• Incorrect HTML Markup: Errors in the HTML markup where the feed URL is defined can lead to issues with feed discovery.

To resolve the "Feed URL is Incorrectly Defined on the Index Page" error, ensure that the feed URL is correctly formatted, points to a valid and accessible location, and is properly specified in the HTML of the index page. Additionally, check for any typographical errors and update outdated URLs as needed.

1.10 Second page of Feed is exactly the same as third page

This issue indicates that when navigating to the second page of a feed (such as an RSS or Atom feed), the content displayed is identical to that of the third page. This could occur due to various reasons in the feed generation or pagination process. Common causes include:

• Pagination Logic Error: There may be a bug in the pagination logic where the second page is incorrectly displaying the content intended for the third page.
• Feed Generation Issue: The mechanism responsible for generating the feed may not be correctly incrementing the pagination parameters (like offset or page) between pages, resulting in duplicate content.
• Caching or Stale Data: If caching is involved, the second page may be serving cached data that is not properly updated or cleared.
• Incorrect URL Parameters: The URLs for the pagination links (e.g., ?page=2) might not be correctly constructed or interpreted by the feed reader or aggregator.

To resolve the issue where the "Second Page of Feed is Exactly the Same as Third Page," review the code responsible for generating the feed content and pagination. Ensure that:

1. Pagination parameters are correctly incremented or calculated.
2. Cached data is refreshed or invalidated appropriately.
3. URL parameters and generation logic are accurate and consistent.

Testing with different feed readers or aggregators can help identify whether the issue is consistent across platforms or specific to certain configurations.

1.11 Updating Store issues

This error indicates that data could not be obtained/updated at Store level in doomanager either because it is not found (inactive or deleted) or the parameters have been passed incorrectly.

1.12 Other connection issues

Connection issues can manifest in various forms across different systems and applications. These issues typically revolve around difficulties establishing or maintaining communication between client and server components.

2. Data issues

2.1 Incorrect Data format

Data that is not formatted correctly according to expected specifications, which can hinder its proper processing by systems and applications.

2.2 Missing or incomplete Data

Data that is partially or completely absent, leading to errors or incomplete outcomes in processes that rely on it.

2.3 Invalid values

Data values that do not meet expected validations or constraints, resulting in errors or unexpected behaviors in the system.

2.4 Data compatibility issues

Issues arising when data is not compatible between systems, software versions, or formats, complicating interoperability and data exchange.

3. Indexing issues

3.1 Issues with doofindex/doofapi

• Problems related to the doofindex or doofapi, potentially involving incorrect indexing, API failures, or misconfigurations affecting data retrieval and indexing operations.

• "Timeout": Timeout occurs when a server takes too long to respond to a request. This can happen due to heavy traffic, slow processing, network issues, or inefficient server code. It indicates that the server failed to respond within the expected time limit.

3.2 Empty Feed

The feed contains no data, which can result from issues with data generation, fetching, or filtering processes that produce or populate the feed.

3.3 Data type problem

Mismatches or errors in data types during indexing, causing incorrect data representation or processing failures in the index.

3.4 Other index issue

Any other problems affecting the indexing process not covered by the specific categories, including performance issues, partial indexing, or incorrect indexing logic.

4. Processing issues

4.1 Incorrect format

Data or input that does not adhere to the required format, leading to processing errors or failures in the system.

4.2 Wrong arguments

Incorrect or inappropriate arguments provided to functions or processes, causing errors or unexpected outcomes.

4.3 Other processing issues

Miscellaneous problems that occur during data or task processing, including performance bottlenecks, logic errors, or unexpected interruptions.

5. Unusual issues

5.1 All other logs not belonging to any other category

Logs or issues that do not fit into any predefined categories, encompassing any unique or unexpected problems that require special attention.

Deactivating the automatic process

If automatic indexing fails 5 times in a row, automatic indexing is disabled. This error doesn't affect the normal functioning of the search function in your site, only affects the products updating.

You can re-enable it from your Admin Panel. Go to Search Engines > Settings > Indices and then click the Configuration button at the top-right side of the screen. The Indices Configuration panel will open at the right side, and you will be able to enable the Automatic Indexing option again.

No changes in feed

To save your plan requests, Doofinder downloads your data and stores it in a file. Then it checks if that file is identical to the one downloaded the last time the indexing was triggered. If the file didn't change, there's no need to reprocess it, and the "nothing changed" message is logged in your Admin.