Troubleshooting

Listed in this section are some scenarios that are known to cause issues.

Out of Memory

If you ever face OutOfMemory errors of the Java daemon (you will find them in the gw-debug.err file),

you are likely using a high level of concurrency through internal concurrent_threads parameter and/or parallel jobs.

To overcome this situation you can:

1. Reduce concurrent_threads parameter

2. Reduce the number of jobs running in parallel

3. If you cannot do that you should increase JVM memory.

To increase JVM memory, you will need to:

Create a this file: ‘/opt/bacula/etc/gw_backend.conf’.

Below, an example of the contents: GW_JVM_MIN=2G GW_JVM_MAX=8G

Those values will define the MIN (GW_JVM_MIN) and MAX (GW_JVM_MAX) memory values assigned to the JVM Heap size. In this example we are setting 2Gb for the minimum, and 8Gb for the maximum. In general, those values should be more than enough. Please, be careful if you are running jobs in parallel, as very big values and several jobs at a time could quickly eat all the memory of your host.

The ‘/opt/bacula/etc/gw_backend.conf’ won’t be modified through package upgrades, so your memory settings will be persistent.

Go back to the Google Workspace Plugin article.