[Archivesspace_Users_Group] logrotate and "binary" logs

Blake Carver blake.carver at lyrasis.org
Mon Jun 14 15:18:05 EDT 2021

archivesspace.out should for sure be "ASCII text, with very long lines"
If it's something else, there's something wrong somewhere.
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Dyson-Smith, Bridger <bdysonsm at utk.edu>
Sent: Monday, June 14, 2021 3:00 PM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] logrotate and "binary" logs

Hi all -

I recently setup logrotate according to the helpful blurb in the tech-
docs[1], which has been great for our disk usage but seems to have
introduced a change in the log file's `file` type.

Before logrotate, we had

$ file archivesspace.out
aspace-log.out: ASCII text, with very long lines

and now with logrotate in play, we have

$ file as-log.out
as-log.out: data

which causes all sorts of trouble if I want to do anything other than
tail a log :).

I guess I was hoping someone may a suggestion or two about how to
approach this, either from the logrotate side or perhaps using another
utility to either modify the `file` metadata or parse the binary format
to something greppable?

Thanks for any advice you can share. My searching hasn't panned out.


[2] my config:
archivesspace/logs/archivesspace.out {
        rotate 7

Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20210614/7833a2a4/attachment.html>

More information about the Archivesspace_Users_Group mailing list