Why is the status message for avahi-daemon.service permanently “starting up”?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
2
down vote

favorite












$ systemctl status avahi-daemon
● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2018-05-08 08:01:52 BST; 8h ago
Main PID: 817 (avahi-daemon)
Status: "avahi-daemon 0.7 starting up."
Tasks: 2 (limit: 4915)
Memory: 1.8M
CGroup: /system.slice/avahi-daemon.service
├─817 avahi-daemon: running [alan-laptop.local]
└─852 avahi-daemon: chroot helper

$ rpm -q avahi
avahi-0.7-12.fc28.x86_64






share|improve this question























    up vote
    2
    down vote

    favorite












    $ systemctl status avahi-daemon
    ● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
    Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled)
    Active: active (running) since Tue 2018-05-08 08:01:52 BST; 8h ago
    Main PID: 817 (avahi-daemon)
    Status: "avahi-daemon 0.7 starting up."
    Tasks: 2 (limit: 4915)
    Memory: 1.8M
    CGroup: /system.slice/avahi-daemon.service
    ├─817 avahi-daemon: running [alan-laptop.local]
    └─852 avahi-daemon: chroot helper

    $ rpm -q avahi
    avahi-0.7-12.fc28.x86_64






    share|improve this question





















      up vote
      2
      down vote

      favorite









      up vote
      2
      down vote

      favorite











      $ systemctl status avahi-daemon
      ● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
      Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled)
      Active: active (running) since Tue 2018-05-08 08:01:52 BST; 8h ago
      Main PID: 817 (avahi-daemon)
      Status: "avahi-daemon 0.7 starting up."
      Tasks: 2 (limit: 4915)
      Memory: 1.8M
      CGroup: /system.slice/avahi-daemon.service
      ├─817 avahi-daemon: running [alan-laptop.local]
      └─852 avahi-daemon: chroot helper

      $ rpm -q avahi
      avahi-0.7-12.fc28.x86_64






      share|improve this question











      $ systemctl status avahi-daemon
      ● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
      Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled)
      Active: active (running) since Tue 2018-05-08 08:01:52 BST; 8h ago
      Main PID: 817 (avahi-daemon)
      Status: "avahi-daemon 0.7 starting up."
      Tasks: 2 (limit: 4915)
      Memory: 1.8M
      CGroup: /system.slice/avahi-daemon.service
      ├─817 avahi-daemon: running [alan-laptop.local]
      └─852 avahi-daemon: chroot helper

      $ rpm -q avahi
      avahi-0.7-12.fc28.x86_64








      share|improve this question










      share|improve this question




      share|improve this question









      asked May 8 at 15:36









      sourcejedi

      18.2k32475




      18.2k32475




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          2
          down vote



          accepted










          The source code for avahi-daemon source code includes several more status messages, e.g.




          sd_notifyf(0, "STATUS=Server startup complete. Host name is %s. Local service cookie is %u.", avahi_server_get_host_name_fqdn(s), avahi_server_get_local_service_cookie(s));




          However, by default avahi-daemon enters a secure chroot during startup. This means it can't access the systemd notification socket /run/systemd/notify. It has blocked itself from sending status messages to systemd. Oops.



          # ls -l /proc/817/root
          lrwxrwxrwx. 1 root root 0 May 8 16:27 /proc/817/root -> /etc/avahi
          # ls -l /proc/817/root/
          -rw-r--r--. 1 root root 1753 Jul 10 2017 avahi-daemon.conf
          drwxr-xr-x. 2 root root 4096 Apr 6 16:48 etc
          -rw-r--r--. 1 root root 1121 Jul 10 2017 hosts
          drwxr-xr-x. 2 root root 4096 Apr 6 16:48 services





          share|improve this answer





















            Your Answer







            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "106"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            convertImagesToLinks: false,
            noModals: false,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );








             

            draft saved


            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f442578%2fwhy-is-the-status-message-for-avahi-daemon-service-permanently-starting-up%23new-answer', 'question_page');

            );

            Post as a guest






























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            2
            down vote



            accepted










            The source code for avahi-daemon source code includes several more status messages, e.g.




            sd_notifyf(0, "STATUS=Server startup complete. Host name is %s. Local service cookie is %u.", avahi_server_get_host_name_fqdn(s), avahi_server_get_local_service_cookie(s));




            However, by default avahi-daemon enters a secure chroot during startup. This means it can't access the systemd notification socket /run/systemd/notify. It has blocked itself from sending status messages to systemd. Oops.



            # ls -l /proc/817/root
            lrwxrwxrwx. 1 root root 0 May 8 16:27 /proc/817/root -> /etc/avahi
            # ls -l /proc/817/root/
            -rw-r--r--. 1 root root 1753 Jul 10 2017 avahi-daemon.conf
            drwxr-xr-x. 2 root root 4096 Apr 6 16:48 etc
            -rw-r--r--. 1 root root 1121 Jul 10 2017 hosts
            drwxr-xr-x. 2 root root 4096 Apr 6 16:48 services





            share|improve this answer

























              up vote
              2
              down vote



              accepted










              The source code for avahi-daemon source code includes several more status messages, e.g.




              sd_notifyf(0, "STATUS=Server startup complete. Host name is %s. Local service cookie is %u.", avahi_server_get_host_name_fqdn(s), avahi_server_get_local_service_cookie(s));




              However, by default avahi-daemon enters a secure chroot during startup. This means it can't access the systemd notification socket /run/systemd/notify. It has blocked itself from sending status messages to systemd. Oops.



              # ls -l /proc/817/root
              lrwxrwxrwx. 1 root root 0 May 8 16:27 /proc/817/root -> /etc/avahi
              # ls -l /proc/817/root/
              -rw-r--r--. 1 root root 1753 Jul 10 2017 avahi-daemon.conf
              drwxr-xr-x. 2 root root 4096 Apr 6 16:48 etc
              -rw-r--r--. 1 root root 1121 Jul 10 2017 hosts
              drwxr-xr-x. 2 root root 4096 Apr 6 16:48 services





              share|improve this answer























                up vote
                2
                down vote



                accepted







                up vote
                2
                down vote



                accepted






                The source code for avahi-daemon source code includes several more status messages, e.g.




                sd_notifyf(0, "STATUS=Server startup complete. Host name is %s. Local service cookie is %u.", avahi_server_get_host_name_fqdn(s), avahi_server_get_local_service_cookie(s));




                However, by default avahi-daemon enters a secure chroot during startup. This means it can't access the systemd notification socket /run/systemd/notify. It has blocked itself from sending status messages to systemd. Oops.



                # ls -l /proc/817/root
                lrwxrwxrwx. 1 root root 0 May 8 16:27 /proc/817/root -> /etc/avahi
                # ls -l /proc/817/root/
                -rw-r--r--. 1 root root 1753 Jul 10 2017 avahi-daemon.conf
                drwxr-xr-x. 2 root root 4096 Apr 6 16:48 etc
                -rw-r--r--. 1 root root 1121 Jul 10 2017 hosts
                drwxr-xr-x. 2 root root 4096 Apr 6 16:48 services





                share|improve this answer













                The source code for avahi-daemon source code includes several more status messages, e.g.




                sd_notifyf(0, "STATUS=Server startup complete. Host name is %s. Local service cookie is %u.", avahi_server_get_host_name_fqdn(s), avahi_server_get_local_service_cookie(s));




                However, by default avahi-daemon enters a secure chroot during startup. This means it can't access the systemd notification socket /run/systemd/notify. It has blocked itself from sending status messages to systemd. Oops.



                # ls -l /proc/817/root
                lrwxrwxrwx. 1 root root 0 May 8 16:27 /proc/817/root -> /etc/avahi
                # ls -l /proc/817/root/
                -rw-r--r--. 1 root root 1753 Jul 10 2017 avahi-daemon.conf
                drwxr-xr-x. 2 root root 4096 Apr 6 16:48 etc
                -rw-r--r--. 1 root root 1121 Jul 10 2017 hosts
                drwxr-xr-x. 2 root root 4096 Apr 6 16:48 services






                share|improve this answer













                share|improve this answer



                share|improve this answer











                answered May 8 at 15:36









                sourcejedi

                18.2k32475




                18.2k32475






















                     

                    draft saved


                    draft discarded


























                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f442578%2fwhy-is-the-status-message-for-avahi-daemon-service-permanently-starting-up%23new-answer', 'question_page');

                    );

                    Post as a guest













































































                    Popular posts from this blog

                    How to check contact read email or not when send email to Individual?

                    Displaying single band from multi-band raster using QGIS

                    How many registers does an x86_64 CPU actually have?