Update to Octoprint 1.3.5 breaks OctoPi #427
Comments
|
I also have a problem updating from 1.3.4 to 1.3.5 with a new Raspberry 3 B. Downloaded the version 0.14 of Octopi, got everything up and running. But when prompted with either the notification that the software is to be updated or when updating from the settings menu it fails, resulting in the octopi to restart and prompting me to update again. |
|
cc @foosel |
|
I'm not aware of any such issues and apart from one (still incomplete) ticket by you @Vankurt I have also not received any reports. Over the course of the release preparations I also always update multiple times from various OctoPi base installs and start versions. |
|
I am having this problem as well whenever I try to login to the octoprint web page the page reloads and nothing happens. |
|
If you have the TPSmartlinkPlug plugin installed, uninstall it via SSH. See jneilliii/OctoPrint-TPLinkSmartplug#19. |
We so far only protected the binding process itself against errors triggered inside view models. Now we are also more resilient against issues arising in view model callbacks like onBeforeBinding, onBoundTo and onAfterBinding as well as exceptions during plugin instantiation itself. Triggered by jneilliii/OctoPrint-TPLinkSmartplug#19 which was also reported on OctoPrint's tracker as #2168, #2170 and #2171 and on OctoPi as guysoft/OctoPi#427.
|
Hi there, so there is my Log file: https://gist.github.com/Tiefschneegiftler/ecdafdbb99685551342063984f8b2f70 (Can you tell me by the way which way to add that log file here?) Dont have the TPSmartlingPlug installed though. However I am using a TP-Link Router. |
|
@Tiefschneegiftler this is not the same issue as the TPLinkSmartplug issue, that's plugin specific. It's however completely unclear as of now if the issue originally reported in this ticket and the TPLinkSmartplug problem are even related. In any case, your problem sounds different in that it manifests in not being able to update in the first place. Please stick to OctoPrint/OctoPrint#2158, @guysoft has no control over the update process (that's an OctoPrint feature unrelated to OctoPi), and for now we have to assume that that's where things are going wrong until proven otherwise. |
|
I tried (and failed with) the update from a fresh OctoPi 0.14 image. So no additional plugins were installed. Will there be an OctoPi 0.15 with the latest OctoPrint on board? That way I would get around the update process ;-) |
|
There is a nightly build |
|
You can also update manually (how is explained in the FAQ) or just cooperate with me and provide all the requested information on the OctoPrint bug tracker so that we can figure out what is going wrong for you. Again, updating from stock version 1.3.4 on OctoPi 0.14 was part of the tests I did prior to this release, and also for every single RC before that, multiple times. If there was a general issue, either I or any one of the people who tested and reported back on the RCs over the past nearly three months would have noticed that. That was not the case so it must be something more rare or restricted to your environment and the only way to solve this is to work with me on this. |
|
same here - just broke two of my PIs... thanks alot for the night shift... patreon cancelled... As for the records l- this is the log: plugin_softwareupdate_console.log And this is the error message after trying to update manually using exactly the commands in the FAQ ~/oprint/bin/python setup.py install: console output: |
|
From a fresh OctoPi 0.14 install just now, updating to 1.3.5: I don't know what to tell you. From your log it looks like for some reason it can't fetch a necessary dependency from python's own package index. That might be due to a timeout while attempting to read the package index data (seen that in the past due to network issues) or due to pypi having some issues (personally I have never seen that but it could probably happen) or due to some proxy between you and pypi doing weird stuff (I have no idea how your network setup looks like, only you know that). If OctoPrint doesn't have an unhindered network connection and hence can't fetch from github and pypi, it can't update itself. And not being able to fetch this data is nothing that a user space program or an image like OctoPi for that matter can fix. You could try if If not, there's your problem, somewhere between your pi and pypi. |
|
Unable to reproduce here either, octopi 0.14 with octoprint 1.3.4 -> 1.3.5 works perfectly fine. |
|
the curl command reproduced the html output perfectly: but the pip command returned immediately. and with immediately i mean IMMEDIATELY - so no timeout or whatever. here's the error message: here's the pip log: as for the assumption of any barreer kinda phenomena: update, upgrade, dist-upgrade, git clones in general and all the rest of the partivular manual update process for octoprint worked just fine. so do other downloads from the internet to my LAN. as for diving into the problem's solution: i am just an octoprint / octopi user and it worked fine for a long time - i am obviously not the only one experiencing this issue, so maybe the statement "works fine here" wouldn't be too helpful. but i also understand as this is free software, i cant complain about that attitude... so what - i cancelled the patreon subscription and may get stuck with this... |
|
So you've used it for a long time, and been happy with it, but as soon as there's one issue with it, you jump ship and cancel your support?
But it is helpful, the update process works for many/most, the whole "no news is good news" doesn't fly when issue trackers are involved, developers need to know whether this is a wide spread issue affecting everyone, or one limited to only a few people. Again, this isn't something any of us can reproduce so figuring out why it doesn't work for you might take time: As you can see, that command works fine for me, and obviously it worked for @foosel, and many others who tested the various stages of the release candidates before 1.3.5 was finally released. Getting angry and yelling about cancelling your support won't get your issue fixed any faster.
Well with that attitude, you WILL get stuck with it. If you feel like you'd be happier with a paid product and don't wish to assist any further in figuring out what went wrong, might I suggest an AstroBox, or Repetier Server Pro. |
|
To be clear: I cancelled it, because this issue killed two PIs, took me an entire night to get the stuff fixed again eventho i luckily had images, thus made me miss printing a birthday present in time. then i realize, i am not the only one having this problem and all i read is: "works fine here" (and implicitly: "your fault"). this is what then really pisses me off - i have been working in software development and IT consulting for almost 25 years now and this is exactly the attitude i am all allergic against: user comes up with a problem, developer says: works fine on my machine, cant be, must be you. there would have been a little difference in an answer like "oh - interesting, never saw that happening, we take a look". you see the difference? no? yes? however... as for the cancellation: at the moment i start the patreon subscription, this becomes a paid product to me, because that's what a patreon subscription is: paying for a product. i did that, because i was convinced of this stuff and i didn't wanna be that kinda guy, who wants everything for free and then complains anyway. i have a certain experience what it means to maintain such a product, and when i saw that good ppl like gina and tom lost their jobs at that spanish company i immediately subscribed to patreon. but as i said - it makes it a paid product then. gina is supposed to get paid for the job she does, but then, if it becomes a paid product, i don't expect neither such surprises nor such responses. OK... one could argue, that microsoft sells bug collections and calls them products... yeah right... and thanks for the recommendations - i am grown up enough to find alternatives or just wait until this problem will be fixed in later releases. but i got the message of being insulted by criticism - could be a milennial prob? ;-) |
Where did anyone say it's your fault? All we're saying is we can't reproduce it, that doesn't make it your fault, if that's the impression you get then that's your own problem with the way you think.
OctoPrint shouldn't be doing anything that can break the underlying OS. The worst that should happen is that OctoPrint itself no longer runs. If it DOES to something terrible that breaks the entire OS, then that's a major bug that needs to be fixed, and the only way it gets fixed is if people who have the bug, co-operate in a civil manner and provide all the information they can, and make themselves available for testing. You say you worked in software dev for 25 years, that's something I'd expect you to know. How are bugs meant to get fixed if the people fixing them can't reproduce them? And for the record, I'm not a developer, I was just saying that it works here for me, another user of OctoPrint. The only things I've done that might be considered "development" is change a couple of things in its UI, and make a couple of plugins, but I'm 99% just a user of it.
Your very first words were about cancelling your support. No offers to help, no "ok, I have this issue, what is required of me" just a big old middle finger to everyone involved, and "you broke my stuff, here's some logs, goodbye".
Yours is not the attitude of a "grown up". |
|
@HerrRausB : Is your system time set to the right time? SSL gets confused when the time is not right. Also, what happens when you try: ~/oprint/bin/pip install --index-url=https://pypi.python.org/simple/ futures |
|
ChinooTx: Time is OK: which is totally fine and precise. the "~/oprint/bin/pip install --index-url=https://pypi.python.org/simple/ futures" resulted in: which looks promising - i'm gonna try to do the manual update tomorrow - thanks alot for the hint! as i am absolute cluelesss on that matter - what is the difference to the other version? the explicit URL? could there be a corrupted repository or repository entry anywhere? i ran the manmual update procedure again and it remains erronious: octoprint again is not starting up and i remain clueless - but at all thanks for the attempt anyways :-) |
|
I can confirm I'm having the same issue as HerrRausB . Seems like it can't resolve to http://pypi.python.org |
|
I believe it's related to something old or leftover in your pip config. It needs to use SSL but doesn't want to for some reason, hence the HTTP Error 403: SSL is required. Forcing it to https as I suggested hint to this, but I have no idea what could be wrong. There are similar issues if you search for "HTTP Error 403: SSL is required pip" on google. Most of them hinting at a version of pip that is too old. :-/ Edit: |
|
I tried upgrading(pip and base system) I'm going to just reformat and start over ...not to hard |
|
at least its now obviously reproducable... |
|
I believe it's a mismatch with the version of pip but I haven't tracked down exactly what. You can run something like: ~/oprint/bin/pip install --index-url=https://pypi.python.org/simple --upgrade pip to update pip to the latest version and then ~/oprint/bin/pip can be run without the --index-url parameter. I did this and got to pip version 9.0.1. |
|
did that pip upgrade and the result here remains the same: but if i understood the above right, then it's maybe the fact, that it still looks for tha packages not using ssh, i.e. http instead of https? maybe i should try that with another complete blank fresh new install :-( |
|
What OctoPi version is everyone experiencing this running? You can determine this via Also, if it's still failing after attempting to update pip, Finally, to get things going fast (note that this will not solve the core issue, merely circumvent it), try Alternatively, in order to roll back see again the FAQ - but I'm not sure if those pip issues won't cause trouble there. |
|
After flashing an 0.12 image I still thankfully had lying around, I could reproduce this, and it's indeed caused by a change to the python package index that happened a couple days after 1.3.5 was released and is unrelated to the release itself. To fix on OctoPi 0.12, SSH into your instance, then first do this: That updates pip and also tells the also quite old version of Python's distutils on there to use the https URL instead of the non-functional http one. Then: |
|
Yes, I can confirm that I was running with Octopi version 0.12.0. I definitely had the = sign in the index-url parameter. From my shell history, the command I ran was: ~/oprint/bin/pip install --index-url=https://pypi.python.org/simple --upgrade pip |
|
Thanks foosel , |
|
I am running OctoPi 0.9 and 0.11 on my printers. Will these versions have the same problem? Related, is there a recommended procedure for updating these to OctoPi 0.14? Edit: I see that earlier releases apparently have the issue too. Is there a general OctoPi upgrade procedure? |
|
experiencing this on as well octopi 0.13 as 0.14 on two different RPI2 and RPI3 |
|
Ok, also saw there is an announcement on OctoPrint now. Should I close this or does anyone else want to do the honors? |
|
I could bow again towards gina... thanks bow done ;-) as the problem is solved, closing would appropriate, i guess :-) |
|
OctoPi 0.9? Wha! Thats so retro! Its like from 2014! You should upgrade.
Even Debian dropped support for stuff on that.
|
|
@guysoft Yeah, I should upgrade, thus "is there a general upgrade procedure?" :-) Can it be done in place, or does it mean setting up from fresh after backing up the octoprint config.yaml? |
|
@Lenbok dont upgrade it - keep it... some day it will be of huge collector's value ;-) |
|
@HerrRausB right on! I will put it in the cupboard along with my MakerBot cupcake #511 that I put aside a few years ago, thinking that one day it might be valuable like an Apple I computer. |
|
@Lenbok yeah - there even are some behavioural parallels between Jobs and Pettis as in screwing the customers :-) Getting off topic I assume... |
I'm using OctoPi on raspberry Pi Zero W. I've tried six (!) times to update OctoPi 0.14 to Octoprint 1.3.5, every time the Pi was broken afterwards. E.g. it did not boot, the web server did not start or the Login-button on the OctoPrint home page was not functional.
Of course I also tried the update with a freshly installed, unmodified OctoPi 0.14 image. Also without success.
Is this normal? Is anyone else having these troubles?
Is there any way to fix this? Will there be an OctoPi 0.15 with latest OctoPrint anytime soon?
Currently I'm simply ignoring the update to OctoPrint 1.3.5 to keep my printer working.
The text was updated successfully, but these errors were encountered: