[SOGo] BTS activities for Monday, October 12 2020

[SOGo reporter]

Title: BTS activities for Monday, October 12 2020





  
BTS Activities

  Home page: https://sogo.nu/bugs
  Project: SOGo
  For the period covering: Monday, October 12 2020

  
  
idlast updatestatus (resolution)categorysummary
	
	
	  
	
4634
	2020-10-12 11:16:17
	updated (open)
	with SOGo
	SOGo does not correctly import S/MIME certificates
	
	  
	
  
  


-- users@sogo.nuhttps://inverse.ca/sogo/lists

Re: [SOGo] Howto Migrating database to new database server? Mysql 5.6 => MySQL 8

[goetz.reini...@filmakademie.de]

Hi,

> Am 12.10.2020 um 13:47 schrieb Odhiambo Washington (odhia...@gmail.com) 
> :
> 
> 
> 
> On Mon, 12 Oct 2020 at 13:39, Götz Reinicke  > wrote:
> Hi,
> 
> what are the right steps to migrate the SOGo database to a new database 
> server (with new server name):
> 
> - dump/backup all user data
> - shutdown sogo
> - add a new database to the new server
> - edit the sogo.conf database serve name/user/password
> 
> It's easier to just reuse the creds from sogo.conf so no need to edit 
> sogo.conf (dbname, username, password):
> MySQL>CREATE USER 'username'@'hostname OR IP' IDENTIFIED WITH 
> mysql_native_password BY 'the_password';
> MYSQL>GRANT ALL ON dbname.* TO  'username'@'hostname OR IP‘;


true@credentials. I’m used to set new ones, so I can be 100% sure I’m 
connecting to the new db.


> 
> - restart sogo
> - restore the user data from the backup
> 
> Did I miss something?
> 
> Yes. move the dump to the new server :-)

I guess you talk about the database dump? As the database server name will 
change, I can’t use the „old“ dump anymore I think.

By dumping the user data I was referring to the pogo-tool backup. May be I was 
a bit confusing, or did misunderstand you.

>  
> 
> Are there known problems with the DB version upgrade?
> 
> I did not encounter any when I migrated from 5.7 to 8.0.

Good to hear. thx.

Regards. . Götz

smime.p7s
Description: S/MIME cryptographic signature

Re: [SOGo] SOGo 5.0.0 Login Problem -> SOGo 5.0.1

[nico...@hoeft.de]

Hi Lars,


Any ideas on that?

It is no problem running 5.0.0 for us for now, I just wanted to share 
this, as it might be helpful. Or should I run SOGo 5.0.1 with SOPE 
5.0.0 on commit 099e8b0ec8251dbddeff337fe728d9398ba744b2?


This Log is not really helpful (at least not to me), unfortunately. If 
you have time and want to figure out what commit is causing this, I'd 
suggest to start with 5.0.0 both SOGo and SOPE and then upgrade SOPE to 
5.0.1 and then if it still works try to bisect which SOGo commit is 
causing the login problems.



cheers,

Nicolas



--
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] Howto Migrating database to new database server? Mysql 5.6 => MySQL 8

[Odhiambo Washington]

On Mon, 12 Oct 2020 at 13:39, Götz Reinicke  wrote:

> Hi,
>
> what are the right steps to migrate the SOGo database to a new database
> server (with new server name):
>
> - dump/backup all user data
> - shutdown sogo
> - add a new database to the new server
> - edit the sogo.conf database serve name/user/password
>

It's easier to just reuse the creds from sogo.conf so no need to edit
sogo.conf (dbname, username, password):
MySQL>CREATE USER 'username'@'hostname OR IP' IDENTIFIED WITH
mysql_native_password BY 'the_password';
MYSQL>GRANT ALL ON dbname.* TO  'username'@'hostname OR IP';

- restart sogo
> - restore the user data from the backup
>
> Did I miss something?
>

Yes. move the dump to the new server :-)


>
> Are there known problems with the DB version upgrade?
>

I did not encounter any when I migrated from 5.7 to 8.0.


-- 
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", grep ^[^#] :-)
-- 
users@sogo.nu
https://inverse.ca/sogo/lists

[SOGo] Howto Migrating database to new database server? Mysql 5.6 => MySQL 8

[goetz.reini...@filmakademie.de]

Hi,

what are the right steps to migrate the SOGo database to a new database server 
(with new server name):

- dump/backup all user data
- shutdown sogo
- add a new database to the new server
- edit the sogo.conf database serve name/user/password
- restart sogo
- restore the user data from the backup

Did I miss something?

Are there known problems with the DB version upgrade?


Thanks for hints and suggestions. Regards . Götz




smime.p7s
Description: S/MIME cryptographic signature

Re: [SOGo] SOGo 5.0.0 Login Problem -> SOGo 5.0.1

[Lars Liedtke]

Hi Nicholas ,

SOGo 5.0.0 with SOPE 5.0.0 updated to commit
099e8b0ec8251dbddeff337fe728d9398ba744b2 (don't leak fds) worked. So
after that I saw that SOGo 5.0.1 and SOPE 5.0.1 were released. So I
tried combining both. But then I again get a blank page after Login,
with errors in the Log like:

> Oct 09 15:17:31 sogod [38523]: |SOGo|   using root-url from context:
> /SOGo/so/
> Oct 09 15:17:31 sogod [38523]: |SOGo| ROOT baseURL(no container,
> name=(null)):
>   own: /SOGo/so/
> Oct 09 15:17:31 sogod [38523]: <0x8127dc208[SOGoUserFolder]:ry86>
> baseURL: name=ry86 (container=SOGo)
>   container: /SOGo --
> https://mail.integration.punkt.hosting/SOGo/so/ry86/Calendar/view
>   own: /SOGo/so/ry86
> Oct 09 15:17:31 sogod [38523]: |SOGo|   using root-url from context:
> /SOGo/so/
> Oct 09 15:17:31 sogod [38523]: |SOGo| ROOT baseURL(no container,
> name=(null)):
>   own: /SOGo/so/
> Oct 09 15:17:31 sogod [38523]: <0x8127dc208[SOGoUserFolder]:ry86>
> baseURL: name=ry86 (container=SOGo)
>   container: /SOGo --
> https://mail.integration.punkt.hosting/SOGo/so/ry86/Calendar/view
>   own: /SOGo/so/ry86
> Oct 09 15:17:31 sogod [38523]:
> <0x80c2a8408[SOGoAppointmentFolders]:Calendar> baseURL: name=Calendar
> (container=SOGoUserFolder)
>   container: /SOGo/so/ry86/
>   own: /SOGo/so/ry86/Calendar
Any ideas on that?

It is no problem running 5.0.0 for us for now, I just wanted to share
this, as it might be helpful. Or should I run SOGo 5.0.1 with SOPE 5.0.0
on commit 099e8b0ec8251dbddeff337fe728d9398ba744b2?

Cheers

Lars

Am 05.10.20 um 14:53 schrieb Lars Liedtke (lied...@punkt.de):
>
> Hi Nicholas,
>
> thank you, indeed I was building SOGo 5 with the latest SOPE Port in
> FreeBSD, which is still on 4.x.
>
> So I will have to try to update the sope4 Port to as well and try with
> that.
>
> Cheers
>
> Lars
>
> Am 04.10.20 um 16:10 schrieb Nicolas Höft (nico...@hoeft.de):
>>
>> Hi,
>>
>> this error:
>>
>> > 2020-10-01 17:35:39.988 sogod[14915:101031] EXCEPTION: > > 0x80c39b878> NAME:NSInvalidArgumentException REASON:-[NSURL 
>> > queryComponents]: 
>> > unrecognized selector sent to instance 0x80c39b7e8 INFO:(null)
>>
>>
>> Indicates your SOPE version is not up-to-date. Make sure you are building 
>> with at least SOPE 5.0.0 (tagged as `SOPE-5.0.0` in git).
>> Also if you're using starttls for smtp or imap, better use the latest HEAD, 
>> otherwise you're going to suffer from leaking file descriptors.
>>
>> Cheers,
>> Nicolas
>> -- 
>> users@sogo.nu
>> https://inverse.ca/sogo/lists
> -- 
> ---
> punkt.de GmbH
> Lars Liedtke
> .infrastructure
>
> Kaiserallee 13a   
> 76133 Karlsruhe
>
> Tel. +49 721 9109 500
> https://infrastructure.punkt.de
> i...@punkt.de
>
> AG Mannheim 108285
> Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein
> -- 
> users@sogo.nu
> https://inverse.ca/sogo/lists

-- 
---
punkt.de GmbH
Lars Liedtke
.infrastructure

Kaiserallee 13a 
76133 Karlsruhe

Tel. +49 721 9109 500
https://infrastructure.punkt.de
i...@punkt.de

AG Mannheim 108285
Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein

-- 
users@sogo.nu
https://inverse.ca/sogo/lists