search for: smb_trans2_request

Why do I keep getting these messages? (from /var/log/messages) I use RedHat 7.1 and have a coupple of shares on the machine on a bizzy samba network. Oct 10 04:03:50 n243 kernel: smb_trans2_request: result=-104, setting invalid Oct 10 04:03:50 n243 kernel: smb_retry: successful, new pid=5506, generation=47 Oct 10 04:44:03 n243 kernel: smb_trans2_request: result=-104, setting invalid Oct 10 04:44:03 n243 kernel: smb_retry: successful, new pid=5506, generation=48 Oct 10 09:03:22 n243 kernel: sm...

Hi people,

Every morning at 2:02am, and 6:25am, I get the following two lines in my /var/log/messages: Nov 6 06:25:15 borgCube kernel: smb_trans2_request: result=-104, setting invalid Nov 6 06:25:16 borgCube kernel: smb_retry: successful, new pid=28929, generation=37 The pid always stays the same, and generation increases by 1 everytime it happens. Currently I got one share from a W2K computer mounted on my filesystem, and one share from the samb...

...hese messages in /var/log/dmesg on a Redhat 7.1 machine running Samba 2.2.2 accessing a Win 2000 share. Actually, there are a bunch of tasks accessing the same share, complete with file locking, etc. Any docs on what that error code means? ...Thanks, ...Kenneth smb_get_length: recv error = 113 smb_trans2_request: result=-113, setting invalid smb_file_write: syndex/csafe.log validation failed, error=4294967291 smb_file_write: syndex/csafe.log validation failed, error=4294967291 smb_file_write: syndex/csafe.log validation failed, error=4294967291 smb_file_write: syndex/cdrsfe.log validation failed, error=429...

Hello. I hope that this is the proper place to ask this. Here is my problem. I have several smbmounts under Red Hat Linux 5.1. They need to be accessed by my apache web server. One of the mounts keeps getting disconnected, but this is not noticed by Linux. So the Linux box thinks that the files under the smbmount are still accessable when they aren't actually mounted. What would be the best

...ou can mount shares, but after a while, the connection is broken and all sorts of strange stuff happens. I've got a share called /mnt/ntshare which remotely mounts an NT host: [arnow@foo /mnt]$ ls ls: ntshare: Input/output error cdrom/ floppy/ [arnow@foo /mnt]$ [arnow@foo /mnt]$ dmesg | tail smb_trans2_request: result=-32, setting invalid smb_retry: new pid=360, generation=2 smb_trans2_request: result=-32, setting invalid smb_retry: new pid=360, generation=3 smb_trans2_request: result=-32, setting invalid smb_retry: new pid=360, generation=4 smb_trans2_request: result=-32, setting invalid smb_retry: sign...

...ntinues to out perform nfs hands down. Problem is - I'm receiving errors on both of the test servers. The backups are completing and nothing is hanging, but I need to find out more on the following errors before making the change in our production environment: smb_get_length: recv error = 5 smb_trans2_request: result=-5, setting invalid smb_retry: successful, new pid=818, generation=114 smb_get_length: recv error = 5 smb_trans2_request: result=-5, setting invalid smb_retry: successful, new pid=818, generation=115 smb_get_length: recv error = 5 smb_request: result -5, setting invalid smb_retry: successfu...

I keep seeing this in my logs: Jul 5 12:37:29 gateway kernel: smb_trans2_request: result=-32, setting invalid What have I screwed up? Also, any news on when the search stuff will be back up?

...the next one after the last process displayed on the term with the frozen 'ps aux', that term freezes. If I leave it alone for a while, it will usally come back to life, and in /var/log/messages, I get: Mar 5 10:22:47 ra kernel: smb_get_length: recv error = 104 Mar 5 10:22:47 ra kernel: smb_trans2_request: result=-104, setting invalid Mar 5 10:22:47 ra kernel: smb_retry: sucessful, new pid=3860, generation=2 Mar 5 10:22:47 ra kernel: smb_proc_readdir_long: error=-104, retrying Mar 5 10:23:47 ra kernel: smb_get_length: recv error = 104 Mar 5 10:23:47 ra kernel: smb_trans2_request: result=-104, se...

...Linux 2.3 (Caldera) system, and I was wondering if this error message is NORMAL behavior for a NT Server share mounted with the following command: //inet_server_1/C /mnt/server1 -o username=xxxxxxxx,password=xxxxxx,ip=x.x.x.2 here is what is in /var/log/messages: Mar 15 09:51:59 htmlodds kernel: smb_trans2_request: result=-32, setting invalid Mar 15 09:51:59 htmlodds kernel: smb_retry: sucessful, new pid=22605, generation=3 Now, in Samba-2.0.7, the response to a df -h message would be a input/output error on /mnt/server1, but in this case, it appears to have recovered the error on it's own (which is a g...

...mounted as SMBFS shares from a Windows 2000 Server. For the most part, this set-up is working great, however, there have been occasional hiccups. Every so often, one of the servers, LINUX-ONE, logs a couple of Samba-related errors. The following is an example: Jun 30 06:30:45 mx-two kernel: smb_trans2_request: result=-104, setting invalid Jun 30 06:30:45 mx-two kernel: smb_retry: successful, new pid=553, generation=25 I believe this is due to the network connection used by the relevant SMBFS mount shutting down because of inactivity, and then being re-established when the mount is access...

...ed device number 1 hub.c: USB hub found hub.c: 2 ports detected Intel(R) PRO/100 Fast Ethernet Adapter - Loadable driver, ver. 1.2.1 Copyright (c) 2000 Intel Corporation e100 - Intel(R) 8255x-based Ethernet eth0: Mem:0xfe900000 IRQ:16 Speed:100 Mbps Dx:Full Hardware receive checksums enabled smb_trans2_request: result=-32, setting invalid smb_lookup: find //My Documents failed, error=-5 smb_lookup: find //My Documents failed, error=-5 smb_lookup: find //My Documents failed, error=-5 smb_lookup: find //My Documents failed, error=-5 smb_lookup: find //My Documents failed, error=-5 smb_lookup: find //My Doc...

...ares (from an NT client), but I would like to report a problem with SMBFS and SMBMOUNT. NT4, SP5 shares mounted into the filespace of the Linux box can disconnect over time with two possible outcomes. The activity is registered in the ring buffer as follows: a) successful reconnect negotiation: smb_trans2_request: result=-32, setting invalid smb_retry: new pid=24456, generation=3 smb_trans2_request: result=-32, setting invalid smb_retry: new pid=24456, generation=4 b) unsuccessful reconnect negotiation: smb_lookup: find //linux failed, error=-5 smb_retry: caught signal smb_retry: signal failed, error=-3...

...a Linux Workstation (Dual Processor Xeon, 800GByte RAID 10, Gigabit Ethernet). There is a Samba Server (2.2.0) on it and there is a mounted Share from an NT-PC (mount -t smbfs -o username=xxx,password=xxx //xxx/mount /home/mnt). In the file /var/log/messages I have the following error Messages : smb_trans2_request: result=-104, setting invalid smb_lookup: find //xxx failed, error=-104 smb_lookup: find //xxx failed, error=--5 # a few of them and there is a Problem to write on it. The Problems come and go, sometimes it's working and sometimes not. What can I do ? It's very important !! Thank yo...

Hi, Could some please tell me what it means if I find sometimes the following message written to the console or the bootup log under Debian Linux: smb_get_lenght: recv error=5 smb_trans2_request: result=-5, invalid setting Samba version is: 2.2.2debian-2 (And other then the occasional message I see no problem with it.) I've tried to look for some info on error messages but I didn't dound any answer. Please copy me on my address as well, as I don't subscribe to the list. Man...

My current smb.conf http://mdew.orcon.net.nz/samba/smb.conf , isnt showing up in windows b0xes (Win2k) I can however mount my drive from the linux router, and it shows this error (maybe unrelated/related to this..) mount /sharing/ryan smb_get_length: recv error = 5 smb_trans2_request: result=-5 setting invalid smb_retry: succesful, new pid=32382, generation=2 My drive is browsable from the router etc...but it does spew this, just the windows clients on the lan cant see my drive. any ideas? Running Debian Sid with the latest Samba 2.2.5 debs. (mounting win2k shares is fine)...

...ient/smbmount.c:send_fs_socket(405) Mar 19 09:13:59 hedron mount.smbfs[23153]: mount.smbfs: entering daemon mode for service \\dborg\POS, pid=23153 Mar 19 09:14:29 hedron kernel: SMB server not responding Mar 19 09:14:29 hedron kernel: smb_get_length: recv error = 5 Mar 19 09:14:29 hedron kernel: smb_trans2_request: result=-5, setting invalid Mar 19 09:15:29 hedron kernel: smb_lookup: find //Store_257 failed, error=-5 Mar 19 09:16:29 hedron kernel: smb_lookup: find //Store_257 failed, error=-5 Mar 19 09:16:39 hedron kernel: smb_retry: caught signal Mar 19 09:16:39 hedron kernel: smb_lookup: find //Store_261 f...

...te, Centos 3 boxes can not use samba to communicate with each other, although Windows and the Centos 3 boxes see each other correctly as do RHEL5 and the Centos3 boxes. The du command works well, but ls, cp, cat ,etc produces the error: PANIC: push_ascii - dest_len == -1 in the server log and smb_trans2_request: result=-5, setting invalid in the client. A similar (but more serious) set of problems was reported in Ubuntu early this morning after their update. Is any one else experiencing this problem with samba and Centos 3 after the update? regards, benm

...[command] mount -t smbfs //rocky/c$ /mnt/rocky -o rw,credentials=/my/credentials/file --or-- mount.smbfs //rocky/c$ /mnt/rocky -o rw,credentials=/my/credentials/file [log] Jul 22 14:42:44 hanako kernel: smb_receive_trans2: data/param too long, data=1024, parm=57231 Jul 22 14:42:44 hanako kernel: smb_trans2_request: result=-5, setting invalid Jul 22 14:42:45 hanako kernel: smb_retry: caught signal [solution] Recompile the kernel with 'MAX_SMB_PACKET_SIZE' set to 65536. My kernel had it at 32763. This can be done easily by hand or with this patch (remember - this is for the SuSE linux 8.2 kernel 2.4.2...

...activity on the NT box, bypassing the cache (i.e., ls > /dev/null doesn't work, but df does). This must be done on a regular basis--every two or three minutes. Error messages me2v:reliant me2v$ ls winnt ls: winnt: Input/output error from /var/log/messages: Sep 15 20:09:14 reliant kernel: smb_trans2_request: result=-32, setting invalid Sep 15 20:10:25 reliant kernel: smb_retry: signal failed, error=-3 This was after only about 1 and 1/2 hours, give or take 15 minutes. This has been a recurring problem since I moved to 2.0.3 from 1.9.18 way back when, and plenty of other people have had it, also. Th...