Homebridge & Systemüberwachung mit ntfy und Telegram Push (systemd)

Einstein77 · 5. März 2018

Code

Mar  5 10:16:27 homebridge systemd[1]: instanzen-reporter.service: Main process exited, code=exited, status=203/EXEC
Mar  5 10:16:27 homebridge systemd[1]: instanzen-reporter.service: Unit entered failed state.
Mar  5 10:16:27 homebridge systemd[1]: instanzen-reporter.service: Failed with result 'exit-code'.
Mar  5 10:16:27 homebridge systemd[1]: instanzen-reporter.service: Service hold-off time over, scheduling restart.
Mar  5 10:16:27 homebridge systemd[1]: Stopped instanzen-reporter.
Mar  5 10:16:27 homebridge systemd[1]: instanzen-reporter.service: Start request repeated too quickly.
Mar  5 10:16:27 homebridge systemd[1]: Failed to start instanzen-reporter.
Mar  5 10:16:27 homebridge systemd[1]: instanzen-reporter.service: Unit entered failed state.
Mar  5 10:16:27 homebridge systemd[1]: instanzen-reporter.service: Failed with result 'exit-code'.
Mar  5 10:16:37 homebridge systemd[1]: Started instanzen-reporter.
Mar  5 10:16:37 homebridge systemd[22284]: instanzen-reporter.service: Failed at step EXEC spawning /usr/local/bin/instanzen-reporter.sh: Exec format error
Mar  5 10:16:37 homebridge systemd[1]: instanzen-reporter.service: Main process exited, code=exited, status=203/EXEC
Mar  5 10:16:37 homebridge systemd[1]: instanzen-reporter.service: Unit entered failed state.
Mar  5 10:16:38 homebridge systemd[1]: instanzen-reporter.service: Failed with result 'exit-code'.
Mar  5 10:16:38 homebridge systemd[1]: instanzen-reporter.service: Service hold-off time over, scheduling restart.
Mar  5 10:16:38 homebridge systemd[1]: Stopped instanzen-reporter.
Mar  5 10:16:38 homebridge systemd[1]: Started instanzen-reporter.
Mar  5 10:16:38 homebridge systemd[22291]: instanzen-reporter.service: Failed at step EXEC spawning /usr/local/bin/instanzen-reporter.sh: Exec format error
Mar  5 10:16:38 homebridge systemd[1]: instanzen-reporter.service: Main process exited, code=exited, status=203/EXEC
Mar  5 10:16:38 homebridge systemd[1]: instanzen-reporter.service: Unit entered failed state.
Mar  5 10:16:38 homebridge systemd[1]: instanzen-reporter.service: Failed with result 'exit-code'.
Mar  5 10:16:38 homebridge systemd[1]: instanzen-reporter.service: Service hold-off time over, scheduling restart.
Mar  5 10:16:38 homebridge systemd[1]: Stopped instanzen-reporter.
Mar  5 10:16:38 homebridge systemd[1]: Started instanzen-reporter.
Mar  5 10:16:38 homebridge systemd[22294]: instanzen-reporter.service: Failed at step EXEC spawning /usr/local/bin/instanzen-reporter.sh: Exec format error
Mar  5 10:16:38 homebridge systemd[1]: instanzen-reporter.service: Main process exited, code=exited, status=203/EXEC
Mar  5 10:16:38 homebridge systemd[1]: instanzen-reporter.service: Unit entered failed state.
Mar  5 10:16:38 homebridge systemd[1]: instanzen-reporter.service: Failed with result 'exit-code'.
Mar  5 10:16:38 homebridge systemd[1]: instanzen-reporter.service: Service hold-off time over, scheduling restart.
Mar  5 10:16:38 homebridge systemd[1]: Stopped instanzen-reporter.
Mar  5 10:16:38 homebridge systemd[1]: Started instanzen-reporter.
Mar  5 10:16:38 homebridge systemd[22297]: instanzen-reporter.service: Failed at step EXEC spawning /usr/local/bin/instanzen-reporter.sh: Exec format error
Mar  5 10:16:38 homebridge systemd[1]: instanzen-reporter.service: Main process exited, code=exited, status=203/EXEC
Mar  5 10:16:38 homebridge systemd[1]: instanzen-reporter.service: Unit entered failed state.
Mar  5 10:16:38 homebridge systemd[1]: instanzen-reporter.service: Failed with result 'exit-code'.
Mar  5 10:16:38 homebridge systemd[1]: instanzen-reporter.service: Service hold-off time over, scheduling restart.
Mar  5 10:16:38 homebridge systemd[1]: Stopped instanzen-reporter.
Mar  5 10:16:38 homebridge systemd[1]: Started instanzen-reporter.
Mar  5 10:16:38 homebridge systemd[22300]: instanzen-reporter.service: Failed at step EXEC spawning /usr/local/bin/instanzen-reporter.sh: Exec format error
Mar  5 10:16:38 homebridge systemd[1]: instanzen-reporter.service: Main process exited, code=exited, status=203/EXEC
Mar  5 10:16:38 homebridge systemd[1]: instanzen-reporter.service: Unit entered failed state.
Mar  5 10:16:38 homebridge systemd[1]: instanzen-reporter.service: Failed with result 'exit-code'.
Mar  5 10:16:39 homebridge systemd[1]: instanzen-reporter.service: Service hold-off time over, scheduling restart.
Mar  5 10:16:39 homebridge systemd[1]: Stopped instanzen-reporter.
Mar  5 10:16:39 homebridge systemd[1]: instanzen-reporter.service: Start request repeated too quickly.
Mar  5 10:16:39 homebridge systemd[1]: Failed to start instanzen-reporter.
Mar  5 10:16:39 homebridge systemd[1]: instanzen-reporter.service: Unit entered failed state.
Mar  5 10:16:39 homebridge systemd[1]: instanzen-reporter.service: Failed with result 'exit-code'.

Alles anzeigen

det · 5. März 2018

Zitat von Einstein77

Exec format error

es muss alles auf einer Zeile stehen und Rechte setzen

/usr/local/bin/instanzen-reporter.sh

Bash

#!/bin/bash 
journalctl --unit homebridge* -f --since "now" | grep --line-buffered "exited" | sudo -u pi xargs -L1 -I '#' ntfy -b telegram send 'Homebridge Instanz ausgefallen'

Einstein77 · 5. März 2018

Dank, hab ich geändert und rechte noch mal gesetzt..

jetzt kommt aber das..

Code

pi@homebridge:/usr/local/bin $ sudo systemctl status instanzen-reporter.service
? instanzen-reporter.service - instanzen-reporter
   Loaded: loaded (/etc/systemd/system/instanzen-reporter.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2018-03-05 10:16:39 CET; 16min ago
 Main PID: 22300 (code=exited, status=203/EXEC)

Mär 05 10:16:38 homebridge systemd[1]: instanzen-reporter.service: Failed with result 'exit-code'.
Mär 05 10:16:39 homebridge systemd[1]: instanzen-reporter.service: Service hold-off time over, scheduling restart.
Mär 05 10:16:39 homebridge systemd[1]: Stopped instanzen-reporter.
Mär 05 10:16:39 homebridge systemd[1]: instanzen-reporter.service: Start request repeated too quickly.
Mär 05 10:16:39 homebridge systemd[1]: Failed to start instanzen-reporter.
Mär 05 10:16:39 homebridge systemd[1]: instanzen-reporter.service: Unit entered failed state.
Mär 05 10:16:39 homebridge systemd[1]: instanzen-reporter.service: Failed with result 'exit-code'.
pi@homebridge:/usr/local/bin $

Alles anzeigen

Einstein77 · 5. März 2018

Zitat von Nastra
Der Service ist auch nicht aktiviert.

Habe gesehen das ich den Schritt in der Anleitung vergessen habe. Korrigiere ich jetzt gleich.

det hat es ja schon geschrieben:
Code
sudo systemctl restart instanzen-reporter.service
danach nochmal den status posten vom Service.
Alles anzeigen

Code

pi@homebridge:/usr/local/bin $ sudo systemctl daemon-reload
pi@homebridge:/usr/local/bin $ sudo systemctl enable instanzen-reporter.service
pi@homebridge:/usr/local/bin $ sudo systemctl restart instanzen-reporter.service
pi@homebridge:/usr/local/bin $

bekomme da leider keine Ausgabe

det · 5. März 2018

Zitat von Einstein77

bekomme da leider keine Ausgabe

das ist gut so.

Zitat von Einstein77

Mär 05 10:16:38 homebridge systemd[1]: instanzen-reporter.service: Failed with result 'exit-code'.
Mär 05 10:16:39 homebridge systemd[1]: instanzen-reporter.service: Service hold-off time over, scheduling restart.
Mär 05 10:16:39 homebridge systemd[1]: Stopped instanzen-reporter.
Mär 05 10:16:39 homebridge systemd[1]: instanzen-reporter.service: Start request repeated too quickly.
Mär 05 10:16:39 homebridge systemd[1]: Failed to start instanzen-reporter.
Mär 05 10:16:39 homebridge systemd[1]: instanzen-reporter.service: Unit entered failed state.
Mär 05 10:16:39 homebridge systemd[1]: instanzen-reporter.service: Failed with result 'exit-code'.

Alles anzeigen

ist das alles was im log kommt?

Einstein77 · 5. März 2018

Code

Mar  5 11:50:20 homebridge systemd[1]: Started Session c2 of user pi.
Mar  5 11:50:40 homebridge systemd[1]: Started instanzen-reporter.
Mar  5 11:50:40 homebridge systemd[1694]: instanzen-reporter.service: Failed at step EXEC spawning /usr/local/bin/instanzen-reporter.sh: Exec format error
Mar  5 11:50:40 homebridge systemd[1]: instanzen-reporter.service: Main process exited, code=exited, status=203/EXEC
Mar  5 11:50:40 homebridge systemd[1]: instanzen-reporter.service: Unit entered failed state.
Mar  5 11:50:40 homebridge systemd[1]: instanzen-reporter.service: Failed with result 'exit-code'.
Mar  5 11:50:40 homebridge systemd[1]: instanzen-reporter.service: Service hold-off time over, scheduling restart.
Mar  5 11:50:40 homebridge systemd[1]: Stopped instanzen-reporter.
Mar  5 11:50:40 homebridge systemd[1]: Started instanzen-reporter.
Mar  5 11:50:40 homebridge systemd[1702]: instanzen-reporter.service: Failed at step EXEC spawning /usr/local/bin/instanzen-reporter.sh: Exec format error
Mar  5 11:50:40 homebridge systemd[1]: instanzen-reporter.service: Main process exited, code=exited, status=203/EXEC
Mar  5 11:50:40 homebridge systemd[1]: instanzen-reporter.service: Unit entered failed state.
Mar  5 11:50:40 homebridge systemd[1]: instanzen-reporter.service: Failed with result 'exit-code'.
Mar  5 11:50:41 homebridge systemd[1]: instanzen-reporter.service: Service hold-off time over, scheduling restart.
Mar  5 11:50:41 homebridge systemd[1]: Stopped instanzen-reporter.
Mar  5 11:50:41 homebridge systemd[1]: Started instanzen-reporter.
Mar  5 11:50:41 homebridge systemd[1706]: instanzen-reporter.service: Failed at step EXEC spawning /usr/local/bin/instanzen-reporter.sh: Exec format error
Mar  5 11:50:41 homebridge systemd[1]: instanzen-reporter.service: Main process exited, code=exited, status=203/EXEC
Mar  5 11:50:41 homebridge systemd[1]: instanzen-reporter.service: Unit entered failed state.
Mar  5 11:50:41 homebridge systemd[1]: instanzen-reporter.service: Failed with result 'exit-code'.
Mar  5 11:50:41 homebridge systemd[1]: instanzen-reporter.service: Service hold-off time over, scheduling restart.
Mar  5 11:50:41 homebridge systemd[1]: Stopped instanzen-reporter.
Mar  5 11:50:41 homebridge systemd[1]: Started instanzen-reporter.
Mar  5 11:50:41 homebridge systemd[1710]: instanzen-reporter.service: Failed at step EXEC spawning /usr/local/bin/instanzen-reporter.sh: Exec format error
Mar  5 11:50:41 homebridge systemd[1]: instanzen-reporter.service: Main process exited, code=exited, status=203/EXEC
Mar  5 11:50:41 homebridge systemd[1]: instanzen-reporter.service: Unit entered failed state.
Mar  5 11:50:41 homebridge systemd[1]: instanzen-reporter.service: Failed with result 'exit-code'.
Mar  5 11:50:41 homebridge systemd[1]: instanzen-reporter.service: Service hold-off time over, scheduling restart.
Mar  5 11:50:41 homebridge systemd[1]: Stopped instanzen-reporter.
Mar  5 11:50:41 homebridge systemd[1]: Started instanzen-reporter.
Mar  5 11:50:41 homebridge systemd[1713]: instanzen-reporter.service: Failed at step EXEC spawning /usr/local/bin/instanzen-reporter.sh: Exec format error
Mar  5 11:50:41 homebridge systemd[1]: instanzen-reporter.service: Main process exited, code=exited, status=203/EXEC
Mar  5 11:50:41 homebridge systemd[1]: instanzen-reporter.service: Unit entered failed state.
Mar  5 11:50:41 homebridge systemd[1]: instanzen-reporter.service: Failed with result 'exit-code'.
Mar  5 11:50:41 homebridge systemd[1]: instanzen-reporter.service: Service hold-off time over, scheduling restart.
Mar  5 11:50:41 homebridge systemd[1]: Stopped instanzen-reporter.
Mar  5 11:50:41 homebridge systemd[1]: instanzen-reporter.service: Start request repeated too quickly.
Mar  5 11:50:41 homebridge systemd[1]: Failed to start instanzen-reporter.
Mar  5 11:50:41 homebridge systemd[1]: instanzen-reporter.service: Unit entered failed state.
Mar  5 11:50:41 homebridge systemd[1]: instanzen-reporter.service: Failed with result 'exit-code'.

Alles anzeigen

Das bekomme ich..

det · 5. März 2018

Zitat von Einstein77

/usr/local/bin/instanzen-reporter.sh

lässt sich diese manuell starten?

det · 5. März 2018

Bash

#!/bin/bash

steht dieses wirklich am anfang von /usr/local/bin/instanzen-reporter.sh (mit einem Linux Editor)

Einstein77 · 5. März 2018

Vielen Dank, an alle die mir geholfen haben..

Ich habe den Fehler gefunden.. Schuld ist Copy&Paste was ich bei dieser Anleitung benutzt habe..

der Anleitung ist das Wort Insanzen 1x mit einem großen I geschrieben worden.

aber jetzt läuft es..

Gruß Marco

Nastra · 5. März 2018

Das ist wohl mein Fehler gewesen im Eifer des Gefechts, da konnte er das Skript nicht finden das erklärt auch den Fehler , änder ich direkt ab. Aber schön das es jetzt geht

det · 5. März 2018

Hauptsache es läuft nun

Dennis_BE · 5. März 2018

Ich bekomme es einfach nicht zum Laufen. Habe alles nochmal nach Anleitung überprüft. Es steht auch alles in einer Reihe.

Steckt der Wurm drin.

Hier der Code wenn ich manuell starten will

Code

pi@raspberrypi:~ $ /usr/local/bin/instanzen-reporter.sh
/bin/bash: journalctl --unit homebridge* -f --since "now" | grep --line-buffered "exited" | sudo -u pi xargs -L1 -I '#' ntfy -: Datei oder Verzeichnis nicht gefunden

Code

pi@raspberrypi:~ $ sudo systemctl status instanzen-reporter.service
? instanzen-reporter.service - instanzen-reporter
   Loaded: loaded (/etc/systemd/system/instanzen-reporter.service; enabled; vendo
   Active: failed (Result: exit-code) since Mon 2018-03-05 20:10:34 CET; 26s ago
  Process: 1306 ExecStart=/usr/local/bin/instanzen-reporter.sh (code=exited, stat
 Main PID: 1306 (code=exited, status=127)

Mär 05 20:10:34 raspberrypi systemd[1]: instanzen-reporter.service: Unit entered 
Mär 05 20:10:34 raspberrypi systemd[1]: instanzen-reporter.service: Failed with r
Mär 05 20:10:34 raspberrypi systemd[1]: instanzen-reporter.service: Service hold-
Mär 05 20:10:34 raspberrypi systemd[1]: Stopped instanzen-reporter.
Mär 05 20:10:34 raspberrypi systemd[1]: instanzen-reporter.service: Start request
Mär 05 20:10:34 raspberrypi systemd[1]: Failed to start instanzen-reporter.
Mär 05 20:10:34 raspberrypi systemd[1]: instanzen-reporter.service: Unit entered 
Mär 05 20:10:34 raspberrypi systemd[1]: instanzen-reporter.service: Failed with r
lines 1-14/14 (END)

Alles anzeigen

Hier miene Log:

Welche Datei fehlt den da?

Code

pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
Mar  5 20:10:34 raspberrypi systemd[1]: instanzen-reporter.service: Unit entered failed state.
Mar  5 20:10:34 raspberrypi systemd[1]: instanzen-reporter.service: Failed with result 'exit-code'.
Mar  5 20:10:34 raspberrypi systemd[1]: instanzen-reporter.service: Service hold-off time over, scheduling restart.
Mar  5 20:10:34 raspberrypi systemd[1]: Stopped instanzen-reporter.
Mar  5 20:10:34 raspberrypi systemd[1]: instanzen-reporter.service: Start request repeated too quickly.
Mar  5 20:10:34 raspberrypi systemd[1]: Failed to start instanzen-reporter.
Mar  5 20:10:34 raspberrypi systemd[1]: instanzen-reporter.service: Unit entered failed state.
Mar  5 20:10:34 raspberrypi systemd[1]: instanzen-reporter.service: Failed with result 'exit-code'.
Mar  5 20:12:30 raspberrypi systemd[1]: Starting Cleanup of Temporary Directories...
Mar  5 20:12:30 raspberrypi systemd[1]: Started Cleanup of Temporary Directories.
Mar  5 20:12:49 raspberrypi systemd[1]: Started instanzen-reporter.
Mar  5 20:12:49 raspberrypi instanzen-reporter.service[1334]: /bin/bash: journalctl --unit homebridge* -f --since "now" | grep --line-buffered "exited" | sudo -u pi xargs -L1 -I '#' ntfy -: Datei oder Verzeichnis nicht gefunden
Mar  5 20:12:49 raspberrypi systemd[1]: instanzen-reporter.service: Main process exited, code=exited, status=127/n/a
Mar  5 20:12:49 raspberrypi systemd[1]: instanzen-reporter.service: Unit entered failed state.
Mar  5 20:12:49 raspberrypi systemd[1]: instanzen-reporter.service: Failed with result 'exit-code'.
Mar  5 20:12:49 raspberrypi systemd[1]: instanzen-reporter.service: Service hold-off time over, scheduling restart.
Mar  5 20:12:49 raspberrypi systemd[1]: Stopped instanzen-reporter.
Mar  5 20:12:49 raspberrypi systemd[1]: Started instanzen-reporter.
Mar  5 20:12:49 raspberrypi instanzen-reporter.service[1339]: /bin/bash: journalctl --unit homebridge* -f --since "now" | grep --line-buffered "exited" | sudo -u pi xargs -L1 -I '#' ntfy -: Datei oder Verzeichnis nicht gefunden
Mar  5 20:12:49 raspberrypi systemd[1]: instanzen-reporter.service: Main process exited, code=exited, status=127/n/a
Mar  5 20:12:49 raspberrypi systemd[1]: instanzen-reporter.service: Unit entered failed state.
Mar  5 20:12:49 raspberrypi systemd[1]: instanzen-reporter.service: Failed with result 'exit-code'.
Mar  5 20:12:49 raspberrypi systemd[1]: instanzen-reporter.service: Service hold-off time over, scheduling restart.
Mar  5 20:12:49 raspberrypi systemd[1]: Stopped instanzen-reporter.
Mar  5 20:12:49 raspberrypi systemd[1]: Started instanzen-reporter.
Mar  5 20:12:49 raspberrypi instanzen-reporter.service[1341]: /bin/bash: journalctl --unit homebridge* -f --since "now" | grep --line-buffered "exited" | sudo -u pi xargs -L1 -I '#' ntfy -: Datei oder Verzeichnis nicht gefunden
Mar  5 20:12:49 raspberrypi systemd[1]: instanzen-reporter.service: Main process exited, code=exited, status=127/n/a
Mar  5 20:12:49 raspberrypi systemd[1]: instanzen-reporter.service: Unit entered failed state.
Mar  5 20:12:49 raspberrypi systemd[1]: instanzen-reporter.service: Failed with result 'exit-code'.
Mar  5 20:12:49 raspberrypi systemd[1]: instanzen-reporter.service: Service hold-off time over, scheduling restart.
Mar  5 20:12:49 raspberrypi systemd[1]: Stopped instanzen-reporter.
Mar  5 20:12:49 raspberrypi systemd[1]: Started instanzen-reporter.
Mar  5 20:12:49 raspberrypi instanzen-reporter.service[1343]: /bin/bash: journalctl --unit homebridge* -f --since "now" | grep --line-buffered "exited" | sudo -u pi xargs -L1 -I '#' ntfy -: Datei oder Verzeichnis nicht gefunden
Mar  5 20:12:49 raspberrypi systemd[1]: instanzen-reporter.service: Main process exited, code=exited, status=127/n/a
Mar  5 20:12:49 raspberrypi systemd[1]: instanzen-reporter.service: Unit entered failed state.
Mar  5 20:12:49 raspberrypi systemd[1]: instanzen-reporter.service: Failed with result 'exit-code'.
Mar  5 20:12:50 raspberrypi systemd[1]: instanzen-reporter.service: Service hold-off time over, scheduling restart.
Mar  5 20:12:50 raspberrypi systemd[1]: Stopped instanzen-reporter.
Mar  5 20:12:50 raspberrypi systemd[1]: Started instanzen-reporter.
Mar  5 20:12:50 raspberrypi instanzen-reporter.service[1345]: /bin/bash: journalctl --unit homebridge* -f --since "now" | grep --line-buffered "exited" | sudo -u pi xargs -L1 -I '#' ntfy -: Datei oder Verzeichnis nicht gefunden
Mar  5 20:12:50 raspberrypi systemd[1]: instanzen-reporter.service: Main process exited, code=exited, status=127/n/a
Mar  5 20:12:50 raspberrypi systemd[1]: instanzen-reporter.service: Unit entered failed state.
Mar  5 20:12:50 raspberrypi systemd[1]: instanzen-reporter.service: Failed with result 'exit-code'.
Mar  5 20:12:50 raspberrypi systemd[1]: instanzen-reporter.service: Service hold-off time over, scheduling restart.
Mar  5 20:12:50 raspberrypi systemd[1]: Stopped instanzen-reporter.
Mar  5 20:12:50 raspberrypi systemd[1]: instanzen-reporter.service: Start request repeated too quickly.
Mar  5 20:12:50 raspberrypi systemd[1]: Failed to start instanzen-reporter.
Mar  5 20:12:50 raspberrypi systemd[1]: instanzen-reporter.service: Unit entered failed state.
Mar  5 20:12:50 raspberrypi systemd[1]: instanzen-reporter.service: Failed with result 'exit-code'.

Alles anzeigen

Nastra · 5. März 2018

Wenn du das Skript angelegt hast fehlen dir entweder die Schreibrecht das der Service nicht drauf zugreiffen kann oder es ist ein Fehler im bzw. am Skript. Eventuell hast du den Namen auch groß geschrieben wie oben Einstein77 ?

Mach mal

cd /usr/local/bin/

dann

ls

und poste mal das Ergebnis.

Dennis_BE · 5. März 2018

Wie kann ich den die Datei mit dem großen I Löschen?

Habe das auch mit dem kleinen I gemacht.

Zitat von Nastra

Mach mal

cd /usr/local/bin/

dann

ls

Versteh ich jetzt nicht.

Nastra · 5. März 2018

cd /usr/local/bin/ = Verzeichnis betreten.

ls = Inhalt anzeigen.

Dennis_BE · 5. März 2018

Zitat von Nastra

cd /usr/local/bin/ = Verzeichnis betreten.

ls = Inhalt anzeigen.

Code

pi@raspberrypi:/usr/local/bin $ ls
dc_eventlog  forever  futurize  homebridge  homebridge-config-ui-x  instanzen-reporter.sh  json  n  node  npm  npx  ntfy  pasteurize  ph  telegram-send  upnp

Nastra · 5. März 2018

Ok, datei ist da.

Jetzt mal öffnen im Verzeichnis mit

sudo nano instanzen-reporter.sh

und posten.

Dennis_BE · 5. März 2018

Bash

#!/bin/bash journalctl --unit homebridge* -f --since "now" | grep --line-buffered "exited" | sudo -u pi xargs -L1 -I '#' ntfy -b telegram send 'Homebridge Instanz ausgefallen'

det · 5. März 2018

Die Datei ist ein 2 zeiler

Nach #!/bin/bash enter drücken

journal......

Der Rest alles auf eine neue Zeile

Du hast alles auf einer Zeile, das ist falsch.

Nastra · 5. März 2018

Na dann kann ich mich ja jetzt hinlegen. det übernehmen Sie die Nachtschicht

Teilen