System crash - strange chars in syslog

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
3
down vote

favorite












I have a small server which I use for testing and programming. Currently it runs Debian 9.4 stretch with 4.14.0-0.bpo.3-amd64 kernel.



Today I tried to connect through SSH but I couldn't then I tried to ping it and it was unreachable. Therefore I had to hard-restart it by unplugging power cable. Then I went to /var/log/syslog and I found a strange line containing exactly 6140 characters like the following



^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@



then nothing else until new log entries of system restart. This is actually the first time it happens.



Does someone know what could it be?










share|improve this question









New contributor




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















  • 1




    Well I wrote about this at askubuntu.com/a/1020373/43344 , for one. (-: Then there are unix.stackexchange.com/questions/227173 and unix.stackexchange.com/questions/237321 …
    – JdeBP
    2 hours ago






  • 1




    @JdeBP I prefer your first answer/link, that is indeed it. Odd has a question with 1500+ visits you have not got a single vote, +1.
    – Rui F Ribeiro
    1 hour ago














up vote
3
down vote

favorite












I have a small server which I use for testing and programming. Currently it runs Debian 9.4 stretch with 4.14.0-0.bpo.3-amd64 kernel.



Today I tried to connect through SSH but I couldn't then I tried to ping it and it was unreachable. Therefore I had to hard-restart it by unplugging power cable. Then I went to /var/log/syslog and I found a strange line containing exactly 6140 characters like the following



^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@



then nothing else until new log entries of system restart. This is actually the first time it happens.



Does someone know what could it be?










share|improve this question









New contributor




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















  • 1




    Well I wrote about this at askubuntu.com/a/1020373/43344 , for one. (-: Then there are unix.stackexchange.com/questions/227173 and unix.stackexchange.com/questions/237321 …
    – JdeBP
    2 hours ago






  • 1




    @JdeBP I prefer your first answer/link, that is indeed it. Odd has a question with 1500+ visits you have not got a single vote, +1.
    – Rui F Ribeiro
    1 hour ago












up vote
3
down vote

favorite









up vote
3
down vote

favorite











I have a small server which I use for testing and programming. Currently it runs Debian 9.4 stretch with 4.14.0-0.bpo.3-amd64 kernel.



Today I tried to connect through SSH but I couldn't then I tried to ping it and it was unreachable. Therefore I had to hard-restart it by unplugging power cable. Then I went to /var/log/syslog and I found a strange line containing exactly 6140 characters like the following



^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@



then nothing else until new log entries of system restart. This is actually the first time it happens.



Does someone know what could it be?










share|improve this question









New contributor




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











I have a small server which I use for testing and programming. Currently it runs Debian 9.4 stretch with 4.14.0-0.bpo.3-amd64 kernel.



Today I tried to connect through SSH but I couldn't then I tried to ping it and it was unreachable. Therefore I had to hard-restart it by unplugging power cable. Then I went to /var/log/syslog and I found a strange line containing exactly 6140 characters like the following



^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@



then nothing else until new log entries of system restart. This is actually the first time it happens.



Does someone know what could it be?







debian logs






share|improve this question









New contributor




DrKey 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 question









New contributor




DrKey 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 question




share|improve this question








edited 2 hours ago









Jeff Schaller

34.4k951114




34.4k951114






New contributor




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









asked 2 hours ago









DrKey

1161




1161




New contributor




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





New contributor





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






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







  • 1




    Well I wrote about this at askubuntu.com/a/1020373/43344 , for one. (-: Then there are unix.stackexchange.com/questions/227173 and unix.stackexchange.com/questions/237321 …
    – JdeBP
    2 hours ago






  • 1




    @JdeBP I prefer your first answer/link, that is indeed it. Odd has a question with 1500+ visits you have not got a single vote, +1.
    – Rui F Ribeiro
    1 hour ago












  • 1




    Well I wrote about this at askubuntu.com/a/1020373/43344 , for one. (-: Then there are unix.stackexchange.com/questions/227173 and unix.stackexchange.com/questions/237321 …
    – JdeBP
    2 hours ago






  • 1




    @JdeBP I prefer your first answer/link, that is indeed it. Odd has a question with 1500+ visits you have not got a single vote, +1.
    – Rui F Ribeiro
    1 hour ago







1




1




Well I wrote about this at askubuntu.com/a/1020373/43344 , for one. (-: Then there are unix.stackexchange.com/questions/227173 and unix.stackexchange.com/questions/237321 …
– JdeBP
2 hours ago




Well I wrote about this at askubuntu.com/a/1020373/43344 , for one. (-: Then there are unix.stackexchange.com/questions/227173 and unix.stackexchange.com/questions/237321 …
– JdeBP
2 hours ago




1




1




@JdeBP I prefer your first answer/link, that is indeed it. Odd has a question with 1500+ visits you have not got a single vote, +1.
– Rui F Ribeiro
1 hour ago




@JdeBP I prefer your first answer/link, that is indeed it. Odd has a question with 1500+ visits you have not got a single vote, +1.
– Rui F Ribeiro
1 hour ago










1 Answer
1






active

oldest

votes

















up vote
5
down vote













That is corruption of the filesystem/syslog writing.



The crash caught the system mid-writing to the syslog file, and that is the end result. Already have seen it several times over the years, in Linux VMs and a couple more times in Raspberries and Banana Pis.



Nothing to obsess about or lose time to investigate a lot why you have this for a one-time event. I would be more worried at finding out why it crashed, especially if it is a regular event.



PS getting into anecdotal territory, last time I had this happening regularly in a Banana Pi R1, I managed to trace the cause to a (faulty) realtek wifi chipset.






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
    );



    );






    DrKey is a new contributor. Be nice, and check out our Code of Conduct.









     

    draft saved


    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f477537%2fsystem-crash-strange-chars-in-syslog%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
    5
    down vote













    That is corruption of the filesystem/syslog writing.



    The crash caught the system mid-writing to the syslog file, and that is the end result. Already have seen it several times over the years, in Linux VMs and a couple more times in Raspberries and Banana Pis.



    Nothing to obsess about or lose time to investigate a lot why you have this for a one-time event. I would be more worried at finding out why it crashed, especially if it is a regular event.



    PS getting into anecdotal territory, last time I had this happening regularly in a Banana Pi R1, I managed to trace the cause to a (faulty) realtek wifi chipset.






    share|improve this answer


























      up vote
      5
      down vote













      That is corruption of the filesystem/syslog writing.



      The crash caught the system mid-writing to the syslog file, and that is the end result. Already have seen it several times over the years, in Linux VMs and a couple more times in Raspberries and Banana Pis.



      Nothing to obsess about or lose time to investigate a lot why you have this for a one-time event. I would be more worried at finding out why it crashed, especially if it is a regular event.



      PS getting into anecdotal territory, last time I had this happening regularly in a Banana Pi R1, I managed to trace the cause to a (faulty) realtek wifi chipset.






      share|improve this answer
























        up vote
        5
        down vote










        up vote
        5
        down vote









        That is corruption of the filesystem/syslog writing.



        The crash caught the system mid-writing to the syslog file, and that is the end result. Already have seen it several times over the years, in Linux VMs and a couple more times in Raspberries and Banana Pis.



        Nothing to obsess about or lose time to investigate a lot why you have this for a one-time event. I would be more worried at finding out why it crashed, especially if it is a regular event.



        PS getting into anecdotal territory, last time I had this happening regularly in a Banana Pi R1, I managed to trace the cause to a (faulty) realtek wifi chipset.






        share|improve this answer














        That is corruption of the filesystem/syslog writing.



        The crash caught the system mid-writing to the syslog file, and that is the end result. Already have seen it several times over the years, in Linux VMs and a couple more times in Raspberries and Banana Pis.



        Nothing to obsess about or lose time to investigate a lot why you have this for a one-time event. I would be more worried at finding out why it crashed, especially if it is a regular event.



        PS getting into anecdotal territory, last time I had this happening regularly in a Banana Pi R1, I managed to trace the cause to a (faulty) realtek wifi chipset.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited 43 mins ago

























        answered 2 hours ago









        Rui F Ribeiro

        37.4k1374118




        37.4k1374118




















            DrKey is a new contributor. Be nice, and check out our Code of Conduct.









             

            draft saved


            draft discarded


















            DrKey is a new contributor. Be nice, and check out our Code of Conduct.












            DrKey is a new contributor. Be nice, and check out our Code of Conduct.











            DrKey is a new contributor. Be nice, and check out our Code of Conduct.













             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f477537%2fsystem-crash-strange-chars-in-syslog%23new-answer', 'question_page');

            );

            Post as a guest













































































            Comments

            Popular posts from this blog

            What does second last employer means? [closed]

            Installing NextGIS Connect into QGIS 3?

            One-line joke