Kopano core for ubuntu 20.04

fbartels

@cbnidk said in Kopano core for ubuntu 20.04:

can I do this if I am up runing with kopano server it shut be done

Some mysql can be applied with a restart, some others may need a dump and restore of the database.

@cbnidk said in Kopano core for ubuntu 20.04:

I have never done that before

Importing data does put a different load on the database than the usual daily usage.

cbnidk

Hi

I have tuned the database with this

innodb_buffer_pool_size = 3GB
innodb_log_file_size = 750M
innodb_log_buffer_size = 32M
max_allowed_packet = 32M
max_connections = kopano (server.cfg) threads(default 8) + thread_limit(default 40) + 9

but I have to # out the last line
max_connections = kopano (server.cfg) threads(default 8) + thread_limit(default 40) + 9
otherwise the copano server will not start
is this line important?
fornow it is # out,

Claus

cbnidk

hi

But it don’t help I have the same error log in syslog when using kopano-migration-imap

Claus

fbartels

@cbnidk said in Kopano core for ubuntu 20.04:

innodb_log_file_size = 750M

I would not set the log file size that high. rather have multiple smaller files.

@cbnidk said in Kopano core for ubuntu 20.04:

max_connections = kopano (server.cfg) threads(default 8) + thread_limit(default 40) + 9
but I have to # out the last line
max_connections = kopano (server.cfg) threads(default 8) + thread_limit(default 40) + 9
otherwise the copano server will not start

Why doesnt it start? What is the error message?

@cbnidk said in Kopano core for ubuntu 20.04:

But it don’t help

Slow disk maybe? Tuning is more than just configuration.

Edit: there are also way more parameters you can tune in MySQL for customers we have a detailed tuning guide that our support can send out.

cbnidk

Hi

how big will be good my old kopano is 134mb but this is default I thing

the error is
2020-05-20T21:22:56.449172: [error ] mysql_real_connect: Too many connections
2020-05-20T21:22:56.449209: [error ] Can’t update the database: MYSQL not initialized
in server.log

Claus

cbnidk

@cbnidk

hi

in my server log I got this one or two time a day

SQL [00020233] info: MySQL server has gone away. Reconnecting.
is there a way to fix this?
mysql config =
innodb_buffer_pool_size = 1600M
innodb_log_file_size = 400M
innodb_log_buffer_size = 100M
max_allowed_packet = 16M
innodb_file_per_table = ON
key_buffer_size = 400M

kopano 10.0.4
ubuntu 20.04

Claus

fbartels

@cbnidk which version as you using exactly. There was recently an issue with stale mysql connections, but that hs been solved meanwhile.

If its just a mysql connection being closed after reaching the connection timeout I would no worry about it.

cbnidk

hi

my ver. is kopano-server_10.0.4.79.bbc9fa6e6-0+91.1_amd64.deb
for ubuntu 20.04

Claus

fbartels

the latest is 10.0.5.2.9bfb891a3-0+102.1.

But is most probably just a connection timeout.

thctlo

You should verify if mysql/mariadb is fully updated.

My upgrade from 18.04 to 20.04 needed some fixing after the upgrade.
apache2 stopped working, mysql stopped working, thinks like that.
it also changed my interface from 0.0.0.0 to 127.0.0.1, i had to correct it manualy again.
check these things.

Which i never have these things in a same setups on Debian itself.
Always problems with Ubuntu and dist upgrades…

cbnidk

Hi

it was a fresh install on 20.04, is it the ip of mysql
or the kopano server you have 0.0.0.0
my kopano server connect to mysql on 127.0.0.1
Claus

cbnidk

Hi
after update ubuntu 20.04 I got this in log

2020-05-27T22:22:23.209505: [crit ] ----------------------------------------------------------------------
2020-05-27T22:22:23.238650: [crit ] Fatal error detected. Please report all following information.
2020-05-27T22:22:23.238672: [crit ] kopano-server 10.0.4
2020-05-27T22:22:23.238679: [crit ] OS: Ubuntu 20.04 LTS (Linux 5.4.0-31-generic x86_64)
2020-05-27T22:22:23.238694: [crit ] Thread name: kopano-server
2020-05-27T22:22:23.238769: [crit ] Peak RSS: 1231136
2020-05-27T22:22:23.238903: [crit ] Pid 2153 caught SIGSEGV (11), traceback:
2020-05-27T22:22:23.238910: [crit ] Backtrace:
2020-05-27T22:22:23.573715: [crit ] f0. /lib/x86_64-linux-gnu/libkcutil.so.0(+0x503e4) [0x7fa3937693e4]
2020-05-27T22:22:23.573751: [crit ] f1. /lib/x86_64-linux-gnu/libkcutil.so.0(+0x377a6) [0x7fa3937507a6]
2020-05-27T22:22:23.573756: [crit ] f2. /lib/x86_64-linux-gnu/libkcutil.so.0(+0x38e74) [0x7fa393751e74]
2020-05-27T22:22:23.573759: [crit ] f3. /lib/x86_64-linux-gnu/libpthread.so.0(+0x153c0) [0x7fa3923af3c0]
2020-05-27T22:22:23.573763: [crit ] f4. /lib/x86_64-linux-gnu/libpthread.so.0(pthread_rwlock_rdlock+0x10) [0x7fa3923a83f0]
2020-05-27T22:22:23.573766: [crit ] f5. /lib/x86_64-linux-gnu/libkcserver.so.0(+0xe1759) [0x7fa3935db759]
2020-05-27T22:22:23.573769: [crit ] f6. /lib/x86_64-linux-gnu/libkcserver.so.0(+0xe7866) [0x7fa3935e1866]
2020-05-27T22:22:23.573772: [crit ] f7. /lib/x86_64-linux-gnu/libkcserver.so.0(+0xba63c) [0x7fa3935b463c]
2020-05-27T22:22:23.573775: [crit ] f8. /lib/x86_64-linux-gnu/libpthread.so.0(+0x9609) [0x7fa3923a3609]
2020-05-27T22:22:23.573778: [crit ] f9. /lib/x86_64-linux-gnu/libc.so.6(clone+0x43) [0x7fa3920cc103]
2020-05-27T22:22:23.573789: [crit ] Signal errno: Success, signal code: 1
2020-05-27T22:22:23.573794: [crit ] Sender pid: 160, sender uid: 0, si_status: 0
2020-05-27T22:22:23.573802: [crit ] Signal value: 0, faulting address: 0xa0
2020-05-27T22:22:23.573806: [crit ] When reporting this traceback, please include Linux distribution name (and version), system architecture and Kopano version.
2020-05-27T22:23:59.291102: [=======] Starting kopano-server version 10.0.4 (pid 1419 uid 0)
2020-05-27T22:23:59.360593: [=======] Starting kopano-server version 10.0.4 (pid 1419 uid 997)

but I think everything is working

Claus

cbnidk

Hi

Aften one more update of Ubuntu 20.04 the error is gone, her today

Claus