Po udanej aktualizacji własnego cloud-a z 2.3.37 na obecny
Pulling supla-db ... done
Pulling supla-cloud ... done
Pulling supla-server ... done
Starting SUPLA containers
Starting supla-db ... done
Recreating supla-cloud ... done
Recreating supla-server ... done
SUPLA containers has been started.
Nie moge połączyć sie z suplą
docker logs --tail=50 supla-server
Fatal Python error: init_interp_main: can't initialize time
Python runtime state: core initialized
PermissionError: [Errno 1] Operation not permitted
Current thread 0xb6f4e520 (most recent call first):
<no Python frame>
Fatal Python error: init_interp_main: can't initialize time
Python runtime state: core initialized
PermissionError: [Errno 1] Operation not permitted
Current thread 0xb6fa6520 (most recent call first):
<no Python frame>
Fatal Python error: init_interp_main: can't initialize time
Python runtime state: core initialized
PermissionError: [Errno 1] Operation not permitted
Current thread 0xb6fb3520 (most recent call first):
<no Python frame>
Fatal Python error: init_interp_main: can't initialize time
Python runtime state: core initialized
PermissionError: [Errno 1] Operation not permitted
Current thread 0xb6fb3520 (most recent call first):
<no Python frame>
Fatal Python error: init_interp_main: can't initialize time
Python runtime state: core initialized
PermissionError: [Errno 1] Operation not permitted
Current thread 0xb6f85520 (most recent call first):
<no Python frame>
Fatal Python error: init_interp_main: can't initialize time
Python runtime state: core initialized
PermissionError: [Errno 1] Operation not permitted
Current thread 0xb6fcc520 (most recent call first):
<no Python frame>
Fatal Python error: init_interp_main: can't initialize time
Python runtime state: core initialized
PermissionError: [Errno 1] Operation not permitted
Current thread 0xb6f7d520 (most recent call first):
<no Python frame>
Fatal Python error: init_interp_main: can't initialize time
Python runtime state: core initialized
PermissionError: [Errno 1] Operation not permitted
Current thread 0xb6f24520 (most recent call first):
<no Python frame>
docker logs --tail=50 supla-db
231027 11:24:53 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
231027 11:24:53 [Note] Plugin 'FEDERATED' is disabled.
231027 11:24:53 InnoDB: The InnoDB memory heap is disabled
231027 11:24:53 InnoDB: Mutexes and rw_locks use GCC atomic builtins
231027 11:24:53 InnoDB: Compressed tables use zlib 1.2.7
231027 11:24:53 InnoDB: Using Linux native AIO
231027 11:24:53 InnoDB: Initializing buffer pool, size = 128.0M
231027 11:24:53 InnoDB: Completed initialization of buffer pool
231027 11:24:53 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
231027 11:24:53 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
231027 11:24:54 InnoDB: Waiting for the background threads to start
231027 11:24:55 InnoDB: 5.5.60 started; log sequence number 965540734
231027 11:24:55 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
231027 11:24:55 [Note] - '0.0.0.0' resolves to '0.0.0.0';
231027 11:24:55 [Note] Server socket created on IP: '0.0.0.0'.
231027 11:24:55 [Note] Event Scheduler: Loaded 0 events
231027 11:24:55 [Note] mysqld: ready for connections.
Version: '5.5.60-0+deb7u1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian)
231027 21:07:38 [Note] mysqld: Normal shutdown
231027 21:07:38 [Note] Event Scheduler: Purging the queue. 0 events
231027 21:07:38 InnoDB: Starting shutdown...
231027 21:07:39 InnoDB: Shutdown completed; log sequence number 965556908
231027 21:07:39 [Note] mysqld: Shutdown complete
231027 21:15:40 [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.
231027 21:15:40 [Note] mysqld (mysqld 5.5.60-0+deb7u1) starting as process 1 ...
231027 21:15:40 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
231027 21:15:40 [Note] Plugin 'FEDERATED' is disabled.
231027 21:15:40 InnoDB: The InnoDB memory heap is disabled
231027 21:15:40 InnoDB: Mutexes and rw_locks use GCC atomic builtins
231027 21:15:40 InnoDB: Compressed tables use zlib 1.2.7
231027 21:15:40 InnoDB: Using Linux native AIO
231027 21:15:40 InnoDB: Initializing buffer pool, size = 128.0M
231027 21:15:40 InnoDB: Completed initialization of buffer pool
231027 21:15:40 InnoDB: highest supported file format is Barracuda.
231027 21:15:43 InnoDB: Waiting for the background threads to start
231027 21:15:44 InnoDB: 5.5.60 started; log sequence number 965556908
231027 21:15:44 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
231027 21:15:44 [Note] - '0.0.0.0' resolves to '0.0.0.0';
231027 21:15:44 [Note] Server socket created on IP: '0.0.0.0'.
231027 21:15:44 [Note] Event Scheduler: Loaded 0 events
231027 21:15:44 [Note] mysqld: ready for connections.
Version: '5.5.60-0+deb7u1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian)