Citadel Support

[#] Mon Jul 07 2025 19:35:39 UTC from HvT

Subject: Re: docker image keeps crashing

Fr Jul 04 2025 00:47:30 UTC von IGnatius T Foobar Betreff: Re: docker image keeps crashing

I am having trouble getting podmal to be ba any verbose at all, and
running in the foreground does not talk much either:

Ok, let's try this. I added some code to the server and to the supervisor, and now when it crashes it will make its best effort to produce a stack trace that has some filenames and line numbers in it.

Go ahead and update your container with the latest image.

Not too chatty, either. But maybe it is still helpful. As you may see, this is the very first start and it crashes (as it usually does), when loading the page, before the login screen is being presented. Hence, no timezone yet. Another instance, where it regulary chrashes, is, when editing certain parameters of rooms. But this one is the crash from before the login screen:

$ podman run --systemd=true --rm --cpus=2 --memory=1g --name=citadel --hostname=hello.world.net --mount=type=bind,source=/daten/podman/data/citadel,destination=/citadel-data,ro=false,U=true --network=pasta:--interface,dummy.pod,--ns-ifname,tap15.pod,--ns-mac-addr,2a:00:00:00:00:15,--address,192.168.89.15,--netmask,255.255.255.0
,--gateway,192.168.89.1,--outbound,192.168.89.15,--outbound-if4,dummy.pod,--fqdn,hello.world.net,--no-dhcpv6,--no-dhcp,--dns,none,--no-map-gw,--tcp-ports,192.168.89.1/25,--tcp-ports,192.168.89.1/80,--tcp-ports,192.168.89.1/110,--tcp-ports,192.168.89.1/119,--tcp-ports,192.168.89.1/143,--tcp-ports,192.168.89.1/443,--tcp-ports,192.168.89.1/465,--tcp-ports,192
.168.89.1/504,--tcp-ports,192.168.89.1/563,--tcp-ports,192.168.89.1/587,--tcp-ports,192.168.89.1/993,--tcp-ports,192.168.89.1/995,--tcp-ports,192.168.89.1/5222 docker.io/citadeldotorg/citadel
Trying to pull docker.io/citadeldotorg/citadel:latest...
Getting image source signatures
Copying blob cf1db188696b done   |
Copying blob cc41ef31545f done   |
Copying blob ff44dcceb233 done   |
Copying blob 36fc4513d1bb done   |
Copying blob 4f4fb700ef54 done   |
Copying blob 2ae7966dbe43 done   |
Copying blob ae1048e58da0 done   |
Copying blob 86d5ae05b3a0 done   |
Copying blob ccbf3b9f7451 done   |
Copying config 1c45cdb189 done   |
Writing manifest to image destination
ctdlvisor: Welcome to the Citadel System running in a container.
ctdlvisor: command line arguments: /usr/local/bin/ctdlvisor
ctdlvisor: /citadel-data is writable
ctdlvisor: /citadel-data/data is writable
ctdlvisor: /citadel-data/files is writable
ctdlvisor: /citadel-data/keys is writable
ctdlvisor: citserver running on pid=2
ctdlvisor: executing citserver
ctdlvisor: webcit (HTTP) running on pid=3
ctdlvisor: webcit (HTTPS) running on pid=4
ctdlvisor: executing webcit (http) on port 80
ctdlvisor: executing webcit (https) on port 443
/usr/local/citadel/guesstimezone.sh: 350: echo: echo: I/O error
ctdlvisor: pid=2 exited, status=139, exitcode=0
ctdlvisor: citserver crashed on signal 11
/citadel/server/session.c:64
??:0
sequence.c:?
/citadel/server/modules/expire/serv_expire.c:142 (discriminator 1)
/citadel/server/modules/imap/serv_imap.c:1130
??:0
ctdlvisor: citserver running on pid=1047
ctdlvisor: executing citserver

[#] Thu Jul 10 2025 00:03:17 UTC from IGnatius T Foobar

Subject: Re: docker image keeps crashing

I updated the container image again today. Went back to offsets because addr2line is hallucinating about where the file names and line numbers line up. I got that weird imap.c one too, and it's definitely wrong.

Also turned up the logging level so we'll get more context.

[#] Thu Jul 10 2025 19:05:58 UTC from HvT

Subject: Re: docker image keeps crashing

Do Jul 10 2025 00:03:17 UTC von IGnatius T Foobar Betreff: Re: docker image keeps crashing

I updated the container image again today. Went back to offsets because addr2line is hallucinating about where the file names and line numbers line up. I got that weird imap.c one too, and it's definitely wrong.

Also turned up the logging level so we'll get more context.

Now we are talking, therefore I have attached them, instead of posting the output.

I have no idea, what is going in, but the suggestion seems to be ssl related. Still, the server also crashes, when called explicitly with http, not https. Again, these crashes are happening before the loginscreen appears. Takes about ~30 seconds to load the site, DNS however is fine (unless there is a podman problem which may very well be, as I am new to this and pasta)

https.txt (text/plain, 36358 bytes) [View| Download]

http.txt (text/plain, 29561 bytes) [View| Download]

[#] Sat Jul 12 2025 01:37:27 UTC from IGnatius T Foobar

Subject: Re: docker image keeps crashing

I have no idea, what is going in, but the suggestion seems to be ssl related. Still, the server also crashes, when called explicitly with http, not https. Again, these crashes are happening before the loginscreen appears. Takes about ~30 seconds to load the site, DNS however is fine (unless there is a podman problem which may very well be, as I am new to this and pasta)

I am an honorary Italian Grandmother so I know plenty about pasta. But that's not important right now.

These traces offer some good clues. It's crashing in cprintf() which is being called by cmd_oimg() and I found an uninitialized variable in cmd_oimg(). Honestly I don't know how you're the only one reporting this problem, but maybe it has to do with podman. I only know it's been tested on Docker Engine and on Kubernetes (probably with runc). In any case, a fix should be forthcoming if that's the problem.

https.txt (text/plain, 36358 bytes) [View| Download]

http.txt (text/plain, 29561 bytes) [View| Download]

[#] Sat Jul 12 2025 02:32:52 UTC from IGnatius T Foobar

Subject: Re: docker image keeps crashing

All righty then, a fix has been checked in, download the new container image (version 1018) and let's see how it works. Attach the trace if not.

[#] Sat Jul 12 2025 20:44:45 UTC from HvT

Subject: Re: docker image keeps crashing

Sa Jul 12 2025 02:32:52 UTC von IGnatius T Foobar Betreff: Re: docker image keeps crashing

All righty then, a fix has been checked in, download the new container image (version 1018) and let's see how it works. Attach the trace if not.

Seems, the Pasta have been a little bit too salty. Happens to the best of us. See Attachment, called without ssl, or just http.

Anyway, mille gracie for the very fast response/patch, even if not complete.

http2.txt (text/plain, 29610 bytes) [View| Download]

[#] Mon Jul 14 2025 20:20:31 UTC from IGnatius T Foobar

Subject: Re: docker image keeps crashing

Wow, I really thought that was going to fix it. Now I also see that the admin account is being created in this trace, which means it's the very first run?

If you could share what OS distribution you're using and what version of Podman is on it, I'd like to try to reproduce the error.

[#] Mon Jul 14 2025 23:26:47 UTC from IGnatius T Foobar

Subject: Re: docker image keeps crashing

Please do share what you're running, but also: I started up a Fedora 42 LXC container, installed podman in it, ran the published Citadel image, sent the "OIMG hello" command to it, and got the exact same crash.

Unfortunately I don't have a development path here, other than to try various fixes and publish new versions of the container, so y'all are gonna see a lot of new Citadel versions coming out that aren't actually new. :)

[#] Tue Jul 15 2025 02:19:05 UTC from IGnatius T Foobar

Subject: Re: docker image keeps crashing

All righty then -- I found the problem. I don't know whether the problem is in Fedora or Podman, but we can blame IBM either way, right? ;)

Any error message that we send to the client that contains the expression strerror(errno) makes the server crash, but only when running in Podman. I don't know why. I removed that expression from OIMG and it now works, but I looked for other functions that use that expression, and they crash too.

So I guess we just can't use that function anymore. I'll remove it. Not a huge deal.

[#] Tue Jul 15 2025 03:41:57 UTC from IGnatius T Foobar

Subject: Re: docker image keeps crashing

Give the new container image a try and see how we did now.

[#] Wed Jul 16 2025 14:35:14 UTC from Fred

Subject: Draft editing

Greetings:

Used easy install method. Was able to get spamd/clamav to function.

However unable to modify/edit drafts (draft room) . No prompt for editing draft or to "send message" from draft room available.

Write mail with Tiny MCE is o.k. Is there some configuration that was missed?

Thanks

[#] Wed Jul 16 2025 21:11:03 UTC from HvT

Subject: Re: docker image keeps crashing

Di Jul 15 2025 03:41:57 UTC von IGnatius T Foobar Betreff: Re: docker image keeps crashing

Give the new container image a try and see how we did now.

I wholeheartly agree on IBM. Otherwise, I didn't had the chance to test too thoroughly, but hey, so far it looks good now! At least calling the login screen and editing rooms now seems to work without crashing. Nice job, thanks again!

In case I'll stumble over other issues, be sure, I'll let you know

[#] Fri Jul 18 2025 15:57:29 UTC from Motobike

Subject: Server fail

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 ?

[#] Fri Jul 18 2025 22:33:26 UTC from Motobike

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)

[#] Sun Jul 20 2025 09:47:02 UTC from MarisaG

Subject: Abity to set quotas?

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...

[#] Sun Aug 03 2025 20:52:20 UTC from IGnatius T Foobar

Subject: Re: Abity to set quotas?

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.

[#] Wed Aug 06 2025 19:55:40 UTC from Motobike

Subject: BCC

There is a problem with BCC recieptiens.

They will all appear in Mail header as > Envelope-to:

Is there a option to hide recieptens in header ?

[#] Wed Aug 27 2025 17:43:58 UTC from luisgo

Subject: Shrink my databases.

Dear All,

I want to shrink my databases. I tried with the shell script "database_cleanup.sh" and it gives a error even with citadel shutdown and with plenty of disk space (I renamed /tmp in the script).

How to set the "c_shrink_db_files" variable (before compilation)?

I want only an one time shrink.

Thank you,

Luís Gonçalves.

[#] Mon Sep 01 2025 17:53:00 UTC from IGnatius T Foobar

Subject: Re: BCC

There is a problem with BCC recieptiens.

They will all appear in Mail header as > Envelope-to:

Is there a option to hide recieptens in header ?

Can you clarify please, is this on outbound or inbound email?

[#] Mon Sep 01 2025 17:57:32 UTC from IGnatius T Foobar

Subject: Re: Shrink my databases.

I want to shrink my databases. I tried with the shell script "database_cleanup.sh" and it gives a error even with citadel shutdown and with plenty of disk space (I renamed /tmp in the script).

How to set the "c_shrink_db_files" variable (before compilation)?

I want only an one time shrink.

c_shrink_db_files is not a compile-time option. We've worked hard to have as few of those as possible.

If you set the c_shrink_db_files configuration option, the database will be compacted at shutdown time.

If you're not satisfied with the results, I would suggest using ctdldump and ctdlload, not database_cleanup.sh. But really, Citadel is good with disk space -- it will reuse the "holes" in those files to write new data. At some point your disk utilization will stabilize if you have both new data coming in and old data being purged. If you have plenty of disk space and your system is running cleanly I would advise leaving it alone.

Uncensored

New user? Register now

Please wait...