Language:
switch to room list switch to menu My folders
Go to page: First ... 50 51 52 53 [54] 55 56 57 58 ... Last
[#] Wed Jun 03 2015 17:59:53 EDT from idlisten @ Uncensored

Subject: Re: Easy install update failed

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

Well, I backed up my (apparently corrupted) citadel directories. I tried to stop the citadel process, but it wouldn't stop normally. I had to pkill the processes I could find. I deleted the *.sum files and forced Easy Install to overwrite the installation. I cranked along for a while and came back with "stopping citadel ... failed". Then it continued for a bit and hit "starting citadel ... ok" and that's where it hung. Now, I get "this webpage is not available" when trying to access citadel.

Any thoughts?



[#] Thu Jun 04 2015 11:51:53 EDT from idlisten @ Uncensored

Subject: Re: Easy install update failed

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

If I delete the citadel installation, reinstall it, and copy my database into the new installation, would that restore my messages?

Thanks



[#] Thu Jun 04 2015 11:58:51 EDT from IGnatius T Foobar @ Uncensored

Subject: Re: [Citadel Support] Re: Citadel Update

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

How can I leave this forum ?

http://uncensored.citadel.org/listsub

[#] Thu Jun 04 2015 12:00:53 EDT from IGnatius T Foobar @ Uncensored

Subject: Re: Easy install update failed

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

Unfortunately there is more to a Citadel installation than just what is stored in Berkeley DB. Of paramount importance are the citadel.config and citadel.control files, which are crucial to the system's operation.

Are you able to connect to Citadel using anything other than WebCit? (text client, imap/smtp, etc)

[#] Thu Jun 04 2015 17:46:27 EDT from "Motty Cruz" <motty.cruz@gmail.com> to citadel_support@citadel.org, Motty Cruz <motty.cruz@gmail.com>

Subject: migrating from Courier-imp to Citadel

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

Hello,
I want to start using Citadel for mail and calendar for medium size
company. Currently we have been using Courier-imap. has anybody
experience migrating mail system from Courier-imap to Citadel? if so,
any suggestions?

clients will be using Thunderbird and Outlook.

Thanks for your suggestions.
-Motty

[#] Thu Jun 04 2015 19:12:59 EDT from IGnatius T Foobar @ Uncensored

Subject: Re: migrating from Courier-imp to Citadel

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


There are some great tools, imapsync and imapcopy are two favorites out there.
Definitely go imap-to-imap to move your mail over.

Thanks for choosing Citadel!

[#] Fri Jun 05 2015 10:29:36 EDT from CarlGambolputty @ Uncensored

Subject: Suggestions for migrating Exchange/SBS 2011 to Citadel/Debian Jessie

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

Situation: I'm a sys/net admin for a small business that tired of Exchange. I'm in charge of taking us to the land of milk and cookies (AKA, NOT Small Business Server) to a Linux distro and open source alternative to Exchange. I went with Citadel / Debian for flexibility and stability/uptime. 

I know the Redhat/Fedora/CentOS family of Linux, but I've never played with Debian before now, and while my Windows server/powershell-fu is strong, I'm still stumbling my way through the Exchange environment. I'm at the point where Debian's up on our test server box, I have Citadel loaded up (using LDAP Active Directory as the authentication and a separate user on the AD for the bind), and I've confirmed all Citadel processes are running as they should. I'm happy to stumble through it on my own (see: how I learned Win server in the first place), but I figured I'd reach out to you guys before doing so before I blow 4 hours twisting myself into knots over what should be a simple solution. 

Any suggestions on migrating over? From what I've seen, you need to recreate your user forest in Citadel and then move everything stored on your Exchange database over by imap.



[#] Fri Jun 05 2015 10:56:38 EDT from IGnatius T Foobar @ Uncensored

Subject: Re: Suggestions for migrating Exchange/SBS 2011 to Citadel/Debian Jessie

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

It sounds as if you already have Citadel successfully authenticating against Active Directory, which is usually the hardest part (since we don't have a way to automate it).

You are correct in observing that the users all need to be created. They will be auto-created the first time they log in, but not until then. However, since you're going to use IMAP-to-IMAP copy to get the mailboxes moved over, you need to have all of the usernames/passwords anyway. If you use imapsync or imapcopy, both of those utilities have a "dry run" mode that will log in to both sides and check to make sure everything's in order, but won't (yet) copy any mail. That's a *great* way to get Citadel to auto-create the accounts.

[#] Fri Jun 05 2015 11:15:43 EDT from CarlGambolputty @ Uncensored

Subject: Re: Suggestions for migrating Exchange/SBS 2011 to Citadel/Debian Jessie

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

You ssssssay that I know we're authenticating against AD. I'm about to test that right now by running the imap dry run you mentioned.

Speaking of which, though, that's really sexy. 

I'll message back in a little bit with the results. On a somewhat separate note: we're going to be using the Citadel server with XMPP texting through some flavor of Jabber client (not sure which yet). Using AD auth, as far as for what Citadel is looking for, what format is it? user name only, pre-2003, full netBios, ect?



[#] Fri Jun 05 2015 18:21:58 EDT from CarlGambolputty @ Uncensored

Subject: Re: Suggestions for migrating Exchange/SBS 2011 to Citadel/Debian Jessie

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

Naturally enough I got swamped with other stuff today and never got a chance to. I'll let you know next week how it turns out.



[#] Mon Jun 08 2015 09:06:13 EDT from CarlGambolputty @ Uncensored

Subject: Re: Suggestions for migrating Exchange/SBS 2011 to Citadel/Debian Jessie

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

Naturally enough I got swamped with other stuff today and never got a chance to. I'll let you know next week how it turns out.



[#] Mon Jun 08 2015 18:18:53 EDT from s3cr3to @ Uncensored

Subject: Citadel from squeeze to sid or a rolling release

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

Greetings,

I look for advice about this:

I wonder if using Citadel on Debian Sid is a good choice to migrate 3 citadel servers running on Squeeze.

I wonder if a rolling release like Arch is a good choice for Citadel Server.

Or what is the best distribution recommended to use (years seems like weeks in Debian).

Regards and thanks for the help.



[#] Mon Jun 08 2015 19:06:05 EDT from CarlGambolputty @ Uncensored

Subject: Re: Suggestions for migrating Exchange/SBS 2011 to Citadel/Debian Jessie

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

So, sort of a half-win. I've set up our Debian server to talk to our AD server using samba, partially on general principle, partly so that I could use NIS for the citadel user, partly for better integration with some monitoring software that uses auth based on creds with in the AD run on our Windows server.

But I'm having problems getting citadel to the point where I can run imapcopy to start porting things over. After having several small issues with Citadel I won't go into detail here, I decided to apt-get purge my install and start from scratch, pulling the tar balls from Citadel and compiling everything myself to make sure I wasn't missing any weird conflicts. After doing so, I restarted, ran setup from my install dir and put in the DC information. Despite the fact that my computer can connect to the AD, and that I've confirmed that it's compliant, I can't log-in to the client when I point a browser at the server's IP address. When I try to connect using the AD creds of "place admin" for the full CN name and the password on the AD, the client says it can't see it, and if I try to create it, the client (naturally enough) says that it doesn't use native mode authentication. ise admin is setup to be the admin/aide on first login.

Suggestions?



[#] Wed Jun 10 2015 07:07:36 EDT from IGnatius T Foobar @ Uncensored

Subject: Re: Suggestions for migrating Exchange/SBS 2011 to Citadel/Debian Jessie

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

For LDAP login try using the user's regular login ID instead of their full name (CN).

[#] Wed Jun 10 2015 07:37:39 EDT from markus @ Uncensored

Subject: Again: Citadel cannot be connected after some time

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

Hello again,

 

does anybody have any idea to my problem posted bellow? If more or more precise information is required, l'm glad about any question.

 

Thank you.

 

Markus

 

 

 

 

Sun May 10 2015 18:16:28 EDT from markus @ Uncensored Subject: Citadel cannot be connected after some time

Hello Citadel Support,

 

I'm running Citadel on Debian 7.

My problem is, that Citadel runs for some hours without any obvious problem (mails getting delivered both ways) and then Citadel gets inaccessable by any email client that I use (WebCit, Thunderbird and TypeMail). When I restart citadel, it runs again without problems and all clients can connect, but after a couple of hours the cycle starts over again.

I have already exported and reimported my database in order to be sure it is not a problem with a corrupted database. But that seems not be the case, because the problem was still there.

Does anybody has any idea what's going on? And: Where can I find usefull log files?

 

Thank you very much in advance!

Markus

 

 



 



[#] Wed Jun 10 2015 10:07:47 EDT from CarlGambolputty @ Uncensored

Subject: Re: Suggestions for migrating Exchange/SBS 2011 to Citadel/Debian Jessie

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

I've tried using a variety of different AD/netbios arrangement of the user name. (For all of ise_adm, I've also tried ise adm and iseadm).

DOMAIN/ise_adm

DOMAIN\ise_adm

DOMAIN.LOCAL/ise_adm (undercase too) (undercase and backslash too)

HOST.DOMAIN.LOCAL/ise_adm (undercase and backslash too)

ise_adm

ise admin (CN name)

ise_adm@domain.local

ise_admin@host.domain.local

I've also tried two other users which are on the AD and that I've proven the machine can log in as with all of those combinations.

 

One curious thing I noted: for some reason, the citadel binary (to run the client from shell) was not installed. 'Citadel' or 'sudo Citadel' as root does nothing, and '% locate citadel' returns 'no such job.' But all four webcit processes are running, alongside the two citadel server processes, and the rest of the install seems ok...

(Thanks for all suggestions so far by the way).



[#] Wed Jun 10 2015 11:48:06 EDT from CarlGambolputty @ Uncensored

Subject: Re: Suggestions for migrating Exchange/SBS 2011 to Citadel/Debian Jessie

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

Doi. For some reason, when I compiled my citadel packages I didn't get a citadel-client package. Thought it would be contained in one of the other ones. Herp derp. It's installed now, so that's out of the way.



[#] Thu Jun 11 2015 05:28:41 EDT from dothebart @ Uncensored

Subject: Re: Suggestions for migrating Exchange/SBS 2011 to Citadel/Debian Jessie

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

 

Wed Jun 10 2015 11:48:06 EDT from CarlGambolputty @ Uncensored Subject: Re: Suggestions for migrating Exchange/SBS 2011 to Citadel/Debian Jessie

Doi. For some reason, when I compiled my citadel packages I didn't get a citadel-client package. Thought it would be contained in one of the other ones. Herp derp. It's installed now, so that's out of the way.



Oh, it was moved out of the citserver package; I need to update the documentation.



[#] Thu Jun 11 2015 12:37:05 EDT from CarlGambolputty @ Uncensored

Subject: Re: Suggestions for migrating Exchange/SBS 2011 to Citadel/Debian Jessie

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

@ dothebart: <meanie_face>

OK. I think I have it narrowed down some. I've been working on this issue for the past few days as time allowed.

The problem here is Webcit, or some dependency of it that it uses, failing to communicate with the AD, with the faliure on the end of the Citadel install, not the Debian server or the AD DC. As mentioned, I connected to the AD with Samba, and can pull tickets, get results from wbinfo, and can log onto the system with home folders using AD users. The only hiccup is that CTDBD, which is a file-sharing component of Samba, is unhappy living on my Jessie install, but that's due to my nodes/private IPs in /etc/ctdb/nodes not being declared (because I don't care), so it's not related AFAIK. 

I think the fault originates in citadel-server, since trying to use the Citadel client from the install box through the shell runs into the same issue; it pretends that users can't be seen. The fact that Webcit doesn't log me on is because the citadel server isn't feeding it information from the AD, because Citadel can't find it.

Backing this up are entries I'm finding in /var/log/syslog when I attempt to log in to the web portal; after webcit notes the log-in IP and matches the session with a cookie, it passes stuff over to the citserver process, which then barfs this up:

 

Jun 11 11:46:35 KRILLAN citserver[812]: [84][(not logged in)(0)] USER ise_adm

Jun 11 11:46:35 KRILLAN citserver[812]: LDAP bind DN: cn=queries,cn=users,dc=domain,dc=local

Jun 11 11:46:35 KRILLAN citserver[812]: LDAP: Cannot bind: Can't contact LDAP server (-1)

Jun 11 11:46:35 KRILLAN webcit[2492]: HTTP: 200 [0.001153] POST /ajax_login_username_password

 

(I'm not sure if citserver would write a different error string if it COULD find the server, but COULDN'T get a query return on the DN bind account.)
 
In addition, when I try running webcit as a direct command at the shell, rather than from /etc/init.d/webcit, I get a bunch of returns in console that look like this (where 192.168.1.2 represents the IP of our domain box):
 
nss_ldap: could not connect to any LDAP server as CN=ise admin,DC=integrated,DC=local - Can't contact LDAP server
nss_ldap: failed to bind to LDAP server ldapi://192.168.1.2/: Can't contact LDAP server
nss_ldap: reconnecting to LDAP server...
 
And so on and so forth. Note that this is the only time I get this message, in console or in logs. I am, by the way, using option '3' (non-standard LDAP) for authentication, though I tried it with option 2 (RFC-compliant LDAP) previously with the same result. I've also verified the bind account's creds on the Windows server; I even made an additional user (info above) with values matching the online guide for funsies, pointed to it with a fresh install, and had the same results.
 
The only other stand-out data point I've found is a WARNING in syslog when I restart the webcit service:
 
Jun 11 11:45:55 KRILLAN webcit[2492]: WARNING: getpwuid(65534): Success#012Group IDs will be incorrect.
Jun 11 11:45:55 KRILLAN webcit[2492]: Changing uid to 65534
Jun 11 11:45:55 KRILLAN webcit[2495]: Listening on socket 7
Jun 11 11:45:55 KRILLAN webcit[2495]: Requesting cipher list: DEFAULT
Jun 11 11:45:55 KRILLAN webcit[2495]: WARNING: getpwuid(65534): File exists#012Group IDs will be incorrect.
Jun 11 11:45:55 KRILLAN webcit[2495]: Changing uid to 65534
 
I've found a reference to this error on https://www.mail-archive.com/room_citadel_development@uncensored.citadel.org/msg09459.html, which I'm going to do when I have a moment, though I'm not sure if this is a relevant issue.
 
 
 
If anyone is interested in the syslog, let me know and I'll email it over (since this forums doesn't seem to support code boxes or post attachments). Again, I'd love suggestions on how to proceed since I'm at a bit of a brick wall, but past anything else I'd also be interested in suggestions on an optimal distro of linux to run this on, as on Saturday, if I'm still stuck I'm going to go nuclear option on this and start from scratch with something else than Debian Jessie.


[#] Thu Jun 11 2015 13:16:24 EDT from CarlGambolputty @ Uncensored

Subject: Re: Suggestions for migrating Exchange/SBS 2011 to Citadel/Debian Jessie

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

@ dothebart: <meanie_face>

OK. I think I have it narrowed down some. I've been working on this issue for the past few days as time allowed.

The problem here is Webcit, or some dependency of it that it uses, failing to communicate with the AD, with the faliure on the end of the Citadel install, not the Debian server or the AD DC. As mentioned, I connected to the AD with Samba, and can pull tickets, get results from wbinfo, and can log onto the system with home folders using AD users. The only hiccup is that CTDBD, which is a file-sharing component of Samba, is unhappy living on my Jessie install, but that's due to my nodes/private IPs in /etc/ctdb/nodes not being declared (because I don't care), so it's not related AFAIK. 

I think the fault originates in citadel-server, since trying to use the Citadel client from the install box through the shell runs into the same issue; it pretends that users can't be seen. The fact that Webcit doesn't log me on is because the citadel server isn't feeding it information from the AD, because Citadel can't find it.

Backing this up are entries I'm finding in /var/log/syslog when I attempt to log in to the web portal; after webcit notes the log-in IP and matches the session with a cookie, it passes stuff over to the citserver process, which then barfs this up:

 

Jun 11 11:46:35 KRILLAN citserver[812]: [84][(not logged in)(0)] USER ise_adm

Jun 11 11:46:35 KRILLAN citserver[812]: LDAP bind DN: cn=queries,cn=users,dc=domain,dc=local

Jun 11 11:46:35 KRILLAN citserver[812]: LDAP: Cannot bind: Can't contact LDAP server (-1)

Jun 11 11:46:35 KRILLAN webcit[2492]: HTTP: 200 [0.001153] POST /ajax_login_username_password

 

(I'm not sure if citserver would write a different error string if it COULD find the server, but COULDN'T get a query return on the DN bind account.)
 
In addition, when I try running webcit as a direct command at the shell, rather than from /etc/init.d/webcit, I get a bunch of returns in console that look like this (where 192.168.1.2 represents the IP of our domain box):
 
nss_ldap: could not connect to any LDAP server as CN=ise admin,DC=integrated,DC=local - Can't contact LDAP server
nss_ldap: failed to bind to LDAP server ldapi://192.168.1.2/: Can't contact LDAP server
nss_ldap: reconnecting to LDAP server...
 
And so on and so forth. Note that this is the only time I get this message, in console or in logs. I am, by the way, using option '3' (non-standard LDAP) for authentication, though I tried it with option 2 (RFC-compliant LDAP) previously with the same result. I've also verified the bind account's creds on the Windows server; I even made an additional user (info above) with values matching the online guide for funsies, pointed to it with a fresh install, and had the same results.
 
The only other stand-out data point I've found is a WARNING in syslog when I restart the webcit service:
 
Jun 11 11:45:55 KRILLAN webcit[2492]: WARNING: getpwuid(65534): Success#012Group IDs will be incorrect.
Jun 11 11:45:55 KRILLAN webcit[2492]: Changing uid to 65534
Jun 11 11:45:55 KRILLAN webcit[2495]: Listening on socket 7
Jun 11 11:45:55 KRILLAN webcit[2495]: Requesting cipher list: DEFAULT
Jun 11 11:45:55 KRILLAN webcit[2495]: WARNING: getpwuid(65534): File exists#012Group IDs will be incorrect.
Jun 11 11:45:55 KRILLAN webcit[2495]: Changing uid to 65534
 
I've found a reference to this error on https://www.mail-archive.com/room_citadel_development@uncensored.citadel.org/msg09459.html, which I'm going to do when I have a moment, though I'm not sure if this is a relevant issue.
 
 
 
If anyone is interested in the syslog, let me know and I'll email it over (since this forums doesn't seem to support code boxes or post attachments). Again, I'd love suggestions on how to proceed since I'm at a bit of a brick wall, but past anything else I'd also be interested in suggestions on an optimal distro of linux to run this on, as on Saturday, if I'm still stuck I'm going to go nuclear option on this and start from scratch with something else than Debian Jessie.


Go to page: First ... 50 51 52 53 [54] 55 56 57 58 ... Last