Date: Tue, 25 Apr 2000 14:50:47 -0500 From: Glenn Johnson <glennpj@bayouhome.net> To: Marcel Moolenaar <marcel@cup.hp.com> Cc: freebsd-emulation@FreeBSD.ORG Subject: Re: linux_kdump of failing Linux program Message-ID: <20000425145047.A17871@node1.cluster.srrc.usda.gov> In-Reply-To: <3905CCB1.B9D231CF@cup.hp.com>; from marcel@cup.hp.com on Tue, Apr 25, 2000 at 09:49:53AM -0700 References: <20000425000641.A939@gforce.johnson.home> <3905CCB1.B9D231CF@cup.hp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 25, 2000 at 09:49:53AM -0700, Marcel Moolenaar wrote:
> Glenn Johnson wrote:
>
> > I have attached a ktrace file, parsed with linux_kdump that I
> > generated from a failing linux program. Unfortunately, I am not a
> > skilled programmer. The only thing I can make of it is that there is
> > a problem with linux_socket calls.
>
> The trace tells me that linux_socket is working fine but that the
> server has dropped the connection...
Thanks for the reply.
The server is the program that I referred to as failing. I set up a
linux box today to verify that the program does work under linux. So,
with FreeBSD running the client and Linux running the server, it
works. The server program is an RPC daemon process that authenticates
via rhosts. I can rsh between the hosts just fine but it seems that the
RPC process can not authenticate. So I am pretty sure it is something
going on in the linux layer of FreeBSD. I have some more debug info that
hopefully will be useful.
Below is some debug output from the client that is trying to connect.
-----
rem_bmin_status: host = node5, user = glenn,
rem_bmin_status: job = mmodtmp
my_clnt_create
helper_rem_host_access:
client user name = glenn
brd remote user name = glenn
brd client user name = glenn
CLIENT: rem host access failed: RPC: Unable to receive; errno = Connection reset by peer
Status: Access denied
executable : bmin
remote host : node5
remote login : glenn
job name : mmodtmp
-----
... and here is debug output from the server program.
-----
Apr 25 14:29:29 node5 bminrd[9479]: : debug is ON
Apr 25 14:29:29 node5 bminrd[9479]: : HOME=/
Apr 25 14:29:29 node5 bminrd[9479]: : PATH=/root/bin:/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin:/sbin:/usr/sbin:/usr/local/sbin:/usr/opt/bin:/usr/opt/cambridge/bin
Apr 25 14:29:29 node5 bminrd[9479]: : inetd_dummy=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Apr 25 14:29:29 node5 bminrd[9479]: : MAIL=/var/mail/root
Apr 25 14:29:29 node5 bminrd[9479]: : BLOCKSIZE=K
Apr 25 14:29:29 node5 bminrd[9479]: : FTP_PASSIVE_MODE=YES
Apr 25 14:29:29 node5 bminrd[9479]: : ----------------
Apr 25 14:29:29 node5 bminrd[9479]: : total vars: 7
Apr 25 14:29:29 node5 bminrd[9479]: : rc vars: 0
Apr 25 14:29:29 node5 bminrd[9479]: : other vars: 2
Apr 25 14:29:29 node5 bminrd[9479]: : HOME=/
Apr 25 14:29:29 node5 bminrd[9479]: : PATH=/root/bin:/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin:/sbin:/usr/sbin:/usr/local/sbin:/usr/opt/bin:/usr/opt/cambridge/bin
Apr 25 14:29:29 node5 bminrd[9479]: : inetd_dummy=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Apr 25 14:29:29 node5 bminrd[9479]: : MAIL=/var/mail/root
Apr 25 14:29:29 node5 bminrd[9479]: : BLOCKSIZE=K
Apr 25 14:29:29 node5 bminrd[9479]: : FTP_PASSIVE_MODE=YES
Apr 25 14:29:29 node5 bminrd[9479]: : BATCH_ROOT=/usr/opt/macromodel/mmod70-LINUX-O/run/mmdat
Apr 25 14:29:29 node5 bminrd[9479]: : MMEXECDIR=/usr/opt/macromodel/mmod70-LINUX-O/run/exec/
Apr 25 14:29:29 node5 bminrd[9479]: : ================
Apr 25 14:29:29 node5 bminrd[9479]: : [9479]: argv[0]: bminrd
Apr 25 14:29:29 node5 bminrd[9479]: : [9479]: argv[1]: /usr/opt/macromodel/mmod70-LINUX-O/run/exec/
Apr 25 14:29:29 node5 bminrd[9479]: : [9479]: argv[2]: /usr/opt/macromodel/mmod70-LINUX-O/run/mmdat
Apr 25 14:29:29 node5 bminrd[9479]: : [9479]: argv[3]: debug
Apr 25 14:29:29 node5 bminrd[9479]: : svctcp_create succeeded
Apr 25 14:29:29 node5 bminrd[9479]: : entering svc_run
-----
The server debug output looks the same when run from Linux so it seems
that the binary is launching OK. It is the communication that is
breaking, apparently due to an inability to authenticate. I set up a
hosts.equiv file in /compat/linux/etc but that did not help.
--
Glenn Johnson
USDA, ARS, SRRC Phone: (504) 286-4252
New Orleans, LA 70124 e-mail: gjohnson@nola.srrc.usda.gov
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-emulation" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000425145047.A17871>