Авг 302017
 

Имеем систему

FreeBSD mail.**** 11.0-RELEASE-p1 FreeBSD 11.0-RELEASE-p1 #1 r308123M: Tue May 16 10:56:22 EEST 2017     slik@mail.****:/usr/obj/usr/src/sys/MAIL  amd64

Система крутиться в качестве почтового сервера предприятия.
Пришло время немного обновить систему, софт и все остальное.

При каждодневной рассілке получал список требуемого обновления софта, когда список стал приличнім, біло решено действовать.

Checking for packages with security vulnerabilities:
Database fetched: Tue Aug 29 03:44:59 EEST 2017
bind99-9.9.9P4
oniguruma5-5.9.6_1
curl-7.51.0
libgcrypt-1.7.3
openvpn-2.3.14
phpMyAdmin-4.6.4_1
zabbix32-server-3.2.3
icu-57.1,1
subversion-1.9.4
mysql55-server-5.5.53
roundcube-1.2.2,1
exim-4.87
graphite2-1.3.8
mysql55-client-5.5.53
freetype2-2.6.3
w3m-0.5.3_5
nginx-1.10.2_1,2
libevent2-2.0.22_1
sqlite3-3.14.1_1
gnutls-3.4.16
tshark-2.0.5
tiff-4.0.6_2
apache22-2.2.34: Tag: expiration_date Value: 2017-07-01
perl5-5.20.3_16: Tag: expiration_date Value: 2017-05-27
apache22-2.2.34: Tag: deprecated Value: Upstream propose EoL of apache 2.2.x during the next 12 months
perl5-5.20.3_16: Tag: deprecated Value: Support end three years after .0 release, please upgrade to a more recent version of Perl

Самій не приятній момент, єто то что сервер в работе, и недоступность его грозит…легким втіком =)

Приступаем.

[root@mail /home/slik]# pkg upgrade

Х.м…
В ответ получил следующее

Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
process with pid 1042 still holds the lock
process with pid 1042 still holds the lock
process with pid 1042 still holds the lock
process with pid 1042 still holds the lock
process with pid 1042 still holds the lock
process with pid 1042 still holds the lock
pkg: Cannot get an advisory lock on a database, it is locked by another process

Делаем kill 1042, после єтого у нас идет обновление, но єто уже другая история =)

[root@mail /tmp]# pkg upgrade
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Checking for upgrades (330 candidates): 100%
Processing candidates (330 candidates): 100%
Checking integrity... done (11 conflicting)
  - mysql56-client-5.6.36 conflicts with mysql55-client-5.5.56 on /usr/local/bin/msql2mysql
  - mysql56-client-5.6.36 conflicts with mysql55-client-5.5.53 on /usr/local/bin/msql2mysql
  - libevent-2.1.8 conflicts with libevent2-2.0.22_1 on /usr/local/bin/event_rpcgen.py
  - py27-setuptools-36.0.1 conflicts with py27-setuptools27-28.1.0 on /usr/local/lib/python2.7/site-packages/easy-install.pth.dist
  - mesa-libs-17.1.4 conflicts with libEGL-11.2.2 on /usr/local/include/EGL/egl.h
  - mesa-libs-17.1.4 conflicts with libGL-11.2.2 on /usr/local/include/GL/gl.h
  - mesa-libs-17.1.4 conflicts with gbm-11.2.2 on /usr/local/include/gbm.h
  - mesa-libs-17.1.4 conflicts with libglapi-11.2.2 on /usr/local/lib/libglapi.so
  - oniguruma6-6.4.0 conflicts with oniguruma5-5.9.6_1 on /usr/local/bin/onig-config
  - apache24-2.4.27 conflicts with apache22-2.2.34 on /usr/local/man/man1/dbmmanage.1.gz
  - apache24-2.4.27 conflicts with apache22-2.2.34 on /usr/local/man/man1/dbmmanage.1.gz
Cannot solve problem using SAT solver, trying another plan
Cannot solve problem using SAT solver, trying another plan
Cannot solve problem using SAT solver, trying another plan
Checking integrity... done (0 conflicting)
The following 221 package(s) will be affected (of 0 checked):