delete task seems doing nothing

[dav1170]

everything is in the tittle.

here's the beginning of the log core log file

[11.08.2017 20:11:15] INFO org.yamj.jetty.Start - Using war file: lib/yamj3-core-3.0-SNAPSHOT.war
[11.08.2017 20:11:15] INFO org.yamj.jetty.Start -
[11.08.2017 20:11:15] INFO org.yamj.jetty.Start - Starting server...
[11.08.2017 20:11:15] INFO org.yamj.jetty.Start - Resource base: file:/foo/bar/.jukebox/core/resources/
[11.08.2017 20:11:15] INFO org.yamj.jetty.Start - Skins directory: resources/skins/
[11.08.2017 20:11:15] INFO org.eclipse.jetty.server.Server - jetty-8.1.16.v20140903
[11.08.2017 20:11:16] INFO org.eclipse.jetty.webapp.WebInfConfiguration - Extract jar:file:/foo/bar/.jukebox/core/lib/yamj3-core-3.0-SNAPSHOT.war!/ to /tmp/jetty-0.0.0.0-8888-yamj3-core-3.0-SNAPSHOT.war-_yamj3-any-/webapp
[11.08.2017 20:11:18] INFO /yamj3 - Set web app root system property: 'yamj3.root' = [/tmp/jetty-0.0.0.0-8888-yamj3-core-3.0-SNAPSHOT.war-_yamj3-any-/webapp]
[11.08.2017 20:11:18] INFO /yamj3 - Initializing log4j from [/tmp/jetty-0.0.0.0-8888-yamj3-core-3.0-SNAPSHOT.war-_yamj3-any-/webapp/WEB-INF/log4j.properties]
[11.08.2017 20:11:19] INFO /yamj3 - Initializing Spring FrameworkServlet 'yamj3'
[11.08.2017 20:11:21] INFO org.yamj.common.tools.PropertyTools - Loading properties file from class path resource [yamj3-core-static.properties]
[11.08.2017 20:11:21] INFO org.yamj.common.tools.PropertyTools - Loading properties file from file [/volume1/videos/.jukebox/core/config/yamj3-core-static.properties]
[11.08.2017 20:11:21] INFO org.yamj.common.tools.PropertyTools - Loading properties file from file [/volume1/videos/.jukebox/core/config/yamj3-core-static.user.properties]
[11.08.2017 20:11:21] INFO org.yamj.common.tools.PropertyTools - Loaded 112 properties
[11.08.2017 20:11:23] DEBUG org.jboss.logging - Logging Provider: org.jboss.logging.Log4jLoggerProvider
[11.08.2017 20:11:30] INFO org.yamj.core.config.LocaleService - YAMY locale: language=en, country=US
[11.08.2017 20:11:30] INFO org.yamj.core.config.LocaleService - YAMY lookup languages: 1257
[11.08.2017 20:11:30] INFO org.yamj.core.config.LocaleService - YAMY display languages: 2175
[11.08.2017 20:11:30] INFO org.yamj.core.config.LocaleService - YAMY lookup countries: 2326
[11.08.2017 20:11:30] INFO org.yamj.core.config.LocaleService - YAMY display countries: 4782
[11.08.2017 20:11:31] DEBUG org.yamj.core.web.WebConfiguration - Using download limits: .*=2,.imdb.=2,.google.=5,.yahoo.=5,.themoviedb.=3,.thetvdb.=2,.apple.=1,.*trailersland.com=1,.fanart.tv=2
[11.08.2017 20:11:31] INFO org.yamj.core.tools.AspectRatioTools - Initialize aspect ratio tools
[11.08.2017 20:11:32] DEBUG org.yamj.core.service.attachment.AttachmentScannerService - Initialize attachment scanner service
[11.08.2017 20:11:32] DEBUG org.yamj.core.service.attachment.AttachmentScannerService - MKV Toolnix Path : ./mkvToolnix
[11.08.2017 20:11:32] INFO org.yamj.core.service.attachment.AttachmentScannerService - Couldn't find MKV toolnix executable tool 'mkvinfo'
[11.08.2017 20:11:32] INFO org.yamj.core.service.file.FileStorageService - Resource path set to 'resources'
[11.08.2017 20:11:32] INFO org.yamj.core.service.file.FileStorageService - Artwork storage path set to 'resources/artwork/'
[11.08.2017 20:11:32] INFO org.yamj.core.service.file.FileStorageService - MediaInfo storage path set to 'resources/mediainfo/'
[11.08.2017 20:11:32] INFO org.yamj.core.service.file.FileStorageService - Photo storage path set to 'resources/photo/'
[11.08.2017 20:11:32] INFO org.yamj.core.service.file.FileStorageService - Skins storage path set to 'resources/skins/'
[11.08.2017 20:11:32] INFO org.yamj.core.service.file.FileStorageService - Trailer storage path set to 'resources/trailer/'
[11.08.2017 20:11:50] INFO ro.fortsoft.pf4j.DefaultPluginManager - PF4J version 0.13.1 in 'deployment' mode
[11.08.2017 20:11:50] INFO ro.fortsoft.pf4j.DefaultPluginStatusProvider - Enabled plugins: []
[11.08.2017 20:11:50] INFO ro.fortsoft.pf4j.DefaultPluginStatusProvider - Disabled plugins: []
[11.08.2017 20:11:50] INFO ro.fortsoft.pf4j.DefaultPluginManager - Plugin 'yamj3-plugin-imdb' resolved
[11.08.2017 20:11:50] INFO ro.fortsoft.pf4j.DefaultPluginManager - Plugin 'yamj3-plugin-ofdb' resolved
[11.08.2017 20:11:50] INFO ro.fortsoft.pf4j.DefaultPluginManager - Plugin 'yamj3-plugin-allocine' resolved
[11.08.2017 20:11:50] INFO ro.fortsoft.pf4j.DefaultPluginManager - Plugin 'yamj3-plugin-comingsoon' resolved
[11.08.2017 20:11:50] INFO ro.fortsoft.pf4j.DefaultPluginManager - Plugin 'yamj3-plugin-thetvdb' resolved
[11.08.2017 20:11:50] INFO ro.fortsoft.pf4j.DefaultPluginManager - Plugin 'yamj3-plugin-moviemeter' resolved
[11.08.2017 20:11:50] INFO ro.fortsoft.pf4j.DefaultPluginManager - Plugin 'yamj3-plugin-fanarttv' resolved
[11.08.2017 20:11:50] INFO ro.fortsoft.pf4j.DefaultPluginManager - Plugin 'yamj3-plugin-youtube' resolved
[11.08.2017 20:11:50] INFO ro.fortsoft.pf4j.DefaultPluginManager - Plugin 'yamj3-plugin-themoviedb' resolved
[11.08.2017 20:11:51] INFO ro.fortsoft.pf4j.DefaultPluginManager - Start plugin 'yamj3-plugin-imdb:3.0.3'
[11.08.2017 20:11:51] INFO ro.fortsoft.pf4j.DefaultPluginManager - Start plugin 'yamj3-plugin-ofdb:3.0.2'
[11.08.2017 20:11:51] INFO ro.fortsoft.pf4j.DefaultPluginManager - Start plugin 'yamj3-plugin-allocine:3.0.3'
[11.08.2017 20:11:51] INFO ro.fortsoft.pf4j.DefaultPluginManager - Start plugin 'yamj3-plugin-comingsoon:3.0.3'
[11.08.2017 20:11:51] INFO ro.fortsoft.pf4j.DefaultPluginManager - Start plugin 'yamj3-plugin-thetvdb:3.0.4'
[11.08.2017 20:11:51] INFO ro.fortsoft.pf4j.DefaultPluginManager - Start plugin 'yamj3-plugin-moviemeter:3.0.2'
[11.08.2017 20:11:51] INFO ro.fortsoft.pf4j.DefaultPluginManager - Start plugin 'yamj3-plugin-fanarttv:3.0.1'
[11.08.2017 20:11:51] INFO ro.fortsoft.pf4j.DefaultPluginManager - Start plugin 'yamj3-plugin-youtube:3.0.1'
[11.08.2017 20:11:51] INFO ro.fortsoft.pf4j.DefaultPluginManager - Start plugin 'yamj3-plugin-themoviedb:3.0.2'
[11.08.2017 20:11:51] INFO org.yamj.core.service.various.IdentifierService - Transliteration is not enabled
[11.08.2017 20:11:52] DEBUG org.yamj.core.service.metadata.extras.ExtrasScannerService - Initialize extras scanner
[11.08.2017 20:11:52] DEBUG org.yamj.core.service.artwork.ArtworkInitialization - Initialize artwork profiles
[11.08.2017 20:11:52] DEBUG org.yamj.core.service.mediainfo.MediaInfoService - Initialize MediaInfo service
[11.08.2017 20:11:52] DEBUG org.yamj.core.service.mediainfo.MediaInfoService - Operating System Name : Linux
[11.08.2017 20:11:52] DEBUG org.yamj.core.service.mediainfo.MediaInfoService - Operating System Version: 3.10.102
[11.08.2017 20:11:52] DEBUG org.yamj.core.service.mediainfo.MediaInfoService - Operating System Type : amd64
[11.08.2017 20:11:52] DEBUG org.yamj.core.service.mediainfo.MediaInfoService - Media Info Path : /foo/bar2/mediainfo/bin
[11.08.2017 20:11:52] INFO org.yamj.core.service.mediainfo.MediaInfoService - MediaInfo tool will be used to extract video data. But not RAR and ISO formats
[11.08.2017 20:11:52] DEBUG org.yamj.common.tools.SystemTools - IPv6 Address: foo
[11.08.2017 20:11:52] DEBUG org.yamj.common.tools.SystemTools - IPv4 Address: xxx.yyy.zzz.000

after running enqueue delete task from the %ip%:8888

[11.08.2017 20:13:32] DEBUG org.yamj.core.service.tasks.DeleteTask - Execute delete task
[11.08.2017 20:13:38] DEBUG org.yamj.core.service.tasks.DeleteTask - Finished delete task after 5764 ms

both before and after running task a select count(*) from videodata where status = 'DELETED' return result above 0 and they are deleted files are still displayed on the eversion skin (even if after a restart of the jukebox).

regards

[jluc2808]

look at the stage_file

[dav1170]

Hello Jluc,

Would you mind explain what is the stage file means?

Regards

[jluc2808]

in the db doesn't request with videodata but with stage_file , which is the db where jetty store the file from the scanner , and the status of the file done, deleted, updated

[jluc2808]

select count(*) from stage_file where status = 'DELETED

[jluc2808]

@dav1170 is that issue still alive ?

[dav1170]

hello @jluc2808

I'm currently doing some tests on a rebuilded database.
I'll give you a feedback soon.

[dav1170]

hello @jluc2808

I still have the same issue:

• I have deleted the database in mariadb (drop database)
• restart yamj3 core services
• when it was up, I launch a filescanner: no exception has been thrown
• after some time, my database has been rebuild
• I delete physically a movie
• I have launched another time the filescanner: no exception has been thrown
• I wait core logs does nothing anymore
• I have forced the execution of the delete task: in the core logs, I can see that delete tasks has been executed and finished
• in database, the movie is still flagged with status DONE
• I have launched another time the filescanner: no exception has been thrown
• I have put in my movie folder another version of the movie.
• I have launched the filescanner to load this new movie
• after core processing, I have two times the movies in eversion; In database I have two records of this movie with DONE status

Additionally I've tried to deleted this unexisting movie in database, (delete from videodata where id = 12 limit 1;), but a foreign key constraint does allow this kind of request:
Cannot delete or update a parent row: a foreign key constraint fails (db.artwork, CONSTRAINT FK_ARTWORK_VIDEODATA FOREIGN KEY (videodata_id) REFERENCES videodata (id))

regards

[jluc2808]

rem: as i said i my previous message don't request or update on videodata table , only on stage_file table

what version yamj3 are you using ?

to delete a movie from the referenced table (stage_file) , use bikini ,

• before any new action, make sure that the status of the movie is DONE (on the datil page , hit the mediainfo icon) , if so
• hit the delete icon on the top detail page of this movie , click on the popup to accept the delete state, i you the request de stage_file for this entry you will see the DELETED status , i don't remember but i think the status returned by the mediainfo windows when you click on mediainfo icon should show DELETED too, so the next deleted task should clean the stage-file and the videodata entry , if you have twice referenced the movie , you need to do this sequence twice.

otherwise : start jetty, start the filescanner with the right library , wait till the filescanner tells
Watching directory ''Your library" for changes...
[17.09.2017 18:33:18]INFO org.yamj.filescanner.tools.Watcher - Register Watcher for: "Your folder"
[17.09.2017 18:33:18]INFO org.yamj.filescanner.tools.Watcher - Enabling the watch process
then delete the movie from the folder or subfolder you are watching
the process should keep this info and it the jetty's task , then perform the delete action in jetty's process.

[dav1170]

Hello,

my yamj version is the following one: 2017-03-12 18:13:21 +0100 (It could be interesting to generate a new log file when the core instead of rotate log files according with size ?: it would be helpful to find the startup information).

I'm not able to use bikini: when I use it, even if I try to update or delete something (firefox 55 and chrome linux, I think the latest version of bikini), the confirm popin does nothing (I means, there is nothing added in the core log file). additionally, interface is very poor with my browser (I can't access to many menus and can"t display many things). This is the reason I try to update the database.

I've already tried to start the core and launch the filescanner, but if I search for "register watcher" in ALL my logs files, "register watcher" NEVER appear.

Additionally, after trying to update database, I think it could be interesting to use "ON DELETE CASCADE" for the foreign keys to avoid errors when trying to delete some wrong seasons or series.

Regards

[jluc2808]

hi, your version seems to be 282ecdb and is an old one , install the lastest 006e995 (del lib folder before)

• to restart a new log (it's a day log) , stop jetty , delete logs and restart jetty

• when using bikini , the delete action should show an api/update request

• as you havn't the last version the "register watcher" shouldn't appeared

• i'm using firefox 55 and chrome too and have no problem to access all menu , make sure you have setted a bikini_skin_0 or bikini_skin_1 in the configuration menu and in the style parameter select frame which is the more usefull with a windows OS (remove all cache too)

[dav1170]

Hello @jluc2808

I'm not sure but it seems that when I restart jetty it does not rotate the log file. I'll check.

regarding bikini, yes, I have a a confirmation popup displayed when I click on the delete button. But all the request made when I click on this confirmation popup failed in a 404 error.

I suppose that the Bikini configuration menu is the menu displayed when we click on the "i" button? Because when I click on this button button, nothing happen too. Is there a way to manage configuration differently?

regards

[jluc2808]

the log rotate when you're in an other day , follow my recommendation, rename the log when you stop jetty , you will get a brand new one

for bikini, it's like you didn't connect bikini and jetty
to start bikini , you have to launch yamj3's html with /ip_of_jetty_machine:8888/yamj3
then enter the skin entry , then launch bikini with the bikini entry Inside the page

if the bikini configuration icon doesn't work, the left frame let you enter the skin configuration menu