Skip to content
  • MySensors
  • OpenHardware.io
  • Categories
  • Recent
  • Tags
  • Popular
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo
  1. Home
  2. Troubleshooting
  3. Raspberry MQTT config give segment fault start gateway

Raspberry MQTT config give segment fault start gateway

Scheduled Pinned Locked Moved Troubleshooting
4 Posts 2 Posters 1.0k Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M Offline
    M Offline
    martim
    wrote on last edited by
    #1

    Hi,

    I have configured the gateway software on the raspberry like:

    ./configure --my-gateway=mqtt --my-controller-ip-address=127.0.0.1 --my-mqtt-publish-topic-prefix=mygateway1-out --my-mqtt-subscribe-topic-prefix=mygateway1-in --my-mqtt-client-id=mygateway1
    

    then

    make
    sudo ./bin/mysgw
    

    which give:

    pi@raspberrypi:~/MySensors $ ./bin/mysgw 
    Nov 19 14:30:07 ERROR Failed to open log pipe.
    Nov 19 14:30:07 INFO  Starting gateway...
    Nov 19 14:30:07 INFO  Protocol version - 2.3.0
    Nov 19 14:30:07 DEBUG MCO:BGN:INIT GW,CP=RNNGL---,VER=2.3.0
    Nov 19 14:30:07 DEBUG TSF:LRT:OK
    Nov 19 14:30:07 DEBUG TSM:INIT
    Nov 19 14:30:07 DEBUG TSF:WUR:MS=0
    Segmentatiefout
    

    Segmentatiefout is Dutch for Segmentation fault

    I have a brand new Raspberry. I have updated everything to the last versions

    Is this a MQTT problem? It is running and seems oke

    1 Reply Last reply
    0
    • M Offline
      M Offline
      martim
      wrote on last edited by
      #2

      Solved. Deleted the /etc/mysensor.conf file and started sudo ./bin/mysgw again. This fixed the problem.

      mfalkviddM 1 Reply Last reply
      1
      • M martim

        Solved. Deleted the /etc/mysensor.conf file and started sudo ./bin/mysgw again. This fixed the problem.

        mfalkviddM Offline
        mfalkviddM Offline
        mfalkvidd
        Mod
        wrote on last edited by
        #3

        @martim thanks for reporting back.

        If it happens again, running

        sudo strace ./bin/mysgw
        

        might give a clue to what's causing the segfault.

        1 Reply Last reply
        0
        • M Offline
          M Offline
          martim
          wrote on last edited by
          #4

          Ok, Thanks. Will do!

          1 Reply Last reply
          0
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          22

          Online

          11.7k

          Users

          11.2k

          Topics

          113.1k

          Posts


          Copyright 2025 TBD   |   Forum Guidelines   |   Privacy Policy   |   Terms of Service
          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • MySensors
          • OpenHardware.io
          • Categories
          • Recent
          • Tags
          • Popular