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



systemd avahi




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



    systemd avahi




    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



      systemd avahi




      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




      systemd avahi





      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?

                    Image
                    Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Sep 26 at 0:12 ToanLuong 49 9 add a comment  |  up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Se
                    Read more

                    Bahrain

                    Image
                    For other uses, see Bahrain (disambiguation). Sovereign island state in the Persian Gulf Kingdom of Bahrain مملكة البحرين   (Arabic) Mamlakat al-Baḥrayn Flag Coat of arms Anthem:  نشيد البحرين الوطني Bahrainona Our Bahrain Location of   Bahrain    (circled in red) Capital and largest city Manama 26°13′N 50°35′E  /  26.217°N 50.583°E  / 26.217; 50.583 Official languages Arabic Ethnic groups (2010 [1] ) 50.7% Arab (46% Bahrani, 4.7% other Arabs) 45.5% Asian 1% European 1.2% Others Religion Islam Demonym(s) Bahraini Government Unitary constitutional monarchy • King Hamad bin Isa Al Khalifa • Crown Prince Salman bin Hamad bin Isa Al Khalifa • Prime Minister Khalifa bin Salman Al Khalifa Legislature National Assembly • Upper house Consultative Council • Lower house Council of Representatives Independence • Declared Independence [2] 14 August 1971 • from United Kingdom [1] 15 August 1971 • Admitted to the United Nations 21 September 1971 • Kingdom of Bahrain 14 February 2002
                    Read more

                    Postfix configuration issue with fips on centos 7; mailgun relay

                    Image
                    Clash Royale CLAN TAG #URR8PPP up vote 0 down vote favorite I am trying to setup postfix to relay all mail generated on the local machine via SMTP to a mailgun relay. I have used the mailgun relay before with success on an ubuntu server, but I am migrating to a Centos 7 server which I will be running in FIPS mode. There error log is below, slightly sanitized. I have a small enough network that I choose to have each machine reach out to mailgun individually (this the loopback-only, 127.0.0.0/8 restrictions) and no firewall open port allowing smtp in to the machine. I assume the FIPS mode (and with it disabling of MD5) is causing problems, but I don't know how to overcome it or if it is even possible for tls_fprint to use some supported hash such as sha256 or sha512. However, the relay=none is slightly concerning since I have relayhost set, but perhaps that is because the smtp process is failing? Any help would be appreciated! postconf -n: alias_database = hash:/etc/alia
                    Read more