Hmm.. upgrading to latest mariaDB corrupted something.(on test).. and
the upgrade process revealed some strange messages from the installed
mariadb so I had to update with --allowerasing.
Didn't help out anything on the qmailadmin issue so
Decided to 'dnf downgrade qmailadmin' on the prod QMT server and all is
back to normal - working (tested with old qmt and test qmt servers
shutdown 👍)
/Finn
Den 25-09-2020 kl. 15:45 skrev qm...@mailonly.dk:
Well .. works perfectly may be an overstatement ...
I think I may have been tricked by my old server (centos 7) and seen the
qmailadmin view from that server because after shutting down the old one
i do only get a blank screen whenever I submit user, domain and password
in order to login.
This is what I see i the log file on the Centos 8 server (journalctl)
kernel: traps: index.cgi[32281] general protection fault ip:7f8b356b724d
sp:7ffc36150ef0 error:0 in libmariadb.so.3[7f8b35696000+47000]
I'll try to update my QMT to latest MariaDB and do some testing.
/Finn
Den 24-09-2020 kl. 16:45 skrev qm...@mailonly.dk:
Thanks - works perfectly
/Finn
Den 23-09-2020 kl. 20:46 skrev Eric Broch:
CentOS 8: qmailadmin w/new interface in repo...may need to wait for
all repos to update or go here:
http://repo.whitehorsetc.com/8/testing/mysql/x86_64/
http://repo.whitehorsetc.com/8/testing/mariadb/x86_64/
On 9/22/2020 8:30 AM, qm...@mailonly.dk wrote:
I'm running Mariadb.
(sqlite3 for fail2ban ofcourse)
Also look into the new dnf tool that replaces yum 🤨
Not stressing You but the 'new' QmailAdmin could be nice for QMT-C8
as well - I have a password manager keeping all the secret
informations created on my Centos7 QMT (with the 'new' qmailadmin
look) and it doesn't like the old qmailadmin view 😞 - but no hurry
I can manage by typing (ouch my fingers) the info when needed.
(Only thing I've noticed is the spamd taking many seconds to check
messages, but it may relate to the old, old server (running centos8
server with KVM - running a Centos 8 - Webserver in one VM and QMT
Centos 8 in another VM) I'm using until I get a new disk for the
real production server.
/Finn
Den 22-09-2020 kl. 15:51 skrev Eric Broch:
This is good news. Thanks for letting me know, Finn. I may move
everything to production (current) repo now.
I'll make the necessary changes to the run file.
Are you running MySQL or MariaDB? I'm thinking about going to one
or the other due to time constraints.
Eric
On 9/22/2020 2:50 AM, qm...@mailonly.dk wrote:
Hi Eric.
I have installed and put Your Qmt for Centos 8 into production
over the weekend.(done some testing first ofcourse)
After running QMT on Centos (5)(6) and recently 7 over the years I
had difficulties converting to EPEL ClamAV - so I decided to go
for the latest and greatest QMT for Centos 8
Using Your instructions from 'Migrate to Centos 7/QMT host' I got
all production data needed.
I ran into 2 issues :
first issue was /var/qmail/supervise/smtps/run that needs to
include the export FORCETLS=0 and export SMTPAUTH="!+cram" in
order to be able to submit mail (just like You helped me solve
same thing in the Centos 7 version)
the second issue is sa-update - it comes to abrupt stop
Systemctl :
Started Spamassassin Rules Update.
Sep 21 00:32:53 my.domain.com sa-update.cron[608160]: channel:
could not find working mirror, channel failed
Sep 21 00:32:54 my.domain.com sa-update.cron[608160]: 21-Sep-2020
00:32:54: SpamAssassin: Update available, but download or extract
failed
Sep 21 00:32:54 my.domain.com systemd[1]: sa-update.service: Main
process exited, code=exited, status=4/NOPERMISSION
Sep 21 00:32:54 my.domain.com systemd[1]: sa-update.service:
Failed with result 'exit-code'.
From journalctl :
spamd[572300]: config: cannot create user preferences file
//.spamassassin/user_prefs: No such file or directory
Sep 21 11:01:38 my.domain.com spamd[572300]: spamd: failed to
create rea dable default_prefs:
//.spamassassin/user_prefs
Sa-update works perfectly when started from command line and I
will look into the matter when time permits.
For now, QMT for Centos8 seems to work perfectly fine and I even
changed my fail2ban and firewall to work with nftables (replacing
iptables) and overall the server seems to run faster...
Thanx for Your GREAT work keeping all of us and QMT updated
Regards,
Finn
---------------------------------------------------------------------
To unsubscribe, e-mail:
qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail:
qmailtoaster-list-h...@qmailtoaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail:
qmailtoaster-list-h...@qmailtoaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail:
qmailtoaster-list-h...@qmailtoaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
