Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. [gelöst]iobroker startet nicht/nicht aufrufbar

    NEWS

    • Wir empfehlen: Node.js 22.x

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker goes Matter ... Matter Adapter in Stable

    [gelöst]iobroker startet nicht/nicht aufrufbar

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

      root@cubietruck:~# cd /opt/iobroker
root@cubietruck:/opt/iobroker# ./reinstall.sh
-bash: ./reinstall.sh: /bin/bash^M: bad interpreter: No suc
 file or directory
root@cubietruck:/opt/iobroker#
      1 Reply Last reply Reply Quote 0
      • paul53
        paul53 last edited by

        Die Datei liegt im DOS-Format vor und muss erst in das Linux-Format gewandelt werden.

        cd /opt/iobroker
mv reinstall.sh reinstall.dos
tr -d '\r' < reinstall.dos > reinstall.sh
chmod +x reinstall.sh
./reinstall.sh
        1 Reply Last reply Reply Quote 0
        • B
          blackangel15741 last edited by

          Ist das jetzt gut?

          Am Ende steht was mit syntax error

          DONE iobroker.admin

> iobroker.js-controller@1.4.2 preinstall /opt/iobroker/nod
_modules/iobroker.js-controller
> node lib/preinstall_check.js

NPM version: 6.2.0
npm version >= 5: disabling package-lock

> unix-dgram@0.2.3 install /opt/iobroker/node_modules/unix-
gram
> node-gyp rebuild

make: Entering directory '/opt/iobroker/node_modules/unix-d
ram/build'
  CXX(target) Release/obj.target/unix_dgram/src/unix_dgram.
  SOLINK_MODULE(target) Release/obj.target/unix_dgram.node
  COPY Release/unix_dgram.node
make: Leaving directory '/opt/iobroker/node_modules/unix-dg
am/build'

> iobroker.js-controller@1.4.2 install /opt/iobroker/node_m
dules/iobroker.js-controller
> node iobroker.js setup first

+ iobroker.js-controller@1.4.2
added 175 packages from 129 contributors and audited 1104 p
ckages in 106.891s
found 22 vulnerabilities (16 low, 6 high)
  run `npm audit fix` to fix them, or `npm audit` for detai
s
DONE iobroker.js-controller
+ iobroker.telegram@1.2.5
added 36 packages from 81 contributors and audited 1241 pac
ages in 51.361s
found 23 vulnerabilities (17 low, 6 high)
  run `npm audit fix` to fix them, or `npm audit` for detai
s
DONE iobroker.telegram
Cannot find io-package.json in null
Cannot parse null/io-package.json:Error: ENOENT: no such fi
e or directory, open 'null/io-package.json'
Cannot find io-package.json in null
Cannot parse null/io-package.json:Error: ENOENT: no such fi
e or directory, open 'null/io-package.json'
Cannot find io-package.json in null
Cannot parse null/io-package.json:Error: ENOENT: no such fi
e or directory, open 'null/io-package.json'
got /opt/iobroker/node_modules/iobroker.telegram/admin
upload [4] telegram.admin /opt/iobroker/node_modules/iobrok
r.telegram/admin/words.js words.js application/javascript
upload [3] telegram.admin /opt/iobroker/node_modules/iobrok
r.telegram/admin/telegram.png telegram.png image/png
upload [2] telegram.admin /opt/iobroker/node_modules/iobrok
r.telegram/admin/index_m.html index_m.html text/html
upload [1] telegram.admin /opt/iobroker/node_modules/iobrok
r.telegram/admin/index.html index.html text/html
upload [0] telegram.admin /opt/iobroker/node_modules/iobrok
r.telegram/admin/blockly.js blockly.js application/javascri
t
Update "system.adapter.telegram.0"
Cannot find io-package.json in null
Cannot parse null/io-package.json:Error: ENOENT: no such fi
e or directory, open 'null/io-package.json'
Cannot find io-package.json in null
Cannot parse null/io-package.json:Error: ENOENT: no such fi
e or directory, open 'null/io-package.json'
Cannot find io-package.json in null
Cannot parse null/io-package.json:Error: ENOENT: no such fi
e or directory, open 'null/io-package.json'
Cannot find io-package.json in null
Cannot parse null/io-package.json:Error: ENOENT: no such fi
e or directory, open 'null/io-package.json'
Cannot find io-package.json in null
Cannot parse null/io-package.json:Error: ENOENT: no such fi
e or directory, open 'null/io-package.json'
Cannot find io-package.json in null
Cannot parse null/io-package.json:Error: ENOENT: no such fi
e or directory, open 'null/io-package.json'
Cannot find io-package.json in null
Cannot parse null/io-package.json:Error: ENOENT: no such fi
e or directory, open 'null/io-package.json'
Cannot find io-package.json in null
Cannot parse null/io-package.json:Error: ENOENT: no such fi
e or directory, open 'null/io-package.json'
Cannot find io-package.json in null
Cannot parse null/io-package.json:Error: ENOENT: no such fi
e or directory, open 'null/io-package.json'
Cannot find io-package.json in null
Cannot parse null/io-package.json:Error: ENOENT: no such fi
e or directory, open 'null/io-package.json'
Cannot find io-package.json in null
Cannot parse null/io-package.json:Error: ENOENT: no such fi
e or directory, open 'null/io-package.json'
Cannot find io-package.json in null
Cannot parse null/io-package.json:Error: ENOENT: no such fi
e or directory, open 'null/io-package.json'
Cannot find io-package.json in null
Cannot parse null/io-package.json:Error: ENOENT: no such fi
e or directory, open 'null/io-package.json'
Cannot find io-package.json in null
Cannot parse null/io-package.json:Error: ENOENT: no such fi
e or directory, open 'null/io-package.json'
Cannot find io-package.json in null
Cannot parse null/io-package.json:Error: ENOENT: no such fi
e or directory, open 'null/io-package.json'
Cannot find io-package.json in null
Cannot parse null/io-package.json:Error: ENOENT: no such fi
e or directory, open 'null/io-package.json'
Cannot find io-package.json in null
Cannot parse null/io-package.json:Error: ENOENT: no such fi
e or directory, open 'null/io-package.json'
Cannot find io-package.json in null
Cannot parse null/io-package.json:Error: ENOENT: no such fi
e or directory, open 'null/io-package.json'
Cannot find io-package.json in null
Cannot parse null/io-package.json:Error: ENOENT: no such fi
e or directory, open 'null/io-package.json'
Cannot find io-package.json in null
Cannot parse null/io-package.json:Error: ENOENT: no such fi
e or directory, open 'null/io-package.json'
Cannot find io-package.json in null
Cannot parse null/io-package.json:Error: ENOENT: no such fi
e or directory, open 'null/io-package.json'
got /opt/iobroker/node_modules/iobroker.admin/admin
upload [3] admin.admin /opt/iobroker/node_modules/iobroker.
dmin/admin/words.js words.js application/javascript
upload [2] admin.admin /opt/iobroker/node_modules/iobroker.
dmin/admin/index_m.html index_m.html text/html
upload [1] admin.admin /opt/iobroker/node_modules/iobroker.
dmin/admin/index.html index.html text/html
upload [0] admin.admin /opt/iobroker/node_modules/iobroker.
dmin/admin/admin.png admin.png image/png
Update "system.adapter.admin.0"
./reinstall.sh: line 34: unexpected EOF while looking for m
tching `"'
./reinstall.sh: line 37: syntax error: unexpected end of fi
e
root@cubietruck:/opt/iobroker#
root@cubietruck:/opt/iobroker#
          1 Reply Last reply Reply Quote 0
          • paul53
            paul53 last edited by

            @blackangel15741:

            Am Ende steht was mit syntax error `
            Das Skript hat eigentlich nur 33 oder 34 (mit zusätzlichem LF) Zeilen. Lässt sich ioBroker jetzt starten ?

            1 Reply Last reply Reply Quote 0
            • B
              blackangel15741 last edited by

              Hat funktioniert. …Iobroker läuft wieder.

              Wie kann man dieses Theater eigentlich vermeiden? Scheint ja oft zu passieren, dass man nur node updaten will und dann läuft nichts mehr.

              Wie erkennt man das mit "dos" und was könnte ich falsch gemacht haben?

              Muss mich das mit dem syntax error beunruhigen?

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

                @blackangel15741:

                Hat funktioniert. …Iobroker läuft wieder. `
                Dann markiere bitte das Thema im Betreff des ersten Beitrags als [gelöst].
                @blackangel15741:

                Wie erkennt man das mit "dos" und was könnte ich falsch gemacht haben? `
                Das erkennt man an der Fehlermeldung mit dem ^M. Du hast an der Stelle nichts falsch gemacht; iobroker.sh wurde eine Zeit lang im falschen Format ausgeliefert.

                -bash: ./reinstall.sh: /bin/bash^M: bad interpreter

                @blackangel15741:

                Muss mich das mit dem syntax error beunruhigen? `
                Nein.

                1 Reply Last reply Reply Quote 0
                • B
                  blackangel15741 last edited by

                  Vielen Dank für die tolle und schnelle Hilfe.

                  LG

                  1 Reply Last reply Reply Quote 0
                  • B
                    blackangel15741 last edited by

                    Wo und wie kann ich das Thema auf gelöst setzen?

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

                      @blackangel15741:

                      Wo und wie kann ich das Thema auf gelöst setzen? `
                      In dem Du den ersten Beitrag (Dein Eröffnungposting) editierst und den Titel um ein vorangestelltes „[gelöst] “ ergänzt (aber bitte ohne die „“).

                      Gruß,

                      Eric

                      Von unterwegs getippert

                      1 Reply Last reply Reply Quote 0
                      • B
                        blackangel15741 last edited by

                        Ok, danke….dachte da gibt's ein Button o.ä.

                        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

                        857
                        Online

                        32.0k
                        Users

                        80.5k
                        Topics

                        1.3m
                        Posts

                        3
                        13
                        2336
                        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