Upgrade between 1.235 and 1.236 appears to fail?

N3LGAN3LGA
edited October 2018 in Problems and Issues
I just went to check in on my Kiwi and it looks like its gotten itself into an upgrade/build loop... I've seen this repeating itself for the last hour and a half, attempting to build, starting up 1.235 again and then attempting to upgrade again.. any ideas of things I should check? I can ssh into the debian user, disk appears to have 2.4g available, web interface appears to be listening, but no response back:

root@kiwisdr:/var/log# nc localhost 8073
GET /
root@kiwisdr:/var/log#

Thanks
- Kevin, N3LGA

---
snip from my /var/log/messages


Sep 30 13:34:29 kiwisdr kiwid: 08:47:10.296 01.. 2 25690.95 kHz amn z5 "162.251.186.154" Los Gatos, California, USA (LEAVING after 1:01:38)
Sep 30 14:00:25 kiwisdr kiwid: 09:13:06.060 012. 2 GEOLOC: 95.246.95.135 sent no geoloc info, trying from here
Sep 30 14:00:25 kiwisdr kiwid: 09:13:06.918 012. 2 GEOLOC: extreme-ip-lookup.com/json/95.246.95.135
Sep 30 15:46:11 kiwisdr kiwid: 10:58:52.698 012. 2 14300.00 kHz usb z11 "w6ddu" 73.241.177.132 Napa, California, USA (ARRIVED)
Sep 30 15:46:22 kiwisdr kiwid: 10:59:03.914 012. 2 14300.00 kHz usb z11 "w6ddu" 73.241.177.132 Napa, California, USA (LEAVING after 0:00:21)
Sep 30 20:48:09 kiwisdr kiwid: 16:00:50.003 012. 2 14072.20 kHz cw z6 "73.15.156.50" Santa Rosa, California, USA (ARRIVED)
Sep 30 20:49:37 kiwisdr kiwid: 16:02:18.904 01.. 2 27385.00 kHz lsb z5 "73.15.156.50" Santa Rosa, California, USA (LEAVING after 0:01:40)
Sep 30 21:57:58 kiwisdr kiwid: 17:10:39.807 012. 2 740.00 kHz am z6 "91.77.59.232" Moscow, Russia (ARRIVED)
Sep 30 21:58:09 kiwisdr kiwid: 17:10:50.047 01.. 2 13087.00 kHz usb z6 "91.77.59.232" Moscow, Russia (LEAVING after 0:00:22)
Sep 30 22:57:45 kiwisdr kiwid: 18:10:26.037 012. 2 GEOLOC: 174.221.129.183 sent no geoloc info, trying from here
Sep 30 22:57:51 kiwisdr kiwid: 18:10:32.157 012. 2 GEOLOC: ipapi.co/174.221.129.183/json
Sep 30 22:59:40 kiwisdr kiwid: 18:12:21.676 012. 2 1000.00 kHz am z4 "174.221.129.183" Chicago, Illinois, USA (ARRIVED)
Sep 30 23:02:05 kiwisdr kiwid: 18:14:46.395 01.. 2 740.00 kHz am z4 "174.221.129.183" Chicago, Illinois, USA (LEAVING after 0:02:37)
Oct 1 00:01:45 kiwisdr kiwid: 19:14:26.039 012. 2 GEOLOC: 95.246.95.135 sent no geoloc info, trying from here
Oct 1 00:01:45 kiwisdr kiwid: 19:14:26.621 012. 2 GEOLOC: ipapi.co/95.246.95.135/json
Oct 1 02:00:25 kiwisdr kiwid: 21:13:06.041 012. 2 GEOLOC: 95.246.95.135 sent no geoloc info, trying from here
Oct 1 02:00:25 kiwisdr kiwid: 21:13:06.791 012. 2 GEOLOC: extreme-ip-lookup.com/json/95.246.95.135
Oct 1 04:42:05 kiwisdr kiwid: 23:54:46.050 01.. UPDATE: check scheduled
Oct 1 04:42:05 kiwisdr kiwid: 23:54:46.064 01.. UPDATE: checking for updates
Oct 1 04:42:06 kiwisdr kiwid: 23:54:47.098 01.. UPDATE: version changed, current 1.235, new 1.236
Oct 1 04:42:06 kiwisdr kiwid: 23:54:47.101 01.. UPDATE: building new version..
Oct 1 04:42:25 kiwisdr kiwid: 00:00:00.579 KiwiSDR v1.235 --------------------------------------------------------------------
Oct 1 04:42:25 kiwisdr kiwid: 00:00:00.583 compiled: Sep 30 2018 04:42:43
Oct 1 04:42:25 kiwisdr kiwid: 00:00:00.586 -debian 8
Oct 1 04:42:25 kiwisdr kiwid: 00:00:00.586 /etc/debian_version 8.5
Oct 1 04:42:25 kiwisdr kiwid: 00:00:00.586 background mode: delaying start 30 secs...
Oct 1 04:42:55 kiwisdr kiwid: 00:00:30.669 reading configuration from file /root/kiwi.config/kiwi.json: 139 tokens
Oct 1 04:42:55 kiwisdr kiwid: 00:00:30.673 reading configuration from file /root/kiwi.config/admin.json: 83 tokens
Oct 1 04:42:56 kiwisdr kiwid: 00:00:31.060 serial number from EEPROM: 1362
Oct 1 04:42:56 kiwisdr kiwid: 00:00:31.131 reading configuration from file /root/kiwi.config/dx.json: 7084 tokens
Oct 1 04:42:56 kiwisdr kiwid: 00:00:31.134 887 dx entries
Oct 1 04:42:56 kiwisdr kiwid: 00:00:31.148 .... firmware: SDR_4RX_4WF
Oct 1 04:42:56 kiwisdr kiwid: 00:00:31.150 .... firmware: rx_chans=4 wf_chans=4
Oct 1 04:42:56 kiwisdr kiwid: 00:00:31.153 .... firmware: NRX bufs=4 samps=170 loop=85/85 rem=0/0
Oct 1 04:42:56 kiwisdr kiwid: 00:00:31.153 .... firmware: NWF xfer=9 samps=911 rpt=50 loop=18 rem=11
Oct 1 04:42:56 kiwisdr kiwid: 00:00:31.154 .... listening on default port 8073/8073 for "openwebrx"
Oct 1 04:42:56 kiwisdr kiwid: 00:00:31.156 .... webserver for "openwebrx" on port [::]:8073
Oct 1 04:42:56 kiwisdr kiwid: 00:00:31.386 .... ### using SPI_DEV
Oct 1 04:42:57 kiwisdr kiwid: 00:00:32.160 .... FPGA version 1
Oct 1 04:42:57 kiwisdr kiwid: 00:00:32.620 .... using DC_offsets: I -0.020000 Q -0.020000
Oct 1 04:43:01 kiwisdr kiwid: 00:00:36.025 01.. 1 14097.10 kHz usb z0 "WSPR-autorun" 127.0.0.1 (ARRIVED)
Oct 1 04:43:01 kiwisdr kiwid: 00:00:36.028 01.. 0 7040.10 kHz usb z0 "WSPR-autorun" 127.0.0.1 (ARRIVED)
Oct 1 04:43:01 kiwisdr kiwid: 00:00:36.032 01.. UPDATE: check scheduled (startup)
Oct 1 04:43:01 kiwisdr kiwid: 00:00:36.038 01.. UPDATE: checking for updates
Oct 1 04:43:01 kiwisdr kiwid: 00:00:36.856 01.. DDNS: public ip 24.130.58.48
Oct 1 04:43:01 kiwisdr kiwid: 00:00:36.859 01.. DDNS: lat/lon = (37.369700, -122.021400)
Oct 1 04:43:01 kiwisdr kiwid: 00:00:36.862 01.. DDNS: private IPv4 <10.0.1.42> 0x0a00012a /24 0xffffff00
Oct 1 04:43:01 kiwisdr kiwid: 00:00:36.862 01.. DDNS: private IPv6 <2601:647:4b00:b00:8a4a:eaff:fee0:13ab> /64 ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00:00:00:00:00:
Oct 1 04:43:01 kiwisdr kiwid: 00:00:36.863 01.. DDNS: private IPv6 LINK-LOCAL /64 ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00:00:00:00:00:
Oct 1 04:43:02 kiwisdr kiwid: 00:00:37.069 01.. UPDATE: version changed, current 1.235, new 1.236
Oct 1 04:43:02 kiwisdr kiwid: 00:00:37.071 01.. UPDATE: building new version..
Oct 1 04:43:20 kiwisdr kiwid: 00:00:00.580 KiwiSDR v1.235 --------------------------------------------------------------------
Oct 1 04:43:20 kiwisdr kiwid: 00:00:00.583 compiled: Sep 30 2018 04:42:43
Oct 1 04:43:20 kiwisdr kiwid: 00:00:00.586 -debian 8
Oct 1 04:43:20 kiwisdr kiwid: 00:00:00.586 /etc/debian_version 8.5
Oct 1 04:43:20 kiwisdr kiwid: 00:00:00.586 background mode: delaying start 30 secs...
Oct 1 04:43:50 kiwisdr kiwid: 00:00:30.669 reading configuration from file /root/kiwi.config/kiwi.json: 139 tokens
Oct 1 04:43:50 kiwisdr kiwid: 00:00:30.673 reading configuration from file /root/kiwi.config/admin.json: 83 tokens
Oct 1 04:43:51 kiwisdr kiwid: 00:00:31.060 serial number from EEPROM: 1362
Oct 1 04:43:51 kiwisdr kiwid: 00:00:31.132 reading configuration from file /root/kiwi.config/dx.json: 7084 tokens
Oct 1 04:43:51 kiwisdr kiwid: 00:00:31.135 887 dx entries
Oct 1 04:43:51 kiwisdr kiwid: 00:00:31.149 .... firmware: SDR_4RX_4WF
Oct 1 04:43:51 kiwisdr kiwid: 00:00:31.151 .... firmware: rx_chans=4 wf_chans=4
Oct 1 04:43:51 kiwisdr kiwid: 00:00:31.154 .... firmware: NRX bufs=4 samps=170 loop=85/85 rem=0/0
Oct 1 04:43:51 kiwisdr kiwid: 00:00:31.154 .... firmware: NWF xfer=9 samps=911 rpt=50 loop=18 rem=11
Oct 1 04:43:51 kiwisdr kiwid: 00:00:31.155 .... listening on default port 8073/8073 for "openwebrx"
Oct 1 04:43:51 kiwisdr kiwid: 00:00:31.159 .... webserver for "openwebrx" on port [::]:8073
Oct 1 04:43:51 kiwisdr kiwid: 00:00:31.389 .... ### using SPI_DEV
Oct 1 04:43:52 kiwisdr kiwid: 00:00:32.160 .... FPGA version 1
Oct 1 04:43:52 kiwisdr kiwid: 00:00:32.620 .... using DC_offsets: I -0.020000 Q -0.020000
Oct 1 04:43:56 kiwisdr kiwid: 00:00:36.015 01.. 1 14097.10 kHz usb z0 "WSPR-autorun" 127.0.0.1 (ARRIVED)
Oct 1 04:43:56 kiwisdr kiwid: 00:00:36.018 01.. 0 7040.10 kHz usb z0 "WSPR-autorun" 127.0.0.1 (ARRIVED)
Oct 1 04:43:56 kiwisdr kiwid: 00:00:36.022 01.. UPDATE: check scheduled (startup)
Oct 1 04:43:56 kiwisdr kiwid: 00:00:36.028 01.. UPDATE: checking for updates
Oct 1 04:43:56 kiwisdr kiwid: 00:00:36.805 01.. DDNS: public ip 24.130.58.48
Oct 1 04:43:56 kiwisdr kiwid: 00:00:36.808 01.. DDNS: lat/lon = (37.369700, -122.021400)
Oct 1 04:43:56 kiwisdr kiwid: 00:00:36.811 01.. DDNS: private IPv4 <10.0.1.42> 0x0a00012a /24 0xffffff00
Oct 1 04:43:56 kiwisdr kiwid: 00:00:36.811 01.. DDNS: private IPv6 <2601:647:4b00:b00:8a4a:eaff:fee0:13ab> /64 ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00:00:00:00:00:
Oct 1 04:43:56 kiwisdr kiwid: 00:00:36.811 01.. DDNS: private IPv6 LINK-LOCAL /64 ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00:00:00:00:00:
Oct 1 04:43:57 kiwisdr kiwid: 00:00:37.060 01.. UPDATE: version changed, current 1.235, new 1.236
Oct 1 04:43:57 kiwisdr kiwid: 00:00:37.063 01.. UPDATE: building new version..
Oct 1 04:44:15 kiwisdr kiwid: 00:00:00.579 KiwiSDR v1.235 --------------------------------------------------------------------
Oct 1 04:44:15 kiwisdr kiwid: 00:00:00.583 compiled: Sep 30 2018 04:42:43
Oct 1 04:44:15 kiwisdr kiwid: 00:00:00.586 -debian 8
Oct 1 04:44:15 kiwisdr kiwid: 00:00:00.586 /etc/debian_version 8.5
Oct 1 04:44:15 kiwisdr kiwid: 00:00:00.586 background mode: delaying start 30 secs...
Oct 1 04:44:45 kiwisdr kiwid: 00:00:30.669 reading configuration from file /root/kiwi.config/kiwi.json: 139 tokens
Oct 1 04:44:45 kiwisdr kiwid: 00:00:30.673 reading configuration from file /root/kiwi.config/admin.json: 83 tokens
Oct

Comments

  • jksjks
    edited October 2018
    I've only had one other complaint and a manual rebuild (I think) cured whatever the problem was.
    Hundreds of other Kiwis have updated just fine.

    I need more information. Do you know how to login to your Kiwi using ssh (Linux/Mac) or PuTTY (Windows)? If so, can you try these commands and let me know what error messages occur after the build starts:

    cdp
    mst (stops Kiwi server running in background)
    k (runs server in foreground)

    If this doesn't work type "up" to do a manual build and see if that clears it up.
    trevmar
  • n8ooun8oou
    This morning my kiwi returned the firefox "unable to connect" page. Before reading this thread I did a power cycle on the kiwi. The result was a kiwi screen that told me the browser was using a old cached version of a javascript. I cleared the cache and tried again. - Same result, but this time I clicked continue. I got some of the openweb RX screen, but no waterfall/receive. The stat button reported v235.

    I read this thread and tried the cdp, mst, then k commands. I didn't see any error type messages, but I was back to the "unable to connect message".

    I then issued the 'up' command, and after the rebuild I seem to be working on 236 now.

    I hope this helps. What is the difference between the k and up commands?

    Mike N8OOU
    trevmar
  • trevmartrevmar
    I have the same problem this morning. Kiwi server dead. Can SSH into Beagle but I have forgotten root password. Never mind, I fixed that one :) I was able to issue the mst command, and it responded correctly, but from beagle su I cannot issue k or up. The console tells me "bash: up: command not found" yet mst worked??? Note that k is not found either. But cdp did work...
    I will keep trying to revive it, but any suggestions would be welcome...
  • trevmartrevmar
    The tail of my /var/log/messages shows "action 17" going wrong. What is that?

    Oct 1 13:33:15 kiwisdr kiwid: 00:00:35.813 01.. UPDATE: check scheduled (startup)
    Oct 1 13:33:15 kiwisdr kiwid: 00:00:35.848 01.. UPDATE: checking for updates
    Oct 1 13:33:15 kiwisdr kiwid: 00:00:36.488 01.. DDNS: public ip ICENSOREDTHIS
    Oct 1 13:33:15 kiwisdr kiwid: 00:00:36.491 01.. DDNS: lat/lon = (34.213300, -118.880000)
    Oct 1 13:33:15 kiwisdr kiwid: 00:00:36.494 01.. DDNS: private IPv4 0xc0a80188 /24 0xffffff00
    Oct 1 13:33:15 kiwisdr kiwid: 00:00:36.494 01.. DDNS: private IPv6 LINK-LOCAL /64 ff:ff:ff:ff :ff:ff:ff:ff:00:00:00:00:00:00:00:00:
    Oct 1 13:33:16 kiwisdr kiwid: 00:00:36.897 01.. UPDATE: version changed, current 1.235, new 1.236
    Oct 1 13:33:16 kiwisdr kiwid: 00:00:36.900 01.. UPDATE: building new version..
    Oct 1 13:34:33 kiwisdr rsyslogd-2007: action 'action 17' suspended, next retry is Mon Oct 1 13:36:03 2018 [try http://www.rsyslog. com/e/2007 ]
    Oct 1 13:40:40 kiwisdr rsyslogd-2007: action 'action 17' suspended, next retry is Mon Oct 1 13:42:10 2018 [try http://www.rsyslog. com/e/2007 ]
    Oct 1 13:50:45 kiwisdr rsyslogd-2007: action 'action 17' suspended, next retry is Mon Oct 1 13:52:15 2018 [try http://www.rsyslog. com/e/2007 ]
    root@kiwisdr:/var/log#
  • trevmartrevmar
    Making headway -- turns up that "up" is a script which has to be executed "./up"
    Upgrade is now proceding, let's hope it finished OK this time :)
    ve6hfd
  • trevmartrevmar
    OK, all fixed now. Just a little linux work was needed, and I don't hack that every day....
  • jksjks
    Well, I wish I understood why this seems to be a problem for some people. Anyone with this problem willing to let me login and take a closer look? You'd either have to have a (temporary) NAT entry for ssh on your router pointed to the Kiwi. Or let me Teamview into your pc and then ssh/PuTTY to the Kiwi.
  • jksjks
    Okay, I think I see a problem here. Mike N8OOU and Trevmar, do you guys run WSPR auto-run on your Kiwis?
  • ve6jyve6jy
    The one KIWI I did have auto run on also is the one of three that has the issue. You're welcome to teamview here if you need.
  • jksjks
    edited October 2018
    Okay, I see the bug. It was actually introduced in v1.235 but doesn't get triggered until a restart (like when updating to v1.236)

    I'll fix it in today's update. But the issue now is that you'll either have to temporarily turn off WSPR auto-run or go through the manual update procedure one more time to get past this problem.
    ve6hfdVK3KHZ
  • jksjks
    Please see the important info here: http://forum.kiwisdr.com/discussion/1341/using-wspr-auto-run-action-required-for-todays-v1-237-update#latest
  • N3LGAN3LGA
    Super sorry that I reported and then wasn't available for troubleshooting, thanks jks and trevmar, I'm back up and running. Thanks again! Kevin, N3LGA
  • jksjks
    @Kevin Not a problem at all. What led me straight to the bug was the report in the other thread: click the "kick" button on a WSPR auto-run connection and the server crashes.
    VK3KHZ
  • JohnTJohnT
    My kiwi has crashed while I am away from home and was running WSPR autorun so guess that was the problem.

    However I have no idea how to implement any of the fixes as I know nothing about Linux or the commands etc. mentioned as I am into radio not software so any suggestions as to what I need to do would be appreciated. I expect to be home tomorrow or Thursday at some point.
  • G8JNJG8JNJ
    edited October 2018
    Hi John,

    You need to connect to your KiWi by means of a terminal program such as PuTTY.

    https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html

    Setup the KiWi IP address in PuTTY and select Port 22.

    Select SSH and connect.

    When you connect you should get a terminal window apear and show a prompt from your KiWi to login. Use the user name "root"

    You should then get a command line cursor.

    type cdp and press enter

    then type up and press enter

    A whole load of stuff should be listed in the terminal window and after about 5 mins the command prompt will reappear.

    Leave it for a short while and the KiWi should have restarted, updated and be back to normal.

    Regards,

    Martin - G8JNJ
  • jksjks
    Worst case: if you have Teamviewer on a pc on the same network as your Kiwi I'd be happy to connect and fix it. You'd just have to start Teamviewer and email me the access id and password it gives you.
  • WA2ZKDWA2ZKD
    TV requires a port in his router to be open though doesn't it?
  • jksjks
    edited October 2018
    Nope, that's the whole idea.
    WA2ZKD
  • m1geom1geo
    edited October 2018
    I have 3 KiwiSDRs and all of them have this issue. SDR is dead on HTTP but SSH running no problem. Martin's instructions didn't work verbatim. I have extensive Linux knowledge, but this is the first time I've played around on the KiwiSDR so apologies if there was a-priori knowledge implied that I don't have.

    What worked for me

    • cd Beagle_SDR_GPS # move into the source folder
    • git pull # update the source files from repository
    • ./up # wait for a while for the compilation to take place
    • reboot # restart OS - when it comes back up, it works!
    Hope that helps,

    George,
    M1GEO.com
    M0TAZOwdjim
  • OwdjimOwdjim
    I had the same issue, but the manual upgrade process mentioned worked for me.

    Cheers, Chris.
  • jksjks
    edited October 2018
    The "git pull" is a little redundant. But it won't hurt anything. You must login to the Beagle as user "root" and not "debian". Contents of "up" file, in part: 
    make stop
git clean -fd
git checkout .
git pull -v
make clean
make
make install
make start
    m1geo
  • JohnTJohnT
    Hi Martin

    Many thanks for the information I will give is a try when I get home.

    Also thanks to John for the offer to fix it via Teamviewer. If I cannot get it sorted using the instructions from Martin i will be in touch.

    Regards

    John - G4HPW / W1JCT
  • JohnTJohnT
    edited October 2018
    Success?

    Had a problem at first with Martin's cpd command returning a not recognised message but a bit of reading this thread identified it should be cdp..

    Once that was resolved all went as per instructions. [I edited his post to now say "cdp" -jks]

    Regards

    John - G4HPW / W1JCT
  • VK3KHZVK3KHZ
    edited October 2018
    Success here too, both SDR's ( 2/4 ) that failed upgrade were running 8CH and had WSPR autoruns.. all happy now thanks !
    PK.
Sign In or Register to comment.