Table 'librenms.history_store' doesn't exist

Having issues logging in and/or creating new users after doing a validate and following the validate schema update instructions.
Now when logging out/in or creating a new user I am getting “Unhandled MySQL Error [42S02] SQLSTATE[42S02]: Base table or view not found: 1146 Table ‘librenms.history_store’ doesn’t exist”
Which was the table that I was instructed by validate.php to drop. I’m not sure what is going on with it, but from the looks of it, it may have been a false positive and looks like it is needed???
I was trying to recreate the history_store table from a very old backup, but it doesn’t like it.

If this table is indeed needed, can someone post for me the sql export to re-create this table?


That’s not one of our tables so I assume you’ve modified some code somewhere that you’ve added.

I have defiantly not modified any code. The only thing outside of the normal base install would have been adding Oxidized and Weathermap. Otherwise it was just running on its own for the past + year.

Here are a few data rows from the table…
2018-12-11 09:02:47;"applications";"<app_id>16</app_id>";"<app_id>16</app_id>";2
2018-12-11 09:14:50;"bgpPeers";"<bgpPeer_id>1</bgpPeer_id>";"<bgpPeer_id>1</bgpPeer_id>";2
2018-12-11 09:37:06;"devices";"<device_id>201</device_id>";"<device_id>201</device_id>";2
2018-12-10 15:17:35;"device_perf";"<id>48349392</id>";"<id>48349392</id>";1
2018-12-10 15:17:44;"eventlog";"<event_id>4712368</event_id>";"<event_id>4712368</event_id>";1
2018-12-11 09:18:51;"mempools";"<mempool_id>45</mempool_id>";"<mempool_id>45</mempool_id>";2
2018-12-10 15:19:12;"notifications_attribs";"<attrib_id>275</attrib_id>";"<attrib_id>275</attrib_id>";1
2018-12-10 15:17:36;"perf_times";"<id>49698769</id>";"<id>49698769</id>";1
2018-12-11 10:16:49;"pollers";"<id>3</id>";"<id>3</id>";2
2018-12-11 09:34:36;"ports";"<port_id>1996</port_id>";"<port_id>1996</port_id>";2
2018-12-11 09:34:50;"ports_statistics";"<port_id>1996</port_id>";"<port_id>1996</port_id>";2
2018-12-11 11:19:58;"ports_stp";"<port_stp_id>547</port_stp_id>";"<port_stp_id>547</port_stp_id>";2
2018-12-11 12:21:51;"processors";"<processor_id>1110</processor_id>";"<processor_id>1110</processor_id>";2
2018-12-11 12:19:37;"sensors";"<sensor_id>3227</sensor_id>";"<sensor_id>3227</sensor_id>";2
2018-12-11 13:40:53;"services";"<service_id>12</service_id>";"<service_id>12</service_id>";2
2018-12-11 09:19:00;"storage";"<storage_id>280</storage_id>";"<storage_id>280</storage_id>";2
2018-12-11 11:32:38;"stp";"<stp_id>92</stp_id>";"<stp_id>92</stp_id>";2

Like I mentioned above - defiantly nothing I directly would have messed with.

Thanks for looking.

I think I found the answer - there was an attempt to replicate the librenms data to another db server, and the tool that was being used created numerous triggers that tracked the sync process. Needless to say, that made quite the mess and I am working on cleaning up the artifacts now.

Thanks for looking laf - you were 100% correct!

1 Like