Can not access kiwi using kiwisdr.local:8073 [fixed with avahi-daemon restart]

edited February 2019 in Problems Now Fixed
Hi,

I have always been able to access my kiwi using the kiwisdr.local:8073 address, on my iOS or OS X devices (never using windows though, always had to use the IP address for that).
A few days ago, I could no longer access it via the kiwisdr.local:8073 on my iOS devices either. Have run all software updates and done a rebuild of the kiwi as well, and the result is the same.
Have checked it’s hostname is set to : kiwisdr

Anything I am missing here?

Id like to get it back to how it was if possible, can still access locally via IP address no worries though.

Cheers

Simon

Comments

  • Not a Mac person but from a quick search perhaps try:

    "I had the same issue and found out how to fix it: turn any of the sharing services ON in the system preferences.
    (File sharing worked for me)."


    (https://discussions.apple.com/thread/7707202)
  • Thanks for the help, tried that fix to no effect.

    I am sure it is sometching on the kiwi which has changed, because I have a MacBook which I hadn’t used since I initially configured the kiwi with it, so hasn’t had any config changes or software updates since then, when it was working.
  • jksjks
    edited February 2019
    Login to the Beagle of your Kiwi, either using ssh from Linux/Mac, PuTTY from Windows or from the console tab of the admin page.
    Type "scs avahi-daemon". Do you see messages like this that give the impression avahi is running?
    (in all the following messages "www" will likely be replaced with "kiwisdr", the default Linux hostname of the Kiwi. My Kiwi happens to be named "www")
    Feb 26 18:22:26 www avahi-daemon[679]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.103.
    Feb 26 18:22:26 www avahi-daemon[679]: New relevant interface eth0.IPv4 for mDNS.
    Feb 26 18:22:26 www avahi-daemon[679]: Registering new address record for 192.168.1.103 on eth0.IPv4.
    
    If not, try restarting with "scst avahi-daemon", "scsa avahi-daemon" and another "scs avahi-daemon" and see if you get something like this:
    root@www:~# scs avahi-daemon
    ? avahi-daemon.service - Avahi mDNS/DNS-SD Stack
       Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled)
       Active: active (running) since Wed 2019-02-27 01:46:17 UTC; 8s ago
      Process: 6088 ExecReload=/usr/sbin/avahi-daemon -r (code=exited, status=0/SUCCESS)
     Main PID: 6109 (avahi-daemon)
       Status: "avahi-daemon 0.6.31 starting up."
       CGroup: /system.slice/avahi-daemon.service
               ??6109 avahi-daemon: running [www.local]
               ??6111 avahi-daemon: chroot helper
    
    Feb 27 01:46:17 www avahi-daemon[6109]: Process 679 died: No such process; trying to remove PID file. (/var/run/avahi-daemon//pid)
    Feb 27 01:46:17 www avahi-daemon[6109]: Found user 'avahi' (UID 107) and group 'avahi' (GID 112).
    Feb 27 01:46:17 www avahi-daemon[6109]: Successfully dropped root privileges.
    Feb 27 01:46:17 www avahi-daemon[6109]: avahi-daemon 0.6.31 starting up.
    Feb 27 01:46:17 www avahi-daemon[6109]: Successfully called chroot().
    Feb 27 01:46:17 www avahi-daemon[6109]: Successfully dropped remaining capabilities.
    Feb 27 01:46:17 www avahi-daemon[6109]: No service file found in /etc/avahi/services.
    Feb 27 01:46:17 www avahi-daemon[6109]: Joining mDNS multicast group on interface usb0.IPv4 with address 192.168.7.2.
    Feb 27 01:46:17 www avahi-daemon[6109]: New relevant interface usb0.IPv4 for mDNS.
    Feb 27 01:46:17 www avahi-daemon[6109]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::9a84:e3ff:fe93:a341.
    Feb 27 01:46:17 www avahi-daemon[6109]: New relevant interface eth0.IPv6 for mDNS.
    Feb 27 01:46:17 www avahi-daemon[6109]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.103.
    Feb 27 01:46:17 www avahi-daemon[6109]: New relevant interface eth0.IPv4 for mDNS.
    Feb 27 01:46:17 www avahi-daemon[6109]: Network interface enumeration completed.
    Feb 27 01:46:17 www avahi-daemon[6109]: Registering new address record for 192.168.7.2 on usb0.IPv4.
    Feb 27 01:46:17 www avahi-daemon[6109]: Registering new address record for fe80::9a84:e3ff:fe93:a341 on eth0.*.
    Feb 27 01:46:17 www avahi-daemon[6109]: Registering new address record for 192.168.1.103 on eth0.IPv4.
    Feb 27 01:46:17 www avahi-daemon[6109]: Registering HINFO record with values 'ARMV7L'/'LINUX'.
    Feb 27 01:46:18 www avahi-daemon[6109]: Server startup complete. Host name is www.local. Local service cookie is 3560849908.
    
    If that doesn't work type "which avahi-daemon". Does it answer "/usr/sbin/avahi-daemon" ?
    Simonc
  • Jks, mate you are a legend, this has resolved the issue

    Many thanks for your reply - I really appreciate it.

    Best regards,

    Simon
  • Okay, but a restart of the Kiwi would have resulted in a restart of the avahi-daemon in the same way as restarting it via a "scsa" (alias for "systemctl start"). So I'm not quite sure why a simple reboot didn't fix the problem for you. If you reboot it now does it continue to work?
  • Yes, rebooted a couple of times to test it since, still working OK.

    I would assume that rebooting it should have fixed the issue previously, but didn’t..anyhow all good now.
Sign In or Register to comment.