[nSpectre]

OS:
Lubuntu 18.04.2 LTS

Problem:
tMM runs peachy-keen except when selecting menu, tinyMediaManager => Launch Updater

Symptoms:
tMM exits, tMM window appears with 0% progress and immediately displays message, "The application failed to launch due to some strange error from which we could not recover. Please visit" and the rest is obscured by the bottom window border. Window cannot be resized.

tMM.log:
https://paste.kodi.tv/doxaweralo.kodi

launcher.log:
https://paste.kodi.tv/ozebiqefod.kodi

Google Sez:
This is a message from com.threerings.getdown
 

---

My system stands ready to be a guinea pig, should you need one.

[mlaggner]

did you re-try to patch (running the tmm updater script from the tmm folder).. this can happen if our CDN is not completely in sync..

otherwise please have a look into the files "digest.txt" and "digest2.txt" if there is a stringe content (e.g. a link) in it

[nSpectre]

As it's been a few days, I backed up the "digest.txt" and digest2.txt" (below) associated with my original post and tried updating in the normal manner. It produced the same symptoms so I'm guessing it's not CDN related.

digest.txt: https://paste.kodi.tv/rowozacofe
digest2.txt: https://paste.kodi.tv/jaqiyodofi

I ran the tinyMediaManagerUpdater.sh script from the command line and it also produced the same symptoms. The following are the digest files associated with that test:

digest.txt: https://paste.kodi.tv/ilomuhujal
digest2.txt: https://paste.kodi.tv/amagihijes

Both file sets have the same file sizes.

I do not see anything in the digest files that look like a URL string.

launcher.log is still showing a "getdown() failed ... ArrayIndexOutOfBoundsException" warning

Potentially related, the last line of launcher.log is "INFO Releasing lock" yet a zero-byte "gettingdown.lock" file remains in the tMM folder. I have no idea if that has anything to do with anything but, far be it from me to interfere with someone getting down so I let it be.

[mlaggner]

ah okay, now I see it..
do you run tmm in some sort of docker instance? we had the same problem with our CI where we run getdown in a docker..

just make sure getdown is started with the jvm arg:

Code:

-Dthread_pool_size=1

I'll have a look if we can put that statically into all code occurances (but it work on >99% of the systems )

[nSpectre]

Nope. No Docker. Just a plain-jane Lubuntu install.

just make sure getdown is started with the jvm arg:

-Dthread_pool_size=1

Unfortunately, I do not know what that means. Is it something I should add to getdown.txt? ¯\_(ツ)_/¯
 

---

Edit:

ho-HO! Got it!

Adding it to getdown.txt didn't work. It just got overwritten when I reran the updater script. So, I changed the Updater script:

From: java -Djava.net.preferIPv4Stack=true -Dappbase=http://www.tinymediamanager.org/ -jar getdown.jar .
To: java -Dthread_pool_size=1 -Djava.net.preferIPv4Stack=true -Dappbase=http://www.tinymediamanager.org/ -jar getdown.jar .

(Note: I don't remember if that trailing period was there originally, I didn't add it, but it's there now)

That did the trick! The Updater ran fine from the command line and tMM is now firing on all 2.9.16 cylinders.

I do note that tinyMediaManagerUpdater.sh appears to have been overwritten and the jvm arg has been removed (and possibly the period added).

Thanks for your help.

[mlaggner]

Yes, the updater will remove that - you need to change it after every update until we change it for all :-(