Language:
switch to room list switch to menu My folders
Go to page: First ... 19 20 21 22 [23]
[#] Thu Jun 26 2025 02:21:13 UTC from IGnatius T Foobar

Subject: Re: Old Citadel version source for VCF table

[Reply] [ReplyQuoted] [Headers] [Print]

I have a SPARCstation 20 running Solaris 7 and found source for
Citadel-UX 5.52 and 6.14, both have various build issues and
wondered if there might happen to be some other versions of the
source around somewhere. Whatever the latest source release was
in the 5.x and 6.x trees might help in building this museum
piece.

What is the experience you are trying to re-create? During the Solaris 7 era we still had the full multiuser experience on both text and web. It was a lot clunkier than it is today but it was similar in spirit.

I'm going to assume that the current version either won't build on Solaris 7 without a lot of modifications or might produce an experience too modern for your purpose. But guess what ... you can just clone the git repository, roll back to whatever year you want to experience, and build from that. If you go back to a year when Solaris 7 was current, you should be able to build everything, because Solaris was fully supported by Citadel back then.

I don't remember what version of Solaris I ran Citadel on, but I had a SPARCstation IPX and later an AXi, and regularly built Citadel on both of them.

[#] Thu Jun 26 2025 05:54:51 UTC from c1ph3rpunk

Subject: Re: Old Citadel version source for VCF table

[Reply] [ReplyQuoted] [Headers] [Print]

Nothing specifically really other than a text mode BBS, there are many DOS and other options, not many for Solaris (which is one of the machines I have on hand). The only real requirement is that I’m trying to target the year 1999 and have it there at the table so anyone can use it 

Version 6 has more Yacc issues than I care to tackle, but after fixing a couple small bugs in the 5.52 version, and adjusting make options, I have it built and working.



[#] Thu Jun 26 2025 16:48:35 UTC from HvT

Subject: docker image keeps crashing

[Reply] [ReplyQuoted] [Headers] [Print]

Running the docker image on arch/podman 5.5.1 (unpriviledged) seems to crash rather happily, after some light use:

Just in case, this output is of any use, meanthile I'll try a complete reboot:

 

Jun 26 18:16:58 podhost systemd-coredump[72142]: Process 71754 (citserver) of user 666 terminated abnormally with signal 11/SEGV, processing...
Jun 26 18:16:58 podhost systemd[1]: Started Process Core Dump (PID 72142/UID 0).
Jun 26 18:16:58 podhost systemd-coredump[72143]: Process 71754 (citserver) of user 666 dumped core.
                                                            
                                                            Stack trace of thread 268:
                                                            #0  0x000077723f430ad9 n/a (/lib/x86_64-linux-gnu/libc-2.31.so + 0x16aad9)
                                                            #1  0x000077723b453630 n/a (n/a + 0x0)
                                                            ELF object binary architecture: AMD x86-64
Jun 26 18:16:58 podhost systemd[1]: systemd-coredump@1-72142-0.service: Deactivated successfully.
Jun 26 18:16:58 podhost citadel[614]: ctdlvisor: pid=265 exited, status=139, exitcode=0
Jun 26 18:16:58 podhost citadel[614]: ctdlvisor: citserver crashed on signal 11
Jun 26 18:16:58 podhost citadel[614]: ctdlvisor: citserver running on pid=274
Jun 26 18:16:58 podhost citadel[614]: ctdlvisor: executing citserver
Jun 26 18:17:40 podhost systemd-coredump[72187]: Process 72149 (citserver) of user 666 terminated abnormally with signal 11/SEGV, processing...
Jun 26 18:17:40 podhost systemd[1]: Started Process Core Dump (PID 72187/UID 0).
Jun 26 18:17:40 podhost systemd-coredump[72188]: Process 72149 (citserver) of user 666 dumped core.
                                                            
                                                            Stack trace of thread 275:
                                                            #0  0x00007915a0fdaad9 n/a (/lib/x86_64-linux-gnu/libc-2.31.so + 0x16aad9)
                                                            #1  0x000079159e009630 n/a (n/a + 0x0)
                                                            ELF object binary architecture: AMD x86-64
Jun 26 18:17:40 podhost citadel[614]: ctdlvisor: pid=274 exited, status=139, exitcode=0
Jun 26 18:17:40 podhost citadel[614]: ctdlvisor: citserver crashed on signal 11
Jun 26 18:17:40 podhost citadel[614]: ctdlvisor: executing citserver
Jun 26 18:17:40 podhost citadel[614]: ctdlvisor: citserver running on pid=280
Jun 26 18:17:40 podhost systemd[1]: systemd-coredump@2-72187-0.service: Deactivated successfully.
Jun 26 18:18:28 podhost systemd-coredump[72202]: Process 72192 (citserver) of user 666 terminated abnormally with signal 11/SEGV, processing...
Jun 26 18:18:28 podhost systemd[1]: Started Process Core Dump (PID 72202/UID 0).
Jun 26 18:18:29 podhost systemd-coredump[72203]: Process 72192 (citserver) of user 666 dumped core.
                                                            
                                                            Stack trace of thread 281:
                                                            #0  0x00007f8ad0c30ad9 n/a (/lib/x86_64-linux-gnu/libc-2.31.so + 0x16aad9)
                                                            #1  0x00007f8acdc5d630 n/a (n/a + 0x0)
                                                            ELF object binary architecture: AMD x86-64
Jun 26 18:18:29 podhost citadel[614]: ctdlvisor: pid=280 exited, status=139, exitcode=0
Jun 26 18:18:29 podhost citadel[614]: ctdlvisor: citserver crashed on signal 11
Jun 26 18:18:29 podhost citadel[614]: ctdlvisor: citserver running on pid=283
Jun 26 18:18:29 podhost systemd[1]: systemd-coredump@3-72202-0.service: Deactivated successfully.
Jun 26 18:18:29 podhost citadel[614]: ctdlvisor: executing citserver
Jun 26 18:19:21 podhost systemd-coredump[72214]: Process 72207 (citserver) of user 666 terminated abnormally with signal 11/SEGV, processing...
Jun 26 18:19:21 podhost systemd[1]: Started Process Core Dump (PID 72214/UID 0).
Jun 26 18:19:21 podhost systemd-coredump[72215]: Process 72207 (citserver) of user 666 dumped core.
                                                            
                                                            Stack trace of thread 284:
                                                            #0  0x0000742305acbad9 n/a (/lib/x86_64-linux-gnu/libc-2.31.so + 0x16aad9)
                                                            #1  0x0000742302af9620 n/a (n/a + 0x0)
                                                            ELF object binary architecture: AMD x86-64
Jun 26 18:19:21 podhost systemd[1]: systemd-coredump@4-72214-0.service: Deactivated successfully.
Jun 26 18:19:21 podhost citadel[614]: ctdlvisor: pid=283 exited, status=139, exitcode=0
Jun 26 18:19:21 podhost citadel[614]: ctdlvisor: citserver crashed on signal 11
Jun 26 18:19:21 podhost citadel[614]: ctdlvisor: executing citserver
Jun 26 18:19:21 podhost citadel[614]: ctdlvisor: citserver running on pid=287
Jun 26 18:19:55 podhost systemd-coredump[72227]: Process 72219 (citserver) of user 666 terminated abnormally with signal 11/SEGV, processing...
Jun 26 18:19:55 podhost systemd[1]: Started Process Core Dump (PID 72227/UID 0).
Jun 26 18:19:55 podhost systemd-coredump[72228]: Process 72219 (citserver) of user 666 dumped core.
                                                            
                                                            Stack trace of thread 289:
                                                            #0  0x000077fca9a75ad9 n/a (/lib/x86_64-linux-gnu/libc-2.31.so + 0x16aad9)
                                                            #1  0x000077fca62a0630 n/a (n/a + 0x0)
                                                            ELF object binary architecture: AMD x86-64
Jun 26 18:19:55 podhost systemd[1]: systemd-coredump@5-72227-0.service: Deactivated successfully.
Jun 26 18:19:55 podhost citadel[614]: ctdlvisor: pid=287 exited, status=139, exitcode=0
Jun 26 18:19:55 podhost citadel[614]: ctdlvisor: citserver crashed on signal 11
Jun 26 18:19:55 podhost citadel[614]: ctdlvisor: citserver running on pid=290
Jun 26 18:19:55 podhost citadel[614]: ctdlvisor: executing citserver
Jun 26 18:20:29 podhost systemd-coredump[72237]: Process 72232 (citserver) of user 666 terminated abnormally with signal 11/SEGV, processing...
Jun 26 18:20:29 podhost systemd[1]: Started Process Core Dump (PID 72237/UID 0).
Jun 26 18:20:29 podhost systemd-coredump[72238]: Process 72232 (citserver) of user 666 dumped core.
                                                            
                                                            Stack trace of thread 292:
                                                            #0  0x0000778b2f4faad9 n/a (/lib/x86_64-linux-gnu/libc-2.31.so + 0x16aad9)
                                                            #1  0x0000778b2bd7f630 n/a (n/a + 0x0)
                                                            ELF object binary architecture: AMD x86-64
Jun 26 18:20:29 podhost systemd[1]: systemd-coredump@6-72237-0.service: Deactivated successfully.
Jun 26 18:20:29 podhost citadel[614]: ctdlvisor: pid=290 exited, status=139, exitcode=0
Jun 26 18:20:29 podhost citadel[614]: ctdlvisor: citserver crashed on signal 11
Jun 26 18:20:29 podhost citadel[614]: ctdlvisor: citserver running on pid=293
Jun 26 18:20:29 podhost citadel[614]: ctdlvisor: executing citserver



[#] Sat Jun 28 2025 18:07:29 UTC from IGnatius T Foobar

Subject: Re: Old Citadel version source for VCF table

[Reply] [ReplyQuoted] [Headers] [Print]

Version 6 has more Yacc issues than I care to tackle, but after fixing
a couple small bugs in the 5.52 version, and adjusting make options, I
have it built and working.

If you're just looking to show a classic text mode BBS, that's really all you need. We've kept it looking more or less the same for the last 43+ years, very deliberately. There have been a few modifications to support things like multiuser chat and knowing who is online, but the classic Citadel BBS interface has been carefully and deliberately preserved.

Most of the work done since 1996 has been around making Citadel do all the other things it can now do. But the text mode BBS is a timeless classic.

[#] Sat Jun 28 2025 18:11:05 UTC from IGnatius T Foobar

Subject: Re: docker image keeps crashing

[Reply] [ReplyQuoted] [Headers] [Print]

Running the docker image on arch/podman 5.5.1 (unpriviledged) seems to
crash rather happily, after some light use:

If you could run the container in the foreground with full logging turned on, it would be great if you could capture the last screenful of log messages before a crash.

As your previous log capture shows, we've been trying to get it to be better about showing where it crashed, but all we're able to get so far is a program name and memory offset.

[#] Mon Jun 30 2025 17:18:23 UTC from HvT

Subject: Re: docker image keeps crashing

[Reply] [ReplyQuoted] [Headers] [Print]

 

Sa Jun 28 2025 18:11:05 UTC von IGnatius T Foobar Betreff: Re: docker image keeps crashing
Running the docker image on arch/podman 5.5.1 (unpriviledged) seems to
crash rather happily, after some light use:

If you could run the container in the foreground with full logging turned on, it would be great if you could capture the last screenful of log messages before a crash.

As your previous log capture shows, we've been trying to get it to be better about showing where it crashed, but all we're able to get so far is a program name and memory offset.

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

 

$ 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
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: webcit (HTTP) running on pid=3
ctdlvisor: executing citserver
ctdlvisor: executing webcit (http) on port 80
ctdlvisor: executing webcit (https) on port 443
ctdlvisor: webcit (HTTPS) running on pid=4
ctdlvisor: pid=2 exited, status=139, exitcode=0
ctdlvisor: citserver crashed on signal 11
ctdlvisor: citserver running on pid=10
ctdlvisor: executing citserver
ctdlvisor: pid=10 exited, status=139, exitcode=0
ctdlvisor: citserver crashed on signal 11
ctdlvisor: citserver running on pid=19
ctdlvisor: executing citserver

 

I have however, attached a coredumd for each of above crashes. Those came from a fresh install (empty citadel-data), so nothing secret in there. I hope. Maybe these help. In case you have any more hints for verbosity, just let me know, please. 



core.citserver.666.c5962faeecaf4730b5e3099303d38910.2789.1751303283000000.zst (application/zstd, 577262 bytes) [ View | Download ]
core.citserver.666.c5962faeecaf4730b5e3099303d38910.2807.1751303330000000.zst (application/zstd, 561708 bytes) [ View | Download ]
[#] Fri Jul 04 2025 00:47:30 UTC from IGnatius T Foobar

Subject: Re: docker image keeps crashing

[Reply] [ReplyQuoted] [Headers] [Print]

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.

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

Subject: Re: docker image keeps crashing

[Reply] [ReplyQuoted] [Headers] [Print]

 

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

[Reply] [ReplyQuoted] [Headers] [Print]

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

[Reply] [ReplyQuoted] [Headers] [Print]

 

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

[Reply] [ReplyQuoted] [Headers] [Print]

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

[Reply] [ReplyQuoted] [Headers] [Print]

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

[Reply] [ReplyQuoted] [Headers] [Print]

 

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

[Reply] [ReplyQuoted] [Headers] [Print]

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.



Go to page: First ... 19 20 21 22 [23]