Language:
switch to room list switch to menu My folders
Go to page: First ... 30 31 32 33 [34] 35
[#] Tue Nov 21 2017 03:02:33 EST from techacq1Aa @ Uncensored

Subject: Re: "Outbound Queue" invisible bounce sender to flood the database

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

 

Mon Nov 20 2017 09:24:16 EST from IGnatius T Foobar @ Uncensored Subject: Re: "Outbound Queue" invisible bounce sender to flood the database
Thanks for the very well written report. Would you be able to tell us how often the retry happened, and what the bounceback looked like? I'd like to ascertain whether the receiving server generated a 5XX error that should have told Citadel to give up, or a 4XX error that would have told Citadel to keep trying.

Older versions of Citadel Server would retry after 15 minutes, doubling the retry time after each attempt. Versions published starting this year (2017) simply retry every 30 minutes for the first four hours, and then every four hours for the next five days. But if it gets a 5XX undeliverable error from the receiving server, it's supposed to stop immediately.

I remember fondly the old double-time delay,
but this tempo was an unwavering  ~60 seconds.

 

In the users inbox, the reply has a sender (Citadel)

and a subject:

Subject: Delivery Status Notification (Failure)

A message you sent could not be delivered to some or all of its recipients
due to prolonged unavailability of its destination(s).
Giving up on the following addresses:

clarisse@abandoned.domain.com: 421 (Domain service not available, closing transmission channel)

 

She always cc: herself to ensure she gets a copy,

  and perhaps this was the crux of the issue - a cc: that trips the system into retrying the target when it sends the failure message, perhaps ?

just a thought

 

And to answer freakdog's suggestion: (thanks)

I never touched the autodelete logs - but checked again anyway to make sure that it is still set to delete and it is indeed set to delete.

 

I was first alarmed that it might be a hack,
but my email counter showed nothing going out

I have a script reporting the number of mails sent logged every few minutes on an admin webpage,
maybe I will add a  df  function to that log so I won't wake up to this again.
Mondays are bad enough without that kind of a hangover

My other concern was how I had set up the kvm with a detachable partition for /usr/local/citadel/data/
 but that was not a problem - it worked even after it hit the limits.

Now to automate the backup of this particular partition.....



[#] Tue Nov 21 2017 14:24:26 EST from kinetix @ Uncensored

Subject: Re: "Outbound Queue" invisible bounce sender to flood the database

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

Thanks for pointing that out!  I read the man page around it and thought I'd see what I got.  Unfortunately, the tool doesn't like something about the db itself:

root@home:/storage/citadel/data# db_hotbackup -v -d . -h . -b ../testbackup/        
db_hotbackup: BDB5032 hot backup started at Tue Nov 21 11:20:16 2017
db_hotbackup: BDB5129 Cannot copy data from a PRIVATE environment
db_hotbackup: BDB5043 HOT BACKUP FAILED!

I'm pretty confused by this, but know nothing about how 'environments' are set up in Berk DB.  I see references to it in citadel's database.c, but other than that, I'm at a loss as to what makes it not work here.

 

Mon Nov 20 2017 05:24:29 PM EST from IGnatius T Foobar @ Uncensored Subject: Re: "Outbound Queue" invisible bounce sender to flood the database
I see that Berkeley DB now has a "db_hotbackup" utility, which looks promising.
I haven't tried it.

 



[#] Thu Nov 23 2017 03:41:48 EST from marisag @ Uncensored

Subject: Directory rooms?

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

How do I set up file directory rooms? I enabled it in the room config but do=
n't see any upload/download buttons...

Marisa



[#] Thu Nov 23 2017 06:55:29 EST from techacq1Aa @ Uncensored

Subject: Re: Directory rooms?

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

clicking on the  word "files" in the upper header may send you to an upload/directory list,

as visible above just under where it says "Citadel Support"

if you gave the file directory a name, hopefully



[#] Thu Nov 23 2017 08:49:19 EST from marisag @ Uncensored

Subject: Re: Directory rooms?

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

Great, that took care of it. Thanks!



[#] Thu Nov 23 2017 08:50:36 EST from marisag @ Uncensored

Subject: Setting up citadel to answer for regular telnet connections?

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

It says to look in the install.txt file for instructions on doing this, but I installed via the easy install and don't have that file. Any pointers?



[#] Thu Nov 23 2017 10:57:39 EST from kinetix @ Uncensored

Subject: Re: Setting up citadel to answer for regular telnet connections?

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

You bet!

http://citadel.org/doku.php/documentation:system_administration_manual?s[]=telnet#bypassingtheloginprompt

 

Thu Nov 23 2017 08:50:36 AM EST from marisag @ Uncensored Subject: Setting up citadel to answer for regular telnet connections?

It says to look in the install.txt file for instructions on doing this, but I installed via the easy install and don't have that file. Any pointers?



 



[#] Thu Nov 23 2017 22:30:09 EST from techacq1Aa @ Uncensored

Subject: Re: "Outbound Queue" invisible bounce sender to flood the database

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

Again,
this time I was a bit better prepared.

Two entries in the outbound,

one original email to be resent
+ one error message about 421 failure (still to be sent !)

 

Both entries are utterly invisible in

..../dotskip?room=__CitadelSMTPspoolout__&view=11

and only visible in

..../dotskip?room=__CitadelSMTPspoolout__&view=1

not yet sure what that implies.

 

The message about ERROR 421 Domain service not available
compelled me to check again the email destination (using dig)
and I see no issues there, MX address seems okay, etc.

 

Ultimately there remain two things for me to solve:

1.
Have I have misconfigured some kind of disjoint
between citadel and the DNS server such that Citadel calls up
and the DNS simply fails to respond, tricking citadel into calling the destination unavailable ?

I will reserve some spare time to try to replicate this failure and examine it using an test email
 and not wait for another bounce event.

 

2.
I should rewire this 421 failure so that the system stops resending itself failed deliveries,
a to-do list thingy - time to read more on SENDCOMMAND.

 

The answer is out there and I will keep looking.

 

Tue Nov 21 2017 03:02:33 EST from techacq1Aa @ Uncensored Subject: Re: "Outbound Queue" invisible bounce sender to flood the database

 

In the users inbox, the reply has a sender (Citadel)

and a subject:

Subject: Delivery Status Notification (Failure)

A message you sent could not be delivered to some or all of its recipients
due to prolonged unavailability of its destination(s).
Giving up on the following addresses:

clarisse@abandoned.domain.com: 421 (Domain service not available, closing transmission channel)

 

She always cc: herself to ensure she gets a copy,

  and perhaps this was the crux of the issue - a cc: that trips the system into retrying the target when it sends the failure message, perhaps ?

just a thought

 

And to answer freakdog's suggestion: (thanks)

I never touched the autodelete logs - but checked again anyway to make sure that it is still set to delete and it is indeed set to delete.

 



[#] Fri Nov 24 2017 13:38:18 EST from richardb49 @ Uncensored

Subject: Installation woes

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

The server I had been running Citadel died two days ago. I put together another computer, installed Debian 9 and from root did the traditional apt-get install citadel-suite setting the IP address to my server's IP, set the admin user name and password.  The one thing I did not do was first create a separate user for Citadel.

Brought up Webcit, entered the user name and password I put in for the admin, got a "Please wait" and several beeps from the speaker. Nothing else. Went to restart the computer, browsed to Webcit, tried to log in and get a wrong password. I have purged and reinstalled, I have wiped the hard drive and started over several times over the last two days. Sometimes it says the citadel server is not running and I manually restart it. All to no avail. I love the program, I just am at my wits end on what should have been a simple install.

Checked the system log and it has:

[ 3710.658289] citserver[1758]: segfault at 0 ip b6ffb5a6 sp b41f4e94 error 4 in libc-2.24.so[b6ebd000+1b1000]
[ 3711.174977] citserver[1778]: segfault at 0 ip b6ffb5a6 sp bfd096f4 error 4 in libc-2.24.so[b6ebd000+1b1000]
[ 3711.633529] citserver[1781]: segfault at 0 ip b6ffb5a6 sp bfd096f4 error 4 in libc-2.24.so[b6ebd000+1b1000]
[ 3789.535293] TCP: request_sock_TCP: Possible SYN flooding on port 25. Sending cookies.  Check SNMP counters.
[ 4315.358799] citserver[1787]: segfault at 0 ip b6ffb5a6 sp b42fd044 error 4 in libc-2.24.so[b6ebd000+1b1000]
[ 4319.219975] citserver[1819]: segfault at 0 ip b6ffb5a6 sp b41fc044 error 4 in libc-2.24.so[b6ebd000+1b1000]
[ 4321.931053] citserver[1823]: segfault at 0 ip b6ffb5a6 sp b42fd044 error 4 in libc-2.24.so[b6ebd000+1b1000]
[ 5073.461855] TCP: request_sock_TCP: Possible SYN flooding on port 25. Sending cookies.  Check SNMP counters.

Any help would be appreciated.



[#] Fri Nov 24 2017 16:08:46 EST from techacq1Aa @ Uncensored

Subject: Re: Installation woes

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

Hi Richard,

Me too - Debian 9 has issues, the packaged debs are hopeless.

If you use the easy-install everything may fall more or less into place.

Just be sure you do install all the prerequisites. I know, I have been slogging into Debian 9 also.

Right now I am degraded to a SolydX 8 (=debian8) due to the problems getting past the post on Debian 9.1 and its SolydX derivative.

Citadel does install a lot easier in Ubuntu, (I am very unhappy with Ubuntu, but easy install on Xubuntu seems to work properly.)

Fri Nov 24 2017 13:38:18 EST from richardb49 @ Uncensored Subject: Installation woes

The server I had been running Citadel died two days ago. I put together another computer, installed Debian 9 and from root did the traditional apt-get install citadel-suite setting the IP address to my server's IP, set the admin user name and password.  The one thing I did not do was first create a separate user for Citadel.

Brought up Webcit, entered the user name and password I put in for the admin, got a "Please wait" and several beeps from the speaker. Nothing else. Went to restart the computer, browsed to Webcit, tried to log in and get a wrong password. I have purged and reinstalled, I have wiped the hard drive and started over several times over the last two days. Sometimes it says the citadel server is not running and I manually restart it. All to no avail. I love the program, I just am at my wits end on what should have been a simple install.

Checked the system log and it has:

[ 3710.658289] citserver[1758]: segfault at 0 ip b6ffb5a6 sp b41f4e94 error 4 in libc-2.24.so[b6ebd000+1b1000]
[ 3711.174977] citserver[1778]: segfault at 0 ip b6ffb5a6 sp bfd096f4 error 4 in libc-2.24.so[b6ebd000+1b1000]
[ 3711.633529] citserver[1781]: segfault at 0 ip b6ffb5a6 sp bfd096f4 error 4 in libc-2.24.so[b6ebd000+1b1000]
[ 3789.535293] TCP: request_sock_TCP: Possible SYN flooding on port 25. Sending cookies.  Check SNMP counters.
[ 4315.358799] citserver[1787]: segfault at 0 ip b6ffb5a6 sp b42fd044 error 4 in libc-2.24.so[b6ebd000+1b1000]
[ 4319.219975] citserver[1819]: segfault at 0 ip b6ffb5a6 sp b41fc044 error 4 in libc-2.24.so[b6ebd000+1b1000]
[ 4321.931053] citserver[1823]: segfault at 0 ip b6ffb5a6 sp b42fd044 error 4 in libc-2.24.so[b6ebd000+1b1000]
[ 5073.461855] TCP: request_sock_TCP: Possible SYN flooding on port 25. Sending cookies.  Check SNMP counters.

Any help would be appreciated.



 



[#] Fri Nov 24 2017 21:05:47 EST from richardb49 @ Uncensored

Subject: Re: Installation woes

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

Thanks for the reply. I will try Debian 8.9 in the morning and post my results. I even bought a new PC in desperation this afternoon in case it was hardware related. I did not realize how many things you have to disable in an HP machine to get it to take anything but Windoze 10. Debian 9 still has issues on the new computer: hangs up, hard to set ethernet ports (no more eth0, eth1, etc.).

Once I get it up and running and all my users accounts are set up again, my next quest will be to figure if it is possible to retrieve the Citadel database on the old hard drive (I have been able to access it by connecting it to a working computer).

 



[#] Sat Nov 25 2017 13:06:48 EST from richardb49 @ Uncensored

Subject: Re: Installation woes

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

Debian 8.9 amd64 can't find citadel-suite.

sources.list contains: deb http://debian.citadel.org/debian/ jessie main

error is: http://debian.citadel.org/debian/dists/jessie/main/binary-amd64/Packages  404  Not Found

Any ideas?

Fri Nov 24 2017 21:05:47 EST from richardb49 @ Uncensored Subject: Re: Installation woes

Thanks for the reply. I will try Debian 8.9 in the morning and post my results. I even bought a new PC in desperation this afternoon in case it was hardware related. I did not realize how many things you have to disable in an HP machine to get it to take anything but Windoze 10. Debian 9 still has issues on the new computer: hangs up, hard to set ethernet ports (no more eth0, eth1, etc.).

Once I get it up and running and all my users accounts are set up again, my next quest will be to figure if it is possible to retrieve the Citadel database on the old hard drive (I have been able to access it by connecting it to a working computer).

 



 



[#] Sat Nov 25 2017 15:25:32 EST from richardb49 @ Uncensored

Subject: Re: Installation woes

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

Finally! Set up every repository I could find and got easy install to work. Everything is up and running under Debian 8.9, so my advice is to stay away from Debian 9 unless you have time to devote to getting it to run.

Now, any advice on retrieving the old database from files?



[#] Sat Nov 25 2017 23:13:16 EST from techacq1Aa @ Uncensored

Subject: Re: Installation woes

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

Good news to hear - congratulations.

Me too - I need to study how to recover an abandoned berkeley db

but my free time is exquisitely limited these days.

All  the info is probably around here somewhere,

and good first reading is in the /usr/local/ctdlsupport/docs directory.

Creating (if you can afford a machine or VM to do so) another image you can test ideas on

 goes a long ways to helping understand what you are trying to do on your workhorse.

cheers

Sat Nov 25 2017 15:25:32 EST from richardb49 @ Uncensored Subject: Re: Installation woes

Finally! Set up every repository I could find and got easy install to work. Everything is up and running under Debian 8.9, so my advice is to stay away from Debian 9 unless you have time to devote to getting it to run.

Now, any advice on retrieving the old database from files?



 



[#] Sun Nov 26 2017 17:56:28 EST from IGnatius T Foobar @ Uncensored

Subject: Re: Installation woes

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

Unfortunately, a lot was changed in Debian 9 that makes Citadel tricky to install. We're slowly working through it and will publish a new release when everything is figured out. The big problem is that we have to make it work on new Debian without breaking it on old Debian.

For now, our official advice is to stick with Debian 8 for production installations.
Also, do stick with the Easy Install method, as the .deb packages are a bit outdated at this point.

Sometime next year we would like to release a Docker container which packages the same code as Easy Install. If successful this will allow you to simply snap that container into place and point it at your database.

[#] Tue Nov 28 2017 11:30:23 EST from Marius @ Uncensored

Subject: Change locale for my own Server

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

I installed a Citadel Server with easy install and it's working fine. Now I realised, that the german language is not translated very clear and I like to change back to english.

How can this be done if I selected the german language as the "only one"?

Marius



[#] Tue Nov 28 2017 15:10:53 EST from wreighn @ Uncensored

Subject: Citserver not starting up after changing FQDN

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

I watched this youtube tutorial on setting up citadel: https://www.youtube.com/watch?v=ys2tj1OM6K0 (long video short, it comes down to setting up a static ip and installing citadel-suite with all of the defaults except the password, and afterwards setting up the fqdn and the domain).

 

Instead of raspbian, I used ubuntu server 17.10. After setting up the "Fully qualified domain name" and restarting the server I get a 503 error: "This program was unable to connect or stay connected to the Citadel server. Please report this problem to your system administrator.". I also changed the hostname of the machine to the no-ip one, but it didn't help.



[#] Tue Nov 28 2017 16:07:50 EST from bennabiy @ Uncensored

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

Ig, I wonder if there should be plastered large above this room a note about using easy install and not the debs. It would solve many problems for people.



[#] Tue Nov 28 2017 18:09:26 EST from wreighn @ Uncensored

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

It works with easy install. I wasn't aware that the deb could cause any issues. Thanks for the tip.



[#] Wed Nov 29 2017 11:29:13 EST from IGnatius T Foobar @ Uncensored

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

Ig, I wonder if there should be plastered large above this room a note about using easy install and not the debs. It would solve many problems for people.

I think I'm going to remove all information about packages from the Downloads page on our web site.  The packages are so easy to deploy but unfortunately their age and difficulty to maintain are causing more trouble than they are worth.

Easy Install is easier for us to deploy patches quickly and is always the latest available version.  As previously mentioned, after we've got 100% of a working system's state into the database, I want to make Citadel available as a Docker container.  That will provide more bang-for-the-buck because we can update it centrally and it'll work everywhere.

In the meantime ... yes, everyone should be using Easy Install, or if you're a guru, compile the sources yourself.

 



Go to page: First ... 30 31 32 33 [34] 35