Skip to content
  • Home
  • Recent
  • Tags
  • 0 Unread 0
  • Categories
  • Unreplied
  • Popular
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Cloud Dienste
  4. Cloud Adapter nicht erreichbar

NEWS

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    17
    1
    2.8k

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    1.1k

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    25
    1
    2.4k

Cloud Adapter nicht erreichbar

Scheduled Pinned Locked Moved Cloud Dienste
24 Posts 5 Posters 2.3k Views 4 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S siggi25

    @thomas-braun said in Cloud Adapter nicht erreichbar:

    sudo usermod -aG adm goppel

    habe ich gemacht

    Thomas BraunT Online
    Thomas BraunT Online
    Thomas Braun
    Most Active
    wrote on last edited by
    #21

    @siggi25

    Dann nochmal

    systemctl status networking.service
    

    Linux-Werkzeugkasten:
    https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
    NodeJS Fixer Skript:
    https://forum.iobroker.net/topic/68035/iob-node-fix-skript
    iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

    S 1 Reply Last reply
    0
    • Thomas BraunT Thomas Braun

      @siggi25

      Dann nochmal

      systemctl status networking.service
      
      S Offline
      S Offline
      siggi25
      wrote on last edited by
      #22

      @thomas-braun said in Cloud Adapter nicht erreichbar:

      systemctl status networking.service

      Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
      permitted by applicable law.
      Last login: Sat Sep 14 21:27:39 CEST 2024 on tty1
      goppel@iobroker:~$ systemctl status networking.service
      x networking.service - Raise network interfaces
           Loaded: loaded (/lib/systemd/system/networking.service; enabled; preset: enabled)
           Active: failed (Result: timeout) since Sat 2024-09-14 21:27:10 CEST; 25min ago
             Docs: man:interfaces(5)
          Process: 68 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
          Process: 164 ExecStopPost=/usr/bin/touch /run/network/restart-hotplug (code=exited, status=0/SUCCESS)
         Main PID: 68 (code=exited, status=1/FAILURE)
              CPU: 66ms
      
      Sep 14 21:26:44 iobroker ifup[157]: XMT:  | X-- Request renew in  +3600
      Sep 14 21:26:44 iobroker ifup[157]: XMT:  | X-- Request rebind in +5400
      Sep 14 21:26:44 iobroker ifup[157]: XMT: Solicit on eth0, interval 128150ms.
      Sep 14 21:26:44 iobroker dhclient[157]: XMT: Solicit on eth0, interval 128150ms.
      Sep 14 21:27:10 iobroker systemd[1]: networking.service: start operation timed out. Terminating.
      Sep 14 21:27:10 iobroker systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
      Sep 14 21:27:10 iobroker ifup[68]: Got signal Terminated, terminating...
      Sep 14 21:27:10 iobroker ifup[68]: ifup: failed to bring up eth0
      Sep 14 21:27:10 iobroker systemd[1]: networking.service: Failed with result 'timeout'.
      Sep 14 21:27:10 iobroker systemd[1]: Failed to start networking.service - Raise network interfaces.
      
      Thomas BraunT 1 Reply Last reply
      0
      • S siggi25

        @thomas-braun said in Cloud Adapter nicht erreichbar:

        systemctl status networking.service

        Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
        permitted by applicable law.
        Last login: Sat Sep 14 21:27:39 CEST 2024 on tty1
        goppel@iobroker:~$ systemctl status networking.service
        x networking.service - Raise network interfaces
             Loaded: loaded (/lib/systemd/system/networking.service; enabled; preset: enabled)
             Active: failed (Result: timeout) since Sat 2024-09-14 21:27:10 CEST; 25min ago
               Docs: man:interfaces(5)
            Process: 68 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
            Process: 164 ExecStopPost=/usr/bin/touch /run/network/restart-hotplug (code=exited, status=0/SUCCESS)
           Main PID: 68 (code=exited, status=1/FAILURE)
                CPU: 66ms
        
        Sep 14 21:26:44 iobroker ifup[157]: XMT:  | X-- Request renew in  +3600
        Sep 14 21:26:44 iobroker ifup[157]: XMT:  | X-- Request rebind in +5400
        Sep 14 21:26:44 iobroker ifup[157]: XMT: Solicit on eth0, interval 128150ms.
        Sep 14 21:26:44 iobroker dhclient[157]: XMT: Solicit on eth0, interval 128150ms.
        Sep 14 21:27:10 iobroker systemd[1]: networking.service: start operation timed out. Terminating.
        Sep 14 21:27:10 iobroker systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
        Sep 14 21:27:10 iobroker ifup[68]: Got signal Terminated, terminating...
        Sep 14 21:27:10 iobroker ifup[68]: ifup: failed to bring up eth0
        Sep 14 21:27:10 iobroker systemd[1]: networking.service: Failed with result 'timeout'.
        Sep 14 21:27:10 iobroker systemd[1]: Failed to start networking.service - Raise network interfaces.
        
        Thomas BraunT Online
        Thomas BraunT Online
        Thomas Braun
        Most Active
        wrote on last edited by
        #23

        @siggi25

        Bei LXCs weiß ich nicht wie da das Netzwerk aufgesetzt wird.

        Linux-Werkzeugkasten:
        https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
        NodeJS Fixer Skript:
        https://forum.iobroker.net/topic/68035/iob-node-fix-skript
        iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

        S 1 Reply Last reply
        0
        • Thomas BraunT Thomas Braun

          @siggi25

          Bei LXCs weiß ich nicht wie da das Netzwerk aufgesetzt wird.

          S Offline
          S Offline
          siggi25
          wrote on last edited by
          #24

          @thomas-braun
          Vielen Dank trotzdem für deine Hilfe, kannst du mir jemanden sagen,
          der sich mit lxc netzwerk auskennt ?
          Gruß Gisela

          1 Reply Last reply
          0
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          Support us

          ioBroker
          Community Adapters
          Donate
          FAQ Cloud / IOT
          HowTo: Node.js-Update
          HowTo: Backup/Restore
          Downloads
          BLOG

          710

          Online

          32.6k

          Users

          82.3k

          Topics

          1.3m

          Posts
          Community
          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
          ioBroker Community 2014-2025
          logo
          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • Home
          • Recent
          • Tags
          • Unread 0
          • Categories
          • Unreplied
          • Popular
          • GitHub
          • Docu
          • Hilfe