Yes, the similar problem happened to me.
What I understood from @orbiter, there is no possibility to make a separate logs now.
But you can set the logging levels to WARNING or SEVERE, to make the log shorter and therefore protected from frequent rotation.
I crafted a bit the logging system in recent months, to be more user-filtrable.
And wrote a description of logging here: https://yacy.net/operation/logging/
Feature to separate an error log would be great also for me! Possibility to use a system logger at least for main errors would be nice!
Maybe it’s easy for someone, who knows Java…
You should also be able to restart Yacy from the command line, so you are not limited to the task manager. The batch files that do this are:
/stopYACY.bat
/startYACY.bat
A friend set up a peer that automatically restarts Yacy if it crashed. This can be detected by trying to load a small image from the Yacy search page, like the logo. If nothing from the Yacy web page loads, obviously the server crashed. Then the batch files are executed to stop and start Yacy again.
i use restartYACY.sh, run from cron daemon, to restart yacy every day.
0 9 * * * /path/to/yacy/restartYACY.sh crontab entry restarts the peer every 9AM. my instance had been crashing after some days regularly before, this was… workaround. but ok since then.