On 02/04/2017 05:45 PM, Philip Guenther wrote:
On Sat, 4 Feb 2017, jungle boogie wrote:
What's happening here?
$ doas pkg_add -u
Error from http://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/amd64/
ftp: connect: Invalid argument
Running that under ktrace -i might help see the problem, ala
doas ktrace -i pkg_add -u
then kdump | less and look for a failed connect call. Should be able to
search for "connect -1 errno" and then go backwards to see the connect()
call and the sockaddr passed to it.
Is this it?
"Trying 129.128.5.191...
"
80377 ftp RET write 24/0x18
80377 ftp CALL kbind(0x7f7fffff1128,24,0x2cca07dce05ae2e3)
80377 ftp RET kbind 0
80377 ftp CALL socket(AF_INET,0x1<SOCK_STREAM>,0x6)
80377 ftp RET socket 3
80377 ftp CALL kbind(0x7f7fffff1128,24,0x2cca07dce05ae2e3)
80377 ftp RET kbind 0
80377 ftp CALL connect(3,0xaf766dd0bf0,16)
80377 ftp STRU struct sockaddr { AF_INET, 129.128.5.191:80 }
80377 ftp RET connect -1 errno 22 Invalid argument
80377 ftp CALL kbind(0x7f7fffff1128,24,0x2cca07dce05ae2e3)
80377 ftp RET kbind 0
80377 ftp CALL close(3)
80377 ftp RET close 0
80377 ftp CALL kbind(0x7f7fffff1128,24,0x2cca07dce05ae2e3)
80377 ftp RET kbind 0
80377 ftp CALL kbind(0x7f7fffff1128,24,0x2cca07dce05ae2e3)
80377 ftp RET kbind 0
80377 ftp CALL write(2,0xaf79ce13000,0x1f)
80377 ftp GIO fd 2 wrote 31 bytes
"ftp: connect: Invalid argument
"
Philip Guenther
