Aktualizacja v2.2.0 -> v2.3.0

Moderator: fracz

User avatar
pzygmunt
Posts: 6003
Joined: Tue Jan 19, 2016 9:26 am
Location: Paczków
Contact:

Wed Feb 13, 2019 11:20 am

supla-server nie może pisać do /var/run/supla
Simono
Posts: 197
Joined: Mon Sep 17, 2018 5:26 pm

Wed Feb 13, 2019 11:41 am

djack2017 wrote:
Wed Feb 13, 2019 10:06 am
Aktualizacja na VPS-ie Debian 8.10 niby przebiegła bez problemów. Nie ma przekierowania z http na https jak było poprzednio, więc się nie zalogowałem. Obecnie udało mi się zalogować (po https) ale mam "żółty" komunikat: "
Serwer oczywiście chodzi ale w logu mam komnikaty:
...
ERR[1550051795.233322] Incorrect database version!
...
ERR[1550052945.513661] Can't bind ipc socket
Miałem tak na malinie, też ten żółty komunikat na www. Aktualizacja również przebiegła poprawnie. Po restarcie maliny wszystko gra.
djack2017
Posts: 199
Joined: Mon Nov 27, 2017 7:36 am

Wed Feb 13, 2019 11:51 am

U mnie po restarcie nic się nie zmieniło.
pzygmunt wrote:
Wed Feb 13, 2019 11:20 am
supla-server nie może pisać do /var/run/supla
Nie wiem czy dobrze zrozumiałem - założyłem katalog /var/run/supla i dałem prawo do zapisu wszystkim.
Bez zmian.
User avatar
pzygmunt
Posts: 6003
Joined: Tue Jan 19, 2016 9:26 am
Location: Paczków
Contact:

Wed Feb 13, 2019 12:10 pm

To nic Ci może nie dać bo po każdym restarcie on zniknie.
Trzeba utworzyć plik
/usr/lib/tmpfiles.d/supla-server.conf


z zawartością:
d /run/supla 0755 supla supla
kris.sg
Posts: 105
Joined: Mon Aug 07, 2017 8:08 pm
Location: Przezchlebie

Wed Feb 13, 2019 12:44 pm

kris.sg wrote:
Wed Feb 13, 2019 10:39 am
na mojej malinie aktualizacja poszła bez błędów, ale po zalogowaniu na clouda mam błąd : supla server is down
restart maliny nie pomaga

log z konsoli:

Code: Select all

pi@raspberrypi:~/supla-docker $ ./supla.sh upgrade
Making database backup
Database backup saved to ./var/backups/supla02132019113456.sql.gz
Stopping SUPLA containers
Stopping supla-server ... done
Stopping supla-cloud  ... done
Stopping supla-db     ... done
SUPLA containers has been stopped.
Pulling supla-db     ... done
Pulling supla-cloud  ... done
Pulling supla-server ... done
Starting SUPLA containers
Starting supla-db ... done
Starting supla-cloud ... done
Starting supla-server ... done
SUPLA containers has been started.

dodatkowo log z supli:

Code: Select all

pi@raspberrypi:~/supla-docker $ docker logs --tail=50 supla-server
INFO[1550059012.506705] Connection accepted: 192.168.1.1:1341 ClientSD: 11 Secure: 1
INFO[1550059012.669118] Cipher: AES128-SHA, ClientSD: 11
INFO[1550059012.974076] Device registered. ID: 291, ClientSD: 11 Protocol Version: 7
2019-02-13 11:56:53,977 INFO success: supla-scheduler entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-02-13 11:56:53,977 INFO success: supla-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
INFO[1550059017.793507] Connection accepted: 192.168.1.1:26337 ClientSD: 13 Secure: 1
INFO[1550059017.954253] Cipher: AES128-SHA, ClientSD: 13
INFO[1550059018.227424] Device registered. ID: 286, ClientSD: 13 Protocol Version: 7
INFO[1550059018.998906] Connection accepted: 192.168.1.1:27675 ClientSD: 16 Secure: 1
INFO[1550059019.171019] Cipher: AES128-SHA, ClientSD: 16
INFO[1550059019.378609] Device registered. ID: 270, ClientSD: 16 Protocol Version: 7
INFO[1550059021.787137] Connection accepted: 192.168.1.1:39259 ClientSD: 19 Secure: 1
INFO[1550059021.989464] Cipher: AES128-SHA, ClientSD: 19
INFO[1550059022.423151] Device registered. ID: 241, ClientSD: 19 Protocol Version: 7
INFO[1550059023.448748] Connection accepted: 192.168.1.1:6729 ClientSD: 22 Secure: 1
INFO[1550059023.599562] Cipher: AES128-SHA, ClientSD: 22
INFO[1550059023.827820] Device registered. ID: 258, ClientSD: 22 Protocol Version: 7
INFO[1550059029.682187] Connection accepted: 192.168.1.1:42391 ClientSD: 25 Secure: 1
INFO[1550059029.833160] Cipher: AES128-SHA, ClientSD: 25
INFO[1550059029.948288] Connection accepted: 192.168.1.1:44970 ClientSD: 28 Secure: 1
INFO[1550059030.62524] Device registered. ID: 243, ClientSD: 25 Protocol Version: 7
INFO[1550059030.112342] Cipher: AES128-SHA, ClientSD: 28
INFO[1550059030.307243] Device registered. ID: 242, ClientSD: 28 Protocol Version: 7
INFO[1550059034.607100] Connection accepted: 192.168.1.1:7544 ClientSD: 32 Secure: 1
INFO[1550059034.767261] Cipher: AES128-SHA, ClientSD: 32
INFO[1550059034.940568] Device registered. ID: 269, ClientSD: 32 Protocol Version: 7
INFO[1550059038.16840] Connection accepted: 192.168.1.1:46771 ClientSD: 34 Secure: 1
INFO[1550059038.168839] Cipher: AES128-SHA, ClientSD: 34
INFO[1550059038.357695] Device registered. ID: 29, ClientSD: 34 Protocol Version: 7
INFO[1550059042.94123] Connection accepted: 192.168.1.162:8650 ClientSD: 15 Secure: 1
INFO[1550059042.268895] Cipher: AES128-SHA, ClientSD: 15
INFO[1550059042.525614] Device registered. ID: 2, ClientSD: 15 Protocol Version: 5
INFO[1550059044.693305] Connection accepted: 192.168.1.1:35959 ClientSD: 18 Secure: 1
INFO[1550059044.853544] Cipher: AES128-SHA, ClientSD: 18
INFO[1550059045.48945] Device registered. ID: 273, ClientSD: 18 Protocol Version: 7
INFO[1550059052.95346] Connection accepted: 192.168.1.1:20184 ClientSD: 24 Secure: 1
INFO[1550059052.258096] Cipher: AES128-SHA, ClientSD: 24
INFO[1550059052.522381] Device registered. ID: 29, ClientSD: 24 Protocol Version: 7
INFO[1550059057.964494] Connection accepted: 192.168.1.190:33427 ClientSD: 25 Secure: 1
INFO[1550059058.127640] Cipher: AES128-SHA, ClientSD: 25
INFO[1550059058.143971] Connection accepted: 192.168.1.149:47099 ClientSD: 28 Secure: 1
INFO[1550059058.297029] Cipher: AES128-SHA, ClientSD: 28
INFO[1550059058.524029] Device registered. ID: 17, ClientSD: 25 Protocol Version: 7
INFO[1550059058.535681] Device registered. ID: 16, ClientSD: 28 Protocol Version: 7
INFO[1550059061.752890] Connection accepted: 192.168.1.94:28674 ClientSD: 34 Secure: 1
INFO[1550059061.927868] Cipher: AES128-SHA, ClientSD: 34
INFO[1550059062.135064] Device registered. ID: 1, ClientSD: 34 Protocol Version: 7
INFO[1550059071.908360] Connection accepted: 192.168.1.21:27883 ClientSD: 37 Secure: 1
INFO[1550059072.89319] Cipher: AES128-SHA, ClientSD: 37
INFO[1550059072.436779] Device registered. ID: 3, ClientSD: 37 Protocol Version: 7
pi@raspberrypi:~/supla-docker $ docker logs --tail=50 supla-cloud
supla:clean:not-confirmed-users: NOT NOW
supla:clean:obsolete-oauth-tokens: NOT NOW
supla:clean:orphaned-measurement-logs: NOT NOW
supla:clean:disable-broken-schedules: NOT NOW
supla:clean:disable-demo-client-apps: RUN:
Clients to disable: 0
supla:generate-schedules-executions: NOT NOW
172.18.0.3:443 91.192.0.86 - - [13/Feb/2019:11:56:10 +0000] "-" 408 2345 "-" "-"
2019-02-13 11:56:22,186 WARN received SIGTERM indicating exit request
2019-02-13 11:56:22,218 INFO waiting for apache, cron to die
2019-02-13 11:56:22,248 INFO stopped: cron (terminated by SIGTERM)
[Wed Feb 13 11:56:22.611269 2019] [mpm_prefork:notice] [pid 49] AH00169: caught SIGTERM, shutting down
2019-02-13 11:56:22,695 INFO stopped: apache (exit status 0)
Database connection has been established.
                                                              
                    Application Migrations                    
                                                              

No migrations to execute.
Client for webapp exists.

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

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

User kris.sg@wp.pl already exists.
2019-02-13 11:57:43,619 CRIT Supervisor running as root (no user in config file)
2019-02-13 11:57:43,637 INFO supervisord started with pid 1
2019-02-13 11:57:44,645 INFO spawned: 'apache' with pid 49
2019-02-13 11:57:44,654 INFO spawned: 'cron' with pid 50
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.18.0.3. Set the 'ServerName' directive globally to suppress this message
[Wed Feb 13 11:57:45.402012 2019] [ssl:warn] [pid 49] AH01909: 172.18.0.3:443:0 server certificate does NOT include an ID which matches the server name
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.18.0.3. Set the 'ServerName' directive globally to suppress this message
2019-02-13 11:57:45,669 INFO success: apache entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-02-13 11:57:45,671 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
[Wed Feb 13 11:57:45.854262 2019] [ssl:warn] [pid 49] AH01909: 172.18.0.3:443:0 server certificate does NOT include an ID which matches the server name
[Wed Feb 13 11:57:45.874124 2019] [mpm_prefork:notice] [pid 49] AH00163: Apache/2.4.25 (Debian) PHP/7.0.33 OpenSSL/1.0.2q configured -- resuming normal operations
[Wed Feb 13 11:57:45.874257 2019] [core:notice] [pid 49] AH00094: Command line: 'apache2 -D FOREGROUND'
supla:clean:passed-io-client-registration-dates: RUN:
Client registration expiration date - cleared: 0
I/O Device registration expiration date - cleared: 0
supla:clean:broker-clouds-cache: NOT NOW
supla:clean:not-confirmed-users: NOT NOW
supla:clean:obsolete-oauth-tokens: NOT NOW
supla:clean:orphaned-measurement-logs: NOT NOW
supla:clean:disable-broken-schedules: NOT NOW
supla:clean:disable-demo-client-apps: RUN:
Clients to disable: 0
supla:generate-schedules-executions: NOT NOW
nie za bardzo wiem w czym problem
mogę liczyć na pomoc czy mam postawić malinę na nowo ?
User avatar
fracz
Posts: 1492
Joined: Fri Oct 28, 2016 10:56 pm
Location: Rybna

Wed Feb 13, 2019 12:44 pm

@djack rozumiem że to nie nie Docker?

Na instancjach bez Dockera trzeba dokonfigurować supla.cfg:

Code: Select all

[GLOBAL]
group=www-data
i dodać użytkownika supla do grupy www-data:

Code: Select all

usermod -a -G www-data supla
Po tym restart supla-server.

Jeśli błąd występuje na Dockerach - restart powinien pomóc. Wynika to z tego że supla-server spróbował wystartować za wcześnie - przed aktualizacją bazy danych.
djack2017
Posts: 199
Joined: Mon Nov 27, 2017 7:36 am

Wed Feb 13, 2019 12:48 pm

pzygmunt wrote:
Wed Feb 13, 2019 12:10 pm
To nic Ci może nie dać bo po każdym restarcie on zniknie.
Trzeba utworzyć plik
/usr/lib/tmpfiles.d/supla-server.conf


z zawartością:
d /run/supla 0755 supla supla
Niestety nic to nie daje. Nie bardzo wiem w czym problem.
djack2017
Posts: 199
Joined: Mon Nov 27, 2017 7:36 am

Wed Feb 13, 2019 1:04 pm

fracz wrote:
Wed Feb 13, 2019 12:44 pm
@djack rozumiem że to nie nie Docker?

Na instancjach bez Dockera trzeba dokonfigurować supla.cfg:

Code: Select all

[GLOBAL]
group=www-data
i dodać użytkownika supla do grupy www-data:

Code: Select all

usermod -a -G www-data supla
Po tym restart supla-server.

Jeśli błąd występuje na Dockerach - restart powinien pomóc. Wynika to z tego że supla-server spróbował wystartować za wcześnie - przed aktualizacją bazy danych.
Przecież to wątek forum poswięcony instalacji kontenerowej.
To instancja dockerowa. Robiłem restarty kontenerów i całego hosta. Kontenery działają. A błąd wciąż występuje.
W logu kontenera supla-server jedyny błąd to jak poniżej:

INFO[1550060971.262649] Scheduler version 2.3.0
INFO[1550060971.263178] Started at Wed Feb 13 12:29:31 2019
INFO[1550060971.267162] Server version 2.3.0 [Protocol v10]
INFO[1550060971.268840] Started at Wed Feb 13 12:29:31 2019
INFO[1550060971.381206] SSL version: OpenSSL 1.0.1t 3 May 2016
ERR[1550060971.402012] Can't bind ipc socket
2019-02-13 12:29:32,403 INFO success: supla-scheduler entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-02-13 12:29:32,404 INFO success: supla-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
kris.sg
Posts: 105
Joined: Mon Aug 07, 2017 8:08 pm
Location: Przezchlebie

Wed Feb 13, 2019 2:34 pm

u mnie już działa problem był z plikiem docker-compose.yml
usunąłem go, zrobiłełem "git-pull", potem "./supla.sh upgrade"
teraz cloud działa poprawnie nie ma już błędów
ale jest jeszcze jeden problem niektóre urządzenia nie łączą się z cloudem, przed aktualizacją nie było problemu
User avatar
lesny8
Posts: 644
Joined: Mon Dec 11, 2017 9:43 pm

Wed Feb 13, 2019 2:45 pm

kris.sg wrote:
Wed Feb 13, 2019 2:34 pm
ale jest jeszcze jeden problem niektóre urządzenia nie łączą się z cloudem, przed aktualizacją nie było problemu
A może masz te same objawy co u mnie? Możesz to sprawdzić? Może nie jestem jedyny z tym problemem...
Post Reply