emmakat
commented
3 years ago rebuilding again, will re-open if this doesn't solve it.
Closed emmakat closed 3 years ago
emmakat
commented
3 years ago rebuilding again, will re-open if this doesn't solve it.
emmakat
commented
3 years ago same issue entirely :( d@Z-230:~/docker stuff/arm$ docker run -d \
-p "8080:8080" \ -e UID="1000" -e GID="1000" \ -v "/home/arm:/home/arm" \ -v "/home/arm/Music:/home/arm/Music" \ -v "/home/arm/config:/home/arm/config" \ -v "/home/arm/logs:/home/arm/logs" \ -v "/home/arm/media:/home/arm/media" \ --device="/dev/sr0:/dev/sr0" \ --device="/dev/sr1:/dev/sr1" \ --device="/dev/sr2:/dev/sr2" \ --device="/dev/sr3:/dev/sr3" \ --device="/dev/sr4:/dev/sr4" \ --device="/dev/sr5:/dev/sr5" \ --device="/dev/sr6:/dev/sr6" \ --privileged \ --restart "always" \ --name "arm-ripper" \ 1337server/automatic-ripping-machine:latest Unable to find image '1337server/automatic-ripping-machine:latest' locally latest: Pulling from 1337server/automatic-ripping-machine 04a5f4cda3ee: Pull complete ff496a88c8ed: Pull complete 0ce83f459fe7: Pull complete c51460f54519: Pull complete 0e5a97d2ea17: Pull complete 50a14fc1a867: Pull complete 421f295fe4da: Pull complete 55b592c96487: Pull complete 482b95676137: Pull complete 190385fb302a: Pull complete 79bd96e61c48: Pull complete c09b55000960: Pull complete ceb7e224480e: Pull complete c29b08fb88f0: Pull complete 211ee9d2530e: Pull complete Digest: sha256:c65f26f8b767360aa739ea7dd124ca22eb102811ad8e6692bb8ce529374a4f7f Status: Downloaded newer image for 1337server/automatic-ripping-machine:latest 0fa2706e5c76f7d73088be03ee6aff4b79028379dcd5c913abc9d88259f96da7 jd@Z-230:~/docker stuff/arm$ setup/docker-setup.sh install: cannot remove '/etc/udev/rules.d/docker-arm.rules/docker-arm.rules': Permission denied jd@Z-230:~/docker stuff/arm$ sudo setup/docker-setup.sh[sudo] password for jd: done. insert a disc...jd@Z-230:~/docker stuff/arm$ docker ps -aCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES0fa2706e5c76 1337server/automatic-ripping-machine:latest "/opt/arm/scripts/do…" 10 minutes ago Restarting (1) 25 seconds ago arm-ripper jd@Z-230:~/docker stuff/arm$ docker logs 0fa2706e5c76 creating group [arm] with id 1000 id: 'arm': no such user creating user [arm] with id 1000 setting makemkv app-Key '/dev/cdrom' -> '/dev/sr0' Traceback (most recent call last): File "/opt/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1705, in _execute_context self.dialect.do_execute( File "/opt/venv/lib/python3.8/site-packages/sqlalchemy/engine/default.py", line 681, in do_execute cursor.execute(statement, parameters) sqlite3.OperationalError: no such table: ui_settings
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/opt/arm/arm/runui.py", line 8, in
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/opt/arm/arm/runui.py", line 8, in
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/opt/arm/arm/runui.py", line 8, in
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/opt/arm/arm/runui.py", line 8, in
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/opt/arm/arm/runui.py", line 8, in
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/opt/arm/arm/runui.py", line 8, in
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/opt/arm/arm/runui.py", line 8, in
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/opt/arm/arm/runui.py", line 8, in
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/opt/arm/arm/runui.py", line 8, in
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/opt/arm/arm/runui.py", line 8, in
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/opt/arm/arm/runui.py", line 8, in
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/opt/arm/arm/runui.py", line 8, in
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/opt/arm/arm/runui.py", line 8, in
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/opt/arm/arm/runui.py", line 8, in
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/opt/arm/arm/runui.py", line 8, in
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/opt/arm/arm/runui.py", line 8, in
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/opt/arm/arm/runui.py", line 8, in
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/opt/arm/arm/runui.py", line 8, in
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/opt/arm/arm/runui.py", line 8, in
1337-server
commented
3 years ago This was because of
# This attaches the armui_cfg globally to let the users use any bootswatch skin from cdn
armui_cfg = UISettings.query.filter_by().first()
app.jinja_env.globals.update(armui_cfg=armui_cfg)I was trying to use the new uisettings globally within the app, but had to remove it from the devel branch because it causes issues it triggers before you visit /setup so it causes this error. I forgot to remove it from the docker branch. Apologies.
The latest docker image (its building ATM) should fix this issue.
emmakat
commented
3 years ago no problem! Thanks so much - I'll give it another go this morning and report back/close this issue if it resolves.
emmakat
commented
3 years ago Ok it got a bit further this time. I opened the webserver setup and see Successfully created all of the ARM directories Couldn't setup database So I tried to create the admin user (just guessing here) and see the following error:
sqlalchemy.exc.OperationalError
sqlalchemy.exc.OperationalError: (sqlite3.OperationalError) no such table: user [SQL: SELECT user.user_id AS user_user_id, user.email AS user_email, user.password AS user_password, user.hash AS user_hash FROM user WHERE user.email = ? LIMIT ? OFFSET ?] [parameters: ('arm', 1, 0)] (Background on this error at: http://sqlalche.me/e/14/e3q8)
emmakat
commented
3 years ago I tried inserting a disc to see if that would kick things off, but no such luck :( I tried running but that didn't work either - seems files aren't there - but I'm guessing I was supposed to do this somehow from within the container but I don't know how to do that.
/usr/bin/python3 /opt/arm/arm/ripper/main.py -d sr0 | at now warning: commands will be executed using /bin/sh /usr/bin/python3: can't open file '/opt/arm/arm/ripper/main.py': [Errno 2] No such file or directory
1337-server
commented
3 years ago Can you try chmod your directory that holds your db ? ARM creates this folder but for some reason its not setup to allow it to write to it.
The default directory would be /home/arm/db
Once you have chmod you should then be able to visit /setup page. If its worked correctly you should see
Setup of the database was successful.
emmakat
commented
3 years ago bingo! It's working now - thank you!
emmakat
commented
3 years ago Now I'm troubleshooting that nothing is happening when I insert the disk and tail -f /var/log/syslog | grep ARM shows nothing. I'll try a few things and see what happens
1337-server
commented
3 years ago Try just the system log tail -f /var/log/syslog It should be showing every time it runs the docker exec
EDIT: You should also make sure that lsscsi is installed on the host device. Not sure if this is something that would be missing in some linux distros. But it wont hurt to check.
emmakat
commented
3 years ago good call on the lsscsi - it wasn't installed. I have some new/different errors, but I'll open a fresh issue for clarity.
Description
I get the error sqlite3.OperationalError: no such table: ui_settings I looked at #29 but I don't understand how to delete the database in order to start over. I can't get to the webserver.
I have no idea how to solve this :( I've tried removing and pruning everything, I've tried rebooting the machine. no matter what, this error occurs.
Environment
[OS Distribution and version (run "cat /etc/lsb-release")] [ARM Release Version or if cloning from git branch/commit (run "git branch" and "git log -1" to get this)]
Log file
[Run the rip in DEBUG and drag and drop the log file onto this comment box]
[>>>>> DRAG AND DROP LOG FILE HERE <<<<<]