Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Autostart wieder herstellen

    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

    Autostart wieder herstellen

    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      mamoel last edited by

      Neustart des Raspberry -> ioBroker startet ebenfalls

      Irgendwie sollte der Dienst über rc.d gestartet werden, das funktioniert nun aber nicht mehr.

      1 Reply Last reply Reply Quote 0
      • S
        Semenchkare last edited by

        Hallo,

        habe gleiches Problem.

        nach Neustart des Banana muss ich immer manuell nach /opt/iobroker und mit iobroker start starten.

        Habe ein BananaPiM2

        mit armbian (igor) (Jessie, deb 8.5).

        Versionen

        node: 4.21 (Link von iobroker-Installationsseite armbian)

        mpm: 2.14.7

        unter etc/init.d/ liegt die iobroker.sh…

        Bis zum heutigen Update ging eigentlich alles...

        1 Reply Last reply Reply Quote 0
        • Homoran
          Homoran Global Moderator Administrators last edited by

          Habt ihr schon mal todesmutig versucht ioBroker noch Mal drüberinstallieren?

          Vorher am besten npm cache leeren mit

          cd /opt/iobroker
          npm cache clean
          iobroker stop
          npm install iobroker --unsafe-perm
          iobroker start
          

          Gruß

          Rainer

          1 Reply Last reply Reply Quote 0
          • S
            Semenchkare last edited by

            root@bananapim2:/opt/iobroker# npm cache clean

            root@bananapim2:/opt/iobroker# iobroker stop

            Stopping iobroker controller daemon…

            iobroker controller daemon stopped.

            Exit code for "killall.sh": 0

            root@bananapim2:/opt/iobroker# npm install iobroker --unsafe-perm

            npm ERR! not a package /opt/iobroker/iobroker

            npm ERR! addLocal Could not install /opt/iobroker/iobroker

            npm ERR! Linux 4.6.3-sunxi

            npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "iobroker" "--unsafe-perm"

            npm ERR! node v4.2.1

            npm ERR! npm v2.14.7

            npm ERR! path /tmp/npm-1479-35c0aa2e/unpack-00c8201481af/package.json

            npm ERR! code ENOENT

            npm ERR! errno -2

            npm ERR! syscall open

            npm ERR! enoent ENOENT: no such file or directory, open '/tmp/npm-1479-35c0aa2e/unpack-00c8201481af/package.json'

            npm ERR! enoent This is most likely not a problem with npm itself

            npm ERR! enoent and is related to npm not being able to find a file.

            npm ERR! enoent

            npm ERR! Please include the following file with any support request:

            npm ERR! /opt/iobroker/npm-debug.log

            root@bananapim2:/opt/iobroker# npm ERR! not a package /opt/iobroker/iobroker

            1 Reply Last reply Reply Quote 0
            • Homoran
              Homoran Global Moderator Administrators last edited by

              Wechsel mal dein Repository auf "online"

              Gruß

              Rainer

              1 Reply Last reply Reply Quote 0
              • S
                Semenchkare last edited by

                ich habe es umgestellt unter ddem iobroker.admin.

                root@bananapim2:/opt/iobroker# npm install iobroker –unsafe-perm

                npm ERR! not a package /opt/iobroker/iobroker

                npm ERR! addLocal Could not install /opt/iobroker/iobroker

                npm ERR! Linux 4.6.3-sunxi

                npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "iobroker" "--unsafe-perm"

                npm ERR! node v4.2.1

                npm ERR! npm v2.14.7

                npm ERR! path /tmp/npm-1057-f0d6f77e/unpack-ef73c59e454a/package.json

                npm ERR! code ENOENT

                npm ERR! errno -2

                npm ERR! syscall open

                npm ERR! enoent ENOENT: no such file or directory, open '/tmp/npm-1057-f0d6f77e/unpack-ef73c59e454a/package.json'

                npm ERR! enoent This is most likely not a problem with npm itself

                npm ERR! enoent and is related to npm not being able to find a file.

                npm ERR! enoent

                npm ERR! Please include the following file with any support request:

                npm ERR! /opt/iobroker/npm-debug.log

                root@bananapim2:/opt/iobroker# npm ERR! not a package /opt/iobroker/iobroker

                1 Reply Last reply Reply Quote 0
                • Homoran
                  Homoran Global Moderator Administrators last edited by

                  Die neuen Versionen benötigen node 4.5

                  Mach mal ein

                  sudo apt-get update && apt-get upgrade
                  

                  Gruß

                  Rainer

                  1 Reply Last reply Reply Quote 0
                  • S
                    Semenchkare last edited by

                    oot@bananapim2:/opt/iobroker# sudo apt-get update && apt-get upgrade

                    Hit http://security.debian.org jessie/updates InRelease

                    Hit http://apt.armbian.com jessie InRelease

                    Ign http://httpredir.debian.org jessie InRelease

                    Get:1 http://httpredir.debian.org jessie-backports InRelease [166 kB]

                    Get:2 http://httpredir.debian.org jessie-updates InRelease [142 kB]

                    Hit http://security.debian.org jessie/updates/main armhf Packages

                    Hit https://deb.nodesource.com jessie InRelease

                    Hit http://httpredir.debian.org jessie Release.gpg

                    Hit http://security.debian.org jessie/updates/contrib armhf Packages

                    Hit http://apt.armbian.com jessie/main armhf Packages

                    Hit http://security.debian.org jessie/updates/non-free armhf Packages

                    Hit http://httpredir.debian.org jessie Release

                    Hit http://security.debian.org jessie/updates/contrib Translation-en

                    Hit http://security.debian.org jessie/updates/main Translation-en

                    Hit http://security.debian.org jessie/updates/non-free Translation-en

                    Get:3 http://httpredir.debian.org jessie-backports/main armhf Packages/DiffIndex [27.8 kB]

                    Get:4 http://httpredir.debian.org jessie-backports/non-free armhf Packages/DiffIndex [3,610 B]

                    Get:5 http://httpredir.debian.org jessie-backports/contrib armhf Packages/DiffIndex [17.7 kB]

                    Get:6 http://httpredir.debian.org jessie-backports/non-free Translation-en/DiffIndex [8,314 B]

                    Get:7 http://httpredir.debian.org jessie-backports/contrib Translation-en/DiffIndex [5,500 B]

                    Get:8 http://httpredir.debian.org jessie-backports/main Translation-en/DiffIndex [27.8 kB]

                    Get:9 http://httpredir.debian.org jessie-backports/main armhf 2016-09-07-0904.04.pdiff [1,346 B]

                    Hit https://deb.nodesource.com jessie/main Sources

                    Get:10 http://httpredir.debian.org jessie-updates/contrib Translation-en [14 B]

                    Get:11 http://httpredir.debian.org jessie-backports/main armhf 2016-09-07-1508.46.pdiff [1,456 B]

                    Hit https://deb.nodesource.com jessie/main armhf Packages

                    Get:12 https://deb.nodesource.com jessie/main Translation-en_US [162 B]

                    Get:13 https://deb.nodesource.com jessie/main Translation-en [162 B]

                    Get:14 https://deb.nodesource.com jessie/main Translation-en_US.UTF-8 [162 B]

                    Get:15 http://httpredir.debian.org jessie-updates/non-free Translation-en/DiffIndex [736 B]

                    Get:16 http://httpredir.debian.org jessie-backports/contrib armhf 2016-09-07-1508.46.pdiff [517 B]

                    Get:17 http://httpredir.debian.org jessie-backports/main armhf 2016-09-07-1508.46.pdiff [1,456 B]

                    Get:18 http://httpredir.debian.org jessie-updates/main armhf Packages/DiffIndex [5,440 B]

                    Hit http://httpredir.debian.org jessie/main armhf Packages

                    Hit http://httpredir.debian.org jessie/contrib Translation-en

                    Get:19 http://httpredir.debian.org jessie-updates/contrib armhf Packages [32 B]

                    Get:20 http://httpredir.debian.org jessie-updates/non-free armhf Packages/DiffIndex [736 B]

                    Get:21 http://httpredir.debian.org jessie-updates/main Translation-en/DiffIndex [2,704 B]

                    Get:22 https://deb.nodesource.com jessie/main Translation-en_US [162 B]

                    Get:23 https://deb.nodesource.com jessie/main Translation-en [162 B]

                    Hit http://httpredir.debian.org jessie/contrib armhf Packages

                    Hit http://httpredir.debian.org jessie/non-free armhf Packages

                    Hit http://httpredir.debian.org jessie/main Translation-en

                    Ign http://apt.armbian.com jessie/main Translation-en_US

                    Hit http://httpredir.debian.org jessie/non-free Translation-en

                    Get:24 https://deb.nodesource.com jessie/main Translation-en_US.UTF-8 [162 B]

                    Get:25 http://httpredir.debian.org jessie-backports/main 2016-09-07-0904.04.pdiff [1,228 B]

                    Ign http://apt.armbian.com jessie/main Translation-en

                    Ign http://apt.armbian.com jessie/main Translation-en_US.UTF-8

                    Get:26 https://deb.nodesource.com jessie/main Translation-en_US [162 B]

                    Get:27 https://deb.nodesource.com jessie/main Translation-en [162 B]

                    Get:28 https://deb.nodesource.com jessie/main Translation-en_US.UTF-8 [162 B]

                    Get:29 https://deb.nodesource.com jessie/main Translation-en_US [162 B]

                    Get:30 http://httpredir.debian.org jessie-backports/contrib armhf 2016-09-07-1508.46.pdiff [517 B]

                    Get:31 http://httpredir.debian.org jessie-backports/main 2016-09-07-0904.04.pdiff [1,228 B]

                    Get:32 https://deb.nodesource.com jessie/main Translation-en [162 B]

                    Get:33 https://deb.nodesource.com jessie/main Translation-en_US.UTF-8 [162 B]

                    Get:34 https://deb.nodesource.com jessie/main Translation-en_US [162 B]

                    Ign https://deb.nodesource.com jessie/main Translation-en_US

                    Get:35 https://deb.nodesource.com jessie/main Translation-en [162 B]

                    Ign https://deb.nodesource.com jessie/main Translation-en

                    Get:36 https://deb.nodesource.com jessie/main Translation-en_US.UTF-8 [162 B]

                    Ign https://deb.nodesource.com jessie/main Translation-en_US.UTF-8

                    Fetched 413 kB in 33s (12.5 kB/s)

                    Reading package lists… Done

                    Reading package lists... Done

                    Building dependency tree

                    Reading state information... Done

                    Calculating upgrade... Done

                    0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

                    root@bananapim2:/opt/iobroker# node -v

                    v4.2.1

                    irgendwie updatet er node nicht...

                    1 Reply Last reply Reply Quote 0
                    • M
                      mamoel last edited by

                      Ich habe auf meinem Pi2````
                      sudo apt-get update && apt-get upgrade

                      
                      dann:
                      
                      

                      root@raspberrypi:/opt/iobroker# npm cache clean
                      root@raspberrypi:/opt/iobroker# iobroker stop
                      Stopping iobroker controller daemon...
                      iobroker controller daemon stopped.
                      Exit code for "killall.sh": 0
                      root@raspberrypi:/opt/iobroker# npm install iobroker --unsafe-perm
                      npm ERR! not a package /opt/iobroker/iobroker
                      npm ERR! addLocal Could not install /opt/iobroker/iobroker
                      npm ERR! Linux 4.4.13-v7+
                      npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "iobroker" "- -unsafe-perm"
                      npm ERR! node v0.12.6
                      npm ERR! npm v2.11.2
                      npm ERR! path /tmp/npm-1110-2a6f4ee3/unpack-5a463a3465aa/package.json
                      npm ERR! code ENOENT
                      npm ERR! errno -2

                      npm ERR! enoent ENOENT, open '/tmp/npm-1110-2a6f4ee3/unpack-5a463a3465aa/package .json'
                      npm ERR! enoent This is most likely not a problem with npm itself
                      npm ERR! enoent and is related to npm not being able to find a file.
                      npm ERR! enoent

                      npm ERR! Please include the following file with any support request:
                      npm ERR! /opt/iobroker/npm-debug.log
                      root@raspberrypi:/opt/iobroker#

                      1 Reply Last reply Reply Quote 0
                      • Homoran
                        Homoran Global Moderator Administrators last edited by

                        Wie hast du das denn geschafft??? .

                        (Nicht böse gemeint)

                        Jetzt hast du eine ganz alte Version von node drauf!

                        Das ist Armbian für den bananapi m2?

                        Jetzt bitte durchführen

                        Die alten node & node.js Versionen deinstallieren

                        apt-get –purge remove node

                        apt-get --purge remove nodejs

                        apt-get autoremove

                        reboot

                        Node.js neu installieren

                        curl -sL https://deb.nodesource.com/setup_4.x | sudo -E bash -

                        sudo apt-get install -y build-essential nodejs

                        reboot

                        Gruß

                        Rainer

                        1 Reply Last reply Reply Quote 0
                        • M
                          mamoel last edited by

                          Die richtige Node-Version habe ich jetzt, aber die iobroker-Installation läuft immer noch nicht:````
                          root@raspberrypi:/opt/iobroker# npm install iobroker --unsafe-perm
                          npm ERR! not a package /opt/iobroker/iobroker
                          npm ERR! addLocal Could not install /opt/iobroker/iobroker
                          npm ERR! Linux 4.4.13-v7+
                          npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "iobroker" "--unsafe-perm"
                          npm ERR! node v4.5.0
                          npm ERR! npm v2.15.9
                          npm ERR! path /tmp/npm-1175-6e26a984/unpack-a9ea635b22b1/package.json
                          npm ERR! code ENOENT
                          npm ERR! errno -2
                          npm ERR! syscall open

                          npm ERR! enoent ENOENT: no such file or directory, open '/tmp/npm-1175-6e26a984/unpack-a9ea635b22b1/package.json'
                          npm ERR! enoent This is most likely not a problem with npm itself
                          npm ERR! enoent and is related to npm not being able to find a file.
                          npm ERR! enoent

                          npm ERR! Please include the following file with any support request:
                          npm ERR! /opt/iobroker/npm-debug.log
                          root@raspberrypi:/opt/iobroker#

                          
                          Witzigerweise funktioniert jetzt aber der Autostart wieder! :lol:
                          1 Reply Last reply Reply Quote 0
                          • Homoran
                            Homoran Global Moderator Administrators last edited by

                            @mamoel:

                            Witzigerweise funktioniert jetzt aber der Autostart wieder! `
                            Dafür war ja der ganze Aufwand.

                            Für den Rest bin ich mit meinem Latein am Ende.

                            Da muss leider jemand anderes ran.

                            Gruß

                            Rainer

                            1 Reply Last reply Reply Quote 0
                            • M
                              mamoel last edited by

                              Ich danke dir auf jeden Fall für deine Hilfe.

                              1 Reply Last reply Reply Quote 0
                              • S
                                Semenchkare last edited by

                                Bei mir klappts bestens. Vielen vielen Dank Rainer!

                                Ich bereue nicht, umgestiegen zu sein!

                                1 Reply Last reply Reply Quote 0
                                • Homoran
                                  Homoran Global Moderator Administrators last edited by

                                  @mamoel:

                                  Ich danke dir auf jeden Fall für deine Hilfe. `
                                  Ich fürchte ich habe euch zwei fröhlich durcheinandergeworfen.

                                  Du hast noch Wheezy drauf?

                                  Da war doch was mit node 4.xx???

                                  Vielleicht kann da mal ein Wissender drüber sehen.

                                  Gruß

                                  Rainer

                                  1 Reply Last reply Reply Quote 0
                                  • M
                                    mamoel last edited by

                                    Nein, ich habe (meines Wissens) Jessie auf meinem Raspberry Pi2.

                                    root@raspberrypi:~# cat /etc/os-release
                                    PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
                                    NAME="Raspbian GNU/Linux"
                                    VERSION_ID="8"
                                    VERSION="8 (jessie)"
                                    ID=raspbian
                                    ID_LIKE=debian
                                    HOME_URL="http://www.raspbian.org/"
                                    SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
                                    BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
                                    root@raspberrypi:~#
                                    
                                    
                                    1 Reply Last reply Reply Quote 0
                                    • Homoran
                                      Homoran Global Moderator Administrators last edited by

                                      Aber bei dir steht:
                                      @mamoel:

                                      Linux 4.4.13-v7+ `
                                      Und v7 ist Wheezy.

                                      Hättest du vor dem letzten Versuch nach Umstellung des Repository npm cache clean gemacht?

                                      Gruß

                                      Rainer

                                      1 Reply Last reply Reply Quote 0
                                      • M
                                        mamoel last edited by

                                        Ich behaupte mal "ja".

                                        Bist du sicher, dass die v7 für Wheezy steht? Ich habe meinen Raspberry erst vor ein paar Wochen komplett neu vom letzten Raspbian Image neu installiert. Da sollte kein Wheezy reingekommen sein.

                                        1 Reply Last reply Reply Quote 0
                                        • Homoran
                                          Homoran Global Moderator Administrators last edited by

                                          @mamoel:

                                          Bist du sicher, dass die v7 für Wheezy steht? `
                                          https://www.debian.org/News/2013/20130504

                                          root@Test-Pi3:~# cat  /etc/issue                                                                                                                                                      
                                          Raspbian GNU/Linux 8 \n \l
                                          

                                          Gruß

                                          Rainer

                                          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

                                          750
                                          Online

                                          31.9k
                                          Users

                                          80.3k
                                          Topics

                                          1.3m
                                          Posts

                                          4
                                          21
                                          5499
                                          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