Announcement

Collapse
No announcement yet.

Avahi daemon files unavailable?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Avahi daemon files unavailable?

    I've installed the plug-in on my Zee S2, I've run the command to install the Avahi daemon files from the Linux Tools page in HS3, but getting 404 errors:

    Err http://mirrordirector.raspbian.org/raspbian/ wheezy/main libisc84 armhf 1:9.8.4.dfsg.P1-6+nmu2+deb7u4 404 Not Found Err http://mirrordirector.raspbian.org/raspbian/ wheezy/main libdns88 armhf 1:9.8.4.dfsg.P1-6+nmu2+deb7u4 404 Not Found Err http://mirrordirector.raspbian.org/raspbian/ wheezy/main libisccc80 armhf 1:9.8.4.dfsg.P1-6+nmu2+deb7u4 404 Not Found Err http://mirrordirector.raspbian.org/raspbian/ wheezy/main libisccfg82 armhf 1:9.8.4.dfsg.P1-6+nmu2+deb7u4 404 Not Found Err http://mirrordirector.raspbian.org/raspbian/ wheezy/main libbind9-80 armhf 1:9.8.4.dfsg.P1-6+nmu2+deb7u4 404 Not Found Err http://mirrordirector.raspbian.org/raspbian/ wheezy/main liblwres80 armhf 1:9.8.4.dfsg.P1-6+nmu2+deb7u4 404 Not Found Err http://mirrordirector.raspbian.org/raspbian/ wheezy/main bind9-host armhf 1:9.8.4.dfsg.P1-6+nmu2+deb7u4 404 Not Found Any thoughts on what I'm doing wrong?

    #2
    It would be helpful to know exactly what command you are running. The error message seems odd as it has some space characters in the file path.

    Perhaps try running the install from a shell login to the pi.

    Comment


      #3
      Ran the following command from the linux tools within HS interface: sudo apt-get install avahi-daemon -y
      Apologies, Linux newbie. Happy to try a shell login if you can point me in the right direction.
      Thanks!

      Comment


        #4
        install putty and follow the first 7 steps of this procedure to connect to your Zee:
        https://forums.homeseer.com/forum/ho...re-using-putty

        then try the following commands:

        Code:
        sudo apt-get update
        sudo apt-get install avahi-daemon

        Comment


          #5
          Thanks! Connected and ran the commands ok. Seems to discover the chromecast devices, but then fails and shuts down the interface. Repeats. Here's the sequence of events and error:
          Dec-29 12:13:20 Info Plugin Chromecast has connected. IP:127.0.0.1:57788
          Dec-29 12:13:18 Warning I/O interface Chromecast is down, executable is not running, restarting ...
          Dec-29 12:13:05 Info Plugin Chromecast with instance: has disconnected
          Dec-29 12:13:03 Chromecast INFO Restarting discovery of chromecasts
          Dec-29 12:13:03 Chromecast ERROR Could not load file or assembly 'System.Threading.Timer, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies.
          Dec-29 12:13:03 Chromecast INFO Connecting to Big TV https://192.168.0.224:8009/
          Dec-29 12:13:03 Chromecast INFO Found Service: Google-Home-71f01924bfb5195391d3587c023fcd80
          Dec-29 12:13:03 Chromecast INFO Found Service: Google-Home-Mini-910e93a6f1d0d7c0dd06f9423559ec52
          Dec-29 12:13:03 Chromecast INFO Found Service: Chromecast-7869efc43ad584d282afc01e4d8b70b6
          Dec-29 12:13:03 Info System connected to MyHS Service successfully with license ID 85166.
          Dec-29 12:13:02 Info System connected to MyHS Service, waiting for acknowledge...
          Dec-29 12:12:49 Starting Plug-In Plugin Chromecast started successfully in 666 milliseconds
          Dec-29 12:12:48 Chromecast INFO Chromecast version 3.0.0.29
          Dec-29 12:12:48 Starting Plug-In Initializing plugin Chromecast ...
          Dec-29 12:12:48 Info Plugin Chromecast has connected. IP:127.0.0.1:57767
          Dec-29 12:12:46 Plug-In Finished initializing plug-in Chromecast
          Seems like the same error as on this forum item, but the solution indicates it's only for the SEL (upgrade to mono 5). Am I safe to perform this on the Zeetroller S2?

          https://forums.homeseer.com/forum/me...ometroller-sel

          Comment


            #6
            what version of mono do you have? run this command to check:

            Code:
            sudo mono --version

            Comment


              #7
              Is the avahi-daemon running? Use the "service --status-all" command to check. The output will list all your services. Those with a + in front of their name are running.

              Comment


                #8
                mono version is:
                Mono JIT comiler version 3.2.8 (Debian 3.2.8+dfsg-4+rpil)

                And yes, it shows [+] avahi-daemon

                Appreciate all the help here!

                Comment


                  #9
                  you need to upgrade to mono 4.x or later using this guide: https://helpdesk.homeseer.com/article/209-update-to-mono-5-12

                  WARNING: by doing this you will lost all your events trigger: https://forums.homeseer.com/forum/ho...r-mono-upgrade
                  so you need to export your events before the upgrade and import them after.

                  back up everything you can, before the upgrade in case something goes wrong

                  Comment


                    #10
                    I've tried the procedure suggested several times over the last few hours, from both the system tools command line as well as from ssh'ing in. When installing, it looks like there are a number of errors when retrieving files. After installing, the system reboots, but when I check the mono version afterward, it's still sitting at v.3.2.8 - any other ways to get those files? Here is a copy of the install process with the retrieval failures if it helps:


                    homeseer@HomeTrollerZeeS2 ~ $ sudo sh mono5.sh
                    Reading package lists... Done
                    Building dependency tree
                    Reading state information... Done
                    E: Unable to locate package mono
                    E: Invalid operation auto-remove
                    Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret -keyring /tmp/tmp.rP6ZZElXVE --trustdb-name /etc/apt//trustdb.gpg --keyring /etc /apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyserver hkp://keyser ver.ubuntu.com:80 --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF
                    gpg: requesting key D3D831EF from hkp server keyserver.ubuntu.com
                    gpg: key D3D831EF: "Xamarin Public Jenkins (auto-signing) <releng@xamarin.com>" not changed
                    gpg: Total number processed: 1
                    gpg: unchanged: 1
                    deb http://download.mono-project.com/repo/ubuntu trusty main
                    Err http://raspberrypi.collabora.com wheezy Release.gpg
                    Something wicked happened resolving 'raspberrypi.collabora.com:http' (-5 - No address associated with hostname)
                    Ign http://raspberrypi.collabora.com wheezy Release
                    Hit http://archive.raspberrypi.org wheezy Release.gpg
                    Hit http://download.mono-project.com trusty Release.gpg
                    Hit http://download.mono-project.com trusty Release
                    Hit http://archive.raspberrypi.org wheezy Release
                    Err http://raspberrypi.collabora.com wheezy/rpi armhf Packages
                    Something wicked happened resolving 'raspberrypi.collabora.com:http' (-5 - No address associated with hostname)
                    Hit http://download.mono-project.com trusty/main armhf Packages
                    Err http://raspberrypi.collabora.com wheezy/rpi Translation-en_US
                    Something wicked happened resolving 'raspberrypi.collabora.com:http' (-5 - No address associated with hostname)
                    Err http://raspberrypi.collabora.com wheezy/rpi Translation-en
                    Something wicked happened resolving 'raspberrypi.collabora.com:http' (-5 - No address associated with hostname)
                    Hit http://archive.raspberrypi.org wheezy/main armhf Packages
                    Ign http://download.mono-project.com trusty/main Translation-en_US
                    Ign http://download.mono-project.com trusty/main Translation-en
                    Ign http://archive.raspberrypi.org wheezy/main Translation-en_US
                    Ign http://archive.raspberrypi.org wheezy/main Translation-en
                    Err http://mirrordirector.raspbian.org wheezy Release.gpg
                    Connection failed
                    Get:1 http://mirrordirector.raspbian.org wheezy Release [14.4 kB]
                    Get:2 http://mirrordirector.raspbian.org wheezy/main armhf Packages [7,680 kB]
                    Get:3 http://mirrordirector.raspbian.org wheezy/contrib armhf Packages [35.0 kB]
                    Get:4 http://mirrordirector.raspbian.org wheezy/non-free armhf Packages [73.6 kB]
                    Get:5 http://mirrordirector.raspbian.org wheezy/rpi armhf Packages [592 B]
                    Ign http://mirrordirector.raspbian.org wheezy/contrib Translation-en_US
                    Ign http://mirrordirector.raspbian.org wheezy/contrib Translation-en
                    Ign http://mirrordirector.raspbian.org wheezy/main Translation-en_US
                    Ign http://mirrordirector.raspbian.org wheezy/main Translation-en
                    Ign http://mirrordirector.raspbian.org wheezy/non-free Translation-en_US
                    Ign http://mirrordirector.raspbian.org wheezy/non-free Translation-en
                    Ign http://mirrordirector.raspbian.org wheezy/rpi Translation-en_US
                    Ign http://mirrordirector.raspbian.org wheezy/rpi Translation-en
                    Fetched 7,804 kB in 7min 36s (17.1 kB/s)
                    W: Failed to fetch http://mirrordirector.raspbian.org/r...zy/Release.gpg Connection failed

                    W: Failed to fetch http://raspberrypi.collabora.com/dis...zy/Release.gpg Something wicked happened resolving 'raspberrypi.collabora.com:http' (-5 - No address associated with hostname)

                    W: Failed to fetch http://raspberrypi.collabora.com/dis...armhf/Packages Something wicked happened resolving 'raspberrypi.collabora.com:http' (-5 - No address associated with hostname)

                    W: Failed to fetch http://raspberrypi.collabora.com/dis...nslation-en_US Something wicked happened resolving 'raspberrypi.collabora.com:http' (-5 - No address associated with hostname)

                    W: Failed to fetch http://raspberrypi.collabora.com/dis...Translation-en Something wicked happened resolving 'raspberrypi.collabora.com:http' (-5 - No address associated with hostname)

                    E: Some index files failed to download. They have been ignored, or old ones used instead.
                    Reading package lists... Done
                    Building dependency tree
                    Reading state information... Done
                    Calculating upgrade... Failed
                    The following packages have unmet dependencies:
                    libmono-security4.0-cil : Depends: libmono-system4.0-cil (>= 3.2.8) but it is not going to be installed
                    E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

                    The system is going down for reboot NOW!eeS2 (pts/0) (Sat Dec 29 21:13:27 201
                    homeseer@HomeTrollerZeeS2 ~ $

                    Comment


                      #11
                      There's a problem with the link in post #9. The URL text displayed is different from the underlying link. The link is for the instructions for the SEL rather than the Zee S2.

                      Try this instead: https://helpdesk.homeseer.com/articl...e-to-mono-5-12

                      Comment


                        #12
                        Thanks for catching that. I've tried with the instructions for the Zee2. Took quite a while but when finally finished indicated "E: Unable to correct problems, you have held broken packages". System then rebooted. Tried a few times with similar results. Still showing mono v3.2.8. Do I need a complete reimage? Other thoughts?

                        Comment


                          #13
                          Moving to the latest HS3-Pi image might be easiest. It comes with mono 4.6.2.

                          I've managed to help a few others with upgrading but it can be an ordeal. LMK what path you want to go with.

                          Comment


                            #14
                            I've tried the upgrade again a few more times with identical results. Looks like I'll need to perform a full upgrade unless anyone has other suggestions?

                            Comment


                              #15
                              Installed new image (thanks!) on the sd card. Booted up ok. Reloaded config and so far so good. Thank you to zwolfpack for the support!

                              Comment

                              Working...
                              X