Error upgrading from 1.8.0 to 1.8.1

Get Help
1

What is the problem?

Getting errors upgrading from 1.8.0 to 1.8.1

What did you already try to solve it?

Restarted octoprint - tried again. And again.

Have you tried running in safe mode?

Yes

Did running in safe mode solve the problem?

No

Systeminfo Bundle

You can download this in OctoPrint's System Information dialog ... no bundle, no support!)

octoprint-systeminfo-20220524115249.zip (21.4 KB)

Additional information about your setup

OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible

WRITE HERE

Recently upgraded to 1.8.0 with no issues - except a small one with the ArcWeld plugin not being able to be updated.

2

It seems that something about either your system or pip installed therein is broken:

2022-05-24 11:52:10,762 ! session = self.get_default_session(options)
2022-05-24 11:52:10,762 ! File "/home/pi/oprint/lib/python3.7/site-packages/pip/_internal/cli/req_command.py", line 78, in get_default_session
2022-05-24 11:52:10,763 ! self._session = self.enter_context(self._build_session(options))
2022-05-24 11:52:10,764 ! File "/home/pi/oprint/lib/python3.7/site-packages/pip/_internal/cli/req_command.py", line 95, in _build_session
2022-05-24 11:52:10,765 ! index_urls=self._get_index_urls(options),
2022-05-24 11:52:10,766 ! File "/home/pi/oprint/lib/python3.7/site-packages/pip/_internal/network/session.py", line 248, in __init__
2022-05-24 11:52:10,766 ! self.headers["User-Agent"] = user_agent()
2022-05-24 11:52:10,767 ! File "/home/pi/oprint/lib/python3.7/site-packages/pip/_internal/network/session.py", line 131, in user_agent
2022-05-24 11:52:10,768 ! zip(["name", "version", "id"], distro.linux_distribution()),
2022-05-24 11:52:10,769 ! File "/home/pi/oprint/lib/python3.7/site-packages/pip/_vendor/distro.py", line 125, in linux_distribution
2022-05-24 11:52:10,770 ! return _distro.linux_distribution(full_distribution_name)
2022-05-24 11:52:10,771 ! File "/home/pi/oprint/lib/python3.7/site-packages/pip/_vendor/distro.py", line 681, in linux_distribution
2022-05-24 11:52:10,771 ! self.version(),
2022-05-24 11:52:10,773 ! File "/home/pi/oprint/lib/python3.7/site-packages/pip/_vendor/distro.py", line 741, in version
2022-05-24 11:52:10,773 ! self.lsb_release_attr('release'),
2022-05-24 11:52:10,774 ! File "/home/pi/oprint/lib/python3.7/site-packages/pip/_vendor/distro.py", line 903, in lsb_release_attr
2022-05-24 11:52:10,775 ! return self._lsb_release_info.get(attribute, '')
2022-05-24 11:52:10,776 ! File "/home/pi/oprint/lib/python3.7/site-packages/pip/_vendor/distro.py", line 556, in __get__
2022-05-24 11:52:10,777 ! ret = obj.__dict__[self._fname] = self._f(obj)
2022-05-24 11:52:10,778 ! File "/home/pi/oprint/lib/python3.7/site-packages/pip/_vendor/distro.py", line 1014, in _lsb_release_info
2022-05-24 11:52:10,778 ! stdout = subprocess.check_output(cmd, stderr=devnull)
2022-05-24 11:52:10,779 ! File "/usr/lib/python3.7/subprocess.py", line 395, in check_output
2022-05-24 11:52:10,780 ! **kwargs).stdout
2022-05-24 11:52:10,781 ! File "/usr/lib/python3.7/subprocess.py", line 487, in run
2022-05-24 11:52:10,782 ! output=stdout, stderr=stderr)
2022-05-24 11:52:10,783 ! subprocess.CalledProcessError: Command '('lsb_release', '-a')' returned non-zero exit status 1.

This looks like this problem:

3

Good call. I just remembered that I updated from Python 3.7 to Python 3.10 (for no particular reason). I have downgraded back to 3.7 - and the problem has gone away. I'm fully updated now.

What version do you do your testing on?

4

Stock versions on OctoPi 0.17 (with update to py3) through 1.0.0rc on every update. Additionally 3.7, 3.8, 3.9, 3.10 automatically on CI. 3.7 and 3.9 on my own dev environments.

The issue here though isn't the python version. It's having upgraded the system wide python version and that apparently missing some bits.

5

sadly i updated my pi from 1.8.0 to the 1.8.1 and now it wont even run and octodash says the pi has timed out. so i need to figure out how to roll back and not being able to get into it .

6

You need to start your own thread and make sure to upload all the details asked for

7

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.