These are the terminal logs
for almost two days now i'm getting destination host unreachable.

  • erik replied to this.

    Hi krishnashravan ,

    Well the RPi CM4 is not at that IP apparently. Perhaps try IP scanner, check router logs (connected devices), or check SSH into RPi docs; ssh pi@luxonis.local -X should be possible.

    Thanks, Erik


    This is just now
    its just that when the pi crashes that ip becomes unreachable
    It crashes at random and comes back up

    • erik replied to this.
      2 months later

      thanks erik for the reply
      anywhere to check if it has any undervoltage issues?

      my use case is basically
      running a node app to run the site on the pi's address
      and running a python file for people counting
      i observed that when i run the python file
      the ping goes up alot and eventually crash(destination host unreachable) or timeout

        Hi krishnashravan
        Sounds like a bandwidth issue then.. I assume ping goes up because the pipeline sends results back to rpi, which saturates its bandwidth and it's therefore unable to return pings, and then it crashes since the server probably times out. Can you confirm you are sending large/high res video back to the rpi?

        Thanks,
        Jaka

          jakaskerl

          Yes the video is high res

          But when i run it manually (change to a particular directory and then execute) less changes of crashing)

          But when i run it using a bat file to run the node app or the video python file more chances of failling

            Hi krishnashravan
            I'm not entirely sure how you are running the scripts (using bat file / manual?). Maybe try lowering the resolution of the video you are sending via ethernet to see if that is the cause.

            Thanks,
            Jaka

            krishnashravan if it "starts to crash" when you start your app, it might be related to the app itself - have you tried debugging it? What's the RAM / CPU usage of the RPi before/after you start the app? Perhaps some memory leak that causes the whole system to crash?

              erik
              I have decreased the no of crashes
              by just manually logging to the pi and run the node and python file
              but it does crash at times
              is it because it overloads the pi?
              i have no issue when i run the same code on the oak d (the one without the pi)

              • erik replied to this.

                Hi krishnashravan ,

                is it because it overloads the pi?

                That would be my initial guess, but I'd suggest you debug the code (checking CPU/RAM consumption).