similar to: urgently help - critical error.

Thanks, chdir dir /data error seems go away, but at 12:00 o'clock the following error appear: Feb 20 11:45:03 brulx01 vsftpd: Mon Feb 20 11:45:03 2006 [pid 12273] [job260] OK DOWNLOAD: Client "10.90.1.1", "/data/mde/DATA/.././ACTUAL/mdeact260.msg", 12481 bytes, 174.76Kbyte/sec Feb 20 11:56:10 brulx01 smbd[12410]: [2006/02/20 11:56:10, 0]

Hi All, I'm working on SUSE Linux 2.6.11.4-21.9-default i686 i386 GNU/Linux, with Samba Version 3.0.21a-0.1-SUSE. At Initially installation seems all works fine, but sometimes happens nobody can access to data share, people already authenticated, continuing working as well, while new users entry receive an error message. I have found something in "/var/log/messages" file

Has anyone seen any fixes above 3.0.23a that addresses an issue similar to this one? [2007/06/13 14:01:40, 0] tdb/tdbutil.c:tdb_log(783) tdb(/usr/local/samba-3.0.23a/private/secrets.tdb): tdb_lock failed on list 65 ltype=1 (Interrupted system call) [2007/06/13 14:01:40, 0] tdb/tdbutil.c:tdb_chainlock_with_timeout_internal(82) tdb_chainlock_with_timeout_internal: alarm (10) timed out for

I've seen more and more occurrences of the following error (other people have different password servers) on the web. I submitted this question before, but it was never resolved. I've even tried changing the underlying file system (from clustered vxfs to ext3) and I still see the error. Error: [2007/10/17 08:29:33, 0] tdb/tdbutil.c:tdb_chainlock_with_timeout_internal(82)

Hi there. I have two samba servers, let's say srv01 and srv02. For that matter, both are Zentyal Server 4 and 8, respectively. In the srv01 there is samba version 4.1, which is in the network 182.168.200.0/24, and which is by the way also the gateway to both network. In the srv02 there is samba version 4.15, which is in the DMZ network 10.10.100.0/24 The first is an additional controller for

Hi all, After much grief today, we'd like to support the 'TODO' note in source/lib/util_tdb.c :- /* TODO: If we time out waiting for a lock, it might * be nice to use F_GETLK to get the pid of the * process currently holding the lock and print that * as part of the debugging message. -- mbp */ It could have saved us a whole-sale restart of Samba if we could have more easily

Hallo, after I got same error messages because of missing Kerberos, I deinstalled heimdal and installed Kerberos 5 (_devel, _libs, _workstation). I also made the necessary changes in the /etc/krb5.conf file and tested the connection with the Active Directory with the kinit ...@.... I also synchronized the time and so I get the tickets. Now I wanted to install Samba 3.0.0 on SuSE 8.2 and there the

On Fri, 17 May 2024 12:36:33 -0300 Gilberto Ferreira via samba <samba at lists.samba.org> wrote: > Hi there. > I have two samba servers, let's say srv01 and srv02. For that matter, > both are Zentyal Server 4 and 8, respectively. > In the srv01 there is samba version 4.1, which is in the network > 182.168.200.0/24, and which is by the way also the gateway to both >

Hi, compile warnings in 3.0.8: lib/util_str.c: In function `strstr_m': lib/util_str.c:1337: warning: return discards qualifiers from pointer target type tdb/tdbutil.c: In function `make_tdb_data': tdb/tdbutil.c:46: warning: assignment discards qualifiers from pointer target type tdb/tdbutil.c: In function `tdb_chainlock_with_timeout_internal': tdb/tdbutil.c:60: warning: passing arg

Hello, We have a 3.0.21c samba server in a PDC role with ldap as the backend database, the server has been working without any problem for several weeks, but today it's started showing this log message: [2006/11/20 09:40:48, 0] tdb/tdbutil.c:tdb_log(772) tdb(/usr/local/etc2/samba_SACOU/private/secrets.tdb): tdb_lock failed on list 100 ltype=1 (Interrupted system call) [2006/11/20

Hi I am testing running tinc in switch mode. , my topology is as follows Site 1 (tinc-srv01) -> Site 2 (tinc-srv02) I have configured the bridge interfaces with ip addresses and able to ping between bridges. I then setup a server on each site and tested layer 2 connectivity between the two servers. Topology as follows. Server 1 - *Site 1* (tinc-srv01) -> *Site 2* (tinc-srv02) - Server 2

Hi Lars Thank you for reply. My apologies it is running in "*TAP*" mode. root at tinc-srv:~# tincd -n netname -D -d3 tincd 1.0.23 (Dec 5 2013 17:16:47) starting, debug level 3 /dev/net/tun is a Linux tun/tap device (tap mode) I have enabled ip forwarding and it seems that bridging rules is enabled root at tinc-srv02:~# cat /proc/sys/net/bridge/bridge-nf-call-iptables 1 root at

Hi all, I wanted to upgrade from samba 3.0.4 to 3.0.7 and installed Samba 3.0.7 in a seperate directory . OS is Solaris 8 on Sun-Sparc. Python 2.3.3 (from sunfreeware) installed libiconv 1.8 installed When running "make check" i get the following output: .......................... # make check WARNING: you need to run ./config.status Linking bigballofmud shared library

Hello Yazeed, Am Tue, 5 Apr 2016 11:26:55 +0300 schrieb Yazeed Fataar <yazeedfataar at gmail.com>: > [..] > > *Site 1* > Server -ping- Site 1 (tinc-srv01) - Success > Server -ping- Site 2 (tinc-srv02) - Success > Server -ping- Site 2 - Server 2 - Failure > > > *Site 2* > Server -ping- Site 2 (tinc-srv02) - Success > Server -ping- Site 1 (tinc-srv01) -

Hello folks, While compiling samba I get a lot of warnings and errors which I don't know how to handle. I've been searching the internet and I found several notes from other people having the same errors/warnings, but never found a solution. In fact there was no response at all to these cries for help. Hopefully somebody will react to my cry... Can somebody give me a clue of what

Hi, We are experiencing a problem with Samba 3.6.4 on Solaris 10 update 10. This problem has only recently started since an upgrade to v3.6.3 and was still present after rebuilding to 3.6.4. We are using the version of samba packaged by OpenCSW. >From a client perspective, the issue is manifested as intermittent very poor performance or intermittent inability to save a file to the share at

Guys, I've a simple setup where a Solaris 8 server running Samba 3.0.4 serves out a single share. User authentication is done through Windows Active Directory servers. This has been working fine with a Windows client where the user can map the share without any problems. The user has now setup a new Windows server and is failing to map the share. I can see the following error message in the

I've managed to configure a LVS Cluster to act as a transparent proxy squid farm, with a virtual server as load balancer, and three real servers. Because redirecting packets going to port 80 to port 3128 of squid in the load balancer doesn't works, the solution has a mix of ip route and iptables. Here is the script I wrote to configure transparent proxy. #!/bin/bash #Transparent proxy

Hello. I run samba 3.0.21c on RHEL AS 4 EMT_64 U3 and I've experienced a strange problem where smbd will go (and stay) in the D state. While waiting for IO (possibly), these smbd processes do not respond to client requests, thus samba appears to be down. I could not kill these processes via kill -9 , so I rebooted which worked. The only error I could see out of the ordinary would be

Hello I have Samba that joined Windows 2003 based ADS. At least "net ads testjoin" and "net rpc testjoin" gives that "Join is OK". Alas clients can't connect to Samba server. In a log I see following messages : [2005/04/08 14:51:41, 0] tdb/tdbutil.c:(725) tdb(/web/opt/etc/smbprivate//secrets.tdb): tdb_lock failed on list 2 ltype=2 (Resource temporarily