Please wait...
0 files
Hi there,
my protocol says this.
Jul 18 17:50:17 pbcontrol citserver[21027]: SIGSEGV received in thread 139790179628800 at address 0x270
Jul 18 17:50:17 pbcontrol citserver[21027]: Stack frame #0: /usr/local/citadel/citserver(+0x163dc) [0x55f5876173dc]
Jul 18 17:50:17 pbcontrol citserver[21027]: Stack frame #1: /lib/x86_64-linux-gnu/libpthread.so.0(+0x12730) [0x7f23931de730]
Jul 18 17:50:17 pbcontrol citserver[21027]: Stack frame #2: /usr/local/citadel/citserver(+0x61dc0) [0x55f587662dc0]
Jul 18 17:50:17 pbcontrol citserver[21027]: Stack frame #3: /usr/local/citadel/citserver(+0x62bd4) [0x55f587663bd4]
Jul 18 17:50:17 pbcontrol citserver[21027]: Stack frame #4: /usr/local/citadel/citserver(+0x62e7c) [0x55f587663e7c]
Jul 18 17:50:17 pbcontrol citserver[21027]: Stack frame #5: /usr/local/citadel/citserver(+0x63aec) [0x55f587664aec]
Jul 18 17:50:17 pbcontrol citserver[21027]: Stack frame #6: /usr/local/citadel/citserver(+0x6e044) [0x55f58766f044]
Jul 18 17:50:17 pbcontrol citserver[21027]: Stack frame #7: /usr/local/citadel/citserver(+0x1732d) [0x55f58761832d]
Jul 18 17:50:17 pbcontrol citserver[21027]: Stack frame #8: /lib/x86_64-linux-gnu/libpthread.so.0(+0x7fa3) [0x7f23931d3fa3]
Jul 18 17:50:17 pbcontrol citserver[21027]: Stack frame #9: /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f2392f1406f]
do someone else have any error like this since update 1018 ?
Subject: Error between Docker and "normal" installation (1020)
If you create a room and set up a Mailing List. In a Docker Container, subscribers will not shown in overview.
In a normal installation it works fine.
Subsribers will get mails normaly, but will not show up in overview. (Docker Container / 1020)
Is it possible to set a quota for space used per user? Want to be sure one user doesn't chew up all the space...
Is it possible to set a quota for space used per user? Want to
be sure one user doesn't chew up all the space...
Unfortunately there are no per-user quotas available in Citadel Server.
What we do have is a system-wide safety check, if available disk space goes below 100 MB it will refuse to accept new messages, so the system doesn't get corrupted by a disk full condition.