davidep
(Davide Principi)
December 4, 2018, 9:10am
4
Please mark Oliver’s answer as topic solution!
grep NsReleaseLock /var/log/messages
Let’s see if the previous log files matche too…
grep NsReleaseLock /var/log/messages-*
And also
grep nethserver-check-nsreleaselock /var/log/cron*
This action was expected to switch the policy to “locked” automatically tonight
nethserver-base/root/etc/cron.daily/nethserver-check-nsreleaselock at 3.5.2 · NethServer/nethserver-base · GitHub
I’d say we’ve a Bug here: it runs after 0yum-cron
! See ls -l /etc/cron.daily/
.
lorcon
(Lorenzo)
December 4, 2018, 9:22am
5
Hi there,
We had the some prolem on 3 mail servers today. As temporary solution we disabled the dovecot antispam plugin. On
/etc/dovecot/dovecot.conf
we commented the lines about spam training. In this way we disabled the antispam plugin.
Afther that we restarted the dovecot services with
systemctl restart dovecot
(or via web interface) and with
systectl status dovecot
we verified that the error was gone away. In about 20 seconds the mail clients started to download the mails
2 Likes
oliver
(Oliver)
December 4, 2018, 9:42am
6
I have no further occurrences of NsReleaseLock in older log files.
[root@myserver dovecot.conf]# grep NsReleaseLock /var/log/messages-*
[root@ myserver dovecot.conf]#
[root@duplex dovecot.conf]# grep nethserver-check-nsreleaselock /var/log/cron*
/var/log/cron:Dec 2 08:33:38 myserver run-parts(/etc/cron.daily)[5447]: starting nethserver-check-nsreleaselock
/var/log/cron:Dec 2 08:33:39 myserver run-parts(/etc/cron.daily)[11366]: finished nethserver-check-nsreleaselock
/var/log/cron:Dec 3 05:26:57 myserver run-parts(/etc/cron.daily)[24034]: starting nethserver-check-nsreleaselock
/var/log/cron:Dec 3 05:26:58 myserver run-parts(/etc/cron.daily)[11029]: finished nethserver-check-nsreleaselock
/var/log/cron:Dec 4 04:04:58 myserver run-parts(/etc/cron.daily)[5880]: starting nethserver-check-nsreleaselock
/var/log/cron:Dec 4 04:06:07 myserver run-parts(/etc/cron.daily)[22308]: finished nethserver-check-nsreleaselock
/var/log/cron-20181111:Nov 4 05:59:10 myserver run-parts(/etc/cron.daily)[6509]: starting nethserver-check-nsreleaselock
/var/log/cron-20181111:Nov 4 05:59:11 myserver run-parts(/etc/cron.daily)[21602]: finished nethserver-check-nsreleaselock
/var/log/cron-20181111:Nov 5 08:31:11 myserver run-parts(/etc/cron.daily)[5461]: starting nethserver-check-nsreleaselock
/var/log/cron-20181111:Nov 5 08:31:12 myserver run-parts(/etc/cron.daily)[30499]: finished nethserver-check-nsreleaselock
/var/log/cron-20181111:Nov 6 06:52:50 myserver run-parts(/etc/cron.daily)[6208]: starting nethserver-check-nsreleaselock
/var/log/cron-20181111:Nov 6 06:52:51 myserver run-parts(/etc/cron.daily)[30177]: finished nethserver-check-nsreleaselock
/var/log/cron-20181111:Nov 7 05:57:17 myserver run-parts(/etc/cron.daily)[32215]: starting nethserver-check-nsreleaselock
/var/log/cron-20181111:Nov 7 05:57:18 myserver run-parts(/etc/cron.daily)[30963]: finished nethserver-check-nsreleaselock
/var/log/cron-20181111:Nov 8 04:14:19 myserver run-parts(/etc/cron.daily)[18339]: starting nethserver-check-nsreleaselock
/var/log/cron-20181111:Nov 8 04:14:20 myserver run-parts(/etc/cron.daily)[25756]: finished nethserver-check-nsreleaselock
/var/log/cron-20181111:Nov 9 08:12:05 myserver run-parts(/etc/cron.daily)[1070]: starting nethserver-check-nsreleaselock
/var/log/cron-20181111:Nov 9 08:12:06 myserver run-parts(/etc/cron.daily)[17962]: finished nethserver-check-nsreleaselock
/var/log/cron-20181111:Nov 10 04:23:34 myserver run-parts(/etc/cron.daily)[31648]: starting nethserver-check-nsreleaselock
/var/log/cron-20181111:Nov 10 04:23:35 myserver run-parts(/etc/cron.daily)[6636]: finished nethserver-check-nsreleaselock
/var/log/cron-20181118:Nov 11 06:09:08 myserver run-parts(/etc/cron.daily)[31879]: starting nethserver-check-nsreleaselock
/var/log/cron-20181118:Nov 11 06:09:09 myserver run-parts(/etc/cron.daily)[32519]: finished nethserver-check-nsreleaselock
/var/log/cron-20181118:Nov 12 07:40:40 myserver run-parts(/etc/cron.daily)[21853]: starting nethserver-check-nsreleaselock
/var/log/cron-20181118:Nov 12 07:40:41 myserver run-parts(/etc/cron.daily)[17894]: finished nethserver-check-nsreleaselock
/var/log/cron-20181118:Nov 13 09:23:28 myserver run-parts(/etc/cron.daily)[6385]: starting nethserver-check-nsreleaselock
/var/log/cron-20181118:Nov 13 09:23:29 myserver run-parts(/etc/cron.daily)[8172]: finished nethserver-check-nsreleaselock
/var/log/cron-20181118:Nov 14 07:42:36 myserver run-parts(/etc/cron.daily)[28652]: starting nethserver-check-nsreleaselock
/var/log/cron-20181118:Nov 14 07:42:37 myserver run-parts(/etc/cron.daily)[26861]: finished nethserver-check-nsreleaselock
/var/log/cron-20181118:Nov 15 08:42:19 myserver run-parts(/etc/cron.daily)[7882]: starting nethserver-check-nsreleaselock
/var/log/cron-20181118:Nov 15 08:42:20 myserver run-parts(/etc/cron.daily)[24861]: finished nethserver-check-nsreleaselock
/var/log/cron-20181118:Nov 16 06:12:51 myserver run-parts(/etc/cron.daily)[32686]: starting nethserver-check-nsreleaselock
/var/log/cron-20181118:Nov 16 06:12:52 myserver run-parts(/etc/cron.daily)[19153]: finished nethserver-check-nsreleaselock
/var/log/cron-20181118:Nov 17 04:20:27 myserver run-parts(/etc/cron.daily)[25207]: starting nethserver-check-nsreleaselock
/var/log/cron-20181118:Nov 17 04:20:28 myserver run-parts(/etc/cron.daily)[4571]: finished nethserver-check-nsreleaselock
/var/log/cron-20181125:Nov 18 04:05:10 myserver run-parts(/etc/cron.daily)[29499]: starting nethserver-check-nsreleaselock
/var/log/cron-20181125:Nov 18 04:05:11 myserver run-parts(/etc/cron.daily)[11436]: finished nethserver-check-nsreleaselock
/var/log/cron-20181125:Nov 19 03:13:35 myserver run-parts(/etc/cron.daily)[15959]: starting nethserver-check-nsreleaselock
/var/log/cron-20181125:Nov 19 03:13:36 myserver run-parts(/etc/cron.daily)[19729]: finished nethserver-check-nsreleaselock
/var/log/cron-20181125:Nov 20 08:25:17 myserver run-parts(/etc/cron.daily)[25880]: starting nethserver-check-nsreleaselock
/var/log/cron-20181125:Nov 20 08:25:18 myserver run-parts(/etc/cron.daily)[13074]: finished nethserver-check-nsreleaselock
/var/log/cron-20181125:Nov 21 07:43:38 myserver run-parts(/etc/cron.daily)[19634]: starting nethserver-check-nsreleaselock
/var/log/cron-20181125:Nov 21 07:43:39 myserver run-parts(/etc/cron.daily)[13731]: finished nethserver-check-nsreleaselock
/var/log/cron-20181125:Nov 22 06:24:47 myserver run-parts(/etc/cron.daily)[4023]: starting nethserver-check-nsreleaselock
/var/log/cron-20181125:Nov 22 06:24:48 myserver run-parts(/etc/cron.daily)[20418]: finished nethserver-check-nsreleaselock
/var/log/cron-20181125:Nov 23 07:59:21 myserver run-parts(/etc/cron.daily)[31631]: starting nethserver-check-nsreleaselock
/var/log/cron-20181125:Nov 23 07:59:22 myserver run-parts(/etc/cron.daily)[26006]: finished nethserver-check-nsreleaselock
/var/log/cron-20181125:Nov 24 04:57:28 myserver run-parts(/etc/cron.daily)[20775]: starting nethserver-check-nsreleaselock
/var/log/cron-20181125:Nov 24 04:57:29 myserver run-parts(/etc/cron.daily)[6660]: finished nethserver-check-nsreleaselock
/var/log/cron-20181202:Nov 25 04:51:27 myserver run-parts(/etc/cron.daily)[8128]: starting nethserver-check-nsreleaselock
/var/log/cron-20181202:Nov 25 04:51:28 myserver run-parts(/etc/cron.daily)[19008]: finished nethserver-check-nsreleaselock
/var/log/cron-20181202:Nov 26 03:35:14 myserver run-parts(/etc/cron.daily)[7429]: starting nethserver-check-nsreleaselock
/var/log/cron-20181202:Nov 26 03:35:15 myserver run-parts(/etc/cron.daily)[10886]: finished nethserver-check-nsreleaselock
/var/log/cron-20181202:Nov 27 09:31:00 myserver run-parts(/etc/cron.daily)[2095]: starting nethserver-check-nsreleaselock
/var/log/cron-20181202:Nov 27 09:31:01 myserver run-parts(/etc/cron.daily)[13560]: finished nethserver-check-nsreleaselock
/var/log/cron-20181202:Nov 28 03:35:37 myserver run-parts(/etc/cron.daily)[15772]: starting nethserver-check-nsreleaselock
/var/log/cron-20181202:Nov 28 03:35:39 myserver run-parts(/etc/cron.daily)[5903]: finished nethserver-check-nsreleaselock
/var/log/cron-20181202:Nov 29 08:25:09 myserver run-parts(/etc/cron.daily)[8882]: starting nethserver-check-nsreleaselock
/var/log/cron-20181202:Nov 29 08:25:10 myserver run-parts(/etc/cron.daily)[16572]: finished nethserver-check-nsreleaselock
/var/log/cron-20181202:Nov 30 05:18:52 myserver run-parts(/etc/cron.daily)[9027]: starting nethserver-check-nsreleaselock
/var/log/cron-20181202:Nov 30 05:18:53 myserver run-parts(/etc/cron.daily)[5034]: finished nethserver-check-nsreleaselock
/var/log/cron-20181202:Dec 1 03:34:12 myserver run-parts(/etc/cron.daily)[8279]: starting nethserver-check-nsreleaselock
/var/log/cron-20181202:Dec 1 03:34:12 myserver run-parts(/etc/cron.daily)[28579]: finished nethserver-check-nsreleaselock
Yes, that seems to be the problem.
2 Likes
davidep
(Davide Principi)
December 4, 2018, 9:46am
7
Dec 4 04:06:05 duplex /sbin/e-smith/db[22295]: /var/lib/nethserver/db/configuration: NEW sysconfig=configuration|Copyright||DefaultLanguage|en_US.utf8|NsReleaseLock|enabled
This confirm my theory: the check action runs after yum updates!
I guess those who have yum-cron automated updates enabled are affected by this bug today…
I’m moving some posts under the Bug category
1 Like
dnutan
(Marc)
December 4, 2018, 10:52am
9
Confirmed. I’d enabled automatic updates to be downloaded (not installed) and received two notification emails:
(Tue, 04 Dec 2018 04:14:17) yum update
(Tue, 04 Dec 2018 04:14:26) anacron /etc/cron.daily/nethserver-check-nsreleaselock
1 Like
davidep
(Davide Principi)
December 4, 2018, 10:55am
10
I guess it’s too late to fix it
zimny
(Zimny)
December 4, 2018, 11:01am
11
I have got exactly the same problems on my servers
and this is imap log about it
Error: Couldn’t load required plugin /usr/lib64/dovecot/lib90_antispam_plugin.so: Module is for different ABI version 2.2.ABIv10(2.2.10) (we have 2.2.ABIv36(2.2.36))
davidep
(Davide Principi)
December 4, 2018, 11:02am
12
This is a possible workaround
It is now possible to upgrade to NethServer 7.6.1810 beta with the following commands
config setprop subscription NsRelease 7.6.1810
Then
go to Software Center and run system upgrade
set the Software updates origin to “Locked” until 7.6 final has been released
Check for open issues again here: https://github.com/NethServer/dev/issues
zimny
(Zimny)
December 4, 2018, 11:21am
13
Thank you for this workaround. It’s helped back email servers (dovecot exactly because postfix is not affected by this bug).
lorcon
(Lorenzo)
December 4, 2018, 11:25am
14
We have just checked the configuration of one of servers which experienced this problem today. In the web interface it was configured to download the updates but not to installs them; but there was a crontab configuration which seemed to overrided the configuration in web interface: al 2 am of every day it was configured a cronjob which download and install the update
We perform a change in to
/etc/crontab
with
crontab -e
it do not show us the content of crontab so we used
vi /etc/crontab
that’s strange but so it is… For security we rebooted the server in order to understand if automatically our change to the crontab was overwritten by something but it was not.
davidep
(Davide Principi)
December 4, 2018, 11:27am
15
lorcon:
/etc/crontab
I’m pretty sure none of NethServer packages changes that file!
Please check /var/log/cron contents to understand what happened
lorcon
(Lorenzo)
December 4, 2018, 12:01pm
16
Well, i found out that it was a legacy of the old version of netheserver, when there were no automatic update via web interface. A coworker of mine setted up the cronjob so it now override the web interface config. We deleted the cronjob
2 Likes
davidep
(Davide Principi)
December 5, 2018, 8:48am
18
The bug is tracked here:
If it is fixed, we’ll avoid update issues when CentOS 7.7 is out.
GG_jr
(Gabriel GHEORGHIU)
December 5, 2018, 8:59am
19
No issues (on NethServer release 7.5.1804 (final) ) with this configuration!
1 Like
davidep
(Davide Principi)
December 5, 2018, 9:02am
20
Yes, only “Install updates automatically” enabled causes the problem…
1 Like
GG_jr
(Gabriel GHEORGHIU)
December 5, 2018, 9:09am
21
I never let “Install updates automatically”, enabled!
davidep
(Davide Principi)
December 5, 2018, 9:38am
22
So you surely won’t test it in production
Who wants to test the bugfix? It’s not so hard:
Install the testing package: yum install http://packages.nethserver.org/nethserver/7.6.1810/testing/x86_64/Packages/nethserver-base-3.6.0-1.1.ga2a2d19.ns7.noarch.rpm
In ns 7.5 set SW origin policy to Unlocked
Enable automatic update download+install
Wait the daily cron job
If tomorrow the system is switched to “SW policy Locked” and centos version is still at 7.5 the fix is correct. /cc @quality_team
For more info: https://github.com/NethServer/dev/issues/5665
GG_jr
(Gabriel GHEORGHIU)
December 5, 2018, 9:43am
23
This server is in production (an email server for a customer) so, you are absolutely right!
Unfortunately, I cannot make any test for now!