Re: Strange issues while upgrading ports

[Doug Barton]

On 11/27/2011 5:01 AM, Jerry wrote:
> Personally, "portmaster"
> always seems to get my ass in a sling when I have attempted to use it
> so I leave it alone. Obviously, YMMV.

As always, if you run into bugs or problems with portmaster I'm happy to
accept bug reports about it.

-- 

"We could put the whole Internet into a book."
"Too practical."

Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price.  :)  http://SupersetSolutions.com/

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Strange issues while upgrading ports

[Kaya Saman]

On 11/27/2011 03:01 PM, Jerry wrote:

On Sun, 27 Nov 2011 14:25:04 +0200
Kaya Saman articulated:


On 11/27/2011 08:03 AM, Kevin Oberman wrote:


When it has been this long, you might want to completely delete and
re-install all ports following the instructions in the portmaster
man page examples. This will assure that EVERYTHING is properly
cleaned up. No obsolete libraries, header files, data files, or
anything else. It's the 11 step process and please read the
relevant example in its entirety to make sure you don't waste too
much time. If your system has a very large number of ports
installed, consider using the -P option to use packages when they
are available.

I do see some ports that might benefit from CPU specific
optimizations. If you feel that these are important, re-install
these after you finish the basic re-installation.

I discovered in the UPDATING file that it claims the same thing:

20100409:
AFFECTS: users of lang/php5
AUTHOR: a...@freebsd.org

As of PHP 5.3, a few extensions were removed from or included into
the core
PHP5 package.  Follow the steps below to update your installation.

1) Delete the following packages (if installed):

   - php5-dbase
   - php5-ncurses
   - php5-pcre
   - php5-spl
   - php5-ming
   - php5-mhash

2) Rebuild lang/php5 and all ports that depend on it.


The only problem is how to go about it?

I mean I have quite a few web based monitoring apps (cacti, zabbix,
munin, etc) which all depend on PHP5 + apache22 so am not really sure
if running:

make deinstall on each port is wise especially since I don't want
the config files do be deleted (even though backed up) or backend
database information to be get lost either.

That was quite a while ago; however, I remember simply deinstalling
each of those ports. Then after updating the ports tree I ran
"portmanager -u -l -y -p" to update and rebuild the ports as required.
It works like a charm. I know others recommend "portupgrade" and I use
that from time to time also but it just seems to fail to update all
required ports sometimes in cases like this. Personally, "portmaster"
always seems to get my ass in a sling when I have attempted to use it
so I leave it alone. Obviously, YMMV.

BTW, if you use "portmanager" you will find a log file
"/var/log/portmanager.log" that will give you a complete list of what
it did if you should experience any problems..


Ok I got this one worked out:


Officially I want to thank Kevin Oberman for his offline help too :-)


Basically I ran:


cd /usr/ports/*/php5-*
make deinstall
make install clean


---php5 sorted out!



Then:


cd /usr/ports/www/apache22
make deinstall

make install clean - came up with errors so here's the next step:

cat Makefile | more
- check the library dependencies

cd /usr/ports/*/{each lib depend}
make deinstall
make install clean

cd /usr/ports/www/apache22
make install clean


Then ran:

portmanager -u -l -y -p


and now the only errornous ports I have are these:

skipping squid-2.7.7 /www/squid marked IGNORE reason: failed during make
skipping libltdl-2.2.6a /devel/libltdl22 marked IGNORE reason: port 
marked IGNORE
skipping gtk-2.16.6 /x11-toolkits/gtk20 marked IGNORE reason: performed 
(6) emergancy restore

skipping oss-4.2.b2000 /audio/oss until dependency gtk-2.24.6 updated
skipping zabbix-1.6.6,1 /net-mgmt/zabbix marked IGNORE reason: failed 
during make

skipping mutt-1.4.2.3_3 /mail/mutt marked IGNORE reason: failed during make


Few!!! :-D all fine and installed - now to fix the rest.


Thanks everyone for all your help

I really appreciate that even though I felt like a total noobie but hey 
this is the first time I've ever updated/upgraded a FreeBSD system. My 
nerves were a bit on edge as there are many ports installed and I was 
quite worried that I was gona loose the installed config files as linux 
is quite prone to doing.


Anyway, with everyone's patience and effort everything went more or less 
smoothly and was in fact quite painless and quick :-)



Best Regards to all.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Strange issues while upgrading ports

[Jerry]

On Sun, 27 Nov 2011 14:25:04 +0200
Kaya Saman articulated:

> On 11/27/2011 08:03 AM, Kevin Oberman wrote:
> 
> >
> > When it has been this long, you might want to completely delete and
> > re-install all ports following the instructions in the portmaster
> > man page examples. This will assure that EVERYTHING is properly
> > cleaned up. No obsolete libraries, header files, data files, or
> > anything else. It's the 11 step process and please read the
> > relevant example in its entirety to make sure you don't waste too
> > much time. If your system has a very large number of ports
> > installed, consider using the -P option to use packages when they
> > are available.
> >
> > I do see some ports that might benefit from CPU specific
> > optimizations. If you feel that these are important, re-install
> > these after you finish the basic re-installation.
> 
> I discovered in the UPDATING file that it claims the same thing:
> 
> 20100409:
>AFFECTS: users of lang/php5
>AUTHOR: a...@freebsd.org
> 
>As of PHP 5.3, a few extensions were removed from or included into 
> the core
>PHP5 package.  Follow the steps below to update your installation.
> 
>1) Delete the following packages (if installed):
> 
>   - php5-dbase
>   - php5-ncurses
>   - php5-pcre
>   - php5-spl
>   - php5-ming
>   - php5-mhash
> 
>2) Rebuild lang/php5 and all ports that depend on it.
> 
> 
> The only problem is how to go about it?
> 
> I mean I have quite a few web based monitoring apps (cacti, zabbix, 
> munin, etc) which all depend on PHP5 + apache22 so am not really sure
> if running:
> 
> make deinstall on each port is wise especially since I don't want 
> the config files do be deleted (even though backed up) or backend 
> database information to be get lost either.

That was quite a while ago; however, I remember simply deinstalling
each of those ports. Then after updating the ports tree I ran
"portmanager -u -l -y -p" to update and rebuild the ports as required.
It works like a charm. I know others recommend "portupgrade" and I use
that from time to time also but it just seems to fail to update all
required ports sometimes in cases like this. Personally, "portmaster"
always seems to get my ass in a sling when I have attempted to use it
so I leave it alone. Obviously, YMMV.

BTW, if you use "portmanager" you will find a log file
"/var/log/portmanager.log" that will give you a complete list of what
it did if you should experience any problems..

-- 
Jerry ♔

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Strange issues while upgrading ports

[Kaya Saman]

On 11/27/2011 08:03 AM, Kevin Oberman wrote:



When it has been this long, you might want to completely delete and
re-install all ports following the instructions in the portmaster man
page examples. This will assure that EVERYTHING is properly cleaned
up. No obsolete libraries, header files, data files, or anything else.
It's the 11 step process and please read the relevant example in its
entirety to make sure you don't waste too much time. If your system
has a very large number of ports installed, consider using the -P
option to use packages when they are available.

I do see some ports that might benefit from CPU specific
optimizations. If you feel that these are important, re-install these
after you finish the basic re-installation.


I discovered in the UPDATING file that it claims the same thing:

20100409:
  AFFECTS: users of lang/php5
  AUTHOR: a...@freebsd.org

  As of PHP 5.3, a few extensions were removed from or included into 
the core

  PHP5 package.  Follow the steps below to update your installation.

  1) Delete the following packages (if installed):

 - php5-dbase
 - php5-ncurses
 - php5-pcre
 - php5-spl
 - php5-ming
 - php5-mhash

  2) Rebuild lang/php5 and all ports that depend on it.


The only problem is how to go about it?

I mean I have quite a few web based monitoring apps (cacti, zabbix, 
munin, etc) which all depend on PHP5 + apache22 so am not really sure if 
running:


make deinstall on each port is wise especially since I don't want 
the config files do be deleted (even though backed up) or backend 
database information to be get lost either.

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Strange issues while upgrading ports

[Kaya Saman]

On 11/27/2011 08:03 AM, Kevin Oberman wrote:

On Sat, Nov 26, 2011 at 8:01 PM, Kaya Saman  wrote:

I tried that and it didn't help :-(

I also just performed a version upgrade to 8.2 and still get the same
errors?

After running portsnap fetch; portsnap update; then portupgrade -a I get
these errors:

** Listing the failed packages (-:ignored / *:skipped / !:failed)
- devel/automake110 (marked as IGNORE)
- devel/automake15 (marked as IGNORE)
- devel/automake19 (marked as IGNORE)
- devel/libltdl22 (marked as IGNORE)

These versions of automake are obsolete. See /usr/ports/UPDATING for
the 20101208 entry for how to deal with them.


Just taking this into account, the /usr/ports/UPDATING file claims to run:

  # portmaster -o devel/autoconf devel/autoconf268
  # portmaster -o devel/automake devel/automake111
  # portmaster -o devel/libtool devel/libtool22
  # portmaster -o devel/libltdl devel/libltdl22

However, after cd'ing to /usr/ports/ the output I get is as so:

# portmaster -o devel/autoconf devel/autoconf268

===>>> The second argument to -o can be a port in /var/db/pkg,
   or a port directory from /usr/ports

   devel/autoconf268 does not seem to be installed,
   or listed as a dependency

===>>> No valid installed port, or port directory given
===>>> Try portmaster --help


Some comments in-line, but you MUST read /us/ports/UPDATING when ports
upgrading ports, especially when it has been a long time since the
existing ports were installed.




I don't really understand how to use the /usr/ports/UPDATING file as I 
had a look for the Apache22 version that I have installed only couldn't 
find anything as it spoke about updating Apache13 to Apache20 then 
Apache22. Nothing came up with the different sub-versions of the 
Apache22 port which I have installed.



Per this: http://www.freebsd.org/doc/handbook/ports-using.html

I have run portmaster -L and am now running portmaster -a

however, on doing so my terminal now seems to be caught in a recursive 
loop under: devel/php5-spl as it's displaying the same thing over and 
over again and not seeming to make any progress???









___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Strange issues while upgrading ports

[Kevin Oberman]

On Sat, Nov 26, 2011 at 8:01 PM, Kaya Saman  wrote:
> I tried that and it didn't help :-(
>
> I also just performed a version upgrade to 8.2 and still get the same
> errors?
>
> After running portsnap fetch; portsnap update; then portupgrade -a I get
> these errors:
>
> ** Listing the failed packages (-:ignored / *:skipped / !:failed)
>    - devel/automake110 (marked as IGNORE)
>    - devel/automake15 (marked as IGNORE)
>    - devel/automake19 (marked as IGNORE)
>- devel/libltdl22 (marked as IGNORE)
These versions of automake are obsolete. See /usr/ports/UPDATING for
the 20101208 entry for how to deal with them.
>    - audio/libmpcdec (marked as IGNORE)
Also obsolete. See the 20101204 entry.
>    - multimedia/mpeg4ip-libmp4v2 (marked as IGNORE)
See 20100811
>    - archivers/xz (marked as IGNORE)
xz is now part of the base system. See 20090921 todeal with it.
>    ! www/squid (squid-2.7.7)    (linker error)
>    ! www/apache22 (apache-2.2.13)    (install error)
>    * www/mod_python3 (mod_python-3.3.1_2)
>    * lang/php5 (php5-5.2.11)
>    * databases/php5-mysql (php5-mysql-5.2.11)
>    * audio/mpg123 (mpg123-1.9.0)
>    ! mail/mutt (mutt-1.4.2.3_3)    (linker error)
>    * textproc/php5-xml (php5-xml-5.2.11)
>    * converters/php5-mbstring (php5-mbstring-5.2.11)
>    * audio/xmms2 (xmms2-0.6_1)
>    ! x11-toolkits/gtk20 (gtk-2.16.6)    (configure error)
>    * math/php5-bcmath (php5-bcmath-5.2.11)
>    * lang/php5 (php5-pcre-5.2.11)
>    * textproc/php5-simplexml (php5-simplexml-5.2.11)
>    * lang/php5 (php5-spl-5.2.11)
>    * audio/oss (oss-4.2.b2000)
>    * net-mgmt/php5-snmp (php5-snmp-5.2.11)
>    * net/php5-sockets (php5-sockets-5.2.11)
>    * databases/adodb (adodb-4.99.1)
>    * graphics/php5-gd (php5-gd-5.2.11)
>    * www/php5-session (php5-session-5.2.11)
>    * net-mgmt/cacti (cacti-0.8.7g)
>    * databases/php5-sqlite (php5-sqlite-5.2.11)
>
>
> Checking the **INDEX** this is the output:
>
> # pkg_version -Iv | grep updating
> adodb-4.99.1 <   needs updating (index has 4.99.2)
> apache-2.2.13 <   needs updating (index has 2.2.21)
> cacti-0.8.7g <   needs updating (index has 0.8.7h)
> gtk-2.16.6 <   needs updating (index has 2.24.6)
> mod_python-3.3.1_2 <   needs updating (index has 3.3.1_3)
> mpg123-1.9.0 <   needs updating (index has 1.13.4)
> mutt-1.4.2.3_3 <   needs updating (index has 1.4.2.3_6)
> oss-4.2.b2000 <   needs updating (index has 4.2.b2005)
> php5-5.2.11 <   needs updating (index has 5.3.8)
> php5-bcmath-5.2.11 <   needs updating (index has 5.3.8)
> php5-gd-5.2.11 <   needs updating (index has 5.3.8)
> php5-mbstring-5.2.11 <   needs updating (index has 5.3.8)
> php5-mysql-5.2.11 <   needs updating (index has 5.3.8)
> php5-session-5.2.11 <   needs updating (index has 5.3.8)
> php5-simplexml-5.2.11 <   needs updating (index has 5.3.8)
> php5-snmp-5.2.11 <   needs updating (index has 5.3.8)
> php5-sockets-5.2.11 <   needs updating (index has 5.3.8)
> php5-sqlite-5.2.11 <   needs updating (index has 5.3.8)
> php5-xml-5.2.11 <   needs updating (index has 5.3.8)
> squid-2.7.7 <   needs updating (index has 2.7.9_1)
> xmms2-0.6_1 <   needs updating (index has 0.7_2)
>
>
>
> # pkg_version -Iv | grep failed
> autoconf-2.62                       !   Comparison failed
> automake-1.10.1                     !   Comparison failed
> automake-1.5_5,1                    !   Comparison failed
> automake-1.9.6_3                    !   Comparison failed
> bind9-9.3.6.1.1                     !   Comparison failed
> drupal5-5.20                        !   Comparison failed
> libltdl-2.2.6a                      !   Comparison failed
> libmpcdec-1.2.6                     !   Comparison failed
> mpeg4ip-libmp4v2-1.6.1              !   Comparison failed
> php5-pcre-5.2.11                    !   Comparison failed
> php5-spl-5.2.11                     !   Comparison failed
> rsyslog-2.0.7                       !   Comparison failed
> torrentflux-2.0.b1                  !   Comparison failed
> zabbix-1.6.6,1                      !   Comparison failed
>
>
>
> Here's the new BSD version info:
>
> # uname -a
> FreeBSD Server 8.2-RELEASE-p3 FreeBSD 8.2-RELEASE-p3 #0: Tue Sep 27 18:45:57
> UTC 2011     r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
>  amd64

Some comments in-line, but you MUST read /us/ports/UPDATING when ports
upgrading ports, especially when it has been a long time since the
existing ports were installed.

When it has been this long, you might want to completely delete and
re-install all ports following the instructions in the portmaster man
page examples. This will assure that EVERYTHING is properly cleaned
up. No obsolete libraries, header files, data files, or anything else.
It's the 11 step process and please read the relevant example in its
entirety to make sure you don't waste too much time. If your system
has a very large number of ports installed, consider using the -P
option to use packages when they are available.

I do see some ports that might benefit from CPU spe

Re: Strange issues while upgrading ports

[Kaya Saman]

On 11/25/2011 09:46 PM, Chris Rees wrote:

On 25 November 2011 15:06, Julian H. Stacey  wrote:

Hi,
Kaya Saman wrote:

On 11/25/2011 02:51 PM, Julian H. Stacey wrote:

Kaya Saman wrote:

Hi,

I'm running FreeBSD version 8.0 x64 edition on my server with multiple
jails.




Can anyone help with my issues??

8.0 is too old, November 2009
http://www.freebsd.org/releases/

8.0 Is not supported.
http://www.freebsd.org/security/security.html#sup

My machine ceased to crash when I moved from 8.0 to 8.2,
I seem to recall other problems eased too.

So upgrade to at least 8.1 !

If you management are saying stay at `proven' 8.0 rather than 8.2,
think again.

It's well known that .0 releases can be problematic, which is I
recall why 8.1 has extended support (even beyond 8.2), useful for
those who don't want to keep upgrading.

Yes, 9.0-RC2 is available for test for those wanting new features,
not for you if you'r still on 8.0. One would expect less stability
from 9.0-RC2 than 8.0.&no more from 9.0 than 8.0, so go for 8.1
or 8.2 then wait for 9.1 not 9.0.

Cheers,
Julian

How is the upgrade of versions done?

I'm sorry I've never done it before; from my linux experience on Debian
at least it's a bit messy.

I found this:

http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html

So I'm guessing - backup /etc, /var, /usr/local/etc, and /usr/local/var

then do:

freebsd-update -r 8.2-RELEASE upgrade

   freebsd-update install

   shutdown -r now

freebsd-update install

#  portupgrade -f ruby
#  rm /var/db/pkg/pkgdb.db
#  portupgrade -f ruby18-bdb
#  rm /var/db/pkg/pkgdb.db /usr/ports/INDEX-*.db
#  portupgrade -af

   freebsd-update install


How will this affect my Jails though? Will I need to rebuild them also?

I mean how will I know if everything is the same as before the upgrade
but obviously just newer?

Sorry, short of time here, so in brief:
This the wrong list to ask about upgrades.
Read http://www.freebsd.org
I dont personaly keep up to date with latest fancy BSD-specific
  update scripts (as I've been doing Unix decades,&  by reflex
  make all of src/&  ports/ that I use, but certainly back up etc
  &  var first )
Others may have more time to add info, but better ask on hackers@
(or questions@ re upgrades)

I would guess jails from 8.0 would survive on 8.2, Try on a spare box.


This actually looks kinda like an INDEX issue.

# make -C /usr/ports fetchindex

should fix it.  Also, since portupgrade is unmaintained, may I suggest
getting to know portmaster

Chris


I tried that and it didn't help :-(

I also just performed a version upgrade to 8.2 and still get the same 
errors?


After running portsnap fetch; portsnap update; then portupgrade -a I get 
these errors:


** Listing the failed packages (-:ignored / *:skipped / !:failed)
- devel/automake110 (marked as IGNORE)
- devel/automake15 (marked as IGNORE)
- devel/automake19 (marked as IGNORE)
- devel/libltdl22 (marked as IGNORE)
- audio/libmpcdec (marked as IGNORE)
- multimedia/mpeg4ip-libmp4v2 (marked as IGNORE)
- archivers/xz (marked as IGNORE)
! www/squid (squid-2.7.7)(linker error)
! www/apache22 (apache-2.2.13)(install error)
* www/mod_python3 (mod_python-3.3.1_2)
* lang/php5 (php5-5.2.11)
* databases/php5-mysql (php5-mysql-5.2.11)
* audio/mpg123 (mpg123-1.9.0)
! mail/mutt (mutt-1.4.2.3_3)(linker error)
* textproc/php5-xml (php5-xml-5.2.11)
* converters/php5-mbstring (php5-mbstring-5.2.11)
* audio/xmms2 (xmms2-0.6_1)
! x11-toolkits/gtk20 (gtk-2.16.6)(configure error)
* math/php5-bcmath (php5-bcmath-5.2.11)
* lang/php5 (php5-pcre-5.2.11)
* textproc/php5-simplexml (php5-simplexml-5.2.11)
* lang/php5 (php5-spl-5.2.11)
* audio/oss (oss-4.2.b2000)
* net-mgmt/php5-snmp (php5-snmp-5.2.11)
* net/php5-sockets (php5-sockets-5.2.11)
* databases/adodb (adodb-4.99.1)
* graphics/php5-gd (php5-gd-5.2.11)
* www/php5-session (php5-session-5.2.11)
* net-mgmt/cacti (cacti-0.8.7g)
* databases/php5-sqlite (php5-sqlite-5.2.11)


Checking the **INDEX** this is the output:

# pkg_version -Iv | grep updating
adodb-4.99.1 <   needs updating (index has 4.99.2)
apache-2.2.13 <   needs updating (index has 2.2.21)
cacti-0.8.7g <   needs updating (index has 0.8.7h)
gtk-2.16.6 <   needs updating (index has 2.24.6)
mod_python-3.3.1_2 <   needs updating (index has 3.3.1_3)
mpg123-1.9.0 <   needs updating (index has 1.13.4)
mutt-1.4.2.3_3 <   needs updating (index has 1.4.2.3_6)
oss-4.2.b2000 <   needs updating (index has 4.2.b2005)
php5-5.2.11 <   needs updating (index has 5.3.8)
php5-bcmath-5.2.11 <   needs updating (index has 5.3.8)
php5-gd-5.2.11 <   needs updating (index has 5.3.8)
php5-mbstring-5.2.11 <   needs updating (index has 5.3.8)
php5-mysql-5.2.11 <   needs updating (index has 5.3.8)
php5-session-5.2.11 <   needs updating (index has 5.3.8)
php5-simplexml-5.2.11 <   needs updating (index has 5.3

Re: Strange issues while upgrading ports

[Kaya Saman]

On 11/26/2011 10:56 AM, Edward wrote:

On 11/25/11 10:14 PM, Kaya Saman wrote:

Would you also advise to upgrade my BSD 'release'?


The FreeBSD Handbook have a section covering it :
http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html

My personal experience :
http://scratching.psybermonkey.net/2009/07/freebsd-how-to-upgrade-kernel-or-base.html

*** disclosure, that's my blog.


Thank you - nice blog! :-)

Also pretty much the approach I am taking, just nice to see that the 
approach is valid and already tested and tried by more experienced people.



If so I would upgrade to 8.2 as stated in a previous posting but since
I'm running jails and many services aggregated into one machine, what's
the best way to proceed?

I'm currently just backing up /etc, /var, /usr/shared, /usr/local/etc,
/usr/local/var, and /usr/local/shared.


Don't forget /usr/jails, that's where your jails live.


Actually all my jails are custom. I have them in /mnt/zfs/jail as I run 
them from my ZFS mount. However, I guess not to loose the information 
residing in them I probably should back them up too.





Will the freebsd-upgrade tool wipe all my config files? Or will the
upgrade be seamless?

You might wanna try freebsd-update on a box with customize config files
(e.g. /etc/hosts, /etc/ssh/sshd_config or blah blah blah) to have a feel
on how mergemaster works on merging config files. It took me a few
upgrade tries to get familiar with it. In general, if you've backup the
configs in /etc&  /usr/local/etc, you can always restore the working
copy back and your services shouldn't fail :)


Unfortunately I don't have another box to test on unless I use a VM in 
VirtualBox on my notebook. Luckily I have backups now of all config file 
directories including /usr/share and /usr/local/share so I hope that I 
won't get in to deep-stuk if everything goes khabluey!


It will just take ages as I kinda run the system as a sort of mainframe 
with 7 jails and many, many services.



___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Strange issues while upgrading ports

[Edward]

On 11/25/11 10:14 PM, Kaya Saman wrote:
> Would you also advise to upgrade my BSD 'release'?
> 
The FreeBSD Handbook have a section covering it :
http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html

My personal experience :
http://scratching.psybermonkey.net/2009/07/freebsd-how-to-upgrade-kernel-or-base.html

*** disclosure, that's my blog.

> If so I would upgrade to 8.2 as stated in a previous posting but since
> I'm running jails and many services aggregated into one machine, what's
> the best way to proceed?
> 
> I'm currently just backing up /etc, /var, /usr/shared, /usr/local/etc,
> /usr/local/var, and /usr/local/shared.
> 
Don't forget /usr/jails, that's where your jails live.

> Will the freebsd-upgrade tool wipe all my config files? Or will the
> upgrade be seamless?

You might wanna try freebsd-update on a box with customize config files
(e.g. /etc/hosts, /etc/ssh/sshd_config or blah blah blah) to have a feel
on how mergemaster works on merging config files. It took me a few
upgrade tries to get familiar with it. In general, if you've backup the
configs in /etc & /usr/local/etc, you can always restore the working
copy back and your services shouldn't fail :)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Strange issues while upgrading ports

[Chris Rees]

On 25 November 2011 15:06, Julian H. Stacey  wrote:
> Hi,
> Kaya Saman wrote:
>> On 11/25/2011 02:51 PM, Julian H. Stacey wrote:
>> > Kaya Saman wrote:
>> >> Hi,
>> >>
>> >> I'm running FreeBSD version 8.0 x64 edition on my server with multiple
>> >> jails.
>> > <  Detail deleted>
>> >
>> >> Can anyone help with my issues??
>> > 8.0 is too old, November 2009
>> > http://www.freebsd.org/releases/
>> >
>> > 8.0 Is not supported.
>> > http://www.freebsd.org/security/security.html#sup
>> >
>> > My machine ceased to crash when I moved from 8.0 to 8.2,
>> > I seem to recall other problems eased too.
>> >
>> > So upgrade to at least 8.1 !
>> >
>> > If you management are saying stay at `proven' 8.0 rather than 8.2,
>> > think again.
>> >
>> > It's well known that .0 releases can be problematic, which is I
>> > recall why 8.1 has extended support (even beyond 8.2), useful for
>> > those who don't want to keep upgrading.
>> >
>> > Yes, 9.0-RC2 is available for test for those wanting new features,
>> > not for you if you'r still on 8.0. One would expect less stability
>> > from 9.0-RC2 than 8.0.&  no more from 9.0 than 8.0, so go for 8.1
>> > or 8.2 then wait for 9.1 not 9.0.
>> >
>> > Cheers,
>> > Julian
>> How is the upgrade of versions done?
>>
>> I'm sorry I've never done it before; from my linux experience on Debian
>> at least it's a bit messy.
>>
>> I found this:
>>
>> http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html
>>
>> So I'm guessing - backup /etc, /var, /usr/local/etc, and /usr/local/var
>>
>> then do:
>>
>> freebsd-update -r 8.2-RELEASE upgrade
>>
>>   freebsd-update install
>>
>>   shutdown -r now
>>
>> freebsd-update install
>>
>> #  portupgrade -f ruby
>> #  rm /var/db/pkg/pkgdb.db
>> #  portupgrade -f ruby18-bdb
>> #  rm /var/db/pkg/pkgdb.db /usr/ports/INDEX-*.db
>> #  portupgrade -af
>>
>>   freebsd-update install
>>
>>
>> How will this affect my Jails though? Will I need to rebuild them also?
>>
>> I mean how will I know if everything is the same as before the upgrade
>> but obviously just newer?
>
> Sorry, short of time here, so in brief:
> This the wrong list to ask about upgrades.
> Read http://www.freebsd.org
> I dont personaly keep up to date with latest fancy BSD-specific
>  update scripts (as I've been doing Unix decades, & by reflex
>  make all of src/ & ports/ that I use, but certainly back up etc
>  & var first )
> Others may have more time to add info, but better ask on hackers@
> (or questions@ re upgrades)
>
> I would guess jails from 8.0 would survive on 8.2, Try on a spare box.


This actually looks kinda like an INDEX issue.

# make -C /usr/ports fetchindex

should fix it.  Also, since portupgrade is unmaintained, may I suggest
getting to know portmaster

Chris
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Strange issues while upgrading ports

[Julian H. Stacey]

Hi,
Reference:
> From: Kaya Saman  
> Date: Fri, 25 Nov 2011 15:41:26 +0200 
> Message-id:   <4ecf9b06.1090...@gmail.com> 

Kaya Saman wrote:
> This is a multi-part message in MIME format.
> --080607030603050400060904
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> Content-Transfer-Encoding: 7bit
> 
> On 11/25/2011 02:51 PM, Julian H. Stacey wrote:
> > Kaya Saman wrote:
> >> Hi,
> >>
> >> I'm running FreeBSD version 8.0 x64 edition on my server with multiple
> >> jails.
> > <  Detail deleted>
> >
> >> Can anyone help with my issues??
> > 8.0 is too old, November 2009
> > http://www.freebsd.org/releases/
> >
> > 8.0 Is not supported.
> > http://www.freebsd.org/security/security.html#sup
> >
> > My machine ceased to crash when I moved from 8.0 to 8.2,
> > I seem to recall other problems eased too.
> >
> > So upgrade to at least 8.1 !
> >
> > If you management are saying stay at `proven' 8.0 rather than 8.2,
> > think again.
> >
> > It's well known that .0 releases can be problematic, which is I
> > recall why 8.1 has extended support (even beyond 8.2), useful for
> > those who don't want to keep upgrading.
> >
> > Yes, 9.0-RC2 is available for test for those wanting new features,
> > not for you if you'r still on 8.0. One would expect less stability
> > from 9.0-RC2 than 8.0.&  no more from 9.0 than 8.0, so go for 8.1
> > or 8.2 then wait for 9.1 not 9.0.
> >
> > Cheers,
> > Julian
> How is the upgrade of versions done?
> 
> I'm sorry I've never done it before; from my linux experience on Debian 
> at least it's a bit messy.
> 
> I found this:
> 
> http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html
> 
> So I'm guessing - backup /etc, /var, /usr/local/etc, and /usr/local/var
> 
> then do:
> 
> freebsd-update -r 8.2-RELEASE upgrade
> 
>   freebsd-update install
> 
>   shutdown -r now
> 
> freebsd-update install
> 
> #  portupgrade -f ruby
> #  rm /var/db/pkg/pkgdb.db
> #  portupgrade -f ruby18-bdb
> #  rm /var/db/pkg/pkgdb.db /usr/ports/INDEX-*.db
> #  portupgrade -af
> 
>   freebsd-update install
> 
> 
> How will this affect my Jails though? Will I need to rebuild them also?
> 
> I mean how will I know if everything is the same as before the upgrade 
> but obviously just newer?

Sorry, short of time here, so in brief:
This the wrong list to ask about upgrades.
Read http://www.freebsd.org 
I dont personaly keep up to date with latest fancy BSD-specific
  update scripts (as I've been doing Unix decades, & by reflex
  make all of src/ & ports/ that I use, but certainly back up etc
  & var first )
Others may have more time to add info, but better ask on hackers@
(or questions@ re upgrades)

I would guess jails from 8.0 would survive on 8.2, Try on a spare box.


> --080607030603050400060904
> Content-Type: text/html; charset=ISO-8859-1
> Content-Transfer-Encoding: 7bit

No HTML duplicates

Cheers,
Julian
-- 
Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com
 Reply below not above, cumulative like a play script, & indent with "> ".
 Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Strange issues while upgrading ports

[RW]

On Fri, 25 Nov 2011 12:14:40 +0200
Kaya Saman wrote:

> I used the:
> 
> portsnap fetch extract upgrade

I assume you mean update rather than upgrade. You don't need to run
extract and update together. You run extract the first time to
extract the full snapshot and then update subsequently. That's not your
problem though.


> 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..

It would have been more useful to see the actual output with some
context.

> # pkg_version -v | grep updating

Try running pkg_version -Iv to see if it's an INDEX problem

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Strange issues while upgrading ports

[Kaya Saman]

On 11/25/2011 04:05 PM, Daniel Nebdal wrote:

On Fri, Nov 25, 2011 at 2:56 PM, Kaya Saman  wrote:

On 11/25/2011 03:44 PM, Daniel Nebdal wrote:

On Fri, Nov 25, 2011 at 2:12 PM, Marco Beishuizenwrote:

On Fri, 25 Nov 2011, the wise Kaya Saman wrote:


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..

Did you csup your portstree first?


He used portsnap, which does the same thing.
By the way: "portsnap fetch extract update" is pointless: "extract"
gives you a clean copy of the last fetched version, and  "update"
extracts only what has changed since the last extract or update. Use
"portsnap fetch extract" once, then "portsnap fetch update" from then
on. (Or replace "fetch" with "cron" if you're doing this automatically
- it adds a random delay to not overload the servers at popular times
of the day.)


Thanks for the tip!

It's my first time updating/upgrading a FreeBSD system so any 'experienced'
advice is always valid and welcome :-)


Ah, right. :)
The nice thing with "update" is that it's much faster than "extract" -
as I'm sure you'll notice.


Would you also advise to upgrade my BSD 'release'?

If so I would upgrade to 8.2 as stated in a previous posting but since 
I'm running jails and many services aggregated into one machine, what's 
the best way to proceed?


I'm currently just backing up /etc, /var, /usr/shared, /usr/local/etc, 
/usr/local/var, and /usr/local/shared.


Will the freebsd-upgrade tool wipe all my config files? Or will the 
upgrade be seamless?

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Strange issues while upgrading ports

[Daniel Nebdal]

On Fri, Nov 25, 2011 at 2:12 PM, Marco Beishuizen  wrote:
> On Fri, 25 Nov 2011, the wise Kaya Saman wrote:
>
>> 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..
>
> Did you csup your portstree first?
>

He used portsnap, which does the same thing.
By the way: "portsnap fetch extract update" is pointless: "extract"
gives you a clean copy of the last fetched version, and  "update"
extracts only what has changed since the last extract or update. Use
"portsnap fetch extract" once, then "portsnap fetch update" from then
on. (Or replace "fetch" with "cron" if you're doing this automatically
- it adds a random delay to not overload the servers at popular times
of the day.)

-- 
Daniel Nebdal
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Strange issues while upgrading ports

[Daniel Nebdal]

On Fri, Nov 25, 2011 at 2:56 PM, Kaya Saman  wrote:
> On 11/25/2011 03:44 PM, Daniel Nebdal wrote:
>>
>> On Fri, Nov 25, 2011 at 2:12 PM, Marco Beishuizen  wrote:
>>>
>>> On Fri, 25 Nov 2011, the wise Kaya Saman wrote:
>>>
 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..
>>>
>>> Did you csup your portstree first?
>>>
>> He used portsnap, which does the same thing.
>> By the way: "portsnap fetch extract update" is pointless: "extract"
>> gives you a clean copy of the last fetched version, and  "update"
>> extracts only what has changed since the last extract or update. Use
>> "portsnap fetch extract" once, then "portsnap fetch update" from then
>> on. (Or replace "fetch" with "cron" if you're doing this automatically
>> - it adds a random delay to not overload the servers at popular times
>> of the day.)
>>
> Thanks for the tip!
>
> It's my first time updating/upgrading a FreeBSD system so any 'experienced'
> advice is always valid and welcome :-)
>

Ah, right. :)
The nice thing with "update" is that it's much faster than "extract" -
as I'm sure you'll notice.

-- 
Daniel Nebdal
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Strange issues while upgrading ports

[Kaya Saman]

On 11/25/2011 03:44 PM, Daniel Nebdal wrote:

On Fri, Nov 25, 2011 at 2:12 PM, Marco Beishuizen  wrote:

On Fri, 25 Nov 2011, the wise Kaya Saman wrote:


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..

Did you csup your portstree first?


He used portsnap, which does the same thing.
By the way: "portsnap fetch extract update" is pointless: "extract"
gives you a clean copy of the last fetched version, and  "update"
extracts only what has changed since the last extract or update. Use
"portsnap fetch extract" once, then "portsnap fetch update" from then
on. (Or replace "fetch" with "cron" if you're doing this automatically
- it adds a random delay to not overload the servers at popular times
of the day.)


Thanks for the tip!

It's my first time updating/upgrading a FreeBSD system so any 
'experienced' advice is always valid and welcome :-)

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Strange issues while upgrading ports

[Kaya Saman]

On 11/25/2011 02:51 PM, Julian H. Stacey wrote:

Kaya Saman wrote:

Hi,

I'm running FreeBSD version 8.0 x64 edition on my server with multiple
jails.

<  Detail deleted>


Can anyone help with my issues??

8.0 is too old, November 2009
http://www.freebsd.org/releases/

8.0 Is not supported.
http://www.freebsd.org/security/security.html#sup

My machine ceased to crash when I moved from 8.0 to 8.2,
I seem to recall other problems eased too.

So upgrade to at least 8.1 !

If you management are saying stay at `proven' 8.0 rather than 8.2,
think again.

It's well known that .0 releases can be problematic, which is I
recall why 8.1 has extended support (even beyond 8.2), useful for
those who don't want to keep upgrading.

Yes, 9.0-RC2 is available for test for those wanting new features,
not for you if you'r still on 8.0. One would expect less stability
from 9.0-RC2 than 8.0.&  no more from 9.0 than 8.0, so go for 8.1
or 8.2 then wait for 9.1 not 9.0.

Cheers,
Julian

How is the upgrade of versions done?

I'm sorry I've never done it before; from my linux experience on Debian 
at least it's a bit messy.


I found this:

http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html

So I'm guessing - backup /etc, /var, /usr/local/etc, and /usr/local/var

then do:

freebsd-update -r 8.2-RELEASE upgrade

 freebsd-update install

 shutdown -r now

freebsd-update install

#  portupgrade -f ruby
#  rm /var/db/pkg/pkgdb.db
#  portupgrade -f ruby18-bdb
#  rm /var/db/pkg/pkgdb.db /usr/ports/INDEX-*.db
#  portupgrade -af

 freebsd-update install


How will this affect my Jails though? Will I need to rebuild them also?

I mean how will I know if everything is the same as before the upgrade 
but obviously just newer?


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Strange issues while upgrading ports

[Marco Beishuizen]

On Fri, 25 Nov 2011, the wise Kaya Saman wrote:


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..


Did you csup your portstree first?

Regards,
Marco

--
Happy feast of the pig!
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Strange issues while upgrading ports

[Julian H. Stacey]

Kaya Saman wrote:
> Hi,
> 
> I'm running FreeBSD version 8.0 x64 edition on my server with multiple 
> jails.

< Detail deleted >

> Can anyone help with my issues??

8.0 is too old, November 2009
http://www.freebsd.org/releases/

8.0 Is not supported.
http://www.freebsd.org/security/security.html#sup

My machine ceased to crash when I moved from 8.0 to 8.2,
I seem to recall other problems eased too.

So upgrade to at least 8.1 !

If you management are saying stay at `proven' 8.0 rather than 8.2,
think again.

It's well known that .0 releases can be problematic, which is I
recall why 8.1 has extended support (even beyond 8.2), useful for
those who don't want to keep upgrading.

Yes, 9.0-RC2 is available for test for those wanting new features,
not for you if you'r still on 8.0. One would expect less stability
from 9.0-RC2 than 8.0. & no more from 9.0 than 8.0, so go for 8.1
or 8.2 then wait for 9.1 not 9.0.

Cheers,
Julian
-- 
Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com
 Reply below not above, cumulative like a play script, & indent with "> ".
 Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Strange issues while upgrading ports

[Kaya Saman]

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 r...@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  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   2230142066%/
 devfs2  2  0   100%/dev
 ZFS_POOL_1  7662907136 5955981824 170692531278%/mnt/zfs
 devfs2  2  0   100%/var/jail/named_1/dev
 devfs2  2  0   100%/var/jail/named_2/dev
 devfs2  2  0   100%/var/jail/squid/dev
 devfs2  2  0   100%/var/jail/postfix/dev
 devfs2  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
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"