SUPLA Cloud v2.3.2 - SUPLA Server is down.

[cosmita]

Witam,

Aktualizacja przeszła bez problemów, po ponownym uruchomieniu supli na serwerze wszystko niby działa, sonoffy się łączą, można nimi sterować ale po wejściu do panelu supla-cloud w zakładkach: moja supla i smartfony otrzymuję komunikat na żółtym tle:

SUPLA Server is down.

nie wyświetla moja supla / kanały cały czas próbuje i nic.

odpalane ./supla.sh restart nie pomaga

Co można w tej kwestii poradzić?

pozdrawiam

[lesny8]

Zaloguj się do cloud przez HTTPS a nie HTTP

[cosmita]

Hej,

Nie w tym rzecz, łączę się po https dokładnie tak:

https://192.168.1.3:20443

pozdrawiam

[lesny8]

Pokaż status kontenerów i logi

Code: Select all

docker ps
docker logs --tail=50 supla-server
docker logs --tail=50 supla-cloud

[cosmita]

Hej,

podaję poniżej

Code: Select all

docker ps
CONTAINER ID        IMAGE                        COMMAND                  CREATED             STATUS              PORTS                                          NAMES
c5a92b51c0e0        supla/supla-server:arm32v7   "/usr/bin/server-ent…"   12 hours ago        Up 12 hours         0.0.0.0:2015-2016->2015-2016/tcp               supla-server
e3be8d8bf188        supla/supla-cloud:arm32v7    "docker-php-entrypoi…"   12 hours ago        Up 12 hours         0.0.0.0:2080->80/tcp, 0.0.0.0:20443->443/tcp   supla-cloud
96a9cd8753d3        suplascripts_suplascripts    "docker-php-entrypoi…"   6 months ago        Up 4 weeks          0.0.0.0:3080->80/tcp, 0.0.0.0:30443->443/tcp   suplascripts
476369b39685        hypriot/rpi-mysql:5.5        "/entrypoint.sh mysq…"   6 months ago        Up 4 weeks          3306/tcp                                       suplascripts-db
1ec2f2be96d0        hypriot/rpi-mysql:5.5        "/entrypoint.sh mysq…"   6 months ago        Up 12 hours         3306/tcp                                       supla-db

kolejna komenda

Code: Select all

docker logs --tail=50 supla-server
INFO[1553199721.929262] Started at Thu Mar 21 20:22:01 2019
ERR[1553199721.957631] Incorrect database version!
2019-03-21 20:22:01,967 INFO exited: supla-scheduler (exit status 1; not expected)
ERR[1553199721.999682] Incorrect database version!
2019-03-21 20:22:02,002 INFO gave up: supla-scheduler entered FATAL state, too many start retries too quickly
2019-03-21 20:22:02,009 INFO exited: supla-server (exit status 1; not expected)
2019-03-21 20:22:03,014 INFO gave up: supla-server entered FATAL state, too many start retries too quickly
2019-03-21 20:34:46,232 WARN received SIGTERM indicating exit request
2019-03-21 20:35:38,312 CRIT Supervisor running as root (no user in config file)
2019-03-21 20:35:38,359 INFO supervisord started with pid 1
2019-03-21 20:35:39,372 INFO spawned: 'supla-scheduler' with pid 9
2019-03-21 20:35:39,388 INFO spawned: 'supla-server' with pid 10
INFO[1553200539.467550] Scheduler version 2.3.1
INFO[1553200539.468243] Started at Thu Mar 21 20:35:39 2019
INFO[1553200539.472621] Server version 2.3.1 [Protocol v10]
INFO[1553200539.473279] Started at Thu Mar 21 20:35:39 2019
INFO[1553200539.561473] SSL version: OpenSSL 1.0.1t  3 May 2016
ERR[1553200539.615092] Can't bind ipc socket
INFO[1553200539.742609] Connection accepted: 109.173.137.152:41729 ClientSD: 10 Secure: 1
INFO[1553200539.824053] Cipher: AES256-GCM-SHA384, ClientSD: 10
INFO[1553200540.444526] Client registered. ClientSD: 10 Protocol Version: 9
2019-03-21 20:35:40,446 INFO success: supla-scheduler entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-03-21 20:35:40,447 INFO success: supla-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
INFO[1553200549.311235] Connection accepted: 192.168.100.50:46182 ClientSD: 13 Secure: 1
INFO[1553200549.480825] Cipher: AES128-SHA, ClientSD: 13
INFO[1553200549.575952] Connection accepted: 192.168.100.19:19408 ClientSD: 16 Secure: 1
INFO[1553200549.627758] Connection accepted: 192.168.100.98:49486 ClientSD: 19 Secure: 1
INFO[1553200549.737823] Cipher: AES128-SHA, ClientSD: 16
INFO[1553200549.793154] Cipher: AES128-SHA, ClientSD: 19
INFO[1553200550.483688] Device registered. ID: 1, ClientSD: 13 Protocol Version: 7
INFO[1553200550.511299] Device registered. ID: 3, ClientSD: 16 Protocol Version: 7
INFO[1553200550.539906] Device registered. ID: 2, ClientSD: 19 Protocol Version: 7
INFO[1553200670.417764] Connection accepted: 109.173.137.152:41731 ClientSD: 23 Secure: 1
INFO[1553200670.484701] Cipher: AES256-GCM-SHA384, ClientSD: 23
INFO[1553200670.751595] Client registered. ClientSD: 23 Protocol Version: 9
INFO[1553201306.875103] Connection accepted: 109.173.137.152:41733 ClientSD: 12 Secure: 1
INFO[1553201306.965989] Cipher: AES256-GCM-SHA384, ClientSD: 12
INFO[1553201307.631853] Client registered. ClientSD: 12 Protocol Version: 9
INFO[1553201317.221888] Connection accepted: 109.173.137.152:41736 ClientSD: 20 Secure: 1
INFO[1553201317.286462] Cipher: AES256-GCM-SHA384, ClientSD: 20
INFO[1553201318.175421] Client registered. ClientSD: 20 Protocol Version: 9
INFO[1553208547.543113] Connection accepted: 109.173.137.152:41798 ClientSD: 12 Secure: 1
INFO[1553208547.827745] Cipher: AES256-GCM-SHA384, ClientSD: 12
INFO[1553208548.301118] Client registered. ClientSD: 12 Protocol Version: 9
ERR[1553209200.228219] IPC connect error 2
ERR[1553209206.356547] IPC connect error 2
INFO[1553236408.327384] Connection accepted: 193.188.22.56:1332 ClientSD: 20 Secure: 1
INFO[1553236513.585417] Connection accepted: 193.188.22.56:784 ClientSD: 9 Secure: 0
INFO[1553236749.765292] Connection accepted: 193.188.22.56:1464 ClientSD: 12 Secure: 1
INFO[1553236873.719341] Connection accepted: 193.188.22.56:852 ClientSD: 20 Secure: 0

i ostatnia

Code: Select all

docker logs --tail=50 supla-cloud
supla:clean:passed-io-client-registration-dates: RUN:
Client registration expiration date - cleared: 0
I/O Device registration expiration date - cleared: 0
supla:clean:disable-demo-client-apps: RUN:
Clients to disable: 0
supla:clean:passed-io-client-registration-dates: RUN:
Client registration expiration date - cleared: 0
I/O Device registration expiration date - cleared: 0
supla:clean:disable-demo-client-apps: RUN:
Clients to disable: 0
supla:clean:passed-io-client-registration-dates: RUN:
Client registration expiration date - cleared: 0
I/O Device registration expiration date - cleared: 0
supla:clean:disable-demo-client-apps: RUN:
Clients to disable: 0
supla:clean:passed-io-client-registration-dates: RUN:
Client registration expiration date - cleared: 0
I/O Device registration expiration date - cleared: 0
supla:clean:disable-demo-client-apps: RUN:
Clients to disable: 0
supla:clean:passed-io-client-registration-dates: RUN:
Client registration expiration date - cleared: 0
I/O Device registration expiration date - cleared: 0
supla:clean:disable-demo-client-apps: RUN:
Clients to disable: 0
supla:clean:passed-io-client-registration-dates: RUN:
Client registration expiration date - cleared: 0
I/O Device registration expiration date - cleared: 0
supla:clean:disable-demo-client-apps: RUN:
Clients to disable: 0
supla:clean:passed-io-client-registration-dates: RUN:
Client registration expiration date - cleared: 0
I/O Device registration expiration date - cleared: 0
supla:clean:disable-demo-client-apps: RUN:
Clients to disable: 0
supla:clean:passed-io-client-registration-dates: RUN:
Client registration expiration date - cleared: 0
I/O Device registration expiration date - cleared: 0
supla:clean:disable-demo-client-apps: RUN:
Clients to disable: 0
supla:clean:passed-io-client-registration-dates: RUN:
Client registration expiration date - cleared: 0
I/O Device registration expiration date - cleared: 0
supla:clean:disable-demo-client-apps: RUN:
Clients to disable: 0
supla:clean:passed-io-client-registration-dates: RUN:
Client registration expiration date - cleared: 0
I/O Device registration expiration date - cleared: 0
supla:clean:disable-demo-client-apps: RUN:
Clients to disable: 0

[lesny8]

Próbowałeś usunąć i przebudować cache?

Code: Select all

docker exec supla-cloud rm -fr var/cache/* 
docker exec -u www-data supla-cloud php bin/console cache:warmup 

[cosmita]

Witam,

odpalone, najpierw oczywiście usunięte wedle zaleceń

Code: Select all

docker exec -u www-data supla-cloud php bin/console cache:warmup

 // Warming up the cache for the prod environment with debug
 // false

 [OK] Cache for the "prod" environment (debug=false) was successfully warmed.

przy czym ja w katalogu supla-docker w var mam tylko to:

Code: Select all

ls -la var
razem 20
drwxr-xr-x 4 pi  pi    4096 wrz 21 08:35 .
drwxr-xr-x 5 pi  pi    4096 wrz 23 20:33 ..
drwxr-xr-x 2 pi  pi    4096 mar 22 11:05 backups
-rw-r--r-- 1 pi  pi      14 wrz 11  2018 .gitignore
drwxr-xr-x 5 999 input 4096 mar 22 15:27 mysql

więc nie wiem czy to co zrobiłem mogło pomóc ale nie pomogło, nadal mam ten sam problem w panelu.

[fracz]

To jeszcze wynik tej komendy będzie interesujący:

Code: Select all

docker exec -it -u www-data supla-cloud ls -al /supla-server

[cosmita]

jestem i podaję

Code: Select all

$ sudo docker exec -it -u www-data supla-cloud ls -al /supla-server
total 8
drwxrwxrwt 2 root root 4096 Mar 22 14:28 .
drwxr-xr-x 1 root root 4096 Mar 21 20:21 ..

nie ogarniam już wszystko mam w domowym katalogu w podkatalogu:

supla-docker

tam też mam skrypt
supla.sh którym wykonuję start lub restart czy upgrade i wszystko leci, więc trochę nie wiem czy dobrze szukamy

[cosmita]

Harmonogram też nie działa:

sobota, 23 marca 2019 17:55
Serwer nieosiągalny

hm, ale jak to, że serwer nie osiągalny po upgradzie nie ma go czy o co kaman?

./supla.sh start

Starting SUPLA containers
Starting supla-db ... done
Starting supla-cloud ... done
Starting supla-server ... done
SUPLA containers has been started.

Code: Select all

ps aux |grep supla
root      9805  0.7  0.4  17176  3624 ?        Sl   19:27   0:00 /usr/local/bin/supla-scheduler
root      9806  0.7  0.7  73696  5608 ?        Sl   19:27   0:00 /usr/local/bin/supla-server

przy czym nie widzę takich plików w /usr/local/bin/ hm

jest tylko docker-compose

czyli co czeka mnie reinstalacja od zera?