| All Forums |
Register |
Login |
Search |
Subscriptions |
My Profile |
Inbox |
| Tool Warehouse |
FAQs |
Resources |
Help |
Member List |
Address Book |
Logout |
|
|
newbie: pkg_add won't work correctly
|
Logged in as: Guest |
| Users viewing this topic: none |
|
Login  |
|
|
 newbie: pkg_add won't work correctly - Oct. 6, '04, 3:51:11 PM
|
|
|
brwarn
Posts: 10
Joined: Oct. 6, '04,
Status: offline
|
Hello,
I'm attempting to add my first package -- the latest version of perl. I tried in both ksh and csh using both the pkg_add ftp://ftp.interopsystems.com/pkgs/3.5/perl-current-bin.tgz command (I already installed the pkg-1.7-bin35.sh script) and pkg_add perl-current-bin.tgz after downloading the file locally.
When using the former method I get a message that tells me I can't connect to ftp.interopsystems.com. When using the latter method, I get a Segmentation fault (core dump) error.
I'm doing this as a user who is a member of the Administrator group and am running XP SP2. What am I missing in all of this?
Thanks much,
Brian
|
|
|
|
|
RE: newbie: pkg_add won't work correctly - Oct. 6, '04, 5:14:20 PM
|
|
|
breiter
Posts: 346
Joined: Jun. 14, '04,
From: Washington, DC
Status: offline
|
I believe you actually need to be "Administrator" or the pseudo-root account of Interix, not just a member of the Administrators group. You can become Administrator by using su and providing the password for the Administrator (root) account.
Here's what this looks like from csh/tcsh. (On my computer Administrator is renamed to root using local policy.):
% whoami
breiter
% su
Password:
> whoami
root
> pkg_add ftp://ftp.interopsystems.com/pkgs/3.5/perl-current-bin.tgz
> exit
exit
% whoami
breiter
%
< Message edited by breiter -- Oct. 6, '04, 5:14:49 PM >
|
|
|
|
|
RE: newbie: pkg_add won't work correctly - Oct. 6, '04, 6:35:05 PM
|
|
|
brwarn
Posts: 10
Joined: Oct. 6, '04,
Status: offline
|
Here's the output (both STDOUT and STDERR) when I try this as Administrator (I'm assuming that I don't have to actually be identified as root using the policy that you mentioned):
% pkg_add ftp://ftp.interopsystems.com/pkgs/3.5/perl-current.bin.tgz
>>> ftp -o - ftp://ftp.interopsystems.com/pkgs/3.5/perl-current.bin.tgz
ftp: socket: Network is down
ftp: Can't connect or login to host `ftp.interopsystems.com'
gzip: stdin: unexpected end of file
tar: End of archive volume 1 reached
tar: Sorry, unable to determine archive format.
>>> ftp -A -o - ftp://ftp.interopsystems.com/pkgs/3.5/perl-current.bin.tgz
ftp: socket: Network is down
ftp: Can't connect or login to host `ftp.interopsystems.com'
gzip: stdin: unexpected end of file
tar: End of archive volume 1 reached
tar: Sorry, unable to determine archive format.
>>> ftp -A -o - ftp://ftp.interopsystems.com/pkgs/3.5/perl-current.bin.tgz
ftp: socket: Network is down
ftp: Can't connect or login to host `ftp.interopsystems.com'
gzip: stdin: unexpected end of file
tar: End of archive volume 1 reached
tar: Sorry, unable to determine archive format.
>>> ftp -A -o - ftp://ftp.interopsystems.com/pkgs/3.5/perl-current.bin.tgz
ftp: socket: Network is down
ftp: Can't connect or login to host `ftp.interopsystems.com'
gzip: stdin: unexpected end of file
tar: End of archive volume 1 reached
tar: Sorry, unable to determine archive format.
>>> ftp -A -o - ftp://ftp.interopsystems.com/pkgs/3.5/perl-current.bin.tgz
ftp: socket: Network is down
ftp: Can't connect or login to host `ftp.interopsystems.com'
gzip: stdin: unexpected end of file
tar: End of archive volume 1 reached
tar: Sorry, unable to determine archive format.
pkg_add(perl-current.bin): unable to open table of contents file `+CONTENTS' - not a package?
|
|
|
|
|
RE: newbie: pkg_add won't work correctly - Oct. 6, '04, 7:35:08 PM
|
|
|
Rodney
Posts: 3728
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
For using pkg_add you can be Administrator or a member of the Administrators group.
(That is from version 1.3 and up; the current version is 1.7.X).
Which shell you use (csh or ksh) doesn't matter.
The repeated tries show the same error happening.
I'm guessing that you're behind a firewall. And that to do HTTP
you go through a http proxy. And that in downloading the Perl package
you did it with HTTP (a web browser). Yes?
Do you have an ftp proxy set up? This would be easiest.
|
|
|
|
|
RE: newbie: pkg_add won't work correctly - Oct. 6, '04, 10:10:21 PM
|
|
|
brwarn
Posts: 10
Joined: Oct. 6, '04,
Status: offline
|
the machine is behind the router/firewall I have set up here at home. I'll go look at the router's documentation to see about setting up the ftp proxy.
|
|
|
|
|
RE: newbie: pkg_add won't work correctly - Oct. 6, '04, 10:31:57 PM
|
|
|
breiter
Posts: 346
Joined: Jun. 14, '04,
From: Washington, DC
Status: offline
|
Hmm. The problem may be that your router doesn't do a great job with NAT. FTP uses two ports not just a reciprical channel like HTTP
Here's a detailed explanation of the problems with NAT and FTP:
http://www.ncftp.com/ncftpd/doc/misc/ftp_and_firewalls.html
Does FTP work for your computer at all? Can you connect to ftp.interopsystems.com with ftp(1)?
If ftp(1) doesn't work then we have found the problem. The simplest thing to do will be to follow Rodney's advice and download the packages over HTTP and then use pkg_add with the file in your filesystem.
Getting FTP to work might be tough. You can check your documentation. There might be a solution. You might also check to see if there is a firmware upgrade available for your router.
|
|
|
|
|
RE: newbie: pkg_add won't work correctly - Oct. 7, '04, 3:27:37 PM
|
|
|
brwarn
Posts: 10
Joined: Oct. 6, '04,
Status: offline
|
I'm using a Linksys router. Any known issues with them? Also, I can FTP down with no problem. I did try to install the package after ftp'ing it to my machine and had the same output as I indicated earlier.
|
|
|
|
|
RE: newbie: pkg_add won't work correctly - Oct. 7, '04, 3:40:48 PM
|
|
|
Rodney
Posts: 3728
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
Each package will have between zero and more dependencies on other packages.
The depended upon packages are ones that are used by several others. The
approach is modular so a particular amount of functionality needs to only
be installed once. So if a depended up package already is installed it makes
the primary package smaller and faster to install. It can also make updates
easier. This shows up as you install more packages.
> I'm using a Linksys router. Any known issues with them?
I don't know.
> Also, I can FTP down with no problem.
Using what to do the FTP? Were you using the Interix ftp or something else?
>I did try to install the package after ftp'ing it to my machine and had the same output as I indicated earlier.
The installer was reaching out to get the depended upon packages.
You can get the depended upon packages by ftp and place them in the same
directory that you have the Perl package. Then pkg_add will see them.
From the ftp site, for Perl, the depended upon packages are:
env_path_local-1.0.1-bin
env_manpath_localshare-1.0.1-bin
env_ldlibrarypath_local-1.0.1-bin
|
|
|
|
|
RE: newbie: pkg_add won't work correctly - Oct. 7, '04, 8:52:22 PM
|
|
|
breiter
Posts: 346
Joined: Jun. 14, '04,
From: Washington, DC
Status: offline
|
quote:
I'm using a Linksys router. Any known issues with them?
As a matter of fact I have a friend who has had no end of quirky problems with a Linksys router and 80.11B/G access point combo device. He is using it with Comcast cable Internet. He was intermittently unable to access FTP sites. I don't honestly understand why. However, the one thing that consistently helped him was to (temporarily) disable the Windows XP firewall.
I also know that there is some compatibility problem between Dell True-mobile drivers and Linksys wireless devices that is solved by new drivers. I would also look for a firmware upgrade from Linksys.
My colleague upgraded to XP SP2, upgraded his firmware on the router and wireless NIC drivers on his computers. (He also happens to have moved to a new house, but still with Comcast.) He reports that his problems with FTP have cleared up (though his Linksys router is still somewhat flakey in general). He no longer has to disable his firewall to get FTP to work.
I can't honestly explain why that ever worked.
quote:
Also, I can FTP down with no problem.
Just to clarify Rodney's question. Have you tried the FTP client from an Interix session? The question is highly relevant because pkg_add uses ftp(1) in Interix to perform the download. Try something like this:
% /usr/bin/ftp ftp.interopsystems.com
Connected to ftp.interopsystems.com.
220 ProFTPD 1.2.9 Server (Interop Systems FTP Server 1) [ftp.interopsystems.com]
Name (ftp.interopsystems.com:JOHNGALT+breiter): anonymous
331 Anonymous login ok, send your complete email address as your password.
Password:
230 Anonymous access granted, restrictions apply.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp> quit
221 Goodbye.
%
(You don't strictly need the whole path, but when I search pkg_add using
strings /usr/local/bin/pkg_add | grep "ftp" I see that it calls /usr/bin/ftp explicitly. So using that full path ensures that you are testing the same ftp that pkg_add uses.)
Totally unrelated to your problem, but an FTP issue. I have experienced great difficulty accessing WS-FTP servers that one of my clients uses. NcFTP in Interix works just fine, but nothing else except the WS-FTP Pro Windows client can connect to those ****ing WS-FTP servers.
< Message edited by breiter -- Oct. 7, '04, 8:53:35 PM >
|
|
|
|
|
RE: newbie: pkg_add won't work correctly - Oct. 10, '04, 1:02:31 AM
|
|
|
brwarn
Posts: 10
Joined: Oct. 6, '04,
Status: offline
|
quote:
ORIGINAL: breiter
quote:
As a matter of fact I have a friend who has had no end of quirky problems with a Linksys router and 80.11B/G access point combo device. He is using it with Comcast cable Internet. He was intermittently unable to access FTP sites. I don't honestly understand why. However, the one thing that consistently helped him was to (temporarily) disable the Windows XP firewall.
I also know that there is some compatibility problem between Dell True-mobile drivers and Linksys wireless devices that is solved by new drivers. I would also look for a firmware upgrade from Linksys.
My colleague upgraded to XP SP2, upgraded his firmware on the router and wireless NIC drivers on his computers. (He also happens to have moved to a new house, but still with Comcast.) He reports that his problems with FTP have cleared up (though his Linksys router is still somewhat flakey in general). He no longer has to disable his firewall to get FTP to work.
I can't honestly explain why that ever worked.
I verified that I have the most current driver for the Dell WLAN adapter and the latest firmware for the Linksys WRT55AG router that I'm using, so hopefully that's not the reason. There is, however, a newer driver for the adapter but apparently it's not approved for use in the US or Japan (I'm in the former locale).
quote:
Just to clarify Rodney's question. Have you tried the FTP client from an Interix session? The question is highly relevant because pkg_add uses ftp(1) in Interix to perform the download. Try something like this:
% /usr/bin/ftp ftp.interopsystems.com
Connected to ftp.interopsystems.com.
220 ProFTPD 1.2.9 Server (Interop Systems FTP Server 1) [ftp.interopsystems.com]
Name (ftp.interopsystems.com:JOHNGALT+breiter): anonymous
331 Anonymous login ok, send your complete email address as your password.
Password:
230 Anonymous access granted, restrictions apply.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp> quit
221 Goodbye.
%
(You don't strictly need the whole path, but when I search pkg_add using
strings /usr/local/bin/pkg_add | grep "ftp" I see that it calls /usr/bin/ftp explicitly. So using that full path ensures that you are testing the same ftp that pkg_add uses.)
Yes, I'm using the Interix ftp at /usr/bin/ftp. The output is:
$ ftp ftp.interopsystems.com
ftp: socket: Network is down
ftp>
I tried other ftp sites with similar results.
|
|
|
|
|
RE: newbie: pkg_add won't work correctly - Oct. 10, '04, 1:04:09 AM
|
|
|
brwarn
Posts: 10
Joined: Oct. 6, '04,
Status: offline
|
I should have added to my last that the Windows FTP command works just fine.
|
|
|
|
|
RE: newbie: pkg_add won't work correctly - Oct. 10, '04, 1:25:37 AM
|
|
|
Rodney
Posts: 3728
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
What is the content of your "/etc/resolv.conf" file ?
If you do an "nslookup ftp.interopsystems.com" does it give a result?
|
|
|
|
|
RE: newbie: pkg_add won't work correctly - Oct. 10, '04, 9:48:39 PM
|
|
|
brwarn
Posts: 10
Joined: Oct. 6, '04,
Status: offline
|
quote:
ORIGINAL: Rodney
What is the content of your "/etc/resolv.conf" file ?
If you do an "nslookup ftp.interopsystems.com" does it give a result?
resolv.conf is:
# This file was automatically generated on Fri Oct 1 15:35:43 PDT 2004
#
search
nameserver 216.39.128.2
lookup file bind
nslookup ftp.interopsystems.com produces:
*** Can't find server name for address 216.39.128.2: No response from server
*** Default servers are not available
|
|
|
|
 RE: newbie: pkg_add won't work correctly - Oct. 10, '04, 9:58:35 PM
|
|
|
breiter
Posts: 346
Joined: Jun. 14, '04,
From: Washington, DC
Status: offline
|
Looks like we have found the problem. From CMD or an Interix shell issue the command "ipconfig /all" (sans quotes) and look at the DNS Server list. You want to edit /etc/resolv.conf to match those servers.
For exampe my local DNS search suffix is wolfereiter.priv and these are my DNS Servers listed from ipconfig /all:
DNS Servers . . . . . . . . . . . : 10.5.1.11
199.45.32.43
199.43.32.38
My resolv.conf looks like this:
search wolfereiter.priv
nameserver 10.5.1.11 199.45.32.43 199.45.32.38
lookup file bind
Once your resov.conf matches your DNS servers, you should be in good shape.
I find this to be an irritation myself, because the DNS servers can change and are usually handed out by DHCP. If we're luck the great and powerful Rodney :) will tell us the magic pixie dust to spinkle that automatically update resolv.conf when DHCP updates the DNS servers.
< Message edited by breiter -- Oct. 10, '04, 9:59:03 PM >
|
|
|
|
|
RE: newbie: pkg_add won't work correctly - Oct. 13, '04, 3:06:36 PM
|
|
|
brwarn
Posts: 10
Joined: Oct. 6, '04,
Status: offline
|
quote:
Looks like we have found the problem. From CMD or an Interix shell issue the command "ipconfig /all" (sans quotes) and look at the DNS Server list. You want to edit /etc/resolv.conf to match those servers.
For exampe my local DNS search suffix is wolfereiter.priv and these are my DNS Servers listed from ipconfig /all:
DNS Servers . . . . . . . . . . . : 10.5.1.11
199.45.32.43
199.43.32.38
My resolv.conf looks like this:
search wolfereiter.priv
nameserver 10.5.1.11 199.45.32.43 199.45.32.38
lookup file bind
Once your resov.conf matches your DNS servers, you should be in good shape.
I find this to be an irritation myself, because the DNS servers can change and are usually handed out by DHCP. If we're luck the great and powerful Rodney :) will tell us the magic pixie dust to spinkle that automatically update resolv.conf when DHCP updates the DNS servers.
I tried this to no avail. Just to see what happens with cygwin tools, I uninstalled SFU and loaded up the cygwin packages. All of them work fine. I'm thinking now that the problem lies somewhere in my McAfee programs since I'm having similar 'network dead/network down' issues when I attempt to use the Windows version of Apache 2. I think I'll post a new thread here and see if anyone has any experience/problems with McAfee VirusScan, Personal Firewall, or Privacy Service and SFU and getting them all to play nice.
|
|
|
|
 RE: newbie: pkg_add won't work correctly - Oct. 15, '04, 3:19:50 PM
|
|
|
breiter
Posts: 346
Joined: Jun. 14, '04,
From: Washington, DC
Status: offline
|
I think this is the McAffee firewall getting the better of you.
The thing about FTP is that there is a control channel and a data channel. The control channel is TCP 21 (generally) but the data channel is another story.
Here are some possible scenarious to check out. Netstat should be some help in figuring this out.
The McAfee firewall is blocking access by unregistered applications to TCP 21 outbound. Symptoms: Interix ftp gives you a message something like the server doesn't exist. You can also try telnet ftp.interopsystems.com 21 from Interix to trouble
or
The FTP client issues a PORT command and starts listening on a random TCP socket. The server then connects to that port (yes on the CLIENT!) from TCP 20, but McAfee firewall and Linksys router are both preventing the client from serving a TCP port up to the FTP server. So Really, this isn't an option, only PASV is going to work.
or
The FTP client issues a PASV command and the server responds with a random TCP port to connect for data. The FTP client connects to the random data port and exchanges data on a recipricol connection. For this to fail, the McAfee firewall would have to be blocking outbound connections. Symptoms: you can log in with Interix ftp but issuing an ls command fails.
If you want to troubleshoot with telnet, you will need to open 2 Interix console windows, one for the control session and the other for the data session.
Control Session:
% telnet ftp.interopsystems.com 21
Trying 64.235.106.194...
Connected to ftp.interopsystems.com.
Escape character is '^]'.
220 ProFTPD 1.2.9 Server (Interop Systems FTP Server 1) [ftp.interopsystems.com]
USER anonymous
331 Anonymous login ok, send your complete email address as your password.
PASS
230 Anonymous access granted, restrictions apply.
PASV
227 Entering Passive Mode (64,235,106,194,7,123)
When you entered the PASV command the server responded with its IP and the port to connect to. The last two numbers are the port: 7*256 + 123 = 1915
So now for the data session:
% telnet ftp.interopsystems.com 1915
Trying 64.235.106.194...
Connected to ftp.interopsystems.com.
Escape character is '^]'.
We have a data connection. So lets go back to the control session and do something:
LIST
150 Opening ASCII mode data connection for file list
226 Transfer complete.
Now in the Data window you should get
drwxr-xr-x 2 ftp interop 80 Jan 31 2004 Japan
drwxr-xr-x 11 ftp interop 251 Feb 10 2004 Win32
drwxr-xr-x 4 ftp interop 175 Feb 11 2004 beta
drwxr-xr-x 2 ftp interop 35 Feb 1 2004 bin
drwxrwxrwx 2 ftp interop 59 Jun 16 05:50 interop
drwxr-xr-x 9 ftp interop 211 Jul 6 13:22 pkgs
drwxr-xr-x 5 ftp interop 455 Sep 13 04:01 pub
drwxr-xr-x 150 ftp interop 3533 Oct 6 06:34 src
drwx-w--w- 2 ftp interop 897 Oct 12 02:21 uploads
Connection closed by foreign host.
%
Back to the control session, we can log out now:
QUIT
221
Connection closed by foreign host.
%
You should be able to home in on just where the problem occurs and fix the firewall settings by running through this excercise with telnet. Good luck.
|
|
|
|
|
RE: newbie: pkg_add won't work correctly - Oct. 29, '04, 6:16:20 PM
|
|
|
Daoenti
Posts: 1
Joined: Oct. 29, '04,
Status: offline
|
quote:
ORIGINAL: brwarn
I tried this to no avail. Just to see what happens with cygwin tools, I uninstalled SFU and loaded up the cygwin packages. All of them work fine. I'm thinking now that the problem lies somewhere in my McAfee programs since I'm having similar 'network dead/network down' issues when I attempt to use the Windows version of Apache 2. I think I'll post a new thread here and see if anyone has any experience/problems with McAfee VirusScan, Personal Firewall, or Privacy Service and SFU and getting them all to play nice.
brwarn,
Did you by chance come up with any answer to this? I'm running into the exact same issue myself. /etc/resolv.conf is correct and matches "ipconfig /all" output, nslookup from a CMD.exe window work just fine, but from within the ksh (or bash) environment they fail with the same errors you were seeing above.
The only difference in our situation is that I am behind a hardware firewall (Watchguard Firebox X700), however as I mentioned even this box can resolve DNS outside of the SFU environment (as well as the four other boxes I have sitting here with the exact same resolv.conf information, just varying platforms). Networking in general seems to be okay as I can ping other boxes behind the firewall without issue (firewall drops ICMP so there's no way to test if I can get past it).
I haven't tried cygwin yet to see if it has the same issues, I was hoping to keep it off of this machine as I really like the SFU and Interop Tools.
I'm sure it's just a configuration issue somewhere, but a couple hours of beating my head against the wall isn't helping me find it. Any info you may have come up with during your further troubleshooting that may help would be greatly appreciated.
Thanks
|
|
|
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
|
 Locked w/ New Messages |
 Locked w/o New Messages |
|
 Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
|
|
Printable Version
