Language:
switch to room list switch to menu My folders
Go to page: First ... 16 17 18 19 [20]
[#] 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

 

 



 



 



Go to page: First ... 16 17 18 19 [20]