Prywatna instancja: SUPLA Server is down. Status: DOWN

karnasw
Posts: 215
Joined: Fri Oct 02, 2020 10:22 am

Post

Cześć, dzisiaj przeniosłem serwer OpenMediaVault z Raspberry pi na Dell Wyse 5070, zainstalowałem standardowo suplę przez dockera. Wszystkie ustawienia mam takie jak miałem na Pi, poza typem obrazu arm32v7 -> latest. Mam problem z Cloud. Wszystkie urządzenia dodały się poprawnie, ale mają status rozłączony. Mogę nimi sterować z aplikacji Android. Na Cloud nie mogę praktycznie nic zrobić, nawet przy zmianie strefy czasowej mam komunikat "SUPLA Server is down. Status: DOWN". W logach mam tylko to:

Code: Select all

2024-03-17 17:45:33,369 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.
2024-03-17 17:45:33,371 INFO supervisord started with pid 1
2024-03-17 17:45:34,375 INFO spawned: 'supla-scheduler' with pid 21
2024-03-17 17:45:34,378 INFO spawned: 'supla-server' with pid 22
INFO[17:45:34.390229] Scheduler version 22.07.01
INFO[17:45:34.390315] Started at Sun Mar 17 17:45:34 2024
INFO[17:45:34.407311] Server version 24.02.02 [Protocol v23]
INFO[17:45:34.407796] Started at Sun Mar 17 17:45:34 2024
INFO[17:45:34.411327] SSL version: LibreSSL 3.5.4
INFO[17:45:34.446281] Connection accepted: 192.168.88.150:58459 ClientSD: 12 Secure: 0
INFO[17:45:34.498967] Connection accepted: 192.168.88.154:57479 ClientSD: 18 Secure: 0
INFO[17:45:34.510796] Connection accepted: 192.168.88.152:55429 ClientSD: 22 Secure: 0
INFO[17:45:34.523201] Connection accepted: 192.168.88.151:65144 ClientSD: 24 Secure: 0
INFO[17:45:34.590066] Device registration started. ClientSD: 12 Protocol Version: 20 ThreadID: 31 GUID: A107EC2E
INFO[17:45:34.596713] Device registration started. ClientSD: 18 Protocol Version: 20 ThreadID: 32 GUID: DC2C6A72
INFO[17:45:34.607735] Device registration started. ClientSD: 22 Protocol Version: 20 ThreadID: 33 GUID: 7C7D032A
INFO[17:45:34.620089] Device registration started. ClientSD: 24 Protocol Version: 20 ThreadID: 34 GUID: 95A1DDB1
INFO[17:45:34.622493] Device registered. ID: 1, ClientSD: 12 Protocol Version: 20 ThreadID: 31 GUID: A107EC2E ResultCode: 3
INFO[17:45:34.634655] Device registered. ID: 5, ClientSD: 18 Protocol Version: 20 ThreadID: 32 GUID: DC2C6A72 ResultCode: 3
ERR[17:45:34.636698] Could not get any token for any remote gateway from AD server.
INFO[17:45:34.638919] Device registered. ID: 2, ClientSD: 22 Protocol Version: 20 ThreadID: 33 GUID: 7C7D032A ResultCode: 3
INFO[17:45:34.639568] Device registered. ID: 4, ClientSD: 24 Protocol Version: 20 ThreadID: 34 GUID: 95A1DDB1 ResultCode: 3
2024-03-17 17:45:35,640 INFO success: supla-scheduler entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-03-17 17:45:35,641 INFO success: supla-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
INFO[17:45:36.355656] Connection accepted: 192.168.88.153:54443 ClientSD: 27 Secure: 0
INFO[17:45:36.460782] Device registration started. ClientSD: 27 Protocol Version: 20 ThreadID: 35 GUID: A349D619
INFO[17:45:36.486521] Device registered. ID: 3, ClientSD: 27 Protocol Version: 20 ThreadID: 35 GUID: A349D619 ResultCode: 3
INFO[17:46:01.779100] Connection accepted: 192.168.88.1:46742 ClientSD: 11 Secure: 1
INFO[17:46:01.820025] Cipher: TLS_AES_256_GCM_SHA384, SSL Version: TLSv1.3, ClientSD: 11
INFO[17:46:01.918440] Client registered. ClientSD: 11 Protocol Version: 23
INFO[17:46:28.896070] Connection accepted: 192.168.88.1:56412 ClientSD: 33 Secure: 1
INFO[17:46:28.906153] Cipher: TLS_AES_256_GCM_SHA384, SSL Version: TLSv1.3, ClientSD: 33
INFO[17:46:28.967819] Connection accepted: 192.168.88.1:35000 ClientSD: 30 Secure: 0
INFO[17:46:29.299350] Connection accepted: 192.168.88.1:56414 ClientSD: 36 Secure: 1
INFO[17:46:29.310964] Cipher: TLS_AES_256_GCM_SHA384, SSL Version: TLSv1.3, ClientSD: 36
INFO[17:46:29.373617] Connection accepted: 192.168.88.1:35016 ClientSD: 35 Secure: 0
INFO[17:46:31.645149] Connection accepted: 192.168.88.1:56426 ClientSD: 34 Secure: 1
INFO[17:46:31.650669] Cipher: TLS_AES_256_GCM_SHA384, SSL Version: TLSv1.3, ClientSD: 34
INFO[17:46:31.671222] Connection accepted: 192.168.88.1:35028 ClientSD: 36 Secure: 0
ERR[17:46:34.896023] Could not get any token for any remote gateway from AD server.
Gdzie może leżeć problem?
Top
User avatar
pzygmunt
Posts: 20302
Joined: Tue Jan 19, 2016 9:26 am
Location: Paczków
Been thanked: 59 times

Post

Z tych logów nic nie wynika. Może kontener cloud-a nie ma dostępu do gniazda służącego do komunikacji z supla-server.
SUPLA.... Nareszcie w domu.
Top
karnasw
Posts: 215
Joined: Fri Oct 02, 2020 10:22 am

Post

Właśnie nie wiem za co się złapać bo w logach nic nie ma. Urządzenia wpadają poprawnie. Sprawdzę jeszcze te sieci w kontenerach.
Tutaj ustawienia sieciówek:

Code: Select all

[
  {
    "Name": "supla_default",
    "Id": "118281408ac38fcb95da1a45dcd8dca854553613164491743e7077c2d7a32646",
    "Created": "2024-03-18T10:30:30.845127245+01:00",
    "Scope": "local",
    "Driver": "bridge",
    "EnableIPv6": false,
    "IPAM": {
      "Driver": "default",
      "Options": null,
      "Config": [
        {
          "Subnet": "172.18.0.0/16",
          "Gateway": "172.18.0.1"
        }
      ]
    },
    "Internal": false,
    "Attachable": false,
    "Ingress": false,
    "ConfigFrom": {
      "Network": ""
    },
    "ConfigOnly": false,
    "Containers": {
      "33628663d3b5deb47b4dbe119b2c5677fc3a4749d37f3102bc066b77c24dd652": {
        "Name": "supla-db",
        "EndpointID": "9f013e0d9303fe9959e23e44cf8626b2dee751d27e51bb6cc2c3151831ab6bc2",
        "MacAddress": "02:42:ac:12:00:02",
        "IPv4Address": "172.18.0.2/16",
        "IPv6Address": ""
      },
      "6bbc05ec338f3a5139c0d72b6a74164e1631c3f29a6a988046d918dd25d6c537": {
        "Name": "supla-server",
        "EndpointID": "d0d8182ff1760fecfb02eeae92fdf4acce0d48e52cbb88d459735f0d969e9238",
        "MacAddress": "02:42:ac:12:00:03",
        "IPv4Address": "172.18.0.3/16",
        "IPv6Address": ""
      },
      "d481ac4a0a365caa8765ed25b053d7122f00299fcef209f8878053de0ceb6e7e": {
        "Name": "supla-cloud",
        "EndpointID": "54db3e79e2006e99f32b305b4bd80db8e3629c5547866c306e85cc9e87e49cb5",
        "MacAddress": "02:42:ac:12:00:04",
        "IPv4Address": "172.18.0.4/16",
        "IPv6Address": ""
      }
    },
    "Options": {},
    "Labels": {
      "com.docker.compose.network": "default",
      "com.docker.compose.project": "supla",
      "com.docker.compose.version": "2.24.7"
    }
  }
]
Trochę jest też dziwne to, że zmienię np. nazwę lokalizacji i wyrzuci mi błąd, ale nazwa lokalizacji się zmienia (widać to też w aplikacji android). Więc jakieś połączenie ma.

I przy próbie usunięcia mam informacje w logu, ale niestety blokuje mnie błąd:

Code: Select all

172.18.0.4:443 192.168.88.100 - - [18/Mar/2024:10:39:04 +0000] "GET /api/iodevices/5?include=connected HTTP/1.1" 200 2939 "https://192.168.88.10:6443/devices/5/channels" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36 Edg/122.0.0.0"
172.18.0.4:443 192.168.88.100 - - [18/Mar/2024:10:39:06 +0000] "GET /api/channels?include=connected HTTP/1.1" 200 15650 "https://192.168.88.10:6443/devices/5/channels" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36 Edg/122.0.0.0"
172.18.0.4:443 192.168.88.100 - - [18/Mar/2024:10:39:07 +0000] "DELETE /api/iodevices/5?safe=0 HTTP/1.1" 503 434 "https://192.168.88.10:6443/devices/5/channels" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36 Edg/122.0.0.0"
172.18.0.4:443 192.168.88.100 - - [18/Mar/2024:10:39:11 +0000] "GET /api/iodevices/5?include=connected HTTP/1.1" 200 1458 "https://192.168.88.10:6443/devices/5/channels" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36 Edg/122.0.0.0"
Top
karnasw
Posts: 215
Joined: Fri Oct 02, 2020 10:22 am

Post

Znalazłem przyczynę, openmediavault podczas tworzenia tworzenia folderów nadaje im maskę 2775, po wyłączeniu ustawienia GID na folderach (0775) wszystko działa poprawnie.

Czy w supla-docker jest możliwość ustawienia przekazywania GID i UID w zmiennych środowiskowych?
Top

Return to “Pomoc”