Language:
switch to room list switch to menu My folders
Go to page: [1] 2 3 4 5 ... Last
↑↑↑ Old messages ↑↑↑            ↓↓↓ New messages ↓↓↓
[#] Fri Jul 31 2015 04:37:23 EDT from zigor @ Uncensored

Subject: Re: [Citadel Support] Citadel Installation

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

I understand, that something is misconfigured. I just wonder what and where.

Thu Jul 30 2015 18:07:46 EDT from "Panagiotis Palias" <panagos81@gmail.com> Subject: Re: [Citadel Support] Citadel Installation

Your webcit only runs on 443  https port. I see you run apache2; my guess is that if you stop apache and restart webcit, it will bind in port 80, which will mean something is misconfigured.



[#] Fri Jul 31 2015 04:42:02 EDT from "Panagiotis Palias" <panagos81@gmail.com> to citadel_support@citadel.org

Subject: Re: [Citadel Support] Citadel Installation

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

Try again to reconfigure the server. Use * for network address to include all ipv4 and ipv6. Make sure you select internal web server and not apache/nginx.

Στις 31 Ιουλ 2015 11:38, ο χρήστης "zigor" <zigor@uncensored.citadel.org> έγραψε:

I understand, that something is misconfigured. I just wonder what and where.

Thu Jul 30 2015 18:07:46 EDT from "Panagiotis Palias" <panagos81@gmail.com> Subject: Re: [Citadel Support] Citadel Installation

Your webcit only runs on 443  https port. I see you run apache2; my guess is that if you stop apache and restart webcit, it will bind in port 80, which will mean something is misconfigured.



[#] Fri Jul 31 2015 04:55:06 EDT from zigor @ Uncensored

Subject: Re: [Citadel Support] Citadel Installation

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

OK, so the /etc/default/webcit now is configured to run webcit on http-port 80.

Apache2 is configured to listen on *:80 for requests to ctdl.mydomain.tld and redirect them to http://127.0.0.1:2000/ via ProxyPass.

Is this correct? I just want apache and citadel to work side by side.

Also, in syslog I get the message that GET is an illegal operation for ManageSieve.

 

Fri Jul 31 2015 04:37:23 EDT from zigor @ Uncensored Subject: Re: [Citadel Support] Citadel Installation

I understand, that something is misconfigured. I just wonder what and where.

Thu Jul 30 2015 18:07:46 EDT from "Panagiotis Palias" <panagos81@gmail.com> Subject: Re: [Citadel Support] Citadel Installation

Your webcit only runs on 443  https port. I see you run apache2; my guess is that if you stop apache and restart webcit, it will bind in port 80, which will mean something is misconfigured.



 



[#] Fri Jul 31 2015 05:06:29 EDT from zigor @ Uncensored

Subject: Re: [Citadel Support] Citadel Installation

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

I tried reconfiguring via /usr/lib/citadel-server/setup. It didn't ask me about apache2/ngnix/internal at all. I set * for adresses to listen on. In the end I got a long error message about not being able to bind a lot of ports. The important part seems to be this:

Can't create a listening socket: Address family not supported by protocol;

Fri Jul 31 2015 04:42:02 EDT from "Panagiotis Palias" <panagos81@gmail.com> Subject: Re: [Citadel Support] Citadel Installation

Try again to reconfigure the server. Use * for network address to include all ipv4 and ipv6. Make sure you select internal web server and not apache/nginx.

Στις 31 Ιουλ 2015 11:38, ο χρήστης "zigor" <zigor@uncensored.citadel.org> έγραψε:

I understand, that something is misconfigured. I just wonder what and where.

Thu Jul 30 2015 18:07:46 EDT from "Panagiotis Palias" <panagos81@gmail.com> Subject: Re: [Citadel Support] Citadel Installation

Your webcit only runs on 443  https port. I see you run apache2; my guess is that if you stop apache and restart webcit, it will bind in port 80, which will mean something is misconfigured.



 



[#] Fri Jul 31 2015 05:25:18 EDT from "Panagiotis Palias" <panagos81@gmail.com> to citadel_support@citadel.org

Subject: Re: [Citadel Support] Citadel Installation

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

You need to post the logs from the commands you give, otherwise we can just guess. Did you run the script as root? You need to read on citadel's site how to configure webcit to run along with apache. In a nutshell you need to run webcit on port 2000 and configure apache to redirect requests to that port.

Στις 31 Ιουλ 2015 12:07, ο χρήστης "zigor" <zigor@uncensored.citadel.org> έγραψε:

I tried reconfiguring via /usr/lib/citadel-server/setup. It didn't ask me about apache2/ngnix/internal at all. I set * for adresses to listen on. In the end I got a long error message about not being able to bind a lot of ports. The important part seems to be this:

Can't create a listening socket: Address family not supported by protocol;

Fri Jul 31 2015 04:42:02 EDT from "Panagiotis Palias" <panagos81@gmail.com> Subject: Re: [Citadel Support] Citadel Installation

Try again to reconfigure the server. Use * for network address to include all ipv4 and ipv6. Make sure you select internal web server and not apache/nginx.

Στις 31 Ιουλ 2015 11:38, ο χρήστης "zigor" <zigor@uncensored.citadel.org> έγραψε:

I understand, that something is misconfigured. I just wonder what and where.

Thu Jul 30 2015 18:07:46 EDT from "Panagiotis Palias" <panagos81@gmail.com> Subject: Re: [Citadel Support] Citadel Installation

Your webcit only runs on 443  https port. I see you run apache2; my guess is that if you stop apache and restart webcit, it will bind in port 80, which will mean something is misconfigured.



 



[#] Fri Jul 31 2015 11:24:06 EDT from s3cr3to @ Uncensored

Subject: Re: [Citadel Support] Citadel Installation

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

On one server I have this un /etc/default/webcit (hope it works for you):

export WEBCIT_APACHEFLAG=" -f "
export WEBCIT_LISTEN_IP=127.0.0.1
export WEBCIT_HTTP_PORT=##chooseYours##
export WEBCIT_HTTPS_PORT=443
export WEBCIT_LANG=UNLIMITED
export WEBCIT_CITADEL_PORT=##(leave default or not)##
export WEBCIT_CITADEL_IP=127.0.0.1

With this I can access webcit using nginx as proxy (I believe works for apache too) and I can access from our local and external network (but I only allow one client from outside... me using https)

Of course I need to tweak some configurations on nginx to allow the proxy and limit outside access.

If you search this forum with the keywork "nginx" or "proxy" I think you'll found something helpful.

Regards

 

Fri Jul 31 2015 05:06:29 AM EDT from zigor @ Uncensored Subject: Re: [Citadel Support] Citadel Installation

I tried reconfiguring via /usr/lib/citadel-server/setup. It didn't ask me about apache2/ngnix/internal at all. I set * for adresses to listen on. In the end I got a long error message about not being able to bind a lot of ports. The important part seems to be this:

Can't create a listening socket: Address family not supported by protocol;

Fri Jul 31 2015 04:42:02 EDT from "Panagiotis Palias" <panagos81@gmail.com> Subject: Re: [Citadel Support] Citadel Installation

Try again to reconfigure the server. Use * for network address to include all ipv4 and ipv6. Make sure you select internal web server and not apache/nginx.

Στις 31 Ιουλ 2015 11:38, ο χρήστης "zigor" <zigor@uncensored.citadel.org> έγραψε:

I understand, that something is misconfigured. I just wonder what and where.

Thu Jul 30 2015 18:07:46 EDT from "Panagiotis Palias" <panagos81@gmail.com> Subject: Re: [Citadel Support] Citadel Installation

Your webcit only runs on 443  https port. I see you run apache2; my guess is that if you stop apache and restart webcit, it will bind in port 80, which will mean something is misconfigured.



 



 



[#] Tue Aug 11 2015 07:50:28 EDT from ghutchi1 @ Uncensored

Subject: No admin user after install

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

Hi, I am new to Citadel and have just installed it on a RPI2 running ubuntu 14.40.

It installed without issue, but when I try accessing the admin account it logs in as a level 4 network user, not an admin user.

I followed the install doco, and a few posts as well, but non of the methods of setting up the admin user have worked.

I have tried this install  times now with no success, this last time I ran citadel from the command line and entered the admin username and password.Any assistance would be appreciated.

Thanks

Geoff.



[#] Tue Aug 11 2015 07:55:56 EDT from ghutchi1 @ Uncensored

Subject: Re: No admin user after install

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

 

Tue Aug 11 2015 07:50:28 EDT from ghutchi1 @ Uncensored Subject: No admin user after install

Hi, I am new to Citadel and have just installed it on a RPI2 running ubuntu 14.40.

It installed without issue, but when I try accessing the admin account it logs in as a level 4 network user, not an admin user.

I followed the install doco, and a few posts as well, but non of the methods of setting up the admin user have worked.

I have tried this install  times now with no success, this last time I ran citadel from the command line and entered the admin username and password.Any assistance would be appreciated.

Thanks

Geoff.



Please disregard this, I found another post that pointed me in the right direction and the admin user now works.



[#] Wed Aug 12 2015 09:59:10 EDT from "tony hughes" <tony.john.hughes@gmail.com> to citadel_support@citadel.org

Subject: changing the base URL

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

Hey,

Can't find it written anywhere but how can i change the base url from / thinking of changing to /mail for a reverse proxy.


Regards,

Tony.



[#] Fri Aug 14 2015 14:26:16 EDT from Nuketroop @ Uncensored

Subject: Imap speed

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

Hello,

Just setup a Linode server with Citadel on an 14.04LTS Ubuntu box and all is working.  Send/rec mail, etc.  Have spamassassin loaded, RBL etc.  Just hoping to clean a bit more speed from IMAP.  I saw the post about changing the header, and tried to find the documentation on it, but was unable to. 

Anyone know where to put that entry for header_cache = yes 

Thank much in advance!  Yes, I'm new to Citadel and out of date with Linux, but appreciate any and all help.

 

-Tom



[#] Sat Aug 15 2015 11:39:34 EDT from Juan C. Cigala (jcigala) @ Uncensored

Subject: Fw: Re: How to compress the database?

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

 

--- forwarded message ---
Thu Sep 04 2014 03:35:54 EDT from dothebart @ Uncensored Subject: Re: How to compress the database?

 

Wed Sep 03 2014 17:31:34 EDT from platonov @ Uncensored Subject: Re: How to compress the database?

 

Wed Sep 03 2014 14:41:09 EDT from IGnatius T Foobar @ Uncensored Subject: Re: How to compress the database?

cdb.* files (as with any Berkeley DB files) never shrink. When you delete data from them, space within the files is marked as unused, and can be re-used for new data.

The effect of this is that when you delete data from Citadel (or anything that uses Berkeley DB), the files will not shrink, but new data will not make them grow any more.

Thanx IGnatius,

That's what I suspected. I'd like to try to dump the database to XML in that case and then restore it from the, if that is the right idea in your opinion.

I saw a couple of times lots of log files that filled the disk completely. So, I have removed all of them but the last one in sequence.

Not sure what it was, but it looked like some attack or something like that. I think I did already have the automatic removal of log flags set at that time.

If you happen to have the link to the instructions on how to dump/restore the database to XML, would be appreciated. I am really swamped here with all sorts of nasty lil things related to running out of disk space and upgrade of BTSync to 1.4.72.




you can use

sendcommand MIGR > /tmp/dump.xml

Please note that in git master are some serious performance boosts to the dump/import facility by switching i.e. the base64 de/encoder; you may consider using this.

One problem seems to still be there in the smtp auth; so you may want to revert the upgrade after your dump/import.



 



[#] Sat Aug 15 2015 14:13:14 EDT from jcigala @ Uncensored

Subject: Re: MIGR IMPORT not importing my messages

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

Hi all,

I have the same issue. ctdlmigrate does not work for me either.

With the new version I can´t make the migration happen.

With the previous version, I succeeded in making the migration several times in several different servers.

I upgraded the target server as the source, but it does not work -maybe got worse.

The system information for the new server

[root@svr02 ~]# cat /etc/*-release
CentOS release 6.7 (Final)
[root@svr02 ~]# cat /proc/version
Linux version 2.6.32-504.12.2.el6.x86_64 (mockbuild@c6b9.bsys.dev.centos.org) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-11) (GCC) ) #1 SMP Wed Mar 11 22:03:14 UTC 2015
[root@svr02 ~]# uname -mrs
Linux 2.6.32-504.12.2.el6.x86_64 x86_64

This is the ./citserver terminal output for the new server:

citserver[6631]: *** Citadel server engine v9.01 (build a845b4f) ***
citserver[6631]: Copyright (C) 1987-2015 by the Citadel development team.
citserver[6631]: This program is distributed under the terms of the GNU General Public License.
citserver[6631]: 
citserver[6631]: Called as: ./citserver
citserver[6631]: libcitadel(unnumbered)
citserver[6631]: Loading citadel.config
citserver[6631]: Acquiring control record
citserver[6631]: master_startup() started
citserver[6631]: Checking directory access
citserver[6631]: Opening databases
citserver[6631]: bdb(): open_databases() starting
citserver[6631]: Compiled db: Berkeley DB 5.1.29: (October 25, 2011)
citserver[6631]:   Linked db: Berkeley DB 5.1.29: (October 25, 2011)
citserver[6631]: Calculated dbversion: 5001029
citserver[6631]:   Previous dbversion: 5001029
citserver[6631]: Linked zlib: 1.2.3
citserver[6631]: bdb(): Setting up DB environment
citserver[6631]: dbenv->open(dbenv, /usr/local/citadel/data/, 19091, 0)
Finding last valid log LSN: file: 1 offset 293588
Recovery starting from [1][291330]

The whole log in svr02_citserver http://pastebin.com/zrLyUstX

This is part of my 'messages' file on the new server:

Aug 12 08:16:50 svr02 citserver[1970]: CC[0]MSGMessage 56340 appears to be corrupted.
Aug 12 08:16:50 svr02 citserver[1970]: SMTPCQ: tried 56340 but no such message!
Aug 12 08:16:50 svr02 citserver[1970]: SMTPCQ: queue run completed; 1 messages processed 0 activated
Aug 12 08:16:50 svr02 citserver[1970]: Imported message #84986, size=0, refcount=0, content-type: Content-Transfer-Encoding:MIME-Version:From:Reply-To:To:Subject
Aug 12 08:16:50 svr02 citserver[1970]: Imported message #84988, size=0, refcount=0, content-type: multipart/alternative
Aug 12 08:16:50 svr02 citserver[1970]: Imported message #84990, size=0, refcount=0, content-type: text/plain
Aug 12 08:16:50 svr02 citserver[1970]: No external notifiers configured on system/user

The whole log in svr02_messages http://pastebin.com/aRK7mHuq

The ./citserver terminal output for the old server:

citserver[1777]: *** Citadel server engine v8.24 (build 5644ab7) ***
citserver[1777]: Copyright (C) 1987-2014 by the Citadel development team.
citserver[1777]: This program is distributed under the terms of the GNU General Public License.
citserver[1777]: 
citserver[1777]: Called as: ./citserver
citserver[1777]: libcitadel(unnumbered)
citserver[1777]: Loading citadel.config
citserver[1777]: Acquiring control record
citserver[1777]: master_startup() started
citserver[1777]: Opening databases
citserver[1777]: bdb(): open_databases() starting
citserver[1777]: Compiled db: Berkeley DB 5.1.29: (October 25, 2011)
citserver[1777]:   Linked db: Berkeley DB 5.1.29: (October 25, 2011)
citserver[1777]: Calculated dbversion: 5001029
citserver[1777]:   Previous dbversion: 5001029
citserver[1777]: Linked zlib: 1.2.3
citserver[1777]: bdb(): Setting up DB environment
citserver[1777]: dbenv->open(dbenv, /usr/local/citadel/data/, 19091, 0)
Finding last valid log LSN: file: 223 offset 10084262
Recovery starting from [223][10082004]

The whole log in bak02_citserver http://pastebin.com/Td9ak6KC

The whole log 'messages' file on the old server: bak02_messages http://pastebin.com/mwziuXyk, but it seems to be ok

Thank you in advance,

 

jcigala

 

 

Tue Jun 23 2015 06:47:47 EDT from breakingbigd @ Uncensored Subject: MIGR IMPORT not importing my messages

Hi all,

I have an old system that's been faithfully running Citadel 8.04 for the past few years. Life happened, and all server maintenance took the very back seat. At this point, I'm thinking it'd just be better to scrap the whole OS and reinstall my stuff. Way too many config changes to keep up with if I updated everything, and I'd imagine some of those would result in an unbootable/highly broken system. As a test, I tried a ctdlmigrate to another machine. Stuff was exported and imported, much rsyncing was done, and ctdlmigrate exited with a failure message because of a missing source directory on the original machine. But everything seemed fine, so I logged in and tried listing/reading my mail. Webcit showed all my messages as empty, with no subject, dated January 1, 1970. Citadel told me it couldn't access the messages on disk. I poked at /var/log/messages, and saw that all the citserver's importing chatter was suppressed, so tried the whole thing again, only with my new citserver in the forground. This is a tiny snippet of what I got:

citserver[29869]: Imported message #29501, size=0, refcount=1, content-type: text/plain
citserver[29869]: Imported message #29502, size=0, refcount=1, content-type: text/plain
citserver[29869]: client_read_blob() failed: StrBufReadBLOBBuffered: to many selects; aborting.
citserver[29869]: Closing socket 39
...

citserver[29869]: CC[1]MSG<0000000008.Contacts> 4 new of 4 total messages, oldest=23692, newest=24604
citserver[29869]: CC[1]MSGMessage 23692 appears to be corrupted.
citserver[29869]: CC[1]MSGMessage 23693 appears to be corrupted.
citserver[29869]: CC[1]MSGMessage 23702 appears to be corrupted.
citserver[29869]: CC[1]MSGMessage 24604 appears to be corrupted.

...That goes on for quite a while. What do I need to do to fix this? A look at the xml shows that as the last message number, and sendcommand doesn't report any problems, but I really don't like the look of that client_read_blob error, and apparently citserver doesn't either. All those corrupted, inaccessible messages...

 

I'd appreciate any help/pointers here. I can provide more of citserver's log, just didn't think anyone would wanna see 1.6MB of that sorta thing. :)

Thanks,

KJ4UFX



 



[#] Sun Aug 16 2015 06:36:14 EDT from dothebart @ Uncensored

Subject: Re: changing the base URL

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

 

Wed Aug 12 2015 09:59:10 EDT from "tony hughes" <tony.john.hughes@gmail.com> Subject: changing the base URL
Hey,
 
Can't find it written anywhere but how can i change the base url from / thinking of changing to /mail for a reverse proxy.
 
 
Regards,
 
Tony.
 


have a look at..

http://citadel.org/doku.php/faq:installation:apacheproxy



[#] Sun Aug 16 2015 06:45:16 EDT from dothebart @ Uncensored

Subject: Re: MIGR IMPORT not importing my messages

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

Yes, I can confirm that the migrate in 9.01 is broken.

I've repaired several things, if you like to compile from git you should be able to utilize these fixes.

It also seems as if dumping & re-loading without the migr tool works better.

You can checkout the 9.01 tag and cherry-pick my commits over.



[#] Sun Aug 16 2015 16:52:12 EDT from cryptearth @ Uncensored

Subject: can't start-up citadel after update opensuse 13.1 to 13.2 on ovh

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

Hey there everybody,

as Google didn't helped I had to register and ask here for help directly in the main support-forum (love how you guys use your own software even for the support).

As the title says : I updated my OVH-root from opensuse 13.1 to 13.2 (mainly cause support for PHP5.4 dropped last friday). So I took the easy way and started a clean re-install with the new OS-version. Installed citadel as usual, tried to set it up and boom - ran into this error

[code]

root1:~ # systemctl status citadel
citadel.service - Citadel Groupware Server
   Loaded: loaded (/usr/lib/systemd/system/citadel.service; disabled)
   Active: failed (Result: exit-code) since Sun 2015-08-16 22:45:12 CEST; 3s ago
  Process: 10027 ExecStart=/usr/sbin/citserver -d -l${CITADEL_LOG_FACILITY} ${CITADEL_DEBUG_AREA} ${CITADEL_HOME_DIR} (code=exited, status=0/SUCCESS)
 Main PID: 10028 (code=exited, status=105)

Aug 16 22:45:12 root1 citserver[10029]: dbenv->open(dbenv, /var/lib/citadel/data/, 10899, 0)
Aug 16 22:45:12 root1 citserver[10029]: DB: Finding last valid log LSN: file: 1 offset 112998
Aug 16 22:45:12 root1 citserver[10029]: DB: Recovery starting from [1][28]
Aug 16 22:45:12 root1 citserver[10029]: DB: Recovery complete at Sun Aug 16 22:45:12 2015
Aug 16 22:45:12 root1 citserver[10029]: DB: Maximum transaction ID 8000001a Recovery checkpoint [1][114077]
Aug 16 22:45:12 root1 citserver[10029]: Starting up DB
Aug 16 22:45:12 root1 citserver[10029]: Checking floor reference counts
Aug 16 22:45:12 root1 citserver[10029]: bdb(): cursor still in progress on cdb 04: can't begin transaction during r/o cursor
Aug 16 22:45:12 root1 citserver[10029]: citserver is stopping in order to prevent data loss. uid=0 gid=0 euid=0 egid=0
Aug 16 22:45:12 root1 systemd[1]: Unit citadel.service entered failed state.
[/code]

As far as Google helped it seems some wrong with the Berkley-DB. opensuse 13.2 uses libdb 4.8 wich can't changed to an older version as it would mess up many base-systems.

Is there any advise I could try to fix it and start my mail-server up again ?

It's not a hard pain in the ass as this system is only used by myself for some "internal-like" mails wich can be done otherwise, but as I'm usin citadel for over a year now I don't want to change and look for another system.

Hope this can get fixed soon.



[#] Mon Aug 17 2015 07:30:19 EDT from dothebart @ Uncensored

Subject: Re: can't start-up citadel after update opensuse 13.1 to 13.2 on ovh

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

Create a backup and try database_cleanup.sh and check whether the problem persists.



[#] Mon Aug 17 2015 16:35:59 EDT from cryptearth @ Uncensored

Subject: Re: can't start-up citadel after update opensuse 13.1 to 13.2 on ovh

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

Well, that didn't helped (obviously, as what's written in this script is just : copy to tmp - delete current files - reload from tmp ~ I'm not see how this should help at all).

Another think that kinda bothered me : on OpenSuSE you need to add the doc-package as it contains the script and also add Berkeley-utils (wich should be marked as a dependency) wich contains the need binaries.

To be true : I guessed this wouldn't help at all because citadel fails on creating these files on the first time.

I also set-up a 13.1-vm and copied the 13.1 files to the 13.2 vm - still getting the same error.

So for me it seems there could be two reasons left : 1) error in release for 13.2 - 2) error on dependecies.

Any other advice ?

Sadly, OVH doesn't allow me to step-back to 13.1 as it isn't available for install anymore.

 

What I had not tried so far : downloading source and building on my own. Maybe this is the next step I try.



[#] Tue Aug 18 2015 03:47:46 EDT from dothebart @ Uncensored

Subject: Re: can't start-up citadel after update opensuse 13.1 to 13.2 on ovh

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

 

Mon Aug 17 2015 16:35:59 EDTfrom cryptearth @ Uncensored Subject: Re: can't start-up citadel after update opensuse 13.1 to 13.2 on ovh

Well, that didn't helped (obviously, as what's written in this script is just : copy to tmp - delete current files - reload from tmp ~ I'm not see how this should help at all).

Another think that kinda bothered me : on OpenSuSE you need to add the doc-package as it contains the script and also add Berkeley-utils (wich should be marked as a dependency) wich contains the need binaries.

To be true : I guessed this wouldn't help at all because citadel fails on creating these files on the first time.

 

No, its not as obvious, since its not copying the files, but dumping and re-importing it.

In debian its not a dependency but a recommendation. I think its similar in the rpms.

 

I also set-up a 13.1-vm and copied the 13.1 files to the 13.2 vm - still getting the same error.

So for me it seems there could be two reasons left : 1) error in release for 13.2 - 2) error on dependecies.

Any other advice ?

Sadly, OVH doesn't allow me to step-back to 13.1 as it isn't available for install anymore.

What I had not tried so far : downloading source and building on my own. Maybe this is the next step I try.



since the error comes from the berkeley db layer which citadel sits on top of, that may be the next step.



[#] Tue Aug 18 2015 12:23:49 EDT from jcigala @ Uncensored

Subject: Re: MIGR IMPORT not importing my messages

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

Can I copy ctdlmigrate v8.24 and replace the version came with v9.01? I'm not a developer, I don't know if there are database issues or any other problem if I use the old ctdlmigrate version. What do you think?

 

 

Sun Aug 16 2015 06:45:16 EDT from dothebart @ Uncensored Subject: Re: MIGR IMPORT not importing my messages

Yes, I can confirm that the migrate in 9.01 is broken.

I've repaired several things, if you like to compile from git you should be able to utilize these fixes.

It also seems as if dumping & re-loading without the migr tool works better.

You can checkout the 9.01 tag and cherry-pick my commits over.



 



[#] Tue Aug 18 2015 19:02:50 EDT from cryptearth @ Uncensored

Subject: Re: can't start-up citadel after update opensuse 13.1 to 13.2 on ovh

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

Well, I tried the easy-install-script in a fresh new clean VM, and the error still exists. It builds just fine, but if it tries to start up the same error message appears.

As noted earlier : I can't change libdb as many system-level things depends on it.

So, even as the own build failed I guess there is something wrong with the B-DB of OpenSuSE 13.2 wich causes this error.

Is there anyway around it so citadel doesn't use they main libdb but the donwloaded one ? As I really want to continue usin Citadel. Would appreciate any help.



Go to page: [1] 2 3 4 5 ... Last