auth.log: systemd Log Spam, suspend.target is masked












0















With my server I have noticed that systemd is spamming the auth.log file with GBs of this:



Jan 29 15:40:14 server systemd-logind[438]: Suspending...
Jan 29 15:40:14 server systemd-logind[438]: Failed to execute operation: Unit suspend.target is masked.


Any idea how I can fix this? It is a laptop with suspension disabled and the lid closed. After a few days of the spam the disk is full and requires me to delete the files and reboot.










share|improve this question













migrated from serverfault.com 33 mins ago


This question came from our site for system and network administrators.























    0















    With my server I have noticed that systemd is spamming the auth.log file with GBs of this:



    Jan 29 15:40:14 server systemd-logind[438]: Suspending...
    Jan 29 15:40:14 server systemd-logind[438]: Failed to execute operation: Unit suspend.target is masked.


    Any idea how I can fix this? It is a laptop with suspension disabled and the lid closed. After a few days of the spam the disk is full and requires me to delete the files and reboot.










    share|improve this question













    migrated from serverfault.com 33 mins ago


    This question came from our site for system and network administrators.





















      0












      0








      0








      With my server I have noticed that systemd is spamming the auth.log file with GBs of this:



      Jan 29 15:40:14 server systemd-logind[438]: Suspending...
      Jan 29 15:40:14 server systemd-logind[438]: Failed to execute operation: Unit suspend.target is masked.


      Any idea how I can fix this? It is a laptop with suspension disabled and the lid closed. After a few days of the spam the disk is full and requires me to delete the files and reboot.










      share|improve this question














      With my server I have noticed that systemd is spamming the auth.log file with GBs of this:



      Jan 29 15:40:14 server systemd-logind[438]: Suspending...
      Jan 29 15:40:14 server systemd-logind[438]: Failed to execute operation: Unit suspend.target is masked.


      Any idea how I can fix this? It is a laptop with suspension disabled and the lid closed. After a few days of the spam the disk is full and requires me to delete the files and reboot.







      systemd






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 29 at 21:43









      gudenaugudenau

      33




      33




      migrated from serverfault.com 33 mins ago


      This question came from our site for system and network administrators.









      migrated from serverfault.com 33 mins ago


      This question came from our site for system and network administrators.
























          1 Answer
          1






          active

          oldest

          votes


















          1














          There is a setting in /etc/systemd/logind.conf that tells systemd-logind how to handle the laptop lid switch event. Try setting HandleLidSwitch=ignore and restart systemd-logind.






          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%2f506629%2fauth-log-systemd-log-spam-suspend-target-is-masked%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









            1














            There is a setting in /etc/systemd/logind.conf that tells systemd-logind how to handle the laptop lid switch event. Try setting HandleLidSwitch=ignore and restart systemd-logind.






            share|improve this answer




























              1














              There is a setting in /etc/systemd/logind.conf that tells systemd-logind how to handle the laptop lid switch event. Try setting HandleLidSwitch=ignore and restart systemd-logind.






              share|improve this answer


























                1












                1








                1







                There is a setting in /etc/systemd/logind.conf that tells systemd-logind how to handle the laptop lid switch event. Try setting HandleLidSwitch=ignore and restart systemd-logind.






                share|improve this answer













                There is a setting in /etc/systemd/logind.conf that tells systemd-logind how to handle the laptop lid switch event. Try setting HandleLidSwitch=ignore and restart systemd-logind.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered 3 hours ago







                Cole White





































                    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%2f506629%2fauth-log-systemd-log-spam-suspend-target-is-masked%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

                    濃尾地震