Date: Fri, 25 Nov 2011 12:14:40 +0200 From: Kaya Saman <kayasaman@gmail.com> To: ports@freebsd.org Subject: Strange issues while upgrading ports Message-ID: <4ECF6A90.9020906@gmail.com>
next in thread | raw e-mail | index | archive | help
Hi,
I'm running FreeBSD version 8.0 x64 edition on my server with multiple
jails.
#uname -a
FreeBSD Server 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:02:08
UTC 2009 root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
A few weeks back I performed a portupgrade on all my installed ports for
the / root filesystem (not jails).
I used the:
portsnap fetch extract upgrade
command in order to get the latest editions of each port.
Then ran portupgrade -a
for some weird reason the packages listed below didn't get upgraded;
upon the error output 'portupgrade' was trying to replace the port with
the same version: eg. apache-2.2.13 error came up with the fact that
apache-2.2.13 was to be installed again but was already installed so I
needed to run: make deinstall; make install; make clean in order to
re-install apache22......
# pkg_version -v | grep updating
adodb-4.99.1 < needs updating (port has 4.99.2)
apache-2.2.13 < needs updating (port has 2.2.21)
cacti-0.8.7g < needs updating (port has 0.8.7h)
curl-7.20.1 < needs updating (port has 7.21.3_2)
drupal5-5.20 < needs updating (port has 5.22)
gtk-2.16.6 < needs updating (port has 2.24.6)
libltdl-2.2.6a < needs updating (port has 2.2.6b)
mod_python-3.3.1_2 < needs updating (port has 3.3.1_3)
mpg123-1.9.0 < needs updating (port has 1.13.4)
mutt-1.4.2.3_3 < needs updating (port has 1.4.2.3_6)
oss-4.2.b2000 < needs updating (port has 4.2.b2005)
php5-5.2.11 < needs updating (port has 5.3.8)
php5-bcmath-5.2.11 < needs updating (port has 5.3.8)
php5-gd-5.2.11 < needs updating (port has 5.3.8)
php5-mbstring-5.2.11 < needs updating (port has 5.3.8)
php5-mysql-5.2.11 < needs updating (port has 5.3.8)
php5-pcre-5.2.11 < needs updating (port has 5.3.8)
php5-session-5.2.11 < needs updating (port has 5.3.8)
php5-simplexml-5.2.11 < needs updating (port has 5.3.8)
php5-snmp-5.2.11 < needs updating (port has 5.3.8)
php5-sockets-5.2.11 < needs updating (port has 5.3.8)
php5-spl-5.2.11 < needs updating (port has 5.3.8)
php5-sqlite-5.2.11 < needs updating (port has 5.3.8)
php5-xml-5.2.11 < needs updating (port has 5.3.8)
squid-2.7.7 < needs updating (port has 2.7.9_1)
xmms2-0.6_1 < needs updating (port has 0.7_2)
I really can't work out why the versions specified from pkg_version -v
are not in my ports tree even with updating it with the latest versions??
Additionally I have an issue with Munin and Logwatch since the upgrade
in that Munin comes up with this error in /var/log/messages:
Nov 25 12:03:03 <user.notice> Server kernel: <6>pid 72181 (perl), uid
1001: exited on signal 11
(UID of Munin is 1001), and no data is generated in the graphs.
Logwatch doesn't output the full information anymore:
################### Logwatch 7.4.0 (03/01/11) ####################
Processing Initiated: Fri Nov 25 04:02:02 2011
Date Range Processed: yesterday
( 2011-Nov-24 )
Period is day.
Detail Level of Output: 10
Type of Output/Format: mail / text
Logfiles for Host: Server
##################################################################
--------------------- Disk Space Begin ------------------------
Filesystem 512-blocks Used Avail Capacity Mounted on
/dev/ad4s1a 71079512 43091732 22301420 66% /
devfs 2 2 0 100% /dev
ZFS_POOL_1 7662907136 5955981824 1706925312 78% /mnt/zfs
devfs 2 2 0 100% /var/jail/named_1/dev
devfs 2 2 0 100% /var/jail/named_2/dev
devfs 2 2 0 100% /var/jail/squid/dev
devfs 2 2 0 100% /var/jail/postfix/dev
devfs 2 2 0 100% /mnt/zfs/jail/imap/dev
devfs => 100% Used. Warning. Disk Filling up.
devfs => 100% Used. Warning. Disk Filling up.
devfs => 100% Used. Warning. Disk Filling up.
devfs => 100% Used. Warning. Disk Filling up.
devfs => 100% Used. Warning. Disk Filling up.
devfs => 100% Used. Warning. Disk Filling up.
---------------------- Disk Space End -------------------------
###################### Logwatch End #########################
and instead just shows the above.
I'm guessing there's a problem with Perl reading the logfiles hence the
fact that it's mentioned in Munin's error log in Messages and the fact
that logwatch is basically a Perl script.
Can anyone help with my issues??
Thanks.
Kaya
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4ECF6A90.9020906>