.... or directory /usr/local/citadel/citadel-admin.socket

When I run it from /etc/init.d/, citserver does show up in the list of process, but setup still fails to connect to it.

So, let me write what has happened so far. Starting around 6PM last night, all of our inboxes received multiple copies of all emails sent. So, we rebooted the email server, but I noticed citserver running 100% on a CPU. Outbound emails were not sending. In order to send them, I had to restart citadel from init.d, and they would send out initially. But any further emails would get stuck in queue.

So, I decided to screw stuff up more. I was running ubuntu 11 wheezy. I decided to run the easy install. In the middle of this install, it prompted me intially to use root to run citadel, but in the description, it said to use a user citadel, which I then typed in and continued. During the portion that says "configured citadel" It got to 95%, with setup and citserver using 100%. After 15 minutes, no changes, so impatiently, I killed the processes.

Tried to run easy install, and started getting "Setup could not connect to...yadda yadda yadda".

Then, figuring, "Hey, I'm 2 distros behind". I upgraded to Ubuntu 12.0.4 and then on to Ubuntu 14.0.4.5

Trying to run easy install gets the same message

How bad did I screw this up?

Running is manually segfault dumps
root@mail:/usr/local/citadel# ./citserver
citserver[26712]:
citserver[26712]:
citserver[26712]: *** Citadel server engine ***
citserver[26712]: Version 902 (build 0e679ba) ***
citserver[26712]: Copyright (C) 1987-2016 by the Citadel development team.
citserver[26712]: This program is distributed under the terms of the GNU General Public License.
citserver[26712]:
citserver[26712]: Called as: ./citserver
citserver[26712]: libcitadel(unnumbered)
citserver[26712]: master_startup() started
citserver[26712]: Checking directory access
citserver[26712]: Opening databases
citserver[26712]: bdb(): open_databases() starting
citserver[26712]: Compiled db: Berkeley DB 5.1.29: (October 25, 2011)
citserver[26712]:   Linked db: Berkeley DB 5.1.29: (October 25, 2011)
citserver[26712]: Linked zlib: 1.2.8
citserver[26712]: bdb(): Setting up DB environment
citserver[26712]: dbenv->open(dbenv, /usr/local/citadel/data/, 19091, 0)
citserver[26712]: DB: Finding last valid log LSN: file: 11122 offset 9081406
citserver[26712]: DB: file cdb.08 has LSN 11122/9172527, past end of log at 11122/9081406
Segmentation fault (core dumped)

Disregard. Do to time crunches, and most of the small office using pop. we decided to just reinstall ubuntu and citadel from scratch

Thu Sep 08 2016 13:53:54 EDT from friday1970 @ Uncensored Subject: Setup could not connect to a running Citadel server.: No such file

.... or directory /usr/local/citadel/citadel-admin.socket

When I run it from /etc/init.d/, citserver does show up in the list of process, but setup still fails to connect to it.

So, let me write what has happened so far. Starting around 6PM last night, all of our inboxes received multiple copies of all emails sent. So, we rebooted the email server, but I noticed citserver running 100% on a CPU. Outbound emails were not sending. In order to send them, I had to restart citadel from init.d, and they would send out initially. But any further emails would get stuck in queue.

So, I decided to screw stuff up more. I was running ubuntu 11 wheezy. I decided to run the easy install. In the middle of this install, it prompted me intially to use root to run citadel, but in the description, it said to use a user citadel, which I then typed in and continued. During the portion that says "configured citadel" It got to 95%, with setup and citserver using 100%. After 15 minutes, no changes, so impatiently, I killed the processes.

Tried to run easy install, and started getting "Setup could not connect to...yadda yadda yadda".

Then, figuring, "Hey, I'm 2 distros behind". I upgraded to Ubuntu 12.0.4 and then on to Ubuntu 14.0.4.5

Trying to run easy install gets the same message

How bad did I screw this up?

 

Running is manually segfault dumps
root@mail:/usr/local/citadel# ./citserver
citserver[26712]:
citserver[26712]:
citserver[26712]: *** Citadel server engine ***
citserver[26712]: Version 902 (build 0e679ba) ***
citserver[26712]: Copyright (C) 1987-2016 by the Citadel development team.
citserver[26712]: This program is distributed under the terms of the GNU General Public License.
citserver[26712]:
citserver[26712]: Called as: ./citserver
citserver[26712]: libcitadel(unnumbered)
citserver[26712]: master_startup() started
citserver[26712]: Checking directory access
citserver[26712]: Opening databases
citserver[26712]: bdb(): open_databases() starting
citserver[26712]: Compiled db: Berkeley DB 5.1.29: (October 25, 2011)
citserver[26712]:   Linked db: Berkeley DB 5.1.29: (October 25, 2011)
citserver[26712]: Linked zlib: 1.2.8
citserver[26712]: bdb(): Setting up DB environment
citserver[26712]: dbenv->open(dbenv, /usr/local/citadel/data/, 19091, 0)
citserver[26712]: DB: Finding last valid log LSN: file: 11122 offset 9081406
citserver[26712]: DB: file cdb.08 has LSN 11122/9172527, past end of log at 11122/9081406
Segmentation fault (core dumped)

Hi, I am using the rolling release installed with easyinstall (refreshed recently) and on the 7th Sept I experienced some kind of problem with the database: after a reboot, citadel failed to start.

The error I can see in the logs is as follows (I am attaching the last I have in the logs):

Sep 11 16:12:46 aa1 citserver[30929]: 

Sep 11 16:12:46 aa1 citserver[30929]: 

Sep 11 16:12:46 aa1 citserver[30929]: *** Citadel server engine ***

Sep 11 16:12:46 aa1 citserver[30929]: Version 902 (build 0e679ba) ***

Sep 11 16:12:46 aa1 citserver[30929]: Copyright (C) 1987-2016 by the Citadel development team.

Sep 11 16:12:46 aa1 citserver[30929]: This program is distributed under the terms of the GNU General Public License.

Sep 11 16:12:46 aa1 citserver[30929]: 

Sep 11 16:12:46 aa1 citserver[30929]: Called as: /usr/local/citadel/citserver

Sep 11 16:12:46 aa1 citserver[30929]: libcitadel(unnumbered)

Sep 11 16:12:46 aa1 citserver[30929]: master_startup() started

Sep 11 16:12:46 aa1 citserver[30929]: Checking directory access

Sep 11 16:12:46 aa1 citserver[30929]: Opening databases

Sep 11 16:12:46 aa1 citserver[30929]: bdb(): open_databases() starting

Sep 11 16:12:46 aa1 citserver[30929]: Compiled db: Berkeley DB 5.1.29: (October 25, 2011)

Sep 11 16:12:46 aa1 citserver[30929]:   Linked db: Berkeley DB 5.1.29: (October 25, 2011)

Sep 11 16:12:46 aa1 citserver[30929]: Linked zlib: 1.2.8

Sep 11 16:12:46 aa1 citserver[30929]: bdb(): Setting up DB environment

Sep 11 16:12:46 aa1 citserver[30929]: dbenv->open(dbenv, /usr/local/citadel/data/, 19091, 0)

Sep 11 16:12:46 aa1 citserver[30929]: DB: Finding last valid log LSN: file: 1 offset 23741

Sep 11 16:12:46 aa1 citserver[30929]: DB: Recovery starting from [1][18641]

Sep 11 16:12:46 aa1 citserver[30929]: DB: Recovery complete at Sun Sep 11 16:12:46 2016

Sep 11 16:12:46 aa1 citserver[30929]: DB: Maximum transaction ID 80000041 Recovery checkpoint [1][24903]

Sep 11 16:12:46 aa1 citserver[30929]: Starting up DB

Sep 11 16:12:46 aa1 citserver[30929]: Initializing configuration system

Sep 11 16:12:46 aa1 citserver[30929]: configuration setting c_default_cal_zone is empty, but must not - check your config!

Sep 11 16:12:46 aa1 citserver[30929]: Checking floor reference counts

Sep 11 16:12:47 aa1 citserver[30929]: Floor 0: 152 rooms

Sep 11 16:12:47 aa1 citserver[30929]: Floor 1: 0 rooms

Sep 11 16:12:47 aa1 citserver[30929]: Floor 2: 0 rooms

Sep 11 16:12:47 aa1 citserver[30929]: Floor 3: 0 rooms

Sep 11 16:12:47 aa1 citserver[30929]: Floor 4: 0 rooms

Sep 11 16:12:47 aa1 citserver[30929]: Floor 5: 0 rooms

Sep 11 16:12:47 aa1 citserver[30929]: Floor 6: 0 rooms

Sep 11 16:12:47 aa1 citserver[30929]: Floor 7: 0 rooms

Sep 11 16:12:47 aa1 citserver[30929]: Floor 8: 0 rooms

Sep 11 16:12:47 aa1 citserver[30929]: Floor 9: 0 rooms

Sep 11 16:12:47 aa1 citserver[30929]: Floor 10: 0 rooms

Sep 11 16:12:47 aa1 citserver[30929]: Floor 11: 0 rooms

Sep 11 16:12:47 aa1 citserver[30929]: Floor 12: 0 rooms

Sep 11 16:12:47 aa1 citserver[30929]: Floor 13: 0 rooms

Sep 11 16:12:47 aa1 citserver[30929]: Floor 14: 0 rooms

Sep 11 16:12:47 aa1 citserver[30929]: Floor 15: 0 rooms

Sep 11 16:12:47 aa1 citserver[30929]: Creating base rooms (if necessary)

Sep 11 16:12:47 aa1 citserver[30929]: Seeding the pseudo-random number generator...

Sep 11 16:12:47 aa1 citserver[30929]: master_startup() finished

Sep 11 16:12:47 aa1 citserver[30929]: Sanity checking the recorded highest message, user, and room numbers

Sep 11 16:12:47 aa1 citserver[30929]: bdb(): cursor still in progress on cdb 02: attempt to write during r/o cursor

Sep 11 16:12:47 aa1 citserver[30929]: citserver is stopping in order to prevent data loss. uid=0 gid=0 euid=0 egid=0

The line that reads "configuration setting c_default_cal_zone is empty, but must not - check your config!" started to appear after I tried to recover using the database_cleanup.sh tool.

I must say I tried both /usr/local/ctdlsupport/bin/db_recover -c and then database_cleanup.sh, without any apparent success.

Currently, I am running the previous night backup but it would be helpful if I could reach the messages received/sent which had not been backed up by the time the problem occurred.

Just in case, I do not really need to repair the database, extracting the text would work for me.

Is there any way to access the database using db tools,etc. by any chance ?

Thanks for your help

I recently changed the IP address under global settings via the web interface to the local IP address of the machine. It used to be 0.0.0.0. After doing this, i now receive the message "This program was unable to connect or stay connected to the Citadel server. Please report this problem to your system administrator.". How do I change the IP address back to 0.0.0.0, and is what I changed even the issue? I am still able to use my imap client to send and receive emails fine.

Thank you

 to show you what i mean see the telnet connection from the

graczyk@graczyk-Satellite-A215:~$ telnet 192.168.2.150 25
Trying 192.168.2.150...
Connected to 192.168.2.150.
Escape character is '^]'.
220 abc.def.com ESMTP Citadel server ready.
ehlo localhost
250-Hello localhost (192.168.2.150 [192.168.2.150])
250-HELP
250-SIZE 20971520
250-AUTH LOGIN PLAIN
250-AUTH=LOGIN PLAIN
250 8BITMIME

this is done on the local machine. 192.168.2.150 is the physical machines address on the LAN. I believe this should be either 127.0.0.1 or 0.0.0.0. when I attempt

---> telnet 127.0.0.1 25

I cannot connect.

As mentioned before, the mail server is sending and receiving fine and i can use it through an IMAP client, however I cannot the webcit interface from a browser anymore.

Thank you. I was actually able to run ./setup instead since I could not get ./ASG to run. Running ./setup worked and I changed the listen IP to 0.0.0.0 and the problem is solved. thanks again for your help.

Mon Sep 12 2016 10:42:43 EDT from romeske @ Uncensored Subject: need to change webcit address

I recently changed the IP address under global settings via the web interface to the local IP address of the machine. It used to be 0.0.0.0. After doing this, i now receive the message "This program was unable to connect or stay connected to the Citadel server. Please report this problem to your system administrator.". How do I change the IP address back to 0.0.0.0, and is what I changed even the issue? I am still able to use my imap client to send and receive emails fine.

 

Thank you

I'm on the packaged version on a ubuntu 16-04 LTS machine and have the same or similar issue.
For me it seems that everytime I make changes under Administration/Site Wide Configuration Webcit looses the port number 504 an tries to connect on port 0 after a restart.
However running /usr/lib/citadel-server/setup an changing the port back to 504 solves the issue.

Is this a bug or a missing configuration entry somewhere ?

Thanks for any hints

I want to migrate from a 32bit CentOS system (citadel-8.24-7.2) to a newer 64bit system (citadel-8.24-10.2). I'm going to use ctdlmigrate.

Can I specify where ctdlmigrate puts the exported xml file?

There is not enough diskspace on the machine that has the current databases to have exported xml of the same size. I was thinking of an nfs mount to a drive with plenty of space to accomodate the export.

Thanks.

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?