OctoPrint 1.3.4->1.3.5 update from GUI fails unless you have libyaml-dev installed

[jarrodasmith]

If you use the current OctoPi image to bring up a new OctoPrint 1.3.4 system, you will be prompted to update to 1.3.5 from inside the server the first time you connect. This update fails if you do not first manually install the libyaml-dev package in the underlying OS.

[GitIssueBot]

Hi @jarrodasmith,

It looks like there is some information missing from your bug report that will be needed in order to solve the problem. Read the Contribution Guidelines which will provide you with a template to fill out here so that your bug report is ready to be investigated (I promise I'll go away then too!).

If you did not intend to report a bug but wanted to request a feature or brain storm about some kind of development, please take special note of the title format to use as described in the Contribution Guidelines.

Please do not abuse the bug tracker as a support forum - if you have a question or otherwise need some kind of help or support refer to the Mailinglist or the G+ Community instead of here.

Also make sure you are at the right place - this is the bug tracker of the official version of OctoPrint, not the Raspberry Pi image OctoPi nor any unbundled third party OctoPrint plugins or unofficial versions. Make sure too that you have read through the Frequently Asked Questions and searched the existing tickets for your problem - try multiple search terms please.

I'm marking this one now as needing some more information. Please understand that if you do not provide that information within the next two weeks (until 2017-11-02 09:10 UTC) I'll close this ticket so it doesn't clutter the bug tracker. This is nothing personal, so please just be considerate and help the maintainers solve this problem quickly by following the guidelines linked above. Remember, the less time the devs have to spend running after information on tickets, the more time they have to actually solve problems and add awesome new features. Thank you!

Best regards,
~ Your friendly GitIssueBot

PS: I'm just an automated script, not a human being, so don't expect any replies from me :) Your ticket is read by humans too, I'm just not one of them.

[Tiefschneegiftler]

I have the same problem, however, mine comes from the OctoPi image 0.14 which unpacks to OctoPi 1.3.4 and than fails at updating to 1.3.5.
The problem is resulting from trying to update from the 1.3.4, as from the freshly installed image, to the 1.3.5 version via the notification in the start screen as well as when trying to update it via the settings.
Log: https://gist.github.com/Tiefschneegiftler/ecdafdbb99685551342063984f8b2f70

Is his thread related to: guysoft/OctoPi#427 ?

[foosel]

I don't know if it's related, I cannot reproduce either. Release procedure involves multiple update tests from various OctoPi and OctoPrint version states (incl. OctoPi 0.14 and OctoPrint 1.3.4 of course), if this was a general problem I would have noticed during those tests (or the four release candidates that went before the stable release). So it must be something odd.

What might help is plugin_softwareupdate_console.log from a failed attempt, should also be under ~/.octoprint/logs on OctoPi (or Linux in general for that matter).

In general though there was no change at all in the yaml dependencies between 1.3.4 and 1.3.5.

[foosel]

@jarrodasmith if you want this solved you should also provide some further information. I run several stock OctoPi 0.14 images here right now that updated fine without any manual installation steps.

[jarrodasmith]

Thanks for looking at this. I didn't provide more info because it was very easy to reproduce (also easy to work around) and I did so twice. I'm surprised to hear you couldn't. I will see if I can reproduce it a third time. I don't have the logfile, Not knowing what would happen after the botched installation, I just reformatted that SD card and applied the workaround which is now in production (very nice, too!). Jarrod

…

On Oct 24, 2017, at 4:26 AM, Gina Häußge ***@***.***> wrote: @jarrodasmith if you want this solved you should also provide some further information. I run several stock OctoPi 0.14 images here right now that updated fine without any manual installation steps. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[foosel]

@jarrodasmith Never assume that just because you can reproduce something easily, everyone can ;) And in case of OctoPrint you can bet on me and all of the people who tested the RCs to have run through the update process multiple times, so if it's failing for you, it must be something hard to reproduce that needs a lot of information to be debugged :)

[jarrodasmith]

So in thinking back on this, "fails" may have been too strong a word. I definitely saw an error in the log that some step had clearly failed due to missing yaml libs or headers. I actually did not follow through to see if the software worked or not. I will go through this again and submit the log file for your perusal, no assumptions on my part this time ;-) Thanks again. jarrod

…

On Oct 24, 2017, at 4:46 AM, Gina Häußge ***@***.***> wrote: @jarrodasmith Never assume that just because you can reproduce something easily, everyone can ;) And in case of OctoPrint you can bet on me and all of the people who tested the RCs to have run through the update process multiple times, so if it's failing for you, it must be something hard to reproduce that needs a lot of information to be debugged :) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[foosel]

Ah... I think I know what you might have seen. If so that's actually a default "behaviour" of pyyaml. It attempts to compile with the headers, but if it doesn't find them, it still installs just fine (just without a native extension). It's always done that and there's nothing I can do about that, plus also no reason since what looks like an error is more like a warning.

If that indeed was what you were running into then whatever @Tiefschneegiftler encountered is something completely different. So let's see some logs from both of you and take it from there.

[jarrodasmith]

I've now reinstalled from scratch without first manually installing the libyaml-dev packages. Here is the error I saw that led me to submit this "bug": 2017-10-26 02:34:45,459 > Searching for PyYAML>=3.10,<3.11 2017-10-26 02:34:45,461 > Reading https://pypi.python.org/simple/PyYAML/ 2017-10-26 02:34:45,463 > Best match: PyYAML 3.10 2017-10-26 02:34:53,247 ! build/temp.linux-armv6l-2.7/check_libyaml.c:2:18: fatal error: yaml.h: No such file or directory 2017-10-26 02:34:53,251 ! #include <yaml.h> 2017-10-26 02:34:53,255 ! ^ 2017-10-26 02:34:53,260 ! compilation terminated. 2017-10-26 02:34:54,687 ! But as you say it continues on and completes the install successfully without the extension. My apologies for raising a red herring. Jarrod

…

On Oct 24, 2017, at 4:54 AM, Gina Häußge ***@***.***> wrote: Ah... I think I know what you might have seen. If so that's actually a default "behaviour" of pyyaml. It attempts to compile with the headers, but if it doesn't find them, it still installs just fine (just without a native extension). It's always done that and there's nothing I can do about that, plus also no reason since what looks like an error is more like a warning. If that indeed was what you were running into then whatever @Tiefschneegiftler encountered is something completely different. So let's see some logs from both of you and take it from there. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[Tiefschneegiftler]

Hi foosel!
So the link to the regular log entries still is the same as above: https://gist.github.com/Tiefschneegiftler/ecdafdbb99685551342063984f8b2f70

However there is that dialog box that pops up:
https://gist.github.com/Tiefschneegiftler/f0f59af15d147920e51cb9bcae8e890a

And here is the "update log":
https://gist.github.com/Tiefschneegiftler/3fdbaa955f95795a34af658fc5215bc1

Anything else I may supply you with?

[normanclanger]

Hi - I'm running Octoprint on a RaspberryPi, attempting to upgrade from 1.3.4 to 1.3.5 because of a prompt that pops up in the GUI. To date, updates within the GUI have always been successful (possibly there was a 1.2.7 manual step required).

Today I get a repeated failure - the log entry is as below. Any clues please?

thanks

Tim

plugin_softwareupdate_console.log [edit by @foosel: moved into gist, too long for a comment]

[foosel]

@Tiefschneegiftler

2017-10-24 08:29:49,957 > 191 files changed, 93857 deletions(-)

This indicates that your checkout is seriously compromised. It's basically showing a diff of the complete code base there, which looks like the checkout on your Pi is pretty much empty.

error: unable to resolve reference refs/remotes/origin/master: Invalid argument

And this screams corrupted git folder. Did you by any chance not shutdown your Pi correctly in the past? Because that certainly looks like some serious data corruption on your SD card. I'd suggest to make a list of your plugins, backup your ~/.octoprint folder and then start with a clean install, because if this much is broken in your filesystem just in that folder, it's unclear what else might be.

@normanclanger

Reading http://pypi.python.org/simple/futures/
Scanning index of all packages (this may take a while)
Reading http://pypi.python.org/simple/

Your's looks like network problems while it's trying to fetch some dependencies from the Python Package Index. Any network issues on your location recently?

---

In any case, both of you are running into issues outside of OctoPrint's control. I'm happy to help you trying to debug them further as time permits, but I think at this point the official support channels in form of the Mailinglist or the G+ community would actually be a better place than a bug tracker.

And the original issue reported by @jarrodasmith (which those two above are completely unrelated two) has turned out to be a red herring as well.

Therefore I'm closing this.

[normanclanger]

Thanks - I burnt a new sd card using octopi, and the upgrade then happened successfully.

[Tiefschneegiftler]

Thx @foosel Works like a charm now. :D