Random overnight restarts/reboots? [probably changes to DX label community database]

I have a KiwiSDR2. I have it set to NOT install updates automatically and to NOT restart overnight. Yet it seems I get seemingly random reboots overnight. I've had it run for 2 weeks with no reboots, or sometimes 2 days. I'll log on the next morning and note the uptime is only a few hours.

Is it possible my Kiwi is restarting itself for some reason? Or is it absolutely power interruptions? Or does it reboot if it loses internet connection and that's a possible issue?

Not a huge deal, but if it's likely power interruptions, would be good for me to know.


-Nate

N8BTR

Comments

  • That sounds like a power supply issue, I've never seen unexpected reboots.

    Maybe you can see using journalctl whether it was a clean shutdown, in that case there would be something like this:

    Dec 15 11:27:44 kiwi systemd[1]: Reached target Shutdown.
    Dec 15 11:27:44 kiwi systemd[1]: Reached target Final Step.
    Dec 15 11:27:44 kiwi systemd[1]: systemd-reboot.service: Succeeded.
    Dec 15 11:27:44 kiwi systemd[1]: Finished Reboot.
    Dec 15 11:27:44 kiwi systemd[1]: Reached target Reboot.
    Dec 15 11:27:44 kiwi systemd[1]: Shutting down.
    


    Nate_R
  • edited December 2024

    I have enjoyed plenty of unexpected reboots of my KiwiSDR 1.

    Sometimes it happens after somebody/something with the same IP address does something.

    It's been a while since this has happened (latter part of 2023), but after fetching the log today I see a little over two weeks ago it happened again... but after somebody/something from a different IP address did something. Except this time, there's a long string of tabs in the log file between the "connection closed" last line before & the first line in the log after reboot with "KiwiSDR v1.xyz".

    But then my KiwiSDR 1 has this annoying habit of the server resetting many times every day, so perhaps I got a dicky one. A possible contrary datapoint to that is in the kiwi-reboot-20xx.log files where I save seemingly relevant lines of the log immediately prior to reboots each year: the number of times this happens has varied significantly over the years (and of course, what happens immediately before a reboot). Can't be bothered to count the actual number of reboots now, but the length of these files are:

    2018 - 134 kB

    2019 - 718 kB

    2020 - uh oh, where'd the file go?

    2021 - 450 kB

    2022 - 30 kB

    2023 - 23 kB

    2024 to today - 27 kB

    Power supply/dicky power connector issues are often the cause for others & therefore will be suggested, but those aren't the only reason.

    -vr2bg.

  • Power supplies have generally been the biggest cause of "random" issues, so it's always worth trying another type, with a different cable and connector, just to be sure.

    Regards,

    Martin

  • OK, did the journalctl and looked at it since before the last reboot.

    Dec 18 07:17:01 kiwisdr CRON[22610]: pam_unix(cron:session): session closed for user root
    Dec 18 07:40:06 kiwisdr kiwid[28278]: 1d:23:59:37.729 0...      UPDATE: check scheduled
    Dec 18 07:40:06 kiwisdr kiwid[28278]: 1d:23:59:37.738 0...      UPDATE: checking for updates
    Dec 18 07:40:11 kiwisdr kiwid[28278]: 1d:23:59:43.559 0...      UPDATE: NO CHANGE current 1.800, new 1.800
    Dec 18 07:40:11 kiwisdr kiwid[28278]: 1d:23:59:43.565 0...      file_GET: running, download/diff/restart only..
    Dec 18 07:40:14 kiwisdr kiwid[28278]: 1d:23:59:45.796 0...      ip_blacklist_get: ip_blacklist_hash = e42728a3
    Dec 18 07:40:14 kiwisdr kiwid[28278]: 1d:23:59:45.805 0...      ip_blacklist_get: stored=1965 downloaded=1965 diff=NO download_diff_restart=1
    Dec 18 07:40:14 kiwisdr kiwid[28278]: 1d:23:59:45.807 0...      DX: checking /root/kiwi.config/dx_community_config.json against kiwisdr.com/dx/dx_community_config.json
    Dec 18 07:40:14 kiwisdr kiwid[28278]: 1d:23:59:46.259 0...      DX: CURRENT /root/kiwi.config/dx_community_config.json
    Dec 18 07:40:14 kiwisdr kiwid[28278]: 1d:23:59:46.274 0...      DX: checking /root/kiwi.config/dx_community.json against kiwisdr.com/dx/dx_community.json
    Dec 18 07:40:15 kiwisdr kiwid[28278]: 1d:23:59:46.801 0...      DX: UPDATING /root/kiwi.config/dx_community.json
    Dec 18 07:40:15 kiwisdr kiwid[28278]: 1d:23:59:46.824 0...      DX: new file installed, need RESTART
    Dec 18 07:40:15 kiwisdr kiwid[28278]: 1d:23:59:46.827 0...      file_GET: RESTARTING...
    Dec 18 07:40:16 kiwisdr kiwid[22806]: BBG_BBB Debian 11.8 USE_SPIDEV
    Dec 18 07:40:16 kiwisdr systemd[1]: kiwid.service: Control process exited, code=killed, status=15/TERM
    Dec 18 07:40:16 kiwisdr kiwid[22806]: Stopping kiwid:
    Dec 18 07:40:16 kiwisdr systemd[1]: kiwid.service: Failed with result 'signal'.
    Dec 18 07:40:16 kiwisdr systemd[1]: kiwid.service: Consumed 1d 17h 22min 32.214s CPU time.
    Dec 18 07:40:26 kiwisdr systemd[1]: kiwid.service: Scheduled restart job, restart counter is at 7.
    Dec 18 07:40:26 kiwisdr systemd[1]: Stopped kiwi daemon.
    Dec 18 07:40:26 kiwisdr systemd[1]: kiwid.service: Consumed 1d 17h 22min 32.214s CPU time.
    Dec 18 07:40:26 kiwisdr systemd[1]: Starting kiwi daemon...
    Dec 18 07:40:26 kiwisdr kiwid[22826]: BBG_BBB Debian 11.8 USE_SPIDEV
    Dec 18 07:40:26 kiwisdr kiwid[22826]: Starting kiwid
    Dec 18 07:40:26 kiwisdr kiwid[22826]: BBG_BBB: Kiwi device tree loaded via U-boot overlay
    Dec 18 07:40:26 kiwisdr kiwid[22826]: BBG_BBB: SPI setup via config-pin
    Dec 18 07:40:26 kiwisdr kiwid[22846]: Current mode for P9_17 is:     spi_cs
    Dec 18 07:40:26 kiwisdr kiwid[22847]: Current mode for P9_18 is:     spi
    Dec 18 07:40:26 kiwisdr kiwid[22848]: Current mode for P9_21 is:     spi
    Dec 18 07:40:26 kiwisdr kiwid[22849]: Current mode for P9_22 is:     spi_sclk
    Dec 18 07:40:26 kiwisdr kiwid[22826]: Start kiwid: OK
    Dec 18 07:40:26 kiwisdr kiwid[22853]: Wed Dec 18 07:40:26 UTC 2024
    Dec 18 07:40:26 kiwisdr systemd[1]: Started kiwi daemon.
    Dec 18 07:40:27 kiwisdr kiwid[22852]: 00:00:00.750   KiwiSDR v1.800 --------------------------------------------------------------------
    Dec 18 07:40:27 kiwisdr kiwid[22852]: 00:00:00.755   compiled: Nov 29 2024 04:41:33 on kiwisdr
    Dec 18 07:40:27 kiwisdr kiwid[22852]: 00:00:00.755   /etc/debian_version 11.8
    Dec 18 07:40:27 kiwisdr kiwid[22852]: 00:00:00.755   Mongoose 5.6
    Dec 18 07:40:27 kiwisdr kiwid[22852]: 00:00:00.865   reading configuration from file /root/kiwi.config/kiwi.json: 739 tokens (9.8k bytes)
    Dec 18 07:40:27 kiwisdr kiwid[22852]: 00:00:00.868   reading configuration from file /root/kiwi.config/admin.json: 145 tokens (3.8k bytes)
    Dec 18 07:40:27 kiwisdr kiwid[22852]: 00:00:01.272   serial number from EEPROM: 21040
    Dec 18 07:40:27 kiwisdr kiwid[22852]: 00:00:01.274   model: KiwiSDR 2
    Dec 18 07:40:27 kiwisdr kiwid[22852]: 00:00:01.277   reading configuration from file /root/kiwi.config/dx_config.json
    Dec 18 07:40:27 kiwisdr kiwid[22852]: 00:00:01.279   reading configuration from file /root/kiwi.config/dx.json
    Dec 18 07:40:27 kiwisdr kiwid[22852]: 00:00:01.299   DX: 872 label entries
    Dec 18 07:40:27 kiwisdr kiwid[22852]: 00:00:01.301   DX: file = 872,db6868b3,52120
    Dec 18 07:40:27 kiwisdr kiwid[22852]: 00:00:01.305   reading configuration from file /root/kiwi.config/dx_community_config.json
    Dec 18 07:40:27 kiwisdr kiwid[22852]: 00:00:01.307   reading configuration from file /root/kiwi.config/dx_community.json
    


    So if I'm understanding correctly, the KiwiSDR saw there was an update to the DX Label database, and downloaded it (since I have that option enabled), and thus commenced a restart then to update the DX database. Is that right? In which case, OK, that makes sense why it would be overnight. It checks for updates then, and restarts the Kiwi if there's a DX label update.

    -Nate

    N8BTR

  • So if I'm understanding correctly, the KiwiSDR saw there was an update to the DX Label database, and downloaded it (since I have that option enabled), and thus commenced a restart then to update the DX database. Is that right?

    Correct. And this possibility should be called out on the admin status tab:

    I have been making updates to that file recently.

  • Ahh, of course, it's all laid out there! Thanks!

    Mystery solved. :-)


    -Nate

    N8BTR

Sign In or Register to comment.