snmpd service failed to start on Red Hat 6












0















I got the following error when I try to start the snmpd service:



service snmpd start



**Starting snmpd:                                            [FAILED]**


Log say:



2017-02-13T13:09:54.473284+01:00 bitwiz1 snmpd[3395]: getaddrinfo("bitwiz1-oam", NULL, ...): Temporary failure in name resolution

2017-02-13T13:09:54.473361+01:00 bitwiz1 snmpd[3395]: Error opening specified endpoint "bitwiz1-oam:161"

2017-02-13T13:09:54.473390+01:00 bitwiz1 snmpd[3395]: Server Exiting with code 1


Could someone help please?










share|improve this question
















bumped to the homepage by Community 1 hour ago


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
















  • So I'm supposing you tried to see if DNS resolution works on that machine, correct?

    – schaiba
    Feb 13 '17 at 12:44











  • Well... just solved my self... in hosts file I change 127.0.0.1 bitwiz1 to 192.168.65.120 bitwiz1, and then... BAM! Service start without problem!! :-)

    – Lucas Rey
    Feb 13 '17 at 13:20
















0















I got the following error when I try to start the snmpd service:



service snmpd start



**Starting snmpd:                                            [FAILED]**


Log say:



2017-02-13T13:09:54.473284+01:00 bitwiz1 snmpd[3395]: getaddrinfo("bitwiz1-oam", NULL, ...): Temporary failure in name resolution

2017-02-13T13:09:54.473361+01:00 bitwiz1 snmpd[3395]: Error opening specified endpoint "bitwiz1-oam:161"

2017-02-13T13:09:54.473390+01:00 bitwiz1 snmpd[3395]: Server Exiting with code 1


Could someone help please?










share|improve this question
















bumped to the homepage by Community 1 hour ago


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
















  • So I'm supposing you tried to see if DNS resolution works on that machine, correct?

    – schaiba
    Feb 13 '17 at 12:44











  • Well... just solved my self... in hosts file I change 127.0.0.1 bitwiz1 to 192.168.65.120 bitwiz1, and then... BAM! Service start without problem!! :-)

    – Lucas Rey
    Feb 13 '17 at 13:20














0












0








0








I got the following error when I try to start the snmpd service:



service snmpd start



**Starting snmpd:                                            [FAILED]**


Log say:



2017-02-13T13:09:54.473284+01:00 bitwiz1 snmpd[3395]: getaddrinfo("bitwiz1-oam", NULL, ...): Temporary failure in name resolution

2017-02-13T13:09:54.473361+01:00 bitwiz1 snmpd[3395]: Error opening specified endpoint "bitwiz1-oam:161"

2017-02-13T13:09:54.473390+01:00 bitwiz1 snmpd[3395]: Server Exiting with code 1


Could someone help please?










share|improve this question
















I got the following error when I try to start the snmpd service:



service snmpd start



**Starting snmpd:                                            [FAILED]**


Log say:



2017-02-13T13:09:54.473284+01:00 bitwiz1 snmpd[3395]: getaddrinfo("bitwiz1-oam", NULL, ...): Temporary failure in name resolution

2017-02-13T13:09:54.473361+01:00 bitwiz1 snmpd[3395]: Error opening specified endpoint "bitwiz1-oam:161"

2017-02-13T13:09:54.473390+01:00 bitwiz1 snmpd[3395]: Server Exiting with code 1


Could someone help please?







snmp






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 13 '17 at 12:56









Kevdog777

2,116123460




2,116123460










asked Feb 13 '17 at 12:40









Lucas ReyLucas Rey

1




1





bumped to the homepage by Community 1 hour 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 1 hour ago


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















  • So I'm supposing you tried to see if DNS resolution works on that machine, correct?

    – schaiba
    Feb 13 '17 at 12:44











  • Well... just solved my self... in hosts file I change 127.0.0.1 bitwiz1 to 192.168.65.120 bitwiz1, and then... BAM! Service start without problem!! :-)

    – Lucas Rey
    Feb 13 '17 at 13:20



















  • So I'm supposing you tried to see if DNS resolution works on that machine, correct?

    – schaiba
    Feb 13 '17 at 12:44











  • Well... just solved my self... in hosts file I change 127.0.0.1 bitwiz1 to 192.168.65.120 bitwiz1, and then... BAM! Service start without problem!! :-)

    – Lucas Rey
    Feb 13 '17 at 13:20

















So I'm supposing you tried to see if DNS resolution works on that machine, correct?

– schaiba
Feb 13 '17 at 12:44





So I'm supposing you tried to see if DNS resolution works on that machine, correct?

– schaiba
Feb 13 '17 at 12:44













Well... just solved my self... in hosts file I change 127.0.0.1 bitwiz1 to 192.168.65.120 bitwiz1, and then... BAM! Service start without problem!! :-)

– Lucas Rey
Feb 13 '17 at 13:20





Well... just solved my self... in hosts file I change 127.0.0.1 bitwiz1 to 192.168.65.120 bitwiz1, and then... BAM! Service start without problem!! :-)

– Lucas Rey
Feb 13 '17 at 13:20










1 Answer
1






active

oldest

votes


















0














Well... just solved my self... in hosts file I change 127.0.0.1 bitwiz1 to 192.168.65.120 bitwiz1, and then... BAM! Service start without problem!! :-)






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',
    autoActivateHeartbeat: false,
    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%2f344625%2fsnmpd-service-failed-to-start-on-red-hat-6%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









    0














    Well... just solved my self... in hosts file I change 127.0.0.1 bitwiz1 to 192.168.65.120 bitwiz1, and then... BAM! Service start without problem!! :-)






    share|improve this answer




























      0














      Well... just solved my self... in hosts file I change 127.0.0.1 bitwiz1 to 192.168.65.120 bitwiz1, and then... BAM! Service start without problem!! :-)






      share|improve this answer


























        0












        0








        0







        Well... just solved my self... in hosts file I change 127.0.0.1 bitwiz1 to 192.168.65.120 bitwiz1, and then... BAM! Service start without problem!! :-)






        share|improve this answer













        Well... just solved my self... in hosts file I change 127.0.0.1 bitwiz1 to 192.168.65.120 bitwiz1, and then... BAM! Service start without problem!! :-)







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Feb 13 '17 at 13:21









        Lucas ReyLucas Rey

        1




        1






























            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.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f344625%2fsnmpd-service-failed-to-start-on-red-hat-6%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

            CARDNET

            Boot-repair Failure: Unable to locate package grub-common:i386

            濃尾地震