[prev in list] [next in list] [prev in thread] [next in thread]
List: kroupware
Subject: Re: Service cyrus-imapd does not start after restore
From: Dashamir Hoxha <dashohoxha () gmail ! com>
Date: 2019-07-03 13:23:07
Message-ID: CAMucfLyOu0KvEVCGVPpOpgi3-ECHqzK05ZSB2M9hs_8Vo0rgJQ () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Wed, Jul 3, 2019 at 12:52 PM Dashamir Hoxha <dashohoxha@gmail.com> wrote:
> On Wed, Jul 3, 2019 at 12:31 PM Jan Kowalsky <jankow@datenkollektiv.net>
> wrote:
>
>>
>> If the problem still exists: Please try to send some debugging
>> information. But, if nothing helps, I could. But I have very little
>> experience with docker and do not feel very comfortable without direct
>> access to the cyrus instance ;-). Or is it a single container with full
>> stack and ssh?
>>
>
>
> The problem is that I am currently trying another solution (mailcow). As
> soon as I am done with this I may have another look at kolab (it is not
> possible to run to mail servers in parallel since they need to use the same
> ports). If I can't fix the problem again, I may ask again for help.
>
I realized that I can stop mailcow (with `docker-compose stop`) and then
run the kolab container. This way there will not be any port conflicts.
I tried the command `cyrus-master -D` that you suggested, but it does not
exist. My installation is based on Debian9.
If you have time to have a look at the server, please let me know. I can
share the screen of my server with you so that we can collaborate. I can
take care of the docker part, and you try to debug the problem with cyrus.
Let me know when you are free. We can meet on the #kolab channel on IRC.
Thanks,
Dashamir
>
> However, if someone has time to have a look at it, the scripts for
> building the container are here: https://gitlab.com/docker-scripts/kolab
> You can reproduce the problem by making first a backup (with `ds backup`),
> then rebuild the container (with `ds make`), then install kolab again
> (`kolab-setup`), then restore the backup (with `ds restore
> backup-file.tgz`).
>
[Attachment #5 (text/html)]
<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Wed, Jul 3, 2019 at 12:52 PM Dashamir Hoxha <<a \
href="mailto:dashohoxha@gmail.com">dashohoxha@gmail.com</a>> \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div \
dir="ltr">On Wed, Jul 3, 2019 at 12:31 PM Jan Kowalsky <<a \
href="mailto:jankow@datenkollektiv.net" \
target="_blank">jankow@datenkollektiv.net</a>> wrote:<br></div><div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br> If the problem \
still exists: Please try to send some debugging<br> information. But, if nothing \
helps, I could. But I have very little<br> experience with docker and do not feel \
very comfortable without direct<br> access to the cyrus instance ;-). Or is it a \
single container with full<br> stack and \
ssh?<br></blockquote><div><br></div><div><br></div><div>The problem is that I am \
currently trying another solution (mailcow). As soon as I am done with this I may \
have another look at kolab (it is not possible to run to mail servers in parallel \
since they need to use the same ports). If I can't fix the problem again, I may \
ask again for help.</div></div></div></blockquote><div><br></div><div>I realized that \
I can stop mailcow (with `docker-compose stop`) and then run the kolab container. \
This way there will not be any port conflicts.</div><div><br></div><div>I tried the \
command `cyrus-master -D` that you suggested, but it does not exist. My installation \
is based on Debian9.</div><div><br></div><div>If you have time to have a look at the \
server, please let me know. I can share the screen of my server with you so that we \
can collaborate. I can take care of the docker part, and you try to debug the problem \
with cyrus. Let me know when you are free. We can meet on the #kolab channel on \
IRC.</div><div><br></div><div>Thanks,</div><div>Dashamir</div><div> \
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px \
solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div \
class="gmail_quote"><div><br></div><div>However, if someone has time to have a look \
at it, the scripts for building the container are here: <a \
href="https://gitlab.com/docker-scripts/kolab" \
target="_blank">https://gitlab.com/docker-scripts/kolab</a></div><div>You can \
reproduce the problem by making first a backup (with `ds backup`), then rebuild the \
container (with `ds make`), then install kolab again (`kolab-setup`), then restore \
the backup (with `ds restore backup-file.tgz`).</div></div></div></blockquote><div> \
</div></div></div>
_______________________________________________
users mailing list
users@lists.kolab.org
https://lists.kolab.org/mailman/listinfo/users
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic