Historian Core Not Logging After JVM SIGKILL Event

Ignition
1

I recently had a GW restart even caused by a JVM received a signal SIGKILL (9). command that permanently killed the ability my instance of Historian Core to log data. The archive of data is still accessible via trends/queries but nothing new is logged.

I resolved the root cause (added more CPU and removed some inefficiencies) and I was able to get a Historian Core working again only by setting up another Historian Core instance with a new name.

How does one recover from something like this? Is there a way yet to combine Historian Core archives or migrate one data archive to another?

2

Restarting the gateway should work, though obviously not ideal.

I wonder if restarting the module on the config/modules page on the gateway would restart the relevant services though

3

Ignition v8.3 doesn't have module restart.

4

I haven't seen any reports like yours. You should open a support ticket. I expect IA will be very interested.

5

I have a ticket open, I will update if there is any resolution with support.

I tried restarting the whole GW, enabled/disabled the Historian Core instance, recreating tags, etc with no luck. The only thing that allowed data logging to Historian Core again was making a new instance :frowning:.

1 Like
6

I have a ticket open, I will update if there is any resolution with support.

@DNice I'm looking into this. Can you tell me what your support ticket number is? Thanks.

7

Actually, I found it. I'll be following up with the current Support Engineer assigned to your case. Thanks.

8

Thank you for the followup.

I could not get my original Core Historian working again but one log error that was of interest was: ALTER TABLE historiancore_archive.datapoints FORCE DROP PARTITION LIST '2025-10-13T153831-850001'. I tried executing this against my QuestDB connection but im not sure anything happened since we dont have read/write access.