BLOBD Log Message ListΒΆ

ID Number Description
061f0000 Failed to get gRPC service name
061f0001 Failed to get gRPC port
061f0002 Failed to get gRPC client certificate
061f0003 Failed to get gRPC client key
061f0004 Failed to get gRPC CA certificate
061f0005 Failed to create download directories: %v
061f0006 CPU
061f0007 TMM
061f0008 Failed to get gRPC service name
061f0009 Failed to get gRPC port
061f000a Failed to get gRPC client certificate
061f000b Failed to get gRPC client key
061f000c Failed to get gRPC CA certificate
061f000d Failed to get database directory
061f000e Stopping grpc server...
061f000f Stopped grpc server and blobd...
061f0010 Failed to get gRPC service name
061f0011 Failed to get gRPC port
061f0012 Failed to get gRPC client certificate
061f0013 Failed to get gRPC client key
061f0014 Failed to get gRPC CA certificate
061f0015 Failed to read the certificate files
061f0016 Grpc Client opening conn
061f0017 gRPCv2 - No heartbeat from TMM
061f0018 gRPCv2 - Recv'd heartbeat from TMM
061f0019 gRPCv2 - Can't get name of Any object
061f001a gRPCv2 - Unknown type in Any
061f001b gRPCv2 - Protobuf
061f001c gRPCv2 - Could not configure TMM
061f001d gRPCv2 - send configuration SUCCESS
061f001e gRPCv2 - Expected
061f001f gRPCv2 message transaction
061f0020 SendGrpcMsg: gRPC connection failed on
061f0021 Send GRPC message retrying
061f0022 SendGrpcMsg: gRPC request failed
061f0023 Send geoip
061f0024 Failed to get gRPC service name
061f0025 Failed to get gRPC port
061f0026 Failed to get gRPC client certificate
061f0027 Failed to get gRPC client key
061f0028 Failed to get gRPC CA certificate
061f0029 Failed to get gRPC service name
061f002a Failed to get gRPC port
061f002b Failed to get gRPC client certificate
061f002c Failed to get gRPC client key
061f002d Failed to get gRPC CA certificate
061f002e Failed to get gRPC service name
061f002f Failed to get gRPC port
061f0030 Failed to get gRPC client certificate
061f0031 Failed to get gRPC client key
061f0032 Failed to get gRPC CA certificate
061f0033 Failed to get gRPC service name
061f0034 Failed to get gRPC port
061f0035 Failed to get gRPC client certificate
061f0036 Failed to get gRPC client key
061f0037 Failed to get gRPC CA certificate
061f0038 Failed to get gRPC service name
061f0039 Failed to get gRPC port
061f003a Failed to get gRPC client certificate
061f003b Failed to get gRPC client key
061f003c Failed to get gRPC CA certificate
061f003d Handling GRPC
061f003e Create Msg
061f003f Got GetHeartbeat.
061f0040 Prepared
061f0041 Received message
061f0042 unmarshalling
061f0043 Unsupported
061f0044 Failed to extract
061f0045 Failed to process received
061f0046 Received exception
061f0047 UnHandled Exception
061f0048 unmarshalling
061f0049 Received exceptionObject
061f004a UnHandled
061f004b Delete file
061f004c Successfully received new
061f004d Unsupported data type
061f004e Failed to process received
061f004f Failed to remove
061f0050 File Received Done
061f0051 File Recv error
061f0052 File Create Failed
061f0053 File write failed
061f0054 Stream send response
061f0055 Environment variable
061f0056 Cannot load TLS credentials
061f0057 Environment variable
061f0058 Failed to listen
061f0059 GRPC server running on
061f005a Failed to serve
061f005b Creating a directory for new geoip file
061f005c Moving file from
061f005d Error opening
061f005e Error creating
061f005f Error Copying File from
061f0060 bytes Copied
061f0061 Failed to rename
061f0062 Failed to remove source file (non-fatal)
061f0063 Error creating geoip destination
061f0064 Error copying GeoIp file
061f0065 Failed to send grpc message to TMM
061f0066 Failed to open
061f0067 Failed to create
061f0068 Failed to copy the file from
061f0069 Failed to remove
061f006a Failed to read AFM blob
061f006b Failed to delete the old AFM
061f006c Old AFM blob file removed
061f006d Invalid AFM blob file name received
061f006e Error in creating AFM blob
061f006f Created AFM blob
061f0070 Failed to move the downloaded
061f0071 Copied downloaded
061f0072 Failed to send grpc message to TMM
061f0073 Failed to copy
061f0074 Failed to rename
061f0075 Failed to remove
061f0076 Received dwbl blob
061f0077 Received Iprep
061f0078 Received invalid
061f0079 Error in creating blob
061f007a Created blob
061f007b Failed to move the downloaded file
061f007c Moved downloaded
061f007d Failed to send grpc message to TMM for IPI feature
061f007e Failed to read directory
061f007f Failed to delete old file
061f0080 Deleted old file
061f0081 Deleting directory
061f0082 Error creating ips blob destination
061f0083 Creating a directory for new ips packages
061f0084 Moving file from
061f0085 Error opening
061f0086 Error creating
061f0087 Error Copying File from
061f0088 bytes Copied
061f0089 Error with path creation
061f008a Error creating ips destination
061f008b Error moving ips files
061f008c Error moving ips files
061f008d Error sending grpc message
061f008e Creating a directory for new netstar packages
061f008f Moving netstar file from
061f0090 Error opening netstar file
061f0091 Error creating netstar file
061f0092 Error copying netstar file
061f0093 bytes copied for netstar file
061f0094 Failed to copy netstar file
061f0095 Failed to rename netstar file
061f0096 Failed to remove netstar source file
061f0097 Unsupported netstar file type
061f0098 Received netstar file
061f0099 Error creating netstar destination folder
061f009a Processing netstar database ZIP file
061f009b Error extracting netstar zip file
061f009c Failed to remove netstar source zip file
061f009d Successfully processed netstar database ZIP file
061f009e Error processing gcf1.conf file
061f009f Failed to remove gcf1.conf source file
061f00a0 Error moving netstar file atomically
061f00a1 Successfully processed netstar config file
061f00a2 Extracting netstar zip file
061f00a3 Failed to open zip file
061f00a4 Invalid database file pattern in zip
061f00a5 Unknown file type in zip
061f00a6 Extracting file from zip
061f00a7 Failed to open file in zip
061f00a8 Failed to create extracted file
061f00a9 Failed to copy file content
061f00aa Failed to rename extracted file
061f00ab Successfully extracted and renamed file
061f00ac meta.json already exists, overwriting with new mappings
061f00ad Failed to create meta.json file
061f00ae Failed to write to meta.json file
061f00af Successfully created meta.json file
061f00b0 Error sending netstar grpc message
061f00b1 Successfully sent netstar database update notification
061f00b2 Processing gcf1.conf file to update DB_PATH and other settings
061f00b3 Failed to open gcf1.conf source file
061f00b4 Failed to create gcf1.conf temp file
061f00b5 Updated DB_PATH in gcf1.conf
061f00b6 Updated TELEMETRY_ENABLE in gcf1.conf
061f00b7 Updated TRACE_LOG_LEVEL in gcf1.conf
061f00b8 Updated LIBRARY_LOG_LEVEL in gcf1.conf
061f00b9 Updated IPDB_ENABLE in gcf1.conf
061f00ba Failed to write line to gcf1.conf
061f00bb Error reading gcf1.conf file
061f00bc Error flushing gcf1.conf file
061f00bd Failed to rename gcf1.conf temp file
061f00be Successfully processed and updated gcf1.conf
061f00bf No target settings found in gcf1.conf, file copied as-is
061f00c0 Failed to read urlcat DB directory
061f00c1 Failed to delete
061f00c2 Old DB file removed
061f00c3 Failed to copy
061f00c4 Failed to rename
061f00c5 Failed to remove
061f00c6 Error in creating blob
061f00c7 Created blob
061f00c8 Attempting to move webroot
061f00c9 Failed to move the file to webroot location
061f00ca Moved webroot
061f00cb Error loading cert/key files
061f00cc Error reading root CA
061f00cd Error loading root CA
061f00ce Reloaded cert files
061f00cf Error creating new watcher for pipefile
061f00d0 Received file watch
061f00d1 File watch event
061f00d2 Error adding watcher cert path for fsnotify
061f00d3 Error adding watcher root CA path for fsnotify

Log Message Details

061f0000 : Failed to get gRPC service name

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC service name for TMM from environment variables.
workaround: Verify the TMM_GRPC_SVC_NAME environment variable is set correctly.

061f0001 : Failed to get gRPC port

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC port for TMM from environment variables.
workaround: Verify the TMM_GRPC_PORT environment variable is set correctly.

061f0002 : Failed to get gRPC client certificate

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC client certificate from environment variables.
workaround: Verify the GRPC_CLT_CERT environment variable is set correctly.

061f0003 : Failed to get gRPC client key

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC client key from environment variables.
workaround: Verify the GRPC_CLT_KEY environment variable is set correctly.

061f0004 : Failed to get gRPC CA certificate

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC server CA certificate from environment variables.
workaround: Verify the GRPC_SRV_CA environment variable is set correctly.

061f0005 : Failed to create download directories: %v

sev: Error
Type: Application
args: N/A
cause: Failed to create required download subdirectories under /var/download.
workaround: Verify the /var/download directory exists, has correct permissions, and is writable by the blobd process user.

061f0006 : CPU

sev: Info
Type: Application
args:
  • Count
cause: N/A
workaround: N/A

061f0007 : TMM

sev: Info
Type: Application
args:
  • Count
cause: N/A
workaround: N/A

061f0008 : Failed to get gRPC service name

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC service name for TMM from environment variables.
workaround: Verify the TMM_GRPC_SVC_NAME environment variable is set correctly.

061f0009 : Failed to get gRPC port

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC port for TMM from environment variables.
workaround: Verify the TMM_GRPC_PORT environment variable is set correctly.

061f000a : Failed to get gRPC client certificate

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC client certificate from environment variables.
workaround: Verify the GRPC_CLT_CERT environment variable is set correctly.

061f000b : Failed to get gRPC client key

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC client key from environment variables.
workaround: Verify the GRPC_CLT_KEY environment variable is set correctly.

061f000c : Failed to get gRPC CA certificate

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC server CA certificate from environment variables.
workaround: Verify the GRPC_SRV_CA environment variable is set correctly.

061f000d : Failed to get database directory

sev: Error
Type: Application
args: N/A
cause: Failed to get the database directory path from environment variables.
workaround: Verify the BC_DATABASE environment variable is set correctly.

061f000e : Stopping grpc server...

sev: Info
Type: Application
args: N/A
cause: N/A
workaround: N/A

061f000f : Stopped grpc server and blobd...

sev: Info
Type: Application
args: N/A
cause: N/A
workaround: N/A

061f0010 : Failed to get gRPC service name

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC service name for TMM from environment variables.
workaround: Verify the TMM_GRPC_SVC_NAME environment variable is set correctly.

061f0011 : Failed to get gRPC port

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC port for TMM from environment variables.
workaround: Verify the TMM_GRPC_PORT environment variable is set correctly.

061f0012 : Failed to get gRPC client certificate

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC client certificate from environment variables.
workaround: Verify the GRPC_CLT_CERT environment variable is set correctly.

061f0013 : Failed to get gRPC client key

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC client key from environment variables.
workaround: Verify the GRPC_CLT_KEY environment variable is set correctly.

061f0014 : Failed to get gRPC CA certificate

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC server CA certificate from environment variables.
workaround: Verify the GRPC_SRV_CA environment variable is set correctly.

061f0015 : Failed to read the certificate files

sev: Error
Type: Application
args:
  • error
cause: Failed to read the TLS certificate files for gRPC client authentication.
workaround: Verify certificate files exist in the expected paths and are readable by the blobd process.

061f0016 : Grpc Client opening conn

sev: Info
Type: Transaction
args:
  • host
  • dialOpts
cause: N/A
workaround: N/A

061f0017 : gRPCv2 - No heartbeat from TMM

sev: Error
Type: Transaction
args:
  • error
cause: Failed to receive heartbeat response from TMM gRPC service.
workaround: Verify TMM is running and the gRPC service is available.

061f0018 : gRPCv2 - Recv'd heartbeat from TMM

sev: Info
Type: Transaction
args:
  • dpcMsg
cause: N/A
workaround: N/A

061f0019 : gRPCv2 - Can't get name of Any object

sev: Info
Type: Application
args:
  • error
cause: N/A
workaround: N/A

061f001a : gRPCv2 - Unknown type in Any

sev: Error
Type: Application
args:
  • name
cause: Received an unknown or unsupported message type in the protobuf Any field.
workaround: Verify the protobuf definitions match between blobd and TMM. Check for version mismatches.

061f001b : gRPCv2 - Protobuf

sev: Info
Type: Transaction
args:
  • index
  • error
cause: N/A
workaround: N/A

061f001c : gRPCv2 - Could not configure TMM

sev: Error
Type: Transaction
args:
  • seq
  • error
cause: Failed to send configuration message to TMM via gRPC.
workaround: Check TMM availability, gRPC connection status, and network connectivity. Review TMM logs for errors.

061f001d : gRPCv2 - send configuration SUCCESS

sev: Info
Type: Transaction
args:
  • dpcMsg
cause: N/A
workaround: N/A

061f001e : gRPCv2 - Expected

sev: Info
Type: Transaction
args:
  • seq
  • got
cause: N/A
workaround: N/A

061f001f : gRPCv2 message transaction

sev: Info
Type: Transaction
args:
  • address
  • SeqStart
cause: N/A
workaround: N/A

061f0020 : SendGrpcMsg: gRPC connection failed on

sev: Error
Type: Transaction
args:
  • endpoint
  • error
cause: Failed to establish gRPC connection to the TMM endpoint.
workaround: Verify TMM is running and the gRPC service is available.

061f0021 : Send GRPC message retrying

sev: Info
Type: Transaction
args:
  • retry count
  • error
cause: N/A
workaround: N/A

061f0022 : SendGrpcMsg: gRPC request failed

sev: Error
Type: Transaction
args:
  • error
cause: gRPC configuration request to TMM failed after retries.
workaround: Check TMM logs for specific error details. Verify the configuration message format is correct.

061f0023 : Send geoip

sev: Info
Type: System
args: N/A
cause: N/A
workaround: N/A

061f0024 : Failed to get gRPC service name

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC service name for TMM from environment variables.
workaround: Verify the TMM_GRPC_SVC_NAME environment variable is set correctly.

061f0025 : Failed to get gRPC port

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC port for TMM from environment variables.
workaround: Verify the TMM_GRPC_PORT environment variable is set correctly.

061f0026 : Failed to get gRPC client certificate

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC client certificate from environment variables.
workaround: Verify the GRPC_CLT_CERT environment variable is set correctly.

061f0027 : Failed to get gRPC client key

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC client key from environment variables.
workaround: Verify the GRPC_CLT_KEY environment variable is set correctly.

061f0028 : Failed to get gRPC CA certificate

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC server CA certificate from environment variables.
workaround: Verify the GRPC_SRV_CA environment variable is set correctly.

061f0029 : Failed to get gRPC service name

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC service name for TMM from environment variables.
workaround: Verify the TMM_GRPC_SVC_NAME environment variable is set correctly.

061f002a : Failed to get gRPC port

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC port for TMM from environment variables.
workaround: Verify the TMM_GRPC_PORT environment variable is set correctly.

061f002b : Failed to get gRPC client certificate

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC client certificate from environment variables.
workaround: Verify the GRPC_CLT_CERT environment variable is set correctly.

061f002c : Failed to get gRPC client key

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC client key from environment variables.
workaround: Verify the GRPC_CLT_KEY environment variable is set correctly.

061f002d : Failed to get gRPC CA certificate

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC server CA certificate from environment variables.
workaround: Verify the GRPC_SRV_CA environment variable is set correctly.

061f002e : Failed to get gRPC service name

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC service name for TMM from environment variables.
workaround: Verify the TMM_GRPC_SVC_NAME environment variable is set correctly.

061f002f : Failed to get gRPC port

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC port for TMM from environment variables.
workaround: Verify the TMM_GRPC_PORT environment variable is set correctly.

061f0030 : Failed to get gRPC client certificate

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC client certificate from environment variables.
workaround: Verify the GRPC_CLT_CERT environment variable is set correctly.

061f0031 : Failed to get gRPC client key

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC client key from environment variables.
workaround: Verify the GRPC_CLT_KEY environment variable is set correctly.

061f0032 : Failed to get gRPC CA certificate

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC server CA certificate from environment variables.
workaround: Verify the GRPC_SRV_CA environment variable is set correctly.

061f0033 : Failed to get gRPC service name

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC service name for TMM from environment variables.
workaround: Verify the TMM_GRPC_SVC_NAME environment variable is set correctly.

061f0034 : Failed to get gRPC port

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC port for TMM from environment variables.
workaround: Verify the TMM_GRPC_PORT environment variable is set correctly.

061f0035 : Failed to get gRPC client certificate

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC client certificate from environment variables.
workaround: Verify the GRPC_CLT_CERT environment variable is set correctly.

061f0036 : Failed to get gRPC client key

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC client key from environment variables.
workaround: Verify the GRPC_CLT_KEY environment variable is set correctly.

061f0037 : Failed to get gRPC CA certificate

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC server CA certificate from environment variables.
workaround: Verify the GRPC_SRV_CA environment variable is set correctly.

061f0038 : Failed to get gRPC service name

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC service name for TMM from environment variables.
workaround: Verify the GRPC_SVC_NAME environment variable is set correctly.

061f0039 : Failed to get gRPC port

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC port for TMM from environment variables.
workaround: Verify the TMM_GRPC_SRV_PORT environment variable is set correctly.

061f003a : Failed to get gRPC client certificate

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC client certificate from environment variables.
workaround: Verify the GRPC_CLIENT_CERT environment variable is set correctly.

061f003b : Failed to get gRPC client key

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC client key from environment variables.
workaround: Verify the GRPC_CLIENT_KEY environment variable is set correctly.

061f003c : Failed to get gRPC CA certificate

sev: Error
Type: Application
args: N/A
cause: Failed to get the gRPC CA certificate from environment variables.
workaround: Verify the GRPC_CLIENT_CA environment variable is set correctly.

061f003d : Handling GRPC

sev: Info
Type: Transaction
args:
  • message
cause: N/A
workaround: N/A

061f003e : Create Msg

sev: Info
Type: Transaction
args:
  • SeqStart
cause: N/A
workaround: N/A

061f003f : Got GetHeartbeat.

sev: Info
Type: Application
args: N/A
cause: N/A
workaround: N/A

061f0040 : Prepared

sev: Info
Type: Transaction
args:
  • reply
cause: N/A
workaround: N/A

061f0041 : Received message

sev: Info
Type: Transaction
args:
  • num
  • name
  • inner
  • Recipient
cause: N/A
workaround: N/A

061f0042 : unmarshalling

sev: Error
Type: Transaction
args:
  • error
cause: Protocol buffer message cannot be unmarshalled due to invalid data format or type mismatch.
workaround: Check correct protobuf message types are being sent. Verify declTmm proto definitions match between blobd and sender.

061f0043 : Unsupported

sev: Warning
Type: Application
args:
  • file type
cause: N/A
workaround: N/A

061f0044 : Failed to extract

sev: Error
Type: Application
args:
  • file
  • error
cause: Tar/gzip extraction failed due to corrupted archive, invalid path, or insufficient permissions.
workaround: Verify tar.gz file is not corrupted. Check download folder permissions and disk space. Ensure file URI is valid.

061f0045 : Failed to process received

sev: Error
Type: Application
args:
  • file
cause: Handler failed to process extracted file due to handler-specific errors (see logs).
workaround: Check specific handler error logs for detailed cause. Verify destination directories exist with proper permissions.

061f0046 : Received exception

sev: Info
Type: Transaction
args:
  • message
  • Recipient
cause: N/A
workaround: N/A

061f0047 : UnHandled Exception

sev: Info
Type: Transaction
args:
  • reason
cause: N/A
workaround: N/A

061f0048 : unmarshalling

sev: Error
Type: Transaction
args:
  • error
cause: Exception object embedded message cannot be unmarshalled due to invalid protobuf data.
workaround: Check correct exception message format is being sent. Verify proto definitions are synchronized.

061f0049 : Received exceptionObject

sev: Info
Type: Transaction
args:
  • name
  • inner
cause: N/A
workaround: N/A

061f004a : UnHandled

sev: Info
Type: Transaction
args:
  • Msg
cause: N/A
workaround: N/A

061f004b : Delete file

sev: Info
Type: Transaction
args:
  • uuid
cause: N/A
workaround: N/A

061f004c : Successfully received new

sev: Info
Type: Transaction
args:
  • component
  • file
cause: N/A
workaround: N/A

061f004d : Unsupported data type

sev: Error
Type: Application
args:
  • component
cause: Received a file download request for an unsupported or unrecognized component type.
workaround: Verify the component type being sent matches one of the supported types (wr-urldb, dpi, ips, ips-blob, ipi, afm, dwbl, geoip).

061f004e : Failed to process received

sev: Error
Type: Application
args:
  • file
cause: Handler failed to process the received file.
workaround: Check logs for specific error details. Verify file format, permissions, and destination directory availability.

061f004f : Failed to remove

sev: Error
Type: System
args:
  • file
  • error
cause: Failed to delete partially received file after download error.
workaround: Verify file permissions and disk space. Manually remove the file if necessary.

061f0050 : File Received Done

sev: Info
Type: System
args:
  • file
  • size
cause: N/A
workaround: N/A

061f0051 : File Recv error

sev: Error
Type: System
args:
  • file
  • error
cause: Failed to receive data from the gRPC stream during file download.
workaround: Check network connectivity and gRPC client status. Retry the download operation.

061f0052 : File Create Failed

sev: Error
Type: System
args:
  • filepath
  • error
cause: Failed to create the destination file for download.
workaround: Verify the download directory exists, has write permissions, and sufficient disk space is available.

061f0053 : File write failed

sev: Error
Type: System
args:
  • error
cause: Failed to write downloaded data to file or write size mismatch.
workaround: Check disk space availability and file system health. Verify write permissions.

061f0054 : Stream send response

sev: Error
Type: System
args:
  • error
cause: Failed to send acknowledgment response back to the gRPC client.
workaround: Check network connectivity and gRPC stream status.

061f0055 : Environment variable

sev: Warning
Type: Application
args:
  • prop
  • error
cause: N/A
workaround: N/A

061f0056 : Cannot load TLS credentials

sev: Emergency
Type: Compliance
args:
  • error
cause: Failed to load TLS credentials for securing the gRPC server.
workaround: Verify certificate files exist and are valid. Check f5-cert-client configuration and certificate paths.

061f0057 : Environment variable

sev: Warning
Type: Application
args:
  • prop
  • error
cause: N/A
workaround: N/A

061f0058 : Failed to listen

sev: Error
Type: System
args:
  • error
cause: Failed to create TCP listener on the specified port for gRPC server.
workaround: Verify the port is not already in use and the process has permission to bind to the port.

061f0059 : GRPC server running on

sev: Info
Type: Application
args:
  • port
cause: N/A
workaround: N/A

061f005a : Failed to serve

sev: Emergency
Type: Application
args:
  • error
cause: gRPC server failed to serve requests.
workaround: Check logs for specific error details. Verify network configuration and system resources.

061f005b : Creating a directory for new geoip file

sev: Info
Type: System
args:
  • path
cause: N/A
workaround: N/A

061f005c : Moving file from

sev: Info
Type: System
args:
  • oldfile
  • newfile
cause: N/A
workaround: N/A

061f005d : Error opening

sev: Error
Type: System
args:
  • file
  • error
cause: Failed to open the source GeoIP file for reading.
workaround: Verify the source file exists and has read permissions. Check the file path is correct.

061f005e : Error creating

sev: Error
Type: System
args:
  • file
  • error
cause: Failed to create the temporary GeoIP file.
workaround: Verify the destination directory exists and has write permissions. Check disk space availability.

061f005f : Error Copying File from

sev: Error
Type: System
args:
  • source file
  • to
  • error
cause: Failed to copy GeoIP file contents from source to destination.
workaround: Verify sufficient disk space and file permissions. Check for filesystem errors.

061f0060 : bytes Copied

sev: Info
Type: System
args:
  • bytes
cause: N/A
workaround: N/A

061f0061 : Failed to rename

sev: Error
Type: System
args:
  • src file
  • dst file
  • error
cause: Atomic rename operation failed due to filesystem issues or permission errors.
workaround: Check destination directory permissions and verify no other process is accessing the target file. Clean up .tmp files manually if needed.

061f0062 : Failed to remove source file (non-fatal)

sev: Error
Type: System
args:
  • file
  • error
cause: Source file cannot be deleted after successful copy, likely due to permission issues or file still open.
workaround: Check file permissions and verify no other process has the file open. Manually remove orphaned source file.

061f0063 : Error creating geoip destination

sev: Error
Type: System
args:
  • folder
cause: Failed to create the GeoIP destination directory.
workaround: Verify parent directory exists and has write permissions. Check disk space and filesystem health.

061f0064 : Error copying GeoIp file

sev: Error
Type: System
args:
  • folder
cause: Failed to copy GeoIP file to the destination directory.
workaround: Check file permissions, disk space, and filesystem health. Verify source file is not corrupted.

061f0065 : Failed to send grpc message to TMM

sev: Error
Type: Transaction
args: N/A
cause: Failed to send GeoIP notification to TMM via gRPC.
workaround: Verify TMM is running and gRPC connection is available. Check logs for additional details.

061f0066 : Failed to open

sev: Error
Type: System
args:
  • file
  • error
cause: Source AFM blob file cannot be opened due to permission issues or file does not exist.
workaround: Check source file permissions and verify file exists. Ensure blobd process has read access to the file.

061f0067 : Failed to create

sev: Error
Type: System
args:
  • file
  • error
cause: Destination AFM blob file cannot be created due to permission issues or invalid path.
workaround: Check destination directory write permissions and verify directory exists. Ensure sufficient disk space.

061f0068 : Failed to copy the file from

sev: Error
Type: System
args:
  • srcFile
  • dstFile
  • error
cause: File copy operation failed due to I/O error, disk full, or filesystem corruption.
workaround: Check disk space availability and filesystem health. Verify source file is not corrupted. Retry download.

061f0069 : Failed to remove

sev: Error
Type: System
args:
  • file
  • error
cause: Source file cannot be deleted after successful copy, likely due to permission issues.
workaround: Check file permissions and verify no other process has the file open. Manually remove orphaned source file.

061f006a : Failed to read AFM blob

sev: Error
Type: System
args:
  • directory
  • error
cause: AFM blob directory cannot be read due to permission issues or directory does not exist.
workaround: Verify directory exists and has read permissions for blobd process. Check filesystem health.

061f006b : Failed to delete the old AFM

sev: Error
Type: System
args:
  • blob file
  • error
cause: Old AFM blob file cannot be deleted due to permission issues or file still in use.
workaround: Check file permissions and verify no other process has the file open. Manually remove old blob files.

061f006c : Old AFM blob file removed

sev: Info
Type: System
args:
  • file
cause: N/A
workaround: N/A

061f006d : Invalid AFM blob file name received

sev: Error
Type: Transaction
args:
  • file
cause: Received file name does not match expected pattern (must contain "nat" or "acl").
workaround: Verify correct file names are being sent.

061f006e : Error in creating AFM blob

sev: Error
Type: System
args:
  • directory
  • error
cause: AFM blob directory creation failed due to permission issues or invalid parent path.
workaround: Verify parent directory exists and has write permissions. Check if blobd process has sufficient privileges.

061f006f : Created AFM blob

sev: Info
Type: System
args:
  • directory
cause: N/A
workaround: N/A

061f0070 : Failed to move the downloaded

sev: Error
Type: System
args:
  • old file
  • new file
  • error
cause: MoveFile operation failed during open, create, copy, or remove steps.
workaround: See specific error from MoveFile above. Check file permissions, disk space, and filesystem health.

061f0071 : Copied downloaded

sev: Info
Type: System
args:
  • old file
  • new file
cause: N/A
workaround: N/A

061f0072 : Failed to send grpc message to TMM

sev: Error
Type: Transaction
args:
  • error
cause: gRPC communication with TMM failed for AFM blob notification.
workaround: Verify TMM is running and gRPC connection is established. Check logs for connection errors. Restart blobd if needed.

061f0073 : Failed to copy

sev: Error
Type: System
args:
  • src file
  • dst file
  • error
cause: Source file cannot be read or destination file cannot be written during IPI file copy operation.
workaround: Check source file permissions and destination directory write permissions. Verify disk space is available.

061f0074 : Failed to rename

sev: Error
Type: System
args:
  • src file
  • dst file
  • error
cause: Atomic rename operation failed due to filesystem issues or permission errors.
workaround: Check destination directory permissions and verify no other process is accessing the target file. Clean up .tmp files manually if needed.

061f0075 : Failed to remove

sev: Error
Type: System
args:
  • file
  • error
cause: Source file cannot be deleted after successful copy, likely due to permission issues or file still open.
workaround: Check file permissions and verify no other process has the file open. Manually remove orphaned source file.

061f0076 : Received dwbl blob

sev: Info
Type: Transaction
args:
  • path name
cause: N/A
workaround: N/A

061f0077 : Received Iprep

sev: Info
Type: Transaction
args:
  • DB file : %s
cause: N/A
workaround: N/A

061f0078 : Received invalid

sev: Error
Type: Transaction
args:
  • file name
cause: Received file name does not match expected pattern (must contain "dwbl" or "F5Ip").
workaround: Verify correct file names are being sent.

061f0079 : Error in creating blob

sev: Error
Type: System
args:
  • directory
  • error
cause: Target directory creation failed due to permission issues or invalid parent path.
workaround: Verify parent directory exists and has write permissions. Check if blobd process has sufficient privileges.

061f007a : Created blob

sev: Info
Type: System
args:
  • directory
cause: N/A
workaround: N/A

061f007b : Failed to move the downloaded file

sev: Error
Type: System
args:
  • absoluteFileName
  • newAbsoluteFileName
  • error
cause: moveIpiFile operation failed during copy, rename, or remove steps.
workaround: See specific error from moveIpiFile above. Check file permissions, disk space, and filesystem health.

061f007c : Moved downloaded

sev: Info
Type: System
args:
  • old file
  • new file
cause: N/A
workaround: N/A

061f007d : Failed to send grpc message to TMM for IPI feature

sev: Error
Type: Transaction
args: N/A
cause: gRPC communication with TMM failed for IPI notification.
workaround: Verify TMM is running and gRPC connection is established. Check logs for connection errors. Restart blobd if needed.

061f007e : Failed to read directory

sev: Error
Type: System
args:
  • directory
  • error
cause: Directory cannot be read due to permission issues or directory does not exist.
workaround: Verify directory exists and has read permissions for blobd process. Check filesystem health.

061f007f : Failed to delete old file

sev: Error
Type: System
args:
  • file
  • error
cause: Old file cannot be deleted due to permission issues or file still in use.
workaround: Check file permissions and verify no other process has the file open. Manually remove old files if needed.

061f0080 : Deleted old file

sev: Info
Type: System
args:
  • file
cause: N/A
workaround: N/A

061f0081 : Deleting directory

sev: Info
Type: System
args:
  • folder
cause: N/A
workaround: N/A

061f0082 : Error creating ips blob destination

sev: Error
Type: System
args:
  • folder
cause: Failed to create the IPS blob destination directory.
workaround: Verify parent directory exists and has write permissions. Check disk space and filesystem health.

061f0083 : Creating a directory for new ips packages

sev: Info
Type: System
args:
  • path
cause: N/A
workaround: N/A

061f0084 : Moving file from

sev: Info
Type: System
args:
  • oldfile
  • newfile
cause: N/A
workaround: N/A

061f0085 : Error opening

sev: Error
Type: System
args:
  • file
cause: Failed to open the source IPS file for reading.
workaround: Verify the source file exists and has read permissions. Check the file path is correct.

061f0086 : Error creating

sev: Error
Type: System
args:
  • file
cause: Failed to create the destination IPS file.
workaround: Verify the destination directory exists and has write permissions. Check disk space availability.

061f0087 : Error Copying File from

sev: Error
Type: System
args:
  • source file
  • new file
cause: Failed to copy IPS file contents from source to destination.
workaround: Verify sufficient disk space and file permissions. Check for filesystem errors.

061f0088 : bytes Copied

sev: Info
Type: System
args:
  • bytes
cause: N/A
workaround: N/A

061f0089 : Error with path creation

sev: Error
Type: System
args:
  • path
cause: Failed to create the IPS directory path.
workaround: Verify parent directory exists and has write permissions. Check disk space and filesystem health.

061f008a : Error creating ips destination

sev: Error
Type: System
args:
  • folder
cause: Failed to create the IPS destination directory for the specific version.
workaround: Verify parent directory exists and has write permissions. Check disk space and filesystem health.

061f008b : Error moving ips files

sev: Error
Type: System
args:
  • source file
  • destination file
cause: Failed to copy IPS file to the destination directory.
workaround: Check file permissions, disk space, and filesystem health. Verify source file is not corrupted.

061f008c : Error moving ips files

sev: Error
Type: System
args:
  • srcDebugpath
  • finalDebugPath
cause: Failed to copy IPS debug file to the destination directory.
workaround: Check file permissions, disk space, and filesystem health. Verify source file is not corrupted.

061f008d : Error sending grpc message

sev: Error
Type: Transaction
args:
  • finalLibPath
  • finalDebugPath
cause: Failed to send IPS path update to TMM via gRPC.
workaround: Verify TMM is running and gRPC connection is available. Check logs for additional details.

061f008e : Creating a directory for new netstar packages

sev: Info
Type: System
args:
  • path
cause: N/A
workaround: N/A

061f008f : Moving netstar file from

sev: Info
Type: System
args:
  • oldfile
  • newfile
cause: N/A
workaround: N/A

061f0090 : Error opening netstar file

sev: Error
Type: System
args:
  • file
cause: Failed to open the netstar source file for reading due to permission issues or file does not exist.
workaround: Verify the source file exists and has appropriate read permissions. Ensure blobd process has read access to the file.

061f0091 : Error creating netstar file

sev: Error
Type: System
args:
  • file
cause: Failed to create the netstar destination file due to permission issues or invalid path.
workaround: Verify the destination directory exists and has appropriate write permissions. Ensure sufficient disk space.

061f0092 : Error copying netstar file

sev: Error
Type: System
args:
  • source file
  • new file
cause: Failed to copy netstar file contents from source to destination due to I/O error, disk full, or file corruption.
workaround: Verify sufficient disk space and that files are not corrupted. Verify source file is not corrupted. Retry operation.

061f0093 : bytes copied for netstar file

sev: Info
Type: System
args:
  • bytes
cause: N/A
workaround: N/A

061f0094 : Failed to copy netstar file

sev: Error
Type: System
args:
  • src file
  • dst file
  • error
cause: Failed to copy netstar file to temporary location.
workaround: Verify disk space, file permissions, and that source file is not corrupted.

061f0095 : Failed to rename netstar file

sev: Error
Type: System
args:
  • src file
  • dst file
  • error
cause: Failed to atomically rename netstar temporary file to final destination.
workaround: Verify file system supports atomic rename operations and has appropriate permissions.

061f0096 : Failed to remove netstar source file

sev: Error
Type: System
args:
  • file
  • error
cause: Failed to remove netstar source file after successful move.
workaround: Verify file permissions and that file is not locked by another process.

061f0097 : Unsupported netstar file type

sev: Error
Type: Application
args:
  • fileName
cause: Received a file that does not match expected netstar file patterns.
workaround: Verify the file name matches expected patterns: netstar_db_files.zip, netstar_gcf1.conf, or netstar_properties.conf.

061f0098 : Received netstar file

sev: Info
Type: Transaction
args:
  • file
cause: N/A
workaround: N/A

061f0099 : Error creating netstar destination folder

sev: Error
Type: System
args:
  • folder
cause: Failed to create the netstar destination directory.
workaround: Verify appropriate permissions and available disk space for creating directories.

061f009a : Processing netstar database ZIP file

sev: Info
Type: Transaction
args:
  • file
cause: N/A
workaround: N/A

061f009b : Error extracting netstar zip file

sev: Error
Type: System
args:
  • source file
  • error
cause: Failed to extract netstar database ZIP file.
workaround: Verify the ZIP file is not corrupted, has valid database files, and sufficient disk space.

061f009c : Failed to remove netstar source zip file

sev: Error
Type: System
args:
  • file
  • error
cause: Failed to remove netstar source ZIP file after successful extraction.
workaround: Verify file permissions and that file is not locked by another process.

061f009d : Successfully processed netstar database ZIP file

sev: Info
Type: Transaction
args:
  • file
cause: N/A
workaround: N/A

061f009e : Error processing gcf1.conf file

sev: Error
Type: System
args:
  • source file
  • destination file
cause: Failed to process and update gcf1.conf configuration file.
workaround: Verify the file format is valid and has appropriate permissions.

061f009f : Failed to remove gcf1.conf source file

sev: Error
Type: System
args:
  • file
  • error
cause: Failed to remove gcf1.conf source file after successful processing.
workaround: Verify file permissions and that file is not locked by another process.

061f00a0 : Error moving netstar file atomically

sev: Error
Type: System
args:
  • source file
  • destination file
cause: Failed to atomically move netstar configuration file to destination.
workaround: Verify file permissions, disk space, and that destination directory exists.

061f00a1 : Successfully processed netstar config file

sev: Info
Type: Transaction
args:
  • original
  • final
cause: N/A
workaround: N/A

061f00a2 : Extracting netstar zip file

sev: Info
Type: System
args:
  • zipPath
  • destDir
cause: N/A
workaround: N/A

061f00a3 : Failed to open zip file

sev: Error
Type: System
args:
  • zipPath
  • error
cause: Failed to open netstar database ZIP file for extraction.
workaround: Verify the ZIP file is not corrupted and has appropriate read permissions.

061f00a4 : Invalid database file pattern in zip

sev: Error
Type: System
args:
  • fileName
cause: Found a file in ZIP that does not match expected netstar database file name patterns.
workaround: Verify ZIP contains only files matching patterns: fcdb.now.*.map, fcdbsmall.now.*.map, or scdb.now.*.map.

061f00a5 : Unknown file type in zip

sev: Error
Type: System
args:
  • fileName
cause: Found a file in the netstar ZIP that does not match expected database file types.
workaround: Verify the ZIP file contains only fcdb, fcdbsmall, or scdb database files.

061f00a6 : Extracting file from zip

sev: Info
Type: System
args:
  • source
  • destination
cause: N/A
workaround: N/A

061f00a7 : Failed to open file in zip

sev: Error
Type: System
args:
  • fileName
  • error
cause: Failed to open a file within the netstar ZIP archive for reading.
workaround: Verify the ZIP archive is not corrupted.

061f00a8 : Failed to create extracted file

sev: Error
Type: System
args:
  • tempPath
  • error
cause: Failed to create temporary file for netstar database extraction.
workaround: Verify disk space and write permissions in the netstar destination directory.

061f00a9 : Failed to copy file content

sev: Error
Type: System
args:
  • fileName
  • error
cause: Failed to copy netstar database file contents from ZIP to temporary file.
workaround: Verify sufficient disk space and that the ZIP archive is not corrupted.

061f00aa : Failed to rename extracted file

sev: Error
Type: System
args:
  • tempPath
  • finalPath
  • error
cause: Failed to atomically rename extracted database file to final destination.
workaround: Verify file system supports atomic rename and has appropriate permissions.

061f00ab : Successfully extracted and renamed file

sev: Info
Type: System
args:
  • original
  • final
cause: N/A
workaround: N/A

061f00ac : meta.json already exists, overwriting with new mappings

sev: Info
Type: System
args:
  • path
cause: N/A
workaround: N/A

061f00ad : Failed to create meta.json file

sev: Error
Type: System
args:
  • path
  • error
cause: Failed to create meta.json file containing netstar database file mappings.
workaround: Verify write permissions and disk space in the netstar destination directory.

061f00ae : Failed to write to meta.json file

sev: Error
Type: System
args:
  • path
  • error
cause: Failed to write database file mappings to meta.json file.
workaround: Verify disk space and that the file is not locked or corrupted.

061f00af : Successfully created meta.json file

sev: Info
Type: System
args:
  • path
cause: N/A
workaround: N/A

061f00b0 : Error sending netstar grpc message

sev: Error
Type: Transaction
args:
  • message
cause: Failed to send gRPC message to TMM notifying of netstar database update.
workaround: Verify TMM is running, gRPC connection is available, and check TMM logs for errors.

061f00b1 : Successfully sent netstar database update notification

sev: Info
Type: Transaction
args:
  • message
cause: N/A
workaround: N/A

061f00b2 : Processing gcf1.conf file to update DB_PATH and other settings

sev: Info
Type: System
args:
  • srcFile
  • dstFile
cause: N/A
workaround: N/A

061f00b3 : Failed to open gcf1.conf source file

sev: Error
Type: System
args:
  • file
  • error
cause: Failed to open gcf1.conf source file for processing.
workaround: Verify the file exists and has appropriate read permissions.

061f00b4 : Failed to create gcf1.conf temp file

sev: Error
Type: System
args:
  • file
  • error
cause: Failed to create temporary gcf1.conf file for processing.
workaround: Verify write permissions and disk space in the netstar destination directory.

061f00b5 : Updated DB_PATH in gcf1.conf

sev: Info
Type: System
args:
  • original
  • modified
cause: N/A
workaround: N/A

061f00b6 : Updated TELEMETRY_ENABLE in gcf1.conf

sev: Info
Type: System
args:
  • original
  • modified
cause: N/A
workaround: N/A

061f00b7 : Updated TRACE_LOG_LEVEL in gcf1.conf

sev: Info
Type: System
args:
  • original
  • modified
cause: N/A
workaround: N/A

061f00b8 : Updated LIBRARY_LOG_LEVEL in gcf1.conf

sev: Info
Type: System
args:
  • original
  • modified
cause: N/A
workaround: N/A

061f00b9 : Updated IPDB_ENABLE in gcf1.conf

sev: Info
Type: System
args:
  • original
  • modified
cause: N/A
workaround: N/A

061f00ba : Failed to write line to gcf1.conf

sev: Error
Type: System
args:
  • error
cause: Failed to write a line to the gcf1.conf temporary file.
workaround: Verify sufficient disk space and that the file is not corrupted.

061f00bb : Error reading gcf1.conf file

sev: Error
Type: System
args:
  • error
cause: Error occurred while reading gcf1.conf file during processing.
workaround: Verify the file is not corrupted and has valid format.

061f00bc : Error flushing gcf1.conf file

sev: Error
Type: System
args:
  • error
cause: Failed to flush buffered data to gcf1.conf temporary file.
workaround: Verify sufficient disk space and that the file system is not full.

061f00bd : Failed to rename gcf1.conf temp file

sev: Error
Type: System
args:
  • tempPath
  • finalPath
  • error
cause: Failed to atomically rename processed gcf1.conf temporary file to final destination.
workaround: Verify file system supports atomic rename and has appropriate permissions.

061f00be : Successfully processed and updated gcf1.conf

sev: Info
Type: System
args:
  • file
  • modificationsCount
cause: N/A
workaround: N/A

061f00bf : No target settings found in gcf1.conf, file copied as-is

sev: Info
Type: System
args:
  • file
cause: N/A
workaround: N/A

061f00c0 : Failed to read urlcat DB directory

sev: Error
Type: System
args:
  • error
cause: Failed to read the Webroot URL database directory.
workaround: Verify the directory exists and has read permissions. Check filesystem health.

061f00c1 : Failed to delete

sev: Error
Type: System
args:
  • file
cause: Failed to delete old Webroot URL database file.
workaround: Verify file permissions and check if file is in use. Manually delete the file if necessary.

061f00c2 : Old DB file removed

sev: Info
Type: System
args:
  • file
cause: N/A
workaround: N/A

061f00c3 : Failed to copy

sev: Error
Type: System
args:
  • src file
  • dst file
  • error
cause: Failed to copy Webroot database file to temporary location.
workaround: Verify destination directory exists and has write permissions. Check disk space availability.

061f00c4 : Failed to rename

sev: Error
Type: System
args:
  • src file
  • dst file
  • error
cause: Failed to rename temporary file to final Webroot database location.
workaround: Verify destination directory permissions and check if destination file is in use. Verify filesystem health.

061f00c5 : Failed to remove

sev: Error
Type: System
args:
  • file
  • error
cause: Failed to remove source Webroot database file after successful copy.
workaround: Verify file permissions. Manually delete the file if necessary.

061f00c6 : Error in creating blob

sev: Error
Type: System
args:
  • directory
  • error
cause: Failed to create the Webroot database directory.
workaround: Verify parent directory exists and has write permissions. Check disk space and filesystem health.

061f00c7 : Created blob

sev: Info
Type: System
args:
  • directory
cause: N/A
workaround: N/A

061f00c8 : Attempting to move webroot

sev: Info
Type: System
args:
  • src file
  • dst file
cause: N/A
workaround: N/A

061f00c9 : Failed to move the file to webroot location

sev: Error
Type: System
args:
  • error
cause: Failed to move Webroot database file to the final location.
workaround: Check file permissions, disk space, and verify the file is not locked by another process.

061f00ca : Moved webroot

sev: Info
Type: System
args:
  • src file
  • dst file
cause: N/A
workaround: N/A

061f00cb : Error loading cert/key files

sev: Error
Type: Application
args:
  • error
cause: Failed to load TLS certificate and key pair from the specified file paths.
workaround: Verify the certificate and key files exist at the specified paths and are readable. Check file permissions and format.

061f00cc : Error reading root CA

sev: Error
Type: Application
args:
  • error
cause: Failed to read the root CA certificate file.
workaround: Verify the root CA file exists at the specified path and is readable. Check file permissions.

061f00cd : Error loading root CA

sev: Error
Type: Application
args:
  • error
cause: Failed to parse and load the root CA certificate from PEM format.
workaround: Verify the root CA file contains valid PEM-encoded certificate data. Check for file corruption.

061f00ce : Reloaded cert files

sev: Info
Type: Application
args: N/A
cause: N/A
workaround: N/A

061f00cf : Error creating new watcher for pipefile

sev: Emergency
Type: System
args:
  • error
cause: Failed to create a filesystem watcher for monitoring certificate file changes.
workaround: Check system resources and file descriptor limits. Verify fsnotify is properly installed.

061f00d0 : Received file watch

sev: Info
Type: System
args:
  • event name
  • event
cause: N/A
workaround: N/A

061f00d1 : File watch event

sev: Error
Type: System
args:
  • error
cause: Filesystem watcher encountered an error while monitoring certificate files.
workaround: Check filesystem health and permissions. Review system logs for underlying filesystem issues.

061f00d2 : Error adding watcher cert path for fsnotify

sev: Emergency
Type: System
args:
  • error
cause: Failed to add certificate file path to filesystem watcher.
workaround: Verify the certificate file path exists and is accessible. Check file permissions and filesystem health.

061f00d3 : Error adding watcher root CA path for fsnotify

sev: Emergency
Type: System
args:
  • error
cause: Failed to add root CA file path to filesystem watcher.
workaround: Verify the root CA file path exists and is accessible. Check file permissions and filesystem health.