Component pod error 'the path xxx does not exist', how to deal with?

Some components on the platform will create directories under the specified or custom paths on the node to store necessary files during program runtime. When these paths are symbolic links, it is necessary to ensure that each symbolic link points to an existing directory on the node. Otherwise, it may cause the container group of the component to fail to start normally or the platform cannot collect data related to the component.

Description of the problem

When checking the container group logs of the component (docker logs <container ID>) or the container group description (docker describe <container ID>), the error message contains the following content:

the path xxx/xxx/xxx.xx does not exist.

Output example:

The directory named as part of the path /scan_dir/cpaas/log/fluent.log does not exist.

General screening method

1. Check if the directory path mentioned in the error message on the node where the container group is located exists.

   • Exists: Please try other troubleshooting methods or contact our company’s operations and maintenance engineer for support.

   • Does not exist: Continue with the remaining steps.

2. Create the missing directory on the node as indicated by the path mentioned in the error message.

3. Rebuild the container group of the component by deleting it.

nevermore component check method

Note: The default path for storing necessary files for the nevermore component during program runtime is /cpaas, and users can modify this path.
After modification, ensure that the path actually exists on the node and that the value of the nevermore.dataDirName field in the chart-alauda-log-agent chart is changed to the modified path.

Procedure

1. Check if the directory path mentioned in the error message on the node where the container group is located exists.

   • Exists: Check if the value of the nevermore.dataDirName field in the chart-alauda-log-agent chart is consistent with the directory path mentioned in the error message.

     • Consistent: Please try other troubleshooting methods or contact our company’s operations and maintenance engineer for support.

     • Inconsistent: Modify the value of the nevermore.dataDirName field in the chart-alauda-log-agent chart to the actual path of the directory that exists on the node.

   • Does not exist: Continue with the remaining steps.

2. Create the missing directory on the node as indicated by the path mentioned in the error message.

3. Rebuild the container group of the component by deleting it.