How to Get Server Logs

Server logs are required for deployment, login, message, file service, database, and memory issues.

Common Symptoms

Multiple users are affected.
Services restart unexpectedly.
The admin console, messages, or file services fail.
Logs contain timeout, exception, or out-of-memory errors.

What to Check First

Failure time and affected service.
Server CPU, memory, disk, ports, and service status.
Recent deployment, upgrade, domain, HTTPS, or License changes.

Recommended Actions

Locate logs for the affected service.
Capture logs around the failure time.
Search for exceptions, timeout errors, and 'OutOfMemoryError'.
Package logs with screenshots and impact information before contacting support.

Common Server Log Paths

Use the actual deployment directory as the source of truth. For Docker deployments, also check container logs and mounted log directories.

Examples for Capturing Error Logs

bash

grep -i "error\|exception\|timeout\|OutOfMemoryError" -R ./logs

Out-of-Memory Keywords

'java.lang.OutOfMemoryError: Java heap space'
'java.lang.OutOfMemoryError: GC overhead limit exceeded'
'java.lang.OutOfMemoryError: Direct buffer memory'
'java.lang.OutOfMemoryError: unable to create new native thread'

When to Contact an Administrator or Operations Team

The issue affects multiple users or the whole company.
The fix requires restarting production services, replacing certificates, changing databases, changing file services, or updating License files.
Provide the failure time, impact scope, screenshots, account information, client version, server address, and related logs when reporting the issue.