Filebot Node installed, no longer starts?

[spurstastic]

Filebot Node has been working faultlessly but has decided it longer wants to start.

Status appears as: Stopped when viewed in the Package Centre.

The bottom half of the log reads:



Can anyone help please?

[kim]

It's say you have a DNS lookup problem....

change your dns servers... always add 2

[spurstastic]

I was already running Google DNS 8.8.8.8, so on your suggestion I switched to Open DNS 208.67.220.220 but Filebot Node still refuses to run.

Status: stopped.

Any other ideas please?

[rednoah]

The log you posted is for "Unofficial Java Installer". What does the log for "FileBot Node" say?

[spurstastic]

Apologies!

Please find below the correct screenshot:



Many thanks in advance x.

[rednoah]

You seem to be using a very old version of node that doesn't support one of the options.

Can you upgrade to a newer version of node?

[spurstastic]

I'm running 0.2.4 of Filebot Node...is there a newer version, and if so, can you forward the link please?

[rednoah]

Not FileBot Node, but the Node.js dependency that is required to run FileBot Node.

[spurstastic]

There are so many different version to choose from on the Package Centre: v0.10, v0.12, v4, v6, v8...in the end I choose v4 and it worked; Filebot Node has been restored.

Once again, many thanks!

[rednoah]

v0.10 won't work as far as I remember. v0.12 or newer should all be fine. The newer the better, probably.

[Fusion]

viewtopic.php?f=13&t=5920&p=34586#p34586

Node.js v8 on Synology does not handle the parameter "--max_executable_size=16" well, for whatever reason.

[rednoah]

Node.JS v8 compatibility has been fixed in the latest beta release:
https://github.com/filebot/filebot-node/releases