Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Off Topic
    4. Proxmox
    5. Proxmox VM mit IOBroker OWServer

    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

    Proxmox VM mit IOBroker OWServer

    This topic has been deleted. Only users with topic management privileges can see it.
    • L
      Laser @crunchip last edited by

      @crunchip
      Das habe ich schon mindestens 10 Mal getan. Der OWServer läßt sich nicht mehr starten.
      Trotzdem mache ich das jetzt nochmal. Ist ja kein Aufwand.

      crunchip L 2 Replies Last reply Reply Quote 0
      • crunchip
        crunchip Forum Testing Most Active @Laser last edited by

        @laser sagte in Proxmox VM mit IOBroker OWServer:

        Das habe ich schon mindestens 10 Mal getan. Der OWServer läßt sich nicht mehr starten.

        der läuft doch während du iobroker installierst

        1 Reply Last reply Reply Quote 0
        • L
          Laser @Laser last edited by Laser

          Neu IOBroker installiert. Ohne Neustart:

          otto@debian11:~$ sudo systemctl status owserver
● owserver.service - Backend server for 1-wire control
     Loaded: loaded (/lib/systemd/system/owserver.service; enabled; vendor pres>
     Active: active (running) since Mon 2023-01-02 11:03:38 CET; 5min ago
TriggeredBy: ● owserver.socket
       Docs: man:owserver(1)
   Main PID: 372 (owserver)
      Tasks: 4 (limit: 4618)
     Memory: 1.4M
        CPU: 108ms
     CGroup: /system.slice/owserver.service
             └─372 /usr/bin/owserver --foreground -c /etc/owfs.conf

Jan 02 11:03:38 debian11 systemd[1]: Starting Backend server for 1-wire control>
Jan 02 11:03:38 debian11 owserver[372]: DEFAULT: ow_opt.c:(780) systemd mode -->
Jan 02 11:03:38 debian11 owserver[372]: DEFAULT: ow_opt.c:(670) systemd mode -->
Jan 02 11:03:38 debian11 owserver[372]: DEFAULT: ow_usb_msg.c:(214) Opened USB >
Jan 02 11:03:38 debian11 owserver[372]: DEFAULT: ow_usb_cycle.c:(128) Set DS949>
Jan 02 11:03:38 debian11 systemd[1]: Started Backend server for 1-wire control.
lines 1-18/18 (END)
● owserver.service - Backend server for 1-wire control
     Loaded: loaded (/lib/systemd/system/owserver.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2023-01-02 11:03:38 CET; 5min ago
TriggeredBy: ● owserver.socket
       Docs: man:owserver(1)
   Main PID: 372 (owserver)
      Tasks: 4 (limit: 4618)
     Memory: 1.4M
        CPU: 108ms
     CGroup: /system.slice/owserver.service
             └─372 /usr/bin/owserver --foreground -c /etc/owfs.conf

Jan 02 11:03:38 debian11 systemd[1]: Starting Backend server for 1-wire control...
Jan 02 11:03:38 debian11 owserver[372]: DEFAULT: ow_opt.c:(780) systemd mode -- ignore foreground request
Jan 02 11:03:38 debian11 owserver[372]: DEFAULT: ow_opt.c:(670) systemd mode -- ignore 'p' option
Jan 02 11:03:38 debian11 owserver[372]: DEFAULT: ow_usb_msg.c:(214) Opened USB DS9490 bus master at 2:2.
Jan 02 11:03:38 debian11 owserver[372]: DEFAULT: ow_usb_cycle.c:(128) Set DS9490 2:2 unique id to 81 69 8E 35 >
Jan 02 11:03:38 debian11 systemd[1]: Started Backend server for 1-wire control.
~
~
~
~
~
lines 1-18/18 (END)
● owserver.service - Backend server for 1-wire control
     Loaded: loaded (/lib/systemd/system/owserver.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2023-01-02 11:03:38 CET; 5min ago
TriggeredBy: ● owserver.socket
       Docs: man:owserver(1)
   Main PID: 372 (owserver)
      Tasks: 4 (limit: 4618)
     Memory: 1.4M
        CPU: 108ms
     CGroup: /system.slice/owserver.service
             └─372 /usr/bin/owserver --foreground -c /etc/owfs.conf

Jan 02 11:03:38 debian11 systemd[1]: Starting Backend server for 1-wire control...
Jan 02 11:03:38 debian11 owserver[372]: DEFAULT: ow_opt.c:(780) systemd mode -- ignore foreground request
Jan 02 11:03:38 debian11 owserver[372]: DEFAULT: ow_opt.c:(670) systemd mode -- ignore 'p' option
Jan 02 11:03:38 debian11 owserver[372]: DEFAULT: ow_usb_msg.c:(214) Opened USB DS9490 bus master at 2:2.
Jan 02 11:03:38 debian11 owserver[372]: DEFAULT: ow_usb_cycle.c:(128) Set DS9490 2:2 unique id to 81 69 8E 35 00 00 00 5F
Jan 02 11:03:38 debian11 systemd[1]: Started Backend server for 1-wire control.
~
~
~
~
~
lines 1-18/18 (END)

          Nach Neustart VM:

          otto@debian11:~$ sudo systemctl status owserver
[sudo] Passwort für otto:
● owserver.service - Backend server for 1-wire control
     Loaded: loaded (/lib/systemd/system/owserver.service; enabled; vendor preset: enabled)
     Active: failed (Result: signal) since Mon 2023-01-02 11:10:49 CET; 7s ago
TriggeredBy: ● owserver.socket
       Docs: man:owserver(1)
    Process: 487 ExecStart=/usr/bin/owserver --foreground -c /etc/owfs.conf (code=killed, signal=SEGV)
   Main PID: 487 (code=killed, signal=SEGV)
        CPU: 24ms

Jan 02 11:10:49 debian11 systemd[1]: owserver.service: Main process exited, code=killed, status=11/SEGV
Jan 02 11:10:49 debian11 systemd[1]: owserver.service: Failed with result 'signal'.
Jan 02 11:10:49 debian11 systemd[1]: owserver.service: Scheduled restart job, restart counter is at 5.
Jan 02 11:10:49 debian11 systemd[1]: Stopped Backend server for 1-wire control.
Jan 02 11:10:49 debian11 systemd[1]: owserver.service: Start request repeated too quickly.
Jan 02 11:10:49 debian11 systemd[1]: owserver.service: Failed with result 'signal'.
Jan 02 11:10:49 debian11 systemd[1]: Failed to start Backend server for 1-wire control.

          Während der Installation war der OWServer noch zugänglich!

          L crunchip 2 Replies Last reply Reply Quote 0
          • L
            Laser @Laser last edited by

            Was mache ich falsch? Wo kann ich mit Suchen ansetzen?
            Die Lösung -eine VM mit OWServer und FHEM, die andere VM mit IOBroker ohne OWServer aber mit FHEM Adapter funktioniert zwar, ist aber wohl nicht im Sinne der Erfinder...

            1 Reply Last reply Reply Quote 0
            • crunchip
              crunchip Forum Testing Most Active @Laser last edited by

              @laser zeig mal den Inhalt von

              cat /lib/systemd/system/owserver.service

              cat /lib/systemd/system/owserver.socket

              cat /etc/owfs.conf
              L 1 Reply Last reply Reply Quote 0
              • L
                Laser @crunchip last edited by

                @crunchip

                cat /lib/systemd/system/owserver.service
[Unit]
Description=Backend server for 1-wire control
Documentation=man:owserver(1)

[Service]
Type=notify
NotifyAccess=all
ExecStart=/usr/bin/owserver --foreground -c /etc/owfs.conf
Restart=on-failure
#User=Debian-ow
#Group=Debian-ow

[Install]
WantedBy=multi-user.target
Also=owserver.socket

                cat /lib/systemd/system/owserver.service
                [Unit]
                Description=Backend server for 1-wire control
                Documentation=man:owserver(1)

                [Service]
                Type=notify
                NotifyAccess=all
                ExecStart=/usr/bin/owserver --foreground -c /etc/owfs.conf
                Restart=on-failure
                #User=Debian-ow
                #Group=Debian-ow

                [Install]
                WantedBy=multi-user.target
                Also=owserver.socket
                otto@debian11:~$ ^C
                otto@debian11:~$
                otto@debian11:~$
                otto@debian11:~$
                otto@debian11:~$
                otto@debian11:~$ cat /lib/systemd/system/owserver.socket
                [Unit]
                Description=Listening socket for owserver
                Documentation=man:owserver(1)

                [Socket]
                ListenStream=4304

                [Install]
                WantedBy=sockets.target

                #
#
# This is the main OWFS configuration file. You should read the
# owfs.conf(5) manual page in order to understand the options listed
# here.

######################## SOURCES ########################
#
# With this setup, any client (but owserver) uses owserver on the
# local machine...
! server: server = localhost:4304
#
# ...and owserver uses the real hardware, by default fake devices
# This part must be changed on real installation
#server: FAKE = DS18S20,DS2405
#
# USB device: DS9490
server: usb = all
#
# Serial port: DS9097
#server: device = /dev/ttyS1
#
# owserver tcp address
#server: server = 192.168.10.1:3131
#
# random simulated device
#server: FAKE = DS18S20,DS2405
#
######################### OWFS ##########################
#
#mountpoint = /mnt/1wire
#allow_other
#
####################### OWHTTPD #########################

http: port = 2121

####################### OWFTPD ##########################

ftp: port = 2120

####################### OWSERVER ########################

#server: port = localhost:4304
server: port = 192.168.2.112:4304
                crunchip 1 Reply Last reply Reply Quote 0
                • crunchip
                  crunchip Forum Testing Most Active @Laser last edited by crunchip

                  @laser sagte in Proxmox VM mit IOBroker OWServer:

                  --foreground

                  wenn du es mal ohne probierst, also das --foreground rauslöschen

                  sudo  /lib/systemd/system/owserver.service

                  und danach VM neu starten

                  L 1 Reply Last reply Reply Quote 0
                  • L
                    Laser @crunchip last edited by

                    @crunchip
                    die Zeile auskommentiert:

                    otto@debian11:~$ sudo systemctl status owserver
[sudo] Passwort für otto:
● owserver.service - Backend server for 1-wire control
     Loaded: bad-setting (Reason: Unit owserver.service has a bad unit file setting.)
     Active: inactive (dead)
TriggeredBy: ● owserver.socket
       Docs: man:owserver(1)
otto@debian11:~$ sudo systemctl status owserver
● owserver.service - Backend server for 1-wire control
     Loaded: bad-setting (Reason: Unit owserver.service has a bad unit file setting.)
     Active: inactive (dead)
TriggeredBy: ● owserver.socket
       Docs: man:owserver(1)
                    crunchip ? 2 Replies Last reply Reply Quote 0
                    • crunchip
                      crunchip Forum Testing Most Active @Laser last edited by

                      @laser sagte in Proxmox VM mit IOBroker OWServer:

                      die Zeile auskommentiert:

                      davon habe ich nichts geschrieben, du solltest die Option rauslöschen

                      anstatt

                      ExecStart=/usr/bin/owserver --foreground -c /etc/owfs.conf

                      sollte das dann drin stehen

                      ExecStart=/usr/bin/owserver -c /etc/owfs.conf
                      L 1 Reply Last reply Reply Quote 0
                      • ?
                        A Former User @Laser last edited by

                        @laser

                        nicht die Zeile auskommentieren, nur das --foreground löschen

                        # sudo systemctl stop owserver.service
# sudo systemctl edit owserver.service
# sudo systemctl daemon-reload
# sudo systemctl start owserver.service

                        @crunchip war schneller 🙂

                        1 Reply Last reply Reply Quote 0
                        • L
                          Laser @crunchip last edited by Laser

                          @crunchip
                          Das war ein Mißverständnis aber trotz Allem:

                          otto@debian11:~$ sudo systemctl status owserver
[sudo] Passwort für otto:
● owserver.service - Backend server for 1-wire control
     Loaded: loaded (/lib/systemd/system/owserver.service; enabled; vendor preset: enabled)
     Active: failed (Result: signal) since Mon 2023-01-02 13:26:39 CET; 15s ago
TriggeredBy: ● owserver.socket
       Docs: man:owserver(1)
    Process: 484 ExecStart=/usr/bin/owserver -c /etc/owfs.conf (code=killed, signal=SEGV)
   Main PID: 484 (code=killed, signal=SEGV)
        CPU: 24ms

Jan 02 13:26:38 debian11 systemd[1]: owserver.service: Main process exited, code=killed, status=11/SEGV
Jan 02 13:26:38 debian11 systemd[1]: owserver.service: Failed with result 'signal'.
Jan 02 13:26:39 debian11 systemd[1]: owserver.service: Scheduled restart job, restart counter is at 5.
Jan 02 13:26:39 debian11 systemd[1]: Stopped Backend server for 1-wire control.
Jan 02 13:26:39 debian11 systemd[1]: owserver.service: Start request repeated too quickly.
Jan 02 13:26:39 debian11 systemd[1]: owserver.service: Failed with result 'signal'.
Jan 02 13:26:39 debian11 systemd[1]: Failed to start Backend server for 1-wire control.
otto@debian11:~$ sudo systemctl status owserver
● owserver.service - Backend server for 1-wire control
     Loaded: loaded (/lib/systemd/system/owserver.service; enabled; vendor preset: enabled)
     Active: failed (Result: signal) since Mon 2023-01-02 13:26:39 CET; 18s ago
TriggeredBy: ● owserver.socket
       Docs: man:owserver(1)
    Process: 484 ExecStart=/usr/bin/owserver -c /etc/owfs.conf (code=killed, signal=SEGV)
   Main PID: 484 (code=killed, signal=SEGV)
        CPU: 24ms

Jan 02 13:26:38 debian11 systemd[1]: owserver.service: Main process exited, code=killed, status=11/SEGV
Jan 02 13:26:38 debian11 systemd[1]: owserver.service: Failed with result 'signal'.
Jan 02 13:26:39 debian11 systemd[1]: owserver.service: Scheduled restart job, restart counter is at 5.
Jan 02 13:26:39 debian11 systemd[1]: Stopped Backend server for 1-wire control.
Jan 02 13:26:39 debian11 systemd[1]: owserver.service: Start request repeated too quickly.
Jan 02 13:26:39 debian11 systemd[1]: owserver.service: Failed with result 'signal'.
Jan 02 13:26:39 debian11 systemd[1]: Failed to start Backend server for 1-wire control.


                          
otto@debian11:~$ sudo systemctl restart owserver
Job for owserver.service failed because the service did not take the steps required by its unit configuration.
See "systemctl status owserver.service" and "journalctl -xe" for details.
                          ? 1 Reply Last reply Reply Quote 0
                          • Homoran
                            Homoran Global Moderator Administrators last edited by

                            ist das hier ein ioBroker Thema??
                            oder offtopic?

                            L 1 Reply Last reply Reply Quote 0
                            • L
                              Laser @Homoran last edited by

                              @homoran
                              so eindeutig kann man das nicht festmachen. Fest steht, nach Installation des IOBroker funktioniert der OWServer nicht mehr.

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

                                @laser sagte in Proxmox VM mit IOBroker OWServer:

                                funktioniert der OWServer nicht mehr.

                                und der gehört zu ioBroker?

                                L 1 Reply Last reply Reply Quote 0
                                • L
                                  Laser @Homoran last edited by Laser

                                  @homoran
                                  Wo hättest Du das Thema gerne? Im Nirvana? IOBroker ohne Zusätze bringt keinen Nutzen.
                                  So wie es früher hieß "Windows ohne Software funktioniert einwandfrei"

                                  Homoran 1 Reply Last reply Reply Quote 0
                                  • ?
                                    A Former User @Laser last edited by

                                    @laser sagte in Proxmox VM mit IOBroker OWServer:

                                    Das war ein Mißverständnis aber trotz Allem:

                                    Hi,
                                    was gibt den journalctl aus? Am besten zweite Konsole aufmachen, wenn Du owserver.service startest

                                    # $ sudo journalctl -f

                                    Oder gibt es noch weitere Log-Files, Syslog oder Logs vom owserver?

                                    VG
                                    Bernd

                                    L 1 Reply Last reply Reply Quote 0
                                    • L
                                      Laser @Guest last edited by Laser

                                      @dp20eic
                                      Beim Start von OWSERVER:

                                      Jan 02 14:22:09 debian11 sudo[586]: pam_unix(sudo:session): session opened for user root(uid=0) by otto(uid=1000)
Jan 02 14:22:12 debian11 qemu-ga[352]: info: guest-ping called
Jan 02 14:22:23 debian11 qemu-ga[352]: info: guest-ping called
Jan 02 14:22:29 debian11 sudo[589]:     otto : TTY=pts/0 ; PWD=/home/otto ; USER=root ; COMMAND=/usr/bin/systemctl restart owserver
Jan 02 14:22:29 debian11 sudo[589]: pam_unix(sudo:session): session opened for user root(uid=0) by otto(uid=1000)
Jan 02 14:22:29 debian11 systemd[1]: Starting Backend server for 1-wire control...
Jan 02 14:22:29 debian11 systemd[1]: owserver.service: Failed with result 'protocol'.
Jan 02 14:22:29 debian11 systemd[1]: Failed to start Backend server for 1-wire control.
Jan 02 14:22:29 debian11 sudo[589]: pam_unix(sudo:session): session closed for user root
Jan 02 14:22:29 debian11 systemd[1]: owserver.service: Scheduled restart job, restart counter is at 1.
Jan 02 14:22:29 debian11 systemd[1]: Stopped Backend server for 1-wire control.
Jan 02 14:22:29 debian11 systemd[1]: Starting Backend server for 1-wire control...
Jan 02 14:22:29 debian11 systemd[1]: owserver.service: Failed with result 'protocol'.
Jan 02 14:22:29 debian11 systemd[1]: Failed to start Backend server for 1-wire control.
Jan 02 14:22:29 debian11 systemd[1]: owserver.service: Scheduled restart job, restart counter is at 2.
Jan 02 14:22:29 debian11 systemd[1]: Stopped Backend server for 1-wire control.
Jan 02 14:22:29 debian11 systemd[1]: Starting Backend server for 1-wire control...
Jan 02 14:22:29 debian11 systemd[1]: owserver.service: Failed with result 'protocol'.
Jan 02 14:22:29 debian11 systemd[1]: Failed to start Backend server for 1-wire control.
Jan 02 14:22:29 debian11 systemd[1]: owserver.service: Scheduled restart job, restart counter is at 3.
Jan 02 14:22:29 debian11 systemd[1]: Stopped Backend server for 1-wire control.
Jan 02 14:22:29 debian11 systemd[1]: Starting Backend server for 1-wire control...
Jan 02 14:22:29 debian11 systemd[1]: owserver.service: Failed with result 'protocol'.
Jan 02 14:22:29 debian11 systemd[1]: Failed to start Backend server for 1-wire control.
Jan 02 14:22:30 debian11 systemd[1]: owserver.service: Scheduled restart job, restart counter is at 4.
Jan 02 14:22:30 debian11 systemd[1]: Stopped Backend server for 1-wire control.
Jan 02 14:22:30 debian11 systemd[1]: Starting Backend server for 1-wire control...
Jan 02 14:22:30 debian11 systemd[1]: owserver.service: Failed with result 'protocol'.
Jan 02 14:22:30 debian11 systemd[1]: Failed to start Backend server for 1-wire control.
Jan 02 14:22:30 debian11 systemd[1]: owserver.service: Scheduled restart job, restart counter is at 5.
Jan 02 14:22:30 debian11 systemd[1]: Stopped Backend server for 1-wire control.
Jan 02 14:22:30 debian11 systemd[1]: owserver.service: Start request repeated too quickly.
Jan 02 14:22:30 debian11 systemd[1]: owserver.service: Failed with result 'protocol'.
Jan 02 14:22:30 debian11 systemd[1]: Failed to start Backend server for 1-wire control.
Jan 02 14:22:34 debian11 qemu-ga[352]: info: guest-ping called

                                      Ich konnte nichts Auschlußreiches finden. Habe auch schon einen neuen USB- Busmaster besorgt, der den OWServer mit Daten versorgt.
                                      Wenn ich beim Durchreichen des USB statt der Hersteller ID direkt den Anschluß wähle, wo der USB Busmaster dranhängt, erscheint immer "ausgesteckt"

                                      1 Reply Last reply Reply Quote 0
                                      • crunchip
                                        crunchip Forum Testing Most Active @Laser last edited by

                                        @laser sagte in Proxmox VM mit IOBroker OWServer:

                                        IOBroker auf VM installiert. Danach OW Sever installiert. Ging nicht

                                        was war denn da das Problem? vllt kommt man so dahinter warum beides zusammen nicht funktioniert

                                        @laser sagte in Proxmox VM mit IOBroker OWServer:

                                        server: port = 192.168.2.103:4304

                                        @laser sagte in Proxmox VM mit IOBroker OWServer:

                                        server: server = 192.168.10.1:3131

                                        was sind das für IP's

                                        hast du die Ports mal abgefragt ob sich da etwas behindert?

                                        L 1 Reply Last reply Reply Quote 0
                                        • L
                                          Laser @crunchip last edited by

                                          @crunchip
                                          Dadurch, daß ich ständig neue VM's erzeugt habe, ändert sich auch die ID + IP-Adresse. Ich habe natürlich (so der Plan) immer die richtige IP- Adresse verwendet.

                                          Thomas Braun ? 2 Replies Last reply Reply Quote 0
                                          • Thomas Braun
                                            Thomas Braun Most Active @Laser last edited by

                                            @laser

                                            Mit welchen Versionen bist du da unterwegs?
                                            Könnte es sein, dass du noch in diesen Fehler rennst?

                                            https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971513

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            875
                                            Online

                                            31.9k
                                            Users

                                            80.1k
                                            Topics

                                            1.3m
                                            Posts

                                            5
                                            150
                                            7793
                                            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