Lost models/GCODE files after updating to 80

tonyallen28

After upgrading to 80 I had no models listed under my printer. I looked in the printer/models/ directory and they were all still there however. Anyway to get the server to reload all the models? Its over 1000 models so having to upload them again would be very time consuming.

Repetier

Well that are a lot of models. After upgrading server starts to recompute timings, so that would take a while!

Apart from this it is nothing more then a restart of the server and we never found out why this is sometimes a problem.

You need to find the file which is corrupted and causes the fail. They are all in your printer directory <data_root>/printer/<yourname>

In data is a file modelGroups.json. You can upload it to http://jsonlint.com/# to test if it was corrupted.

If your log/server.log contains

Handling action 'listModels' caused error Not found

one of your .gin files is defect. Since you do now know which, just delete all and restart server. They then get rebuild on next start also that can take a while. Since this was done after upgrade I guess that it is what happens. Since I just figured out this can happen, I will add a fix in next release that will just recreate the defect .gin file for next release.

tonyallen28

Thanks repeiter I did have "Handling action 'listModels' caused error Not found" in my logs so I deleted all .gin files and let the server rebuild them. I think the server tried to rebuild all at once though here is a short clip from the server log:

<div>2016-10-30 11:50:23: Updating info for /var/lib/Repetier-Server/printer/WhitePrinter/models/00002165_Elf Girl-2.g printer WhitePrinter

2016-10-30 11:50:23: Updating info for /var/lib/Repetier-Server/printer/WhitePrinter/models/00002168_Chubby Gingerboy-3.g printer WhitePrinter

2016-10-30 11:50:23: Updating info for /var/lib/Repetier-Server/printer/WhitePrinter/models/00002169_Chubby Cardinal-4.g printer WhitePrinter

2016-10-30 11:50:23: Updating info for /var/lib/Repetier-Server/printer/WhitePrinter/models/00002170_Nutcracker-2.g printer WhitePrinter

2016-10-30 11:50:23: Updating info for /var/lib/Repetier-Server/printer/WhitePrinter/models/00002167_Santa Baby Lettering-2.g printer WhitePrinter

2016-10-30 11:50:23: Updating info for /var/lib/Repetier-Server/printer/WhitePrinter/models/00002171_25 December-2.g printer WhitePrinter

2016-10-30 11:50:23: Updating info for /var/lib/Repetier-Server/printer/WhitePrinter/models/00002172_Hanging Stocking-2.g printer WhitePrinter

2016-10-30 11:50:23: Updating info for /var/lib/Repetier-Server/printer/WhitePrinter/models/00002173_Whispy Tree-2.g printer WhitePrinter

2016-10-30 11:50:23: Updating info for /var/lib/Repetier-Server/printer/WhitePrinter/models/00002174_HoHo 1-2.g printer WhitePrinter

2016-10-30 11:50:23: Updating info for /var/lib/Repetier-Server/printer/WhitePrinter/models/00002175_Chubby Gingergirl-3.g printer WhitePrinter

2016-10-30 11:50:26: Updating info for /var/lib/Repetier-Server/printer/WhitePrinter/models/00002181_Nutcracker-3.g printer WhitePrinter

2016-10-30 11:50:26: Updating info for /var/lib/Repetier-Server/printer/WhitePrinter/models/00002176_Elf Girl-3.g printer WhitePrinter

2016-10-30 11:50:26: Updating info for /var/lib/Repetier-Server/printer/WhitePrinter/models/00002177_Mrs Claus-3.g printer WhitePrinter

2016-10-30 11:50:26: Updating info for /var/lib/Repetier-Server/printer/WhitePrinter/models/00002180_Santa-3.g printer WhitePrinter

2016-10-30 11:50:26: Updating info for /var/lib/Repetier-Server/printer/WhitePrinter/models/00002178_Santa Baby Lettering-3.g printer WhitePrinter

2016-10-30 11:50:26: Updating info for /var/lib/Repetier-Server/printer/WhitePrinter/models/00002179_Chubby Gingerboy-4.g printer WhitePrinter

2016-10-30 11:50:26: Updating info for /var/lib/Repetier-Server/printer/WhitePrinter/models/00002182_25 December-3.g printer WhitePrinter

2016-10-30 11:50:31: boost::thread_resource_error: Resource temporarily unavailable

2016-10-30 11:50:32: boost::thread_resource_error: Resource temporarily unavailable

2016-10-30 11:50:33: boost::thread_resource_error: Resource temporarily unavailable

2016-10-30 11:50:34: boost::thread_resource_error: Resource temporarily unavailable

2016-10-30 11:50:35: boost::thread_resource_error: Resource temporarily unavailable

2016-10-30 11:50:36: boost::thread_resource_error: Resource temporarily unavailable

2016-10-30 11:50:37: Handling action 'listModels' caused error boost::thread_resource_error: Resource temporarily unavailable

2016-10-30 11:50:37: boost::thread_resource_error: Resource temporarily unavailable

2016-10-30 11:50:38: boost::thread_resource_error: Resource temporarily unavailable

2016-10-30 11:50:39: boost::thread_resource_error: Resource temporarily unavailable

2016-10-30 11:50:40: boost::thread_resource_error: Resource temporarily unavailable

2016-10-30 11:50:41: boost::thread_resource_error: Resource temporarily unavailable

2016-10-30 11:50:44: Closing websocket for missing ping

2016-10-30 11:50:45: boost::thread_resource_error: Resource temporarily unavailable

2016-10-30 11:50:46: boost::thread_resource_error: Resource temporarily unavailable

2016-10-30 11:50:47: boost::thread_resource_error: Resource temporarily unavailable

2016-10-30 11:50:49: boost::thread_resource_error: Resource temporarily unavailable

2016-10-30 11:50:52: boost::thread_resource_error: Resource temporarily unavailable

2016-10-30 11:50:53: boost::thread_resource_error: Resource temporarily unavailable

2016-10-30 11:50:55: boost::thread_resource_error: Resource temporarily unavailable

2016-10-30 11:50:56: boost::thread_resource_error: Resource temporarily unavailable

2016-10-30 11:50:57: boost::thread_resource_error: Resource temporarily unavailable

2016-10-30 11:50:58: boost::thread_resource_error: Resource temporarily unavailable

2016-10-30 11:51:05: boost::thread_resource_error: Resource temporarily unavailable

2016-10-30 11:51:06: boost::thread_resource_error: Resource temporarily unavailable

This log except is after several restarts of the server. It seemed like it would 'update the info' for a couple hundred files then run out of resources. I had to restart the server to get it going again about 10 times but it eventually completed all and now they are showing up in the printer. Maybe if there was a way to limit how many files it tries to update in order to prevent the server from running out of resources would be better. Also of note this was on a raspberry Pi 2 so the fact that it can handle as many as it can shows how well the server program was designed.

</div>

Repetier

Normally this is no problem as you can only add file by file. Deleting all .gin is n exception. For next update I have a autofix to fix only defect .gin files on startup.

james8

Use this to validate your JSON: JSON validator