Language:
switch to room list switch to menu My folders
Go to page: 1 2 3 4 [5] 6 7 8 9 ... Last
[#] Sat Dec 11 2021 16:15:21 EST from meshmark

Subject: User Time Zone

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

How does one set their user time zone? I've gone to my Preferences and settings page and am able to change my time format. But, nowhere on that page is an entry for setting for my time zone.

Reason I ask, I have just been admitted to a Citadel machine in Oregon (as an admin) and I live in New Jersey. In particular, getting a calendar entry correct seems difficult. Indeed, under Administration -> General site configuration items there is something called "Default timezone for unzoned calendar items". This would seem to indicate that Citadel is looking for someone's time zone when he makes a calendar entry.  Thus, my question.

Regards

 



[#] Sat Dec 11 2021 16:24:33 EST from meshmark

Subject: Re: User Time Zone

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

Further info:

The system in question has the "Default timezone for unzoned calendar items" set to "America/Los Angeles". This appears to be set correctly for where the machine is located. Unfortunately, when I access the calendar, the dates/times appear to be in UTC. Something seems to be missing...

 



[#] Tue Dec 14 2021 09:10:17 EST from whitejack

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

Why is citadel not packed for Debian 11?

 



[#] Tue Dec 14 2021 14:14:32 EST from s3cr3to to Citadel_Support <room_Citadel_Support@uncensored.citadel.org>

Subject: Re: (no subject)

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

Although for ease I would ask the same question some time ago.

Today I can say that Citadel presents several options that could be better than a debian package:

From https://www.citadel.org/download.html
A script for installation (EasyInstall) and a Docker version, and even the source code.

The latter needs an enthusiastic volunteer to create and maintain the package for Debian. (note the emphasis)


Personally, I am currently struggling trying to understand Docker (especially in allocating the space I need to migrate).
And of course, I have no doubt that once I master this it will be very easy (... ¿easy? ).

On 12/14/21 07:10, whitejack wrote:

Why is citadel not packed for Debian 11?

 




[#] Tue Dec 14 2021 17:02:10 EST from StarbaseSSD

Subject: Re: Docker container of Citadel is now ready to download

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

Peter:

Found a work-around / fix for keys in the docker container. I have tested in both a RaspberryOS host, and a Debian 11 host, YMMV.

Note: The shared volume I had to change from /usr/local/citadel to /citadel-data to get it to work.

=====

sudo apt install docker.io -y
sudo usermod -aG docker pi
sudo mkdir /citadel-data
reboot
docker run -d --restart=unless-stopped --network host \
--volume=/citadel-data:/citadel-data \
--name=citadel citadeldotorg/citadel

docker stop citadel

sudo cd /citadel-data/keys
sudo rm -f citadel.*
sudo openssl genrsa -out citadel.key 2048
sudo openssl req -new -key citadel.key -out citadel.csr
     Answer the questions to the best of your ability
sudo openssl x509 -req -days 365 -in citadel.csr -signkey citadel.key -out citadel.cer
sudo chmod 777 citadel.*
docker start citadel
Connect to Citadel:
https://<ip_address>
username: admin
password: citadel

You get the warning about a self-signed certificate, and you can accept the exception
now, and all the ssl functionality now works in the other connections with the same limitation.

Feel free to use it, update docs, fix the issue for real.



[#] Wed Dec 15 2021 05:52:34 EST from sciens

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

I just saw your request for a gdb trace.

 

I have not done this before. But I enabled the debuginfo repo and installed the requested packages while trying to run a debug. Let me know if this is correct....

 

[root@mailsrv01 ~]# gdb /usr/local/citadel/citserver
GNU gdb (GDB) Red Hat Enterprise Linux 8.2-16.el8
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/local/citadel/citserver...done.
(gdb) start
Temporary breakpoint 1 at 0x4179aa: file server_main.c, line 73.
Starting program: /usr/local/citadel/citserver
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".

Temporary breakpoint 1, main (argc=1, argv=0x7fffffffe2f8) at server_main.c:73
73      server_main.c: No such file or directory.
(gdb)



[#] Wed Dec 15 2021 08:37:14 EST from sciens

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

I just saw your request for a gdb trace.

 

I have not done this before. But I enabled the debuginfo repo and installed the requested packages while trying to run a debug. Let me know if this is correct....

 

[root@mailsrv01 ~]# gdb /usr/local/citadel/citserver
GNU gdb (GDB) Red Hat Enterprise Linux 8.2-16.el8
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/local/citadel/citserver...done.
(gdb) start
Temporary breakpoint 1 at 0x4179aa: file server_main.c, line 73.
Starting program: /usr/local/citadel/citserver
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".

Temporary breakpoint 1, main (argc=1, argv=0x7fffffffe2f8) at server_main.c:73
73      server_main.c: No such file or directory.
(gdb)



[#] Wed Dec 15 2021 13:59:19 EST from s3cr3to to Citadel_Support <room_Citadel_Support@uncensored.citadel.org>

Subject: Docker version, reporting some bugs with aliases

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

Good day
I have some issues with the docker version unning Citadel 941 with WebCit 941, server build 941

Issue 1. I cannot find a shortcut to edit my address and aliases.

But, in order to "see" my vcard I need to perform the following steps:
  • Open "Contacts".
  • Go to: Administration - User account management - Add, change, delete user accounts
    • Search & select for an account (mine for example)
    • Click on "Edit address book entry".
    • Show a window with title "Contacts" only with my name "My Name" + Click on the button "Cancel".
    • Click on the "Cancel" button
    • Displays another window identical to the Contacts window with my name
    (no - (no     
    My Name
  • Click on my name
  • Shows my vcard
  • Click below on "[edit]"
My: Primary Internet e-mail address and Internet e-mail aliases appear.
Here I can edit and add addresses.
Issue 2: My primary address shows incorrect; it always shows something different if I change it and go back to edit vcard
  • Save changes (if I correct or add something)
  • The "Basic commands" window is displayed
Issue 3:
Although the vcard displayed shows a number of aliases.
When editing, it removes one address at random from the list of aliases.
If I save without adding, is deletes the missing address.
Every time I repeat the process, it changes the primary and when editing it removes a random address.
And so on ad-nauseum.

Regards


[#] Thu Dec 16 2021 14:26:51 EST from Art Cancro to s3cr3to <s3cr3to@uncensored.citadel.org>, Citadel_Support <room_Citadel_Support@uncensored.citadel.org>

Subject: Re: Docker version, reporting some bugs with aliases

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

To edit the email aliases for a user:

1. From the main screen, select "Administration"

2. Under the "User account management" menu, select "Add, change, delete user accounts"

3. Select the user to be edited, and click "Edit configuration"
     (do not click "Edit address book entry".  It is not there anymore.)

4. On this screen, "Primary Internet e-mail address" is the address that will be used for all outgoing mail.  The user can also receive mail at this address.

5. "Internet e-mail aliases" is where you would put any additional addresses for the user, separated by commas.  The user can receive mail at any of these addresses.


You can also edit a user's email addresses in the text mode client, using the .Aide User-edit command.


Again, there is no longer any ability to edit email addresses from the user's address book entry.  That was a hack that has been removed.



On 12/15/21 13:59, s3cr3to wrote:
Good day
I have some issues with the docker version unning Citadel 941 with WebCit 941, server build 941

Issue 1. I cannot find a shortcut to edit my address and aliases.



[#] Thu Dec 16 2021 16:55:48 EST from IGnatius T Foobar

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

Why is citadel not packed for Debian 11?

The short answer is that no one was willing to continue maintaining the package.

We owe a debt of gratitude to previous maintainers for their work. It would be difficult to continue doing so, because Citadel no longer supports being installed in LHFS mode with different files everywhere (/etc /var /usr/sbin and so on). This was becoming very cumbersome to maintain, as it added a lot of complexity to the build system.

Now that Citadel only supports a consolidated installation, it can be packaged for Debian, but they would never include it in the main repos. So if you want a convenient, pre-compiled, correctly built Citadel system that is guaranteed to run, your best option is now the Docker version.

[#] Sat Dec 18 2021 11:04:39 EST from s3cr3to to room_Citadel_Support@uncensored.citadel.org

Subject: Re: Docker version, reporting some bugs with aliases

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

Thank you!,

Unfortunately after repeating the steps several times; neither the primary address nor the aliases are preserved in the mentioned boxes.

It seems that something is missing in this version of Docker that works on your side.

Randomly something is left in the primary address, hard to know which one is going to be left and as at the moment my Citadel-docker is not in production I don't know if it is preserving the other aliases; I will check my notes I think I remember we once mentioned how to do a test mailing for any of the addresses I may have; if it works with the primary address or invisible aliases I will comment later.


Regards.

On 12/16/21 12:26, Art Cancro wrote:

To edit the email aliases for a user:

1. From the main screen, select "Administration"

2. Under the "User account management" menu, select "Add, change, delete user accounts"

3. Select the user to be edited, and click "Edit configuration"
     (do not click "Edit address book entry".  It is not there anymore.)

4. On this screen, "Primary Internet e-mail address" is the address that will be used for all outgoing mail.  The user can also receive mail at this address.

5. "Internet e-mail aliases" is where you would put any additional addresses for the user, separated by commas.  The user can receive mail at any of these addresses.


You can also edit a user's email addresses in the text mode client, using the .Aide User-edit command.


Again, there is no longer any ability to edit email addresses from the user's address book entry.  That was a hack that has been removed.



On 12/15/21 13:59, s3cr3to wrote:
Good day
I have some issues with the docker version unning Citadel 941 with WebCit 941, server build 941

Issue 1. I cannot find a shortcut to edit my address and aliases.




[#] Sat Dec 18 2021 11:04:47 EST from s3cr3to to room_Citadel_Support@uncensored.citadel.org

Subject: Re: Docker version, reporting some bugs with aliases

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

Thank you!,

Unfortunately after repeating the steps several times; neither the primary address nor the aliases are preserved in the mentioned boxes.

It seems that something is missing in this version of Docker that works on your side.

Randomly something is left in the primary address, hard to know which one is going to be left and as at the moment my Citadel-docker is not in production I don't know if it is preserving the other aliases; I will check my notes I think I remember we once mentioned how to do a test mailing for any of the addresses I may have; if it works with the primary address or invisible aliases I will comment later.


Regards.

On 12/16/21 12:26, Art Cancro wrote:

To edit the email aliases for a user:

1. From the main screen, select "Administration"

2. Under the "User account management" menu, select "Add, change, delete user accounts"

3. Select the user to be edited, and click "Edit configuration"
     (do not click "Edit address book entry".  It is not there anymore.)

4. On this screen, "Primary Internet e-mail address" is the address that will be used for all outgoing mail.  The user can also receive mail at this address.

5. "Internet e-mail aliases" is where you would put any additional addresses for the user, separated by commas.  The user can receive mail at any of these addresses.


You can also edit a user's email addresses in the text mode client, using the .Aide User-edit command.


Again, there is no longer any ability to edit email addresses from the user's address book entry.  That was a hack that has been removed.



On 12/15/21 13:59, s3cr3to wrote:
Good day
I have some issues with the docker version unning Citadel 941 with WebCit 941, server build 941

Issue 1. I cannot find a shortcut to edit my address and aliases.




[#] Mon Dec 27 2021 14:06:38 EST from IGnatius T Foobar

Subject: Re: Citadel Docker XMPP client

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

You get the warning about a self-signed certificate, and you can
accept the exception

The majority of support issues these days seem to center around certificate management. These are being heard loud and clear, and we are going to make some big changes in the next release.

I think what we need to do is eliminate the requirement for Citadel Server and WebCit to have different certificate directories (even though you can link them together), and manage it all together. This implies that WebCit will always have to run on the same host as Citadel Server, but I think everyone is doing that already. Shout out if you have any other configuration.

The system will be modified to allow the certificate to be changed without restarting, and support for the ACME HTTP-01 challenge, which should allow us to use Let's Encrypt certificates.

[#] Tue Dec 28 2021 09:57:42 EST from sirdotco

Subject: Usenet in webcit

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

I was browsing the setup menus and found entries for NNTP ports.  Cool!  Citadel can do Usenet?  I searched the GUI but I can't find where they are.  Will someone enlighten me please?

 



[#] Tue Dec 28 2021 10:35:00 EST from IGnatius T Foobar

Subject: Re: Usenet in webcit

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

There is a very basic, undocumented, read-only NNTP service in Citadel Server.
It was built as part of a project that ended before we added read-write and server-to-server support. We are exploring other ways of joining Citadel into federated social networks; these days it doesn't look like NNTP is it, but if that ever changes we can expand on our existing work.

Meanwhile, if you find the existing service useful, enjoy it!

[#] Tue Dec 28 2021 10:56:11 EST from sirdotco

Subject: Re: Usenet in webcit

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

 

Tue Dec 28 2021 10:35:00 EST from IGnatius T Foobar Subject: Re: Usenet in webcit
There is a very basic, undocumented, read-only NNTP service in Citadel Server.
It was built as part of a project that ended before we added read-write and server-to-server support. We are exploring other ways of joining Citadel into federated social networks; these days it doesn't look like NNTP is it, but if that ever changes we can expand on our existing work.

Meanwhile, if you find the existing service useful, enjoy it!

Well thanks for the info and satisfying my curiosity :)



[#] Wed Jan 05 2022 04:36:21 EST from zcw159357

Subject: server crashes after upgrade to 942

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

Hi,

  I'm using the docker version of citadel, and after upgrade to 942, it constantly crashes, and it may results in a db error.

citadel | citserver[1608]: sysdep: new client socket 36
citadel | citserver[1608]: sysdep: new client socket 35
citadel | citserver[1608]: sysdep: new client socket 37
citadel | citserver[1608]: sysdep: new client socket 41
citadel | citserver[1608]: context: session (POP3S) started from 192.168.1.1 (192.168.1.1) uid=-1
citadel | citserver[1608]: crypto: using certificate chain keys/citadel.cer
citadel | citserver[1608]: context: session (POP3S) started from 192.168.1.1 (192.168.1.1) uid=-1
citadel | citserver[1608]: crypto: using certificate chain keys/citadel.cer
citadel | citserver[1608]: context: session (POP3S) started from 192.168.1.1 (192.168.1.1) uid=-1
citadel | citserver[1608]: context: session (POP3S) started from 192.168.1.1 (192.168.1.1) uid=-1
citadel | citserver[1608]: crypto: using certificate chain keys/citadel.cer
citadel | citserver[1608]: crypto: using certificate chain keys/citadel.cer
citadel | citserver[1608]: crypto: using private key keys/citadel.key
citadel | ctdlvisor: pid=1608 exited, status=139, exitcode=0
citadel | ctdlvisor: citserver crashed on signal 11
citadel | ctdlvisor: citserver running on pid=1676
citadel | ctdlvisor: executing citserver
citadel | citserver[1676]: main: creating lockfile
citadel | citserver[1676]: crypto: using certificate chain keys/citadel.cer
citadel | citserver[1676]: crypto: using private key keys/citadel.key
citadel | citserver[1676]: extensions: registered server command STLS (Start SSL/TLS session)
citadel | citserver[1676]: extensions: registered server command GTLS (Get SSL/TLS session status)
citadel | citserver[1676]: extensions: registered a new session function (type 0 Priority 30010)
citadel | citserver[1676]: master_startup() started
citadel | citserver[1676]: Checking directory access
citadel | citserver[1676]: Opening databases
citadel | citserver[1676]: db: open_databases() starting

 

 

citadel | citserver[1676]: sysdep: new client socket 36
citadel | citserver[1676]: sysdep: new client socket 38
citadel | citserver[1676]: sysdep: new client socket 37
citadel | citserver[1676]: sysdep: new client socket 41
citadel | citserver[1676]: sysdep: new client socket 43
citadel | citserver[1676]: context: session (POP3S) started from 192.168.1.1 (192.168.1.1) uid=-1
citadel | citserver[1676]: crypto: using certificate chain keys/citadel.cer
citadel | citserver[1676]: context: session (POP3S) started from 192.168.1.1 (192.168.1.1) uid=-1
citadel | citserver[1676]: crypto: using certificate chain keys/citadel.cer
citadel | citserver[1676]: context: session (POP3S) started from 192.168.1.1 (192.168.1.1) uid=-1
citadel | citserver[1676]: crypto: using certificate chain keys/citadel.cer
citadel | citserver[1676]: crypto: using private key keys/citadel.key
citadel | citserver[1676]: crypto: using private key keys/citadel.key
citadel | free(): invalid pointer
citadel | ctdlvisor: pid=1676 exited, status=134, exitcode=0
citadel | ctdlvisor: citserver crashed on signal 6
citadel | ctdlvisor: citserver running on pid=1973
citadel | ctdlvisor: executing citserver
citadel | citserver[1973]: main: creating lockfile
citadel | citserver[1973]: crypto: using certificate chain keys/citadel.cer
citadel | citserver[1973]: crypto: using private key keys/citadel.key
citadel | citserver[1973]: extensions: registered server command STLS (Start SSL/TLS session)
citadel | citserver[1973]: extensions: registered server command GTLS (Get SSL/TLS session status)
citadel | citserver[1973]: extensions: registered a new session function (type 0 Priority 30010)
citadel | citserver[1973]: master_startup() started
citadel | citserver[1973]: Checking directory access
citadel | citserver[1973]: Opening databases

 

Jan 4 00:28:43 ubuntunas citserver[7]: msgbase: saving to disk
Jan 4 00:28:43 ubuntunas citserver[7]: msgbase: creating metadata record
Jan 4 00:28:43 ubuntunas citserver[7]: msgbase: CtdlOutputPreLoadedMsg(TheMessage=not null, 1, 0, 0, 1
Jan 4 00:28:43 ubuntunas citserver[7]: internet_addressing: qp_encode_email_addrs <yyy@xxx>
Jan 4 00:28:43 ubuntunas citserver[7]: internet_addressing: qp_encode_email_addrs <yyy@xxx>
Jan 4 00:28:43 ubuntunas citserver[7]: msgbase: storing pointers
Jan 4 00:28:43 ubuntunas citserver[7]: msgbase: updating user
Jan 4 00:28:43 ubuntunas citserver[7]: msgbase: delivering private local mail to <yyy>
Jan 4 00:28:43 ubuntunas citserver[7]: msgbase: CtdlSaveMsgPointersInRoom(room=0000000027.Mail, num_msgs=1, repl=0, suppress_rca=0)
Jan 4 00:28:43 ubuntunas citserver[7]: msgbase: 1 unique messages to be merged
Jan 4 00:28:43 ubuntunas citserver[7]: db: BDB0689 cdb.04 page 25 is on free list with type 7
Jan 4 00:28:43 ubuntunas citserver[7]: db: BDB0061 PANIC: Invalid argument
Jan 4 00:28:43 ubuntunas citserver[7]: db: PANIC: Invalid argument
Jan 4 00:28:43 ubuntunas citserver[7]: db: BDB0060 PANIC: fatal region error detected; run recovery
Jan 4 00:28:43 ubuntunas citserver[7]: db: PANIC: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
Jan 4 00:28:43 ubuntunas citserver[7]: db: BDB1005 cursor adjustment after delete failed: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
Jan 4 00:28:43 ubuntunas citserver[7]: db: PANIC: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
Jan 4 00:28:43 ubuntunas citserver[7]: db: BDB0060 PANIC: fatal region error detected; run recovery
Jan 4 00:28:43 ubuntunas citserver[7]: db: PANIC: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
Jan 4 00:28:43 ubuntunas citserver[7]: db: cdb_store(4): BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
Jan 4 00:28:43 ubuntunas citserver[7]: db: citserver is stopping in order to prevent data loss. uid=0 gid=0 euid=0 egid=0
Jan 4 00:28:48 ubuntunas citserver:
Jan 4 00:28:48 ubuntunas citserver:
Jan 4 00:28:48 ubuntunas citserver: *** Citadel server engine ***
Jan 4 00:28:48 ubuntunas citserver: Version 943 (build 34dbf6c32) ***
Jan 4 00:28:48 ubuntunas citserver: Copyright (C) 1987-2021 by the Citadel development team.
Jan 4 00:28:48 ubuntunas citserver:
Jan 4 00:28:48 ubuntunas citserver: This program is open source software: you can redistribute it and/or
Jan 4 00:28:48 ubuntunas citserver: modify it under the terms of the GNU General Public License, version 3.
Jan 4 00:28:48 ubuntunas citserver:
Jan 4 00:28:48 ubuntunas citserver: This program is distributed in the hope that it will be useful,

I'm guessing it may have something to do with the changes in serv_crypto.c ?

 



[#] Wed Jan 05 2022 08:31:01 EST from zcw159357

Subject: Re: server crashes after upgrade to 942

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

Found something....

according to the code cert_time is the mtime of cert file, but in my case my key file's mtime is always after the cert's, bind_to_key_and_certificate will be called every time.



[#] Wed Jan 05 2022 12:02:17 EST from IGnatius T Foobar

Subject: Re: server crashes after upgrade to 942

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

That bit with the key and certificate looks like it needs attention, but I don't think it's what is causing your server to crash. Try running the container in database cleanup mode.

[#] Wed Jan 05 2022 23:30:19 EST from zcw159357

Subject: Re: server crashes after upgrade to 942

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

I've tried cleanup on the first crash, that doesn't help, I have to use a backup and roll back to 941 version image. SSL_CTX_use_certificate_chain_file in the bind_to_key_and_certificate is not thread safe right? I think when multiple threads entered this function can cause the server crash.



Go to page: 1 2 3 4 [5] 6 7 8 9 ... Last