1

Topic: Problem with SOGo Active Sync upgrade cronjob

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release):
- Deployed with iRedMail Easy or the downloadable installer?
- Linux/BSD distribution name and version:
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):
- Web server (Apache or Nginx):
- Manage mail accounts with iRedAdmin-Pro?
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

Hi everyone! This is a very-noob- question. I received the following notification in my email. But I'm having a hard time trying to understand it. I think it says that it has some problems ugprading Active Sync, something in the first lines, about "debconf". But some lines below I think it says that it did upgraded that? I'm not completely sure.

Could someone help understand this message a little better? I googled several parts of this but couldn't find anything specific and I'm not sure exactly where to look in the documentation.

Any help would be really appreciated!

/etc/cron.daily/os-updates:
Hit:1 http://security.debian.org buster/updates InRelease
Get:2 https://packages.inverse.ca/SOGo/nightly/4/debian buster InRelease [2,513 B]
Get:3 https://packages.inverse.ca/SOGo/nightly/4/debian buster/buster amd64 Packages [6,197 B]
Hit:4 http://debian.mirror.serveriai.lt/debian buster InRelease
Fetched 8,710 B in 1s (7,365 B/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages will be upgraded:
sogo sogo-activesync
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 21.3 MB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 https://packages.inverse.ca/SOGo/nightly/4/debian buster/buster amd64 sogo-activesync amd64 4.3.2.20200626-1 [1,439 kB]
Get:2 https://packages.inverse.ca/SOGo/nightly/4/debian buster/buster amd64 sogo amd64 4.3.2.20200626-1 [19.8 MB]
apt-listchanges: Reading changelogs...
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
Fetched 21.3 MB in 4s (5,442 kB/s)
(Reading database ... (Reading database ... 5%(Reading database ... 10%(Reading database ... 15%(Reading database ... 20%(Reading database ... 25%(Reading database ... 30%(Reading database ... 35%(Reading database ... 40%(Reading database ... 45%(Reading database ... 50%(Reading database ... 55%(Reading database ... 60%(Reading database ... 65%(Reading database ... 70%(Reading database ... 75%(Reading database ... 80%(Reading database ... 85%(Reading database ... 90%(Reading database ... 95%(Reading database ... 100%(Reading database ... 110730 files and directories currently installed.)
Preparing to unpack .../sogo-activesync_4.3.2.20200626-1_amd64.deb ...
Unpacking sogo-activesync (4.3.2.20200626-1) over (4.3.2.20200625-1) ...
Preparing to unpack .../sogo_4.3.2.20200626-1_amd64.deb ...
Unpacking sogo:amd64 (4.3.2.20200626-1) over (4.3.2.20200625-1) ...
Setting up sogo:amd64 (4.3.2.20200626-1) ...
======= Important SOGo post-installation note =======

SOGo database schemas are _not_ automatically upgraded by
the packaging system.

Please check the list of database schema upgrade scripts
inside /usr/share/doc/sogo/ and apply them if needed.

More details can be found in the Upgrading section:
https://sogo.nu/files/docs/SOGoInstallationGuide.html#_upgrading

Setting up sogo-activesync (4.3.2.20200626-1) ...
Processing triggers for systemd (241-7~deb10u4) ...
Processing triggers for libc-bin (2.28-10) ...

2

Re: Problem with SOGo Active Sync upgrade cronjob

I think this is to do with the fact that it didn't have a console to output the results to, since it ran under cron and not as a logged in shell.

As far as I can tell, it looks like the update was successful, but my recommendation would be to avoid doing apt software updates with cron, better to schedule your time hands on with your updates so that you can see interactively whats happening. Last thing you want is all your configs wiped out by an automated update, or a situation where something stopped working who knows how long ago and you struggle to figure out when/what things went wrong smile

3 (edited by dropestein 2020-06-26 23:13:25)

Re: Problem with SOGo Active Sync upgrade cronjob

MuPp3t33r wrote:

I think this is to do with the fact that it didn't have a console to output the results to, since it ran under cron and not as a logged in shell.

As far as I can tell, it looks like the update was successful, but my recommendation would be to avoid doing apt software updates with cron, better to schedule your time hands on with your updates so that you can see interactively whats happening. Last thing you want is all your configs wiped out by an automated update, or a situation where something stopped working who knows how long ago and you struggle to figure out when/what things went wrong smile

Got it! Thanks for the suggestion smile

Actually, the only cron jobs I have is a certrenew with my normal user and iRedMail placed these ones in the root user:

30   3   *   *   *   /bin/bash /var/vmail/backup/backup_mysql.sh

# iRedAPD: Clean up expired tracking records hourly.
1   *   *   *   *   python2 /opt/iredapd/tools/cleanup_db.py >/dev/null

# iRedAPD: Convert SPF DNS record of specified domain names to IP
#          addresses/networks hourly.
2   *   *   *   *   python2 /opt/iredapd/tools/spf_to_greylist_whitelists.py >/dev/null

# iRedMail: Cleanup Amavisd database
1   2   *   *   *   python2 /opt/www/iredadmin/tools/cleanup_amavisd_db.py >/dev/null

# iRedAdmin: Clean up sql database.
1   *   *   *   *   python2 /opt/www/iredadmin/tools/cleanup_db.py >/dev/null 2>&1

# iRedAdmin: Delete mailboxes on file system which belong to removed accounts.
1   *   *   *   *   python2 /opt/www/iredadmin/tools/delete_mailboxes.py
# iRedMail: Backup SOGo data databases on 04:01AM
1   4   *   *   *   /bin/bash /var/vmail/backup/backup_sogo.sh

# Fail2ban: Unban IP addresses pending for removal (stored in SQL db).
* * * * * /bin/bash /usr/local/bin/fail2ban_banned_db unban_db

So... I don't exactly know where that message came from. Maybe it was something that runs in the first install? Because it arrived after I installed iRedMail

4

Re: Problem with SOGo Active Sync upgrade cronjob

dropestein wrote:

I don't exactly know where that message came from.

It's mentioned in first line of the cron output:

/etc/cron.daily/os-updates

----

Does my reply help a little? How about buying me a cup of coffee ($5) as an encouragement?

buy me a cup of coffee