1

Topic: Ubuntu 18.0.4 LTS and upgrade to 1.5.1 - fail

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release):      2021091301
- Deployed with iRedMail Easy or the downloadable installer? WebEasy
- Linux/BSD distribution name and version: Ubuntu 18.04. LTS
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): mariaDB
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? Yes
====

Upgrade itself went smooth, but iRedMail was unusable slow after, even login took >10 secs, normally it's instantly.

Went back to the "old" version.

Is this a side effect of (still) running Ubuntu 18.0.4 - and if so, are their instructions available what to do after upgrading to Ubuntu 20.0.x?

Thanx,

Peter

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: Ubuntu 18.0.4 LTS and upgrade to 1.5.1 - fail

The slowness is not expected, and Ubuntu 18.04 is fine.
Are we walking about the slow login on Roundcube webmail, or SOGo, or iRedAdmin-Pro?

3

Re: Ubuntu 18.0.4 LTS and upgrade to 1.5.1 - fail

ZhangHuangbin wrote:

The slowness is not expected, and Ubuntu 18.04 is fine.
Are we walking about the slow login on Roundcube webmail, or SOGo, or iRedAdmin-Pro?

Hi Huangbin,

All of them were slow, the WebMin access  (and ssh) was fast as usual.

Peter

4

Re: Ubuntu 18.0.4 LTS and upgrade to 1.5.1 - fail

All of them? This is weird.

Roundcube is a php application, iRedAdmin-Pro is a Python application, SOGo is a ObjectiveC application, if they all are slow, then it’s probably  the web server causes the issue. Did you take a look at web server performance?
Do you run netdata for real-time system monitoring?

5

Re: Ubuntu 18.0.4 LTS and upgrade to 1.5.1 - fail

ZhangHuangbin wrote:

All of them? This is weird.

Roundcube is a php application, iRedAdmin-Pro is a Python application, SOGo is a ObjectiveC application, if they all are slow, then it’s probably  the web server causes the issue. Did you take a look at web server performance?
Do you run netdata for real-time system monitoring?

Neither of all - but I try again this weekend.