Started having errors today, with all Tags not writing. The console is full of the following:

Time Logger Message 10:34:45 AM com.inductiveautomation.ignition.gateway.localdb.LocalDBManagerImpl Cannot create autobackup for internal database "settings".
java.sql.SQLException: java.lang.OutOfMemoryError
at org.hsqldb.jdbc.Util.sqlException(Util.java:392)
at org.hsqldb.jdbc.Util.sqlException(Util.java:227)
at org.hsqldb.jdbc.JDBCStatement.fetchResult(JDBCStatement.java:1830)
at org.hsqldb.jdbc.JDBCStatement.executeUpdate(JDBCStatement.java:207)
at org.apache.commons.dbcp.DelegatingStatement.executeUpdate(DelegatingStatement.java:228)
at com.inductiveautomation.ignition.gateway.localdb.hsql.HSQLDBManager$AutoBackupDaemon.run(HSQLDBManager.java:619)
at com.inductiveautomation.ignition.common.execution.impl.BasicExecutionEngine$TrackedTask.run(BasicExecutionEngine.java:573)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: org.hsqldb.HsqlException: java.lang.OutOfMemoryError
at org.hsqldb.error.Error.error(Error.java:111)
at org.hsqldb.result.Result.newErrorResult(Result.java:1057)
at org.hsqldb.StatementCommand.execute(StatementCommand.java:208)
at org.hsqldb.Session.executeCompiledStatement(Session.java:1339)
at org.hsqldb.Session.executeDirectStatement(Session.java:1216)
at org.hsqldb.Session.execute(Session.java:1002)
at org.hsqldb.jdbc.JDBCStatement.fetchResult(JDBCStatement.java:1822)
... 13 more
Caused by: java.lang.OutOfMemoryError
at java.util.zip.Deflater.deflateBytes(Native Method)
at java.util.zip.Deflater.deflate(Unknown Source)
at java.util.zip.DeflaterOutputStream.deflate(Unknown Source)
at java.util.zip.DeflaterOutputStream.write(Unknown Source)
at java.util.zip.GZIPOutputStream.write(Unknown Source)
at org.hsqldb.lib.tar.TarFileOutputStream.write(TarFileOutputStream.java:199)
at org.hsqldb.lib.tar.TarFileOutputStream.writeBlock(TarFileOutputStream.java:225)
at org.hsqldb.lib.tar.TarGenerator$TarEntrySupplicant.write(TarGenerator.java:632)
at org.hsqldb.lib.tar.TarGenerator.write(TarGenerator.java:232)
at org.hsqldb.lib.tar.DbBackup.write(DbBackup.java:299)
at org.hsqldb.persist.Logger.backup(Logger.java:1884)
at org.hsqldb.StatementCommand.getResult(StatementCommand.java:279)
at org.hsqldb.StatementCommand.execute(StatementCommand.java:206)
... 17 more
(I) 10:34:44 AM hsqldb.db.HSQLDB2AF197DF72.ENGINE Initiating backup of instance 'settings' (I) 10:34:44 AM hsqldb.db.HSQLDB2AF197DF72.ENGINE dataFileCache commit start (I) 10:34:44 AM com.inductiveautomation.ignition.gateway.localdb.LocalDBManagerImpl Creating auto-backup of internal database "settings"... 10:32:44 AM com.inductiveautomation.ignition.gateway.localdb.LocalDBManagerImpl Cannot create autobackup for internal database "settings".

Any ideas?

You're out of memory! Further investigation to figure out why will be necessary... Can you attach or email us your logs?

Here is the export of the logs:

What version of Ignition are you running? The OPC-COM module may have had a memory leak that was just recently fixed. Upgrading to the latest would probably be a good idea.

Also, I didn't see that error you posted anywhere in the logs...

Current Version: 7.3.3 (b570)

Strange thing about the log file ... attached is a new export and a screen shot of the logs.

Also including a screen shot of the task manager showing java using 1.8 Gs of memory!

Well it's not that strange to be showing 1.8GB because you ran out of memory.

Upgrade to 7.3.7 and if the leak was on the COM module you should be all set.

Thanks Kevin, I see version 7.4.2 is the latest. Since we have Total Care upgrade protection, we will upgrade to that level.

Ah, I didn't realize that. Yes, upgrading to 7.4.2 is a great idea