Messages in this thread | | | Date | Sat, 27 Mar 1999 17:04:46 -0600 (CST) | From | Matthew Vanecek <> | Subject | Re: smbfs still timing out |
| |
On 27 Mar, Michael H. Warfield spewed forth: :: mev0003@unt.edu enscribed thusly: :: > On 26 Mar, Eloy A. Paris spewed forth: :: > :: I have seen this here too, and also when doing an ls on the root :: :: Ok... That keeps me from running down after a wild goose chase. :: It's not the password cache then... ::
Ok, this is with the PASSWD env. variable set:
Mar 27 14:16:37 reliant kernel: smb_trans2_request: result=-32, setting invalid Mar 27 14:16:37 reliant kernel: smb_retry: new pid=16508, generation=3
Mar 27 16:53:27 reliant kernel: smb_trans2_request: result=-32, setting invalid
:: The error=-3 is telling me that the smbmount daemon is gone, or didn't :: get registered right, or blew a core ball, or something. The smbfs module :: is trying to signal it to rebuild the connection and it's not there. When :: this happens, can you do a "ps ax" and check if there is an smbmount process :: running? :: :: If there is not, then the problem is to determine what happened to it. :: :: What you might want to do is to do the mount and then find the process :: id of the smbmount daemon. Once you have that, run gdb on the smbmount :: binary and "attach {PID}" from the gdb prompt and then "continue". If :: smbmount exits for some reason, you'll get a gdb prompt back with the exit :: reason. If it's some error, you can type "where" and get a traceback. :: That will tell me a lot, if this thing is exiting prematurely.
Here is the output from gdb:
root:reliant me2v$ gdb /usr/bin/smbmount GNU gdb 4.17 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux"... (gdb) attach 16508 Attaching to program `/usr/bin/smbmount', process 16508 Reading symbols from /lib/libdl.so.2...done. Reading symbols from /lib/libcrypt.so.1...done. Reading symbols from /lib/libpam.so.0...done. Reading symbols from /lib/libc.so.6...done. Reading symbols from /lib/ld-linux.so.2...done. Reading symbols from /lib/libnss_files.so.1...done. Reading symbols from /lib/libnss_nis.so.1...done. Reading symbols from /lib/libnsl.so.1...done. Reading symbols from /lib/libnss_dns.so.1...done. Reading symbols from /lib/libresolv.so.2...done. 0x400a4237 in pause () (gdb) continue Continuing.
(gdb) continue Continuing.
Program received signal SIGUSR1, User defined signal 1. 0x400a4237 in pause () (gdb) where #0 0x400a4237 in pause () #1 0x804aad0 in send_fs_socket () #2 0x804adec in cmd_mount () #3 0x804b2d1 in process () #4 0x804c06e in main () (gdb)
I'll try it again with the password on the command line and see what happens.
-- Matthew Vanecek Studies in Business Computers at the University of North Texas http://www.unt.edu/bcis Visit my Website at http://people.unt.edu/~mev0003 ***************************************************************** For 93 million miles, there is nothing between the sun and my shadow except me. I'm always getting in the way of something...
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |