/var/log/bluecherry.log wrong ownership

Server discussion
1

Sorry for the dumb question, but I’m not supper strong on Linux administration. I do not know what I did or if it was tied to an update, however when bluecherry does a log rotation, the new file is owned by root:bluecherry and nothing gets written into the new log file. The old log files are all owned by syslog:bluecherry. If I change the ownership of the new log file to syslog:bluecherry, then the application starts logging normally. At the new log rotate, the problem returns.

I’m not sure what I need to fix here.

Running bluecherry 3.1.14 under Ubuntu 6.14.0-28-generic #28~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 25 10:47:01 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

If anyone has a quick corrective action here, I’d really appreciate it.

2

In the logrotate config for bluecherry, add “create 0644 syslog bluecherry”

3

That would have taken me a while to find. Guessing 3.1.14 might have updated that file and set it to root vs. syslog.

Thanks for the assist!

4

That’s just how logrotate in of itself works for permissions/ownerships.