Re: Shared object libc.so.5 not found

2004-01-17 Thread Matthew Seaman
On Sat, Jan 17, 2004 at 03:17:32PM +0100, Manfred Lotz wrote:
 I've set up a new 4.9 STABLE system. Now when I want to install wget
 I get 
 Shared object libc.so.5 not found
 after a while.
 
 I did a: cd /usr/ports/ftp/wget;make install
 
 Any idea what's happening?

Yes.  Somehow you've managed to install a FreeBSD 5.x version of one
of the build tools used by the ftp/wget port, and that won't run under
FreeBSD 4.x.  devel/gmake is a likely candidate -- can you run?:

% gmake --version

If that doesn't work, then you should:

# pkg_delete -f gmake-\*
# cd /usr/ports/devel/gmake
# make install

However, the problem doesn't have to be within gmake -- it could be
any of these ports:

...ports/ftp/wget:% make pretty-print-build-depends-list
This port requires package(s) expat-1.95.6_1 gettext-0.12.1 gmake-3.80_1 
libiconv-1.9.1_3 to build.

and you might have to delete and re-install those in a similar way.

Alternatively, if you're a portupgrade user you can force a
rebuild/reinstall of *everything* that the wget port depends on in one
fell swoop by:

# portupgrade -Rf ftp/wget

which should sort things out.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   26 The Paddocks
  Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614  Bucks., SL7 1TH UK


pgp0.pgp
Description: PGP signature


Re: Shared object libc.so.5 not found

2004-01-17 Thread Manfred Lotz
On Sat, 17 Jan 2004 15:58:23 +, Matthew Seaman wrote:

 On Sat, Jan 17, 2004 at 03:17:32PM +0100, Manfred Lotz wrote:
 I've set up a new 4.9 STABLE system. Now when I want to install wget I
 get
 Shared object libc.so.5 not found
 after a while.
 
 I did a: cd /usr/ports/ftp/wget;make install
 
 Any idea what's happening?
 
 Yes.  Somehow you've managed to install a FreeBSD 5.x version of one of
 the build tools used by the ftp/wget port, and that won't run under
 FreeBSD 4.x.  devel/gmake is a likely candidate -- can you run?:
 
 % gmake --version
 
 If that doesn't work, then you should:
 
 # pkg_delete -f gmake-\*
 # cd /usr/ports/devel/gmake
 # make install
 
 However, the problem doesn't have to be within gmake -- it could be any
 of these ports:
 
 ...ports/ftp/wget:% make pretty-print-build-depends-list This port
 requires package(s) expat-1.95.6_1 gettext-0.12.1 gmake-3.80_1
 libiconv-1.9.1_3 to build.
 
 and you might have to delete and re-install those in a similar way.
 
 Alternatively, if you're a portupgrade user you can force a
 rebuild/reinstall of *everything* that the wget port depends on in one
 fell swoop by:
 
 # portupgrade -Rf ftp/wget
 
 which should sort things out.
 
 
I tried it all although it didn't help. But your comments were very
valuable because they did point me to the right direction.

There was a makeinfo binary from FreeBSD 5.1 in my path which caused the
problems. This was because I have a TeXLive installation which I took over
from my FreeBSD 5.2 CURRENT system as well as I took over the ~/.zshrc
which had a PATH statement including the old FreeBSD 5.2 bin directory
of TeXLive.


Thanks a lot,
Manfred


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Odd lag/hanging issue with production ftp server - Please help AS AP!

2004-01-17 Thread Elliott Freis
I am forwarding this to this list per recommendation.


Note on recent test:  Trying to do a transfer on the public LAN off the ftp
server, I am only able to get a bursty 20k/s! down from the ftp server.
This was with nfs completely unmounted, ftping from a local drive so its not
an NFS problem.  It should get a full 2-3mb a sec at least.  It used to.  Up
is still full speed.  The machine has a Intel pro NIC, direct to a Cisco
ArrowPoint.  Both are set to 100 FD.  ifconfig_fxp2=inet 66.151.XXX.XXX
netmask 255.255.255.224 media 100baseTX

Any help GREATLY appreciated, I have exhausted all avenues I can think of,
including hardware swaps.  Here is some diag:

last pid: 49903;  load averages:  0.12,  0.20,  0.25
up 0+15:19:19  14:19:00
73 processes:  1 running, 72 sleeping
CPU states:  1.4% user,  0.0% nice, 17.1% system,  2.3% interrupt, 79.2%
idle
Mem: 24M Active, 1233M Inact, 178M Wired, 68M Cache, 163M Buf, 3600K Free
Swap: 1024M Total, 12K Used, 1024M Free

353/17120/262144 mbufs in use (current/peak/max):
271 mbufs allocated to data
82 mbufs allocated to packet headers
213/16806/65536 mbuf clusters in use (current/peak/max)
37892 Kbytes allocated to network (19% of mb_map in use)
0 requests for memory denied
0 requests for memory delayed
0 calls to protocol drain routines

Name  Mtu   Network   AddressIpkts IerrsOpkts Oerrs
Coll
fxp2  1500  Link#300:02:a5:13:fc:b5 30214691 0 22672636 0
589096
fxp2  1500  66.151.XXX.XXX  ftp 30150589 - 22683851
- -
fxp2  1500  fe80:3::202 fe80:3::202:a5ff:0 -0 -
-

  -Original Message-
 From: Elliott Freis  
 Sent: Friday, January 09, 2004 3:28 PM
 To:   '[EMAIL PROTECTED]'
 Subject:  Odd lag/hanging issue with production ftp server - Please
 help ASAP!
 
   I have been struggling with this one for over a month now.  Here is a
 quick layout of my setup:
 
 Primary FTP server:
 Compaq DL380 1.5gb ram
 FreeBSD 4.5  
 3x36gb RAID 5 drives as local boot/storage
 ProFTPd
 
 Array server for FTP:
 AMD Athlon 2200 512mb ram
 FreeBSD 4.8
 7x36gb Fiber channel drives, RAID 5 via Vinum.
 
 Both machines are connected via a cross-over cable, that has been tested
 good and swapped just in case.  The primary storage for FTP is done on the
 Fiber drives via nfs from FTP to Array server.  NFS options are -U -3.
 
 My problem is this.  As more users connect and store files, the primary
 FTP machine becomes increasingly unresponsive.  Currently, I max at about
 350 concurrent FTP connections.  The most basic test I have been doing is
 just holding down enter on an SSH session.  As you hold enter down, you
 see it visually just hang for a second or more (up to about 5 seconds
 depending on the load).  It is even worse if I spam df -k for example.
 For part of the time, it responds fine, though its randomly a second to
 multiple seconds.  In other words, it is randomly responsive and not
 responsive every 5 seconds or so.  During the hanging time, ftp sessions
 are also hung.  So you see very bursty data transfers.  Now thankfully, no
 ftp sessions drop, so we do get the data we need.  But this is a terrible
 thing to be happening to a production server.
 
  One other thing of note, this happened to me about 4-5 months ago, but a
 reboot fixed it for some reason.  So I concluded it was just a hiccup.
 But it has returned after a different reboot, and won't go away.  
 
   Any help in troubleshooting this is very appreciated!  Happy new year,
 
  -Elliott
 
 Example of enter latency (this is from a LAN connection):
 At shell prompt 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Odd lag/hanging issue with production ftp server - Please help AS AP!

2004-01-17 Thread Brad Davis
Elliott,

You might try downloading a file from the internet to locate where the
problem is. Or a different FTP server. Etc. Keep trying to narrow down
where the problem is.


Regards,
Brad

On Sat, Jan 17, 2004 at 02:24:51PM -0800, Elliott Freis wrote:
 I am forwarding this to this list per recommendation.
 
 
 Note on recent test:  Trying to do a transfer on the public LAN off the ftp
 server, I am only able to get a bursty 20k/s! down from the ftp server.
 This was with nfs completely unmounted, ftping from a local drive so its not
 an NFS problem.  It should get a full 2-3mb a sec at least.  It used to.  Up
 is still full speed.  The machine has a Intel pro NIC, direct to a Cisco
 ArrowPoint.  Both are set to 100 FD.  ifconfig_fxp2=inet 66.151.XXX.XXX
 netmask 255.255.255.224 media 100baseTX
 
 Any help GREATLY appreciated, I have exhausted all avenues I can think of,
 including hardware swaps.  Here is some diag:
 
 last pid: 49903;  load averages:  0.12,  0.20,  0.25
 up 0+15:19:19  14:19:00
 73 processes:  1 running, 72 sleeping
 CPU states:  1.4% user,  0.0% nice, 17.1% system,  2.3% interrupt, 79.2%
 idle
 Mem: 24M Active, 1233M Inact, 178M Wired, 68M Cache, 163M Buf, 3600K Free
 Swap: 1024M Total, 12K Used, 1024M Free
 
 353/17120/262144 mbufs in use (current/peak/max):
 271 mbufs allocated to data
 82 mbufs allocated to packet headers
 213/16806/65536 mbuf clusters in use (current/peak/max)
 37892 Kbytes allocated to network (19% of mb_map in use)
 0 requests for memory denied
 0 requests for memory delayed
 0 calls to protocol drain routines
 
 Name  Mtu   Network   AddressIpkts IerrsOpkts Oerrs
 Coll
 fxp2  1500  Link#300:02:a5:13:fc:b5 30214691 0 22672636 0
 589096
 fxp2  1500  66.151.XXX.XXXftp 30150589 - 22683851
 - -
 fxp2  1500  fe80:3::202 fe80:3::202:a5ff:0 -0 -
 -
 
   -Original Message-
  From:   Elliott Freis  
  Sent:   Friday, January 09, 2004 3:28 PM
  To: '[EMAIL PROTECTED]'
  Subject:Odd lag/hanging issue with production ftp server - Please
  help ASAP!
  
I have been struggling with this one for over a month now.  Here is a
  quick layout of my setup:
  
  Primary FTP server:
  Compaq DL380 1.5gb ram
  FreeBSD 4.5  
  3x36gb RAID 5 drives as local boot/storage
  ProFTPd
  
  Array server for FTP:
  AMD Athlon 2200 512mb ram
  FreeBSD 4.8
  7x36gb Fiber channel drives, RAID 5 via Vinum.
  
  Both machines are connected via a cross-over cable, that has been tested
  good and swapped just in case.  The primary storage for FTP is done on the
  Fiber drives via nfs from FTP to Array server.  NFS options are -U -3.
  
  My problem is this.  As more users connect and store files, the primary
  FTP machine becomes increasingly unresponsive.  Currently, I max at about
  350 concurrent FTP connections.  The most basic test I have been doing is
  just holding down enter on an SSH session.  As you hold enter down, you
  see it visually just hang for a second or more (up to about 5 seconds
  depending on the load).  It is even worse if I spam df -k for example.
  For part of the time, it responds fine, though its randomly a second to
  multiple seconds.  In other words, it is randomly responsive and not
  responsive every 5 seconds or so.  During the hanging time, ftp sessions
  are also hung.  So you see very bursty data transfers.  Now thankfully, no
  ftp sessions drop, so we do get the data we need.  But this is a terrible
  thing to be happening to a production server.
  
   One other thing of note, this happened to me about 4-5 months ago, but a
  reboot fixed it for some reason.  So I concluded it was just a hiccup.
  But it has returned after a different reboot, and won't go away.  
  
Any help in troubleshooting this is very appreciated!  Happy new year,
  
   -Elliott
  
  Example of enter latency (this is from a LAN connection):
  At shell prompt 
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-stable
 To unsubscribe, send any mail to [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Odd lag/hanging issue with production ftp server - Please help AS AP!

2004-01-17 Thread Matt Douhan

 Note on recent test:  Trying to do a transfer on the public LAN off the ftp
 server, I am only able to get a bursty 20k/s! down from the ftp server.
 This was with nfs completely unmounted, ftping from a local drive so its
 not an NFS problem.  It should get a full 2-3mb a sec at least.  It used
 to.  Up is still full speed.  The machine has a Intel pro NIC, direct to a
 Cisco ArrowPoint.  Both are set to 100 FD.  ifconfig_fxp2=inet
 66.151.XXX.XXX netmask 255.255.255.224 media 100baseTX

If you use mediaopt on your client you will need to also hardcode the settings 
on the arrowpoint or you may end up in trouble there with the negotiation, 
and also if you only set the speed and not the duplex hardcoded you will have 
troubles as well.

your options are, hardcode neither speed nor duplex, or hardcode both speed 
and duplex, you seem to have a mix of both and that is never a good idea.

-- 
Matt Douhan
www.fruitsalad.org
[EMAIL PROTECTED]
ping elvis
elvis is alive


pgp0.pgp
Description: signature