Under review

Испортилось ядро в роутере после недельной работы. Shutdown 1m-core (SIGSEGV).

5 years ago • updated by 5 years ago • 12

Tue Oct 15 22:37:01 2019 local0.info 1mcore[1746]: main: Starting 1M-Core version 0.1.5.20

Tue Oct 15 22:37:01 2019 local0.info 1mcore[1746]: client: initialized

Tue Oct 15 22:37:01 2019 local0.info 1mcore[1746]: server: initialized

Tue Oct 15 22:37:01 2019 local0.info 1mcore[1746]: control: initialized

Tue Oct 15 22:37:01 2019 local0.info 1mcore[1746]: scn: initialized

Tue Oct 15 22:37:01 2019 local0.info 1mcore[1746]: webserver: initialized

Tue Oct 15 22:37:01 2019 local0.info 1mcore[1746]: main: /etc/1m/conf

Tue Oct 15 22:37:01 2019 local0.info 1mcore[1746]: main: db_loadconf: -1

Tue Oct 15 22:37:01 2019 local0.info 1mcore[1746]: http: initialized

Tue Oct 15 22:37:01 2019 local0.info 1mcore[1746]: client: Can't open work certificate or pkey file, try to load root certificate

Tue Oct 15 22:37:15 2019 daemon.err uhttpd[1074]: luci: accepted login on /admin for root from 192.168.2.10

Tue Oct 15 22:37:16 2019 local0.info 1mcore[1746]: client: Can't open root certificate, need activate

Tue Oct 15 22:40:06 2019 daemon.err uhttpd[1074]: Collected errors:

Tue Oct 15 22:40:06 2019 daemon.err uhttpd[1074]: * opkg_conf_load: Could not lock /var/lock/opkg.lock: Resource temporarily unavailable.

Tue Oct 15 22:40:18 2019 local0.info 1mcore[1746]: main: Shutdown 1m-core

Tue Oct 15 22:40:18 2019 local0.info 1mcore[1746]: main: GracefulShutdown

Tue Oct 15 22:40:18 2019 local0.info 1mcore[1746]: main: 1m-daemon closed

Tue Oct 15 22:40:47 2019 local0.info 1mcore[1959]: main: Starting 1M-Core version 0.1.5.20

Tue Oct 15 22:40:47 2019 local0.info 1mcore[1959]: client: initialized

Tue Oct 15 22:40:47 2019 local0.info 1mcore[1959]: server: initialized

Tue Oct 15 22:40:47 2019 local0.info 1mcore[1959]: control: initialized

Tue Oct 15 22:40:47 2019 local0.info 1mcore[1959]: scn: initialized

Tue Oct 15 22:40:47 2019 local0.info 1mcore[1959]: webserver: initialized

Tue Oct 15 22:40:47 2019 local0.info 1mcore[1959]: main: /etc/1m/conf

Tue Oct 15 22:40:47 2019 local0.info 1mcore[1959]: main: db_loadconf: -1

Tue Oct 15 22:40:47 2019 local0.info 1mcore[1959]: http: initialized

Tue Oct 15 22:40:47 2019 local0.info 1mcore[1959]: client: Can't open work certificate or pkey file, try to load root certificate

Tue Oct 15 22:41:02 2019 local0.info 1mcore[1959]: client: Can't open root certificate, need activate

Tue Oct 15 22:41:51 2019 local0.info 1mcore[1959]: main: Start Activation

Tue Oct 15 22:41:52 2019 local0.info 1mcore[1959]: client: Connecting to 185.72.247.85...

Tue Oct 15 22:41:52 2019 local0.info 1mcore[1959]: client: Activation started

Tue Oct 15 22:41:52 2019 local0.info 1mcore[1959]: client: HEAD 1

Tue Oct 15 22:41:52 2019 local0.info 1mcore[1959]: client: ACT 2

Tue Oct 15 22:41:52 2019 local0.info 1mcore[1959]: client: len = 233 0 233 - 185

Tue Oct 15 22:41:52 2019 local0.info 1mcore[1959]: client: TIME 3

Tue Oct 15 22:41:52 2019 local0.info 1mcore[1959]: client: CRC 4 - 185

Tue Oct 15 22:41:52 2019 local0.info 1mcore[1959]: client: BEFORE CRYPT 4 - 250

Tue Oct 15 22:41:52 2019 local0.info 1mcore[1959]: client: 000000000A1405010014

Tue Oct 15 22:41:52 2019 local0.info 1mcore[1959]: client: 38364A5A85DFEF90F9DD

Tue Oct 15 22:41:52 2019 local0.info 1mcore[1959]: client: 90B30748C659CBEC15BD

Tue Oct 15 22:41:52 2019 local0.info 1mcore[1959]: client: 6609A74A090B5E73EF27

Tue Oct 15 22:41:52 2019 local0.info 1mcore[1959]: client: 3F85CBDF13DDD0BB8800

Tue Oct 15 22:41:52 2019 local0.info 1mcore[1959]: client: ENCRYPT 5

Tue Oct 15 22:41:52 2019 local0.info 1mcore[1959]: client: HEAD 6 - 0 - 16385

Tue Oct 15 22:41:52 2019 local0.info 1mcore[1959]: client: CLEN 7- 0 - 16385

Tue Oct 15 22:41:52 2019 local0.info 1mcore[1959]: client: CRC 8

Tue Oct 15 22:41:53 2019 local0.info 1mcore[1959]: client: arecv_getcert: starting

Tue Oct 15 22:41:53 2019 local0.info 1mcore[1959]: client: arecv_getcert: open pkey file SUCCESS

Tue Oct 15 22:41:53 2019 local0.info 1mcore[1959]: client: Device is successful activated, reconnect to server

Tue Oct 15 22:41:57 2019 local0.info 1mcore[1959]: client: Connecting to 185.72.247.85...

Tue Oct 15 22:41:57 2019 local0.info 1mcore[1959]: client: Connecting with root certificate

Tue Oct 15 22:41:58 2019 local0.info 1mcore[1959]: client: No work cert, try to download

Tue Oct 15 22:41:58 2019 local0.info 1mcore[1959]: main: spkt_decrypt: time is synchronized

Tue Oct 15 22:41:58 2019 local0.info 1mcore[1959]: client: arecv_getcert: starting

Tue Oct 15 22:41:58 2019 local0.info 1mcore[1959]: client: arecv_getcert: open pkey file SUCCESS

Tue Oct 15 22:41:58 2019 local0.info 1mcore[1959]: client: work cert successful downloaded

Tue Oct 15 22:41:58 2019 local0.info 1mcore[1959]: client: Connecting to 185.72.247.85...

Tue Oct 15 22:41:58 2019 local0.info 1mcore[1959]: client: Connecting with work certificate

Tue Oct 15 22:41:58 2019 local0.info 1mcore[1959]: client: Connected to server

Tue Oct 15 22:41:58 2019 local0.info 1mcore[1959]: client: cmd_sendversion: version sent

Tue Oct 15 22:41:58 2019 local0.info 1mcore[1959]: client: cmd_getsuntime: query sent

Tue Oct 15 22:41:58 2019 local0.info 1mcore[1959]: client: cmd_getconf: query sent

Tue Oct 15 22:41:59 2019 local0.info 1mcore[1959]: client: cmd_sendversion: version ack received

Tue Oct 15 22:41:59 2019 local0.info 1mcore[1959]: client: cmd_getsuntime: suntime received

Tue Oct 15 22:42:00 2019 local0.info 1mcore[1959]: client: cmd_getconf: next packet received - 1

Tue Oct 15 22:42:00 2019 local0.info 1mcore[1959]: client: cmd_getconf: all packets received

Tue Oct 15 22:42:00 2019 local0.info 1mcore[1959]: main: /etc/1m/conf

Tue Oct 15 22:42:00 2019 local0.info 1mcore[1959]: http: param 0

Tue Oct 15 22:42:00 2019 local0.info 1mcore[1959]: main: db_loadconf: save 16 channels states to file

Tue Oct 15 22:42:00 2019 local0.info 1mcore[1959]: main: fbd_init started

Tue Oct 15 22:42:00 2019 local0.info 1mcore[1959]: main: fbd_cnt: 0

Tue Oct 15 22:42:00 2019 local0.info 1mcore[1959]: main: fbd_init: 0

Tue Oct 15 22:42:00 2019 local0.info 1mcore[1959]: main: DBCONF 1 1

Tue Oct 15 22:42:00 2019 local0.info 1mcore[1959]: main: STATEGATE 65535 65535

Tue Oct 15 22:42:00 2019 local0.info 1mcore[1959]: client: cmd_sendversion: version sent

Tue Oct 15 22:42:00 2019 local0.info 1mcore[1959]: client: cmd_getsuntime: query sent

Tue Oct 15 22:42:00 2019 local0.info 1mcore[1959]: client: cmd_ctrlstate: device: 2, channel: 0, value: 0, bits: 0x20

Tue Oct 15 22:42:00 2019 local0.info 1mcore[1959]: client: cmd_ctrlstate: device: 2, channel: 1, value: 0, bits: 0x20

Tue Oct 15 22:42:00 2019 local0.info 1mcore[1959]: client: cmd_ctrlstate: device: 2, channel: 2, value: 0, bits: 0x00

Tue Oct 15 22:42:00 2019 local0.info 1mcore[1959]: client: cmd_ctrlstate: device: 0, channel: 3, value: 0, bits: 0x20

Tue Oct 15 22:42:00 2019 local0.info 1mcore[1959]: client: cmd_ctrlstate: device: 0, channel: 4, value: 0, bits: 0x20

Tue Oct 15 22:42:00 2019 local0.info 1mcore[1959]: client: cmd_ctrlstate: device: 0, channel: 5, value: 0, bits: 0x20

Tue Oct 15 22:42:00 2019 local0.info 1mcore[1959]: client: cmd_ctrlstate: device: 0, channel: 6, value: 0, bits: 0x20

Tue Oct 15 22:42:00 2019 local0.info 1mcore[1959]: client: cmd_ctrlstate: device: 1, channel: 7, value: 0, bits: 0x20

Tue Oct 15 22:42:00 2019 local0.info 1mcore[1959]: client: cmd_ctrlstate: device: 1, channel: 8, value: 0, bits: 0x20

Tue Oct 15 22:42:00 2019 local0.info 1mcore[1959]: client: cmd_ctrlstate: device: 1, channel: 9, value: 0, bits: 0x20

Tue Oct 15 22:42:00 2019 local0.info 1mcore[1959]: client: cmd_ctrlstate: device: 1, channel: 10, value: 0, bits: 0x20

Tue Oct 15 22:42:00 2019 local0.info 1mcore[1959]: client: cmd_ctrlstate: device: 1, channel: 11, value: 0, bits: 0x20

Tue Oct 15 22:42:00 2019 local0.info 1mcore[1959]: client: cmd_ctrlstate: device: 1, channel: 12, value: 0, bits: 0x20

Tue Oct 15 22:42:00 2019 local0.info 1mcore[1959]: client: cmd_ctrlstate: send states 13 of 16 channels

Tue Oct 15 22:42:00 2019 local0.info 1mcore[1959]: scn: SCNSTEP_TYPE_SETCHANNEL(1): scn:2 device: 2, channel: 0, value: 0

Tue Oct 15 22:42:00 2019 local0.info 1mcore[1959]: main: caught signal: Segmentation fault - restart

Tue Oct 15 22:42:00 2019 local0.info 1mcore[1959]: main: Shutdown 1m-core (SIGSEGV)

Vote

Replies 12
Oldest first
- Newest first
- Oldest first

Under review

5 years ago

Какие изменения выполняли в структуре или конфигурации?

5 years ago

игрался со сценариями в конфигураторе... и вдруг ядро перестало отвечать. Переустановка не помогает.

5 years ago

Какие сценарии?

5 years ago

Психанул и сбросил роутер. Поставил все заново. Активировал - все заработало. Извините, наверное все-таки проблемы с моей железякой.

5 years ago

Какой размер свободной памяти?

5 years ago

если речь о памяти программ, то роутер показывает порядка 2Мб, оперативка - порядка 30 Мб. Работает все как-то не очень стабильно... Надо больше?

5 years ago

Нет, достаточно.

Какой роутер? Cpuinfo покажите.

5 years ago

system type : Qualcomm Atheros QCA956X ver 1 rev 0 machine : TP-LINK Archer C60 v2 processor : 0 cpu model : MIPS 74Kc V5.0 BogoMIPS : 385.84 wait instruction: yes

microsecond timers: yes

tlb_entries: 32

extra interrupt vector: yes

hardware watchpoint: yes, count: 4, address/irw mask: [0x0ffc, 0x0ffc, 0x0ffb, 0x0ffb]

isa: mips1 mips2 mips32r1 mips32r2

ASEs implemented: mips16 dsp dsp2

shadow register sets: 1

kscratch registers: 0

package: 0

core: 0

VCED exceptions: not available

VCEI exceptions: not available

5 years ago

Вы знаете, тестово поэксплуатировав вашу облачную 1М у меня возник вопрос от которого будет зависеть оставаться ли на ней или искать другое решение. У меня бойлер, управляется через sonoff TH16, сценарии настроены на контроль температуры. К примеру, температура упала и ТН включил ТЭН бойлера. И тут возникает ситуация недоступности 1М ядра (упал роутер, поломалось ядро на нем, собака перегрызла сетевой шнурок и т.д.) - вопрос - ТН выключит бойлер, согласно сценарию или будет греть его до бесконечности? т.е. где хранится этот конкретный сценарий и кто выдает команду на отключение реле ТН?

5 years ago

в облачной сценарии работают в ядре.

для такой задачи Вам больше подходит 1М Smartphone (1msmart.com)

5 years ago

Спасибо за совет. То что нужно. Особенно прошивки со сдвигом точки комфорта в сценариях - красота, за полтарифа разогреть к утру бойлер, а с 7 утра вернуть режим экономии, просто здорово.

Если вы одна команда, то по моему нужно не распыляться и сосредоточиться на одной системе. зарабатывать можно, прикрутив к 1м смарту платные плюшки в виде удаленного управления и оповещения из того-же 1м облака. Готов платить разумные суммы за такое. Удачи вам.

5 years ago

Спасибо. Мы сейчас в основном сконцентрированы на 1М Smartphone, но облачный поддерживаем.

Удаленное управление и оповещения в 1М Smartphone есть. Оповещения реализуются через сценарии, пока только android push.

Поддержка проекта https://cloud.1msmart.com

Customer support service by UserEcho