THJ

Members
  • Content Count

    15
  • Joined

  • Last visited

About THJ

  • Rank
    Member
  • Birthday 03/08/1981

Contact Methods

  • Website URL
    http://appinstaller.kralj.info/forum

Profile Information

  • Gender
    Not Telling
  1. THJ

    Mips Support

    +1 # cat /proc/cpuinfo system type : (null) processor : 0 cpu model : MIPS 24Kc V8.5 FPU V0.0 BogoMIPS : 502.98 wait instruction : yes microsecond timers : yes tlb_entries : 32 extra interrupt vector : yes hardware watchpoint : yes, count: 4, address/irw mask: [0x0818, 0x08e0, 0x0640, 0x0fd8] ASEs implemented : mips16 shadow register sets : 1 core : 0 VCED exceptions : not available VCEI exceptions : not available
  2. Yes then it works. Device no longer freezes. But this could be solved from inside application and not by running a command prior to starting btsync.
  3. Just tested version 1.1.82 and this bug is still present. Any ETA when we can expect a solution? Thank you.
  4. Or at least explanation if this will ever get fixed?
  5. Any other solution that wouldn't crash entire NAS?
  6. THJ

    Mips Support

    Another vote for MIPS version.
  7. I still have the same problem with ARM release. Alignment error which is fixed using "echo 2 > /proc/cpu/alignment". But as soon as btsync starts whole networking on NAS device crashes and I need to hard reset it.
  8. Another user that has same problems running latest version on ARM CPU based NAS: http://forum.bittorrent.com/topic/22654-btsync-1169-arm-alignment-error/ btsync freezes the NAS completly and with that can damage the data on HDD as it needs to be force restarted.
  9. btsync version 1.1.48 worked perfectly on Xtreamer eTRAYz NAS. But latest version 1.1.69 has problems and it crashes the entire NAS. I posted the problems with it here: http://forum.bittorrent.com/topic/22654-btsync-1169-arm-alignment-error/ It can be easily installed onto the NAS using my custom created project APP Installer: http://appinstaller.kralj.info/forum
  10. Hello again. This solution seems to be only valid for application to start. But after about 10 seconds when it starts the whole NAS will freeze and I have to reboot it. This is my btsync.conf: { "device_name": "eTRAYz NAS", "listening_port" : 0, "storage_path" : "/home/epkg/share/btsync/.sync", "pid_file" : "/home/epkg/share/btsync/.sync/btsync.pid", "check_for_updates" : true, "use_upnp" : true, "download_limit" : 0, "upload_limit" : 0, "webui" : { "listen" : "0.0.0.0:7777", "login" : "admin", "password" : "sysadmin" }, "shared_folders": [] } And this is how I start the process: /home/epkg/share/btsync/btsync --config /home/epkg/share/btsync/.sync/sync.conf I've tried to change the value in /proc/cpu/alignment to 3, 4 or 5 and with all the NAS freezes as soon as btsync process starts. Any other suggestion?
  11. Perfect solution. $ echo 2 > /proc/cpu/alignment $ ./btsync --help BitTorrent Sync 1.1.69 Thank you.
  12. While version 1.1.48 workes without any problems on my ARM NAS device, 1.1.69 doesn't want to start and exists with Alignment error. $ ./btsync Alignment error Here are last few lines of strace if it helps to debug the error: getrlimit(RLIMIT_STACK, {rlim_cur=8192*1024, rlim_max=RLIM_INFINITY}) = 0 brk(0) = 0x349000 brk(0x36a000) = 0x36a000 gettimeofday({1376379137, 723324}, NULL) = 0 mkdir("/tmp", 0777) = -1 EEXIST (File exists) mkdir("/tmp/btsync_dumps", 0777) = -1 EEXIST (File exists) gettimeofday({1376379137, 727732}, NULL) = 0 futex(0x3361e8, FUTEX_WAKE, 2147483647) = 0 sigaltstack(NULL, {ss_sp=0, ss_flags=SS_DISABLE, ss_size=0}) = 0 sigaltstack({ss_sp=0x3499e0, ss_flags=0, ss_size=8192}, NULL) = 0 rt_sigaction(SIGSEGV, NULL, {SIG_DFL, [], 0}, 8) = 0 rt_sigaction(SIGABRT, NULL, {SIG_DFL, [], 0}, 8) = 0 rt_sigaction(SIGFPE, NULL, {SIG_DFL, [], 0}, 8) = 0 rt_sigaction(SIGILL, NULL, {SIG_DFL, [], 0}, 8) = 0 rt_sigaction(SIGBUS, NULL, {SIG_DFL, [], 0}, 8) = 0 rt_sigaction(SIGSEGV, {0x14af0, [ILL ABRT BUS FPE SEGV], SA_STACK|SA_SIGINFO|0x4000000}, NULL, 8) = 0 rt_sigaction(SIGABRT, {0x14af0, [ILL ABRT BUS FPE SEGV], SA_STACK|SA_SIGINFO|0x4000000}, NULL, 8) = 0 rt_sigaction(SIGFPE, {0x14af0, [ILL ABRT BUS FPE SEGV], SA_STACK|SA_SIGINFO|0x4000000}, NULL, 8) = 0 rt_sigaction(SIGILL, {0x14af0, [ILL ABRT BUS FPE SEGV], SA_STACK|SA_SIGINFO|0x4000000}, NULL, 8) = 0 rt_sigaction(SIGBUS, {0x14af0, [ILL ABRT BUS FPE SEGV], SA_STACK|SA_SIGINFO|0x4000000}, NULL, 8) = 0 fstat64(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 1), ...}) = 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x4001f000 write(1, "Alignment error\n", 16Alignment error ) = 16 exit_group(1) LDD output looks ok: $ ldd btsync librt.so.1 => /lib/librt.so.1 (0x4002d000) libdl.so.2 => /lib/libdl.so.2 (0x4003c000) libm.so.6 => /lib/libm.so.6 (0x40047000) libpthread.so.0 => /lib/libpthread.so.0 (0x400f2000) libc.so.6 => /lib/libc.so.6 (0x40110000) /lib/ld-linux.so.3 (0x40000000) Any clue what changed that is preventing the new version to start? Thanks.
  13. Yes. My question was for Linux daemon. And I think I got it. killproc btsync seems to be enough and when I restart it with btsync --config /some/folder/sync.conf it will continue to sync preadded folder from my Windows PC. Works perfectly! Thank you again.
  14. Hello, Very nice application that also run on NAS with ARM CPU. But what is a proper stop procedure for the btsync daemon? killall btsync is enough? If it is started with btsync --config /some/folder/sync.conf and later new folders to sync are added, will when daemon is stopped this new folder be saved inside config file and resynced when daemon is started again? Thank you and looking forward to the new versions.