bash-4.3# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 44
model name : Intel(R) Xeon(R) CPU           E5620  @ 2.40GHz
stepping : 2
microcode : 0x1
cpu MHz : 2400.084
cache size : 12288 KB
physical id : 0
siblings : 1
core id : 0
cpu cores : 1
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat 
pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm 
constant_tsc arch_perfmon rep_good nopl pni pclmulqdq ssse3 cx16 pcid 
sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes hypervisor lahf_lm
bogomips : 4800.16
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management:


Linux sds 3.10.0-327.18.2.el7.x86_64 #1 SMP Thu May 12 11:03:55 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

what to watch?

вторник, 27 сентября 2016 г., 15:29:17 UTC+9 пользователь M-MZ написал:
>
> I know this error. It happens when a nif tries to lock resources or start 
> threads on a erlang VM without SMP support. Travis used to have this in the 
> past.
>
> I don't know what you are running on, but check the SMP support of your VM.
>
> Regards,
>
> Maas
>
>
>
> On Monday, September 26, 2016 at 5:57:55 PM UTC+2, heiheshang wrote:
>>
>> enif_send: called from non-scheduler thread on non-SMP VM/opt/zotonic/src
>> /scripts/zotonic-debug: line 33:  1613 Aborted                 (core 
>> dumped) $ERL -env ERL_MAX_PORTS $MAX_PORTS +P $MAX_PROCESSES +K 
>> $KERNEL_POLL -pa $PA $NAME_ARG $NODENAME@$NODEHOST -boot start_sasl 
>> $(find_config_arg 
>> erlang.config) $(find_config_arg zotonic.config) -sasl errlog_type error 
>> -s zotonic
>>
>> I run docker
>>
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Zotonic developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to zotonic-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to