Pokaż
Kod: Zaznacz cały
docker ps
Moderator: fracz
Kod: Zaznacz cały
docker ps
Haha wątpięlesny8 pisze: ↑pt sty 25, 2019 12:36 pm Bądź optymistą, w 2h się wyrobisz taki żarcik
PokażKod: Zaznacz cały
docker ps
Kod: Zaznacz cały
pi@raspberrypi:~ $ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
cc74e6a11aec nginx "nginx -g 'daemon of…" 2 hours ago Restarting (1) 51 seconds ago nginx-web
b3dbb3fd82ed supla/supla-server:arm32v7 "/usr/bin/server-ent…" 4 hours ago Up 4 hours 0.0.0.0:2015-2016->2015-2016/tcp supla-server
7221664a76ee supla/supla-cloud:arm32v7 "docker-php-entrypoi…" 4 hours ago Up About a minute 80/tcp supla-cloud
7b928f26008d hypriot/rpi-mysql:5.5 "/entrypoint.sh mysq…" 4 hours ago Restarting (1) 20 seconds ago supla-db
f92143ea1a2c sameersbn/bind:latest "/sbin/entrypoint.sh…" 5 weeks ago Up 6 hours 53/tcp, 0.0.0.0:53->53/udp, 0.0.0.0:10000->10000/tcp bind
6d05d106a581 suplascripts_suplascripts "docker-php-entrypoi…" 6 weeks ago Up 6 hours 80/tcp suplascripts
736758ef6e92 hypriot/rpi-mysql:5.5 "/entrypoint.sh mysq…" 7 weeks ago Up 6 hours 3306/tcp suplascripts-db
fb9c1ad6f4ab wouterds/rpi-docker-letsencrypt-nginx-proxy-companion "/bin/bash /app/entr…" 7 weeks ago Up 6 hours nginx-letsencrypt
2e28b0b600d6 wouterds/rpi-docker-gen "/usr/local/bin/dock…" 7 weeks ago Up 2 hours nginx-gen
823f4de9080c httpd:alpine "httpd-foreground" 7 weeks ago Up 6 hours 80/tcp supla-scripts
2e3e9dbada99 httpd:alpine "httpd-foreground" 7 weeks ago Up 6 hours 80/tcp supla-docker
pi@raspberrypi:~ $
Kod: Zaznacz cały
docker stop supla-docker supla-scripts && docker rm supla-docker supla-scripts
Kod: Zaznacz cały
cd ~
source supla-docker/.env
docker logs --tail=50 supla-db
Kod: Zaznacz cały
pi@raspberrypi:~ $ docker stop supla-docker supla-scripts && docker rm supla-dock
ker supla-scripts
supla-docker
supla-scripts
supla-docker
supla-scripts
pi@raspberrypi:~ $ cd ~
pi@raspberrypi:~ $ source supla-docker/.env
pi@raspberrypi:~ $ docker logs --tail=50 supla-db
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 2897.
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.
190125 16:05:47 InnoDB: Assertion failure in thread 1710224480 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.
16:05:47 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.
190125 16:06:18 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
190125 16:06:18 [Note] mysqld (mysqld 5.5.60-0+deb7u1) starting as process 1 ...
pi@raspberrypi:~ $
Kod: Zaznacz cały
reboot
Kod: Zaznacz cały
docker ps
Kod: Zaznacz cały
sudo reboot