![]() ![]() The example file is treated as binary because it doesn't fit the current locale (probably some UTF locale), not because it has null bytes. However, that's not the case with the example input. and the binary-ness is due to null bytes.the -I/ -binary-files=without-match options are given.Variables), or null input bytes when the -z ( -null-data) That are improperly encoded for the current locale (see Environment Non-text bytes indicate binary data these are either output bytes However, grep also considers other data as indicating binary files: It assumes that the rest of the file does not match this is If type is ‘ without-match’, when grep discovers null input binary data One reboot later, this seems to be working for me.Looking at the grep manual, this seems to be because (bold mine): If i disable the threading option (threaded(yes) => threaded(no)) in /etc/syslog-ng/nf the issue is gone I don't seem to be able to link directly to the comment, so here's the relevant part: It's easy to overlook this fix, amongst all the other reports and the mess of copy-pasted logfiles and stuff. I also found this in bugzilla and added my comment.įor the benefit of anyone else arriving here by Google, note comment 19, by Steven, in that bug report. I marked this as solved yesterday, but found that after a reboot the problem returned. I intend to keep my eye on it to see if it happens again and hopefully which process is causing the problem. Mar 21 22:58:02 gentoo-gateway bill: test console log # Thanks for your reply, it's much appreciatedĪfter deleting and logging a message all seems to be fine log # file messages This isn't a big problem, just puzzling and I thought that syslog-ng was the culprit due to a yet undiscovered bug. I tried entering a message with logger thinking that maybe the stat would update, but no joy there. What I'm going to do is just delete the file and see what happens. I don't have that package (app-editors/vim-core) installed so equery isn't going to return anything. Life should be so simple - that was the first thing I boot # equery b xxd Systems which offer service to the public are frequently attacked by bots looking for easy vulnerabilities. If this occurred, it does not necessarily mean that the system was breached. This might occur if some daemon was attacked and logged unfiltered shellcode as part of a "failed to authenticate user" message. I suspect that something caused a non-printable character to be written to /var/log/messages. I'm lost with xxd -l 512 /var/log/messagesĪpparently I don't have the package installed and I couldn't find it.Īpp-editors/vim-core-7.3.409 (/usr/bin/xxd) chown /var/lib/nfs to choose different user Mar 18 23:37:44 gentoo-gateway rpc.statd: Running as root. Mar 18 23:37:44 gentoo-gateway rpc.statd: Flags: TI-RPC Mar 18 23:37:44 gentoo-gateway rpc.statd: Version 1.2.5 starting chown /var/lib/nfs to choose different user If you want to match one of several characters, you can wrap those characters in brackets ( ) grep 13, mystring) 1 3 4 grep /, mystring) 1 5 7 It may be useful to indicate character sequences. Mar 18 22:53:10 gentoo-gateway rpc.statd: Running as root. Mar 18 22:53:10 gentoo-gateway rpc.statd: Flags: TI-RPC ![]() Mar 18 22:53:10 gentoo-gateway rpc.statd: Version 1.2.5 starting Mar 18 22:51:52 gentoo-gateway rpc.statd: Caught signal 15, un-registering and exiting If you're wondering if there's any content in portage # strings /var/log/messages|grep rpc.statd I have the result of ls -d /var/db/pkg/app-admin/*log*/, but I'm lost with xxd -l 512 /var/log/messagesĪpparently I don't have the package installed and I couldn't find boot # ls -d /var/db/pkg/app-admin/*log*/ Last edited by BillWho on Thu 3:03 am edited 1 time in total I can't remember the last time I had to check the log though so I don't know how recent this anomaly is. He hasn't updated his installation for quite some time so I was wondering if anyone else here has experienced this behavior recently and if it could possibly be related to a recent update. var/log/messages: UTF-8 Unicode text, with very long lines I contacted a friend on IRC and his output of file is Code: It appears to be related with the type of linux # file /var/log/messages What I have to do pipe strings to grep then I get results. The same happens with piping the output of linux # cat /var/log/messages|grep nfs Not sure if this is the correct forum, but I can't grep /var/log/messages - well I can, but the result linux # grep nfs /var/log/messages Posted: Thu 12:12 am Post subject: strange behaviour with /var/log/messages Gentoo Forums Forum Index Portage & Programming strange behaviour with /var/log/messages Gentoo Forums :: View topic - strange behaviour with /var/log/messages ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |