Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Server Cannot start inMem-objects on port 9001

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    Server Cannot start inMem-objects on port 9001

    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      Dieter_P @Thomas Braun last edited by Dieter_P

      @thomas-braun said in Server Cannot start inMem-objects on port 9001:

      @dieter_p

      Den cupsd fängt man sich halt bevorzugt mit einem Desktop ein, deswegen komme ich darauf.

      npm cache mal gelöscht?

      Sollte man das forcen?

      pi@raspberrypi:~ $ sudo npm cache clean
      npm ERR! As of npm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid. If you want to make sure everything is consistent, use 'npm cache verify' instead. On the other hand, if you're debugging an issue with the installer, you can use `npm install --cache /tmp/empty-cache` to use a temporary cache instead of nuking the actual one.
      npm ERR!
      npm ERR! If you're sure you want to delete the entire cache, rerun this command with --force.
      
      npm ERR! A complete log of this run can be found in:
      npm ERR!     /root/.npm/_logs/2022-07-07T16_39_18_206Z-debug.log
      
      

      Edit: Durch ein Verify des caches ergab sich keine Änderung:

      pi@raspberrypi:~ $ npm cache verify
      Cache verified and compressed (~/.npm/_cacache):
      Content verified: 1864 (82698644 bytes)
      Index entries: 2895
      Finished in 41.415s
      pi@raspberrypi:~ $ cd /opt/iobroker
      pi@raspberrypi:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller
      
      > iobroker.js-controller@4.0.21 preinstall /opt/iobroker/node_modules/iobroker.js-controller
      > node lib/preinstallCheck.js
      
      NPM version: 6.14.17
      
      > iobroker.js-controller@4.0.21 install /opt/iobroker/node_modules/iobroker.js-controller
      > node iobroker.js setup first
      
      Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"!
      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/chokidar/node_modules/fsevents):
      npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.7 (node_modules/osx-temperature-sensor):
      npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/zigbee-herdsman/node_modules/fsevents):
      npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/fsevents):
      npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/zigbee-herdsman-converters/node_modules/fsevents):
      npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
      
      npm ERR! code ELIFECYCLE
      npm ERR! errno 24
      npm ERR! iobroker.js-controller@4.0.21 install: `node iobroker.js setup first`
      npm ERR! Exit status 24
      npm ERR!
      npm ERR! Failed at the iobroker.js-controller@4.0.21 install script.
      npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
      
      npm ERR! A complete log of this run can be found in:
      npm ERR!     /home/iobroker/.npm/_logs/2022-07-07T16_47_48_644Z-debug.log
      pi@raspberrypi:/opt/iobroker $
      
      

      Edit2: Etwas blöd, dass mir erst jetzt auffällt das ich in der Cloud nur BackUps bis zum 02.05.2022 liegen hab. Da scheint schon was länger nicht einwandfrei zu laufen. Sonst wäre eine Neuinstallation sicher der bessere Weg.

      1 Reply Last reply Reply Quote 0
      • apollon77
        apollon77 last edited by apollon77

        Dann ersuch mal Controller auf 4.0.23 ohne die install Skripte.

        Also

        cd /opt/iobroker
        npm i iobroker.js-controller@4.0.23 --ignore-scripts

        Dann mal

        iob status Bzw iob update

        Edit:und vorher sicherstellen das wirklich aus ist. Also auch das im logfile unter /opt/iobroker/log nix neues kommt.

        D 1 Reply Last reply Reply Quote 0
        • D
          Dieter_P @apollon77 last edited by

          @apollon77
          Danke. Leider noch gleiche Meldungen:

          pi@raspberrypi:/opt/iobroker/log $ nano iobroker.2022-07-08.log
          pi@raspberrypi:/opt/iobroker/log $ cd /opt/iobroker
          pi@raspberrypi:/opt/iobroker $ npm i iobroker.js-controller@4.0.23 --ignore-scripts
          npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/chokidar/node_modules/fsevents):
          npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
          npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.7 (node_modules/osx-temperature-sensor):
          npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
          npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/zigbee-herdsman-converters/node_modules/fsevents):
          npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
          npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/fsevents):
          npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
          npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/zigbee-herdsman/node_modules/fsevents):
          npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
          
          + iobroker.js-controller@4.0.23
          added 6 packages from 10 contributors and removed 3 packages in 156.871s
          
          87 packages are looking for funding
            run `npm fund` for details
          
          pi@raspberrypi:/opt/iobroker $ cd
          pi@raspberrypi:~ $ iob status
          No connection to databases possible ...
          pi@raspberrypi:~ $ iob update
          No connection to databases possible ...
          pi@raspberrypi:~ $ npm fund
          /home/pi
          
          
          
             ╭────────────────────────────────────────────────────────────────╮
             │                                                                │
             │      New major version of npm available! 6.14.17 → 8.13.2      │
             │   Changelog: https://github.com/npm/cli/releases/tag/v8.13.2   │
             │               Run npm install -g npm to update!                │
             │                                                                │
             ╰────────────────────────────────────────────────────────────────╯
          
          pi@raspberrypi:~ $
          
          
          apollon77 1 Reply Last reply Reply Quote 0
          • apollon77
            apollon77 @Dieter_P last edited by

            @dieter_p Dann bitte "Iob custom" aufrufen und die Ausgabe zeigen. kannst DU mit CTRL-C abbrechen. Und bitte auch zeigen was ein "iob start" im ioBroker log bringt

            D 1 Reply Last reply Reply Quote 0
            • D
              Dieter_P @apollon77 last edited by Dieter_P

              @apollon77 said in Server Cannot start inMem-objects on port 9001:

              Iob custom

              Danke. Der Befehl "custom" fehlt oder ich mach was falsch

              pi@raspberrypi:~ $ iob custom
              iobroker [command]
              
              Commands:
                iobroker setup                                               Setup ioBroker
                iobroker start [all|<adapter>.<instance>]                    Starts the js-controller or a specified adapter instance
                iobroker stop [<adapter>.<instance>]                         stops the js-controller or a specified adapter instance
                iobroker restart [<adapter>.<instance>]                      Restarts js-controller or a specified adapter instance  [aliases: r]
                iobroker debug <adapter>[.<instance>]                        Starts a Node.js debugging session for the adapter instance
                iobroker info                                                Shows the host info
                iobroker logs [<adapter>]                                    Monitor log
                iobroker add <adapter> [desiredNumber]                       Add instance of adapter  [aliases: a]
                iobroker install <adapter>                                   Installs a specified adapter  [aliases: i]
                iobroker rebuild [<module>]                                  Rebuild all native modules or path
                iobroker url <url> [<name>]                                  Install adapter from specified url, e.g. GitHub
                iobroker del <adapter>                                       Remove adapter and all instances from this host  [aliases: delete]
                iobroker del <adapter>.<instance>                            Remove adapter instance  [aliases: delete]
                iobroker update [<repositoryUrl>]                            Update repository and list adapters
                iobroker upgrade                                             Upgrade management
                iobroker upload [all|<adapter>]                              Upload management  [aliases: u]
                iobroker object                                              Object management  [aliases: o]
                iobroker state                                               State management  [aliases: s]
                iobroker message <adapter>[.instance] <command> [<message>]  Send message to adapter instance/s
                iobroker list <type> [<filter>]                              List all entries, like objects
                iobroker chmod <mode> <file>                                 Change file rights
                iobroker chown <user> <group> <file>                         Change file ownership
                iobroker touch <file>                                        Touch file
                iobroker rm <file>                                           Remove file
                iobroker file                                                File management
                iobroker user                                                User commands
                iobroker group                                               group management
                iobroker host <hostname>                                     Set host to given hostname
                iobroker set <adapter>.<instance>                            Change settings of adapter config
                iobroker license <license.file or license.text>              Update license by given file
                iobroker cert                                                Certificate management
                iobroker clean <yes>                                         Clears all objects and states
                iobroker backup                                              Create backup
                iobroker restore <backup name or path>                       Restore a specified backup
                iobroker validate <backup name or path>                      Validate a specified backup
                iobroker status [all|<adapter>.<instance>]                   Status of ioBroker or adapter instance  [aliases: isrun]
                iobroker repo [<name>]                                       Show repo information
                iobroker uuid                                                Show uuid of the installation  [aliases: id]
                iobroker unsetup                                             Reset license, installation secret and language
                iobroker fix                                                 Execute the installation fixer script, this updates your ioBroker installation
                iobroker multihost                                           Multihost management
                iobroker compact                                             compact group management
                iobroker plugin                                              Plugin management
                iobroker version [<adapter>]                                 Show version of js-controller or specified adapter  [aliases: v]
              
              Options:
                --help  Show help  [boolean]
              pi@raspberrypi:~ $ iob info
              No connection to databases possible ...
              pi@raspberrypi:~ $ iob start
              pi@raspberrypi:~ $ iob status
              Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"!
              pi@raspberrypi:~ $
              
              
              
              Thomas Braun 1 Reply Last reply Reply Quote 0
              • Thomas Braun
                Thomas Braun Most Active @Dieter_P last edited by

                @dieter_p

                iobroker setup custom
                
                D apollon77 2 Replies Last reply Reply Quote 1
                • D
                  Dieter_P @Thomas Braun last edited by Dieter_P

                  @thomas-braun said in Server Cannot start inMem-objects on port 9001:

                  iobroker setup custom

                  Danke

                  pi@raspberrypi:~ $ iobroker setup custom
                  Current configuration:
                  - Objects database:
                    - Type: jsonl
                    - Host/Unix Socket: 127.0.0.1
                    - Port: 9001
                  - States database:
                    - Type: jsonl
                    - Host/Unix Socket: 127.0.0.1
                    - Port: 9000
                  - Data Directory: ../../iobroker-data/
                  
                  Type of objects DB [(j)sonl, (f)ile, (r)edis, ...], default [jsonl]:
                  
                  
                  Thomas Braun 1 Reply Last reply Reply Quote 0
                  • Thomas Braun
                    Thomas Braun Most Active @Dieter_P last edited by Thomas Braun

                    @dieter_p

                    Und wie sieht ein Start im LogFile aus?
                    Mit

                    tail -f /opt/iobroker/log/iobroker.current.log
                    

                    in einer zweiten Session nachschauen.

                    D 1 Reply Last reply Reply Quote 0
                    • D
                      Dieter_P @Thomas Braun last edited by

                      @thomas-braun said in Server Cannot start inMem-objects on port 9001:

                      tail -f /opt/iobroker/log/iobroker.current.log

                      Hab die MAC Adressen mal "angepasst" die sollten hier doch nichts zu beitragen, oder?

                      2022-07-08 10:24:44.819  - info: host.raspberrypi iobroker _restart
                      2022-07-08 10:24:53.399  - info: host.raspberrypi iobroker.js-controller version 4.0.23 js-controller starting
                      2022-07-08 10:24:53.424  - info: host.raspberrypi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
                      2022-07-08 10:24:53.427  - info: host.raspberrypi hostname: raspberrypi, node: v14.19.3
                      2022-07-08 10:24:53.429  - info: host.raspberrypi ip addresses: 192.168.0.38 2a02:908:13b7:xxxx:xxxx:4331:xxxxx:82ad fe80::xxx:b07e:xxxx:49ba 10.0.1.2
                      2022-07-08 10:25:23.502  - error: host.raspberrypi No connection to databases possible, restart
                      2022-07-08 10:25:23.559  - info: host.raspberrypi iobroker _restart
                      
                      
                      Thomas Braun 1 Reply Last reply Reply Quote 0
                      • Thomas Braun
                        Thomas Braun Most Active @Dieter_P last edited by

                        @dieter_p

                        Läuft das im Docker oder sowas?

                        D 1 Reply Last reply Reply Quote 0
                        • D
                          Dieter_P @Thomas Braun last edited by

                          @thomas-braun

                          Nein ganz klassisch auf nem RPI2 nur mit SD-Karte und nem ZigbeeStick.
                          Installiert über die Installationsanleitung aus der Doku hier.

                          apollon77 1 Reply Last reply Reply Quote 0
                          • apollon77
                            apollon77 @Thomas Braun last edited by

                            @thomas-braun ÄÄähhmm ja .. danke ...war zu spät gestern Abend am Handy. Sorry

                            1 Reply Last reply Reply Quote 0
                            • apollon77
                              apollon77 @Dieter_P last edited by

                              @dieter_p Komisch ... zeig mal "ip a" Ausgabe (hoffe das geht da). Ich will mal die Netzwerkinterfaces sehen. Weil erste Vermutung ist das die 127.0.0.1 whyever nicht auf sich selbst auflöst

                              D 1 Reply Last reply Reply Quote 0
                              • D
                                Dieter_P @apollon77 last edited by

                                @apollon77
                                Thx. Warum das jetzt auf einmal auftritt kommt mir auch komisch vor. Diese Konfig läuft so unverändert ca seit 1 Jahr inkl. Wireguard

                                pi@raspberrypi:~ $ ip a
                                1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
                                    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
                                    inet 127.0.0.1/8 scope host lo
                                       valid_lft forever preferred_lft forever
                                    inet6 ::1/128 scope host
                                       valid_lft forever preferred_lft forever
                                2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
                                    link/ether b8:27:xx:c2:xx:be brd ff:ff:ff:ff:ff:ff
                                    inet 192.168.0.38/24 brd 192.168.0.255 scope global noprefixroute eth0
                                       valid_lft forever preferred_lft forever
                                    inet6 2a02:xxx:13b7:xxxx:64ad:4331:xxxx:82ad/64 scope global dynamic mngtmpaddr noprefixroute
                                       valid_lft 68729sec preferred_lft 25529sec
                                    inet6 fe80::xxx:b07e:xxxx:49ba/64 scope link
                                       valid_lft forever preferred_lft forever
                                3: wgclient0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN group default qlen 1000
                                    link/none
                                    inet 10.0.1.2/24 scope global wgclient0
                                       valid_lft forever preferred_lft forever
                                
                                
                                1 Reply Last reply Reply Quote 0
                                • apollon77
                                  apollon77 last edited by

                                  Also das ganze funktioniert so. ioBroker startet und startet die DB auf dem Port 9000 und 9001 und die "Listenen" auf der IP (127.0.01 in deinem Fall) die angegeben ist. Sobald die DB gestartet ist versucht ein DB-Client in der Software sich darauf zu verbinden. Und DAS geht bei dir nicht, deswegen sagt der Client nach 30s ... da passt was net. Meine Vermutung ist das er bei diesem "eigentlich lokalen" verbindungsversuch nicht "lokal" rumkommt und daher das Listen auf 127.0.01 es blockt.

                                  Auch wenn ich nicht verstehe warum die 127.0.01 nicht geht (vllt hat Thomas noch ne Idee), ändere mal in /opt/iobroker/iobroker-data/iobroker.json in den objects und state Abschnitten die 127.0.01 gegen 0.0.0.0 und versuch dann mal. Damit "Listened" er auf "egal woher die verbindung kommt". Wenn das geht hast Du nen Workaround ...

                                  D 1 Reply Last reply Reply Quote 0
                                  • D
                                    Dieter_P @apollon77 last edited by

                                    @apollon77 said in Server Cannot start inMem-objects on port 9001:

                                    /opt/iobroker/iobroker-data/iobroker.json

                                    Vielen Dank auch für Deine für mich verständliche Erklärung! In Object und states angepasst aber leider immer noch der Zugriffsfehler:

                                    pi@raspberrypi:~ $ sudo nano /opt/iobroker/iobroker-data/iobroker.json
                                    pi@raspberrypi:~ $ iob stop
                                    pi@raspberrypi:~ $ iob start
                                    pi@raspberrypi:~ $ iob status
                                    Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"!
                                    pi@raspberrypi:~ $
                                    
                                    
                                    apollon77 1 Reply Last reply Reply Quote 0
                                    • Glasfaser
                                      Glasfaser @Dieter_P last edited by

                                      @dieter_p sagte in Server Cannot start inMem-objects on port 9001:

                                      Auf dem Pi läuft noch ein WireGuard Client

                                      Komischerweise ist er bei dir nicht aufgelistet !?

                                      Kannst du das nochmal zeigen :

                                      sudo netstat -ntlp | grep LISTEN
                                      
                                      D 1 Reply Last reply Reply Quote 0
                                      • D
                                        Dieter_P @Glasfaser last edited by

                                        @glasfaser said in Server Cannot start inMem-objects on port 9001:

                                        sudo netstat -ntlp | grep LISTEN

                                        pi@raspberrypi:~ $ sudo netstat -ntlp | grep LISTEN
                                        tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      443/sshd
                                        tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN      329/cupsd
                                        tcp6       0      0 :::22                   :::*                    LISTEN      443/sshd
                                        tcp6       0      0 ::1:631                 :::*                    LISTEN      329/cupsd
                                        
                                        

                                        Funktionieren, sollte er da ich auch über den Tunnel aktuell arbeiten kann.

                                        Glasfaser 1 Reply Last reply Reply Quote 0
                                        • Glasfaser
                                          Glasfaser @Dieter_P last edited by

                                          @dieter_p sagte in Server Cannot start inMem-objects on port 9001:

                                          Funktionieren, sollte er da ich auch über den Tunnel aktuell arbeiten kann.

                                          Wie hast du denn gerade Zugriff auf deinem Pi !?

                                          D 1 Reply Last reply Reply Quote 0
                                          • D
                                            Dieter_P @Glasfaser last edited by Dieter_P

                                            @glasfaser
                                            Auf diesen Pi direkt im lokalen Netz über Putty

                                            Wireguard verbindet bei mir 2 Netze. Ich sitze lokal im Netz des IOBroker der aktuell probleme macht. Da gibt es auch Routingtabellen ins andere Netz die aber liegen jeweils auf den Clients und nicht zentral am RPI da das nicht so einfach war, wenn ich das noch richtig zusammen bekomme.

                                            Das aber alles unverändert seit ca. 1 Jahr wo es lief.

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

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

                                            941
                                            Online

                                            31.9k
                                            Users

                                            80.2k
                                            Topics

                                            1.3m
                                            Posts

                                            40
                                            429
                                            69816
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo