Supla docker na ubuntu wersja 25.02. Wczoraj wszystkie urządzenia poza virtual-device rozłączyły się z serwerem i nie mogę ich ponownie podłączyć. Urządzenia są widoczne w sieci WIFI na część z nich która ma wystawione GUI bez problemu się loguję ale ich status to rozłączony. Podobnie mam w supla cloud wszystko z czerwonym statusem niedostępny.
Zatrzymałem suplę, wyczyściłem obrazy zrobiłem nawet docker system prune. Odpaliłem na nowo obrazy się pobrały na nowo wszystko wstało ale bez zmian jedynie virtual device jest podłączony. W logach supla-server jedyny błąd to Could not get any token ale mam wrażenie że miałem go już wcześniej:
Code: Select all
2025-03-22 15:07:35,304 INFO success: supla-scheduler entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-03-22 15:07:35,304 INFO success: supla-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
INFO[15:07:40.843639] Connection accepted: 192.168.1.1:35140 ClientSD: 14 Secure: 1
INFO[15:07:40.849343] Cipher: TLS_AES_256_GCM_SHA384, SSL Version: TLSv1.3, ClientSD: 14
INFO[15:07:40.854663] Connection accepted: 192.168.1.1:59648 ClientSD: 17 Secure: 0
INFO[15:07:41.011423] Connection accepted: 192.168.1.1:35146 ClientSD: 21 Secure: 1
INFO[15:07:41.016670] Cipher: TLS_AES_256_GCM_SHA384, SSL Version: TLSv1.3, ClientSD: 21
INFO[15:07:41.023696] Connection accepted: 192.168.1.1:59656 ClientSD: 24 Secure: 0
ERR[15:08:34.423055] Could not get any token for any remote gateway from AD server.
INFO[15:09:16.439394] Connection accepted: 192.168.1.1:36674 ClientSD: 15 Secure: 1
INFO[15:09:16.449458] Cipher: TLS_AES_256_GCM_SHA384, SSL Version: TLSv1.3, ClientSD: 15
INFO[15:09:16.457937] Connection accepted: 192.168.1.1:48008 ClientSD: 17 Secure: 0
INFO[15:09:16.547038] Connection accepted: 192.168.1.1:36688 ClientSD: 16 Secure: 1
INFO[15:09:16.553399] Cipher: TLS_AES_256_GCM_SHA384, SSL Version: TLSv1.3, ClientSD: 16
INFO[15:09:16.560446] Connection accepted: 192.168.1.1:48020 ClientSD: 21 Secure: 0
ERR[15:09:34.548113] Could not get any token for any remote gateway from AD server.W logu cloud nie widzę żadnych błędów:
Code: Select all
Database connection has been established.
[OK] Metadata storage synchronized
[OK] Already at the latest version
("SuplaBundle\Migrations\Migration\Version20250104154701")
[OK] The "async" transport was set up successfully.
Creating SQL procedures and views
=================================
Number of scripts to execute: 29
Procedures
----------
✅ supla_add_channel.sql
✅ supla_add_client.sql
✅ supla_add_em_current_log_item.sql
✅ supla_add_em_power_active_log_item.sql
✅ supla_add_em_voltage_aberration_log_item.sql
✅ supla_add_em_voltage_log_item.sql
✅ supla_add_iodevice.sql
✅ supla_calculate_channel_checksum.sql
✅ supla_current_weekday_hour.sql
✅ supla_is_now_active.sql
✅ supla_mark_gate_closed.sql
✅ supla_mark_gate_open.sql
✅ supla_mqtt_broker_auth.sql
✅ supla_set_channel_caption.sql
✅ supla_set_channel_json_config.sql
✅ supla_set_closing_attempt.sql
✅ supla_set_device_json_config.sql
✅ supla_update_channel_conflict_details.sql
✅ supla_update_channel_flags.sql
✅ supla_update_channel_functions.sql
✅ supla_update_channel_state.sql
✅ supla_update_client.sql
✅ supla_update_device_pairing_result.sql
✅ supla_update_iodevice.sql
✅ supla_update_push_notification_client_token.sql
✅ supla_update_subdevice.sql
Views
-----
✅ supla_v_accessid_active.sql
✅ supla_v_auto_gate_closing.sql
✅ supla_v_client_channel.sql
Client for webapp exists.
// Warming up the cache for the prod environment with debug
// false
[OK] Cache for the "prod" environment (debug=false) was successfully warmed.
2025-03-22 15:00:01,105 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
2025-03-22 15:00:01,107 INFO supervisord started with pid 1
2025-03-22 15:00:02,110 INFO spawned: 'apache' with pid 35
2025-03-22 15:00:02,113 INFO spawned: 'cron' with pid 36
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.18.0.3. Set the 'ServerName' directive globally to suppress this message
[Sat Mar 22 15:00:02.190998 2025] [ssl:warn] [pid 35:tid 35] AH01909: 172.18.0.3:443:0 server certificate does NOT include an ID which matches the server name
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.18.0.3. Set the 'ServerName' directive globally to suppress this message
[Sat Mar 22 15:00:02.226656 2025] [ssl:warn] [pid 35:tid 35] AH01909: 172.18.0.3:443:0 server certificate does NOT include an ID which matches the server name
[Sat Mar 22 15:00:02.231373 2025] [mpm_prefork:notice] [pid 35:tid 35] AH00163: Apache/2.4.62 (Debian) OpenSSL/3.0.15 configured -- resuming normal operations
[Sat Mar 22 15:00:02.231396 2025] [core:notice] [pid 35:tid 35] AH00094: Command line: 'apache2 -D FOREGROUND'
2025-03-22 15:00:03,232 INFO success: apache entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-03-22 15:00:03,233 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
172.18.0.3:443 192.168.1.1 - - [22/Mar/2025:15:00:14 +0000] "GET /login HTTP/1.1" 200 4733 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36"
172.18.0.3:443 192.168.1.1 - - [22/Mar/2025:15:00:23 +0000] "POST /api/webapp-auth HTTP/1.1" 200 4404
172.18.0.3:443 192.168.1.1 - - [22/Mar/2025:15:00:24 +0000] "GET /api/users/current HTTP/1.1" 200 1045
"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36"
"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36"
172.18.0.3:443 192.168.1.1 - - [22/Mar/2025:15:00:24 +0000] "GET /api/iodevices?include=connected HTTP/1.1" 200 29617
172.18.0.3:443 192.168.1.1 - - [22/Mar/2025:15:00:24 +0000] "GET /api/channels?include=state,connected HTTP/1.1" 200 98883
172.18.0.3:80 127.0.0.1 - - [22/Mar/2025:15:00:26 +0000] "HEAD /api/server-info HTTP/1.1" 301 262 "-" "Wget/1.21.3"
"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36"
172.18.0.3:80 127.0.0.1 - - [22/Mar/2025:15:00:56 +0000] "HEAD /api/server-info HTTP/1.1" 301 262 "-" "Wget/1.21.3"
172.18.0.3:80 172.18.0.4 - - [22/Mar/2025:15:00:56 +0000] "HEAD /api/server-status HTTP/1.1" 301 266 "-" "Wget/1.21"
"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36"
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
---------------------------------Desperacja sięga zenitu mam już w głowie przełączanie się na publiczną instancję z najbardziej kluczowymi urządzeniami.
Może coś poradzicie nie wiem jak to debugować