Language:

en_US

switch to room list switch to menu My folders
Go to page: First ... 16 17 18 19 [20] 21 22
[#] Mon Dec 09 2024 17:08:43 UTC from night

Subject: Re: ports?

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

 

Mon Dec 09 2024 02:38:11 UTC from night Subject: Re: ports?

1st port check was freshly installed.

2nd was a fresh installation of citadel

3rd was a different port check.

 

I've also noticed one other weird thing. When I go to administration and press restart, the server shuts down but doesn't restart. I have to reboot the system.

 

Thank you for helping

Night



Would it help the support team of citadel to have ssh access to a fresh install of the OS?

 

Night



[#] Mon Dec 09 2024 20:29:28 UTC from ParthChaudhary

Subject: Regarding tool deployment and its functionality

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

Hi Everyone.
I have installed this tool on linux using the easy install method and trying the tool .
Previously I was able to add attendees and also send invites to a meeting or event created in calendar to others which I am unable to do it now.
Also If I try to install the tool using the source code I am unable to do it as I cant install the berkeleydb.
I created an account on oracle and downloaded the wget.sh file for linux but it says while ./configure and make file missing.
Provide some help....



[#] Tue Dec 10 2024 08:09:11 UTC from alperumit

Subject: Re: Citserver crash "malloc.c:2379: sysmalloc: Assertion"

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

Hello All,

Have you had a chance to look into this issue? My Exchange replacement project has unfortunately stalled. I am not allowed to proceed without RCA. Any ideas? Thank you for your help in advance. 

 

Wed Dec 04 2024 09:39:47 UTC from alperumit Subject: Citserver crash "malloc.c:2379: sysmalloc: Assertion"

Hello everyone,

 

I don't know the reason yet and I'm not sure how to reproduce the problem bu If you can guide me I'll try to provide more information. For now, I can say that while I'm asleep ( isn't it always like that :) ) citserver crashes with the following log. Then it restarts itself and crashes again. This continues. I hope you can help me. Thank you very much in advance.

First Crash Logs

{"log":"citserver[3664]: msgbase: fixed_output_pre() type=\u003cmultipart/mixed\u003e\n","stream":"stderr","time":"2024-12-03T18:15:13.77452087Z"}

{"log":"citserver[3664]: msgbase: fixed_output() part 1:  (text/html) (107493 bytes)\n","stream":"stderr","time":"2024-12-03T18:15:13.77474904Z"}

{"log":"citserver[3664]: ZBO2 SELECT Inbox\n","stream":"stderr","time":"2024-12-03T18:15:13.775558266Z"}

{"log":"citserver[3664]: ---- Looking up [SELECT] -----\n","stream":"stderr","time":"2024-12-03T18:15:13.775570699Z"}

{"log":"citserver[3664]: Found.\n","stream":"stderr","time":"2024-12-03T18:15:13.77557505Z"}

{"log":"citserver[3664]: \u001b[33mimap: imap_roomname(Inbox) returned(ret=0, floor=0, is_mailbox=1, roomname=Mail)\u001b[0m\n","stream":"stderr","time":"2024-12-03T18:15:13.775579122Z"}

{"log":"citserver[3664]: imap_do_expunge() called\n","stream":"stderr","time":"2024-12-03T18:15:13.775583578Z"}

{"log":"citserver[3664]: room_ops: 0000000016.Mail : 1 seen of 1 total messages, oldest=88, newest=88\n","stream":"stderr","time":"2024-12-03T18:15:13.775587407Z"}

{"log":"citserver[3664]: IMAP command completed in 0.349 seconds\n","stream":"stderr","time":"2024-12-03T18:15:13.775591427Z"}

{"log":"citserver[3664]: bnBzdXBwb3J0QGRhZmFiZXQuY29t\n","stream":"stderr","time":"2024-12-03T18:15:13.804031904Z"}

{"log":"citserver[3664]: user_ops: CtdlLoginExistingUser(****@****)\n","stream":"stderr","time":"2024-12-03T18:15:13.804070642Z"}

{"log":"citserver[3664]: internet_addressing: directory key is \u003c****@****\u003e\n","stream":"stderr","time":"2024-12-03T18:15:13.80422317Z"}

{"log":"citserver[3664]: internet_addressing: directory alias \u003c****@****\u003e to \u003c****-****\u003e\n","stream":"stderr","time":"2024-12-03T18:15:13.804246595Z"}

{"log":"citserver[3664]: Recipient #0 of type 2 is \u003c****-****\u003e\n","stream":"stderr","time":"2024-12-03T18:15:13.804268809Z"}

{"log":"citserver[3664]: internet_addressing: validate_recipients() = 1 local, 0 room, 0 SMTP, 0 error\n","stream":"stderr","time":"2024-12-03T18:15:13.804319842Z"}

{"log":"malloc(): invalid next size (unsorted)\n","stream":"stderr","time":"2024-12-03T18:15:13.806072112Z"}

{"log":"ctdlvisor: pid=3664 exited, status=134, exitcode=0\n","stream":"stderr","time":"2024-12-03T18:15:14.269828826Z"}

{"log":"ctdlvisor: citserver crashed on signal 6\n","stream":"stderr","time":"2024-12-03T18:15:14.269871183Z"}

{"log":"ctdlvisor: citserver running on pid=5420\n","stream":"stderr","time":"2024-12-03T18:15:14.269950552Z"}

{"log":"ctdlvisor: executing citserver\n","stream":"stderr","time":"2024-12-03T18:15:14.269967024Z"}

 

Second Crash Logs

{"log":"citserver[5420]: test: module is disabled\n","stream":"stderr","time":"2024-12-03T18:15:46.022969103Z"}

{"log":"citserver[5420]: extensions: init test\n","stream":"stderr","time":"2024-12-03T18:15:46.022999481Z"}

{"log":"citserver[5420]: extensions: init upgrade\n","stream":"stderr","time":"2024-12-03T18:15:46.023012507Z"}

{"log":"citserver[5420]: extensions: init vcard\n","stream":"stderr","time":"2024-12-03T18:15:46.023041989Z"}

{"log":"citserver[5420]: extensions: init wiki\n","stream":"stderr","time":"2024-12-03T18:15:46.023091718Z"}

{"log":"citserver[5420]: extensions: init xmpp\n","stream":"stderr","time":"2024-12-03T18:15:46.02310597Z"}

{"log":"citserver[5420]: extensions: init netconfig\n","stream":"stderr","time":"2024-12-03T18:15:46.023140815Z"}

{"log":"citserver[5420]: extensions: finished initializing modules (threading=1)\n","stream":"stderr","time":"2024-12-03T18:15:46.023161433Z"}

{"log":"webcit[9]: language found: en_US\n","stream":"stderr","time":"2024-12-03T18:15:46.230470541Z"}

{"log":"citserver[5420]: sysdep: new client socket 32\n","stream":"stderr","time":"2024-12-03T18:15:46.231069354Z"}

{"log":"citserver[5420]: fulltext: indexing started. msgs 110407--110408\n","stream":"stderr","time":"2024-12-03T18:15:46.231081849Z"}

{"log":"citserver[5420]: context: session (citadel-UDS) started from  () uid=-1\n","stream":"stderr","time":"2024-12-03T18:15:46.23108641Z"}

{"log":"webcit[9]: Client is at ::ffff:172.23.34.2\n","stream":"stderr","time":"2024-12-03T18:15:46.232542646Z"}

{"log":"citserver[5420]: [(not logged in)(0)] MSGP application/x-citadel-delivery-list|text/calendar|application/ics|text/vnote|text/x-vcard|text/vcard|text/html|text/plain|text/x-citadel-variformat|text/x-markdown\n","stream":"stderr","time":"2024-12-03T18:15:46.232643436Z"}

{"log":"citserver[5420]: [(not logged in)(0)] MESG hello\n","stream":"stderr","time":"2024-12-03T18:15:46.23277837Z"}

{"log":"webcit[9]: HTTP: 200 [11.013566] GET \n","stream":"stderr","time":"2024-12-03T18:15:46.232873461Z"}

{"log":"citserver[5420]: msgbase: CtdlFetchMessage(110408, 1)\n","stream":"stderr","time":"2024-12-03T18:15:46.233912312Z"}

{"log":"citserver[5420]: fulltext: ft_index_message() adding msg 110408\n","stream":"stderr","time":"2024-12-03T18:15:46.234223191Z"}

{"log":"citserver[5420]: msgbase: CtdlOutputPreLoadedMsg(TheMessage=not null, 0, 0, 0, 1\n","stream":"stderr","time":"2024-12-03T18:15:46.23426493Z"}

{"log":"citserver[5420]: msgbase: fixed_output_pre() type=\u003cmultipart/mixed\u003e\n","stream":"stderr","time":"2024-12-03T18:15:46.234434983Z"}

{"log":"citserver[5420]: msgbase: fixed_output() part 1:  (text/html) (107493 bytes)\n","stream":"stderr","time":"2024-12-03T18:15:46.234735738Z"}

{"log":"citserver: malloc.c:2379: sysmalloc: Assertion `(old_top == initial_top (av) \u0026\u0026 old_size == 0) || ((unsigned long) (old_size) \u003e= MINSIZE \u0026\u0026 prev_inuse (old_top) \u0026\u0026 ((unsigned long) old_end \u0026 (pagesize - 1)) == 0)' failed.\n","stream":"stderr","time":"2024-12-03T18:15:46.266152398Z"}

{"log":"ctdlvisor: pid=5420 exited, status=134, exitcode=0\n","stream":"stderr","time":"2024-12-03T18:15:46.271281561Z"}

{"log":"ctdlvisor: citserver crashed on signal 6\n","stream":"stderr","time":"2024-12-03T18:15:46.271294147Z"}

{"log":"ctdlvisor: citserver running on pid=5423\n","stream":"stderr","time":"2024-12-03T18:15:46.271388146Z"}

{"log":"ctdlvisor: executing citserver\n","stream":"stderr","time":"2024-12-03T18:15:46.271400291Z"}

 



 



[#] Tue Dec 10 2024 23:06:18 UTC from IGnatius T Foobar

Subject: Re: Citserver crash "malloc.c:2379: sysmalloc: Assertion"

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


Are you able to provide a stack trace? Please do so if you can. Or indicate if you need help doing that.

[#] Wed Dec 11 2024 07:47:08 UTC from alperumit

Subject: Re: Citserver crash "malloc.c:2379: sysmalloc: Assertion"

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

Hello, thank you for your reply. I'll need your guidance to provide a stack trace or any other information. I'll do my best. Thank you. 



[#] Wed Dec 11 2024 13:59:34 UTC from IGnatius T Foobar

Subject: Re: Citserver crash "malloc.c:2379: sysmalloc: Assertion"

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

Hello, thank you for your reply. I'll need your guidance to
provide a stack trace or any other information. I'll do my best.

If you have a core dump, you can start the debugger with

gdb /usr/local/citadel/citserver <path to core file>

Otherwise you have to run citserver *in* the debugger. Stop the service and then restart it with:

cd /usr/local/citadel
gdb ./citserver
run -x9

If you have the core file, it will bring the debugger up at the point where it crashed. Otherwise you will have to wait for it to crash again. At that point:

thread apply all bt

...and post the output. Obviously if you're able to come up with a set of steps and/or inputs that reliably crash the server every time, we can try to replicate them, but if it's only crashing for you then the stack trace will hopefully do the trick.

[#] Tue Dec 17 2024 10:12:25 UTC from alperumit

Subject: Re: Citserver crash "malloc.c:2379: sysmalloc: Assertion"

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

Hello again,

 

I am sorry for the late response, I needed to figure out how to do it in the container. I hope I got what you wanted. Please check the attachment. Thanks again for your help. 



core.10533.txt (text/plain, 10299 bytes) [View| Download]
[#] Fri Dec 20 2024 20:12:28 UTC from IGnatius T Foobar

Subject: Re: Citserver crash "malloc.c:2379: sysmalloc: Assertion"

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


Wow. Ok, so someone sent you a message (probably spam) that crashes the server whenever it tries to parse it. If that message is going into the indexer or something then it's probably trying over and over again.

Do you think you could find a way to get a copy of the raw RFC822 source of that message? If so, please drop it either here or somewhere safe (as a .zip or .tar attachment) and we'll see if we can get it to reliably crash the parser on any read.

If not, debugging will be harder, but we'll definitely try.

[#] Fri Dec 20 2024 20:23:16 UTC from IGnatius T Foobar

Subject: Re: Citserver crash "malloc.c:2379: sysmalloc: Assertion"

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


Also ... from the look of that stack trace, it is confirmed that the server is crashing every time the indexer tries to parse that message. So as a temporary workaround you can turn off full text indexing on your server (it's in the global system settings) and you won't get that crash unless you try to read the poison email with the text client.

The bug is somewhere in the HTML to Text conversion function. We'll find it one way or another, but we'll find it a lot faster if you can supply the message that is crashing it.

[#] Fri Dec 27 2024 21:22:42 UTC from Will.i.am

Subject: unstaking IOST in citadel wallet

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

Why cannot not use the password I originally used to get this far ??? help



Screenshot 2024-12-28 at 10.21.12 (image/png, 213851 bytes) [ View | Download ]
[#] Fri Dec 27 2024 22:38:34 UTC from IGnatius T Foobar

Subject: Re: unstaking IOST in citadel wallet

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

Why cannot not use the password I originally used to get this far ???
help

Because I took all of your money. I can put it to better use than you can.

[#] Fri Dec 27 2024 23:33:29 UTC from Kurisu

Subject: Re: unstaking IOST in citadel wallet

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

This amused me far more than it should have. :D

 

Fri Dec 27 2024 22:38:34 UTC from IGnatius T Foobar Subject: Re: unstaking IOST in citadel wallet
Why cannot not use the password I originally used to get this far ???
help

Because I took all of your money. I can put it to better use than you can.

Anyway, were I in need of support I guess i would take this time to ask for help, but that's if I had a major problem that I needed assistance with... which I don't, so, yeah.



[#] Sat Dec 28 2024 01:13:04 UTC from IGnatius T Foobar

Subject: Re: unstaking IOST in citadel wallet

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

Heh. You should have been here in 1996 when a clueless journalist who thought she had stumbled across a message board populated by cadets at The Citadel, and asked us what we thought about the academy going co-ed. We gave her all sorts of great gossip about secret ceremonies with ritual sacrifices, and other wonderful inside information.

[#] Sat Dec 28 2024 02:20:21 UTC from Kurisu

Subject: Re: unstaking IOST in citadel wallet

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

HAHA! Ah, yes, I truly wish I had been here for that one. Sadly before my time with a computer of my own to speak of, for sure. :)

Still a nice story to hear about, even nearly 30 years after the fact.

Sat Dec 28 2024 01:13:04 UTC from IGnatius T Foobar Subject: Re: unstaking IOST in citadel wallet
Heh. You should have been here in 1996 when a clueless journalist who thought she had stumbled across a message board populated by cadets at The Citadel, and asked us what we thought about the academy going co-ed. We gave her all sorts of great gossip about secret ceremonies with ritual sacrifices, and other wonderful inside information.

 



[#] Thu Jan 02 2025 00:00:45 UTC from darkoff

Subject: RSpamd Integration

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

Hi,

I would like to know if it is possible to use an antispam other than SpamAssassin, and in this case RSpamd? I am trying to integrate RSpamd directly on Citadel (in the manner of spamassassin) without success.

 

Thanks in advance for your answers! :)



[#] Thu Jan 02 2025 08:00:44 UTC from jiten

Subject: Email Setup

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

How Do I setup email that citadel will send and received email from upstream provider (gmail, zoho) and serve it as imap to local network. ??

 

 



[#] Fri Jan 03 2025 00:57:47 UTC from IGnatius T Foobar

Subject: Re: RSpamd Integration

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

I would like to know if it is possible to use an antispam other
than SpamAssassin, and in this case RSpamd? I am trying to
integrate RSpamd directly on Citadel (in the manner of
spamassassin) without success.

You can use any spam filter you want, but SpamAssassin is the only one that can be directly integrated into Citadel's MTA.

Any other filter must be set up in the conventional manner: you have some other MTA listening on port 25, emails are passed through the filter and then forwarded to Citadel's MDA. Most mailers support final delivery via LMTP over a local socket, and Citadel has that available on /usr/local/citadel/lmtp.socket


rspamd does appear to have a client protocol, so it's conceptually possible to write a Citadel module for it. But such a module does not currently exist.

[#] Fri Jan 03 2025 00:58:09 UTC from IGnatius T Foobar

Subject: Re: Email Setup

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

How Do I setup email that citadel will send and received email
from upstream provider (gmail, zoho) and serve it as imap to
local network. ??

smart-host rule for outbound, and remote retrieval rule for inbound.

[#] Fri Jan 03 2025 04:58:42 UTC from jiten

Subject: Re: Email Setup

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

thanks.

Any link to documentation for smart-host and remote retrieval Please.

 



[#] Sun Jan 12 2025 17:36:13 UTC from sankalpa

Subject: Citserver crash when using SSL

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

Hi Everyone,

 

Everytime I try to connect to citadel via IMAPS or POP3S I get a crash when using SSL

citadel-1  | citserver[8]: context: session (IMAP) started from 77-172-227-99.fixed.kpn.net (77.172.227.99) uid=-1

citadel-1  | citserver[8]: 1.385 STARTTLS

citadel-1  | citserver[8]: ---- Looking up [STARTTLS] -----

citadel-1  | citserver[8]: Found.

citadel-1  | citserver[8]: crypto: using certificate chain keys/citadel.cer

citadel-1  | citserver[8]: crypto: using private key keys/citadel.key

citadel-1  | citserver[8]: sysdep: new client socket 36

citadel-1  | citserver[8]: context: session (IMAP) started from 77-172-227-99.fixed.kpn.net (77.172.227.99) uid=-1

citadel-1  | citserver[8]: 1.38 STARTTLS

citadel-1  | citserver[8]: ---- Looking up [STARTTLS] -----

citadel-1  | citserver[8]: Found.

citadel-1  | ctdlvisor: pid=8 exited, status=139, exitcode=0

citadel-1  | ctdlvisor: citserver crashed on signal 11

citadel-1  | ctdlvisor: citserver running on pid=16

 

citadel-1  | ctdlvisor: executing citserver


The certificate I am using where generated with letsencrypt !


Any ideas ?



Go to page: First ... 16 17 18 19 [20] 21 22