User avatar
johan
GpsGate
Posts: 14913
Joined: Wed Aug 04, 2004 10:40 pm
Location: Sweden
Contact: Website

FIX: GpsGate crash at midnight

Tue Jul 26, 2011 4:21 pm

FIX: GpsGate crash at midnight / MySQL memory problems.

SYMPTOM

GpsGate Server crash when processing reports. You typically get errors like those in the ErrorLog

System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

System.InvalidOperationException: ERROR - unable to allocate an environment handle.

CAUSE

innodb_additional_mem_pool_size in my.ini is probably set to a too low value.

SOLUTION

MySQL my.ini parameters, you find my.ini where you installed MySQL.

# Set this parameter to minimum of 32M
# Smaller values will crash a busy GpsGate Server
innodb_additional_mem_pool_size=32M

# Set this parameter to minimum of 64M
# Smaller values will crash a busy GpsGate Server
innodb_log_buffer_size=64M


# Set to value about half the free memory you have on your server.
# As an example it is set to 1024 MB = 1 GB here
innodb_buffer_pool_size=1024M

Always backup my.ini before making any changes

After making a change in my.ini you need to restart the MySQL service for changes to take effect

If your server is running out of memory, please add more RAM.

Regards,
Johan

GpsGate Support

Return to “GpsGate Server - How to setup and use”