# Historian Core Not Logging After JVM SIGKILL Event **URL:** \ **Category:** Ignition\ **Tags:** ignition83\ **Created:** [October 15, 2025, 1:27pm UTC](https://forum.inductiveautomation.com/t/historian-core-not-logging-after-jvm-sigkill-event/111469 "2025-10-15T13:27:03Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![DNice](https://avatars.discourse-cdn.com/v4/letter/d/858c86/32.png) [@DNice](https://forum.inductiveautomation.com/u/DNice)\ **Post date:** [October 15, 2025, 1:27pm UTC](https://forum.inductiveautomation.com/t/historian-core-not-logging-after-jvm-sigkill-event/111469/1 "2025-10-15T13:27:03Z")
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? ---
**Author:** ![hayden.watson](https://avatars.discourse-cdn.com/v4/letter/h/77aa72/32.png) [@hayden.watson](https://forum.inductiveautomation.com/u/hayden.watson)\ **Post date:** [October 15, 2025, 1:36pm UTC](https://forum.inductiveautomation.com/t/historian-core-not-logging-after-jvm-sigkill-event/111469/2 "2025-10-15T13:36:27Z")
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 ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [October 15, 2025, 1:40pm UTC](https://forum.inductiveautomation.com/t/historian-core-not-logging-after-jvm-sigkill-event/111469/3 "2025-10-15T13:40:59Z")
> [@hayden.watson](#): > > restarting the module Ignition v8.3 doesn't have module restart. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [October 15, 2025, 1:41pm UTC](https://forum.inductiveautomation.com/t/historian-core-not-logging-after-jvm-sigkill-event/111469/4 "2025-10-15T13:41:57Z")
> [@DNice](#): > > How does one recover from something like this? I haven't seen any reports like yours. You should open a support ticket. I expect IA will be very interested. ---
**Author:** ![DNice](https://avatars.discourse-cdn.com/v4/letter/d/858c86/32.png) [@DNice](https://forum.inductiveautomation.com/u/DNice)\ **Post date:** [October 15, 2025, 1:47pm UTC](https://forum.inductiveautomation.com/t/historian-core-not-logging-after-jvm-sigkill-event/111469/5 "2025-10-15T13:47:47Z")
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 ☹. ---
**Author:** ![Kurt.Larson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kurt.larson/32/6426_2.png) [@Kurt.Larson](https://forum.inductiveautomation.com/u/Kurt.Larson)\ **Post date:** [October 20, 2025, 5:19pm UTC](https://forum.inductiveautomation.com/t/historian-core-not-logging-after-jvm-sigkill-event/111469/6 "2025-10-20T17:19:12Z")
> 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. ---
**Author:** ![Kurt.Larson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kurt.larson/32/6426_2.png) [@Kurt.Larson](https://forum.inductiveautomation.com/u/Kurt.Larson)\ **Post date:** [October 20, 2025, 6:27pm UTC](https://forum.inductiveautomation.com/t/historian-core-not-logging-after-jvm-sigkill-event/111469/7 "2025-10-20T18:27:18Z")
Actually, I found it. I'll be following up with the current Support Engineer assigned to your case. Thanks. ---
**Author:** ![DNice](https://avatars.discourse-cdn.com/v4/letter/d/858c86/32.png) [@DNice](https://forum.inductiveautomation.com/u/DNice)\ **Post date:** [October 21, 2025, 11:36am UTC](https://forum.inductiveautomation.com/t/historian-core-not-logging-after-jvm-sigkill-event/111469/8 "2025-10-21T11:36:04Z")
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.