Language:
switch to room list switch to menu My folders
Go to page: 1 2 3 4 [5] 6 7 8 9 ... Last
[#] Sat Sep 23 2023 00:12:38 EDT from IGnatius T Foobar

Subject: Re: installing on AmazonLinux (or any ARM, really)

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

I get a similar error on Ubuntu:

All right, I've gone ahead and updated the OS detection logic in Easy Install and tried it on both Amazon Linux and Ubuntu, both on ARM. Both detect the OS correctly.

That having been said, you really might want to have a look at the Docker version of Citadel; it's the same software but it's much easier to get running.

[#] Sat Sep 23 2023 07:02:11 EDT from p.agsten

Subject: Citadel Server stopped sending mails out

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

Dear All,

couple of days back server stopped sending mails. Notices because of an error message coming back with SMTP code 412. Receiving is fine, no issues.

In the logs I keep seeing this message:

Sep 23 12:56:17 citserver[5959]: citserver[5959]: msgbase: message #97535 was not found
Sep 23 12:56:17 citserver[5959]: citserver[5959]: smtpclient: 97535 does not exist
Sep 23 12:56:17 citserver[5959]: msgbase: message #97535 was not found
Sep 23 12:56:17 citserver[5959]: smtpclient: 97535 does not exist

Thought maybe database had issues so restored a backup from before last time message was sent successfully. But this did not change anything. No mail goes out and the error also reappears. I therefore guess it is unrelated.

When I login as admin in Webcit and go to outbound SMTP queue it is showing:

As there are mails pending that have not been delivered, I would have expected to see them here.

Any ideas would be much welcome.

Thanks,

P.

         


[#] Sat Sep 23 2023 13:23:21 EDT from javier.putterman

Subject: Re: Rebooted my RHEL 8.8 instance and now Citadel crashes upon start...

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

Tried re-running the Easy Install, but that crapped out too after it started up.

I guess I can try just blowing it all away and start from scratch, but I'd rather not.

Definitely bombs out at the segfault mentioned above. 

 



[#] Sat Sep 23 2023 14:01:41 EDT from IGnatius T Foobar

Subject: Re: Rebooted my RHEL 8.8 instance and now Citadel crashes upon start...

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

Tried re-running the Easy Install, but that crapped out too after it
started up.

Ok, one more time.

You should definitely wipe out /usr/local/ctdlsupport, /usr/local/citadel, and /usr/local/webcit before continuing.

I made some tweaks to Easy Install and tested it on a brand new RHEL installation.
It worked for me.

[#] Sat Sep 23 2023 14:06:48 EDT from javier.putterman

Subject: Re: Rebooted my RHEL 8.8 instance and now Citadel crashes upon start...

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

Yep. Doing that right now. Thank you.

 



[#] Sat Sep 23 2023 14:29:43 EDT from javier.putterman

Subject: Re: Rebooted my RHEL 8.8 instance and now Citadel crashes upon start...

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

I got through the Easy Install after deleting those folders and cleaning everything up, seemed to install just fine, but...

Then it crashed as I was re-creating an email account through the web interface. I saved the changes, and then it lost connection.

Checked systemctl status citadel on the server, and it looks like the same exact segfault issue again.

It's strange because it was working perfectly fine for over a week, and I was starting to create a few accounts, and then this happened. Actually, now that I'm thinking about it, I think this started when I changed something from the web interface the first time.

FWIW I'm running: Red Hat Enterprise Linux release 8.8 (Ootpa).

It's frustrating because I was really starting to dig Citadel, and then this. 

Everything else on that server is running fine. Didn't do a yum update until AFTER the first time this happened. 

Weird.

Thanks for looking into it, thought. Much appreciated.

Cheers,

-JP

 

 

 



[#] Sat Sep 23 2023 15:10:08 EDT from javier.putterman

Subject: Re: Rebooted my RHEL 8.8 instance and now Citadel crashes upon start...

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

Sir,

Here's what I've been able to figure out, so far, not that I entirely understand it:

When I write data to the server using the web app via HTTP (8080), it's fine, but...

If I do the same thing via HTTPS (8443) it crashes and the server poops the bed with the same segfault error until I blow it all away and start over.

Something happens when I write to the server from 8443. It's the only variable I changed that lead it to crash. And it was working for a while just using 8080, so...

Will do it again to confirm.

I hope this helps. 

Cheers,

-JP

 



[#] Sat Sep 23 2023 19:53:24 EDT from IGnatius T Foobar

Subject: Re: Rebooted my RHEL 8.8 instance and now Citadel crashes upon start...

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

Can I ask why you're using RHEL in the first place? Are you running Citadel inside an organization that needs their paid support?

[#] Sun Sep 24 2023 05:07:17 EDT from p.agsten

Subject: Re: Citadel Server stopped sending mails out

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

Dear All,

eventually found the issue. Somehow Citadel was no longer able to resolve names. Removed systemd-resolved and completely reconfigured. Afterwards resolution was working again resolving the issue.

Now the only remaining question is how to address the error messages related to message #97535.

Any ideas here?

P.

 

Sat Sep 23 2023 07:02:11 EDT from p.agsten Subject: Citadel Server stopped sending mails out

Dear All,

couple of days back server stopped sending mails. Notices because of an error message coming back with SMTP code 412. Receiving is fine, no issues.

In the logs I keep seeing this message:

Sep 23 12:56:17 citserver[5959]: citserver[5959]: msgbase: message #97535 was not found
Sep 23 12:56:17 citserver[5959]: citserver[5959]: smtpclient: 97535 does not exist
Sep 23 12:56:17 citserver[5959]: msgbase: message #97535 was not found
Sep 23 12:56:17 citserver[5959]: smtpclient: 97535 does not exist

Thought maybe database had issues so restored a backup from before last time message was sent successfully. But this did not change anything. No mail goes out and the error also reappears. I therefore guess it is unrelated.

When I login as admin in Webcit and go to outbound SMTP queue it is showing:

As there are mails pending that have not been delivered, I would have expected to see them here.

Any ideas would be much welcome.

Thanks,

P.

         


 



[#] Sun Sep 24 2023 13:36:24 EDT from IGnatius T Foobar

Subject: Re: Citadel Server stopped sending mails out

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

Now the only remaining question is how to address the error messages related

to message #97535.

Any ideas here?

There might be a message in the queue that has that number but it isn't there anymore. If that is the case, the mail delivery system will give up after five days and you will stop receiving that message. If you feel like tinkering, the queue is in a hidden room called __CitadelSMTPspoolout__ and you can poke around in there looking for it.

[#] Mon Sep 25 2023 11:19:38 EDT from javier.putterman

Subject: Re: Rebooted my RHEL 8.8 instance and now Citadel crashes upon start...

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

So...after about the 2nd or 3rd re-Easy Install, I was able to make changes in the db from :8443 without it crashing, and it's been up and just fine ever since.

About RHEL...I inherited it with the project. There's a subscription already in place, and I've never messed with RHEL much, so now's my chance, I guess. 

My only previous linux experience had been with the Ubuntu and Centos flavors.

Thank you for the help. 

Cheers,

JP



[#] Tue Sep 26 2023 09:58:03 EDT from cjonline

Subject: Re: Rebooted my RHEL 8.8 instance and now Citadel crashes upon start...

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

Hi, Can you please tell me how you fixed this?  getting similar messages on rasbian.

 

Craig.



[#] Tue Sep 26 2023 10:03:11 EDT from cjonline

Subject: Citadel wont start after EASY INSTALL upgrade to 944 (rasbian)

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

Hi,

I've been using citadel for a few months and decided to upgrade to the latest and greatest version with easy install.. I have done this before on previous version with success, however, this time the install ran through fine, but at the point where it stops the services and restarts the install failed to connect.. it bombed to the shell.   I tried to start citadel from command line but it starts then segfaults a few seconds later... please help as this is my main email.

 

thanks

Craig.  (log below) 

 

Sep 26 14:51:16 victor.cajsoft.co.uk citserver[9846]: rssclient: using libcurl/7.64.0 OpenSSL/1.1.1n zlib/1.2.11 libidn2/2.2.0 libpsl/0.20.2 (+lib

Sep 26 14:51:16 victor.cajsoft.co.uk citserver[9846]: extensions: TCP port 0.0.0.0:25: (SMTP-MTA) registered.

Sep 26 14:51:16 victor.cajsoft.co.uk citserver[9846]: extensions: TCP port 0.0.0.0:465: (SMTPs-MTA) registered.

Sep 26 14:51:16 victor.cajsoft.co.uk citserver[9846]: extensions: TCP port 0.0.0.0:587: (SMTP-MSA) registered.

Sep 26 14:51:16 victor.cajsoft.co.uk citserver[9846]: extensions: unix domain socket 'lmtp.socket': registered.

Sep 26 14:51:16 victor.cajsoft.co.uk citserver[9846]: extensions: unix domain socket 'lmtp-unfiltered.socket': registered.

Sep 26 14:51:16 victor.cajsoft.co.uk citserver[9846]: citserver[9846]: Existing database version on disk is 994

Sep 26 14:51:16 victor.cajsoft.co.uk citserver[9846]: Existing database version on disk is 994

Sep 26 14:51:16 victor.cajsoft.co.uk citserver[9846]: citserver[9846]: extensions: service DICT_TCP has been manually disabled, skipping

Sep 26 14:51:16 victor.cajsoft.co.uk citserver[9846]: citserver[9846]: extensions: TCP port 0.0.0.0:5222: (XMPP) registered.

Sep 26 14:51:16 victor.cajsoft.co.uk citserver[9846]: extensions: service DICT_TCP has been manually disabled, skipping

Sep 26 14:51:16 victor.cajsoft.co.uk citserver[9846]: citserver[9846]: main: changing uid to 112

Sep 26 14:51:16 victor.cajsoft.co.uk citserver[9846]: extensions: TCP port 0.0.0.0:5222: (XMPP) registered.

Sep 26 14:51:16 victor.cajsoft.co.uk citserver[9846]: main: changing uid to 112

Sep 26 14:51:17 victor.cajsoft.co.uk citserver[9846]: citserver[9846]: context: session (SMTP-MSA) started from 77.90.185.59 (77.90.185.59) uid=-1

Sep 26 14:51:17 victor.cajsoft.co.uk citserver[9846]: context: session (SMTP-MSA) started from 77.90.185.59 (77.90.185.59) uid=-1

Sep 26 14:51:18 victor.cajsoft.co.uk systemd[1]: citadel.service: Main process exited, code=killed, status=11/SEGV

-- Subject: Unit process exited

-- Defined-By: systemd

-- Support: https://www.debian.org/support

--

-- An ExecStart= process belonging to unit citadel.service has exited.

--

-- The process' exit code is 'killed' and its exit status is 11.

Sep 26 14:51:18 victor.cajsoft.co.uk systemd[1]: citadel.service: Failed with result 'signal'.

-- Subject: Unit failed

-- Defined-By: systemd

-- Support: https://www.debian.org/support

--

-- The unit citadel.service has entered the 'failed' state with result 'signal'.

Sep 26 14:51:18 victor.cajsoft.co.uk systemd[1]: citadel.service: Service RestartSec=100ms expired, scheduling restart.

Sep 26 14:51:18 victor.cajsoft.co.uk systemd[1]: citadel.service: Scheduled restart job, restart counter is at 5.

-- Subject: Automatic restarting of a unit has been scheduled

-- Defined-By: systemd

-- Support: https://www.debian.org/support

--

-- the configured Restart= setting for the unit.

Sep 26 14:51:18 victor.cajsoft.co.uk systemd[1]: Stopped Citadel Server.

-- Subject: A stop job for unit citadel.service has finished

-- Defined-By: systemd

-- Support: https://www.debian.org/support

--

-- A stop job for unit citadel.service has finished.

--

-- The job identifier is 24163 and the job result is done.

Sep 26 14:51:18 victor.cajsoft.co.uk systemd[1]: citadel.service: Start request repeated too quickly.

Sep 26 14:51:18 victor.cajsoft.co.uk systemd[1]: citadel.service: Failed with result 'signal'.

-- Subject: Unit failed

-- Defined-By: systemd

-- Support: https://www.debian.org/support

--

-- The unit citadel.service has entered the 'failed' state with result 'signal'.

Sep 26 14:51:18 victor.cajsoft.co.uk systemd[1]: Failed to start Citadel Server.

-- Subject: A start job for unit citadel.service has failed

-- Defined-By: systemd

-- Support: https://www.debian.org/support

--

-- A start job for unit citadel.service has finished with a failure.

--

-- The job identifier is 24163 and the job result is failed.

-- Automatic restarting of the unit citadel.service has been scheduled, as the result for

 


[#] Tue Sep 26 2023 10:11:16 EDT from Nurb432

Subject: Re: Citadel wont start after EASY INSTALL upgrade to 944 (rasbian)

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

Cant help with the crash, but you did make a backup right? Could always roll back and do some testing with coming suggestions.  

Tue Sep 26 2023 10:03:11 EDT from cjonline Subject: Citadel wont start after EASY INSTALL upgrade to 944 (rasbian)

 please help as this is my main email.

 



[#] Tue Sep 26 2023 10:38:56 EDT from cjonline

Subject: Re: Citadel wont start after EASY INSTALL upgrade to 944 (rasbian)

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

Would you believe it.. NO I didnt as the previous upgrade I did I made a backup but it went smoothly so thought it wouldnt be needed :(

how I was wrong !

 

Craig.

 

Tue Sep 26 2023 10:11:16 EDT from Nurb432 Subject: Re: Citadel wont start after EASY INSTALL upgrade to 944 (rasbian)

Cant help with the crash, but you did make a backup right? Could always roll back and do some testing with coming suggestions.  

Tue Sep 26 2023 10:03:11 EDT from cjonline Subject: Citadel wont start after EASY INSTALL upgrade to 944 (rasbian)

 please help as this is my main email.

 



 



[#] Tue Sep 26 2023 10:52:42 EDT from Nurb432

Subject: Re: Citadel wont start after EASY INSTALL upgrade to 944 (rasbian)

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

Darn. i always do that even if i have tested it. you never know. power fail, OS freak out = corrupted files = ack!

Once the others see this i'm sure you will be getting suggestions.  



[#] Tue Sep 26 2023 11:04:54 EDT from cjonline

Subject: Re: Citadel wont start after EASY INSTALL upgrade to 944 (rasbian)

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

I know.. I made a BIG mistake.. I usually do back up but thought this time it would be ok!!

 

I've tried clearing down the citadel folders /usr/local/citadel and /usr/local/webcit, then ran the easy install.. it runs fine but crashes at the setup phase.  I suspect it's something to do with the latest version and the new db functions?

 

Tue Sep 26 2023 10:52:42 EDT from Nurb432 Subject: Re: Citadel wont start after EASY INSTALL upgrade to 944 (rasbian)

Darn. i always do that even if i have tested it. you never know. power fail, OS freak out = corrupted files = ack!

Once the others see this i'm sure you will be getting suggestions.  



 



[#] Tue Sep 26 2023 11:38:17 EDT from Nurb432

Subject: Re: Citadel wont start after EASY INSTALL upgrade to 944 (rasbian)

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

once IG sees the post im sure he will have ideas. 



[#] Tue Sep 26 2023 12:49:41 EDT from IGnatius T Foobar

Subject: Re: Citadel wont start after EASY INSTALL upgrade to 944 (rasbian)

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


Perhaps we can get more information.

First, flog yourself with a wet noodle for disregarding common sense about taking backups. You should be backing up every day, not just when you're about to perform an upgrade. Use a filesystem like `btrfs` or `zfs` which can make instant snapshots, then rsync those snapshots to a backup location.

Then shut down the systemd unit file for Citadel (`systemctl stop citadel`).
It's ok to leave the web interface running.

Run the Citadel Server in the foreground with maximum debugging:

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

If there is really a problem with the server software, it will crash with maximum logging right in front of you. You can post the last screenful or so of the output and perhaps it will tell us more.

For "even more" information, you can try running it in the debugger:

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

If it crashes, post the last screenful up to the crash, then do `thread apply all bt` and stash that output too, just in case we need it.

[#] Tue Sep 26 2023 15:19:09 EDT from cjonline

Subject: Re: Citadel wont start after EASY INSTALL upgrade to 944 (rasbian)

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

./citserver -x9

citserver[1776]: extensions: finished initializing modules (threading=1)

citserver[1776]: sysdep: new client socket 39

citserver[1776]: fulltext: indexing started. msgs 6996--7111

citserver[1776]: msgbase: CtdlFetchMessage(6997, 1)

citserver[1776]: fulltext: ft_index_message() adding msg 6997

citserver[1776]: msgbase: CtdlOutputPreLoadedMsg(TheMessage=not null, 0, 0, 0, 1

citserver[1776]: msgbase: fixed_output() part 1:  (text/html) (35175 bytes)

citserver[1776]: context: session (SMTPs-MTA) started from 46.148.40.151 (46.148.40.151) uid=-1

citserver[1776]: crypto: using certificate chain keys/citadel.cer

citserver[1776]: crypto: using private key keys/citadel.key

citserver[1776]: fulltext: wordbreaking message 6997 (79 bytes)

citserver[1776]: fulltext: indexing message 6997 [0 tokens]

citserver[1776]: msgbase: CtdlFetchMessage(6998, 1)

citserver[1776]: fulltext: ft_index_message() adding msg 6998

citserver[1776]: msgbase: CtdlOutputPreLoadedMsg(TheMessage=not null, 0, 0, 0, 1

citserver[1776]: msgbase: fixed_output() part 1:  (text/html) (53736 bytes)

citserver[1776]: fulltext: wordbreaking message 6998 (0 bytes)

 

Segmentation fault

------------
 
 
gdb ./citserver
run -x9


citserver[2086]: extensions: finished initializing modules (threading=1)
[New Thread 0xb3f5c200 (LWP 2089)]
[New Thread 0xb3e5b200 (LWP 2090)]
citserver[2086]: fulltext: indexing started. msgs 6996--7111
citserver[2086]: msgbase: CtdlFetchMessage(6997, 1)
citserver[2086]: fulltext: ft_index_message() adding msg 6997
citserver[2086]: msgbase: CtdlOutputPreLoadedMsg(TheMessage=not null, 0, 0, 0, 1
citserver[2086]: msgbase: fixed_output() part 1:  (text/html) (35175 bytes)
citserver[2086]: fulltext: wordbreaking message 6997 (79 bytes)
citserver[2086]: fulltext: indexing message 6997 [0 tokens]
citserver[2086]: msgbase: CtdlFetchMessage(6998, 1)
citserver[2086]: fulltext: ft_index_message() adding msg 6998
citserver[2086]: msgbase: CtdlOutputPreLoadedMsg(TheMessage=not null, 0, 0, 0, 1
citserver[2086]: msgbase: fixed_output() part 1:  (text/html) (53736 bytes)
citserver[2086]: fulltext: wordbreaking message 6998 (0 bytes)

Thread 2 "citserver" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb3f5c200 (LWP 2089)]
array_len (arr=0x0) at lib/array.c:71
71      lib/array.c: No such file or directory.

--------
thread apply all bt
 
Thread 3 (Thread 0xb3e5b200 (LWP 2090)):
#0  __GI___select (timeout=0xbeffe4ea, exceptfds=0x0, writefds=0x0, readfds=0xb3e5ab54, nfds=39) at ../sysdeps/unix/sysv/linux/select.c:41
#1  __GI___select (nfds=39, readfds=0xb3e5ab54, writefds=0x0, exceptfds=0x0, timeout=0xb3e5ab4c) at ../sysdeps/unix/sysv/linux/select.c:37
#2  0x000278f8 in worker_thread (blah=0x0) at server/sysdep.c:730
#3  0xb6c98494 in start_thread (arg=0xb3e5b200) at pthread_create.c:486
#4  0xb6a3be98 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 2 (Thread 0xb3f5c200 (LWP 2089)):
#0  array_len (arr=0x0) at lib/array.c:71
#1  0x00059000 in ft_index_message (msgnum=6998, op=1) at server/modules/fulltext/serv_fulltext.c:97
#2  0x00059604 in do_fulltext_indexing () at server/modules/fulltext/serv_fulltext.c:237
#3  0x00039474 in PerformSessionHooks (EventType=12) at server/serv_extensions.c:469
#4  0x00037278 in do_housekeeping () at server/housekeeping.c:130
#5  0x00027e90 in worker_thread (blah=0x0) at server/sysdep.c:876
#6  0xb6c98494 in start_thread (arg=0xb3f5c200) at pthread_create.c:486
#7  0xb6a3be98 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0xb6fefe00 (LWP 2086)):
#0  __GI___nanosleep (remaining=0x0, requested_time=0xbeffe564) at ../sysdeps/unix/sysv/linux/nanosleep.c:28
#1  __GI___nanosleep (requested_time=0xbeffe564, requested_time@entry=0xbeffe55c, remaining=remaining@entry=0x0)
    at ../sysdeps/unix/sysv/linux/nanosleep.c:25
#2  0xb6a358e0 in usleep (useconds=<optimized out>) at ../sysdeps/posix/usleep.c:32
#3  0x00036b18 in go_threading () at server/threads.c:96
#4  0x00025888 in main (argc=2, argv=0xbefff744) at server/server_main.c:293
 
 


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