Supla ❤ Docker

Moderator: fracz

User avatar
fracz
Posts: 921
Joined: Fri Oct 28, 2016 10:56 pm
Location: Rybna

Sat Mar 31, 2018 6:22 am

You need to restart the containers after any change in the .env files.

Code: Select all

./supla.sh restart 
vuhazu
Posts: 34
Joined: Wed Dec 21, 2016 2:19 pm

Sat Mar 31, 2018 2:38 pm

Thanks!
Ryo
Posts: 21
Joined: Fri Jan 27, 2017 7:00 am

Sat May 12, 2018 5:55 pm

Witajcie ludziska. Padła mi dockerowa baza supla-db na RPI i nie bardzo wiem jak to wskrzesić. Macie jakieś pomysły?

komenda docker logs supla-db daje taki output:

Code: Select all

  InnoDB: End of page dump
180509 22:34:55  InnoDB: Page checksum 3707371545, prior-to-4.0.14-form checksum 2686931671
InnoDB: stored checksum 2951683818, prior-to-4.0.14-form stored checksum 3646857931
InnoDB: Page lsn 2 14929473, low 4 bytes of lsn at page end 13356609
InnoDB: Page number (if stored to page already) 59,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a system page
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 59.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
180509 22:34:55  InnoDB: Assertion failure in thread 1992622080 in file buf0buf.c line 3623
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
22:34:55 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed, 
something is definitely wrong and this may fail.

key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346093 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x30000
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
error from daemon in stream: Error grabbing logs: json: cannot unmarshal number into Go value of type jsonlog.JSONLog

 
User avatar
fracz
Posts: 921
Joined: Fri Oct 28, 2016 10:56 pm
Location: Rybna

Mon May 14, 2018 3:00 pm

Wygląda na awarię karty SD. Niesety one nienajlepiej znoszą bazy danych.

Raczej musisz odtworzyć bazę z backupu.
Ryo
Posts: 21
Joined: Fri Jan 27, 2017 7:00 am

Wed May 16, 2018 6:46 am

Backup :lol:
bartekk942
Posts: 8
Joined: Fri May 04, 2018 7:33 pm

Sun May 27, 2018 5:57 pm

Cześć, podbiłem suple do v2.2.0 i teraz gdy próbuje się zalogować to przeglądarka rzuca błędem:

Code: Select all

This site can’t provide a secure connection
xx.xx.xx.xx sent an invalid response.
ERR_SSL_PROTOCOL_ERROR
User avatar
fracz
Posts: 921
Joined: Fri Oct 28, 2016 10:56 pm
Location: Rybna

Sun May 27, 2018 7:10 pm

Proxy czy standalone?
bartekk942
Posts: 8
Joined: Fri May 04, 2018 7:33 pm

Mon May 28, 2018 12:20 pm

Standalone.
bartekk942
Posts: 8
Joined: Fri May 04, 2018 7:33 pm

Wed Jun 20, 2018 5:45 pm

fracz wrote:
Sun May 27, 2018 7:10 pm
Proxy czy standalone?
Podbijam, bo ponownie wróciłem do tematu.
User avatar
fracz
Posts: 921
Joined: Fri Oct 28, 2016 10:56 pm
Location: Rybna

Wed Jun 20, 2018 6:22 pm

Czy po aktualizacji zmienił się adres strony? Upewnij się że masz ustawiony dobry adres w .env, zatrzymaj kontenery, usuń certyfikaty z supla-docker/ssl/*, wystartuj i zobacz czy nadal jest problem.
Post Reply