Language:
switch to room list switch to menu My folders
Go to page: First ... 22 23 24 25 [26] 27 28 29 30 ... Last
[#] Sat Jan 02 2021 01:00:48 EST from hamiltra

Subject: Citadel Ldap support with Debian

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

Hello Support,

I'm trying to enable Citadel using ldap on a local debian machine. i have installed and configured ldap and have the development libraries installed. when i run easy install and start Citadel, the logs are showing that the server does not have ldap support. no errors in the citadel build. Please advise.



[#] Sat Jan 02 2021 04:58:49 EST from markus

Subject: Re: Citadel server and Openmediavault on the same debian machine.

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

Well that's true. And in fact the 2020 version of config.guess and config.sub work for me well in that way that they are able to recognize my operationg system. But I'm not the one who can decide that these versions should be included in libcitadel-easyinstall.tar.gz which is in my opinion necessary that citadel easy install could work for me and maybe others that have never operating systems that could not be recognized by the old version of 2006.

Fri Jan 01 2021 19:21:56 EST from Nurb432 Subject: Re: Citadel server and Openmediavault on the same debian machine.

Not an expert here, but what do you have to lose by trying? Worst case it fails again, it wont eat your system or anything.

 

 

Fri Jan 01 2021 19:13:29 EST from markus Subject: Re: Citadel server and Openmediavault on the same debian machine.

 

Could you please check if these newer files from 2020 can replace the once from 2006? Thanks in advance.

 



 



[#] Sat Jan 02 2021 08:23:41 EST from Nurb432

Subject: Re: Citadel server and Openmediavault on the same debian machine.

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

I think there is a dev channel around here, would not hurt to mention it there too.

 

Reason i answered the way i did, is i had a similar issue  ( unrelated software  ) and i just grabbed a copy from something else that did compile on that same machine. I guess going to the 'source' like you did would have made more sense, and i have bookmarked that for next time :) 



[#] Sat Jan 02 2021 09:44:53 EST from hamiltra

Subject: Re: Citadel Ldap support with Debian

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

I checked citserver which is linked against 2.4 version of the OpenLDAP library:

libldap_r-2.4.so.2 => /lib/x86_64-linux-gnu/libldap_r-2.4.so.2 (0x00007efe72a42000)

Sat Jan 02 2021 01:00:48 EST from hamiltra Subject: Citadel Ldap support with Debian

Hello Support,

I'm trying to enable Citadel using ldap on a local debian machine. i have installed and configured ldap and have the development libraries installed. when i run easy install and start Citadel, the logs are showing that the server does not have ldap support. no errors in the citadel build. Please advise.



 



[#] Sat Jan 02 2021 12:46:50 EST from hamiltra

Subject: Re: Citadel Ldap support with Debian

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

this is the error that I'm seeing in /var/log/syslog:

Jan  2 09:43:20 debian citserver[12952]: Your system is configured for LDAP authentication,

Jan  2 09:43:20 debian citserver[12952]: but you are running a server built without OpenLDAP support.

Jan  2 09:43:20 debian systemd[1]: citadel.service: Main process exited, code=exited, status=107/n/a

 
Sat Jan 02 2021 09:44:53 EST from hamiltra Subject: Re: Citadel Ldap support with Debian

I checked citserver which is linked against 2.4 version of the OpenLDAP library:

libldap_r-2.4.so.2 => /lib/x86_64-linux-gnu/libldap_r-2.4.so.2 (0x00007efe72a42000)

Sat Jan 02 2021 01:00:48 EST from hamiltra Subject: Citadel Ldap support with Debian

Hello Support,

I'm trying to enable Citadel using ldap on a local debian machine. i have installed and configured ldap and have the development libraries installed. when i run easy install and start Citadel, the logs are showing that the server does not have ldap support. no errors in the citadel build. Please advise.



 



 



[#] Sun Jan 03 2021 13:14:44 EST from markus

Subject: Re: Citadel server and Openmediavault on the same debian machine.

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

In addition: "config.guess" and "config.sub" should also be replaced in "citadel-easinstall.tar.gz", because the original ones are as old as those in "libcitadel-easyinstall.tar.gz". Much newer are those in "webcit-easyinstall.tar.gz" (from 2014) and they worked well for me. But it is no fault to replace them also by the 2020 version.

Sat Jan 02 2021 04:58:49 EST from markus Subject: Re: Citadel server and Openmediavault on the same debian machine.

Well that's true. And in fact the 2020 version of config.guess and config.sub work for me well in that way that they are able to recognize my operationg system. But I'm not the one who can decide that these versions should be included in libcitadel-easyinstall.tar.gz which is in my opinion necessary that citadel easy install could work for me and maybe others that have never operating systems that could not be recognized by the old version of 2006.

Fri Jan 01 2021 19:21:56 EST from Nurb432 Subject: Re: Citadel server and Openmediavault on the same debian machine.

Not an expert here, but what do you have to lose by trying? Worst case it fails again, it wont eat your system or anything.

 

 

Fri Jan 01 2021 19:13:29 EST from markus Subject: Re: Citadel server and Openmediavault on the same debian machine.

 

Could you please check if these newer files from 2020 can replace the once from 2006? Thanks in advance.

 



 



 



[#] Mon Jan 04 2021 10:36:36 EST from markus

Subject: How to use ctdlmigrate successfully?

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

Hello!

Does anybody have experience with "ctdlmigrate"? I gave it a try (from an older citadel server version 824 to the actual 930).  Starting "ctdlmigrate" it seems to export the database from the older system. But obviously there is a problem doing the import to the new system. When "ctdlmigrate" ends no login to the server was possible. After stopping the server it couldn't be restartet.

Any hints are wellcome!

Markus



[#] Mon Jan 04 2021 11:57:42 EST from markus

Subject: Longer keys to communicate to citadel via https

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

Hello!

I had to generate a new key file (ending .key), a new certificate signing request file (ending .csr) and a new certificate file (ending .cer) to communicate via https to my citadel server. Accoring to the following howto page

https://www.citadel.org/how_to_install_a_certificate_signed_by_a_recognized_certificate_authority.html

the key length should be "1024". 

I think that was true in former days. Nowadays it seems to be too insecure. Browsers like Firefox and MS Internet Explorer refuse connections to websites that use keys with that length. Would you kindly change your howto page (like for example from "1024" to "4096") to help people generate proper keys or do I have the chance to do it?

Regards

Markus



[#] Mon Jan 04 2021 14:17:23 EST from ParanoidDelusions

Subject: Re: How to use ctdlmigrate successfully?

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

If you read back several pages in this room, there was quite a discussion about the different methods of migrating Citadel, including ctdlmigrate. Those discussions might help. 

I was able to successfully migrate a Citadel database from a Pi running Rapsbian to an i5 running Debian. It took me several attempts, I had to jump through a lot of hoops, I couldn't recreate it after I had done it, and I'm not sure what I got right. I know permissions are important - you've got to be root on both systems, and it seemed like directory paths where the files are was important.

It *can* be done. I know that much - but it did not seem remarkably reliable. 

When it is starting, it gives a spinning "/", right? Does that stop? 

sudo tail /var/logs/system.log -f  in a separate terminal window while running the ctdlmigrate - and see if it is throwing up errors. Also, it seems like either running it in a terminal or in a console might have been the key - but I'm not sure which. I know I tried running it in the console logged in as root, I tried running it in a terminal logged in as a regular user, I tried terminal running it sudo, and I tried terminal running it after SU-ing to root. 

I threw everything at the wall - and something stuck. Once. 



Mon Jan 04 2021 10:36:36 EST from markus Subject: How to use ctdlmigrate successfully?

Hello!

Does anybody have experience with "ctdlmigrate"? I gave it a try (from an older citadel server version 824 to the actual 930).  Starting "ctdlmigrate" it seems to export the database from the older system. But obviously there is a problem doing the import to the new system. When "ctdlmigrate" ends no login to the server was possible. After stopping the server it couldn't be restartet.

Any hints are wellcome!

Markus



 



[#] Mon Jan 04 2021 14:21:25 EST from ParanoidDelusions

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

sudo tail /var/log/syslog -f - that is. 

I'm not a Linux expert. 

 



[#] Mon Jan 04 2021 18:46:43 EST from omatnet

Subject: Re: How to use ctdlmigrate successfully?

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

Echoing this latest reply, see my posting and related replies that started on November 12 with the subject: 'Both methods of migration attempts crash within seconds'. ctdlmigrate works well also from an old version to a new version. But in my case, I had a problem - it either crashed midway (too much information) or simply timed out (the old ctdlmigrate did not yet accept the '-w' switch to extend the timeout period). But if this is the issue, you have a work around method, by using IMAP account, transferring safely (albeit slowly) all emails from the old server to the new one. If you read all the postings you will see the answers there.

Mon Jan 04 2021 14:17:23 EST from ParanoidDelusions Subject: Re: How to use ctdlmigrate successfully?

If you read back several pages in this room, there was quite a discussion about the different methods of migrating Citadel, including ctdlmigrate. Those discussions might help. 

I was able to successfully migrate a Citadel database from a Pi running Rapsbian to an i5 running Debian. It took me several attempts, I had to jump through a lot of hoops, I couldn't recreate it after I had done it, and I'm not sure what I got right. I know permissions are important - you've got to be root on both systems, and it seemed like directory paths where the files are was important.

It *can* be done. I know that much - but it did not seem remarkably reliable. 

When it is starting, it gives a spinning "/", right? Does that stop? 

sudo tail /var/logs/system.log -f  in a separate terminal window while running the ctdlmigrate - and see if it is throwing up errors. Also, it seems like either running it in a terminal or in a console might have been the key - but I'm not sure which. I know I tried running it in the console logged in as root, I tried running it in a terminal logged in as a regular user, I tried terminal running it sudo, and I tried terminal running it after SU-ing to root. 

I threw everything at the wall - and something stuck. Once. 



Mon Jan 04 2021 10:36:36 EST from markus Subject: How to use ctdlmigrate successfully?

Hello!

Does anybody have experience with "ctdlmigrate"? I gave it a try (from an older citadel server version 824 to the actual 930).  Starting "ctdlmigrate" it seems to export the database from the older system. But obviously there is a problem doing the import to the new system. When "ctdlmigrate" ends no login to the server was possible. After stopping the server it couldn't be restartet.

Any hints are wellcome!

Markus



 



 



[#] Thu Jan 07 2021 14:45:00 EST from mkuhn

Subject: Citadel log level

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

Hi,

Happy new year!

I'm running Citadel 930 and Webcit 927, installed with easyinstall on my Odroid C2 (updating config.guess in libcitadel.tar and citadel-easyinstall.tar would be great). 

I would like to change the log level for smtp events to let Fail2ban block IPs (i.e. telnet connects on port 25).  What would I need to do to generate that information in either mail.log or syslog?

Regards.

Michael

 



[#] Thu Jan 07 2021 19:01:43 EST from markus

Subject: Re: How to use ctdlmigrate successfully?

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

Well, I have stoppend citadel and webcit, have then deleted all files bellow citadel/data and finally have started citadel and webcit and did citadel setup, but I wasn't lucky in case a) and b), while the cases are:

a) executing ctdlmigrate on destination system 

b) executing sendcommand "MIGR export" > citadel_export.xml on source system and afterwards sendcommand -w <seconds> "MIGR import" < citadel_export.xml on the destination system

In both cases I recognize errors in /var/log/syslog. Rooms were missing as far as I remember and other errors. Does citadel/database need any pretreatment before doing an import? Or do you think source and destination system are too different to migrate going way a) or b)?

If this is the case the only option that I have would be to use a mail user agent to transfer between old and new system. Right?

 

Mon Jan 04 2021 18:46:43 EST from omatnet Subject: Re: How to use ctdlmigrate successfully?

Echoing this latest reply, see my posting and related replies that started on November 12 with the subject: 'Both methods of migration attempts crash within seconds'. ctdlmigrate works well also from an old version to a new version. But in my case, I had a problem - it either crashed midway (too much information) or simply timed out (the old ctdlmigrate did not yet accept the '-w' switch to extend the timeout period). But if this is the issue, you have a work around method, by using IMAP account, transferring safely (albeit slowly) all emails from the old server to the new one. If you read all the postings you will see the answers there.

Mon Jan 04 2021 14:17:23 EST from ParanoidDelusions Subject: Re: How to use ctdlmigrate successfully?

If you read back several pages in this room, there was quite a discussion about the different methods of migrating Citadel, including ctdlmigrate. Those discussions might help. 

I was able to successfully migrate a Citadel database from a Pi running Rapsbian to an i5 running Debian. It took me several attempts, I had to jump through a lot of hoops, I couldn't recreate it after I had done it, and I'm not sure what I got right. I know permissions are important - you've got to be root on both systems, and it seemed like directory paths where the files are was important.

It *can* be done. I know that much - but it did not seem remarkably reliable. 

When it is starting, it gives a spinning "/", right? Does that stop? 

sudo tail /var/logs/system.log -f  in a separate terminal window while running the ctdlmigrate - and see if it is throwing up errors. Also, it seems like either running it in a terminal or in a console might have been the key - but I'm not sure which. I know I tried running it in the console logged in as root, I tried running it in a terminal logged in as a regular user, I tried terminal running it sudo, and I tried terminal running it after SU-ing to root. 

I threw everything at the wall - and something stuck. Once. 



Mon Jan 04 2021 10:36:36 EST from markus Subject: How to use ctdlmigrate successfully?

Hello!

Does anybody have experience with "ctdlmigrate"? I gave it a try (from an older citadel server version 824 to the actual 930).  Starting "ctdlmigrate" it seems to export the database from the older system. But obviously there is a problem doing the import to the new system. When "ctdlmigrate" ends no login to the server was possible. After stopping the server it couldn't be restartet.

Any hints are wellcome!

Markus



 



 



 



[#] Thu Jan 07 2021 19:33:43 EST from markus

Subject: Email copy in sent folder: Why source as destination address?

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

Hello,

when I send an email from test@x to test@y citadel places a copy of this email in the "sent items" folder of test@x. So far so god.

But why does citadel insert test@x as second destination address (second To-address) to this email copy? How can I avoid that?

Regards

Markus



[#] Thu Jan 07 2021 20:30:32 EST from ParanoidDelusions

Subject: Re: How to use ctdlmigrate successfully?

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

This is *exactly* what I was seeing. Error after error, in rooms, in messages... I can't remember the exact error. 

I got it to work exactly ONE time - between a RiP 3b+ and an i5. 

But really, you've that is all you need - is for it to work once. 

I wish I remember what worked, or even what I was doing now. 

Thu Jan 07 2021 19:01:43 EST from markus Subject: Re: How to use ctdlmigrate successfully?

Well, I have stoppend citadel and webcit, have then deleted all files bellow citadel/data and finally have started citadel and webcit and did citadel setup, but I wasn't lucky in case a) and b), while the cases are:

a) executing ctdlmigrate on destination system 

b) executing sendcommand "MIGR export" > citadel_export.xml on source system and afterwards sendcommand -w <seconds> "MIGR import" < citadel_export.xml on the destination system

In both cases I recognize errors in /var/log/syslog. Rooms were missing as far as I remember and other errors. Does citadel/database need any pretreatment before doing an import? Or do you think source and destination system are too different to migrate going way a) or b)?

If this is the case the only option that I have would be to use a mail user agent to transfer between old and new system. Right?

 

Mon Jan 04 2021 18:46:43 EST from omatnet Subject: Re: How to use ctdlmigrate successfully?

Echoing this latest reply, see my posting and related replies that started on November 12 with the subject: 'Both methods of migration attempts crash within seconds'. ctdlmigrate works well also from an old version to a new version. But in my case, I had a problem - it either crashed midway (too much information) or simply timed out (the old ctdlmigrate did not yet accept the '-w' switch to extend the timeout period). But if this is the issue, you have a work around method, by using IMAP account, transferring safely (albeit slowly) all emails from the old server to the new one. If you read all the postings you will see the answers there.

Mon Jan 04 2021 14:17:23 EST from ParanoidDelusions Subject: Re: How to use ctdlmigrate successfully?

If you read back several pages in this room, there was quite a discussion about the different methods of migrating Citadel, including ctdlmigrate. Those discussions might help. 

I was able to successfully migrate a Citadel database from a Pi running Rapsbian to an i5 running Debian. It took me several attempts, I had to jump through a lot of hoops, I couldn't recreate it after I had done it, and I'm not sure what I got right. I know permissions are important - you've got to be root on both systems, and it seemed like directory paths where the files are was important.

It *can* be done. I know that much - but it did not seem remarkably reliable. 

When it is starting, it gives a spinning "/", right? Does that stop? 

sudo tail /var/logs/system.log -f  in a separate terminal window while running the ctdlmigrate - and see if it is throwing up errors. Also, it seems like either running it in a terminal or in a console might have been the key - but I'm not sure which. I know I tried running it in the console logged in as root, I tried running it in a terminal logged in as a regular user, I tried terminal running it sudo, and I tried terminal running it after SU-ing to root. 

I threw everything at the wall - and something stuck. Once. 



Mon Jan 04 2021 10:36:36 EST from markus Subject: How to use ctdlmigrate successfully?

Hello!

Does anybody have experience with "ctdlmigrate"? I gave it a try (from an older citadel server version 824 to the actual 930).  Starting "ctdlmigrate" it seems to export the database from the older system. But obviously there is a problem doing the import to the new system. When "ctdlmigrate" ends no login to the server was possible. After stopping the server it couldn't be restartet.

Any hints are wellcome!

Markus



 



 



 



 



[#] Thu Jan 07 2021 21:13:43 EST from markus

Subject: Re: How to use ctdlmigrate successfully?

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

I wish you could remember, too :-)

Did you migrate between the same version of citadel on RiP 3b+ and on i5 or at least between the same major numbers like 8xx or 9xx?

Was a password set for your admin-account on citadel of RPi 3b+?

Did you copy any files from RPi 3b+ to i5 except the export of the database on RPi 3b+?

Thu Jan 07 2021 20:30:32 EST from ParanoidDelusions Subject: Re: How to use ctdlmigrate successfully?

This is *exactly* what I was seeing. Error after error, in rooms, in messages... I can't remember the exact error. 

I got it to work exactly ONE time - between a RiP 3b+ and an i5. 

But really, you've that is all you need - is for it to work once. 

I wish I remember what worked, or even what I was doing now. 

Thu Jan 07 2021 19:01:43 EST from markus Subject: Re: How to use ctdlmigrate successfully?

Well, I have stoppend citadel and webcit, have then deleted all files bellow citadel/data and finally have started citadel and webcit and did citadel setup, but I wasn't lucky in case a) and b), while the cases are:

a) executing ctdlmigrate on destination system 

b) executing sendcommand "MIGR export" > citadel_export.xml on source system and afterwards sendcommand -w <seconds> "MIGR import" < citadel_export.xml on the destination system

In both cases I recognize errors in /var/log/syslog. Rooms were missing as far as I remember and other errors. Does citadel/database need any pretreatment before doing an import? Or do you think source and destination system are too different to migrate going way a) or b)?

If this is the case the only option that I have would be to use a mail user agent to transfer between old and new system. Right?

 

Mon Jan 04 2021 18:46:43 EST from omatnet Subject: Re: How to use ctdlmigrate successfully?

Echoing this latest reply, see my posting and related replies that started on November 12 with the subject: 'Both methods of migration attempts crash within seconds'. ctdlmigrate works well also from an old version to a new version. But in my case, I had a problem - it either crashed midway (too much information) or simply timed out (the old ctdlmigrate did not yet accept the '-w' switch to extend the timeout period). But if this is the issue, you have a work around method, by using IMAP account, transferring safely (albeit slowly) all emails from the old server to the new one. If you read all the postings you will see the answers there.

Mon Jan 04 2021 14:17:23 EST from ParanoidDelusions Subject: Re: How to use ctdlmigrate successfully?

If you read back several pages in this room, there was quite a discussion about the different methods of migrating Citadel, including ctdlmigrate. Those discussions might help. 

I was able to successfully migrate a Citadel database from a Pi running Rapsbian to an i5 running Debian. It took me several attempts, I had to jump through a lot of hoops, I couldn't recreate it after I had done it, and I'm not sure what I got right. I know permissions are important - you've got to be root on both systems, and it seemed like directory paths where the files are was important.

It *can* be done. I know that much - but it did not seem remarkably reliable. 

When it is starting, it gives a spinning "/", right? Does that stop? 

sudo tail /var/logs/system.log -f  in a separate terminal window while running the ctdlmigrate - and see if it is throwing up errors. Also, it seems like either running it in a terminal or in a console might have been the key - but I'm not sure which. I know I tried running it in the console logged in as root, I tried running it in a terminal logged in as a regular user, I tried terminal running it sudo, and I tried terminal running it after SU-ing to root. 

I threw everything at the wall - and something stuck. Once. 



Mon Jan 04 2021 10:36:36 EST from markus Subject: How to use ctdlmigrate successfully?

Hello!

Does anybody have experience with "ctdlmigrate"? I gave it a try (from an older citadel server version 824 to the actual 930).  Starting "ctdlmigrate" it seems to export the database from the older system. But obviously there is a problem doing the import to the new system. When "ctdlmigrate" ends no login to the server was possible. After stopping the server it couldn't be restartet.

Any hints are wellcome!

Markus



 



 



 



 



 



[#] Thu Jan 07 2021 21:48:56 EST from markus

Subject: Error on citadel restart with webcit

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

Hello?

Recently I used citadel to restart citadel clicking on /adminstration/Shutdown Citadel/Restart Now. Among all the entries I go in /var/log/syslog there are the following ones:

citserver[22211]: extensions: Startup Problems
citserver[22211]: citserver[22211]: msgbase: room hooks returned 1 errors
citserver[22211]: msgbase: room hooks returned 1 errors

First line was also written on console.

What is the reason for that error and how can I avoid it?

Markus



[#] Thu Jan 07 2021 22:14:09 EST from markus

Subject: Cannot add user with underscore in Webcit anymore.

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

Hello,

in former times I was able to add users with underscores using webcit. With Citadel 930 and Webcit 927 this seems not possible anymore. Why is that? Can I change that?

Regard

Markus



[#] Thu Jan 07 2021 22:50:43 EST from markus

Subject: It seems that Citadel does not forward emails to a smart host.

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

Hello again,

In order to test sending emails via citadel my email user agent is connects to citadel via SMTP MSA Serverport 587. Citadel itself is configured to forward each email to a smart host whoes connection parameters are set bellow Administration / Domain names and Internet mail configuration / Smart hosts. But it seems that citadel does not forward incoming emails to that smart host. Assuming connection parameters are correct, what could be the reason?

Markus



[#] Thu Jan 07 2021 23:03:37 EST from markus

Subject: Re: Cannot add user with underscore in Webcit anymore.

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

When I use webcit to add an user whoes user name includes dots then I can afterwards successfully log via webcit using the exactly same user name or a user name that replaces dots by underscores. Does webcit translate underscores to dots or dots to underscores? If so, why? Can I change that behaviour?

Thu Jan 07 2021 22:14:09 EST from markus Subject: Cannot add user with underscore in Webcit anymore.

Hello,

in former times I was able to add users with underscores using webcit. With Citadel 930 and Webcit 927 this seems not possible anymore. Why is that? Can I change that?

Regard

Markus



 



Go to page: First ... 22 23 24 25 [26] 27 28 29 30 ... Last