Syslog filled with “@â€-sign, Server not reachable
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
today something happend to my ubuntu 16.04 server running plesk onxy.
the server was unreachable, so i did a hard reset.
after looking into /var/log/syslog, something strange was shown:
syslog-output
kern.log output
Did anyone else has seen this before? The hard-reset of the server was on 23:23:51, so the Kernel Messages seems to be "normal". But the really strange party are those @-signs and there was no log during 23:06 and 23:23.
Any idea what happend on my server?
if you need more information feel free to ask me!
Thanks in advice
16.04 server syslog
asked Feb 23 at 22:50
Marcwa19197
11
add a comment |Â
up vote
0
down vote
favorite
today something happend to my ubuntu 16.04 server running plesk onxy.
the server was unreachable, so i did a hard reset.
after looking into /var/log/syslog, something strange was shown:
syslog-output
kern.log output
Did anyone else has seen this before? The hard-reset of the server was on 23:23:51, so the Kernel Messages seems to be "normal". But the really strange party are those @-signs and there was no log during 23:06 and 23:23.
Any idea what happend on my server?
if you need more information feel free to ask me!
Thanks in advice
16.04 server syslog
asked Feb 23 at 22:50
Marcwa19197
11
^@represents a null byte. See en.wikipedia.org/wiki/Caret_notation
– wjandrea
Feb 23 at 23:15
This happens a lot in the case of hard power off. Usually represents corruption/half written lines. I'd examine/var/log/syslog, and also/var/log/kern.log. The null bytes by themselves really don't tell you anything unfortunately. :/
– dpb
Feb 23 at 23:23
hi, i added the kern.log file. Can this be cause by my veeam backup?
– Marcwa19197
Feb 23 at 23:28
if the answer here is useful for you. unix.stackexchange.com/a/320977
– Dagim Sisay
Mar 23 at 18:21
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
today something happend to my ubuntu 16.04 server running plesk onxy.
the server was unreachable, so i did a hard reset.
after looking into /var/log/syslog, something strange was shown:
syslog-output
kern.log output
Did anyone else has seen this before? The hard-reset of the server was on 23:23:51, so the Kernel Messages seems to be "normal". But the really strange party are those @-signs and there was no log during 23:06 and 23:23.
Any idea what happend on my server?
if you need more information feel free to ask me!
Thanks in advice
16.04 server syslog
asked Feb 23 at 22:50
Marcwa19197
11
today something happend to my ubuntu 16.04 server running plesk onxy.
the server was unreachable, so i did a hard reset.
after looking into /var/log/syslog, something strange was shown:
syslog-output
kern.log output
Did anyone else has seen this before? The hard-reset of the server was on 23:23:51, so the Kernel Messages seems to be "normal". But the really strange party are those @-signs and there was no log during 23:06 and 23:23.
Any idea what happend on my server?
if you need more information feel free to ask me!
Thanks in advice
16.04 server syslog
16.04 server syslog
asked Feb 23 at 22:50
Marcwa19197
11
asked Feb 23 at 22:50
Marcwa19197
11
edited Feb 23 at 23:27
asked Feb 23 at 22:50
Marcwa19197
11
asked Feb 23 at 22:50
Marcwa19197
11
asked Feb 23 at 22:50
Marcwa19197
11
11
^@represents a null byte. See en.wikipedia.org/wiki/Caret_notation
– wjandrea
Feb 23 at 23:15
This happens a lot in the case of hard power off. Usually represents corruption/half written lines. I'd examine/var/log/syslog, and also/var/log/kern.log. The null bytes by themselves really don't tell you anything unfortunately. :/
– dpb
Feb 23 at 23:23
hi, i added the kern.log file. Can this be cause by my veeam backup?
– Marcwa19197
Feb 23 at 23:28
if the answer here is useful for you. unix.stackexchange.com/a/320977
– Dagim Sisay
Mar 23 at 18:21
add a comment |Â
^@represents a null byte. See en.wikipedia.org/wiki/Caret_notation
– wjandrea
Feb 23 at 23:15
This happens a lot in the case of hard power off. Usually represents corruption/half written lines. I'd examine/var/log/syslog, and also/var/log/kern.log. The null bytes by themselves really don't tell you anything unfortunately. :/
– dpb
Feb 23 at 23:23
hi, i added the kern.log file. Can this be cause by my veeam backup?
– Marcwa19197
Feb 23 at 23:28
if the answer here is useful for you. unix.stackexchange.com/a/320977
– Dagim Sisay
Mar 23 at 18:21
^@ represents a null byte. See en.wikipedia.org/wiki/Caret_notation– wjandrea
Feb 23 at 23:15
^@ represents a null byte. See en.wikipedia.org/wiki/Caret_notation– wjandrea
Feb 23 at 23:15
This happens a lot in the case of hard power off. Usually represents corruption/half written lines. I'd examine
/var/log/syslog, and also /var/log/kern.log. The null bytes by themselves really don't tell you anything unfortunately. :/– dpb
Feb 23 at 23:23
This happens a lot in the case of hard power off. Usually represents corruption/half written lines. I'd examine
/var/log/syslog, and also /var/log/kern.log. The null bytes by themselves really don't tell you anything unfortunately. :/– dpb
Feb 23 at 23:23
hi, i added the kern.log file. Can this be cause by my veeam backup?
– Marcwa19197
Feb 23 at 23:28
hi, i added the kern.log file. Can this be cause by my veeam backup?
– Marcwa19197
Feb 23 at 23:28
if the answer here is useful for you. unix.stackexchange.com/a/320977
– Dagim Sisay
Mar 23 at 18:21
if the answer here is useful for you. unix.stackexchange.com/a/320977
– Dagim Sisay
Mar 23 at 18:21
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1009178%2fsyslog-filled-with-sign-server-not-reachable%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
^@represents a null byte. See en.wikipedia.org/wiki/Caret_notation– wjandrea
Feb 23 at 23:15
This happens a lot in the case of hard power off. Usually represents corruption/half written lines. I'd examine
/var/log/syslog, and also/var/log/kern.log. The null bytes by themselves really don't tell you anything unfortunately. :/– dpb
Feb 23 at 23:23
hi, i added the kern.log file. Can this be cause by my veeam backup?
– Marcwa19197
Feb 23 at 23:28
if the answer here is useful for you. unix.stackexchange.com/a/320977
– Dagim Sisay
Mar 23 at 18:21