Language:
switch to room list switch to menu My folders
Go to page: First ... 14 15 16 17 [18] 19 20 21 22 ... Last
[#] Tue Aug 19 2014 02:14:41 EDT from dothebart @ Uncensored

Subject: Re: Delivery failure

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

[#] Thu Aug 21 2014 04:05:29 EDT from tigerteron @ Uncensored

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

hi dear i have problem after upgrade citadel when i send mail from asp.net application i get following error:
Mailbox unavailable. The server response was: You must log in to send mail
please help me
thanks best regards



[#] Thu Aug 21 2014 10:59:51 EDT from IGnatius T Foobar @ Uncensored

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

Does your asp.net SMTP connector have the ability to authenticate? If so, please supply a username and password that are valid on the Citadel system and you will succeed. Otherwise Citadel is assuming that you are trying to exploit it as an open relay.

[#] Thu Aug 21 2014 11:04:02 EDT from dothebart @ Uncensored

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

 

Thu Aug 21 2014 04:05:29 EDT from tigerteron @ Uncensored

hi dear i have problem after upgrade citadel when i send mail from asp.net application i get following error:
Mailbox unavailable. The server response was: You must log in to send mail
please help me
thanks best regards

Relaying isn't supported without authentication; if you originate (send from) a user of this system, you have to log in.

 



[#] Fri Aug 22 2014 07:59:30 EDT from puig @ Uncensored

Subject: IMAP problems every day

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

Hi, I very new in citadel server, but it seems to be configured properly (I can send and receive emails, connect with an IMAP client, etc).

The problem I have is every day or 2 days I have to restart the citadel service because all IMAP clients cannot communicate to it.

It is only a restart, bu I have to do it once a day and is very frustrating when you're out of office.

Log messages don't show any error despite of:

mail citserver[28114]: No external notifiers configured on system/user

Every minute.

 

Server is under Debian 7.5

Thanks for your help!



[#] Fri Aug 22 2014 10:10:54 EDT from puig @ Uncensored

Subject: Re: [Citadel Support] Failing yum update [Reply] [ReplyQuoted] [Heade

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

Hi Steve, thanks for your answer. This is what I have installed:

Package citadel-client:                
i A 8.14-2                                                               stable                                            500

Package citadel-dbg:
p   8.14-2                                                               stable                                            500

Package citadel-doc:
p   8.14-2                                                               stable                                            500

Package citadel-mta:
i   8.14-2                                                               stable                                            500

Package citadel-server:
i A 8.14-2                                                               stable                                            500

Package citadel-suite:
i   8.14-dfsg-1                                                          stable                                            500

Package citadel-webcit:
i A 8.14-dfsg-1                                                          stable                                            500

Package libcitadel-dev:
p   8.14-1                                                               stable                                            500

Package libcitadel3:
i A 8.14-1                                                               stable                                            500

Package libcitadel3-dbg:
p   8.14-1                                                               stable                                            500

Package libnet-citadel-perl:
p   0.02-1                                                               stable                                            500

 

I've installed it from default debian sources via apt:

deb http://ftp.es.debian.org/debian/ wheezy main
deb-src http://ftp.es.debian.org/debian/ wheezy main

I tried to install citadel-selinux but apt cannot find it, do you know a source from apt from where to be installed?

 

Thank you!



[#] Sat Aug 23 2014 13:55:56 EDT from toscho @ Uncensored

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

Hi,

 

I have set up a citadel server and can successfully use it for email. But I can't get it to sync with thunderbird via groupdav.

I have installed the SOGo-Connector-plugin and try to add remote address books or network calendars in the places specified by the documentation:

my.domain/groupdav/

my.domain/groudav/Calendar

my.domain/groupdav/Contacts

 

Whenever I'm asked to authenticate, I give my usual account name and password (which I also use to log into webcit) but it doesn't accept it and syncs.

 

What am I doing wrong?

 

ciao

 

Toscho



[#] Sun Aug 24 2014 13:42:40 EDT from herpi @ Uncensored

Subject: Sync error

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

Hi,

I've set up a Citadel server and I've created a user in it. I have Outlook 2003 on my desktop. I've installed the Webdav Collaborator plugin.
I tried to "Configure for DAV" my local Outlook calendar with the following settings:
username: <username>
password. <password>
Server URL: https://mydomain.com/groupdav/Calendar/calendar.ics

When I tried to syncronize the calendar folder, I got error message:  The resource pointed to by the requested URL was not found on the server. 

What am I doing wrong? Is it the correct URL for the Citadel calendar?

Cheers,

Herpi
 



[#] Mon Aug 25 2014 04:24:48 EDT from "Stefan Jakobs" <stefan@localside.net> to room_citadel_support@uncensored.citadel.org

Subject: Re: [Citadel Support] Failing yum update

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

You wrote:
Hi Steve, thanks for your answer. This is what I have installed:

Package citadel-client:
....

I've installed it from default debian sources via apt:

deb http://ftp.es.debian.org/debian/ wheezy main
deb-src http://ftp.es.debian.org/debian/ wheezy main

I tried to install citadel-selinux but apt cannot find it, do you know a
source from apt from where to be installed?

OK, now I'm confused. The subject says "Failing yum update" which indicates
that you're using fedora or RHEL/CentOS. But now you're talking about apt and
debian. As far as I know debian doesn't use selinux. The citadel-selinux
package I mentioned is only available for fedora, RHEL/CentOS.

You should probably use the more recent citadel versions from citadel.org.
See: http://www.citadel.org/doku.php/installation:debian

Thank you!

Regards
Stefan

[#] Fri Aug 29 2014 17:05:09 EDT from platonov @ Uncensored

Subject: How to compress the database?

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

My database grew up to huge size (>11 GB).

Is there a way to compress it and recover tons of wasted space?

 



[#] Fri Aug 29 2014 18:03:54 EDT from IGnatius T Foobar @ Uncensored

Subject: Re: How to compress the database?

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

Is it the database that has grown, or the log files? You can turn on automatic log file removal, if that's what's causing all of the space consumption.

[#] Sat Aug 30 2014 04:22:12 EDT from platonov @ Uncensored

Subject: Re: How to compress the database?

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

 

Fri Aug 29 2014 18:03:54 EDT from IGnatius T Foobar @ Uncensored Subject: Re: How to compress the database?
Is it the database that has grown, or the log files? You can turn on automatic log file removal, if that's what's causing all of the space consumption.

It is the database itself that has grown. One of cdb.* files in particular.

I already turned on automatic log file removal.

 



[#] Sat Aug 30 2014 04:51:20 EDT from platonov @ Uncensored

Subject: Citserver can't start because database got screwed up

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

Sorry to bother,

I ran out of disk space and found a lot of log.* files in about 20 log.* files in /usr/local/citadel/data (Ubuntu 14.04).

So, I removed all the log files and I guess it screwed up the database.

I am getting this in syslog:

Aug 30 11:43:56 preciseinfo citserver[3521]: DB: file cdb.00 has LSN 17296/3999708, past end of log at 1/28
Aug 30 11:43:56 preciseinfo citserver[3521]: DB: Commonly caused by moving a database from one database environment
Aug 30 11:43:56 preciseinfo citserver[3521]: DB: to another without clearing the database LSNs, or by removing all of
Aug 30 11:43:56 preciseinfo citserver[3521]: DB: the log files from a database environment
Aug 30 11:43:56 preciseinfo citserver[3521]: DB: the log files from a database environment
Aug 30 11:43:56 preciseinfo citserver[3521]: DB: __db_meta_setup: /usr/local/citadel/data/cdb.00: unexpected file type or format
Aug 30 11:43:56 preciseinfo citserver[3521]: DB: __db_meta_setup: /usr/local/citadel/data/cdb.00: unexpected file type or format
Aug 30 11:43:56 preciseinfo citserver[3521]: db_open[00]: Invalid argument
Aug 30 11:43:56 preciseinfo citserver[3521]: exit code 22

How can I recover?

 

 



[#] Mon Sep 01 2014 15:49:21 EDT from IGnatius T Foobar @ Uncensored

Subject: Re: Citserver can't start because database got screwed up

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

You can't. Deleting uncommitted log files will absolutely corrupt your database beyond repair. The automatic log file removal built in to Citadel is designed to only remove the ones that are fully committed and no longer needed by the system.

I'm sorry to say that you're going to have to restore from your latest complete backup.

[#] Mon Sep 01 2014 21:51:36 EDT from platonov @ Uncensored

Subject: Re: Citserver can't start because database got screwed up

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

 

Mon Sep 01 2014 15:49:21 EDT from IGnatius T Foobar @ Uncensored Subject: Re: Citserver can't start because database got screwed up
You can't. Deleting uncommitted log files will absolutely corrupt your database beyond repair. The automatic log file removal built in to Citadel is designed to only remove the ones that are fully committed and no longer needed by the system.

I'm sorry to say that you're going to have to restore from your latest complete backup.

Yep. I realized that pretty quickly and that is what we have done. But it was a mess in a situation where you run out of disk space.

So, now we have a backup of the database and in that backup we include only the last log.NNN file. Is that a correct assumption?

Also, since restoring from a backup, there appears to be a room with blank name and I tried to do all sorts of things to remove it, but no luck. I am curious about where did it come from and what can I do to clean it up or out.


Another thing is I view all my rooms in mbox format and I like it sorted in the latest date first order. It used to work fine. But now, even if I change that order it only works for as long as I don't leave that room. If I access that room again via Rooms->Room Name, it falls back on oldest day first order. I looked for some setting in Webcit but do not seem to see anything anywhere? How can I fix this?

And the last thing, I notice a lot of "Not found" messages especially when I try to move messages from one room to another. I have a room where I store all the messages I'd like to keep and so I have to move messages around all the time.

There are variations on "Not found" message. Don't recall exactly at the moment, but something like "Object does not exist" or "Invalid object" or something along those lines.

Are there any plans to fix these "Not found" situations?

 



[#] Mon Sep 01 2014 23:14:56 EDT from IGnatius T Foobar @ Uncensored

Subject: Re: Citserver can't start because database got screwed up

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

In a Berkeley DB environment (such as Citadel), you can use the db_archive utility to list the names of all log files which are no longer in use.

Man page for db_archive: http://docs.oracle.com/cd/E17275_01/html/api_reference/C/db_archive.html

In an Easy Install system you'll find db_archive in /usr/local/ctdlsupport/bin/db_archive , run it from /usr/local/citadel/data to hit your Citadel database.

Really though, it's easier to just let Citadel take care of this for you.
The only reason we make it an option not to automatically delete logs in the first place is because some people like to write scripts that delete them manually only after a successful backup has been run.

[#] Wed Sep 03 2014 12:33:03 EDT from platonov @ Uncensored

Subject: Re: How to compress the database?

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

 

Sat Aug 30 2014 04:22:12 EDT from platonov @ Uncensored Subject: Re: How to compress the database?

 

Fri Aug 29 2014 18:03:54 EDT from IGnatius T Foobar @ Uncensored Subject: Re: How to compress the database?
Is it the database that has grown, or the log files? You can turn on automatic log file removal, if that's what's causing all of the space consumption.

It is the database itself that has grown. One of cdb.* files in particular.

I already turned on automatic log file removal.

Somehow I doubt that I do have > 11 GB of actual data in the database.

Question: will database (cdb.* files) reduce in size if I try to set a shorter expiration interval on messages in some big rooms?

Or the cdb files will still remain the same size?

In that case, is is a good idea to try to dump the database to XML files and then try to restore it to see if database size decreases?



[#] Wed Sep 03 2014 14:41:09 EDT from IGnatius T Foobar @ Uncensored

Subject: Re: How to compress the database?

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


cdb.* files (as with any Berkeley DB files) never shrink. When you delete data from them, space within the files is marked as unused, and can be re-used for new data.

The effect of this is that when you delete data from Citadel (or anything that uses Berkeley DB), the files will not shrink, but new data will not make them grow any more.

[#] Wed Sep 03 2014 17:31:34 EDT from platonov @ Uncensored

Subject: Re: How to compress the database?

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

 

Wed Sep 03 2014 14:41:09 EDT from IGnatius T Foobar @ Uncensored Subject: Re: How to compress the database?

cdb.* files (as with any Berkeley DB files) never shrink. When you delete data from them, space within the files is marked as unused, and can be re-used for new data.

The effect of this is that when you delete data from Citadel (or anything that uses Berkeley DB), the files will not shrink, but new data will not make them grow any more.

Thanx IGnatius,

That's what I suspected. I'd like to try to dump the database to XML in that case and then restore it from the, if that is the right idea in your opinion.

I saw a couple of times lots of log files that filled the disk completely. So, I have removed all of them but the last one in sequence.

Not sure what it was, but it looked like some attack or something like that. I think I did already have the automatic removal of log flags set at that time.

If you happen to have the link to the instructions on how to dump/restore the database to XML, would be appreciated. I am really swamped here with all sorts of nasty lil things related to running out of disk space and upgrade of BTSync to 1.4.72.




[#] Thu Sep 04 2014 03:35:54 EDT from dothebart @ Uncensored

Subject: Re: How to compress the database?

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

 

Wed Sep 03 2014 17:31:34 EDT from platonov @ Uncensored Subject: Re: How to compress the database?

 

Wed Sep 03 2014 14:41:09 EDT from IGnatius T Foobar @ Uncensored Subject: Re: How to compress the database?

cdb.* files (as with any Berkeley DB files) never shrink. When you delete data from them, space within the files is marked as unused, and can be re-used for new data.

The effect of this is that when you delete data from Citadel (or anything that uses Berkeley DB), the files will not shrink, but new data will not make them grow any more.

Thanx IGnatius,

That's what I suspected. I'd like to try to dump the database to XML in that case and then restore it from the, if that is the right idea in your opinion.

I saw a couple of times lots of log files that filled the disk completely. So, I have removed all of them but the last one in sequence.

Not sure what it was, but it looked like some attack or something like that. I think I did already have the automatic removal of log flags set at that time.

If you happen to have the link to the instructions on how to dump/restore the database to XML, would be appreciated. I am really swamped here with all sorts of nasty lil things related to running out of disk space and upgrade of BTSync to 1.4.72.




you can use

sendcommand MIGR > /tmp/dump.xml

Please note that in git master are some serious performance boosts to the dump/import facility by switching i.e. the base64 de/encoder; you may consider using this.

One problem seems to still be there in the smtp auth; so you may want to revert the upgrade after your dump/import.



Go to page: First ... 14 15 16 17 [18] 19 20 21 22 ... Last