-
-
Notifications
You must be signed in to change notification settings - Fork 401
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Movie search doesn't work after upgrade to v3.0.4880 #3253
Comments
Hi! |
I'm facing the same issue with latest version 3.0.4880. Movie search doesn't work and there is no cover for TV shows. |
i have the same problem after update to v3.0.4880 |
yes me too! everything was solid up till last night. i noticed plex library syncs are also affected |
Can someone please email me the OmbiExternal.db to tidusjar@gmail.com |
Fixed in v3.0.4887 |
This is still broken for me on 4890 and 4892. The Obi system page still says that the DB is Sqlite. |
Run 4887. Then do some searching etc and then upgrade to the latest |
I continue to get the same error on 4887.
Reverted to 4880. Same error.
, but searches worked. Then I started stepping forward through the releases: |
Encountered the same issue on latest build as of this writing. Reverting to 4817 has fixed it. This issue should not be closed @tidusjar. |
@Spass1966 I had thought I'd fixed the issue. That's why the issue is closed. Apologies I cannot monitor the thread 24/7. For anyone experiencing the issue, please run the following against your SQLite database. Due the the recent changes to the multiple DB providers, if the migrations did not run in the correct order it has caused this issue and it's quite difficult to fix with EF migrations due to some users have the issue, and some dont.
|
Apologies for the stupid question but how do I access the SQLite database from inside the LinuxServer container? |
I ran the alter table command and still get the error. I wonder if my error is for a different table. Here's my full stack trace (though note that it's upside down)
Here's my table schema:
Is there a full migration script available somewhere that I can just run and be done? |
@Spass1966
|
@rsteckler you applied that to |
Sorry guys apply it to the Ombi external db |
That worked. Thanks! |
I had this problem also and fixed it by running the previously recommended SQL query against OmbiExternal.db
I didn't want to install stuff into my container so I just used the zip version (no install needed on your desktop either) of this SQLite browser/editor. I stopped my Ombi container, opened the OmbiExternal.db with the SQLite editor program, ran the query above, verified it had added the column into the proper table, saved it, and then started the Ombi container back up again. Everything looks like it working again with movies and TV posters showing up, as well as the "no such columns" error now no longer showing up in the logs. |
Here is a oneliner to fix the issue, assuming you are running in a docker container, your container has sudo apt update; \
sudo apt install -y sqlite3; \
sqlite3 $( \
docker inspect --format '{{ range .Mounts }}{{if eq .Destination "/config"}}{{ .Source }}{{end}}{{end}}' \
$(docker ps --filter name=ombi --format '{{.ID}}') \
)/app/OmbiExternal.db 'ALTER TABLE PlexServerContent ADD COLUMN RequestId INTEGER NULL' Explanation of parts: Update sudo apt update; \
sudo apt install -y sqlite3; Inspect container docker inspect --format \
'{{ range .Mounts }}{{if eq .Destination "/config"}}{{ .Source }}{{end}}{{end}}' \
$CONTAINER_ID List containers, filtering on docker ps --filter name=ombi --format '{{.ID}}' Concatenate the inspected directory path with the path to the $( ... )/app/OmbiExternal.db Tell sqlite3 /opt/ombi/app/OmbiExternal.db 'ALTER TABLE PlexServerContent ADD COLUMN RequestId INTEGER NULL' After you are done, you can remove sudo apt remove --purge sqlite3 |
It looks like Unraid doesn't have a package manager, but luckily there is a standalone binary for First you need to find where the find / -name OmbiExternal.db Then you can download the cd ~
wget https://www.sqlite.org/2019/sqlite-tools-linux-x86-3300100.zip
unzip sqlite-tools-linux-x86-3300100.zip
cd sqlite-tools-linux-x86-3300100 You need to tell the computer it's allowed to run the binary file, not just look at its contents chmod a+x sqlite3 Now you should be able to run the query, making sure to replace the path with the correct one from the sqlite3 /your/path/here/OmbiExternal.db 'ALTER TABLE PlexServerContent ADD COLUMN RequestId INTEGER NULL' Here it is all in one block (theoretically). I would always be careful copying and pasting stuff like this from the internet, if you don't know what it does. cd ~
wget https://www.sqlite.org/2019/sqlite-tools-linux-x86-3300100.zip
unzip sqlite-tools-linux-x86-3300100.zip
cd sqlite-tools-linux-x86-3300100
chmod a+x sqlite3
./sqlite3 $(find / -name OmbiExternal.db -print0 -quit 2>/dev/null) 'ALTER TABLE PlexServerContent ADD COLUMN RequestId INTEGER NULL' |
still seeing this issue on 3.0.4890 |
Was seeing the issue on 3.0.4892, but sqlite3 commands posted above corrected the problem for me |
I tried that I'm getting Error: attempt to write a readonly database |
stop the ombi service, and use sudo when running the sqlite3 command |
FYI if you dont want to run the script, just delete the OmbiExternal.db and then restart Ombi. |
This work for me on #3286 |
This works. After restarting docker, simply manually run the cacher/scan against Plex/Emby, |
Worked for me, thank you! |
+1, worked here too. Thanks! |
Hey guys and gals. I had the same problem after upgrading from v3.0.4817 to latest release and dev. As a test I reverted back to 4817nit worked again. I upgraded to the next upgrade v3.0.4887, the issue came up again. So something is up with the newer versions. Please help by fixing the issues. I will also try deleting the ombiexternal.db then restart to see if that fixes the issue for now. |
Ok deleting worked. I do have a question though. What am i missing without ombiexternal.db present? does it eventually repopulate the file when it is required? |
Confirmed, worked. For those without docker installs, just change to /etc/Ombi (or wherever your "Storage path" shows as at the /Settings/About page) then do :
|
How do I do this for Windows using DB Browser for SQLite? |
I may have answered this for myself:
I hope that helps someone |
I did this but skipped steps 3-5. Not sure why you export/import. Is there a reason I'm missing for those steps? As soon as I added the field it was good to go and I just copied it back to the docker volume. |
This is still an issue on a brand new install. I'm experiencing this on a brand new install on v3.0.4892. I'm getting the same error as everyone else: 'no such column: x.RequestId.' Also this error for TotalSeasons & RequestByAlias.
|
Hopefully fix bug Ombi-app#3253
I am having the same issue. Adding x.RequestId eliminates that error, but I still get 'no such column: x.TotalSeasons' and 'no such column: x.RequestedByAlias'. TV search works fine, Movie search, Movie Requests, and TV Requests are all broken. Deleting OmbiExternal.db then reverting to v3.0.4817 has resolved the issue for now. linuxserver/ombi:v3.0.4817-ls38 for those running from linuxserver. |
Same issue on a fresh install running 4892. In addition, movie requests are not being sent to radarr. Nothing appears in the logs from these actions. Edit: Reverting to 4817 as @Tripwyr suggested resolves the issue. |
Same issue on latest develop build 3.0.4958 |
I can confirm a fresh install of 4892 had the symptom of Radarr/Movies not searching/responding. Deleting "OmbiExternal.db" and restarting Ombi then resumed expected functionality. Below was the observed error I saw repeated many times in the logs. Happy to diagnose more if I could be pointed in a direction.
|
@tidusjar It appears the EF migrations are not running after upgrading or they are purposefully being skipped in favour of the SQLite Initial script which has an issue with CreateTable vs alterTable for upgrade (see my last paragraph below). I am using SQLite. Looking at the Ombi.db __EFMigrationsHistory table the last few entries I have are: In the source code I see there are these migration files that didn't get applied: These migrations add the columns that are called out in the error messages. The 20191102235658_Inital 2.2.6-servicing-10079 has create table calls with the appropriate columns for SQLite, but since the tables already exist from a previous installation I suspect they don't modify an existing table. If we're upgrading from a previous installation we would want to use the AlterTable() call instead of CreateTable(). |
same issue... new install. Took maybe 3 days for this to get into this condition. DO see lots of errors in the Logs dir. (log-20200126.txt). Also... I had to delete the DB because of this issue: Additional info when running in foreground:
|
I have the same problem, fresh install from : 3.0.4892 under ubuntu 16.04.3 |
same here, same output like fireheadman |
Cannot reproduce this issue on the latest version of ombi. Closing this for now as all the issues in here being raised are already covered above. If you think you genuinely have an issue please raise a new issue on github. |
Describe the bug
A clear and concise description of what the bug is.
Section
Movies
in Search tab doesn't show any movies and don't return any results after trying to search. There is no such problem inTV Shows
tab.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Movie propositions are displayed and search works.
Screenshots
Logs (Logs directory where Ombi is located)
I think this one is relevant:
Desktop (please complete the following information):
Ombi Version (please complete the following information):
Additional context
This happened after upgrade from
Ombi v3.0.4817
. Everything is run in containers usinglinuxserver/ombi
with persistent volume attached.Excerpt from docker-compose:
The text was updated successfully, but these errors were encountered: