-
-
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
No search Movies, SQLite Error 1: 'no such column: x.RequestId'. #3214
Comments
Hi! |
Having exactly the same problem |
Yeah my bad! This has been fixed in the develop branch! 🎉 🎈 |
OK, now back to work correctly. 😃 |
I'm still getting this issue, can't do anything in ombi with hundreds of inputs of these in logs:
OS: Unraid docker |
Can confirm. seeing the same since last night at some point on latest. tried some reversions, still no joy |
same here |
It's been fixed in the latest version. |
Fixed! Many thanks. |
I noticed the same problem today but after updating to the latest version! |
Run build 4887, login and perform a search then use build 4892 |
just hit the issue, tried going back to 4887 performing a search then back to 4892 no joy using https://hub.docker.com/r/linuxserver/ombi/ |
I'm also on Docker and can't get it to install 4887 to perform a search. |
Didn't seem to be able to get any recent version working, rolled back to v3.0.4680 on Windows |
Bump, also not working for me |
After some searching, found the solution in this thread. 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 OR Just delete your |
@maximoosemine please read up. |
I'm on Ubuntu-ish Linux running build 3.0.4892 and I'm having this issue. It's not in a docker container. Should I roll back to a specific build? Some people are claiming the same issue on earlier builds. No offense meant, but I'm considering turning auto-update off as it's broken my setup for me about three times in the past few months. |
@dlynchcodes please read a few posts up on this issue. |
I found that I just needed to add that column to the PlexServerContent table and it's working now. |
@Sibicle Thanks for posting the solution, worked for me. |
Just wanted to share that I was able to use @Sibicle's solution to fix my ombi instance on my Unraid server. I had updated to 3.0.4892 but that didn't solve the problem. Using @Sibicle's command didn't quite work for me; I was getting an error saying |
if you are using linuxserver.io docker then the command is different you have to remove /app in the command line. |
I'm still having this issue on the macOS (osx) build. Followed what appear to be the recommended steps:
What exactly am I missing here? |
Using this on CentOS7 results with zsh: command not found: docker |
|
@Sibicle 's instructions explain this in much more detail, but the short version is:
|
I had this issue after upgrading to 3.0.5223 (
OS: unRAID 6.6.5 Thank you to @Sibicle, @Fredrik81, @freeload101, and @sarink for the solution(s)! |
Describe the bug
No search Movies.
To Reproduce
Screenshots
Logs (Logs directory where Ombi is located)
Desktop (please complete the following information):
Ombi Version (please complete the following information):
The text was updated successfully, but these errors were encountered: