Jump to content
XPEnology Community

Kollcn

Transition Member
  • Posts

    7
  • Joined

  • Last visited

Posts posted by Kollcn

  1. On 1/24/2019 at 5:01 PM, Designator said:
    
    cat /proc/cpuinfo
    processor       : 0
    vendor_id       : GenuineIntel
    cpu family      : 6
    model           : 60
    model name      : Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz
    stepping        : 3
    microcode       : 0x19
    cpu MHz         : 3400.000
    cache size      : 3072 KB
    physical id     : 0
    siblings        : 4
    core id         : 0
    cpu cores       : 2
    apicid          : 0
    initial apicid  : 0
    fpu             : yes
    fpu_exception   : yes
    cpuid level     : 13
    wp              : yes
    flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmo pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdt scp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc ap erfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm arat invpcid_single pln pts dtherm retpoline tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt

    So I´ve been having the same problem that only places is being indexed and everything else remains "indexing" as displayed on the web but in fact the sevice stopped.

    Above is my cpuinfo. I´m currently running a DS918+ build with Jun´s Loader 1.04

     

     

    The last few lines of /var/log/synophoto.log show that an error occures but I´m not able to identify what´s really going on. Any ideas ?

    
    2019-01-24T09:49:21+01:00 iDisk synophoto-task-center: /source/synophoto/src/daemon/task-center/plugin-monitor/sended_task_queue_base.cpp:77 Plugin         Monitor timeout restart Plugin pkg-SynologyMoments-concept
    2019-01-24T09:49:21+01:00 iDisk synophoto-task-center: /source/synophoto/src/daemon/task-center/plugin-monitor/sended_task_queue.cpp:93 Plugin wake         up pkg-SynologyMoments-concept, clean task
    2019-01-24T09:49:21+01:00 iDisk synophoto-task-center: /source/synophoto/src/daemon/task-center/plugin-monitor/sended_task_queue.cpp:96 Delete task         user_id 1, unit_id 3899, type 6
    2019-01-24T09:49:21+01:00 iDisk synophoto-task-center: /source/synophoto/src/daemon/task-center/plugin-monitor/sended_task_queue.cpp:96 Delete task         user_id 1, unit_id 3900, type 6
    2019-01-24T09:49:21+01:00 iDisk synophoto-task-center: /source/synophoto/src/daemon/task-center/plugin-monitor/sended_task_queue.cpp:96 Delete task         user_id 1, unit_id 3901, type 6
    2019-01-24T09:49:21+01:00 iDisk synophoto-task-center: /source/synophoto/src/daemon/task-center/plugin-monitor/sended_task_queue.cpp:96 Delete task         user_id 1, unit_id 3902, type 6
    2019-01-24T09:49:21+01:00 iDisk synophoto-task-center: /source/synophoto/src/daemon/task-center/plugin-monitor/sended_task_queue.cpp:96 Delete task         user_id 1, unit_id 3904, type 6
    2019-01-24T09:49:21+01:00 iDisk synophoto-concept: /source/synophoto-plugin-detection/src/detection/plugin.cpp:21 detection plugin init
    2019-01-24T09:49:22+01:00 iDisk synophoto-concept: uncaught thread task exception /source/synophoto/src/daemon/plugin/plugin_worker.cpp:102 plugin         init failed: /var/packages/SynologyMoments/target/usr/lib/libsynophoto-plugin-detection.so
    2019-01-24T09:49:22+01:00 iDisk synophoto-concept: /source/synophoto-plugin-detection/src/detection/plugin.cpp:21 detection plugin init
    2019-01-24T09:49:22+01:00 iDisk synophoto-concept: uncaught thread task exception /source/synophoto/src/daemon/plugin/plugin_worker.cpp:102 plugin         init failed: /var/packages/SynologyMoments/target/usr/lib/libsynophoto-plugin-detection.so
    2019-01-24T09:49:22+01:00 iDisk synophoto-concept: /source/synophoto-plugin-detection/src/detection/plugin.cpp:21 detection plugin init
    2019-01-24T09:49:22+01:00 iDisk synophoto-concept: uncaught thread task exception /source/synophoto/src/daemon/plugin/plugin_worker.cpp:102 plugin         init failed: /var/packages/SynologyMoments/target/usr/lib/libsynophoto-plugin-detection.so
    2019-01-24T09:49:22+01:00 iDisk synophoto-concept: /source/synophoto-plugin-detection/src/detection/plugin.cpp:21 detection plugin init
    2019-01-24T09:49:22+01:00 iDisk synophoto-concept: uncaught thread task exception /source/synophoto/src/daemon/plugin/plugin_worker.cpp:102 plugin         init failed: /var/packages/SynologyMoments/target/usr/lib/libsynophoto-plugin-detection.so
    2019-01-24T09:49:22+01:00 iDisk synophoto-concept: /source/synophoto-plugin-detection/src/detection/plugin.cpp:21 detection plugin init
    2019-01-24T09:49:22+01:00 iDisk synophoto-concept: uncaught thread task exception /source/synophoto/src/daemon/plugin/plugin_worker.cpp:102 plugin         init failed: /var/packages/SynologyMoments/target/usr/lib/libsynophoto-plugin-detection.so
    

     

    **Update** I just did a downgrade as cyberwitch suggested to version Moments 1.1.2-0511 and started a re-indexing. As of now the first categories and the people ablum are being populated. So one of the updates broke the detection. 

    My logs is the same to yours.And I'm using intel G5500T,like your i3-4130,2 cores 4 siblings,maybe need real 4 cores cpu?the same to J3455 on 918+.maybe I should try i3-8100t or other real 4 cores cpu.

  2. On 1/25/2019 at 11:10 AM, mcdull said:

    Woo... I got it solved.!!!!! 

    thanks for @Designator to tell me that he got the same issue while he got a new CPU.

    Then I looked into others set up again and checked the log.

     

    /run/synophoto/concept.socket] construct failed: connect: Connection refused  

     

    This line drew my attention and I believe it is all related to the setting of hypervisors.

    It seems that the software tried to connected to something that failed.. which is in terms of sockets.

     

    It turns out to be the "NUMBER OF CORES" has to match with the identified CPU.  I always assign 2 cores in previous setting. Now, with 4 cores, subjects now popping out real fast.!!!!!!!!

     

    Can you post your settings on ESXI? I tried set cpu settings to 2  cores and 4 cores and others.the log always returns like:

    p.s  I am using 1.04b loader and DSM 6.2.1-23824 Update 6 under ESXi 6.7.0

    synophoto-concept: uncaught thread task exception /source/synophoto/src/daemon/plugin/plugin_worker.cpp:102 plugin init failed: /var/packages/SynologyMoments/target/usr/lib/libsynophoto-plugin-detection.so

     

×
×
  • Create New...