1 Topic by agrophyzz

  • agrophyzz
  • Member
  • Offline
  • Registered: 2022-02-01
  • Posts: 3

Topic: Installation freezes at one of the MariaDB files

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

Installation log shows this and installation stops

/usr/ports/databases/mariadb105-server/work/mariadb-10.5.15/sql/yy_mariadb.cc:34992: warning: suspicious sequence in the output: b4_bin

Bison version is 3.8.2, system is fresh and only recently installed. What in the world can cause this crap?

----

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

2 Reply by agrophyzz (edited by agrophyzz 2022-05-12 20:19:20)

  • agrophyzz
  • Member
  • Offline
  • Registered: 2022-02-01
  • Posts: 3

Re: Installation freezes at one of the MariaDB files

Upgraded the fresh FreeBSD 13.0-RELEASE-p3 to the newest FreeBSD 13.1-RC6-p0 and then restarted the installation. Warning persists, though not stalling the installation process and throwing additional -Wother variable signature, previously unable to occur.

3 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,082

Re: Installation freezes at one of the MariaDB files

So the installer finished without error now?

4 Reply by jloc0

  • jloc0
  • Member
  • Offline
  • Registered: 2017-11-15
  • Posts: 6

Re: Installation freezes at one of the MariaDB files

My workaround for this was to manually build the mariadb port using the expected config and then mark it as finished in the iRedMail installer log so it moves onto the next item during the install.

I believe the failure is caused by not enough free ram. I posted this issue on github a while back as well.