Hi,

the transferred bytes are just to small, but I cannot find the problem...

output of migration tool looks like this:

Testing a command over the connection...

Remote commands are executing successfully.


Locating the remote 'sendcommand' and Citadel installation...
bash: /usr/local/citadel/sendcommand: Datei oder Verzeichnis nicht gefunden
sendcommand: started (pid=7287) connecting to Citadel server at /var/run/citadel/citadel-admin.socket
200 mail Citadel server ADMIN CONNECTION ready.
NOOP
200 ok
sendcommand: processing ended.

ctdlmigrate will now begin a database migration...
  if the system doesn't start working,
  have a look at the syslog for pending jobs needing to be terminated.
sendcommand: started (pid=1867) connecting to Citadel server at /usr/local/citadel/citadel-admin.socket
200 VG-JAN-CITADEL Citadel server ADMIN CONNECTION ready.
MIGR import
400 sock it to me
sendcommand: usage: sendcommand [-h server_dir] [-w watchdog_timeout]
sendcommand: processing ended.
sendcommand: started (pid=7289) connecting to Citadel server at /var/run/citadel/citadel-admin.socket
200 mail Citadel server ADMIN CONNECTION ready.
MIGR listdirs
100 Don't forget these:
sendcommand: processing ended.
false
rsync -va --rsh='ssh -S /tmp/ctdl.073a.579478fe' root@dgh:/var/lib/citadel/files// /usr/local/citadel/files//
receiving incremental file list
./
Dateien/

sent 18 bytes  received 74 bytes  184.00 bytes/sec
total size is 0  speedup is 0.00
false
rsync -va --rsh='ssh -S /tmp/ctdl.073a.579478fe' root@dgh:/etc/citadel/messages// /usr/local/citadel/messages//
receiving incremental file list
./
aideopt
changepw
dotopt
entermsg
entopt
goodbye
hello
help
mainmenu
newuser
readopt
register
roomaccess
unlisted

sent 382 bytes  received 1,670 bytes  4,104.00 bytes/sec
total size is 5,325  speedup is 2.60
false
rsync -va --rsh='ssh -S /tmp/ctdl.073a.579478fe' root@dgh:/etc/ssl/citadel// /usr/local/citadel/keys/
receiving incremental file list
./
citadel.cer
citadel.csr
citadel.key

sent 101 bytes  received 2,411 bytes  5,024.00 bytes/sec
total size is 2,211  speedup is 0.88
false
false


 *** Citadel migration was unsuccessful. ***

Hey guys! I just installed Citadel for the first time and I set it up using LDAP with Active Directory and I can't login with the admin credentials I provided during setup.. Would I need to reinstall Citadel or is there a way to add an admin user or change the information for the current one?

Which install method did you use? Easy Install or packages from the distro?

Fri Jun 16 2017 08:00:08 PM EDT from ghostwolf1228 @ Uncensored

Hey guys! I just installed Citadel for the first time and I set it up using LDAP with Active Directory and I can't login with the admin credentials I provided during setup.. Would I need to reinstall Citadel or is there a way to add an admin user or change the information for the current one?

I went away for a weekend and found that my database size has quintupled, and my /usr/local/citadel/data folder is now full log.<number> files. Is there a way of clearing out those log files without damaging data, and finding out which account(s) are the culprits in this massive growth?

<singsong> Never mind....

I found the perp (um, friend) and deleted his account. I'll wait for the scheduled purge to run for those log files.

The purge cleaned up the log files, but I'm still seeing a really large database; is there a way to clean it up?

That would be a worthy thing to look into....

Wed Jun 21 2017 01:19:22 PM EDT from IGnatius T Foobar @ Uncensored

Unfortunately you are seeing the natural way that Berkeley DB allocates disk space. The files never shrink; instead, empty space is marked for re-use later on. As a result, the size of the file isn't actually the size of the data; it's more like a "high water mark."

See also: http://www.citadel.org/doku.php/faq:systemadmin:disk_space

If this is highly undesirable for some reason, you can (after taking a backup, of course) shut down Citadel server and run database_cleanup.sh to dump-and-load your database. Keep in mind, however, that database_cleanup.sh requires enough free space on your disk to hold both the dump and the database itself, so if you're doing this because of a disk space crunch, make sure there's an amount of free space on the filesystem containing /tmp that is *at least* double the size of your database.

Hmm. Now I'm seeing there's a function called db->compact()
https://docs.oracle.com/cd/E17275_01/html/api_reference/C/dbcompact.html

Maybe that can be worked into the code, but I don't see a command line utility to do that.