automatic-ripping-machine: ARM Will not RIP Disk or create log file - Error

  • I have checked the wiki
  • I have searched for similar issues

Describe the bug When I insert disk log created but nothing else happens

To Reproduce Steps to reproduce the behavior:

  1. Insert Disk

Environment

DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION=“Ubuntu 22.04.1 LTS”] ARM v 2.6.0

Log file

No Log file create

I got this from /var/mail/arm file:

Subject: Output from your job       89
To: arm@arm
Message-Id: <20221022215238.3DF3616E00AD@arm>
Date: Sat, 22 Oct 2022 17:52:38 -0400 (EDT)
From: rick <arm@arm>

Traceback (most recent call last):
  File "/opt/arm/arm/ripper/main.py", line 443, in <module>
    running_jobs = db.session.query(Job).filter(Job.status.notin_(['fail', 'success']), Job.devpath == devpath).all()
  File "<string>", line 2, in query
  File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/orm/scoping.py", line 24, in _proxied
    return self.registry()
  File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/util/_collections.py", line 1006, in __call__
    key = self.scopefunc()
  File "/usr/local/lib/python3.10/dist-packages/flask_sqlalchemy/session.py", line 81, in _app_ctx_id
    return id(app_ctx._get_current_object())  # type: ignore[attr-defined]
  File "/usr/local/lib/python3.10/dist-packages/werkzeug/local.py", line 513, in _get_current_object
    raise RuntimeError(unbound_message) from None
RuntimeError: Working outside of application context.

This typically means that you attempted to use functionality that needed the current application. To solve this, set up an application context with app.app_context(). See the documentation for more information.

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 19 (8 by maintainers)

Commits related to this issue

Most upvoted comments

For what it’s worth, I traced this back to a too-new version of flask_sqlalchemy on my machine (was 3.0.2, 2.5.1 worked). A lot of other functionality like the ‘database’ page would crash the server due to breaking changes from the new major version.

If you’re hitting this, try pip install flask_sqlalchemy==2.5.1.

@shitwolfymakes

They are completely blank. I only have one accessible at the moment, but the other was completely identical to this one just with a different file name.

POSEIDON_ADVENTURE_166682270030.log

I will give the automated installer a try here in the next day or so if all goes well.