systemd[1]: realmd.service start operation timed out. Terminating












0















I am trying to put my CentOS 7 in the domain, I put some others and it was normal, but this machine is not working.



follows the configuration of the machine:



Icon name: computer-vm
Chassis: vm
Virtualization: microsoft
Operating System: CentOS Linux 7 (Core)
CPE OS Name: cpe: / o: centos: centos: 7
Kernel: Linux 3.10.0-514.26.2.el7.x86_64
Architecture: x86-64


I followed the how to put CentOs in the domain when I realized that the realmd service itself is not working.



Follow the "journalctl -xe" log:



- Subject: Unit realmd.service has started start-up
- Unit realmd.service has begun starting up.
Jan 04 17:25:27 SERVER realmd [25333]: Loaded settings from: /usr/lib64/realmd/realmd-defaults.conf / usr / lib64 / realm
/realmd-distro.conf /etc/realmd.conf
Jan 04 17:25:27 SERVER realmd [25333]: holding daemon: startup
Jan 04 17:25:27 SERVER realmd [25333]: starting service
Jan 04 17:25:27 SERVER realmd [25333]: connected to bus
Jan 04 17:25:27 SERVER realmd [25333]: released daemon: startup
Jan 04 17:25:27 SERVER realmd [25333]: could not claim service name on DBus bus: org.freedesktop.realmd
Jan 04 17:25:27 SERVER realmd [25333]: could not claim service name on DBus bus: org.freedesktop.realmd
Jan 04 17:26:57 SERVER systemd [1]: realmd.service start operation timed out. Terminating.
Jan 04 17:26:57 SERVER realmd [25333]: stopping service
- Subject: Unit realmd.service has failed
- Unit realmd.service has failed.
Jan 04 17:26:57 SERVER systemd [1]: Unit realmd.service entered failed state.
Jan 04 17:26:57 SERVER systemd [1]: realmd.service failed.


Has anyone ever experienced this?










share|improve this question

























  • The realm list command will list your Microsoft Domain?

    – nwildner
    Jan 7 at 16:47











  • The problem is that the service itself is not "up": $ systemctl status realmd ● realmd.service - Realm and Domain Configuration Loaded: loaded (/usr/lib/systemd/system/realmd.service; static; vendor preset: disabled) Active: failed (Result: timeout) since Mon 2019-01-07 09:31:10 -02; 5h 40min ago Docs: man:realm(8) Process: 50010 ExecStart=/usr/lib64/realmd/realmd (code=exited, status=0/SUCCESS) Main PID: 50010 (code=exited, status=0/SUCCESS)

    – Douglas Ribeiro
    Jan 7 at 17:17













  • I know, and this seems to be a timeout while searching the domain. I just wanted to make sure if there isn't any domain searching issue by suggesting you to run realm list. Could you do that?

    – nwildner
    Jan 7 at 17:56











  • I understood, sorry the delay of the answer, I can execute yes, it follows the result: # realm list realm: Could not connect to realm service: Error calling StartServiceByName for org.freedesktop.realmd: Timeout was reached

    – Douglas Ribeiro
    Jan 8 at 10:20











  • That's weird. And what about selinux. Could you please check at /var/log/audit/audit.log if there is any avc on realm and realmd related programs?

    – nwildner
    Jan 8 at 12:06


















0















I am trying to put my CentOS 7 in the domain, I put some others and it was normal, but this machine is not working.



follows the configuration of the machine:



Icon name: computer-vm
Chassis: vm
Virtualization: microsoft
Operating System: CentOS Linux 7 (Core)
CPE OS Name: cpe: / o: centos: centos: 7
Kernel: Linux 3.10.0-514.26.2.el7.x86_64
Architecture: x86-64


I followed the how to put CentOs in the domain when I realized that the realmd service itself is not working.



Follow the "journalctl -xe" log:



- Subject: Unit realmd.service has started start-up
- Unit realmd.service has begun starting up.
Jan 04 17:25:27 SERVER realmd [25333]: Loaded settings from: /usr/lib64/realmd/realmd-defaults.conf / usr / lib64 / realm
/realmd-distro.conf /etc/realmd.conf
Jan 04 17:25:27 SERVER realmd [25333]: holding daemon: startup
Jan 04 17:25:27 SERVER realmd [25333]: starting service
Jan 04 17:25:27 SERVER realmd [25333]: connected to bus
Jan 04 17:25:27 SERVER realmd [25333]: released daemon: startup
Jan 04 17:25:27 SERVER realmd [25333]: could not claim service name on DBus bus: org.freedesktop.realmd
Jan 04 17:25:27 SERVER realmd [25333]: could not claim service name on DBus bus: org.freedesktop.realmd
Jan 04 17:26:57 SERVER systemd [1]: realmd.service start operation timed out. Terminating.
Jan 04 17:26:57 SERVER realmd [25333]: stopping service
- Subject: Unit realmd.service has failed
- Unit realmd.service has failed.
Jan 04 17:26:57 SERVER systemd [1]: Unit realmd.service entered failed state.
Jan 04 17:26:57 SERVER systemd [1]: realmd.service failed.


Has anyone ever experienced this?










share|improve this question

























  • The realm list command will list your Microsoft Domain?

    – nwildner
    Jan 7 at 16:47











  • The problem is that the service itself is not "up": $ systemctl status realmd ● realmd.service - Realm and Domain Configuration Loaded: loaded (/usr/lib/systemd/system/realmd.service; static; vendor preset: disabled) Active: failed (Result: timeout) since Mon 2019-01-07 09:31:10 -02; 5h 40min ago Docs: man:realm(8) Process: 50010 ExecStart=/usr/lib64/realmd/realmd (code=exited, status=0/SUCCESS) Main PID: 50010 (code=exited, status=0/SUCCESS)

    – Douglas Ribeiro
    Jan 7 at 17:17













  • I know, and this seems to be a timeout while searching the domain. I just wanted to make sure if there isn't any domain searching issue by suggesting you to run realm list. Could you do that?

    – nwildner
    Jan 7 at 17:56











  • I understood, sorry the delay of the answer, I can execute yes, it follows the result: # realm list realm: Could not connect to realm service: Error calling StartServiceByName for org.freedesktop.realmd: Timeout was reached

    – Douglas Ribeiro
    Jan 8 at 10:20











  • That's weird. And what about selinux. Could you please check at /var/log/audit/audit.log if there is any avc on realm and realmd related programs?

    – nwildner
    Jan 8 at 12:06
















0












0








0








I am trying to put my CentOS 7 in the domain, I put some others and it was normal, but this machine is not working.



follows the configuration of the machine:



Icon name: computer-vm
Chassis: vm
Virtualization: microsoft
Operating System: CentOS Linux 7 (Core)
CPE OS Name: cpe: / o: centos: centos: 7
Kernel: Linux 3.10.0-514.26.2.el7.x86_64
Architecture: x86-64


I followed the how to put CentOs in the domain when I realized that the realmd service itself is not working.



Follow the "journalctl -xe" log:



- Subject: Unit realmd.service has started start-up
- Unit realmd.service has begun starting up.
Jan 04 17:25:27 SERVER realmd [25333]: Loaded settings from: /usr/lib64/realmd/realmd-defaults.conf / usr / lib64 / realm
/realmd-distro.conf /etc/realmd.conf
Jan 04 17:25:27 SERVER realmd [25333]: holding daemon: startup
Jan 04 17:25:27 SERVER realmd [25333]: starting service
Jan 04 17:25:27 SERVER realmd [25333]: connected to bus
Jan 04 17:25:27 SERVER realmd [25333]: released daemon: startup
Jan 04 17:25:27 SERVER realmd [25333]: could not claim service name on DBus bus: org.freedesktop.realmd
Jan 04 17:25:27 SERVER realmd [25333]: could not claim service name on DBus bus: org.freedesktop.realmd
Jan 04 17:26:57 SERVER systemd [1]: realmd.service start operation timed out. Terminating.
Jan 04 17:26:57 SERVER realmd [25333]: stopping service
- Subject: Unit realmd.service has failed
- Unit realmd.service has failed.
Jan 04 17:26:57 SERVER systemd [1]: Unit realmd.service entered failed state.
Jan 04 17:26:57 SERVER systemd [1]: realmd.service failed.


Has anyone ever experienced this?










share|improve this question
















I am trying to put my CentOS 7 in the domain, I put some others and it was normal, but this machine is not working.



follows the configuration of the machine:



Icon name: computer-vm
Chassis: vm
Virtualization: microsoft
Operating System: CentOS Linux 7 (Core)
CPE OS Name: cpe: / o: centos: centos: 7
Kernel: Linux 3.10.0-514.26.2.el7.x86_64
Architecture: x86-64


I followed the how to put CentOs in the domain when I realized that the realmd service itself is not working.



Follow the "journalctl -xe" log:



- Subject: Unit realmd.service has started start-up
- Unit realmd.service has begun starting up.
Jan 04 17:25:27 SERVER realmd [25333]: Loaded settings from: /usr/lib64/realmd/realmd-defaults.conf / usr / lib64 / realm
/realmd-distro.conf /etc/realmd.conf
Jan 04 17:25:27 SERVER realmd [25333]: holding daemon: startup
Jan 04 17:25:27 SERVER realmd [25333]: starting service
Jan 04 17:25:27 SERVER realmd [25333]: connected to bus
Jan 04 17:25:27 SERVER realmd [25333]: released daemon: startup
Jan 04 17:25:27 SERVER realmd [25333]: could not claim service name on DBus bus: org.freedesktop.realmd
Jan 04 17:25:27 SERVER realmd [25333]: could not claim service name on DBus bus: org.freedesktop.realmd
Jan 04 17:26:57 SERVER systemd [1]: realmd.service start operation timed out. Terminating.
Jan 04 17:26:57 SERVER realmd [25333]: stopping service
- Subject: Unit realmd.service has failed
- Unit realmd.service has failed.
Jan 04 17:26:57 SERVER systemd [1]: Unit realmd.service entered failed state.
Jan 04 17:26:57 SERVER systemd [1]: realmd.service failed.


Has anyone ever experienced this?







centos systemd






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 7 at 19:26









filbranden

7,4002837




7,4002837










asked Jan 7 at 15:29









Douglas RibeiroDouglas Ribeiro

13




13













  • The realm list command will list your Microsoft Domain?

    – nwildner
    Jan 7 at 16:47











  • The problem is that the service itself is not "up": $ systemctl status realmd ● realmd.service - Realm and Domain Configuration Loaded: loaded (/usr/lib/systemd/system/realmd.service; static; vendor preset: disabled) Active: failed (Result: timeout) since Mon 2019-01-07 09:31:10 -02; 5h 40min ago Docs: man:realm(8) Process: 50010 ExecStart=/usr/lib64/realmd/realmd (code=exited, status=0/SUCCESS) Main PID: 50010 (code=exited, status=0/SUCCESS)

    – Douglas Ribeiro
    Jan 7 at 17:17













  • I know, and this seems to be a timeout while searching the domain. I just wanted to make sure if there isn't any domain searching issue by suggesting you to run realm list. Could you do that?

    – nwildner
    Jan 7 at 17:56











  • I understood, sorry the delay of the answer, I can execute yes, it follows the result: # realm list realm: Could not connect to realm service: Error calling StartServiceByName for org.freedesktop.realmd: Timeout was reached

    – Douglas Ribeiro
    Jan 8 at 10:20











  • That's weird. And what about selinux. Could you please check at /var/log/audit/audit.log if there is any avc on realm and realmd related programs?

    – nwildner
    Jan 8 at 12:06





















  • The realm list command will list your Microsoft Domain?

    – nwildner
    Jan 7 at 16:47











  • The problem is that the service itself is not "up": $ systemctl status realmd ● realmd.service - Realm and Domain Configuration Loaded: loaded (/usr/lib/systemd/system/realmd.service; static; vendor preset: disabled) Active: failed (Result: timeout) since Mon 2019-01-07 09:31:10 -02; 5h 40min ago Docs: man:realm(8) Process: 50010 ExecStart=/usr/lib64/realmd/realmd (code=exited, status=0/SUCCESS) Main PID: 50010 (code=exited, status=0/SUCCESS)

    – Douglas Ribeiro
    Jan 7 at 17:17













  • I know, and this seems to be a timeout while searching the domain. I just wanted to make sure if there isn't any domain searching issue by suggesting you to run realm list. Could you do that?

    – nwildner
    Jan 7 at 17:56











  • I understood, sorry the delay of the answer, I can execute yes, it follows the result: # realm list realm: Could not connect to realm service: Error calling StartServiceByName for org.freedesktop.realmd: Timeout was reached

    – Douglas Ribeiro
    Jan 8 at 10:20











  • That's weird. And what about selinux. Could you please check at /var/log/audit/audit.log if there is any avc on realm and realmd related programs?

    – nwildner
    Jan 8 at 12:06



















The realm list command will list your Microsoft Domain?

– nwildner
Jan 7 at 16:47





The realm list command will list your Microsoft Domain?

– nwildner
Jan 7 at 16:47













The problem is that the service itself is not "up": $ systemctl status realmd ● realmd.service - Realm and Domain Configuration Loaded: loaded (/usr/lib/systemd/system/realmd.service; static; vendor preset: disabled) Active: failed (Result: timeout) since Mon 2019-01-07 09:31:10 -02; 5h 40min ago Docs: man:realm(8) Process: 50010 ExecStart=/usr/lib64/realmd/realmd (code=exited, status=0/SUCCESS) Main PID: 50010 (code=exited, status=0/SUCCESS)

– Douglas Ribeiro
Jan 7 at 17:17







The problem is that the service itself is not "up": $ systemctl status realmd ● realmd.service - Realm and Domain Configuration Loaded: loaded (/usr/lib/systemd/system/realmd.service; static; vendor preset: disabled) Active: failed (Result: timeout) since Mon 2019-01-07 09:31:10 -02; 5h 40min ago Docs: man:realm(8) Process: 50010 ExecStart=/usr/lib64/realmd/realmd (code=exited, status=0/SUCCESS) Main PID: 50010 (code=exited, status=0/SUCCESS)

– Douglas Ribeiro
Jan 7 at 17:17















I know, and this seems to be a timeout while searching the domain. I just wanted to make sure if there isn't any domain searching issue by suggesting you to run realm list. Could you do that?

– nwildner
Jan 7 at 17:56





I know, and this seems to be a timeout while searching the domain. I just wanted to make sure if there isn't any domain searching issue by suggesting you to run realm list. Could you do that?

– nwildner
Jan 7 at 17:56













I understood, sorry the delay of the answer, I can execute yes, it follows the result: # realm list realm: Could not connect to realm service: Error calling StartServiceByName for org.freedesktop.realmd: Timeout was reached

– Douglas Ribeiro
Jan 8 at 10:20





I understood, sorry the delay of the answer, I can execute yes, it follows the result: # realm list realm: Could not connect to realm service: Error calling StartServiceByName for org.freedesktop.realmd: Timeout was reached

– Douglas Ribeiro
Jan 8 at 10:20













That's weird. And what about selinux. Could you please check at /var/log/audit/audit.log if there is any avc on realm and realmd related programs?

– nwildner
Jan 8 at 12:06







That's weird. And what about selinux. Could you please check at /var/log/audit/audit.log if there is any avc on realm and realmd related programs?

– nwildner
Jan 8 at 12:06












1 Answer
1






active

oldest

votes


















0














@nwildner thank you for your attention but I managed to find the solution on the problem reported above in the CentOS forum, it was only to reboot the machine! Follow the link.



https://www.centos.org/forums/viewtopic.php?f=47&t=69338&p=291404#p291404






share|improve this answer








New contributor




Douglas Ribeiro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















    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%2f493020%2fsystemd1-realmd-service-start-operation-timed-out-terminating%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














    @nwildner thank you for your attention but I managed to find the solution on the problem reported above in the CentOS forum, it was only to reboot the machine! Follow the link.



    https://www.centos.org/forums/viewtopic.php?f=47&t=69338&p=291404#p291404






    share|improve this answer








    New contributor




    Douglas Ribeiro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.

























      0














      @nwildner thank you for your attention but I managed to find the solution on the problem reported above in the CentOS forum, it was only to reboot the machine! Follow the link.



      https://www.centos.org/forums/viewtopic.php?f=47&t=69338&p=291404#p291404






      share|improve this answer








      New contributor




      Douglas Ribeiro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.























        0












        0








        0







        @nwildner thank you for your attention but I managed to find the solution on the problem reported above in the CentOS forum, it was only to reboot the machine! Follow the link.



        https://www.centos.org/forums/viewtopic.php?f=47&t=69338&p=291404#p291404






        share|improve this answer








        New contributor




        Douglas Ribeiro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.










        @nwildner thank you for your attention but I managed to find the solution on the problem reported above in the CentOS forum, it was only to reboot the machine! Follow the link.



        https://www.centos.org/forums/viewtopic.php?f=47&t=69338&p=291404#p291404







        share|improve this answer








        New contributor




        Douglas Ribeiro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        share|improve this answer



        share|improve this answer






        New contributor




        Douglas Ribeiro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        answered Jan 10 at 9:24









        Douglas RibeiroDouglas Ribeiro

        13




        13




        New contributor




        Douglas Ribeiro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.





        New contributor





        Douglas Ribeiro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






        Douglas Ribeiro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






























            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%2f493020%2fsystemd1-realmd-service-start-operation-timed-out-terminating%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

            Morgemoulin

            Scott Moir

            Souastre