Filebot crashing on movie matching Ubuntu 12.04

Any questions? Need some help?
Post Reply
knuw
Posts: 3
Joined: 09 Aug 2014, 12:19

Filebot crashing on movie matching Ubuntu 12.04

Post by knuw »

Hello,

I am new to Ubuntu learning Linux. One my favourite tools is Filebot and it has worked flawlessly up until 2 nights ago. For some reason anytime I try and match a movie to a database (any of them) Filebot crashes.

I have come to understand if you start a GUI'd app via Terminal when it ends it outputs any relevant info so that's what I pasted in below along with the sysinfo request as stated in the instructions for requesting help.

It all looks java related but if that's what Filebot is built on it's no surprise that's where the error is, at least I'd assume as much.

I'm on Ubuntu 12.04 and I've tried a variation of file types and sizes and I always get the same results. It also makes no difference if I choose symlinks, hardlinks, etc as the output though my requested output is/are symlinks.

Here's the sysinfo:

filebot -script fn:sysinfo
FileBot 4.2 (r2326)
JNA Native: 4.0.0
MediaInfo: MediaInfoLib - v0.7.69
7-Zip-JBinding: OK
chromaprint-tools: fpcalc version 1.1.0 (/usr/share/filebot/fpcalc)
Extended Attributes: OK
Groovy Engine: 2.3.4
JRE: OpenJDK Runtime Environment 1.7.0_55
JVM: 64-bit OpenJDK 64-Bit Server VM
CPU/MEM: 2 Core / 494 MB Max Memory / 15 MB Used Memory
OS: Linux (amd64)
uname: Linux cube 2.6.32-042stab062.2 #1 SMP Wed Oct 10 18:28:35 MSK 2012 x86_64 x86_64 x86_64 GNU/Linux
Done ?(?????)?

Here's the terminal output:

/usr/bin/filebot: line 2: 6752 Killed java -Dunixfs=false -DuseGVFS=false -DuseExtendedFileAttributes=true -DuseCreationDate=false -Djava.net.useSystemProxies=false -Dsun.net.client.defaultConnectTimeout=10000 -Dsun.net.client.defaultReadTimeout=60000 -Djna.nosys=true -Dapplication.deployment=deb -Dapplication.analytics=true -Dapplication.dir=$HOME/.filebot -Djava.io.tmpdir=$HOME/.filebot/temp -Djna.library.path=/usr/share/filebot -Djava.library.path=/usr/share/filebot -Dnet.filebot.AcoustID.fpcalc=/usr/share/filebot/afpcalc -jar /usr/share/filebot/FileBot.jar "$@"

I hope that's enough information.

The only thing I can think to do is update Java which seems like a rather desperate actions. Any advice would be great. I should state in advance, again, that Ubuntu / Linux is not my best skillset so if you have any special commands or suggestions I'm happy to execute but I'll need a bit of support in typing the right things into Terminal.

Thanks!

(p.s. I noticed my Firefox suddenly started crashing constantly as well, could be unrelated, hard to say.) :?
User avatar
rednoah
The Source
Posts: 23940
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: Filebot crashing on movie matching Ubuntu 12.04

Post by rednoah »

This is odd:

/usr/bin/filebot: line 2: 6752 Killed

Looks like you killed the process. Or the system killed the process. But jvm crash reports look very different and issues with Java code give you detailed stack trace reports. So doesn't look like a crash either JVM or FileBot to me.
:idea: Please read the FAQ and How to Request Help.
knuw
Posts: 3
Joined: 09 Aug 2014, 12:19

Re: Filebot crashing on movie matching Ubuntu 12.04

Post by knuw »

Hmm.. So you're thinking it's something else in the system, unrelated to Filebot?

When Firefox crashes it sometimes, also says "Killed" in the terminal output.

Perhaps I have a serial killer inside my system.

Any generic recommendations?

I did notice on the last attempt to the get the name of a movie with Filebot it had this to say:

WARNING: Failed To grep IMDbID: <name of movie>

After that same error as posted above, Killed with a different process number.
knuw
Posts: 3
Joined: 09 Aug 2014, 12:19

Re: Filebot crashing on movie matching Ubuntu 12.04

Post by knuw »

I think I sussed this. It seems I was just running out of memory on my box, Plex + Firefox + Dropbox = .96GB RAM on a 1GB RAM box. Then add on the remote GUI connection and it was just too much. As soon as I restarted the machine and SSH'd in everything seemed fine again. +1 for the command line.
Post Reply