pykolab.log is empty
Michael Menge
michael.menge at zdv.uni-tuebingen.de
Fri Jun 30 09:56:42 CEST 2023
Hi,
i have the same problem. I suspect that after the log-rotate the old
file handle
is still used. So a postrotate script in the logrotate config is
probably needed
to signal the services to reopen the file, or to restart the service
kind regards
Michael
On 2023-06-16 08:14, Johannes Ranke wrote:
> Dear Kolab users,
>
> I have the same problem described below, also on a stretch system that was
> previously running buster.
>
> Any hints would be appreciated.
>
> Johannes
>
> Am Dienstag, 6. Juni 2023, 20:44:05 CEST schrieb Eric Chaput:
>> Hi Everyone,
>>
>> after an upgrade from Debian Stretch to Buster I've been troubleshooting
>> issues with kolab_smtp_access_policy.py and when trying to find the logs
>> for it, I noticed that my pykolab.log is empty. What's strange is that
>> the timestamp / last modified time on the file changes from time to time
>> but it stays empty.
>>
>> Any idea what could be wrong with the kolab logging?
>>
>> Thanks
>>
>> Eric
--------------------------------------------------------------------------------
Michael Menge Tel.: (49) 7071 / 29-70316
Universität Tübingen Fax.: (49) 7071 / 29-5912
Zentrum für Datenverarbeitung mail:
michael.menge at zdv.uni-tuebingen.de
Wächterstraße 76
72074 Tübingen
More information about the users
mailing list