We are running a "C" app on a Linux 2.4.31 box that accesses some =
mounted Windows 2000 drives. Everything worked fine while the Linux and =
Windows servers were located on the same subnet, and in the same =
physical area.

We recently moved the Windows server to another location some forty =
miles away, and are connecting to it through a VPN connection over the =
Internet.

Since moving it, the "C" app has become unstable, and will periodically =
have one of its processes die without saying why. The only thing I =
notice is that when the remaining processes are killed, in both =
/var/log/messages and /var/log/syslog I see the following.

/var/log/messages
Mar 6 20:59:04 ou-one kernel: smb_get_length: recv error =3D 512
Mar 6 20:59:04 ou-one kernel: smb_request: result -512, setting invalid
Mar 6 20:59:04 ou-one kernel: smb_retry: caught signal
Mar 6 20:59:04 ou-one last message repeated 4 times

/var/log/syslog
Mar 6 20:59:04 ou-one mount.smbfs[10144]: =
tdb(/var/cache/samba/gencache.tdb): tdb_lock failed on list 99 ltype=3D0 =
(Bad file descriptor)=20
Mar 6 20:59:04 ou-one mount.smbfs[10144]: [2006/03/06 20:59:04, 0] =
tdb/tdbutil.c:tdb_log(767)=20
Mar 6 20:59:04 ou-one mount.smbfs[10144]: =
tdb(/var/cache/samba/gencache.tdb): tdb_lock failed on list 99 ltype=3D1 =
(Bad file descriptor)=20
Mar 6 20:59:04 ou-one mount.smbfs[10144]: [2006/03/06 20:59:04, 0] =
tdb/tdbutil.c:tdb_log(767)=20
Mar 6 20:59:04 ou-one mount.smbfs[10144]: =
tdb(/var/cache/samba/gencache.tdb): tdb_lock failed on list 99 ltype=3D1 =
(Bad file descriptor)=20

We are using the samba that came with Slackware 10.2, =
samba-3.0.20-i486-2.

Any thoughts?
=20
David Beitler
Network Systems Engineer
Telisimo International (www.Telisimo.com)
9370 Chesapeake Dr.
San Diego, CA 92123
(858)654-9000 x2103
dbeitler@telisimo.com
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba