gritor Posted March 4, 2019 Share #26 Posted March 4, 2019 Hello, Is there any solution, for the detection of faces and objects, for the latest version? I have a HP N54L baremetal processor AMD Turion (tm) II Neo N54L Dual-Core Processor, with version 1.1.2-0511 works all right, but there are features of the latest version, which I would like to use. Quote Link to comment Share on other sites More sharing options...
Kollcn Posted March 30, 2019 Share #27 Posted March 30, 2019 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 Quote Link to comment Share on other sites More sharing options...
Kollcn Posted March 30, 2019 Share #28 Posted March 30, 2019 The Moments version 1.2.1-0646 works very well,When you upgrade to 1.3.0+,you will get the 'uncaught thread task exception' log,And faces and objects will never display Or only children categorie,Sometimes can recoganize faces but the number of photos must be not right. Quote Link to comment Share on other sites More sharing options...
Kollcn Posted April 2, 2019 Share #29 Posted April 2, 2019 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. Quote Link to comment Share on other sites More sharing options...
mcdull Posted April 2, 2019 Share #30 Posted April 2, 2019 On 3/30/2019 at 10:40 AM, Kollcn said: My setting. E3-1275 ESXi, CPU=4 Cores per Socket = 4: Sockets:1 On 3/30/2019 at 10:40 AM, Kollcn said: 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 Quote Link to comment Share on other sites More sharing options...
Kollcn Posted April 2, 2019 Share #31 Posted April 2, 2019 19 minutes ago, mcdull said: My setting. E3-1275 ESXi, CPU=4 Cores per Socket = 4: Sockets:1 Thanks for your reply.I've tried this setting,didn't work.I guess it need real 4 cores CPU. Quote Link to comment Share on other sites More sharing options...
mcdull Posted April 2, 2019 Share #32 Posted April 2, 2019 5 minutes ago, Kollcn said: Thanks for your reply.I've tried this setting,didn't work.I guess it need real 4 cores CPU. also try 3615 if you are in 3617. Quote Link to comment Share on other sites More sharing options...
Kollcn Posted April 3, 2019 Share #33 Posted April 3, 2019 9 hours ago, mcdull said: also try 3615 if you are in 3617. Oh,maybe it's a right way to change version to 3615,I'm in 918+.Thank you! Quote Link to comment Share on other sites More sharing options...
Kollcn Posted April 4, 2019 Share #34 Posted April 4, 2019 I reinstalled the version to DS3615xs,everything is perfect right now. My setting. Intel G5500T ESXi, CPU=4 Cores per Socket = 2: Sockets:2 Quote Link to comment Share on other sites More sharing options...
Kollcn Posted April 4, 2019 Share #35 Posted April 4, 2019 @mcdull Thanks for your help.:) Quote Link to comment Share on other sites More sharing options...
cyberwitch Posted May 28, 2019 Share #36 Posted May 28, 2019 Warning: If you're trying to hold on to Moments 1.1.2, don't allow your system to upgrade to DSM 6.2.2 - it will force you to upgrade to the latest version of Moments. DSM 6.2.1 is the last version to suppport Moments 1.1.2. Luckily I was able to downgrade DSM and I am currently trying to restore the old Moments database from a remote backup. 1 Quote Link to comment Share on other sites More sharing options...
pacemaker72 Posted June 1, 2019 Share #37 Posted June 1, 2019 With DSM 6.2.1-23824 Update 6- 3615xs(AMD) with moments 1.3.2 installed (genuine serial number fixed transcoding and video indexing) Two things are not working... 1. Categories except for CHILD 2. New pictures taken were not face discovered actively in people section (stuck..' says x amount of photos to be discovered' )...only fix is to reindex (guess default background indexing not working)....saw a lot of discussion with this bug elsewhere on stock boxes too and hope Synology will come up with a fix on this. Other than the above two bugs, facial recognition/tags/places/transcoding/videos work well with newer version too (just have to be patient after the update...2days in my case) I prefer newer versions (1.3x) compared to 1.12 because of HEIC support/shared photo library/similar photo grouping... Hope this helps someone Quote Link to comment Share on other sites More sharing options...
Andrii Posted September 3, 2019 Share #38 Posted September 3, 2019 When I'm uploading my HEIC photos from iPhone I can't open it in moments, I have error thumbnails. In synophoto.log files I see error: Server synophoto-task-center: /source/synophoto/src/daemon/task-center/metadata_index.cpp:471 parse metadata failed [/var/services/homes/admin/Drive/Moments/Web/2019-09-03/IMG_4287.HEIC] [the output of metadata-wrapper is empty] Any idea why it's not working? My DMS version: DSM 6.2.2-24922 Update 3 My loader Jun's 1.03b Quote Link to comment Share on other sites More sharing options...
imaleecher Posted January 14, 2020 Share #39 Posted January 14, 2020 On 4/4/2019 at 3:22 AM, Kollcn said: ESXi, CPU=4 Cores per Socket = 2: Sockets:2 Yes! Thank you @Kollcn and @mcdull. Subjects are now popping up after updating Cores per Socket in ESXi VM settings. Quote Link to comment Share on other sites More sharing options...
Jlozde Posted June 9, 2020 Share #40 Posted June 9, 2020 I have the exact same issue. I am running a bare metal installition. I believe, I also need to move to DS3615xs. Can anybody please show me how i can migrate to DS3615, I am currently on DS918+ Here is my CPUInfo its i3 7100 root@DATA:/dev# cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 158 model name : Intel(R) Core(TM) i3-7100 CPU @ 3.90GHz stepping : 9 microcode : 0x80 cpu MHz : 3900.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 : 22 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch invpcid_single intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 dtherm arat pln pts hwp hwp_notify hwp_act_window hwp_epp bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs bogomips : 7823.85 clflush size : 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 158 model name : Intel(R) Core(TM) i3-7100 CPU @ 3.90GHz stepping : 9 microcode : 0x80 cpu MHz : 3900.000 cache size : 3072 KB physical id : 0 siblings : 4 core id : 1 cpu cores : 2 apicid : 2 initial apicid : 2 fpu : yes fpu_exception : yes cpuid level : 22 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch invpcid_single intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 dtherm arat pln pts hwp hwp_notify hwp_act_window hwp_epp bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs bogomips : 7823.85 clflush size : 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management: processor : 2 vendor_id : GenuineIntel cpu family : 6 model : 158 model name : Intel(R) Core(TM) i3-7100 CPU @ 3.90GHz stepping : 9 microcode : 0x80 cpu MHz : 3900.000 cache size : 3072 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 2 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 22 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch invpcid_single intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 dtherm arat pln pts hwp hwp_notify hwp_act_window hwp_epp bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs bogomips : 7823.85 clflush size : 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 158 model name : Intel(R) Core(TM) i3-7100 CPU @ 3.90GHz stepping : 9 microcode : 0x80 cpu MHz : 3900.000 cache size : 3072 KB physical id : 0 siblings : 4 core id : 1 cpu cores : 2 apicid : 3 initial apicid : 3 fpu : yes fpu_exception : yes cpuid level : 22 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch invpcid_single intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 dtherm arat pln pts hwp hwp_notify hwp_act_window hwp_epp bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs bogomips : 7823.85 clflush size : 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management: Quote Link to comment Share on other sites More sharing options...
Jamzor Posted June 16, 2020 Share #41 Posted June 16, 2020 So will latest moments work on latest DSM for a 3617xs ? For me now I have genuine serial and moment works but not for face recognition.. Quote Link to comment Share on other sites More sharing options...
Jamzor Posted June 24, 2020 Share #42 Posted June 24, 2020 On 4/4/2019 at 10:22 AM, Kollcn said: I reinstalled the version to DS3615xs,everything is perfect right now. My setting. Intel G5500T ESXi, CPU=4 Cores per Socket = 2: Sockets:2 On 4/2/2019 at 5:56 PM, mcdull said: My setting. E3-1275 ESXi, CPU=4 Cores per Socket = 4: Sockets:1 Do you guys now how to set it for DS3617xs . It is originally a 4c8t CPU. My E5-2690 v2 is a 10c 20t in case that matthers. I dont get moments face recogintion to work but I have valid serial number and activation is correct.. I just have ESXi on 8vCPU and didnt touch the socket setting so far.. Quote Link to comment Share on other sites More sharing options...
Jlozde Posted June 26, 2020 Share #43 Posted June 26, 2020 On 6/24/2020 at 10:26 AM, Jamzor said: Do you guys now how to set it for DS3617xs . It is originally a 4c8t CPU. My E5-2690 v2 is a 10c 20t in case that matthers. I dont get moments face recogintion to work but I have valid serial number and activation is correct.. I just have ESXi on 8vCPU and didnt touch the socket setting so far.. Fixed with this 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.