Language:
switch to room list switch to menu My folders
Go to page: 1 2 3 4 5 [6] 7 8 9 10 ... Last
[#] Mon Sep 26 2016 11:58:45 EDT from IGnatius T Foobar @ Uncensored

Subject: Re: ctdlmigrate question regarding the xml file

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

ctdlmigrate uses an SSH connection between the two systems to do its thing.
You shouldn't have to store the XML file anywhere.

That having been said ... the export format is more robust and reliable in Citadel 9XX, so you might want to upgrade first. But it sounds like you might be using the RPM packages, and I don't know the current status of those.

[#] Mon Sep 26 2016 13:07:06 EDT from nutbeam @ Uncensored

Subject: Re: ctdlmigrate question regarding the xml file

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

 

Mon Sep 26 2016 11:58:45 EDT from IGnatius T Foobar @ Uncensored Subject: Re: ctdlmigrate question regarding the xml file
ctdlmigrate uses an SSH connection between the two systems to do its thing.
You shouldn't have to store the XML file anywhere.

That having been said ... the export format is more robust and reliable in Citadel 9XX, so you might want to upgrade first. But it sounds like you might be using the RPM packages, and I don't know the current status of those.

Oh. I was thinking that the ctdlmigrate tool does an export of an xml file and then copies it to the target system and then does an import of that xml file. That was the impression I got reading the documentation.


I'm using the rpm files where the latest  is 8.24-10.2

I'm migrating approx 45GB of email.

Would it be safer to manually migrate the databases using sendcommand "MIGR export" and import?



[#] Tue Sep 27 2016 12:15:22 EDT from IGnatius T Foobar @ Uncensored

Subject: Re: ctdlmigrate question regarding the xml file

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

Would it be safer to manually migrate the databases using sendcommand "MIGR

export" and import?

Yes, but keep in mind that if you're on Citadel 8XX instead of Citadel 9XX, there are some other directories you need to bring over:

netconfigs
info
userpics
bio
keys

The contents of those directories are not in any architecture-specific format so you can simply copy them to the new system.

We realized this was awkward so most of that stuff has been integrated into the database as of version 902 (yes we removed the decimal points from the version numbers) so it gets exported with everything else.

[#] Tue Sep 27 2016 12:17:57 EDT from nutbeam @ Uncensored

Subject: Re: ctdlmigrate question regarding the xml file

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

 

Tue Sep 27 2016 12:15:22 EDT from IGnatius T Foobar @ Uncensored Subject: Re: ctdlmigrate question regarding the xml file
Would it be safer to manually migrate the databases using sendcommand "MIGR

export" and import?

Yes, but keep in mind that if you're on Citadel 8XX instead of Citadel 9XX, there are some other directories you need to bring over:

netconfigs
info
userpics
bio
keys

The contents of those directories are not in any architecture-specific format so you can simply copy them to the new system.

We realized this was awkward so most of that stuff has been integrated into the database as of version 902 (yes we removed the decimal points from the version numbers) so it gets exported with everything else.

Thanks. That is helpful :-)



[#] Wed Sep 28 2016 06:05:07 EDT from iX315 @ Uncensored

Subject: easyinstall

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

got a nice error installing citadel via easyinstall:

cp: cannot stat '/home/willi/Downloads/discount*z'

see easyinstall.sh @ line 356 !

____________________

but the real question is... who is willi ?



[#] Fri Sep 30 2016 17:35:05 EDT from axionjoey @ Uncensored

Subject: Citadel won't save changes to Contact

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

Hi,

 

We just installed citadel and we love it so far. But now when we try to edit and existing contact (or example adding an Internet e-mail aliases) it doesn't save. There are no error message the data simply isn't saved. Any help would be greatly appreciated.



[#] Fri Sep 30 2016 17:41:07 EDT from axionjoey @ Uncensored

Subject: Re: Citadel won't save changes to Contact

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

A little more info. Whenever we try to apply an update this appears in /var/log/messages

 

citserver[80]: CC[7]MSG CtdlFetchMessage(0, 1) Failed!

 


[#] Sun Oct 02 2016 10:31:42 EDT from alban @ Uncensored

Subject: SSL_accept failure sometimes, from Outlook on imap 993 SSL

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

Hi!

I have installed citadel on a debian 8 server. Imap is SSL 993, and SSL certificates are configured using let's encrypt.

Using Mozilla Thunderbird, syncing on my IMAP account works flawlessly everytime.

However, using Microsoft Outlook, sometimes (1/3 times) I get an error 0x800CCC0E when attempting to sync.

On the server side, in /var/log/daemon.log, I get

imap SSL_accept failed: retval=-1, errval=1, err=error:00000001:lib(0):func(0):reason(1)

Now, error 1 is SSL_ERROR_SSL, but I can't seem to be able to get more information.

 

Retrying usually works. Many of my users will be using Outlook to connect.

Any ideas?

Thank you for your help!



[#] Mon Oct 03 2016 00:25:54 EDT from nutbeam @ Uncensored

Subject: Re: ctdlmigrate question regarding the xml file

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

 

Tue Sep 27 2016 12:15:22 EDT from IGnatius T Foobar @ Uncensored Subject: Re: ctdlmigrate question regarding the xml file
Would it be safer to manually migrate the databases using sendcommand "MIGR

export" and import?

Yes, but keep in mind that if you're on Citadel 8XX instead of Citadel 9XX, there are some other directories you need to bring over:

netconfigs
info
userpics
bio
keys

The contents of those directories are not in any architecture-specific format so you can simply copy them to the new system.

We realized this was awkward so most of that stuff has been integrated into the database as of version 902 (yes we removed the decimal points from the version numbers) so it gets exported with everything else.

I tried to import the xml file using sendcommand -w60 "MIGR import" < /mnt/citbackup/exported.xml

and it runs for a short time and I get this and it stops with the message "Alarm clock"

200 dberp1 Citadel server ADMIN CONNECTION ready.

MIGR import

400 sock it to me

Alarm clock

 

Any ideas what is going wrong?

 



[#] Mon Oct 03 2016 15:19:03 EDT from gabovsky @ Uncensored

Subject: Contacts

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

Hello, Welcome!

Today i installed a brandnew Ubuntu server with Citadel "Easy Install" and so far everthing ok, burt i cant create Cotacts. I tried with 4 diferend Users, doesn´t work. Anny Ideas? thx



[#] Tue Oct 04 2016 06:40:50 EDT from gabovsky2 @ Uncensored

Subject: Adressbook istnt working

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

Hi,

I installed Citadel on Ubuntuserver 16.04.1 via Easy-Install weblink...

 And everthing works fine but not the Adressbook. Icreated 4 different User, but its not possible to enter new Contacts into the Adressbook. I also tried to make new Rooms as Adressbokk, but this doese not matter. Any ideas? 

 

thx a lot

 



[#] Tue Oct 04 2016 12:32:17 EDT from gabovsky2 @ Uncensored

Subject: Re: Adressbook istnt working

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

OMG! Is there anybody out there?



[#] Wed Oct 05 2016 14:52:04 EDT from docmathoc @ Uncensored

Subject: citadel.socket file

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

Hi All,

 

Compiling on an LFS system (NuTyX) gives no errors, but fails at setup.

No citadel-admin.socket is created when the citserver starts.

I looked at the -i0.0.0.0 solution but this appears to be for webcit, and that's not running yet.

Everything in the three directories (citadel, webcit, ctdlsupoort) is owned by citadel, group root.

Command line 'setup' from in the home directory fails with:

Connecting to Citadel server

       Error

Setup could not connect to a running Citadel server.: No such file or directory /usr/local/citadel/citadel-admin.socket

 

sys.log, daemon.log have no useful output that I can find.

/tmp/citadel-install-log.txt offers no clues to me as compilation and install appears successful.

 

Please be gentle with me if this is very very obvious, but any help to sort this out would be greatly appreciated - and one more platform for citadel.

Many thanks!



[#] Wed Oct 05 2016 16:41:56 EDT from nutbeam @ Uncensored

Subject: Re: ctdlmigrate question regarding the xml file

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

 

Mon Oct 03 2016 00:25:54 EDT from nutbeam @ Uncensored Subject: Re: ctdlmigrate question regarding the xml file

 

Tue Sep 27 2016 12:15:22 EDT from IGnatius T Foobar @ Uncensored Subject: Re: ctdlmigrate question regarding the xml file
Would it be safer to manually migrate the databases using sendcommand "MIGR

export" and import?

Yes, but keep in mind that if you're on Citadel 8XX instead of Citadel 9XX, there are some other directories you need to bring over:

netconfigs
info
userpics
bio
keys

The contents of those directories are not in any architecture-specific format so you can simply copy them to the new system.

We realized this was awkward so most of that stuff has been integrated into the database as of version 902 (yes we removed the decimal points from the version numbers) so it gets exported with everything else.

I tried to import the xml file using sendcommand -w60 "MIGR import" < /mnt/citbackup/exported.xml

and it runs for a short time and I get this and it stops with the message "Alarm clock"

200 dberp1 Citadel server ADMIN CONNECTION ready.

MIGR import

400 sock it to me

Alarm clock

 

Any ideas what is going wrong?

 



So "Alarm clock" is a watchdog error? I set it to five minutes and after five minutes I got the "Alarm clock error". So from this I'm thinking I have to estimate how long it's going to take to import this 58GB xml file and set the flag -w to a little longer than that in a seconds value. I am right in this assumption?



[#] Mon Oct 10 2016 17:11:32 EDT from nutbeam @ Uncensored

Subject: Re: ctdlmigrate question regarding the xml file

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

 

Wed Oct 05 2016 16:41:56 EDT from nutbeam @ Uncensored Subject: Re: ctdlmigrate question regarding the xml file

 

Mon Oct 03 2016 00:25:54 EDT from nutbeam @ Uncensored Subject: Re: ctdlmigrate question regarding the xml file

 

Tue Sep 27 2016 12:15:22 EDT from IGnatius T Foobar @ Uncensored Subject: Re: ctdlmigrate question regarding the xml file
Would it be safer to manually migrate the databases using sendcommand "MIGR

export" and import?

Yes, but keep in mind that if you're on Citadel 8XX instead of Citadel 9XX, there are some other directories you need to bring over:

netconfigs
info
userpics
bio
keys

The contents of those directories are not in any architecture-specific format so you can simply copy them to the new system.

We realized this was awkward so most of that stuff has been integrated into the database as of version 902 (yes we removed the decimal points from the version numbers) so it gets exported with everything else.

I tried to import the xml file using sendcommand -w60 "MIGR import" < /mnt/citbackup/exported.xml

and it runs for a short time and I get this and it stops with the message "Alarm clock"

200 dberp1 Citadel server ADMIN CONNECTION ready.

MIGR import

400 sock it to me

Alarm clock

 

Any ideas what is going wrong?

 



So "Alarm clock" is a watchdog error? I set it to five minutes and after five minutes I got the "Alarm clock error". So from this I'm thinking I have to estimate how long it's going to take to import this 58GB xml file and set the flag -w to a little longer than that in a seconds value. I am right in this assumption?



Ok. So now I set the watchdog long enough so the import is done. I shutdown citadel when I get a prompt back. I try to start it and I get this:

Broadcast message from systemd-journald@email.xxxxxxxxx.com (Mon 2016-10-10 17:07:28 EDT):

citserver[7617]: configuration setting c_default_cal_zone is empty, but must not - check your config!


Message from syslogd@email at Oct 10 17:07:28 ...
 citserver[7617]:configuration setting c_default_cal_zone is empty, but must not - check your config!

Broadcast message from systemd-journald@email.xxxxxxxxxx.com (Mon 2016-10-10 17:07:29 EDT):

citserver[7617]: bdb(): cursor still in progress on cdb 02: attempt to write during r/o cursor


Message from syslogd@email at Oct 10 17:07:29 ...
 citserver[7617]:bdb(): cursor still in progress on cdb 02: attempt to write during r/o cursor

Any ideas on what is wrong? Is citadel still doing something regarding the import even after I get a prompt back? Is shutting it down to restart it trashing something? I didn't get any errors during the export or import.



[#] Thu Oct 13 2016 11:27:59 EDT from nutbeam @ Uncensored

Subject: Re: ctdlmigrate question regarding the xml file

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

 

Mon Oct 10 2016 17:11:32 EDT from nutbeam @ Uncensored Subject: Re: ctdlmigrate question regarding the xml file

 

Wed Oct 05 2016 16:41:56 EDT from nutbeam @ Uncensored Subject: Re: ctdlmigrate question regarding the xml file

 

Mon Oct 03 2016 00:25:54 EDT from nutbeam @ Uncensored Subject: Re: ctdlmigrate question regarding the xml file

 

Tue Sep 27 2016 12:15:22 EDT from IGnatius T Foobar @ Uncensored Subject: Re: ctdlmigrate question regarding the xml file
Would it be safer to manually migrate the databases using sendcommand "MIGR

export" and import?

Yes, but keep in mind that if you're on Citadel 8XX instead of Citadel 9XX, there are some other directories you need to bring over:

netconfigs
info
userpics
bio
keys

The contents of those directories are not in any architecture-specific format so you can simply copy them to the new system.

We realized this was awkward so most of that stuff has been integrated into the database as of version 902 (yes we removed the decimal points from the version numbers) so it gets exported with everything else.

I tried to import the xml file using sendcommand -w60 "MIGR import" < /mnt/citbackup/exported.xml

and it runs for a short time and I get this and it stops with the message "Alarm clock"

200 dberp1 Citadel server ADMIN CONNECTION ready.

MIGR import

400 sock it to me

Alarm clock

 

Any ideas what is going wrong?

 



So "Alarm clock" is a watchdog error? I set it to five minutes and after five minutes I got the "Alarm clock error". So from this I'm thinking I have to estimate how long it's going to take to import this 58GB xml file and set the flag -w to a little longer than that in a seconds value. I am right in this assumption?



Ok. So now I set the watchdog long enough so the import is done. I shutdown citadel when I get a prompt back. I try to start it and I get this:

Broadcast message from systemd-journald@email.xxxxxxxxx.com (Mon 2016-10-10 17:07:28 EDT):

citserver[7617]: configuration setting c_default_cal_zone is empty, but must not - check your config!


Message from syslogd@email at Oct 10 17:07:28 ...
 citserver[7617]:configuration setting c_default_cal_zone is empty, but must not - check your config!

Broadcast message from systemd-journald@email.xxxxxxxxxx.com (Mon 2016-10-10 17:07:29 EDT):

citserver[7617]: bdb(): cursor still in progress on cdb 02: attempt to write during r/o cursor


Message from syslogd@email at Oct 10 17:07:29 ...
 citserver[7617]:bdb(): cursor still in progress on cdb 02: attempt to write during r/o cursor

Any ideas on what is wrong? Is citadel still doing something regarding the import even after I get a prompt back? Is shutting it down to restart it trashing something? I didn't get any errors during the export or import.



Any chance of some helpful hints, pointers etc., on this in the next couple of days? I want to attempt migrating systems again this weeked.

 

Thanks.



[#] Thu Oct 13 2016 12:43:15 EDT from IGnatius T Foobar @ Uncensored

Subject: Re: ctdlmigrate question regarding the xml file

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

citserver[7617]: bdb(): cursor still in progress on cdb 02: attempt to
write
during r/o cursor

This kind of error usually means you somehow got two instances of citserver running simultaneously. Doing so will almost certainly corrupt your database.
The locking mechanism that kept this from happening is not present in Citadel Server versions 900 through 902, but will appear again in the next release.

[#] Fri Oct 14 2016 13:44:45 EDT from nutbeam @ Uncensored

Subject: Re: ctdlmigrate question regarding the xml file

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

Any idea what is causing that? Used Easy Install on CentOS 7. No errors during the install and only this one when starting citadel:

Broadcast message from systemd-journald@email.electroconnectinc.com (Fri 2016-10-14 13:40:23 EDT):

citserver[14596]: configuration setting c_default_cal_zone is empty, but must not - check your config!

 

 



[#] Mon Oct 17 2016 12:37:11 EDT from nutbeam @ Uncensored

Subject: Re: ctdlmigrate question regarding the xml file

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

My citadel migration is not going well.

I did a fresh install using the Easy Install method to a CentOS 7 (1511) x86_64 box. No errors during the install, entered values into setup, etc. Did not log in.

Citadel server gives this error  on starting "citserver[17964]: configuration setting c_default_cal_zone is empty, but must not - check your config!" but starts.

Webcit gives a login screen so it is connecting ok to citadel. I shut down citadel and webcit, and started them up again. No errors except the one above.

I did an export from the CentOS 5 (i686) box, Citadel 8.24, using MIGR export. Takes a few hours (47GB databases to 58GB XML file). Nobody is connected and no errors during the export.

I did an import using a very long watchdog (-w18000) as it takes hours to import. It finished with no errors reported. I waited about ten minutes then checked the citadel processes to make sure they weren't busy still doing something. I shut down citadel and checked it wasn't running.

I started up citadel and I got the c_default_cal_zone error and "citserver[17964]: bdb(): cursor still in progress on cdb 02: attempt to write during r/o cursor" error message. Citadel did not start.

I was using the init script that worked fine after the initial install.

I have no idea what else to try. Help please.

 



[#] Mon Oct 17 2016 13:41:06 EDT from alex007 @ Uncensored

Subject: cdb_store(4): Cannot allocate memory

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

After about one hour of running well, citadel shuts down with the message:

cdb_store(4): Cannot allocate memory

Is there a quick solution. Maybe a permission issue?

3 weeks ago I had a big citadel crash and had to recover my citadel with an backup.

 

Cheers

Alex



Go to page: 1 2 3 4 5 [6] 7 8 9 10 ... Last