Couchdb stoped writing to the journald logs

[NOTE]: # ( ^^ Provide a general summary of the issue in the title above. ^^ )

## Description

We are using couchdb v 3.3.3 with the log settings as :

```
"log": {
"level": "error",
"writer": "journald"
},
```

We noticed that couchdb stopped writing to the journald logs and we have to restart the couchdb service for it to start writing to the journal. This has happened few times and has limited our ability to troubleshoot or look at the logs.

We are on Ubuntu 22.04.3 LTS and the all the settings for the journald are the default ones:

```
cat /etc/systemd/journald.conf

[Journal]
#Storage=auto
#Compress=yes
#Seal=yes
#SplitMode=uid
#SyncIntervalSec=5m
#RateLimitIntervalSec=30s
#RateLimitBurst=10000
#SystemMaxUse=
#SystemKeepFree=
#SystemMaxFileSize=
#SystemMaxFiles=100
#RuntimeMaxUse=
#RuntimeKeepFree=
#RuntimeMaxFileSize=
#RuntimeMaxFiles=100
#MaxRetentionSec=
#MaxFileSec=1month
#ForwardToSyslog=yes
#ForwardToKMsg=no
#ForwardToConsole=no
#ForwardToWall=yes
#TTYPath=/dev/console
#MaxLevelStore=debug
#MaxLevelSyslog=debug
#MaxLevelKMsg=notice
#MaxLevelConsole=info
#MaxLevelWall=emerg
#LineMax=48K
#ReadKMsg=yes
#Audit=no
```

We also noticed that restarting the systemd-journald service would not help, only restarting the couchdb service will make it start writing to the logs.

Please let me know if we are facing any bug or have to tweak any settings.

Thanks,

[NOTE]: #
[TIP]: # ( Do NOT give us access or passwords to your actual CouchDB! )

## Steps to Reproduce

[NOTE]: # ( Include commands to reproduce, if possible. curl is preferred. )

## Expected Behaviour

[NOTE]: # ( Tell us what you expected to happen. )

## Your Environment

[TIP]: # ( Include as many relevant details about your environment as possible. )
[TIP]: # ( You can paste the output of curl http://YOUR-COUCHDB:5984/ here. )

* CouchDB version used: 3.3.3
* Browser name and version:
* Operating system and version: Ubuntu 22.04.3 LTS

## Additional Context

[TIP]: # ( Add any other context about the problem here. )

Start by reproducing the failure with CouchDB 3.3.3 using the shown log configuration on Ubuntu 22.04.3 LTS, and compare CouchDB's journald behavior with /etc/systemd/journald.conf. Done means identifying a reliable trigger and documenting either the relevant CouchDB defect or the setting and workaround that prevents logging from stopping.

Written by the indexing model from the issue text.