Film-Tech Forum ARCHIVE: Orphan Content on DSS200

This is topic Orphan Content on DSS200 in forum Digital Cinema Forum at Film-Tech Forum ARCHIVE.

To visit this topic, use this URL:
https://ft-forum.com/ft/cgi-bin/ubb/ultimatebb.cgi?ubb=get_topic;f=16;t=002455

Posted by Steve Kraus (Member # 476) on 10-27-2015, 01:32 PM:

I thought this had been discussed but I can't find it.

Dolby DSS-200 (4.3.5.13)

I deleted a movie but it's still listed in content and on the build menu. Content shows it < 1GB. "Purge" under server tools did not get rid of it. It will let you add it to a show. I don't see anything related via FTP though I may just not be recognizing it. Is this going to go away on the next reboot? (I have not had time yet so I realize this post may be a little premature.)

Posted by Marco Giustini (Member # 4544) on 10-27-2015, 02:57 PM:

Reboot and good luck.
Why Dolby can't make the database more robust, escapes me.

Posted by Leo Enticknap (Member # 534) on 10-27-2015, 03:37 PM:

Might the following work?

- In Show Manager, right-click on the DCP that refuses to die, select "Properties" and note the first few characters of the UUID

- Connect to the DSS200 using an FTP client

- Go to the "GeneratedPackages" folder

- Look for the folder with the same number as the UUID, then delete it

- Refresh the DCP listing in Show Manager, and see if that has nuked it. If not, reboot.

Posted by Steve Guttag (Member # 268) on 10-27-2015, 03:55 PM:

I do not believe you can delete (and I know you cannot add) to the generated packages folder (unless you have root level access).

Posted by Marco Giustini (Member # 4544) on 10-27-2015, 04:48 PM:

Why is it so easy to corrupt a Dolby database? I like Dolby's but I have never seen anything like this on a Doremi. At least it would be nice to have an option to say "delete the database and rebuild it" (no, the unconfigure script does not qualify as it also removes GPIO's or serial - yes I know they are easy-ish to back up but I'd like an easy way to just rest the thing without having to worry about losing settings!)
Or maybe a script to check the database integrity. It cannot be so hard to achieve!

Posted by Steve Kraus (Member # 476) on 10-27-2015, 05:48 PM:

I didn't see it in FTP but was probably not looking in the right place. Reboot took care of it. It's been up for at least a couple of months so long overdue for the periodic reboot. If that's the worst thing that happens with the not-exactly-recommended 4.3.5.13 that's not so bad. (Appendages crossed.)