[btsync just dies]

Have you tried updating to the latest version - 1.0.132?

Yea, I just updated to 1.0.132 and same issues. It may likely be due to memory as referenced above.

Thanks!

[btsync just dies]

If Linux just says "Killed" that's probably the OOM killer.

How big is your 'sync.dat' file ? (Possibly .sync/sync.dat) How much memory in the machine?

This http://forum.bittorr...-syncapp-issue/ shows you how to turn on debug logging.

NB: OOM = Out Of Memory

Thanks for the reply.

The sync.dat is about 75MB, the machine has 2GB memory

I tried to turn on debug logging, but it looks like it's not starting or initiated to do any debugging.

I do wonder if OOM is the potential culprit.

thanks!

[btsync just dies]

It was working for a while, then today I noticed that it wasn't running anymore on my linux server.

Running on 1.0.116

If I run

./btsync --config sync.confit just dies after a few seconds.

My sync.log is 0 bytes

If I try and run

./btsync --config sync.conf --nodaemonIt runs for a few seconds and then just says "Killed"

again sync.log is 0 bytes

32-bit btsync on a 3.4.36 kernel

thanks!

• 
  

• 
  

[NAS Advanced Application Settings]

Tried that, actually tried multiple combinations of comas at different locations and still the same error. I need to know what the format is that btsync is expecting. I noticed other settings have the following format

"webui" :

{

"listen" : "0.0.0.0:8888"

"login" : "admin"

"password" : "password"

}

Is btsync expecting this format for advanced settings? If so, what is the format structure? There is no documentation on it that I can find anywhere.

I got it working by just adding a comma before ,"disk_low_priority"

the app started, whether it took the configs I am not sure yet.