Language:
switch to room list switch to menu My folders
Go to page: First ... 29 30 31 32 [33] 34
[#] Sun Sep 19 2021 15:45:53 EDT from s3cr3to

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

Test Sept-19B from Firefox; the previous test from SMTP does not appear yet.

The message shows as "Error"


ERROR: �n�� �E�

Wed Dec 31 1969 07:00:00 PM EST from <>
 

 



[#] Sun Sep 19 2021 15:49:19 EDT from s3cr3to

Subject: (Ignore please)

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

How strange, the message was originally sent from "Development" and appeared here in "Support" and no subject.
(Ignore please)

 

Sun Sep 19 2021 03:45:53 PM EDT from s3cr3to

Test Sept-19B from Firefox; the previous test from SMTP does not appear yet.

The message shows as "Error"


ERROR: �n�� �E�

Wed Dec 31 1969 07:00:00 PM EST from <>
 

 



 



[#] Sun Sep 19 2021 17:09:37 EDT from JanDenOuden

Subject: Citadel contineously crashing and restarting

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

Hi,

I have been using Citadel in a private situation for more than 10 years, without problems.

But the NAS (LG) I was running it on needed replacement.

So now I have a new OpenMediaVault NAS, which is running without problems.

After I installed Citadel as a normal application, alongside OpenMediaVault (same as I did on my old NAS), things in OpenMediaVault broke seriously. I had to re-install it completely.

Then I learned I could run Citadel through docker/portainer in OpenMediaVault. That installation was a breeze, and didn't affect OpenMediaVault.

I copied mails from old NAS to new OMV Nas with a simple tool imapcopy. Was a bit problematic, some mails failed. But it succeeded seemingly well.

Since then, I have been using it for a couply of weeks. I noticed some problems. Connection seemed problematic, difficult to receive new mails. Retreiving mails from folders other than Inbox was problematic as well.

After investigating, I found out that the Citadel server and container is continuously crashing, and automatically restarting. This explains the problems described.

This happend on version 931.

I created a new container, which has version 938. After initial install, this container is stable, no crashes/restarts.

After I copy the data from first container (931) to the new container, the new container shows the same problems as the first. This happens when I copy all data, or only cdb.08 datafile.

Log file:

2021-09-19T21:00:26.960210325Z ctdlvisor: Welcome to the Citadel System running in a container.,
2021-09-19T21:00:26.960330444Z ctdlvisor: command line arguments: /usr/local/bin/ctdlvisor ,
2021-09-19T21:00:26.968395558Z ctdlvisor: /citadel-data/data is writable,
2021-09-19T21:00:26.960339997Z ctdlvisor: /citadel-data is writable,
2021-09-19T21:00:26.968477417Z ctdlvisor: /citadel-data/files is writable,
2021-09-19T21:00:26.968483671Z ctdlvisor: /citadel-data/keys is writable,
2021-09-19T21:00:26.968631336Z ctdlvisor: citserver running on pid=9,
2021-09-19T21:00:26.968640286Z ctdlvisor: executing citserver,
2021-09-19T21:00:26.968645473Z ctdlvisor: webcit (HTTP) running on pid=10,
2021-09-19T21:00:26.968650047Z ctdlvisor: webcit (HTTPS) running on pid=11,
2021-09-19T21:00:26.968654534Z ctdlvisor: executing webcit (https),
2021-09-19T21:00:26.968658960Z ctdlvisor: executing webcit (http),
2021-09-19T21:00:36.682189203Z ctdlvisor: pid=9 exited, status=26880, exitcode=105,
2021-09-19T21:00:41.696606302Z ctdlvisor: webcit (HTTPS) running on pid=11,
2021-09-19T21:00:36.682271066Z ctdlvisor: citserver exited intentionally - ending container session,
2021-09-19T21:00:37.682593778Z ctdlvisor: pid=10 exited, status=15, exitcode=0,
2021-09-19T21:00:38.682742827Z ctdlvisor: pid=11 exited, status=15, exitcode=0,
2021-09-19T21:00:40.683049304Z ctdlvisor: exit code 105,
2021-09-19T21:00:39.682808558Z ctdlvisor: pid=-1 exited, status=15, exitcode=0,
2021-09-19T21:00:41.693614399Z ctdlvisor: Welcome to the Citadel System running in a container.

There seems to be nothing I can do to futher investigate, due to the contineous and frequent crashes/restarts

I was thinking to copy mails from the first container to a new stable container, but that won't work either due to the crashes.

Only solution I can think of now is copy mails from old NAS to new container again. And then accepting I loose the new mails from the couple of weeks I have been using Citadel on the new NAS. Or try to copy these mails one by one through a mail client like Thunderbird.

Do you have any other suggestions?

Best regards,

Jan den Ouden

 

 



[#] Mon Sep 20 2021 00:35:16 EDT from ParanoidDelusions

Subject: Re: Citadel contineously crashing and restarting

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

I was having VERY similar issues, continuously - and interestingly - I discovered that I was getting multiple PIDs for both the HTTP and HTTPS instances of Citadel. Citadel was crashing and restarting constantly, flooding my logs with error messages. 

Finally I went after it very hard - and unfortunately as usually happens - this was months ago and I don't remember exactly what the fix was. I think I documented most of what I was doing either here on Uncensored or on my own Citadel - but I didn't do it in this room for sure - because I've gotten some heat for blogging my personal troubleshooting randomly in this room. It creates a mess of the threaded view. 

It may not be related - it may just be a similar symptom. I'll see if I can find the messages. 


Sun Sep 19 2021 17:09:37 EDT from JanDenOuden Subject: Citadel contineously crashing and restarting

Hi,

I have been using Citadel in a private situation for more than 10 years, without problems.

But the NAS (LG) I was running it on needed replacement.

So now I have a new OpenMediaVault NAS, which is running without problems.

After I installed Citadel as a normal application, alongside OpenMediaVault (same as I did on my old NAS), things in OpenMediaVault broke seriously. I had to re-install it completely.

Then I learned I could run Citadel through docker/portainer in OpenMediaVault. That installation was a breeze, and didn't affect OpenMediaVault.

I copied mails from old NAS to new OMV Nas with a simple tool imapcopy. Was a bit problematic, some mails failed. But it succeeded seemingly well.

Since then, I have been using it for a couply of weeks. I noticed some problems. Connection seemed problematic, difficult to receive new mails. Retreiving mails from folders other than Inbox was problematic as well.

After investigating, I found out that the Citadel server and container is continuously crashing, and automatically restarting. This explains the problems described.

This happend on version 931.

I created a new container, which has version 938. After initial install, this container is stable, no crashes/restarts.

After I copy the data from first container (931) to the new container, the new container shows the same problems as the first. This happens when I copy all data, or only cdb.08 datafile.

Log file:

2021-09-19T21:00:26.960210325Z ctdlvisor: Welcome to the Citadel System running in a container.,
2021-09-19T21:00:26.960330444Z ctdlvisor: command line arguments: /usr/local/bin/ctdlvisor ,
2021-09-19T21:00:26.968395558Z ctdlvisor: /citadel-data/data is writable,
2021-09-19T21:00:26.960339997Z ctdlvisor: /citadel-data is writable,
2021-09-19T21:00:26.968477417Z ctdlvisor: /citadel-data/files is writable,
2021-09-19T21:00:26.968483671Z ctdlvisor: /citadel-data/keys is writable,
2021-09-19T21:00:26.968631336Z ctdlvisor: citserver running on pid=9,
2021-09-19T21:00:26.968640286Z ctdlvisor: executing citserver,
2021-09-19T21:00:26.968645473Z ctdlvisor: webcit (HTTP) running on pid=10,
2021-09-19T21:00:26.968650047Z ctdlvisor: webcit (HTTPS) running on pid=11,
2021-09-19T21:00:26.968654534Z ctdlvisor: executing webcit (https),
2021-09-19T21:00:26.968658960Z ctdlvisor: executing webcit (http),
2021-09-19T21:00:36.682189203Z ctdlvisor: pid=9 exited, status=26880, exitcode=105,
2021-09-19T21:00:41.696606302Z ctdlvisor: webcit (HTTPS) running on pid=11,
2021-09-19T21:00:36.682271066Z ctdlvisor: citserver exited intentionally - ending container session,
2021-09-19T21:00:37.682593778Z ctdlvisor: pid=10 exited, status=15, exitcode=0,
2021-09-19T21:00:38.682742827Z ctdlvisor: pid=11 exited, status=15, exitcode=0,
2021-09-19T21:00:40.683049304Z ctdlvisor: exit code 105,
2021-09-19T21:00:39.682808558Z ctdlvisor: pid=-1 exited, status=15, exitcode=0,
2021-09-19T21:00:41.693614399Z ctdlvisor: Welcome to the Citadel System running in a container.

There seems to be nothing I can do to futher investigate, due to the contineous and frequent crashes/restarts

I was thinking to copy mails from the first container to a new stable container, but that won't work either due to the crashes.

Only solution I can think of now is copy mails from old NAS to new container again. And then accepting I loose the new mails from the couple of weeks I have been using Citadel on the new NAS. Or try to copy these mails one by one through a mail client like Thunderbird.

Do you have any other suggestions?

Best regards,

Jan den Ouden

 

 



 



[#] Mon Sep 20 2021 00:48:44 EDT from ParanoidDelusions

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

http://uncensored.citadel.org/readfwd?go=Techie%20Talk?start_reading_at=2099263559#2099263559


Is where I am talking about this issue. It'll give you a date - and it was related to redirects to blog rooms in my case - I also see this happening on Smashbot's Citadel. 

in Aide: you should have an error message, fairly frequently, something like: 

Citadel had trouble on starting up. We couldn't bind all ports you configured to be provided by Citadel Server.
This means, Citadel won't be the service provider for a specific service you configured it to.

If you don't want Citadel to provide these services, turn them off in WebCit via: "Admin->System Preferences->Network".

The failed ports and sockets are: extensions: TCP port *:504: (citadel-TCP) ;extensions: TCP port *:143: (IMAP) ;extensions: TCP port *:993: (IMAPS) ;extensions: TCP port *:119: (NNTP) ;extensions: TCP port *:563: (NNTPS) ;extensions: TCP port *:110:
(POP3) ;extensions: TCP port *:995: (POP3S) ;extensions: TCP port *:25: (SMTP-MTA) ;extensions: TCP port *:465: (SMTPs-MTA) ;extensions: TCP port *:587: (SMTP-MSA)

If you want Citadel to provide you with that functionality, check the output of "netstat -lnp" on Linux, or "netstat -na" on BSD and disable the program that binds these ports.


To make both ways actualy take place restart the citserver with "sendcommand down"

The errors returned by the system were:
failed; failed; failed; failed; failed; failed; failed; failed; failed; failed

You can recheck the above if you follow this faq item:


------------------

A PS -A may be insightful in showing that Citadel thinks it isn't running, is trying to launch a new instance, and can't bind the new instance because Citadel is already running and has those ports bound. 

And I think it is related to how Citadel launches. Are you running Debian or a Debian variant? 

 



[#] Mon Sep 20 2021 15:49:15 EDT from IGnatius T Foobar

Subject: Re: Citadel contineously crashing and restarting

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

After investigating, I found out that the Citadel server and
container is continuously crashing, and automatically restarting.
This explains the problems described.

Exit code 105 is a database error.

Have you tried running in database cleanup mode (after taking a backup, of course)

[#] Mon Sep 20 2021 16:59:48 EDT from JanDenOuden

Subject: Re: Citadel contineously crashing and restarting

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

Thanks for your quick response.

I would want to try a database cleanup, but as you can see from the logs, citadel and the whole container crashes/restarts in about 10 seconds. I don't get a chance to start a database cleanup.

 

 



[#] Tue Sep 21 2021 09:27:46 EDT from IGnatius T Foobar

Subject: Re: Citadel contineously crashing and restarting

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

I would want to try a database cleanup, but as you can see from the
logs, citadel and the whole container crashes/restarts in about 10
seconds. I don't get a chance to start a database cleanup.

The server doesn't run when you do a database cleanup.

If you are using the container version, stop the container, and then run it from the command line using the following command:

docker run -it --volume=/usr/local/citadel:/citadel-data citadeldotorg/citadel -d

That last "-d" will make the container run database_cleanup.sh instead of the Citadel Server. After it finishes dumping and loading, you can restart the server the normal way.

If you're not running in a container, just stop the server and run database_cleanup.sh

[#] Tue Sep 21 2021 14:38:27 EDT from michael

Subject: SMTP authentication fails, POP3 ok...

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

Hi,

i installed Citadel via easy-install. Everything works fine, i can receive e-mails via pop3 port 110. But when i try to send e-mails via smpt port 25 or in my case port 26 (changed the port via webcit) i get an authentication failure:

Sep 21 20:29:17 db0alg citserver[8069]: citserver[8069]: context: session (SMTP-MTA) started from 192.168.2.128 (192.168.2.128) uid=-1

Sep 21 20:29:17 db0alg citserver[8069]: context: session (SMTP-MTA) started from 192.168.2.128 (192.168.2.128) uid=-1

Sep 21 20:29:17 db0alg citserver[8069]: citserver[8069]: user_ops: bad password specified for <> Service <SMTP-MTA> Port <26> Remote <192.168.2.128 / 192.168.2.128>

Sep 21 20:29:17 db0alg citserver[8069]: user_ops: bad password specified for <> Service <SMTP-MTA> Port <26> Remote <192.168.2.128 / 192.168.2.128>

Sep 21 20:29:17 db0alg citserver[8069]: citserver[8069]: SMTP: client disconnected: ending session.

Sep 21 20:29:17 db0alg citserver[8069]: citserver[8069]: context: [231]SRV[SMTP-MTA] Session ended.

Sep 21 20:29:17 db0alg citserver[8069]: SMTP: client disconnected: ending session.

Sep 21 20:29:17 db0alg citserver[8069]: context: [231]SRV[SMTP-MTA] Session ended.

 

Any idea? And yes, username and password are correct, i can login with theese credentials via webcit with no problem. I can also send e-mails via webcit, but have no luck with external clients. Another old installation of Citadel works with no problems, using same client.

System is a RaspberryPI 4 and Debian Buster.

 

 


[#] Tue Sep 21 2021 17:41:42 EDT from michael

Subject: SMTP authentication fails, POP3 ok...

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

Hi,

i installed Citadel via easy-install. Everything works fine, i can receive e-mails via pop3 port 110. But when i try to send e-mails via smpt port 25 or in my case port 26 (changed the port via webcit) i get an authentication failure:

Sep 21 20:29:17 db0alg citserver[8069]: citserver[8069]: context: session (SMTP-MTA) started from 192.168.2.128 (192.168.2.128) uid=-1

Sep 21 20:29:17 db0alg citserver[8069]: context: session (SMTP-MTA) started from 192.168.2.128 (192.168.2.128) uid=-1

Sep 21 20:29:17 db0alg citserver[8069]: citserver[8069]: user_ops: bad password specified for <> Service <SMTP-MTA> Port <26> Remote <192.168.2.128 / 192.168.2.128>

Sep 21 20:29:17 db0alg citserver[8069]: user_ops: bad password specified for <> Service <SMTP-MTA> Port <26> Remote <192.168.2.128 / 192.168.2.128>

Sep 21 20:29:17 db0alg citserver[8069]: citserver[8069]: SMTP: client disconnected: ending session.

Sep 21 20:29:17 db0alg citserver[8069]: citserver[8069]: context: [231]SRV[SMTP-MTA] Session ended.

Sep 21 20:29:17 db0alg citserver[8069]: SMTP: client disconnected: ending session.

Sep 21 20:29:17 db0alg citserver[8069]: context: [231]SRV[SMTP-MTA] Session ended.

 

Any idea? And yes, username and password are correct, i can login with theese credentials via webcit with no problem. I can also send e-mails via webcit, but have no luck with external clients. Another old installation of Citadel works with no problems, using same client.

System is a RaspberryPI 4 and Debian Buster.

 

 


[#] Tue Sep 21 2021 19:08:17 EDT from michael

Subject: SMTP authentication fails, POP3 ok...

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

Hi,

i installed Citadel via easy-install. Everything works fine, i can receive e-mails via pop3 port 110. But when i try to send e-mails via smpt port 25 or in my case port 26 (changed the port via webcit) i get an authentication failure:

Sep 21 20:29:17 db0alg citserver[8069]: citserver[8069]: context: session (SMTP-MTA) started from 192.168.2.128 (192.168.2.128) uid=-1

Sep 21 20:29:17 db0alg citserver[8069]: context: session (SMTP-MTA) started from 192.168.2.128 (192.168.2.128) uid=-1

Sep 21 20:29:17 db0alg citserver[8069]: citserver[8069]: user_ops: bad password specified for <> Service <SMTP-MTA> Port <26> Remote <192.168.2.128 / 192.168.2.128>

Sep 21 20:29:17 db0alg citserver[8069]: user_ops: bad password specified for <> Service <SMTP-MTA> Port <26> Remote <192.168.2.128 / 192.168.2.128>

Sep 21 20:29:17 db0alg citserver[8069]: citserver[8069]: SMTP: client disconnected: ending session.

Sep 21 20:29:17 db0alg citserver[8069]: citserver[8069]: context: [231]SRV[SMTP-MTA] Session ended.

Sep 21 20:29:17 db0alg citserver[8069]: SMTP: client disconnected: ending session.

Sep 21 20:29:17 db0alg citserver[8069]: context: [231]SRV[SMTP-MTA] Session ended.

 

Any idea? And yes, username and password are correct, i can login with theese credentials via webcit with no problem. I can also send e-mails via webcit, but have no luck with external clients. Another old installation of Citadel works with no problems, using same client.

System is a RaspberryPI 4 and Debian Buster.

 

 


[#] Wed Sep 22 2021 13:54:47 EDT from IGnatius T Foobar

Subject: Re: SMTP authentication fails, POP3 ok...

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

Maybe if you post it a fourth time someone will answer?

Please advise what SMTP client software you are using, and what SASL method it is using (LOGIN, PLAIN, etc).

Also try port 587 instead of port 25.

[#] Wed Sep 22 2021 15:05:42 EDT from michael

Subject: Re: SMTP authentication fails, POP3 ok...

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

I am using Microsoft Outlook as a client, also tryed other ones but no luck.

Auth is plain, no spa/ssl/tls. I also tested with port 587, same problem....i have no idea anymore.

 



[#] Wed Sep 22 2021 18:24:47 EDT from Silverfoxe

Subject: email

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

I just performed an easyinstall  on a virgin pi 3 with debian buster.

Am having issues with email contact settings and noticed display_reg?suppress_email=1 with no email information if I change email=0 looks like the information is available but isn't; anybody else have this issue?

I can locally email between primary accounts but not aliases.

this situation has happened with the current software on various pi operating systems including ubuntu server and manjaro, is anybody else having issues?

btw - working with my isp to resolved port 25 issues that appear to be connected to the router.

I've used citadel in the past without fail so I would like to get back to the application.

any help would be appreciated!

 



[#] Fri Sep 24 2021 17:58:05 EDT from JanDenOuden

Subject: Re: Citadel contineously crashing and restarting

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

I did the database cleanup job. I expected a lengthy job, but it finished in only 2 seconds or so (database more than 2 GB).

For 1 or 2 minutes it looked OK. But then I got the crashes/restarts again, same error code 105.

Meanwhile, I have created a new citadel docker container, and did a new copy from my old NAS. Now with another tool, imapsync. This has been running now for 2 days, and looks good.

Thanks for you assistance in this. Using Citadel just for free as a private user, I appreciate the prompt help.

 

 



[#] Wed Sep 29 2021 07:09:22 EDT from xx1182

Subject: Easy Install witouth Systemd

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

Hi, i've tried the EasyInstall method, and it says:

systemd was not found

cause even tho it is Debian my init system is not Systemd.

 

So according to the wiki, and the installer i'm supposed to go to /usr/local/citadel/setup, but it doesn't work, since setup tries to connect to a server.



[#] Wed Sep 29 2021 08:50:17 EDT from xx1182

Subject: Re: Easy Install witouth Systemd

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

Well, i managed to just run "citserver" and then setup, i suppose that's the only binary that is needed to run, but how do i change the default ports?



[#] Wed Sep 29 2021 09:15:54 EDT from IGnatius T Foobar

Subject: Re: Easy Install witouth Systemd

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

You are correct about the Easy Install system requiring systemd to automatically start Citadel, and you are also correct about just running the citserver binary using whatever local method you're using.

To change the default ports, log in to any client. You can use the console mode client (citadel) if you want to. But you probably want the web client (WebCit), which is another server binary found in /usr/local/webcit/webcit.

[#] Wed Sep 29 2021 09:26:42 EDT from xx1182

Subject: Re: Easy Install witouth Systemd

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

Very, VERY VERY NICE. It's all integrated, i've actually found the ports way back, but i tought, they were referring to the "webcit client" ports, and i didn't know it would actually change ports.

 

VERY VERY NICE. Regards.



[#] Wed Sep 29 2021 13:49:12 EDT from leemon

Subject: managesieve port

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

Hi,

it seems managesieve port is not saved in [Administration -> Edit site-wide configuration -> SMTP], it's always "0", at least in the latest docker container.

 



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