Mam prywatną instancje. Co jakiś czas mam problem z zalogowaniem sie przez www i aplikacje do clouda . Po wykonaniu reboot, supla działa jakieś 3-4 dni i ponawia sie problem. W aplikacji jest stan łączenia i www też nie działa. Przez Putty normalnie sie loguje , poniżej wklejam logi (akurat mam stan problemu)
docker logs --tail=50 supla-server
INFO[18:40:48.333309] Device registration started. ClientSD: 27 Protocol Version : 16 ThreadID: 3412 GUID: C6F84F51
INFO[18:40:48.432550] Device registered. ID: 39, ClientSD: 27 Protocol Version: 16 ThreadID: 3412 GUID: C6F84F51 ResultCode: 3
INFO[18:41:01.401524] Connection accepted: 10.0.6.23:61174 ClientSD: 52 Secure: 1
INFO[18:41:01.622959] Cipher: AES128-SHA256, SSL Version: TLSv1.2, ClientSD: 52
INFO[18:41:01.705385] Device registration started. ClientSD: 52 Protocol Version : 16 ThreadID: 3416 GUID: 8FEEFBE3
INFO[18:41:01.834661] Device registered. ID: 41, ClientSD: 52 Protocol Version: 16 ThreadID: 3416 GUID: 8FEEFBE3 ResultCode: 3
INFO[18:41:24.234402] Connection accepted: 10.0.6.17:59736 ClientSD: 92 Secure: 1
INFO[18:41:24.450769] Cipher: AES128-SHA256, SSL Version: TLSv1.2, ClientSD: 92
INFO[18:41:24.529226] Device registration started. ClientSD: 92 Protocol Version : 16 ThreadID: 3417 GUID: 6D22231F
INFO[18:41:24.627674] Device registered. ID: 34, ClientSD: 92 Protocol Version: 16 ThreadID: 3417 GUID: 6D22231F ResultCode: 3
INFO[18:41:34.167782] Connection accepted: 10.0.6.23:53937 ClientSD: 70 Secure: 1
INFO[18:41:34.382744] Cipher: AES128-SHA256, SSL Version: TLSv1.2, ClientSD: 70
INFO[18:41:34.461188] Device registration started. ClientSD: 70 Protocol Version : 16 ThreadID: 3418 GUID: 8FEEFBE3
INFO[18:41:34.706421] Device registered. ID: 41, ClientSD: 70 Protocol Version: 16 ThreadID: 3418 GUID: 8FEEFBE3 ResultCode: 3
ERR[18:41:36.663418] Could not get any token for any remote gateway from AD serv er.
INFO[18:41:52.595855] Connection accepted: 10.0.6.17:62553 ClientSD: 52 Secure: 1
INFO[18:41:52.815123] Cipher: AES128-SHA256, SSL Version: TLSv1.2, ClientSD: 52
INFO[18:41:52.897512] Device registration started. ClientSD: 52 Protocol Version : 16 ThreadID: 3429 GUID: 6D22231F
INFO[18:41:53.143204] Device registered. ID: 34, ClientSD: 52 Protocol Version: 16 ThreadID: 3429 GUID: 6D22231F ResultCode: 3
INFO[18:42:31.844711] Connection accepted: 10.0.6.23:50259 ClientSD: 76 Secure: 1
INFO[18:42:32.066722] Cipher: AES128-SHA256, SSL Version: TLSv1.2, ClientSD: 76
INFO[18:42:32.144798] Device registration started. ClientSD: 76 Protocol Version : 16 ThreadID: 3436 GUID: 8FEEFBE3
INFO[18:42:32.252197] Device registered. ID: 41, ClientSD: 76 Protocol Version: 16 ThreadID: 3436 GUID: 8FEEFBE3 ResultCode: 3
INFO[18:42:34.104287] Connection accepted: 10.0.6.31:51647 ClientSD: 65 Secure: 1
INFO[18:42:34.335620] Cipher: AES128-SHA256, SSL Version: TLSv1.2, ClientSD: 65
INFO[18:42:34.413766] Device registration started. ClientSD: 65 Protocol Version : 16 ThreadID: 3437 GUID: C6F84F51
INFO[18:42:34.506389] Device registered. ID: 39, ClientSD: 65 Protocol Version: 16 ThreadID: 3437 GUID: C6F84F51 ResultCode: 3
ERR[18:42:36.864235] Could not get any token for any remote gateway from AD serv er.
INFO[18:43:03.465602] Connection accepted: 10.0.6.17:57711 ClientSD: 37 Secure: 1
INFO[18:43:03.683150] Cipher: AES128-SHA256, SSL Version: TLSv1.2, ClientSD: 37
INFO[18:43:03.765562] Device registration started. ClientSD: 37 Protocol Version : 16 ThreadID: 3448 GUID: 6D22231F
INFO[18:43:03.970584] Device registered. ID: 34, ClientSD: 37 Protocol Version: 16 ThreadID: 3448 GUID: 6D22231F ResultCode: 3
ERR[18:43:37.060390] Could not get any token for any remote gateway from AD serv er.
INFO[18:43:38.481025] Connection accepted: 10.0.6.23:52606 ClientSD: 33 Secure: 1
INFO[18:43:38.698510] Cipher: AES128-SHA256, SSL Version: TLSv1.2, ClientSD: 33
INFO[18:43:38.776872] Device registration started. ClientSD: 33 Protocol Version : 16 ThreadID: 3456 GUID: 8FEEFBE3
INFO[18:43:38.899610] Device registered. ID: 41, ClientSD: 33 Protocol Version: 16 ThreadID: 3456 GUID: 8FEEFBE3 ResultCode: 3
INFO[18:44:01.439580] Connection accepted: 10.0.6.17:55112 ClientSD: 70 Secure: 1
INFO[18:44:01.663342] Cipher: AES128-SHA256, SSL Version: TLSv1.2, ClientSD: 70
INFO[18:44:01.741630] Device registration started. ClientSD: 70 Protocol Version : 16 ThreadID: 3464 GUID: 6D22231F
INFO[18:44:01.858257] Device registered. ID: 34, ClientSD: 70 Protocol Version: 16 ThreadID: 3464 GUID: 6D22231F ResultCode: 3
INFO[18:44:20.964196] Connection accepted: 10.0.6.23:58865 ClientSD: 52 Secure: 1
INFO[18:44:21.182665] Cipher: AES128-SHA256, SSL Version: TLSv1.2, ClientSD: 52
INFO[18:44:21.265630] Device registration started. ClientSD: 52 Protocol Version : 16 ThreadID: 3465 GUID: 8FEEFBE3
INFO[18:44:21.353512] Device registered. ID: 41, ClientSD: 52 Protocol Version: 16 ThreadID: 3465 GUID: 8FEEFBE3 ResultCode: 3
ERR[18:44:36.277318] Could not get any token for any remote gateway from AD serv er.
INFO[18:44:53.719476] Connection accepted: 10.0.6.17:53307 ClientSD: 92 Secure: 1
INFO[18:44:53.938526] Cipher: AES128-SHA256, SSL Version: TLSv1.2, ClientSD: 92
INFO[18:44:54.017053] Device registration started. ClientSD: 92 Protocol Version : 16 ThreadID: 3477 GUID: 6D22231F
INFO[18:44:54.308631] Device registered. ID: 34, ClientSD: 92 Protocol Version: 16 ThreadID: 3477 GUID: 6D22231F ResultCode: 3
docker logs --tail=50 supla-cloud
supla:clean:passed-io-client-registration-dates
-----------------------------------------------
Client registration expiration date - cleared: 0
I/O Device registration expiration date - cleared: 0
supla:clean:disable-demo-client-apps
------------------------------------
Clients to disable: 0
supla:generate-schedules-executions
-----------------------------------
Schedules to regenerate: 0
Deleted expired scheduled executions: 0
supla:cyclic:send-server-messages
---------------------------------
172.18.0.4:80 127.0.0.1 - - [20/Nov/2024:18:43:21 +0000] "HEAD /api/server-info HTTP/1.1" 301 262 "-" "Wget/1.21"
172.18.0.4:80 172.18.0.2 - - [20/Nov/2024:18:43:39 +0000] "HEAD /api/server-stat us HTTP/1.1" 301 266 "-" "Wget/1.21"
172.18.0.4:80 127.0.0.1 - - [20/Nov/2024:18:43:52 +0000] "HEAD /api/server-info HTTP/1.1" 301 262 "-" "Wget/1.21"
supla:clean:passed-io-client-registration-dates
-----------------------------------------------
Client registration expiration date - cleared: 0
I/O Device registration expiration date - cleared: 0
supla:clean:disable-demo-client-apps
------------------------------------
Clients to disable: 0
supla:generate-schedules-executions
-----------------------------------
Schedules to regenerate: 0
Deleted expired scheduled executions: 0
supla:cyclic:send-server-messages
---------------------------------
172.18.0.4:80 127.0.0.1 - - [20/Nov/2024:18:44:22 +0000] "HEAD /api/server-info HTTP/1.1" 301 262 "-" "Wget/1.21"
172.18.0.4:80 172.18.0.2 - - [20/Nov/2024:18:44:39 +0000] "HEAD /api/server-stat us HTTP/1.1" 301 266 "-" "Wget/1.21"
172.18.0.4:80 127.0.0.1 - - [20/Nov/2024:18:44:53 +0000] "HEAD /api/server-info HTTP/1.1" 301 262 "-" "Wget/1.21"
docker logs --tail=50 supla-db
241120 15:12:32 InnoDB: Initializing buffer pool, size = 128.0M
241120 15:12:32 InnoDB: Completed initialization of buffer pool
241120 15:12:32 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 12525264046
241120 15:12:32 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...
InnoDB: Doing recovery: scanned up to log sequence number 12525270211
241120 15:12:34 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
241120 15:12:35 InnoDB: Waiting for the background threads to start
241120 15:12:36 InnoDB: 5.5.60 started; log sequence number 12525270211
241120 15:12:36 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
241120 15:12:36 [Note] - '0.0.0.0' resolves to '0.0.0.0';
241120 15:12:36 [Note] Server socket created on IP: '0.0.0.0'.
241120 15:12:36 [Note] Event Scheduler: Loaded 0 events
241120 15:12:36 [Note] mysqld: ready for connections.
Version: '5.5.60-0+deb7u1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian)
241120 18:51:13 [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.
241120 18:51:13 [Note] mysqld (mysqld 5.5.60-0+deb7u1) starting as process 1 ...
241120 18:51:13 [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.
241120 18:51:13 [Note] Plugin 'FEDERATED' is disabled.
241120 18:51:13 InnoDB: The InnoDB memory heap is disabled
241120 18:51:13 InnoDB: Mutexes and rw_locks use GCC atomic builtins
241120 18:51:13 InnoDB: Compressed tables use zlib 1.2.7
241120 18:51:13 InnoDB: Using Linux native AIO
241120 18:51:13 InnoDB: Initializing buffer pool, size = 128.0M
241120 18:51:13 InnoDB: Completed initialization of buffer pool
241120 18:51:13 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 12534536516
241120 18:51:13 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...
InnoDB: Doing recovery: scanned up to log sequence number 12534541273
241120 18:51:14 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
241120 18:51:15 InnoDB: Waiting for the background threads to start
241120 18:51:16 InnoDB: 5.5.60 started; log sequence number 12534541273
241120 18:51:16 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
241120 18:51:16 [Note] - '0.0.0.0' resolves to '0.0.0.0';
241120 18:51:16 [Note] Server socket created on IP: '0.0.0.0'.
241120 18:53:04 [Note] Event Scheduler: Loaded 0 events
241120 18:53:04 [Note] mysqld: ready for connections.
Version: '5.5.60-0+deb7u1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian)