Aktualizacja v2.2.0 -> v2.3.0

Moderator: fracz

mariusz_70
Posts: 52
Joined: Thu Nov 10, 2016 5:51 pm

Tue Feb 19, 2019 11:38 am

fracz wrote:
Tue Feb 19, 2019 6:46 am
slavo_s2k wrote:
Mon Feb 18, 2019 9:51 pm
Po instalacji (czystej)i pierwszym zalogowaniu nie można dodawać urządzeń ani smartfonu , po restarcie już dodaje bez problemu , ale jest komunikat "SUPLA server is down"
Tez na qnapie?
Tak z ciekawości zainstalowałem na qnapie i potwierdzam jest ten błąd .
User avatar
fracz
Posts: 1603
Joined: Fri Oct 28, 2016 10:56 pm
Location: Rybna

Tue Feb 19, 2019 11:55 am

Na tym branchu qnap-2.3 też?
User avatar
lesny8
Posts: 870
Joined: Mon Dec 11, 2017 9:43 pm

Tue Feb 19, 2019 2:22 pm

fracz wrote:
Tue Feb 19, 2019 11:55 am
Na tym branchu qnap-2.3 też?
Na tego brancha w ogóle nie idzie przestawić qnapa bo nie ma tego wspaniałego wizarda.
Logi z supla-server mówią, że nie może połączyć się z bazą. Ale jak wejdę do kontenera i przeszukam to nie mam tam socketa, tak jak na malinie. W supla-cloud też go brak.

Code: Select all

INFO[1550582303.926906] Scheduler version 2.3.0                                                                                             
INFO[1550582303.927605] Started at Tue Feb 19 13:18:23 2019                                                                                 
ERR[1550582303.929077] MySQL - Failed to connect to database.                                                                               
ERR[1550582303.929099] Can't connect to database!                                                                                           
INFO[1550582303.930432] Server version 2.3.0 [Protocol v10]                                                                                 
INFO[1550582303.930511] Started at Tue Feb 19 13:18:23 2019                                                                                 
2019-02-19 13:18:23,931 INFO exited: supla-scheduler (exit status 1; not expected)                                                          
ERR[1550582303.931798] MySQL - Failed to connect to database.                                                                               
ERR[1550582303.931816] Can't connect to database!                                                                                           
2019-02-19 13:18:23,932 INFO gave up: supla-scheduler entered FATAL state, too many start retries too quickly                               
2019-02-19 13:18:23,932 INFO exited: supla-server (exit status 1; not expected)                                                             
2019-02-19 13:18:24,934 INFO gave up: supla-server entered FATAL state, too many start retries too quickly 
Czy cloud powinien utworzyć supla-server-ctrl.sock, czy jak?

Od niedzieli zainstalowałem tam SUPLE już z 50 razy i jak bym nie mapował volumes to cloud nie ma gdzie zapisać, a wydaje mi się że to on go tworzy. Nie do końca to wszystko ogarniam, bynajmniej na qnapie socketa nie ma w miejscu gdzie jest na RPi:

Code: Select all

sudo find / | grep ctrl.sock
/home/pi/supla-docker/var/supla-server-socket/supla-server-ctrl.sock
W kontenerze supla-server na RPi

Code: Select all

find / | grep ctrl.sock
/run/supla/supla-server-ctrl.sock
W kontenerze supla-cloud na RPi

Code: Select all

find / | grep ctrl.sock
/supla-server/supla-server-ctrl.sock
Wydaje mi się, że tu leży przyczyna... :roll:
User avatar
fracz
Posts: 1603
Joined: Fri Oct 28, 2016 10:56 pm
Location: Rybna

Tue Feb 19, 2019 6:39 pm

Aaaa bo Wy tym wizardem instalujecie. To ja już wiem o co chodzi. W nocy ogarnę
User avatar
fracz
Posts: 1603
Joined: Fri Oct 28, 2016 10:56 pm
Location: Rybna

Tue Feb 19, 2019 9:23 pm

Gotowe. Próbować instalację z wizarda :-)
User avatar
lesny8
Posts: 870
Joined: Mon Dec 11, 2017 9:43 pm

Tue Feb 19, 2019 10:27 pm

Niestety nie działa :(
Takiej samej zmiany próbowałem w niedziele :roll:

Zalogować się można do Cloud bo nawiązuję połączenie z DB i wypełnia ją jak trzeba, widać w logach podczas instalacji.

Logi z kontenera bazy

Code: Select all

MySQL init process done. Ready for start up.                                                                                                                                                                                                                                                       
                                                                                                                                                                                                                                                                                                   
2019-02-19T22:06:57.512268Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).                                                                                                      
2019-02-19T22:06:57.514251Z 0 [Note] mysqld (mysqld 5.7.20) starting as process 1 ...                                                                                                                                                                                                              
2019-02-19T22:06:57.519482Z 0 [Note] InnoDB: PUNCH HOLE support available                                                                                                                                                                                                                          
2019-02-19T22:06:57.519539Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins                                                                                                                                                                                                          
2019-02-19T22:06:57.519552Z 0 [Note] InnoDB: Uses event mutexes                                                                                                                                                                                                                                    
2019-02-19T22:06:57.519560Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier                                                                                                                                                                                        
2019-02-19T22:06:57.519591Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3                                                                                                                                                                                                                      
2019-02-19T22:06:57.519608Z 0 [Note] InnoDB: Using Linux native AIO                                                                                                                                                                                                                                
2019-02-19T22:06:57.519996Z 0 [Note] InnoDB: Number of pools: 1                                                                                                                                                                                                                                    
2019-02-19T22:06:57.520161Z 0 [Note] InnoDB: Using CPU crc32 instructions                                                                                                                                                                                                                          
2019-02-19T22:06:57.522290Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M                                                                                                                                                                         
2019-02-19T22:06:57.534931Z 0 [Note] InnoDB: Completed initialization of buffer pool                                                                                                                                                                                                               
2019-02-19T22:06:57.537503Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().                                                                                                                           
2019-02-19T22:06:57.550181Z 0 [Note] InnoDB: Highest supported file format is Barracuda.                                                                                                                                                                                                           
2019-02-19T22:06:57.650221Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables                                                                                                                                                                                                       
2019-02-19T22:06:57.650341Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...                                                                                                                                                              
2019-02-19T22:06:57.818209Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.                                                                                                                                                                                                                    
2019-02-19T22:06:57.819610Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.                                                                                                                                                                            
2019-02-19T22:06:57.819646Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.                                                                                                                                                                                                           
2019-02-19T22:06:57.820360Z 0 [Note] InnoDB: 5.7.20 started; log sequence number 12157631                                                                                                                                                                                                          
2019-02-19T22:06:57.820713Z 0 [Note] Plugin 'FEDERATED' is disabled.                                                                                                                                                                                                                               
2019-02-19T22:06:57.823120Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool                                                                                                                                                                                             
2019-02-19T22:06:57.827118Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.                                                                                                                                                  
2019-02-19T22:06:57.827636Z 0 [Warning] CA certificate ca.pem is self signed.                                                                                                                                                                                                                      
2019-02-19T22:06:57.830640Z 0 [Note] Server hostname (bind-address): '*'; port: 3306                                                                                                                                                                                                               
2019-02-19T22:06:57.830709Z 0 [Note] IPv6 is available.                                                                                                                                                                                                                                            
2019-02-19T22:06:57.830724Z 0 [Note]   - '::' resolves to '::';                                                                                                                                                                                                                                    
2019-02-19T22:06:57.830781Z 0 [Note] Server socket created on IP: '::'.                                                                                                                                                                                                                            
2019-02-19T22:06:57.831074Z 0 [Note] InnoDB: Buffer pool(s) load completed at 190219 22:06:57                                                                                                                                                                                                      
2019-02-19T22:06:57.862225Z 0 [Warning] 'user' entry 'root@localhost' ignored in --skip-name-resolve mode.                                                                                                                                                                                         
2019-02-19T22:06:57.862278Z 0 [Warning] 'user' entry 'mysql.session@localhost' ignored in --skip-name-resolve mode.                                                                                                                                                                                
2019-02-19T22:06:57.862331Z 0 [Warning] 'user' entry 'mysql.sys@localhost' ignored in --skip-name-resolve mode.                                                                                                                                                                                    
2019-02-19T22:06:57.862380Z 0 [Warning] 'db' entry 'performance_schema mysql.session@localhost' ignored in --skip-name-resolve mode.                                                                                                                                                               
2019-02-19T22:06:57.862392Z 0 [Warning] 'db' entry 'sys mysql.sys@localhost' ignored in --skip-name-resolve mode.                                                                                                                                                                                  
2019-02-19T22:06:57.862409Z 0 [Warning] 'proxies_priv' entry '@ root@localhost' ignored in --skip-name-resolve mode.                                                                                                                                                                               
2019-02-19T22:06:57.865982Z 0 [Warning] 'tables_priv' entry 'user mysql.session@localhost' ignored in --skip-name-resolve mode.                                                                                                                                                                    
2019-02-19T22:06:57.866018Z 0 [Warning] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.                                                                                                                                                                  
2019-02-19T22:06:57.874502Z 0 [Note] Event Scheduler: Loaded 0 events                                                                                                                                                                                                                              
2019-02-19T22:06:57.874758Z 0 [Note] mysqld: ready for connections.                                                                                                                                                                                                                                
Version: '5.7.20'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server (GPL)                                                                                                                                                                                                 
2019-02-19T22:06:57.874776Z 0 [Note] Executing 'SELECT * FROM INFORMATION_SCHEMA.TABLES;' to get a list of tables using the deprecated partition engine. You may use the startup option '--disable-partition-engine-check' to skip this check.                                                     
2019-02-19T22:06:57.874781Z 0 [Note] Beginning of list of non-natively partitioned tables                                                                                                                                                                                                          
2019-02-19T22:06:57.891304Z 0 [Note] End of list of non-natively partitioned tables


Czy to nie jest dziwne?

Code: Select all

2019-02-19T22:06:57.830781Z 0 [Note] Server socket created on IP: '::'.

Smartfona nie mogę dodać, apka wisi cały czas.

Logi z supla-server

Code: Select all

INFO[1550613984.287171] Server version 2.3.0 [Protocol v10]                                                                                                                                                                                                                                        
INFO[1550613984.287246] Started at Tue Feb 19 22:06:24 2019                                                                                                                                                                                                                                        
ERR[1550613984.288029] MySQL - Failed to connect to database.                                                                                                                                                                                                                                      
ERR[1550613984.290409] Can't connect to database!                                                                                                                                                                                                                                                  
2019-02-19 22:06:24,291 INFO exited: supla-scheduler (exit status 1; not expected)                                                                                                                                                                                                                 
ERR[1550613984.292123] MySQL - Failed to connect to database.                                                                                                                                                                                                                                      
ERR[1550613984.292134] Can't connect to database!                                                                                                                                                                                                                                                  
2019-02-19 22:06:24,296 INFO exited: supla-server (exit status 1; not expected)                                                                                                                                                                                                                    
2019-02-19 22:06:25,298 INFO spawned: 'supla-scheduler' with pid 19                                                                                                                                                                                                                                
2019-02-19 22:06:25,314 INFO spawned: 'supla-server' with pid 21                                                                                                                                                                                                                                   
INFO[1550613985.306905] Scheduler version 2.3.0                                                                                                                                                                                                                                                    
INFO[1550613985.306966] Started at Tue Feb 19 22:06:25 2019                                                                                                                                                                                                                                        
ERR[1550613985.307800] MySQL - Failed to connect to database.                                                                                                                                                                                                                                      
ERR[1550613985.307810] Can't connect to database!                                                                                                                                                                                                                                                  
2019-02-19 22:06:25,315 INFO exited: supla-scheduler (exit status 1; not expected)                                                                                                                                                                                                                 
INFO[1550613985.329058] Server version 2.3.0 [Protocol v10]                                                                                                                                                                                                                                        
INFO[1550613985.329561] Started at Tue Feb 19 22:06:25 2019                                                                                                                                                                                                                                        
ERR[1550613985.330903] MySQL - Failed to connect to database.                                                                                                                                                                                                                                      
ERR[1550613985.330919] Can't connect to database!                                                                                                                                                                                                                                                  
2019-02-19 22:06:25,332 INFO exited: supla-server (exit status 1; not expected)                                                                                                                                                                                                                    
2019-02-19 22:06:27,335 INFO spawned: 'supla-scheduler' with pid 23                                                                                                                                                                                                                                
2019-02-19 22:06:27,337 INFO spawned: 'supla-server' with pid 24                                                                                                                                                                                                                                   
INFO[1550613987.343204] Scheduler version 2.3.0                                                                                                                                                                                                                                                    
INFO[1550613987.343710] Started at Tue Feb 19 22:06:27 2019                                                                                                                                                                                                                                        
ERR[1550613987.344884] MySQL - Failed to connect to database.                                                                                                                                                                                                                                      
ERR[1550613987.344908] Can't connect to database!                                                                                                                                                                                                                                                  
2019-02-19 22:06:27,346 INFO exited: supla-scheduler (exit status 1; not expected)                                                                                                                                                                                                                 
INFO[1550613987.347431] Server version 2.3.0 [Protocol v10]                                                                                                                                                                                                                                        
INFO[1550613987.347498] Started at Tue Feb 19 22:06:27 2019                                                                                                                                                                                                                                        
ERR[1550613987.348490] MySQL - Failed to connect to database.                                                                                                                                                                                                                                      
ERR[1550613987.348507] Can't connect to database!                                                                                                                                                                                                                                                  
2019-02-19 22:06:27,349 INFO exited: supla-server (exit status 1; not expected)                                                                                                                                                                                                                    
2019-02-19 22:06:30,353 INFO spawned: 'supla-scheduler' with pid 27                                                                                                                                                                                                                                
2019-02-19 22:06:30,355 INFO spawned: 'supla-server' with pid 28                                                                                                                                                                                                                                   
INFO[1550613990.361125] Scheduler version 2.3.0                                                                                                                                                                                                                                                    
INFO[1550613990.361203] Started at Tue Feb 19 22:06:30 2019                                                                                                                                                                                                                                        
ERR[1550613990.362357] MySQL - Failed to connect to database.                                                                                                                                                                                                                                      
ERR[1550613990.362376] Can't connect to database!                                                                                                                                                                                                                                                  
2019-02-19 22:06:30,363 INFO exited: supla-scheduler (exit status 1; not expected)                                                                                                                                                                                                                 
INFO[1550613990.363858] Server version 2.3.0 [Protocol v10]                                                                                                                                                                                                                                        
INFO[1550613990.363933] Started at Tue Feb 19 22:06:30 2019                                                                                                                                                                                                                                        
2019-02-19 22:06:30,364 INFO gave up: supla-scheduler entered FATAL state, too many start retries too quickly                                                                                                                                                                                      
ERR[1550613990.364899] MySQL - Failed to connect to database.                                                                                                                                                                                                                                      
ERR[1550613990.364918] Can't connect to database!                                                                                                                                                                                                                                                  
2019-02-19 22:06:30,365 INFO exited: supla-server (exit status 1; not expected)                                                                                                                                                                                                                    
2019-02-19 22:06:31,367 INFO gave up: supla-server entered FATAL state, too many start retries too quickly   
User avatar
fracz
Posts: 1603
Joined: Fri Oct 28, 2016 10:56 pm
Location: Rybna

Wed Feb 20, 2019 6:42 am

Potrzebuję dostęp SSH do jakiegoś qnapa (TeamViewer mnie nie urządza bo ciężko mi zaplanować porę dnia w której mogę się za to wziąć). Chętnych proszę na priv ;-)
andras
Posts: 250
Joined: Fri Dec 30, 2016 5:51 pm

Wed Feb 20, 2019 8:51 am

TS-219P może być ?
slavo_s2k
Posts: 27
Joined: Sat Mar 10, 2018 7:32 pm

Fri Feb 22, 2019 5:05 pm

Coś się ruszyło w temacie??
thomass
Posts: 20
Joined: Wed Dec 19, 2018 11:31 pm
Location: Rzeszów

Fri Feb 22, 2019 5:37 pm

Fracz na urlopie?
Post Reply