Thruk installation “failed to open socket”











up vote
1
down vote

favorite












I am extremely confused, and Google isn't really helping. Also, I'm kind of a Linux novice. I've taken a couple of classes, but that was all about how to configure things in a basic Linux setup. I'm now trying to learn how to set things up to actually use. At work we use Nagios/Thruk so I'm trying to set it up on my home network so I can learn it better.



I set up a CentOS 6.6 machine. I've installed Nagios on it, and that's working fine. Now I'm trying to set up Thruk. I've managed to get livestatus and Thruk installed, but I'm stuck at getting it to actually work. In the documentation it shows that I'm supposed to add these two lines to the /usr/local/nagios/etc/nagios.cfg file:



broker_module=/usr/local/lib/mk-livestatus/livestatus.o /var/lib/nagios/rw/live
event_broker_options=-1


the event_broker_options=-1 line already existed, so I added the other line above it. In some examples, it is shown as this instead:



broker_module=/usr/local/lib/mk-livestatus/livestatus.o /tmp/live.sock
event_broker_options=-1


I've tried both, and I cannot seem to get this to work. I've done all the basics I can think of. I've reinstalled and updated all of the components (nagios, livestatus, thruk), I've reloaded and restarted all service associated a billion times. When the line I added is in there, Nagios starts when I tell it to start, but it then stops immediately. When I go into the /usr/local/nagios/var/nagios.log file, I see the following lines whenever I try to start Nagios and it fails:



Error: Could not load module '/usr/local/lib/mk-livestatus/livestatus.o' -> /usr/local/lib/mk-livestatus/livestatus.o: undefined symbol: last_command_check
Error: Failde to load module '/usr/local/lib/mk-livestatus/livestatus.o' .
Error: Module loading failed. Aborting.


If I comment out the line I added to the nagios.cfg file, Nagios will load and work properly, but Thruk still isn't working properly. If I load the Thruk page, I get this:



No Backend available
None of the configured Backends could be reached, please have a look at the logfile for detailed information and make sure the core is up and running.
Details:
home-net: ERROR: failed to open socket /tmp/live.sock: No such file or directory (/tmp/live.sock)


It appears to me to be something wrong with livestatus, but I don't understand it well enough to fix it on my own and I'm having a lot of difficulty finding (or maybe understanding) the answer anywhere. From what I understood, I thought the nagios.cfg file was supposed to configure the live.sock file. Is that not correct? I'm doing my best, but I need some help.










share|improve this question
















bumped to the homepage by Community 2 days ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.



















    up vote
    1
    down vote

    favorite












    I am extremely confused, and Google isn't really helping. Also, I'm kind of a Linux novice. I've taken a couple of classes, but that was all about how to configure things in a basic Linux setup. I'm now trying to learn how to set things up to actually use. At work we use Nagios/Thruk so I'm trying to set it up on my home network so I can learn it better.



    I set up a CentOS 6.6 machine. I've installed Nagios on it, and that's working fine. Now I'm trying to set up Thruk. I've managed to get livestatus and Thruk installed, but I'm stuck at getting it to actually work. In the documentation it shows that I'm supposed to add these two lines to the /usr/local/nagios/etc/nagios.cfg file:



    broker_module=/usr/local/lib/mk-livestatus/livestatus.o /var/lib/nagios/rw/live
    event_broker_options=-1


    the event_broker_options=-1 line already existed, so I added the other line above it. In some examples, it is shown as this instead:



    broker_module=/usr/local/lib/mk-livestatus/livestatus.o /tmp/live.sock
    event_broker_options=-1


    I've tried both, and I cannot seem to get this to work. I've done all the basics I can think of. I've reinstalled and updated all of the components (nagios, livestatus, thruk), I've reloaded and restarted all service associated a billion times. When the line I added is in there, Nagios starts when I tell it to start, but it then stops immediately. When I go into the /usr/local/nagios/var/nagios.log file, I see the following lines whenever I try to start Nagios and it fails:



    Error: Could not load module '/usr/local/lib/mk-livestatus/livestatus.o' -> /usr/local/lib/mk-livestatus/livestatus.o: undefined symbol: last_command_check
    Error: Failde to load module '/usr/local/lib/mk-livestatus/livestatus.o' .
    Error: Module loading failed. Aborting.


    If I comment out the line I added to the nagios.cfg file, Nagios will load and work properly, but Thruk still isn't working properly. If I load the Thruk page, I get this:



    No Backend available
    None of the configured Backends could be reached, please have a look at the logfile for detailed information and make sure the core is up and running.
    Details:
    home-net: ERROR: failed to open socket /tmp/live.sock: No such file or directory (/tmp/live.sock)


    It appears to me to be something wrong with livestatus, but I don't understand it well enough to fix it on my own and I'm having a lot of difficulty finding (or maybe understanding) the answer anywhere. From what I understood, I thought the nagios.cfg file was supposed to configure the live.sock file. Is that not correct? I'm doing my best, but I need some help.










    share|improve this question
















    bumped to the homepage by Community 2 days ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

















      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      I am extremely confused, and Google isn't really helping. Also, I'm kind of a Linux novice. I've taken a couple of classes, but that was all about how to configure things in a basic Linux setup. I'm now trying to learn how to set things up to actually use. At work we use Nagios/Thruk so I'm trying to set it up on my home network so I can learn it better.



      I set up a CentOS 6.6 machine. I've installed Nagios on it, and that's working fine. Now I'm trying to set up Thruk. I've managed to get livestatus and Thruk installed, but I'm stuck at getting it to actually work. In the documentation it shows that I'm supposed to add these two lines to the /usr/local/nagios/etc/nagios.cfg file:



      broker_module=/usr/local/lib/mk-livestatus/livestatus.o /var/lib/nagios/rw/live
      event_broker_options=-1


      the event_broker_options=-1 line already existed, so I added the other line above it. In some examples, it is shown as this instead:



      broker_module=/usr/local/lib/mk-livestatus/livestatus.o /tmp/live.sock
      event_broker_options=-1


      I've tried both, and I cannot seem to get this to work. I've done all the basics I can think of. I've reinstalled and updated all of the components (nagios, livestatus, thruk), I've reloaded and restarted all service associated a billion times. When the line I added is in there, Nagios starts when I tell it to start, but it then stops immediately. When I go into the /usr/local/nagios/var/nagios.log file, I see the following lines whenever I try to start Nagios and it fails:



      Error: Could not load module '/usr/local/lib/mk-livestatus/livestatus.o' -> /usr/local/lib/mk-livestatus/livestatus.o: undefined symbol: last_command_check
      Error: Failde to load module '/usr/local/lib/mk-livestatus/livestatus.o' .
      Error: Module loading failed. Aborting.


      If I comment out the line I added to the nagios.cfg file, Nagios will load and work properly, but Thruk still isn't working properly. If I load the Thruk page, I get this:



      No Backend available
      None of the configured Backends could be reached, please have a look at the logfile for detailed information and make sure the core is up and running.
      Details:
      home-net: ERROR: failed to open socket /tmp/live.sock: No such file or directory (/tmp/live.sock)


      It appears to me to be something wrong with livestatus, but I don't understand it well enough to fix it on my own and I'm having a lot of difficulty finding (or maybe understanding) the answer anywhere. From what I understood, I thought the nagios.cfg file was supposed to configure the live.sock file. Is that not correct? I'm doing my best, but I need some help.










      share|improve this question















      I am extremely confused, and Google isn't really helping. Also, I'm kind of a Linux novice. I've taken a couple of classes, but that was all about how to configure things in a basic Linux setup. I'm now trying to learn how to set things up to actually use. At work we use Nagios/Thruk so I'm trying to set it up on my home network so I can learn it better.



      I set up a CentOS 6.6 machine. I've installed Nagios on it, and that's working fine. Now I'm trying to set up Thruk. I've managed to get livestatus and Thruk installed, but I'm stuck at getting it to actually work. In the documentation it shows that I'm supposed to add these two lines to the /usr/local/nagios/etc/nagios.cfg file:



      broker_module=/usr/local/lib/mk-livestatus/livestatus.o /var/lib/nagios/rw/live
      event_broker_options=-1


      the event_broker_options=-1 line already existed, so I added the other line above it. In some examples, it is shown as this instead:



      broker_module=/usr/local/lib/mk-livestatus/livestatus.o /tmp/live.sock
      event_broker_options=-1


      I've tried both, and I cannot seem to get this to work. I've done all the basics I can think of. I've reinstalled and updated all of the components (nagios, livestatus, thruk), I've reloaded and restarted all service associated a billion times. When the line I added is in there, Nagios starts when I tell it to start, but it then stops immediately. When I go into the /usr/local/nagios/var/nagios.log file, I see the following lines whenever I try to start Nagios and it fails:



      Error: Could not load module '/usr/local/lib/mk-livestatus/livestatus.o' -> /usr/local/lib/mk-livestatus/livestatus.o: undefined symbol: last_command_check
      Error: Failde to load module '/usr/local/lib/mk-livestatus/livestatus.o' .
      Error: Module loading failed. Aborting.


      If I comment out the line I added to the nagios.cfg file, Nagios will load and work properly, but Thruk still isn't working properly. If I load the Thruk page, I get this:



      No Backend available
      None of the configured Backends could be reached, please have a look at the logfile for detailed information and make sure the core is up and running.
      Details:
      home-net: ERROR: failed to open socket /tmp/live.sock: No such file or directory (/tmp/live.sock)


      It appears to me to be something wrong with livestatus, but I don't understand it well enough to fix it on my own and I'm having a lot of difficulty finding (or maybe understanding) the answer anywhere. From what I understood, I thought the nagios.cfg file was supposed to configure the live.sock file. Is that not correct? I'm doing my best, but I need some help.







      centos nagios






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jun 13 '16 at 4:49









      Mongrel

      2,05331345




      2,05331345










      asked Dec 19 '14 at 1:22









      duzzy

      1114




      1114





      bumped to the homepage by Community 2 days ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 2 days ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          If you are using Nagios 4.X make sure to install livestatus from the sources using the option to make it compatible with Nagios 4.X
          -> https://mathias-kettner.de/checkmk_livestatus.html
          Else Nagios can't create the socket during launching and crashes.
          I am using exactly the same configuration you are, and still block on the next step : making thruk read the socket. If you manage it, please give details.






          share|improve this answer





















          • Welcome to Stack Exchange! We recommend that users include relevant parts of articles they link to rather than post links only. This prevents the answers from becoming unusable if links become obsolete. Please edit your post and include most important points, if that's possible, to improve your answer.
            – Erathiel
            Apr 20 '15 at 13:27











          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: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          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%2f174964%2fthruk-installation-failed-to-open-socket%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          0
          down vote













          If you are using Nagios 4.X make sure to install livestatus from the sources using the option to make it compatible with Nagios 4.X
          -> https://mathias-kettner.de/checkmk_livestatus.html
          Else Nagios can't create the socket during launching and crashes.
          I am using exactly the same configuration you are, and still block on the next step : making thruk read the socket. If you manage it, please give details.






          share|improve this answer





















          • Welcome to Stack Exchange! We recommend that users include relevant parts of articles they link to rather than post links only. This prevents the answers from becoming unusable if links become obsolete. Please edit your post and include most important points, if that's possible, to improve your answer.
            – Erathiel
            Apr 20 '15 at 13:27















          up vote
          0
          down vote













          If you are using Nagios 4.X make sure to install livestatus from the sources using the option to make it compatible with Nagios 4.X
          -> https://mathias-kettner.de/checkmk_livestatus.html
          Else Nagios can't create the socket during launching and crashes.
          I am using exactly the same configuration you are, and still block on the next step : making thruk read the socket. If you manage it, please give details.






          share|improve this answer





















          • Welcome to Stack Exchange! We recommend that users include relevant parts of articles they link to rather than post links only. This prevents the answers from becoming unusable if links become obsolete. Please edit your post and include most important points, if that's possible, to improve your answer.
            – Erathiel
            Apr 20 '15 at 13:27













          up vote
          0
          down vote










          up vote
          0
          down vote









          If you are using Nagios 4.X make sure to install livestatus from the sources using the option to make it compatible with Nagios 4.X
          -> https://mathias-kettner.de/checkmk_livestatus.html
          Else Nagios can't create the socket during launching and crashes.
          I am using exactly the same configuration you are, and still block on the next step : making thruk read the socket. If you manage it, please give details.






          share|improve this answer












          If you are using Nagios 4.X make sure to install livestatus from the sources using the option to make it compatible with Nagios 4.X
          -> https://mathias-kettner.de/checkmk_livestatus.html
          Else Nagios can't create the socket during launching and crashes.
          I am using exactly the same configuration you are, and still block on the next step : making thruk read the socket. If you manage it, please give details.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Apr 20 '15 at 13:15









          EChauve

          1




          1












          • Welcome to Stack Exchange! We recommend that users include relevant parts of articles they link to rather than post links only. This prevents the answers from becoming unusable if links become obsolete. Please edit your post and include most important points, if that's possible, to improve your answer.
            – Erathiel
            Apr 20 '15 at 13:27


















          • Welcome to Stack Exchange! We recommend that users include relevant parts of articles they link to rather than post links only. This prevents the answers from becoming unusable if links become obsolete. Please edit your post and include most important points, if that's possible, to improve your answer.
            – Erathiel
            Apr 20 '15 at 13:27
















          Welcome to Stack Exchange! We recommend that users include relevant parts of articles they link to rather than post links only. This prevents the answers from becoming unusable if links become obsolete. Please edit your post and include most important points, if that's possible, to improve your answer.
          – Erathiel
          Apr 20 '15 at 13:27




          Welcome to Stack Exchange! We recommend that users include relevant parts of articles they link to rather than post links only. This prevents the answers from becoming unusable if links become obsolete. Please edit your post and include most important points, if that's possible, to improve your answer.
          – Erathiel
          Apr 20 '15 at 13:27


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f174964%2fthruk-installation-failed-to-open-socket%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Accessing regular linux commands in Huawei's Dopra Linux

          Can't connect RFCOMM socket: Host is down

          Kernel panic - not syncing: Fatal Exception in Interrupt