Language:
switch to room list switch to menu My folders
Go to page: First ... 5 6 7 8 [9] 10 11 12 13 ... Last
[#] 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
 
 


[#] Wed Sep 27 2023 00:28:29 EDT from IGnatius T Foobar

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

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


All right, this is your lucky day. That was an easy problem to spot and I've published a fix.

Somehow you got a couple of zero-length messages into your system (how?) and the indexer choked on a null word list. Go ahead and do the upgrade again.
Make sure you get at least version 995 of the server.

And start taking daily backups. :)

[#] Wed Sep 27 2023 05:23:46 EDT from cjonline

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

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

Hi, Still not working.. same issue - 

DB version is 995

----

 



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

citserver[18815]: context: session (SMTP-MSA) started from 77.90.185.59 (77.90.185.59) uid=-1

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

Segmentation fault

 
----
 
citserver[18848]: msgbase: CtdlOutputPreLoadedMsg(TheMessage=not null, 0, 0, 0, 1
citserver[18848]: msgbase: fixed_output() part 1:  (text/html) (53736 bytes)
citserver[18848]: fulltext: wordbreaking message 6998 (0 bytes)
 
Thread 2 "citserver" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb3f5c200 (LWP 18854)]
array_len (arr=0x0) at lib/array.c:71
71      lib/array.c: No such file or directory.
 
 
-----
 
Thread 2 (Thread 0xb3f5c200 (LWP 18854)):
#0  array_len (arr=0x0) at lib/array.c:71
#1  0x0005900c in ft_index_message (msgnum=6998, op=1) at server/modules/fulltext/serv_fulltext.c:97
#2  0x00059624 in do_fulltext_indexing () at server/modules/fulltext/serv_fulltext.c:241
#3  0x00039480 in PerformSessionHooks (EventType=12) at server/serv_extensions.c:469
#4  0x00037284 in do_housekeeping () at server/housekeeping.c:130
#5  0x00027ec8 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 18848)):
#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  0x00036b50 in go_threading () at server/threads.c:96
#4  0x000258c0 in main (argc=2, argv=0xbefff744) at server/server_main.c:295
 
Wed Sep 27 2023 00:28:29 EDT from IGnatius T Foobar Subject: Re: Citadel wont start after EASY INSTALL upgrade to 944 (rasbian)

All right, this is your lucky day. That was an easy problem to spot and I've published a fix.

Somehow you got a couple of zero-length messages into your system (how?) and the indexer choked on a null word list. Go ahead and do the upgrade again.
Make sure you get at least version 995 of the server.

And start taking daily backups. :)

 



[#] Thu Sep 28 2023 05:19:24 EDT from cjonline

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

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

Hi IG,

please can you help ?

Craig.



[#] Thu Sep 28 2023 07:26:19 EDT from Nurb432

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

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

He will. Hes got a day job remember :) 

Thu Sep 28 2023 05:19:24 EDT from cjonline Subject: Re: Citadel wont start after EASY INSTALL upgrade to 944 (rasbian)

Hi IG,

please can you help ?

Craig.



 



[#] Thu Sep 28 2023 22:21:22 EDT from IGnatius T Foobar

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

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


All right, one more try. Make sure you get version 996 of the server.

That fix we put in to get around your mysterious null message needed to be a few lines earlier in the code. I hope this fixes it.

[#] Fri Sep 29 2023 05:40:59 EDT from cjonline

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

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

Thank you so much!  that fixed my issue.. will create backups now going forward.

You are the best!

 

Craig.

Thu Sep 28 2023 22:21:22 EDT from IGnatius T Foobar Subject: Re: Citadel wont start after EASY INSTALL upgrade to 944 (rasbian)

All right, one more try. Make sure you get version 996 of the server.

That fix we put in to get around your mysterious null message needed to be a few lines earlier in the code. I hope this fixes it.

 



[#] Fri Sep 29 2023 16:48:00 EDT from IGnatius T Foobar

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

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

Spread the word!

[#] Fri Sep 29 2023 17:24:33 EDT from LadySerenaKitty

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

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

Word the spread!

Fri Sep 29 2023 16:48:00 EDT from IGnatius T Foobar Subject: Re: Citadel wont start after EASY INSTALL upgrade to 944 (rasbian)
Spread the word!

 



[#] Fri Sep 29 2023 17:46:15 EDT from Nurb432

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

all this spreading going on....



[#] Mon Oct 02 2023 08:59:48 EDT from f.giannini

Subject: LDAP - custom email format

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

Hi all,

Can I set a custom email format for LDAP (MS Active Directory) users? The default format is firstname_lastname@domain (e.g.: nome_cognome@domain), I would like firstInitial.lastName@domain (e.g.:n.cognome@domain)

 

Thks

 


[#] Thu Oct 05 2023 12:31:52 EDT from jhwatts

Subject: New Setup Issues by a Newbie

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

 

First things first. I have never set up an email server before, including citadel. I just recently install a copy of citadel on a VirtualBox on my server. How can I verify it is sending and receiving emails appropriately? I sent one to my gmail and one to my yahoo and got the following errors.

 

mygmail.com 550 (550-5.7.26 This mail has been blocked because the sender is unauthenticated.)

 

myyahoo.com 553 (553 5.7.2 [TSS09] All messages from 71.64.132.66 will be permanently deferred; Retrying will NOT succeed. See https://postmaster.yahooinc.com/error-codes )

 

At least it sending. I have clearly sent outgoing mail but neither yahoo or gmail like my email setup. How can I fix this so they will accept my emails?


I used my server key nad crt in place of the citadel ones located in the /usr/local/citadel/keys/ directory. I changed the cert names to citadel.key and citadel.crt.


 

I tried to send email from both yahoo and gmail but received neither.

 

I have made a port forwarding list for the VB allowing all of the ports listed in the citadel administration screen access. It is possible my firewall is blocking. It’s a ubuntu server. Also, I have a Sonicwall on the frontend of my network.

 



[#] Thu Oct 05 2023 18:02:27 EDT from IGnatius T Foobar

Subject: Re: New Setup Issues by a Newbie

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


There's not enough information to troubleshoot. At the very least you should show us your DNS configuration, identify the domain you're trying to use, show that the MX and RDNS records are correct; and show the configuration settings of your Citadel installation.

It'
s also possible that both gmail and yahoo simply reject mail originating from residential address blocks such as the one you are using on Charter Cable.
If that is the case, and you are serious about hosting a "real" Internet server from your home, you might consider a service such as https://www.aceinnovative.com/internet-access/static-ip-vpn/ to place your server on a "real" hosting network with static IP and no port restrictions. (This is not sponsored -- I and other Citadel operators are very happy customers.)

[#] Thu Oct 05 2023 18:16:53 EDT from Nurb432

Subject: Re: New Setup Issues by a Newbie

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

That is one reason i stopped self hosting my mail. Decades ago people started blocking residential IP. Not everone but enough to make it problematic for me then. I'm sure its only got worse. 

Thu Oct 05 2023 18:02:27 EDT from IGnatius T Foobar Subject: Re: New Setup Issues by a Newbie
It's also possible that both gmail and yahoo simply reject mail originating from residential address blocks such as the one you are using on Charter Cable.

 



[#] Thu Oct 05 2023 20:36:38 EDT from jhwatts

Subject: Re: New Setup Issues by a Newbie

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

 

Thu Oct 05 2023 18:02:27 EDT from IGnatius T Foobar Subject: Re: New Setup Issues by a Newbie

There's not enough information to troubleshoot. At the very least you should show us your DNS configuration, identify the domain you're trying to use, show that the MX and RDNS records are correct; and show the configuration settings of your Citadel installation.

It'
s also possible that both gmail and yahoo simply reject mail originating from residential address blocks such as the one you are using on Charter Cable.
If that is the case, and you are serious about hosting a "real" Internet server from your home, you might consider a service such as https://www.aceinnovative.com/internet-access/static-ip-vpn/ to place your server on a "real" hosting network with static IP and no port restrictions. (This is not sponsored -- I and other Citadel operators are very happy customers.)

It is residential but it  is business class internet. I  had  static IP but  got of rid of it but will get it back tomorrow. Its a a real  server 88threads, etc. I'm not trying to host a public email server. I really just need it to  receive  emails  from yahoo, google etc. I don't need to  send  them. 

Again, the email server thing is new to me. I have citadel on a box on  my  server  behind a reverse  proxy. My domain  name I want to use  for  this is companalyticscloud.net. Can you look at the DNS information from it? I can open and close ports as needed.

 

 

Thanks for any help getting  me  started  on  this.



[#] Fri Oct 06 2023 13:56:19 EDT from s3cr3to to jhwatts <jhwatts@uncensored.citadel.org>, Citadel_Support <room_Citadel_Support@uncensored.citadel.org>

Subject: Re: New Setup Issues by a Newbie

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

Try this tool and test the suggestions of IG (For now, only you know the real information about your system).

https://mxtoolbox.com/SuperTool.aspx?action=mx%3acompanalyticscloud.net&run=toolpage
https://mxtoolbox.com/

Good luck!


On 10/5/23 17:36, jhwatts wrote:

 

Thu Oct 05 2023 18:02:27 EDT from IGnatius T Foobar Subject: Re: New Setup Issues by a Newbie

There's not enough information to troubleshoot. At the very least you should show us your DNS configuration, identify the domain you're trying to use, show that the MX and RDNS records are correct; and show the configuration settings of your Citadel installation.

It'
s also possible that both gmail and yahoo simply reject mail originating from residential address blocks such as the one you are using on Charter Cable.
If that is the case, and you are serious about hosting a "real" Internet server from your home, you might consider a service such as https://www.aceinnovative.com/internet-access/static-ip-vpn/ to place your server on a "real" hosting network with static IP and no port restrictions. (This is not sponsored -- I and other Citadel operators are very happy customers.)

It is residential but it  is business class internet. I  had  static IP but  got of rid of it but will get it back tomorrow. Its a a real  server 88threads, etc. I'm not trying to host a public email server. I really just need it to  receive  emails  from yahoo, google etc. I don't need to  send  them. 

Again, the email server thing is new to me. I have citadel on a box on  my  server  behind a reverse  proxy. My domain  name I want to use  for  this is companalyticscloud.net. Can you look at the DNS information from it? I can open and close ports as needed.

 

 

Thanks for any help getting  me  started  on  this.




[#] Sun Oct 08 2023 23:50:30 EDT from LadySerenaKitty

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

Just updated my Citadel to 996 and ....

citserver 38182 - - msgbase: message #8836 was not found
citserver 38182 - - msgbase: message #8837 was not found
citserver 38182 - - msgbase: message #8838 was not found
citserver 38182 - - msgbase: message #8839 was not found
citserver 38182 - - msgbase: message #8841 was not found
citserver 38182 - - msgbase: message #8842 was not found
citserver 38182 - - msgbase: message #8844 was not found
citserver 38182 - - msgbase: message #8845 was not found
citserver 38182 - - msgbase: message #8847 was not found
citserver 38182 - - msgbase: message #8848 was not found

Plus loads moar.  I tried using the database_cleanup.sh and I still get this issue.



[#] Mon Oct 09 2023 13:52:33 EDT from IGnatius T Foobar

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

It's possible that during some previous event those messages were deleted but one or more rooms still has pointers to them. In the new database code this should theoretically never happen, but if you still have those pointers to messages that don't exist, no amount of database cleanup will make the warnings go away.

If you can figure out what room they are in, you can safely delete them.

To be clear: anyone who is running Citadel 993 or later should almost never have any need to run the database_cleanup script. I spent my whole summer making the database_bdb module bullet proof, and would be quite surprised if anyone ever had that kind of corruption again.

Now if you're *really* picky and have a lot of time to kill, you could run `ctdldump` and edit the dump by hand, and then `ctdlload` it back into a fresh database. But you've probably got better ways to spend your time.

[#] Tue Oct 10 2023 01:48:10 EDT from LadySerenaKitty

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

The broken messages aren't in a room.  They're in the Outbound SMTP Queue.

Mon Oct 09 2023 13:52:33 EDT from IGnatius T Foobar
It's possible that during some previous event those messages were deleted but one or more rooms still has pointers to them. In the new database code this should theoretically never happen, but if you still have those pointers to messages that don't exist, no amount of database cleanup will make the warnings go away.

If you can figure out what room they are in, you can safely delete them.

To be clear: anyone who is running Citadel 993 or later should almost never have any need to run the database_cleanup script. I spent my whole summer making the database_bdb module bullet proof, and would be quite surprised if anyone ever had that kind of corruption again.

Now if you're *really* picky and have a lot of time to kill, you could run `ctdldump` and edit the dump by hand, and then `ctdlload` it back into a fresh database. But you've probably got better ways to spend your time.

 



[#] Tue Oct 10 2023 07:05:44 EDT from velocite

Subject: easyinstall upgrade from 958 to 996 hanging

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

I'm attempting to upgrade our Citadel instance from version 958 to 996, using easyinstall (it was originally built using easyinstall).

The server is a 6-core, 12 thread I5-10400 with 64GB of RAM and NVMe disk, running Ubuntu 22.04.3 LTS 6.2.0-34-generic kernel.

The database size is 5.5GB, but has never had any issues. The server logs look clean; starting with 'citserver -x9' doesn't show any obvious problems.

But the update attempt always gets stuck (until I kill it after an hour) at:

Restarting Citadel server to apply changes

[************************************************************************....]

using 100% of one CPU core, but not generating disk I/O. So it's obviously getting stuck near the end of citadel/utils/setup.c

 

An strace on the setup process shows continual attempts of:

read(-1, 0x7ffcca70371f, 1)             = -1 EBADF (Bad file descriptor)

(the read address changes from run to run)

Is this a repeated socket read attempt?

 

To proceed I have to kill the setup process and restore from backup.

 

Suggestions for how to diagnose further will be gratefully received...

 


Go to page: First ... 5 6 7 8 [9] 10 11 12 13 ... Last