Troubleshooting

From ARSWiki

1 Startup Problems
- 1.1 Creating Startup Logs
2 Undocumented ar.conf Settings
- 2.1 Large-Result-Logging-Threshold
  - 2.1.1 Examples
3 Email Engine
- 3.1 Debug Logging

Startup Problems

This section covers various methods to troubleshoot a server that will not start.

Creating Startup Logs

ARServer has an undocumented flag, -t, that can be used to generate a startup log. To utilize this flag, update armonitor.conf/armonitor.cfg so that the line that addresses arserverd/arserver.exe passes -t.

Unix/Linux armonitor.conf Example

Windows armonitor.cfg Example

Notes:

The examples contain a single line from armonitor.conf/cfg but has been broken into multiple lines for presentation.

Before

"C:\Program Files\AR System\xxx\arserver.exe" 
-i "C:\Program Files\AR System\xxx" 
-l "C:\Program Files\Common Files\AR System\Licenses\xxx" 
-m

After

"C:\Program Files\AR System\xxx\arserver.exe" 
-i "C:\Program Files\AR System\xxx" 
-l "C:\Program Files\Common Files\AR System\Licenses\xxx" 
-m 
-t

Sample Log File

Undocumented ar.conf Settings

Large-Result-Logging-Threshold

Enables loggging for large memory allocations due to large queries using GLEWF.

Examples

Large-Result-Logging-Threshold: 50000

/* Tue Jul 01 2003 13:03:55.6420 */ Thread Id 2352 (GLEWF) large result - /
Entries: 1000/Overflow memory: 88143/Pending file size: 73895/
RPC ID: 0/User: Demo/Form: xxx/

Large-Result-Logging-Threshold: 75000

/* Tue Jul 01 2003 13:05:30.0770 */ Thread Id 1844 (GLEWF) large result - /
Entries: 1000/Overflow memory: 88143/Pending file size: 73895/
RPC ID: 0/User: Demo/Form: xxx/

Large-Result-Logging-Threshold: 88143

/* Tue Jul 01 2003 13:19:23.4860 */ Thread Id 2308 (GLEWF) large result - /
Entries: 1000/Overflow memory: 88143/Pending file size: 73895/
RPC ID: 0/User: Demo/Form: xxx/