-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Persistent store error #22
Comments
I just did some more tests, it looks like this happens when i power cycle the pi (without proper shutdown) `2018-05-03 12:40:00: ######################################################### 2018-05-03 12:40:00: Starting the ZTP Service ● ztp.service - FreeZTP Service May 03 12:39:59 raspberrypi bash[367]: fulldb = self._pull_full_db() # Pull a full copy of the db |
Strange. Looks like something got corrupted in the db. Try deleting the db |
Done and all good, it does it every time the pi is not shutdown properly. Also, new one after after provisioning first batch. 2018-05-03 14:41:01: persistent_store: ERROR: Error in reading from store file 2018-05-03 14:41:01: persistent_store: ERROR: Extra data: line 237 column 2 - line 249 column 2 (char 7879 - 8208) 2018-05-03 14:41:01: persistent_store: ERROR: Error in reading from store file 2018-05-03 14:41:01: persistent_store: ERROR: Extra data: line 237 column 2 - line 249 column 2 (char 7879 - 8208) 2018-05-03 14:41:01: persistent_store: ERROR: Error in reading from store file 2018-05-03 14:41:01: persistent_store: ERROR: Extra data: line 237 column 2 - line 249 column 2 (char 7879 - 8208) Will do some more tshooting.. |
Can you attach a sanitized copy of the pdb file here? |
And did the provisioning work OK? |
Already removed unfortunately. Will grab one if it happens again. I added 6 switches then another 4 after 5 minutes. The first batch did the upgrade, however, only 2 took the cfg, while the other did not (I am checking whether the hostname has changed to confirm the sw has been installed) the other 4 did not upgrade. Will keep you posted. |
Ok, patched 8 together, 5 in json then same issue. It did push the new io to all of them though, just not all got the cfg. Json file attached. |
yea I can see towards the bottom where the JSON file got screwed up. So what happens when they don't get their configs? Is it because the ZTP server crashes in the middle of provisioning? |
Not sure! Will do some more testing tomorrow and keep you posted. Luca |
Ran into the same thing today, everything was working fine and started seeing the following when running
I'm wondering if we hit some kind of line/size limit. Anyways, resolved by backing up the pdb file and restarting ztp services. mv /etc/ztp/pdb /etc/ztp/pdb.bak
ztp services restart @PackeTsar, let me know if you want the pdb file for review. |
I have seen recurring reports of this issue. It may be related to how I am writing data to that file. Thinking that it may get corrupted due to multiple concurrent writes. I will look into this. |
Tracking this. Closing. |
Hello,
I am getting this error when I try to show provisioning
2018-05-02 10:30:44: persistent_store: ERROR: Error in reading from store file
2018-05-02 10:30:44: persistent_store: ERROR: No JSON object could be decoded
I only changed DHCP scope, other than that cfg is default.
Cheers,
Luca
The text was updated successfully, but these errors were encountered: