Language:
switch to room list switch to menu My folders
Go to page: First ... 14 15 16 17 [18] 19 20 21 22
[#] Sat Oct 05 2019 07:13:04 EDT from btg @ Uncensored

Subject: var/run/citadel/citadel-admin.socket

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

Won't seem to install and get the error no file or directory var/run/citadel/citadel-admin.socket on Raspbian system - any suggestions?

 



[#] Mon Oct 07 2019 00:14:11 EDT from IGnatius T Foobar @ Uncensored

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

Lobby> @Server command: rwho
100
540060|(not logged in)||45.82.153.37|SMTP session|1570421294| |.-||||0


Wow

More than half a million sessions served by this running instance of citserver.

It just goes to show how exceptionally stable the server is now. This must be a disappointment for the people who used to enjoy posting "BOOM!" every time they were disconnected, some ~20 years ago when we first changed to a multithreaded server.

I almost hate to upgrade and lose the session count!

[#] Sat Oct 12 2019 11:59:49 EDT from TheOneLaw @ Uncensored

Subject: STARTTLS on SMTP port 25

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

#

You are connected to CitadelServer, running Citadel 927 with WebCit 925, server build 927

My easy install on an updated Debian 9 seems to work well with the single exception of the STARTTLS missing on port 25

root@mynew.org:~# telnet xx.xx.xxx.xxx 25
Trying xx.xx.xxx.xxx...
Connected to xx.xx.xxx.xxx.
Escape character is '^]'.
220 mynew.org ESMTP Citadel server ready.
ehlo
250-Hello  (xx.xx.xxx.xxx [xx.xx.xxx.xxx])
250-HELP
250-SIZE 10485760
250-AUTH LOGIN PLAIN
250-AUTH=LOGIN PLAIN
250 8BITMIME
quit
221 Goodbye...
Connection closed by foreign host.

Anyway,

running as root

/usr/local/citadel/citserver -x9

seemed to perform exactly what is needed (StARTTLS works properly)

which makes me wonder if

this differs somehow from running it from  the systemd ExecStart which is passed on to user "citadel'

[noting that the setup default is 'root' which I tried first

before trying a local user, both of which the system utterly ignored]

# Citadel Server unit file created by Easy Install
[Unit]
Description=Citadel Server
After=network.target
[Service]
ExecStart=/usr/local/citadel/citserver
ExecReload=/bin/kill
KillMode=process
Restart=on-failure
LimitCORE=infinity
[Install]
WantedBy=multi-user.target

so perhaps it is yet another SystemD gotcha ?

It is definitely running by system user 'citadel' in both instances:

SystemD:

citadel    683     1  0 13:42 ?        00:00:00 /usr/local/citadel/citserver

CommandLine, as ROOT,:

citadel    757   566  0 14:00 pts/0    00:00:00 /usr/local/citadel/citserver -x9

still looking for the issue,

thought this should be in a citadel.rc config file somewhere but that seems to only be for sendcommand sessions...

 

cheers

 

Thu Jun 06 2019 19:21:22 EDT from c3rebro2 @ Uncensored Subject: Issues updating from 8.24 to 925

Hello together.

Iam ran into an issue when trying to update citadel.

 

I previously installed citadel on debian 8 "jessie" with "apt-get install citadel-suite". That worked fine for several months. I now tried to get rid of the poor security report from https://www.checktls.com/TestReceiver.

Appearantly 8.24 that i installed was compiled without openssl support (at least the cli-client which is from the same source claims so). so there seems to be no way to enable the starttls capability for Port 25 smtp or at least i didn't know how to enable it.

 

Thats the reason when i decided to give a try to update citadel.

First i tried to build the sources from scratch.

 

Unfortunately i got error messages when trying to run make:

Dependencies: gcc -M -I. -I ./include/  | sed -e 's!.o!.o /.o buildinfo!' > buildinfo
Compile: gcc -g -O2 -Wall -Wcast-qual -Wcast-align -Wstrict-prototypes -Wno-strict-aliasing -D_REENTRANT -pthread -I ./include/ -I. -I ./include/ -DHAVE_CONFIG_H -DDIFF="/usr/bin/diff" -DPATCH="/usr/bin/patch" -c  -o buildinfo
LDFLAGS:

serv_extensions.o: In function `CtdlRegisterProtoHook':
/usr/src/citadel/serv_extensions.c:273: undefined reference to `FourHash'
msgbase.o: In function `FillMsgKeyLookupTable':
/usr/src/citadel/msgbase.c:103: undefined reference to `FourHash'
msgbase.o: In function `CtdlWriteObject':
/usr/src/citadel/msgbase.c:3632: undefined reference to `StrBufBase64Append'
modules/instmsg/serv_instmsg.o: In function `flush_individual_conversation':
/usr/src/citadel/modules/instmsg/serv_instmsg.c:441: undefined reference to `StrBufRFC2047encodeMessage'
modules/migrate/serv_migrate.o: In function `migr_xml_end':
/usr/src/citadel/modules/migrate/serv_migrate.c:801: undefined reference to `StrBufDecodeBase64To'
collect2: error: ld returned 1 exit status
Makefile:134: recipe for target 'citserver' failed
make: *** [citserver] Error 1

Because i was not able to resolve these messages i went over to the "easy-install" script. That indeed did compiled successfully. However, the script was not able to run the setup procedure.

When i tried to run citserver 925 from the fresh build manually from /usr/local/citadel i was presented with the following:

citserver[1523]: Initializing configuration system
Your system is configured for LDAP authentication,
but you are running a server built without OpenLDAP support.

Lets stay honest: I have no clue if i need the update to enable starttls support on port 25 at all. So that might be the first question to answer before continuing...

 

Cheers

Steven

 



 



[#] Mon Oct 14 2019 02:18:03 EDT from TheOneLaw @ Uncensored

Subject: Re: STARTTLS on SMTP port 25

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

Attempting to replicate this but now all efforts end with no STARTTLS no matter how I reconfigure or re-install.
 I am guessing this is something inside the Debian 9 permissions but still too early to know any more.

{yes, I am using setcap ~+eip to ensure the port is open to citserver}

more later, someday



[#] Mon Oct 14 2019 04:04:02 EDT from alex007 @ Uncensored

Subject: Re: Email attachments

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

This issue was named in the past several times, not a solution yet, seems only occur with raspbian or raspi respectively

Sat Oct 05 2019 06:33:06 EDT from Skaterunner @ Uncensored Subject: Email attachments

Hi all,

Email attachments are still corrupted! 

Citadel installed on a raspberry pi 4. I use it on a standalone network for personal use. Email attachments are corrupted just going from one account to another without leaving the closed network. By corrupted I mean they can’t be read by the original program. I tried text files and libre doc files. This issue must have been addressed but I can’t find any info about remedies. Suggestions welcomed.

Sincerly Skaterunner




 



[#] Mon Oct 14 2019 15:57:06 EDT from TheOneLaw @ Uncensored

Subject: Re: STARTTLS on SMTP port 25

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

STARTTLS also missing

on DEBIAN BUSTER via easy-install.

 

wondering if this implicates anything important:

(from Debian stretch effort)

/usr/bin/ld: warning: libssl.so.1.0.2, needed by /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libcurl.so, may conflict with libssl.so.1.1
/usr/bin/ld: warning: libcrypto.so.1.0.2, needed by /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libcurl.so, may conflict with libcrypto.so.1.1



[#] Tue Oct 15 2019 11:52:11 EDT from simon2371 @ Uncensored

Subject: Citadel stop working BDB0075 DB_PAGE_NOTFOUND

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

Citadel had been working for months without issue. Out of not where it stops, and produces an error:

citserver[1522]: db: cdb_fetch(9): BDB0075 DB_PAGE_NOTFOUND: Requested page not found

Step I took trying to resolve this:

rebooted the server

rpm --rebuilddb

yum update

rpm -q rpm

rpm --rebuilddb

rpm -q rpm

rm -rf /var/lib/rpm/__db*

db_verify /var/lib/rpm/Packages

rpm --rebuilddb

grep rpm /etc/rc.d/rc.sysinit

rm -f /var/lib/rpm/__db* &> /dev/null

ps -aux | grep -e rpm -e yum -e up2date

lsof | grep /var/lib/rpm

rm -f /var/lib/rpm/__db*

cd /var/lib

tar -zcvf /var/preserve/rpmdb-$(date +%Y-%m-%d_%H-%M-%S).tar.gz rpm

cd /var/lib/rpm

rm -f __db*

/usr/lib/rpm/rpmdb_verify Packages

echo $?

rpm -vv --rebuilddb

cd /var/lib/rpm

/usr/lib/rpm/rpmdb_verify Packages

 

I even tried to reinstall citadel, same error. On the messages log:

Oct 15 11:22:37 gundam citserver[1763]: db: cdb_fetch(9): BDB0075 DB_PAGE_NOTFOUND: Requested page not found

Oct 15 11:22:37 gundam citserver: citserver[1763]: db: cdb_fetch(9): BDB0075 DB_PAGE_NOTFOUND: Requested page not found

Oct 15 11:22:37 gundam systemd: citadel.service: main process exited, code=exited, status=105/n/a

Oct 15 11:22:37 gundam systemd: Unit citadel.service entered failed state.

Oct 15 11:22:37 gundam systemd: citadel.service failed.

Oct 15 11:22:37 gundam systemd: citadel.service holdoff time over, scheduling restart.

Oct 15 11:22:37 gundam systemd: Stopped Citadel Server.

Oct 15 11:22:37 gundam systemd: start request repeated too quickly for citadel.service

Oct 15 11:22:37 gundam systemd: Failed to start Citadel Server.

Oct 15 11:22:37 gundam systemd: Unit citadel.service entered failed state.

Oct 15 11:22:37 gundam systemd: citadel.service failed.

 

 Can someone please help me out? Thank you.



[#] Tue Oct 15 2019 14:34:04 EDT from branco @ Uncensored

Subject: Unable to bind ports..user rights issue?

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

Hi guys, 

I have recently installed Citadel using the easy install, everything appears to work except the opening of ports. 

When i start the server i get this message in the console:

 

citserver[1632]: extensions: 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 0.0.0.0:504: (citadel-TCP) ;extensions: TCP port 0.0.0.0:143: (IMAP) ;extensions: TCP port 0.0.0.0:993: (IMAPS) ;extensions: TCP port 0.0.0.0:119: (NNTP) ;extensions: TCP port 0.0.0.0:563: (NNTPS) ;extensions: TCP port 0.0.0.0:110: (POP3) ;extensions: TCP port 0.0.0.0:995: (POP3S) ;extensions: TCP port 0.0.0.0:25: (SMTP-MTA) ;extensions: TCP port 0.0.0.0: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:

Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied

 

 

Is this a user rights issue? I created the user citadel during the installation process and gave it ownership of the entire /usr/local/citadel folder.

Web interface works fine and I've setup all required ports there, but it looks like citadel is not listening on any of them:

Active Internet connections (only servers)

Proto Recv-Q Send-Q Local Address           Foreign Address         State      

tcp        0      0 127.0.0.1:6010          0.0.0.0:*               LISTEN     

tcp        0      0 0.0.0.0:2020            0.0.0.0:*               LISTEN     

tcp        0      0 0.0.0.0:5222            0.0.0.0:*               LISTEN     

tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN     

tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN     

tcp6       0      0 ::1:6010                :::*                    LISTEN     

tcp6       0      0 :::443                  :::*                    LISTEN     

tcp6       0      0 :::80                   :::*                    LISTEN     

tcp6       0      0 :::22                   :::*                    LISTEN     

udp        0      0 127.0.0.53:53           0.0.0.0:*                          

udp        0      0 172.31.46.125:68        0.0.0.0:*        

 

Any help will be greatly appreciated. 

 

Cheers, 

Branco

 

 

 



[#] Tue Oct 15 2019 14:47:21 EDT from warbaby @ Uncensored

Subject: Re: Citadel stop working BDB0075 DB_PAGE_NOTFOUND

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

That's a Berkeley database error, not a system package error. Try the db cleanup/repair procedure. 

Database repair

Although Citadel's data store is quite reliable, database corruption can occur in rare instances. External factors such as an operating system crash or an unexpected loss of power might leave the database in an unknown state. A utility is provided which may be able to repair your database if this occurs. If you find that your Citadel server is not running, and reading the logs shows that it is crashing because of an inability to validate a database, follow these steps:

Stop the Citadel service with a command like ”/etc/init.d/citadel stop”

Make a backup of your data. Either write it out to tape or copy it to another directory, or a tarball.

“cd” to your Citadel directory and type ”./database_cleanup.sh”

Let the cleanup script run. Do not interrupt this process for any reason.

Restart the Citadel service with a command like ”/etc/init.d/citadel start”

If this procedure does not work, you must restore from your most recent backup.

http://www.citadel.org/doku.php?id=documentation:system_administration_manual

See also Importing/Exporting your Citadel database, same page.

 

 



[#] Tue Oct 15 2019 15:00:40 EDT from branco @ Uncensored

Subject: Unable to bind ports..user rights issue?

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

Hi guys, 

I have recently installed Citadel using the easy install, everything appears to work except the opening of ports. 

When i start the server i get this message in the console:

 

citserver[1632]: extensions: 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 0.0.0.0:504: (citadel-TCP) ;extensions: TCP port 0.0.0.0:143: (IMAP) ;extensions: TCP port 0.0.0.0:993: (IMAPS) ;extensions: TCP port 0.0.0.0:119: (NNTP) ;extensions: TCP port 0.0.0.0:563: (NNTPS) ;extensions: TCP port 0.0.0.0:110: (POP3) ;extensions: TCP port 0.0.0.0:995: (POP3S) ;extensions: TCP port 0.0.0.0:25: (SMTP-MTA) ;extensions: TCP port 0.0.0.0: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:

Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied

 

 

Is this a user rights issue? I created the user citadel during the installation process and gave it ownership of the entire /usr/local/citadel folder.

Web interface works fine and I've setup all required ports there, but it looks like citadel is not listening on any of them:

Active Internet connections (only servers)

Proto Recv-Q Send-Q Local Address           Foreign Address         State      

tcp        0      0 127.0.0.1:6010          0.0.0.0:*               LISTEN     

tcp        0      0 0.0.0.0:2020            0.0.0.0:*               LISTEN     

tcp        0      0 0.0.0.0:5222            0.0.0.0:*               LISTEN     

tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN     

tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN     

tcp6       0      0 ::1:6010                :::*                    LISTEN     

tcp6       0      0 :::443                  :::*                    LISTEN     

tcp6       0      0 :::80                   :::*                    LISTEN     

tcp6       0      0 :::22                   :::*                    LISTEN     

udp        0      0 127.0.0.53:53           0.0.0.0:*                          

udp        0      0 172.31.46.125:68        0.0.0.0:*        

 

Any help will be greatly appreciated. 

 

Cheers, 

Branco

 

 

 



[#] Tue Oct 15 2019 16:28:24 EDT from warbaby @ Uncensored

Subject: Joe Biden Collapse/Missed Space Issue In Subject Line

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

[This is is an actual programming defect, not system support.  I am not currently on the dev list, so am posting here instead.. ]

SYNOPSIS:  Message with Subject Line greater than 69 characters sent via SMTP has all whitespace greedily left trimmed from 69th char to the next printable char.  Sometimes a space character is the intended character at Subject pos 69. 

SCOPE:  Universal. 

VERSION: Citadel 921, ezinstall 

OS: Debian 8 "Jessie"

STEPS TO REPRODUCE: Send yourself a message through your Citadel box via SMTP, with the following subject line:

01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01

You will see, upon it's arrival it appears as:

01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 0101 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01

This, like Joe Biden, shows the consistent collapse on any character count past 69, regardless of whether it is a space or tab.  Whitespace at or after position "69" is trimmed to the next printable character.  
 
Here is an example Subject Line with 10 extra spaces: 

01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01          01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01

it is returned as 

01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 0101 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01

This issue also occurs with tabs. I did not test for all possible white space characters. 

ATTEMPTS TO RESOLVE:
 
Tested for condition.  I looked at code but did not find. I do not have environment set up to compile at this time. 
 
 
THOUGHTS:
 
It's probably very near an isspace() where the "short subject string" with a length of 69 is strcat() back together with "rest of subject string." I would consider the addition of a single space between the two parts to be a good solution.   I don't have much of an expectation of using tabs, bells, or form feeds in subject lines, although I do frequently like to have a space appearing at offset 69.  For such an minor issue, it has had a very bad effect on my self-esteem. I've had to talk to people about it. In all my carefully crafted long subject lines, I appear to have a broken spacebar or to write like Joe Biden. Correspondingly, I am recommending a priority level of "VERY HIGH". 
 
 


[#] Tue Oct 15 2019 16:53:28 EDT from warbaby @ Uncensored

Subject: Re: Unable to bind ports..user rights issue?

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

kill apache or nginx or whatever you have listening on 80 and 443, then try to start it again. 

Tue Oct 15 2019 03:00:40 PM EDT from branco @ Uncensored Subject: Unable to bind ports..user rights issue?

Hi guys, 

I have recently installed Citadel using the easy install, everything appears to work except the opening of ports. 

When i start the server i get this message in the console:

 

citserver[1632]: extensions: 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 0.0.0.0:504: (citadel-TCP) ;extensions: TCP port 0.0.0.0:143: (IMAP) ;extensions: TCP port 0.0.0.0:993: (IMAPS) ;extensions: TCP port 0.0.0.0:119: (NNTP) ;extensions: TCP port 0.0.0.0:563: (NNTPS) ;extensions: TCP port 0.0.0.0:110: (POP3) ;extensions: TCP port 0.0.0.0:995: (POP3S) ;extensions: TCP port 0.0.0.0:25: (SMTP-MTA) ;extensions: TCP port 0.0.0.0: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:

Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied

 

 

Is this a user rights issue? I created the user citadel during the installation process and gave it ownership of the entire /usr/local/citadel folder.

Web interface works fine and I've setup all required ports there, but it looks like citadel is not listening on any of them:

Active Internet connections (only servers)

Proto Recv-Q Send-Q Local Address           Foreign Address         State      

tcp        0      0 127.0.0.1:6010          0.0.0.0:*               LISTEN     

tcp        0      0 0.0.0.0:2020            0.0.0.0:*               LISTEN     

tcp        0      0 0.0.0.0:5222            0.0.0.0:*               LISTEN     

tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN     

tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN     

tcp6       0      0 ::1:6010                :::*                    LISTEN     

tcp6       0      0 :::443                  :::*                    LISTEN     

tcp6       0      0 :::80                   :::*                    LISTEN     

tcp6       0      0 :::22                   :::*                    LISTEN     

udp        0      0 127.0.0.53:53           0.0.0.0:*                          

udp        0      0 172.31.46.125:68        0.0.0.0:*        

 

Any help will be greatly appreciated. 

 

Cheers, 

Branco

 

 

 



 



[#] Tue Oct 15 2019 18:08:18 EDT from branco @ Uncensored

Subject: Unable to bind ports..user rights issue?

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

Hi guys, 

I have recently installed Citadel using the easy install, everything appears to work except the opening of ports. 

When i start the server i get this message in the console:

 

citserver[1632]: extensions: 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 0.0.0.0:504: (citadel-TCP) ;extensions: TCP port 0.0.0.0:143: (IMAP) ;extensions: TCP port 0.0.0.0:993: (IMAPS) ;extensions: TCP port 0.0.0.0:119: (NNTP) ;extensions: TCP port 0.0.0.0:563: (NNTPS) ;extensions: TCP port 0.0.0.0:110: (POP3) ;extensions: TCP port 0.0.0.0:995: (POP3S) ;extensions: TCP port 0.0.0.0:25: (SMTP-MTA) ;extensions: TCP port 0.0.0.0: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:

Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied

 

 

Is this a user rights issue? I created the user citadel during the installation process and gave it ownership of the entire /usr/local/citadel folder.

Web interface works fine and I've setup all required ports there, but it looks like citadel is not listening on any of them:

Active Internet connections (only servers)

Proto Recv-Q Send-Q Local Address           Foreign Address         State      

tcp        0      0 127.0.0.1:6010          0.0.0.0:*               LISTEN     

tcp        0      0 0.0.0.0:2020            0.0.0.0:*               LISTEN     

tcp        0      0 0.0.0.0:5222            0.0.0.0:*               LISTEN     

tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN     

tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN     

tcp6       0      0 ::1:6010                :::*                    LISTEN     

tcp6       0      0 :::443                  :::*                    LISTEN     

tcp6       0      0 :::80                   :::*                    LISTEN     

tcp6       0      0 :::22                   :::*                    LISTEN     

udp        0      0 127.0.0.53:53           0.0.0.0:*                          

udp        0      0 172.31.46.125:68        0.0.0.0:*        

 

Any help will be greatly appreciated. 

 

Cheers, 

Branco

 

 

 



[#] Tue Oct 15 2019 18:09:48 EDT from branco @ Uncensored

Subject: Re: Unable to bind ports..user rights issue?

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

Ports 80 and 443 are fine, i can connect to WebCit, and there is no apache or nginx - clean ubuntu server install. 

The issue are the other mail ports (265, 143, 587, etc)

 

BR, 

 

Branco

Tue Oct 15 2019 16:53:28 EDT from warbaby @ Uncensored Subject: Re: Unable to bind ports..user rights issue?

kill apache or nginx or whatever you have listening on 80 and 443, then try to start it again. 

Tue Oct 15 2019 03:00:40 PM EDT from branco @ Uncensored Subject: Unable to bind ports..user rights issue?

Hi guys, 

I have recently installed Citadel using the easy install, everything appears to work except the opening of ports. 

When i start the server i get this message in the console:

 

citserver[1632]: extensions: 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 0.0.0.0:504: (citadel-TCP) ;extensions: TCP port 0.0.0.0:143: (IMAP) ;extensions: TCP port 0.0.0.0:993: (IMAPS) ;extensions: TCP port 0.0.0.0:119: (NNTP) ;extensions: TCP port 0.0.0.0:563: (NNTPS) ;extensions: TCP port 0.0.0.0:110: (POP3) ;extensions: TCP port 0.0.0.0:995: (POP3S) ;extensions: TCP port 0.0.0.0:25: (SMTP-MTA) ;extensions: TCP port 0.0.0.0: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:

Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied

 

 

Is this a user rights issue? I created the user citadel during the installation process and gave it ownership of the entire /usr/local/citadel folder.

Web interface works fine and I've setup all required ports there, but it looks like citadel is not listening on any of them:

Active Internet connections (only servers)

Proto Recv-Q Send-Q Local Address           Foreign Address         State      

tcp        0      0 127.0.0.1:6010          0.0.0.0:*               LISTEN     

tcp        0      0 0.0.0.0:2020            0.0.0.0:*               LISTEN     

tcp        0      0 0.0.0.0:5222            0.0.0.0:*               LISTEN     

tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN     

tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN     

tcp6       0      0 ::1:6010                :::*                    LISTEN     

tcp6       0      0 :::443                  :::*                    LISTEN     

tcp6       0      0 :::80                   :::*                    LISTEN     

tcp6       0      0 :::22                   :::*                    LISTEN     

udp        0      0 127.0.0.53:53           0.0.0.0:*                          

udp        0      0 172.31.46.125:68        0.0.0.0:*        

 

Any help will be greatly appreciated. 

 

Cheers, 

Branco

 

 

 



 



 



[#] Wed Oct 16 2019 03:51:23 EDT from TheOneLaw @ Uncensored

Subject: Re: Unable to bind ports..user rights issue?

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

As I am having a related problem,

the question arises - does rebooting the system affect the port bindings ?

the reason I ask is that my system binds ports okay only on system boot
 but anytime I use the "restart now" inside webcit > administration citserver abandons everything.

( ports 80 and 443 are bound by webcit, not citserver)

Tue Oct 15 2019 18:09:48 EDT from branco @ Uncensored Subject: Re: Unable to bind ports..user rights issue?

Ports 80 and 443 are fine, i can connect to WebCit, and there is no apache or nginx - clean ubuntu server install. 

The issue are the other mail ports (265, 143, 587, etc)

 

BR, 

 

Branco

 

 



 



 



[#] Wed Oct 16 2019 12:25:48 EDT from TheOneLaw @ Uncensored

Subject: Re: STARTTLS on SMTP port 25

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

Looks like a Houdini moment.

In exasperation issued the STARTTLS command into a telnet test and the response was:

root@myoldmail:~# telnet xx.xx.xxx.xxx 25
Trying xx.xx.xxx.xxx...
Connected to xx.xx.xxx.xxx.
Escape character is '^]'.
220 mynewmail.org ESMTP Citadel server ready.
ehlo home
250-Hello home (xx.xx.xxx.xxx [xx.xx.xxx.xxx])
250-HELP
250-SIZE 10485760
250-AUTH LOGIN PLAIN
250-AUTH=LOGIN PLAIN
250 8BITMIME
STARTTLS
220 Begin TLS negotiation now
^C

huh.

If so then the only thing missing is the advertisement,

250 STARTTLS

 which may be just a cosmetic requirement ?:

According to ssl-tools.net the STARTTLS is working as needed but this is dubious - no email was 250actually sent..

Some method to require encryption for all inbound might be nice but not sure if that is even realistic...

 

Mon Oct 14 2019 15:57:06 EDT from TheOneLaw @ Uncensored Subject: Re: STARTTLS on SMTP port 25

STARTTLS also missing

on DEBIAN BUSTER via easy-install.

 

wondering if this implicates anything important:

(from Debian stretch effort)

/usr/bin/ld: warning: libssl.so.1.0.2, needed by /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libcurl.so, may conflict with libssl.so.1.1
/usr/bin/ld: warning: libcrypto.so.1.0.2, needed by /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libcurl.so, may conflict with libcrypto.so.1.1



 



[#] Wed Oct 16 2019 13:55:39 EDT from TheOneLaw @ Uncensored

Subject: Re: STARTTLS on SMTP port 25

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

Looks like port 25 has STARTTLS but nobody uses it due to the missing line?:

....citserver[519]: context: session (SMTP-MTA) started from ssl-tools.net...

Bail...

Wed Oct 16 2019 12:25:48 EDT from TheOneLaw @ Uncensored Subject: Re: STARTTLS on SMTP port 25

Looks like a Houdini moment.

In exasperation issued the STARTTLS command into a telnet test and the response was:

root@myoldmail:~# telnet xx.xx.xxx.xxx 25
Trying xx.xx.xxx.xxx...
Connected to xx.xx.xxx.xxx.
Escape character is '^]'.
220 mynewmail.org ESMTP Citadel server ready.
ehlo home
250-Hello home (xx.xx.xxx.xxx [xx.xx.xxx.xxx])
250-HELP
250-SIZE 10485760
250-AUTH LOGIN PLAIN
250-AUTH=LOGIN PLAIN
250 8BITMIME
STARTTLS
220 Begin TLS negotiation now
^C

huh.

If so then the only thing missing is the advertisement,

250 STARTTLS

 which may be just a cosmetic requirement ?:

According to ssl-tools.net the STARTTLS is working as needed but this is dubious - no email was 250actually sent..

Some method to require encryption for all inbound might be nice but not sure if that is even realistic...

 



[#] Thu Oct 17 2019 08:51:01 EDT from TheOneLaw @ Uncensored

Subject: SMTP MSA on Port 25 serving SMTP MTA inbound connections

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

I was truly hoping this would not be necessary,

but it does appear that

c3rebro2

found the best answer which simply looks like this:

 

 

It does seem to work with most of the mail servers I need to receive from,

now they choose to use encryption during SMTP connections,

unlike how they connected on the MTA port - bareskin naked with no encryption at all.

Works for now, hope this helps someone.

 

 

 Sat Jun 08 2019 18:14:39 EDT from c3rebro2 @ Uncensored

Yeah - you're right. Maybe i should have left it alone.

I now reverted all changes (restored a full server backup after the -self modified- install scripts messed up the system with several changes).

The final solution currently looks really weird to me but seem to work:

 

- Network configuration: I re-mapped my msa port 587 to the mta port 25 in the wan to lan rules.

- In Citadel: i disabled the mta port 25 completely and changed the msa port to 25.

 

I have really no clue if this is how it is supposed to be. but: if i now send a mail to myself from e.g. gmail, gmx or company account i can see the starttls init procedure which was missing before. Iam really too lazy to switch to a postfix, dovecot and roundcube setup (including migration of gigs of mail data).



 



[#] Tue Oct 22 2019 12:27:48 EDT from simon2371 @ Uncensored

Subject: Re: Citadel stop working BDB0075 DB_PAGE_NOTFOUND

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

Thank you.Its works!!



[#] Wed Oct 23 2019 03:36:16 EDT from madadam @ Uncensored

Subject: ctdlmigrate problem

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

Hi,

I have a nicely working citadel (824)  on a RaspberryPi (raspbian, jessie).

Trying to migrate to freshly installed citadel (917) on PC (x86_64, Ubuntu 18.04).

It all seems to go well, apart from some inconsequential locale warnings, but it ends with "*** Citadel migration was unsuccessful. ***". See the attached screenlog.txt.

syslog:
 citserver[1873]: sysdep: client_read_blob() failed: StrBufReadBLOBBuffered: to many selects; aborting.

Is there any way of circumventing this without having to change the code?

Thanks,
Marge



screenlog.txt (text/plain, 5769 bytes) [View| Download]
Go to page: First ... 14 15 16 17 [18] 19 20 21 22