I’m sorry if this is the wrong place for this, if it is, just let me know where I should post it and Ill repost there. Also, I’m quite the linux noob, so excuse me if my troubleshooting is missing something obvious. Thirdly, sorry if this is covered in another post somewhere. I used the search function and didnt see anything that covered this specifically
I’m using the Pi4 image at the top of this post on 2 different pi4s and have installed the latest patches. Creating an internal video database is fine, but when I create one on a mysql server I have hosted on a third pi I’m having problems. I can scan content and can see items being added to the MYSQL database from the progress bar in the gui and by querying the database directly, but I’m unable to view the library from my 2 OSMC nodes using the Movies shortcut. In the kodi.log I can see this error from when I attempt to browse ‘titles’ under Movies.
2021-06-12 16:03:13.004 T:979 ERROR <general>: SQL: [MyVideos119] The table does not exist
Query: select * from movie_view
I installed the mariadb sql client and connected to the database from the machine running OSMC and ran the failing query
select * from movie_view, and got the error:
ERROR 1146 (42S02): Table 'MyVideos119.movie_view' doesn't exist
I ran a
SHOW TABLES query and got the below output. There’s no movie_view table present
+-----------------------+ | Tables_in_MyVideos119 | +-----------------------+ | actor | | actor_link | | art | | bookmark | | country | | country_link | | director_link | | episode | | files | | genre | | genre_link | | movie | | movielinktvshow | | musicvideo | | path | | rating | | seasons | | sets | | settings | | stacktimes | | streamdetails | | studio | | studio_link | | tag | | tag_link | | tvshow | | tvshowlinkpath | | uniqueid | | version | | writer_link | +-----------------------+
This is a brand new database (I dropped my previous one during a moment of poor judgement after dealing with some corruption I couldn’t figure out how to resolve after I initially upgraded. In hindsight this may have been a rash decision). I created another new database to test on and saw the same behaviour on that as well. I’ve also rebuilt the OSMC nodes a few times from scratch.
Does this look like a bug in how the database is written to or am I doing something wrong? Can anyone else replicate this with a new database? I’d appreciate any help.