Mideye Logs: Debug & Interpretation

Logs are the most important diagnostic tool for troubleshooting Mideye Server. This guide explains how to read, interpret, and use log files effectively.

Overview

Mideye Server generates several types of logs:

• Application logs — Main server operations and errors
• Authentication logs — User authentication attempts (viewable in web interface)
• Audit logs — Administrative actions (viewable in web interface)
• System service logs — Service management logs (OS-level)
• Database logs — Database server logs (external)

Viewing Logs in the Web Interface

The recommended way to view logs is through the web administration interface:

1. Navigate to Log Files
2. Select log file from dropdown
3. Use Follow mode for real-time viewing
4. Use the Search function to find specific entries

For authentication-specific issues:

• Authentication Logs — Shows all user authentication attempts with details
• Audit Logs — Shows administrator actions and configuration changes

Log File Locations

Linux

Log File	Location	Purpose
Main Application Log	/opt/mideyeserver6/log/mideyeserver.log	All application events
Error Log	/opt/mideyeserver6/log/mideyeserver.error	Error-level messages only
Archived Logs	/opt/mideyeserver6/log/old/	Rotated logs
System Service Logs	journalctl -u mideyeserver6	Service startup/stop

Windows

Log File	Location	Purpose
Main Application Log	C:\Program Files\Mideye Server\log\mideyeserver.log	All application events
Error Log	C:\Program Files\Mideye Server\log\mideyeserver.error	Error-level messages only
Windows Event Log	Event Viewer → Application	Service startup/stop

Viewing Logs from the Command Line

Linux:

# Tail main log
tail -f /opt/mideyeserver6/log/mideyeserver.log

# View error log
tail -f /opt/mideyeserver6/log/mideyeserver.error

# View system service logs
journalctl -u mideyeserver6 -f

# View recent startup
journalctl -u mideyeserver6 --since "10 minutes ago"

Windows (PowerShell):

# Tail main log
Get-Content "C:\Program Files\Mideye Server\log\mideyeserver.log" -Wait

# View last 100 lines
Get-Content "C:\Program Files\Mideye Server\log\mideyeserver.log" -Tail 100

# Search for errors
Select-String -Path "C:\Program Files\Mideye Server\log\mideyeserver.log" -Pattern "ERROR"

---

Log Levels

Mideye Server uses standard logging levels:

Level	Usage	What to Look For
ERROR	Critical failures	Service failures, data loss, unrecoverable errors
WARN	Problems that might cause issues	Connection failures, timeouts, degraded functionality
INFO	Normal operations	Startup, shutdown, configuration changes, successful operations
DEBUG	Detailed troubleshooting	Detailed decision flows and operations
TRACE	Very detailed debugging	Full request/response details

Default Level: INFO

Changing Log Level:

Edit the logging configuration in the application configuration file to increase verbosity for specific components. Restart the service to apply changes.

---

Common Log Patterns

Authentication Failures

Pattern: User authentication failed

WARN  - Authentication failed for user [username]: Invalid password

Action:

• Check Authentication Logs in web interface
• Verify user account status
• Check password policy
• Look for repeated failures (possible brute force)

---

LDAP Connection Failures

Pattern: Cannot connect to LDAP

WARN  - Failed to connect to LDAP profile: [ProfileName] with error: [Connection timed out]

Action:

• Test LDAP connectivity (see commands below)
• Check firewall rules
• Verify LDAP server is running
• See LDAP Connection Issues

---

Database Connection Failures

Pattern: Database connectivity problem

ERROR - Exception during pool initialization
ERROR - Communications link failure

Action:

• Verify database is running
• Test database connection
• Check credentials in configuration
• See Database Issues

---

Phone Number Validation Failures

Pattern: Invalid phone number format

WARN  - Phone or token number is invalid or missing

Action:

• Check phone number format in directory (LDAP/AD)
• Remove hidden characters
• Ensure international format: +[country][number]
• See Phone Number Issues

---

MAS Magic Link Failures

Pattern: Cannot load magic link URL

WARN  - Failed to get magic link frontend URL from: [https://mas.mideyecloud.se/...]
INFO  - frontEndBaseUrl: [null]

Action:

• Test MAS connectivity: curl -v https://mas.mideyecloud.se
• Check proxy configuration
• Wait for retry (10 minutes) or restart service
• See External Service Issues

---

Switch Connection Failures

Pattern: Cannot reach Mideye Switch

WARN  - Failed to connect to primary switch: [Connection refused]
INFO  - Trying secondary switch

Action:

• Test Switch connectivity: nc -zv primary.mideye.com 20460
• Check for SSL proxy interception (verify certificate with openssl s_client)
• Check firewall and proxy settings
• See External Service Issues

---

Certificate Errors

Pattern: SSL/TLS certificate issues

ERROR - Failed to initialize SSL context from keystore
ERROR - SSL handshake failed

Action:

• Use the Certificate Management page to verify certificates
• Check certificate expiration
• See Certificate Issues

---

Database Migration Issues

Pattern: Database migration problems

INFO  - Waiting for changelog lock....
ERROR - Validation Failed: ...

Action:

• Check for stuck migrations: SELECT * FROM DATABASECHANGELOGLOCK;
• Release lock if stuck: UPDATE DATABASECHANGELOGLOCK SET LOCKED=0;
• See Database Issues

---

Error Code Reference

Common error codes found in logs:

Code	Description	See Also
11002	Invalid phone number format	Phone Number Issues
19002	Approver has no phone number	Phone Number Issues
19003	Approver phone number invalid format	Phone Number Issues
503	LDAP connection failed (HTTP response)	LDAP Connection Issues

---

Log Searching Techniques

Search for Specific User

Linux:

grep "username" /opt/mideyeserver6/log/mideyeserver.log

# With context lines
grep -C 5 "username" /opt/mideyeserver6/log/mideyeserver.log

Windows:

Select-String -Path "C:\Program Files\Mideye Server\log\mideyeserver.log" -Pattern "username" -Context 5

Search by Time Range

Linux:

# Logs from specific time range
awk '/2026-02-19 10:30/,/2026-02-19 11:00/' /opt/mideyeserver6/log/mideyeserver.log

Find Connection Issues

Linux:

# All connection problems
grep -iE "connection.*fail|connection.*refused|connection.*timeout" \
  /opt/mideyeserver6/log/mideyeserver.log

# LDAP connection issues
grep -i "ldap.*fail" /opt/mideyeserver6/log/mideyeserver.log

# Switch connection issues
grep -i "switch" /opt/mideyeserver6/log/mideyeserver.log

Windows:

# All connection problems
Select-String -Path "C:\Program Files\Mideye Server\log\mideyeserver.log" -Pattern "connection.*fail|timeout"

# Switch issues
Select-String -Path "C:\Program Files\Mideye Server\log\mideyeserver.log" -Pattern "switch"

Count Errors by Type

Linux:

grep -i error /opt/mideyeserver6/log/mideyeserver.log | \
  awk '{for(i=1;i<=NF;i++) if($i ~ /error/i) print $(i+2)}' | sort | uniq -c | sort -rn

---

Log Rotation

Log files are automatically rotated:

• Daily rotation — New log file each day
• Default retention — 30 days of logs
• Archived to — old/ subdirectory within the log folder

Viewing Archived Logs

Linux:

ls -lh /opt/mideyeserver6/log/old/
less /opt/mideyeserver6/log/old/mideyeserver.2026-02-18.log

Windows:

Get-ChildItem "C:\Program Files\Mideye Server\log\old\"

---

Collecting Logs for Support

Using the Web Interface (Recommended)

1. Navigate to Log Files
2. Select the relevant log file
3. Use the download or export function
4. Include the time range covering the issue

Using the Command Line

Linux:

# Collect recent logs
tail -1000 /opt/mideyeserver6/log/mideyeserver.log > /tmp/mideye-logs.txt
journalctl -u mideyeserver6 --since "1 hour ago" > /tmp/mideye-systemd.txt

Windows:

# Collect recent logs
Get-Content "C:\Program Files\Mideye Server\log\mideyeserver.log" -Tail 1000 | Out-File C:\temp\mideye-logs.txt

What to Include for Support

1. Application logs — Recent entries showing the problem
2. Error logs — If error-specific log exists
3. System service logs — Service startup/failure events
4. Configuration — Sanitized config files (remove passwords)
5. Screenshots — Of the web interface showing the issue

Always sanitize passwords and sensitive data before sharing logs!

Remove: database passwords, LDAP passwords, shared secrets, API keys, certificate passwords.

---

Real-Time Monitoring

Watch for Specific Events

Linux:

# Monitor authentication failures
tail -f /opt/mideyeserver6/log/mideyeserver.log | grep -i "authentication.*fail"

# Monitor external service connections
tail -f /opt/mideyeserver6/log/mideyeserver.log | grep -iE "switch|mas|shield"

# Monitor errors only
tail -f /opt/mideyeserver6/log/mideyeserver.log | grep -i error

Windows:

# Monitor errors
Get-Content "C:\Program Files\Mideye Server\log\mideyeserver.log" -Wait | Select-String "ERROR"

---

Getting Help

When contacting support with log-related questions:

1. Specify time range — Exact timestamps of problem occurrence
2. Include context — What was being done when problem happened
3. Provide full error messages — Include surrounding log lines
4. Sanitize sensitive data — Remove passwords, secrets, PII
5. Note frequency — Is it one-time or recurring?
6. Include environment info — OS version, database type