FHEM - Hausautomations-Systeme > Unterstützende Dienste

Neues Modul: Signalbot (Integration für den Signal Messenger) via signal-cli

<< < (100/120) > >>

Kohle77:
Hi,
ich bin da über noch etwas gestolpert.

--- Code: ---sudo ldconfig -v | grep libzkgroup.so
ldconfig: Pfad »/usr/lib/arm-linux-gnueabihf« mehrfach angegeben
ldconfig: Pfad »/lib/arm-linux-gnueabihf« mehrfach angegeben
ldconfig: Pfad »/usr/lib/arm-linux-gnueabihf« mehrfach angegeben
ldconfig: Pfad »/usr/lib« mehrfach angegeben
ldconfig: /lib/arm-linux-gnueabihf/ld-2.28.so is the dynamic linker, ignoring

ldconfig: /lib/ld-linux.so.3 is the dynamic linker, ignoring

--- Ende Code ---

und

--- Code: ---sudo ldconfig -v | grep libsignal_jni.so
ldconfig: Pfad »/usr/lib/arm-linux-gnueabihf« mehrfach angegeben
ldconfig: Pfad »/lib/arm-linux-gnueabihf« mehrfach angegeben
ldconfig: Pfad »/usr/lib/arm-linux-gnueabihf« mehrfach angegeben
ldconfig: Pfad »/usr/lib« mehrfach angegeben
ldconfig: /lib/arm-linux-gnueabihf/ld-2.28.so is the dynamic linker, ignoring

ldconfig: /lib/ld-linux.so.3 is the dynamic linker, ignoring

--- Ende Code ---
Ist das normal oder meinst du dieses Ergebnis mit dem im wicki beschriebenen "Da die libraries in .jar files eingebettet sind, darf hier keine gefunden werden."

Gruß
Christian

Adimarantis:
Was du beim ldconfig siehst ist wahrscheinlich normal - das ist stderr output welches vom grep nicht weggefiltert wird. Die libs die wir brauchen findet er nicht - das passt.

Allerdings ist bei dir noch irgendwas mit den libs/jars nicht in Ordnung.
Um alles sauber zu kriegen - lösch mal komplett /opt/signal und dann nochmal signal_install.sh ausführen.

Jörg

Edit: Obwohl, das Script das eigentlich sowieso schon macht....

Kohle77:
Hallo,
also mal geschaut was ich in /opt finde und die beiden removed:


--- Code: ---/opt $ ls
fhem  fhem2  gradle-7.2  signal  signal-cli_source  vc  zkgroup-0.7.4
/opt $ sudo rm -r signal
/opt $ sudo rm -r signal-cli_source

--- Ende Code ---

Das Ergebniss ist:

--- Code: ---signal.service - Send secure messages to Signal clients
   Loaded: loaded (/etc/systemd/system/signal.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2021-12-08 07:30:57 CET; 33s ago
  Process: 2881 ExecStart=/opt/signal/bin/signal-cli --config /var/lib/signal-cli daemon --system (code=exited, status=1/FAILURE)
 Main PID: 2881 (code=exited, status=1/FAILURE)

--- Ende Code ---

Mit systemctl status signal.service bekomme ich das:

--- Code: ---Dez 08 07:30:46 FHEM systemd[1]: Starting Send secure messages to Signal clients...
Dez 08 07:30:56 FHEM signal-cli[2881]: OpenJDK Server VM warning: You have loaded library /tmp/resource14856610907052668369.so which might have disabled stack guard. The VM will try to fix the stack guard now.
Dez 08 07:30:56 FHEM signal-cli[2881]: It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'.
Dez 08 07:30:56 FHEM signal-cli[2881]: WARN ServiceConfig - Failed to call libzkgroup: /tmp/resource14856610907052668369.so: /tmp/resource14856610907052668369.so: falsche ELF-Klasse: ELFCLASS64 (Possible cause: architecture word widt
Dez 08 07:30:56 FHEM signal-cli[2881]: WARN App - WARNING: Support for new group V2 is disabled, because the required native library dependency is missing: libzkgroup
Dez 08 07:30:57 FHEM signal-cli[2881]: WARN ServiceConfig - Failed to call libsignal-client: /tmp/resource4834344169808386157.so: /tmp/resource4834344169808386157.so: falsche ELF-Klasse: ELFCLASS64 (Possible cause: architecture word
Dez 08 07:30:57 FHEM signal-cli[2881]: Missing required native library dependency: libsignal-client
Dez 08 07:30:57 FHEM systemd[1]: signal.service: Main process exited, code=exited, status=1/FAILURE
Dez 08 07:30:57 FHEM systemd[1]: signal.service: Failed with result 'exit-code'.
Dez 08 07:30:57 FHEM systemd[1]: Failed to start Send secure messages to Signal clients.

--- Ende Code ---

Das journalctl -xe liefert dies:

--- Code: --- journalctl -xe
-- The job identifier is 3611.
Dez 08 07:30:32 FHEM signal-cli[2818]: OpenJDK Server VM warning: You have loaded library /tmp/resource15504035341442631258.so which might have disabled stack guard. The VM will try to fix the stack guard now.
Dez 08 07:30:32 FHEM signal-cli[2818]: It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'.
Dez 08 07:30:32 FHEM signal-cli[2818]: WARN ServiceConfig - Failed to call libzkgroup: /tmp/resource15504035341442631258.so: /tmp/resource15504035341442631258.so: falsche ELF-Klasse: ELFCLASS64 (Possible cause: architecture word widt
Dez 08 07:30:33 FHEM signal-cli[2818]: WARN App - WARNING: Support for new group V2 is disabled, because the required native library dependency is missing: libzkgroup
Dez 08 07:30:34 FHEM signal-cli[2818]: WARN ServiceConfig - Failed to call libsignal-client: /tmp/resource13299115370021254553.so: /tmp/resource13299115370021254553.so: falsche ELF-Klasse: ELFCLASS64 (Possible cause: architecture wor
Dez 08 07:30:34 FHEM signal-cli[2818]: Missing required native library dependency: libsignal-client
Dez 08 07:30:35 FHEM systemd[1]: signal.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit signal.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
Dez 08 07:30:35 FHEM systemd[1]: signal.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit signal.service has entered the 'failed' state with result 'exit-code'.
Dez 08 07:30:35 FHEM systemd[1]: Failed to start Send secure messages to Signal clients.
-- Subject: A start job for unit signal.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit signal.service has finished with a failure.
--
-- The job identifier is 3611 and the job result is failed.
Dez 08 07:30:39 FHEM kernel: Voltage normalised (0x00000000)
Dez 08 07:30:46 FHEM dbus-daemon[362]: [system] Failed to activate service 'org.asamk.Signal': timed out (service_start_timeout=25000ms)
Dez 08 07:30:46 FHEM dbus-daemon[362]: [system] Activating via systemd: service name='org.asamk.Signal' unit='dbus-org.asamk.Signal.service' requested by ':1.81' (uid=0 pid=2880 comm="perl /tmp/signal2607.tmp ")
Dez 08 07:30:46 FHEM systemd[1]: Starting Send secure messages to Signal clients...
-- Subject: A start job for unit signal.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit signal.service has begun execution.
--
-- The job identifier is 3677.
Dez 08 07:30:56 FHEM signal-cli[2881]: OpenJDK Server VM warning: You have loaded library /tmp/resource14856610907052668369.so which might have disabled stack guard. The VM will try to fix the stack guard now.
Dez 08 07:30:56 FHEM signal-cli[2881]: It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'.
Dez 08 07:30:56 FHEM signal-cli[2881]: WARN ServiceConfig - Failed to call libzkgroup: /tmp/resource14856610907052668369.so: /tmp/resource14856610907052668369.so: falsche ELF-Klasse: ELFCLASS64 (Possible cause: architecture word widt
Dez 08 07:30:56 FHEM signal-cli[2881]: WARN App - WARNING: Support for new group V2 is disabled, because the required native library dependency is missing: libzkgroup
Dez 08 07:30:57 FHEM signal-cli[2881]: WARN ServiceConfig - Failed to call libsignal-client: /tmp/resource4834344169808386157.so: /tmp/resource4834344169808386157.so: falsche ELF-Klasse: ELFCLASS64 (Possible cause: architecture word
Dez 08 07:30:57 FHEM signal-cli[2881]: Missing required native library dependency: libsignal-client
Dez 08 07:30:57 FHEM systemd[1]: signal.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit signal.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
Dez 08 07:30:57 FHEM systemd[1]: signal.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit signal.service has entered the 'failed' state with result 'exit-code'.
Dez 08 07:30:57 FHEM systemd[1]: Failed to start Send secure messages to Signal clients.
-- Subject: A start job for unit signal.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit signal.service has finished with a failure.
--
-- The job identifier is 3677 and the job result is failed.
Dez 08 07:31:11 FHEM dbus-daemon[362]: [system] Failed to activate service 'org.asamk.Signal': timed out (service_start_timeout=25000ms)
Dez 08 07:31:11 FHEM sudo[2605]: pam_unix(sudo:session): session closed for user root


--- Ende Code ---

Gruß
Christian

Adimarantis:
Hi Christian,

Ich denke ich hab das Problem gefunden: Der Installer hatte einen Fehler und hat ausgerechnet für die Kombination arm 0.9.0 die libs gar nicht upgedated (was so ein "," ausmachen kann). Sorry for that. (Wäre daran zu sehen gewesen das er sich über "unsupported combination" mockiert hat)
Hol dir vom svn oder per "reinit" bitte das neuste signal_install.sh, passe es wieder für 0.9.0 an, und dann sollte es hoffentlich klappen.

Für 0.9.2 habe ich eine Idee - muss ich erst probieren. Die libs werden mit experimentellen Rust compiler Versionen übersetzt und ich erinnere mich, dass es da Probleme für ARM gab, als ich die entsprechend libs gebaut hab. Ich musste die Compiler Version ändern, damit es überhaupt ging. Evtl. war trotzdem noch ein Wurm drin. Ich hab die jetzt mal neu (neuerer Compiler) übersetzt und probiere ob das so läuft, wenn das bei mir stabil läuft, aktualisiere ich es und du kannst die 0.9.2 nochmal probieren.

Fürs erste aber hoffe ich die 0.9.0 läuft bei dir jetzt.

Jörg

Kohle77:
Hi,
erstmal danke für die Hilfe.
Ich bekomme einen Fehler das der Signal Service nicht gestartet werden kann während der installation.


--- Code: ---Checking for /usr/lib...found
Checking for /etc/dbus-1...found
Checking for /etc/dbus-1/system.d...found
Checking for /usr/share/dbus-1...found
Checking for /usr/share/dbus-1/system-services...found
Checking for /etc/systemd/system...found
Checking for /run/dbus...found
Checking for apt-ftparchive...available
Checking for wget...available
Checking for sudo...available
Checking for haveged...available
Checking for java...available
Checking for diff...available
Checking for dbus-send...available
Checking for cpan...available
Checking for zip...available
Checking for /usr/include/dbus-1.0/dbus/dbus.h...available
Checking for /usr/share/build-essential/essential-packages-list...available
Checking for /usr/share/doc/libimage-librsvg-perl...available
Checking for /usr/share/perl5/URI.pm...available
Checking for Protocol::DBus...V0.19 found
Checking user signal-cli ...found
Checking for /opt...found
Checking for /var/lib/signal-cli...created
Checking for existing signal-cli installation...not found
Proceed with signal cli installation
Stopping signal-cli service
Downloading signal-cli 0.9.0...done
Unpacking ...
Downloading native libraries...done
Updating native libs for armhf-glibc2.28-0.9.0
updating: libzkgroup.so (deflated 72%)
updating: libsignal_jni.so (deflated 73%)
done
Checking for /etc/dbus-1/system.d/org.asamk.Signal.conf.../etc/dbus-1/system.d/org.asamk.Signal.conf installed
Checking for /usr/share/dbus-1/system-services/org.asamk.Signal.service.../usr/share/dbus-1/system-services/org.asamk.Signal.service installed
Checking for /etc/systemd/system/signal.service.../etc/systemd/system/signal.service installed
Created symlink /etc/systemd/system/dbus-org.asamk.Signal.service ? /etc/systemd/system/signal.service.
Created symlink /etc/systemd/system/multi-user.target.wants/signal.service ? /etc/systemd/system/signal.service.
Start signal-cli service
Job for signal.service failed because a timeout was exceeded.
See "systemctl status signal.service" and "journalctl -xe" for details.
Checking installation via dbus-send command...Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
unexpected reply

Sending a message via perl Protocol::DBus...reply received

--- Ende Code ---

Checked ich die beiden services scheint org.asamk.Signal.service nicht zu laufen

--- Code: ---pi@FHEM:~ $ sudo systemctl status org.asamk.Signal.service
Unit org.asamk.Signal.service could not be found.

--- Ende Code ---

aber der Signal Service läuft:

--- Code: ---pi@FHEM:~ $ sudo systemctl status signal.service
? signal.service - Send secure messages to Signal clients
   Loaded: loaded (/etc/systemd/system/signal.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2021-12-08 10:26:59 CET; 2min 12s ago
 Main PID: 1846 (java)
    Tasks: 16 (limit: 2059)
   CGroup: /system.slice/signal.service
           +-1846 java -Xms2m -classpath /opt/signal/lib/signal-cli-0.9.0.jar:/opt/signal/lib/lib.jar:/opt/signal/lib/bcprov-jdk15on-1.69.jar:/opt/signal/lib/argparse4j-0.9.0.jar:/opt/signal/lib/dbus-java-3.3.0.jar:/opt/signal/lib/slf4j-

Dez 08 10:26:17 FHEM systemd[1]: Starting Send secure messages to Signal clients...
Dez 08 10:26:59 FHEM systemd[1]: Started Send secure messages to Signal clients.

--- Ende Code ---

hab mal noch einen shutdown -h now , power removed und wieder angestöpselt, jetzt scheint es zu laufen.

Danke
Christian

Navigation

[0] Themen-Index

[#] Nächste Seite

[*] Vorherige Sete

Zur normalen Ansicht wechseln