![]() ![]() The rocksdb table holding the device identifier is not compressed with Snappy, hence the identifier could be recovered before trashing the DB. I'm wondering whether we could just enable WITH_SNAPPY and link to the arch provided library - although I know you want the package to be more based on the default osquery setting.Īnother idea would be submitting a patch for the scenario to osquery. To get it fixed we'd need to add Snappy to the osquery deps. My suspicion is that previously with linked libraries we were using rocksdb 6.23 with enabled Snappy support (see ) and now we're back at 6.14 that does not contain Snappy. I can also create a separate ticket for this, if you've an idea whether it's an upstream or packaging issue. ![]() With this a new DB is created and yields new host identifiers => duplicated hosts in fleet. Locate the file on your hard drive and use the rpm. Substitute the name of the file in our example with the name of the one you download. Okt 01 09:16:03 xps13 osqueryd: W1001 09:16:03.990839 40300 rocksdb.cpp:256] Destroying RocksDB database due to corruption Change directory to the Downloads directory and then use dpkg command to install the. Okt 01 09:11:32 xps13 osqueryd: I1001 09:11:32.587396 40300 rocksdb.cpp:165] Cannot compact column family queries: Corruption: Unsupported compression method or corrupted compressed block contents: SnappyĪfter the next restart I get the following: Let us teach you just how simple it could be to keep your 3rd party applications updated. Okt 01 09:11:32 xps13 osqueryd: I1001 09:11:32.587299 40300 rocksdb.cpp:67] RocksDB: Compaction error: Corruption: Unsupported compression method or corrupted compressed block contents: Snappy At Chocolatey Software we strive for simple, and teaching others. I get another error now where I am unsure whether it's coming from the switch to 5.0, from removing some patches or just corruption of the DB on my side: ![]()
0 Comments
Leave a Reply. |