Zabbix 5.4.1 installation from repo error - Ubuntu 20.04.2

[Maximus_Mc]

Hi All,

I came across an error during the installation from the Zabbix repo:

root@zzzz-zabbix-1:~# apt update
Get:1 [URL]http://security.ubuntu.com/ubuntu[/URL] focal-security InRelease [114 kB]
Hit:2 [URL]http://archive.ubuntu.com/ubuntu[/URL] focal InRelease
Hit:3 [URL]https://repo.zabbix.com/zabbix/5.4/ubuntu[/URL] focal InRelease
Get:4 [URL]http://archive.ubuntu.com/ubuntu[/URL] focal-updates InRelease [114 kB]
Get:5 [URL]http://archive.ubuntu.com/ubuntu[/URL] focal-backports InRelease [101 kB]
Get:6 [URL]http://archive.ubuntu.com/ubuntu[/URL] focal-updates/main amd64 Packages [1,032 kB]
Get:7 [URL]http://archive.ubuntu.com/ubuntu[/URL] focal-updates/main i386 Packages [490 kB]
Get:8 [URL]http://archive.ubuntu.com/ubuntu[/URL] focal-updates/main amd64 c-n-f Metadata [ 13.5 kB]
Get:9 [URL]http://archive.ubuntu.com/ubuntu[/URL] focal-updates/universe amd64 Packages [78 4 kB]
Get:10 [URL]http://archive.ubuntu.com/ubuntu[/URL] focal-updates/universe i386 Packages [57 7 kB]
Get:11 [URL]http://archive.ubuntu.com/ubuntu[/URL] focal-updates/universe amd64 c-n-f Metad ata [17.7 kB]
Get:12 [URL]http://archive.ubuntu.com/ubuntu[/URL] focal-updates/multiverse amd64 Packages [23.6 kB]
Fetched 3,266 kB in 2s (1,713 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
8 packages can be upgraded. Run 'apt list --upgradable' to see them.
[U][B]N: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'https://repo.zabbix.com/zabbix/5.4/ubuntu focal InRelease' doesn't support architecture 'i386'[/B][/U]

So I did my fair share of googling and came across a "fix" where I appended [arch=amd64] within the repository statement in "zabbix.list" under apt sources:

[EMAIL="root@zzzz-zabbix-1:/etc/apt/sources.list"]root@zzzz-zabbix-1:/etc/apt/sources.list[/EMAIL].d# cat zabbix.list
[B]deb[U] [arch=amd64] [/U][URL]https://repo.zabbix.com/zabbix/5.4/ubuntu[/URL] focal main[/B]
deb-src [URL]https://repo.zabbix.com/zabbix/5.4/ubuntu[/URL] focal main

I re-ran apt update and the resulting returned repos had all the i386 ones removed which brought the hits from 12 down to 5:

[EMAIL="root@zzzz-zabbix-1:/etc/apt/sources.list"]root@zzzz-zabbix-1:/etc/apt/sources.list[/EMAIL].d# apt update
Hit:1 [URL]http://security.ubuntu.com/ubuntu[/URL] focal-security InRelease
Hit:2 [URL]http://archive.ubuntu.com/ubuntu[/URL] focal InRelease
Hit:3 [URL]http://archive.ubuntu.com/ubuntu[/URL] focal-updates InRelease
Hit:4 [URL]https://repo.zabbix.com/zabbix/5.4/ubuntu[/URL] focal InRelease
Hit:5 [URL]http://archive.ubuntu.com/ubuntu[/URL] focal-backports InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
8 packages can be upgraded. Run 'apt list --upgradable' to see them.

So the questions I have are:
1. Has anyone come across this in the latest installation of Zabbix on Ubuntu Server and is this error expected/common?
2. Is this a valid fix for the issue
3. What are the possible issues that can arise from this, noting that the install has been done on MariaDB and Apache2. So unless there are any services outside from Zabbix, the lack of i386 packages should not pose an issue?

Ubuntu 20.04.2
Zabbix 5.4.1

MariaDB
mysql Ver 15.1 Distrib 10.3.29-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2

Apache2
Server version: Apache/2.4.41 (Ubuntu)
Server built: 2020-08-12T19:46:17

Any guidance would be greatly appreciated, thank you.

[Maximus_Mc]

So just a quick update, the initial install mentioned above is on Vultr. I downloaded the Server ISO from Ubuntu directly and ran the installation on Virtualbox and VMware locally and I did not run into this problem, if it is a problem. Not a single complaint about i386 support. Zabbix seems to be installed correctly in Vultr, but I am curious to understand what the difference is. I also ran uname -m and both show 64 bit.

root@zzzz-zabbix-1:~# uname -m
x86_64

[Maximus_Mc]

I just completed a ticket with the Vultr Team, which I must say was awesome support. They confirmed that the issue can be replicated and is related to the repos that are being installed, so the fix I applied was appropriate, but cosmetic as the error does not affect anything and is ignored as the error states. So we can consider this issue solved. I guess this is a good place for anyone having a similar issue. Thanks.