Mon Apr 14 2025 06:57:22 UTC from luisgo Subject: Re: Citadel Server sudden stop and restart fails with error DBD2055

 

Mon Apr 14 2025 01:39:12 UTC from IGnatius T Foobar Subject: Re: Citadel Server sudden stop and restart fails with error DBD2055

I had a similar problem this late afternoon. I had to recover the data
files from a backup due a full disk. I reported a similar problem some
time ago.

You know what, I'm going to add something to the server to make it refuse to accept new messages when the free disk space is under 100 MB. It sure seems better than seeing people have problems *after* they run out of disk.

Dear All,

What I think that will help a lot from my experience dealing with this is doing the following:

It is doing Auto-Purging from 15 minutes in 15 minutes instead only one time a day.

Hour to run database auto-purge

Thanks,

Luís Gonçalves

Doing that without accepting transactions (stopped server).

Dear All,

I tried to disable without success. Is it normal?

ManageSieve Port (-1 to disable)

Thanks,

Luís Gonçalves

Mo Apr 14 2025 01:39:12 UTC von IGnatius T Foobar Betreff: Re: Citadel Server sudden stop and restart fails with error DBD2055

I had a similar problem this late afternoon. I had to recover the data
files from a backup due a full disk. I reported a similar problem some
time ago.

You know what, I'm going to add something to the server to make it refuse to accept new messages when the free disk space is under 100 MB. It sure seems better than seeing people have problems *after* they run out of disk.

That could indeed be helpful for scenarios where disk space is an issue. However, just to re-confirm in my particular case disk is no issue at all. I have around 470GiB free on the file system where the database resides. So question is still how I can understand what causes the SIGSEGV crash on the citadel server. 

Mo Apr 14 2025 18:25:54 UTC von IGnatius T Foobar Betreff: Re: Citadel Server sudden stop and restart fails with error DBD2055

However, just to re-confirm in my particular case disk is no issue at
all. I have around 470GiB free on the file system where the database
resides. So question is still how I can understand what causes the
SIGSEGV crash on the citadel server. 

If you have a core dump you can do a stack trace against it. If not, you can run citserver in the debugger. Like this:

systemctl stop citserver
cd /usr/local/citadel
gdb ./citserver
gdb> run -x9
[ wait for it to crash ]
gdb> thread apply all bt

Then post the output here.

With some logfile watching I was able to track the issue back to two iOS devices. As soon as these start syncing IMAP the server crashes and executes automatic restart. I disabled the devices and did export and re-import of database. Server was stable after. Re-nable on device was triggering the crashes again. Went then and updated server to 1011. So far server has not crahed again even with the Apple devices synching. Will watch, let's hope this did the trick.  

Dear All,

I am getting again message not found errors in the syslog:

Apr 27 11:12:55 [hostname]citserver[172369]: citserver[172369]: msgbase: error; invalid preloaded message for output
Apr 27 11:12:55 [hostname]citserver[172369]: msgbase: message #93638 was not found
Apr 27 11:12:55 [hostname]citserver[172369]: message repeated 2 times: [ msgbase: message #93638 was not found]
Apr 27 11:12:55 [hostname]citserver[172369]: msgbase: error; invalid preloaded message for output
Apr 27 11:12:56 [hostname]citserver[172369]: citserver[172369]: msgbase: message #93647 was not found
Apr 27 11:12:56 [hostname]citserver[172369]: citserver[172369]: msgbase: message #93647 was not found
Apr 27 11:12:56 [hostname]citserver[172369]: msgbase: message #93647 was not found
Apr 27 11:12:56 [hostname]citserver[172369]: citserver[172369]: msgbase: message #93647 was not found
Apr 27 11:12:56 [hostname]citserver[172369]: citserver[172369]: msgbase: error; invalid preloaded message for output
Apr 27 11:12:56 [hostname]citserver[172369]: msgbase: message #93647 was not found
Apr 27 11:12:56 [hostname]citserver[172369]: msgbase: message #93647 was not found
Apr 27 11:12:56 [hostname]citserver[172369]: msgbase: error; invalid preloaded message for output
Apr 27 11:51:12 [hostname]citserver[172369]: citserver[172369]: msgbase: message #140726346663536 was not found
Apr 27 11:51:12 [hostname]citserver[172369]: msgbase: message #140726346663536 was not found

Believe ther was a way to target and remove these message references from the system using the console interface but I can't recall how this was done. Also did not find this in the documentation. Can somebody remind me on the procedure, please.

Thanks! 

Hi Ignatius,

but where will it be defined ? First start citadel, it will defined in a config that starts webcit with parameters X. 

Do Feb 13 2025 23:38:47 UTC von IGnatius T Foobar Betreff: Re: First Room

What you mean with [other options] ?

WebCit is normally called with options to specify the port number it's listening on, whether to enable HTTPS, and the directory where Citadel Server can be found.

For example, here are the commands we are using to start WebCit here:

webcit -x1 -s -p 443 -g /dotgoto?room='Welcome to UNCENSORED!' uds /citadel-data
webcit -x1 -p 80 -g /dotgoto?room='Welcome to UNCENSORED!' uds /citadel-data

(Most sites will have two, one for HTTP and one for HTTPS, but if you have Citadel sitting behind a proxy or if you have some other webserver redirecting HTTP to HTTPS you might only have one.)

Sorry for the dumb question :)

There was a missing Information to edit it in systemd.

nano /etc/systemd/system/webcit-https.service

nano /etc/systemd/system/webcit-http.service

[Unit]

Description=Citadel web service with encryption

After=citadel.target

[Service]

ExecStart=/usr/local/webcit/webcit -s -p443 -g /dotgoto?room='MBF' uds /usr/local/citadel

ExecReload=/bin/kill

KillMode=process

Restart=always

RestartSec=3

[Install]

WantedBy=multi-user.target

Do Mai 01 2025 09:26:51 UTC von Motobike Betreff: Re: First Room

Hi Ignatius,

but where will it be defined ? First start citadel, it will defined in a config that starts webcit with parameters X. 

 

Do Feb 13 2025 23:38:47 UTC von IGnatius T Foobar Betreff: Re: First Room

What you mean with [other options] ?

WebCit is normally called with options to specify the port number it's listening on, whether to enable HTTPS, and the directory where Citadel Server can be found.

For example, here are the commands we are using to start WebCit here:

webcit -x1 -s -p 443 -g /dotgoto?room='Welcome to UNCENSORED!' uds /citadel-data
webcit -x1 -p 80 -g /dotgoto?room='Welcome to UNCENSORED!' uds /citadel-data

(Most sites will have two, one for HTTP and one for HTTPS, but if you have Citadel sitting behind a proxy or if you have some other webserver redirecting HTTP to HTTPS you might only have one.)

 

Hi there,

i got problems with insert links after update to 1011. Same here...

Greetings

Mike

Good Night (here),

I use Thunderbird as email client.

Due to I am being now unemployed I send lots of emails advertizing me. I use an email template and the plugin/extension Merge to send a batch of emails.

When I send a batch of several emails and store the template email in a folder in the citadel server I notice that I have only access to about 40 emails addresses (i.e. when I do a reply to all from the email template) when the template have much more than 40 destinataries. When I store in a local folder or in another email server (e.g. Microsoft Exchange) I have access to all the emails addresses. 

I suppose this is a limitation of the Citadel Email Server.

It is normal that I send batches greater than 100 emails each.

Could it be solved?

Thank you,

Luís Gonçalves.

i got problems with insert links after update to 1011. Same here...

Maybe try from another browser or clear your cache?   It seems to work for me.

I suppose this is a limitation of the Citadel Email Server.

It is normal that I send batches greater than 100 emails each.

Could it be solved?

I believe there is a limit of 1024 characters.  I don't quite remember whether that's in total or for each of to/cc/bcc, but it's a character limit, not an address limit.

Good Afternoon,

Cloud you please increase to say 4096 or 8192 charaters instead of 1024?

Or it has difficult implications on the database?

Thank you,

Luís Gonçalves.

Tue May 06 2025 02:25:09 UTC from IGnatius T Foobar Subject: Re: Message with more than 40 destinataries

 

I suppose this is a limitation of the Citadel Email Server.

It is normal that I send batches greater than 100 emails each.

Could it be solved?

I believe there is a limit of 1024 characters.  I don't quite remember whether that's in total or for each of to/cc/bcc, but it's a character limit, not an address limit.

I hope this time I am not being rude. Thank you.

Tue May 06 2025 11:10:54 UTC from luisgo Subject: Re: Message with more than 40 destinataries

Good Afternoon,

Cloud you please increase to say 4096 or 8192 charaters instead of 1024?

Or it has difficult implications on the database?

Thank you,

Luís Gonçalves.

Tue May 06 2025 02:25:09 UTC from IGnatius T Foobar Subject: Re: Message with more than 40 destinataries

 

I suppose this is a limitation of the Citadel Email Server.

It is normal that I send batches greater than 100 emails each.

Could it be solved?

I believe there is a limit of 1024 characters.  I don't quite remember whether that's in total or for each of to/cc/bcc, but it's a character limit, not an address limit.

 

Since updating to 1012, the first access of the website issues a 503 error:

This program was unable to connect or stay connected to the Citadel server. Please report this problem to your system administrator.

If you reload, it works and stays working.  If you navigate away for a while (half hourish?) and go back you get the error again.

In the log, I see a message like:

This is a private/testing instance so I'm the only user, so I can't comment if other users have this problem.

I am not sure if I broke something or it's a regression from 1011 to 1012

Thanks!

Do you have set a Session limit in the options ?

Mi Mai 07 2025 17:49:54 UTC von MisterC Betreff: Initial web access pops 503 error.

Since updating to 1012, the first access of the website issues a 503 error:

This program was unable to connect or stay connected to the Citadel server. Please report this problem to your system administrator.

If you reload, it works and stays working.  If you navigate away for a while (half hourish?) and go back you get the error again.

 

In the log, I see a message like:

2025-05-07T17:41:59.145989868Z webcit[8]: StrBuf_ServGetln(): Server connection broken: Resource temporarily unavailable

This is a private/testing instance so I'm the only user, so I can't comment if other users have this problem.

I am not sure if I broke something or it's a regression from 1011 to 1012

 

Thanks!