beagle seems to be working, kiwi may not be...need help

w2dbw2db
in Configuration and Operation

I have a several year old kiwi which has been rock stable all these days. But today went to look at it and got no response. At first thought it to be a network project but I can ssh into it. ifconfig shows no change in net. netstat shows port 8073 coming and going, each time it comes up the kiwi process ID number has increased. So did ps -aux and I can see the kiwi process start, run CPU up to about 16% with 168700 memory usage and four instances of /lib/systemd/systemd-udevd then after what seems like under ten seconds those five processes die and restart with higher process ID numbers.

Now I saw a procedure re: admin connection reloading/crashing, is that the same thing. Even when I see port 8073 up I cannot connect with a web browser in normal user mode or admin.

Where might my problem be? I sure hope it isn't the kiwi board...

GeorgeC W2DB

Crowley, TX

Comments

  • w2dbw2db
    edited December 2024

    Well, not sure what was up but it suddenly started working. powered down and re-mounted it in its place. Back to the original problem, kiwi process keeps re-starting every ten seconds or so. SSH still fine. I'm puzzled by this. Also, when it did come up I looked at version number and it was 1.800

    GeorgeC W2DB

  • w2dbw2db

    And again after about five to ten minutes it came up

    ???

    GeorgeC W2DB

  • jksjks
    edited December 2024

    Hi George,

    So I don't quite understand. Where are you at with this? Is connecting to the admin page now stable? And on the admin status tab it says v1.800? And can you make a user connection that stays running?

  • jksjks

    If you're still having trouble, and can ssh in, use htop to look at the processes. Set "tree" mode with the "t" key. You're looking for the "kiwid" process, not "udevd". See if it's crashing and restarting with different PIDs as you mentioned.

    If so, then do: cd; ms and look for any obvious errors in the log messages.

    If you're able to open an ssh port on your router I'm happy to connect and take a look. Email details to support@kiwisdr.com

  • w2dbw2db

    Did all of that initially. It is 1.800. And it is staying up though from reboot it takes a very long time before kiwid stays running. And this wasn't just /admin this was user access as well. So now not sure what is up with it. It just seems ok now. Not sure what happened or why.

    GeorgeC

  • jksjks

    What does "very long time" mean? On a power-up, after the Linux boot delay, kiwid purposely waits 30 seconds before allowing connections (it only does this on a power-up). It does this to allow things like the DHCP server and NTPd to stabilize in case this was actually a recovery from a general power failure at the site.

    And kiwid should only be starting once. The only exception is if it needs to fetch a newer version of the community dx file. In that case it must restart. But that should only happen once per change of the file (which doesn't occur very often).

  • G8JNJG8JNJ

    As per another thread.

    Power supplies have generally been the biggest cause of "random" issues.

    The electrolytic capacitors in power supplies dry out over time, and the voltage, current and general regulation go through a long period of gradual degradation. During this time, operation can become intermittent, and the problem may only really become apparent during periods of greater than average current draw, for example when flashing an SD card.

    I've been caught out by this on several occasions, so it's always worth trying another type of PSU, with a different cable and connector, just to be sure.

    Regards,

    Martin

Sign In or Register to comment.