AMPS Log Messages

📄️ How do I get more information on an AMPS error?

Learn how to use the `ampserr` command-line tool to find detailed information about AMPS error codes and messages.

📄️ How Can I Tell Where a Connection is Coming From?

Learn how to distinguish between AMPS connection names and client names to trace incoming network connections.

📄️ Does AMPS log current process limits?

Learn how AMPS logs current process limits, specifically via the '00-0032' info message, useful for troubleshooting OS limits.

📄️ What does it mean when AMPS has detected that it may not be running correctly?

Learn what AMPS error codes 30-0000 and 01-0022 mean when threads fail to report progress, potentially indicating stuck threads or resource issues.

📄️ How can I keep only the last week of error logs?

Learn two methods to configure AMPS to automatically retain only the last week of error logs using scheduled actions or log rotation.

📄️ What is the difference between "execution time" and "elapsed time" in the logs?

Clarifies the distinction between "execution time" and "elapsed time" in AMPS query logs, noting elapsed time includes parallel processing overhead.

📄️ What does a "potential stuck thread" message mean?

Understand what a potential stuck thread message (AMPS error 30-0000) means and how to troubleshoot resource contention or slow operations in AMPS.

📄️ What does a "message cache is throttled" warning mean?

Explains the "message cache is throttled" warning in AMPS, indicating resource exhaustion in the message processing pipeline.

📄️ What does "Replication has detected existing connection" mean? Why does AMPS close the connection?

Explains the non-error message "Replication has detected existing connection" (1E-0063) in AMPS replication and why the connection closes.

📄️ Where is the list of all of the error messages in AMPS?

Learn how to use the `ampserr` utility with wildcards to retrieve all AMPS error messages.

📄️ What can cause an "unknown command received" or "parse format error"?

Troubleshoot "unknown command received" or "parse format error" in AMPS caused by protocol mismatch between client and transport configuration.

📄️ How do I exclude passwords in trace logging?

Learn how to exclude sensitive passwords from Docusaurus trace logging using the `ExcludeErrors` configuration element.