re: this issue (osqueryd initialize failed: Could not open RocksDB) https://github.com/facebook/osquery/issues/1629 We’re seeing this behavior when our automated scripts restart the daemon after pulling down a new config. Basically the script does the following:

1. check for new config
2. if config updated, download new config
3. osqueryctl stop
4. install new config
5. osqueryctl start

If we don’t add a sleep statement between steps 4 and 5, we occasionally see this error pop up. Is there a best practice to avoid having this happen? sleeping seems kinda janky 😕