AMPS Log Messages
📄️ How do I get more information on an AMPS error?
Learn how to use the `ampserr` command-line tool to get detailed information about AMPS error codes and messages.
📄️ How Can I Tell Where a Connection is Coming From?
Learn to differentiate between AMPS connection names and client names for troubleshooting connection origins.
📄️ Does AMPS log current process limits?
Learn how AMPS logs process limits using the `00-0032` info message for troubleshooting OS-enforced constraints.
📄️ What does it mean when AMPS has detected that it may not be running correctly?
Learn what AMPS message 30-0000 and error 01-0022 mean when the AMPS server detects potentially stuck or slow threads.
📄️ How can I keep only the last week of error logs?
Learn how to configure AMPS to automatically retain only the last week of error logs using scheduled file removal or log rotation.
📄️ What is the difference between "execution time" and "elapsed time" in the logs?
Clarifying the difference between "execution time" and "elapsed time" found in system logs for query processing.
📄️ What does a "potential stuck thread" message mean?
Understand what potential stuck thread messages (AMPS 30-0000) mean, common causes, and troubleshooting steps.
📄️ What does a "message cache is throttled" warning mean?
Explaining the "message cache is throttled" warning in AMPS, indicating resource exhaustion in the messaging pipeline.
📄️ What does "Replication has detected existing connection" mean? Why does AMPS close the connection?
AMPS closes a redundant connection when two instances establish a single optimized replication link, indicated by message 1E-0063.
📄️ Where is the list of all of the error messages in AMPS?
Learn how to use the `ampserr` utility with wildcards to list all AMPS error messages and categories.
📄️ 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 trace logs in AMPS using the `ExcludeErrors` configuration element.