Opened 11 years ago
Closed 9 years ago
#12033 closed Bug Report - General (Fixed)
mythmetadatalookup --refresh-all-artwork started by housekeeping no longer runs in master.
Reported by: | Owned by: | Karl Egly | |
---|---|---|---|
Priority: | minor | Milestone: | 0.27 |
Component: | MythTV - Housekeeper | Version: | Master Head |
Severity: | medium | Keywords: | |
Cc: | Ticket locked: | no |
Description
If the hostname for value 'DailyArtworkUpdates?' is set to a host (ofc0 in my case,) then housekeeping doesn't run mythmetadatalookup --refresh-all-artwork.
Changing the value of hostname to NULL re-enables --refresh-all-artwork.
The data field for both values of hostname equals '1'.
Attachments (1)
Change History (11)
Changed 11 years ago by
Attachment: | GoodArtworkRun.log added |
---|
comment:1 Changed 11 years ago by
Owner: | set to Raymond Wagner |
---|---|
Status: | new → accepted |
comment:4 Changed 11 years ago by
These two commits fix the hostname problem but they change the setting type from string to binary. Was that intended? I'm OK if it was but it made it look a bit weird in mysql when I was checking for the per-host setting.
comment:8 Changed 11 years ago by
I can confirm, that for some reason, I had a hostname in this field and it was preventing any artwork from being retrieved. Once I nulled out that field, everything worked great the next time the housekeeper ran.
If possible, the fix should either account for a field that has a hostname there (and ignore it?) or perhaps even NULL out the field for the users as part of an update.
comment:9 follow-up: 10 Changed 9 years ago by
Component: | MythTV - General → MythTV - Housekeeper |
---|---|
Milestone: | unknown → 0.28 |
Owner: | changed from Raymond Wagner to Karl Egly |
I'll see if I can come up with a schema update to fix old values in time for fixes/0.28.
comment:10 Changed 9 years ago by
Milestone: | 0.28 → 0.27 |
---|---|
Resolution: | → Fixed |
Status: | accepted → closed |
Replying to dekarl:
I see 6 things to consider:
DailyArtworkUpdates plus: | Action |
No entry in settings | Do nothing |
Single NULL host | Do nothing |
Single (non NULL) host | Convert hostname to NULL, assume old data is desired |
Single host and NULL host | Delete host setting |
Multiple hosts | Guess which frontend added the desired setting, convert 1, delete others |
Multiple hosts and NULL | Delete all non NULL entries |
The final solution for this was: changeset:e45e1ca on Feb 3, 2014.
After 2 years, it's likely that users will have fixed their entry (or configured it properly after the above fixes.)
And any conversion and especially guesses may not have the desired result. I can compare the sum of the non NULL host's data with the number of non NULL hosts and if it were 0 or the the same as the non NULL host count, then INSERT the NULL version of the setting.
I recall significant discussion on the -users list. Mostly from those that didn't want artwork, so automatically turning it on based on earlier (mis)settings wouldn't be good. Even if I add a warning in the release notes.
I'm closing this as fixed, please reopen if you disagree.
'Good' log and version: v0.28-pre-739-g7b9d369