What comes to my mind is the following: and there do indeed seem to be control
characters added whenever Solr start running
[16:33 solr10 1435]$ strings solr.log | diff - solr.log | less
7,8c7
< 2025-01-13 09:42:29.112 INFO (main) [ ] o.a.s.s.CoreContainerProvider ___
_ Welcome to Apache Solr
< version 9.2.1
---
> 2025-01-13 09:42:29.112 INFO (main) [ ] o.a.s.s.CoreContainerProvider ___
> _ Welcome to Apache Solr<E2><84><A2> version 9.2.1
*[16:33 solr10 1436]$ strings solr.log | diff - solr.log | sed -n -e l
7,8c7$
< 2025-01-13 09:42:29.112 INFO (main) [ ] o.a.s.s.CoreContainerPro\
vider ___ _ Welcome to Apache Solr$
< version 9.2.1$
---$
> 2025-01-13 09:42:29.112 INFO (main) [ ] o.a.s.s.CoreContainerPro\
vider ___ _ Welcome to Apache Solr\342\204\242 version 9.\
2.1$
[16:34 solr10 1437]$
-----Original Message-----
From: Silverman, Harry (Contractor) <[email protected]>
Sent: Tuesday, January 28, 2025 4:28 PM
To: [email protected]
Subject: [EXTERNAL] log file appears binary
Hi -
We have multiple Solr 9.5.0 installations running on Linux. All are configured
the same.
On one of those installations, when I grep the solr log, it returns "Binary
file solr.log matches".
The "file" command returns "data".
I can edit or cat the log file and it looks like regular text.
We have bash scripts that grep the solr log, and so these scripts don't work on
this particular installation.
I tried adding charset="UTF-8" to the PatternLayout in the log4j configuration
file. That did not help.
Any ideas what may be going on here?
Thanks,
Jay
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you recognize the sender and are confident the
content is safe.
