similar to: unexpected smb stop service.

Displaying 20 results from an estimated 1000 matches similar to: "unexpected smb stop service."

2006 Feb 20
0
R: unexpected smb stop service.
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]
2006 Nov 20
0
NO_LOGON_SERVERS error
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
2007 Jun 13
2
tdb_lock failed.... (Interrupted system call)
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
2007 Jun 15
2
secrets.tdb locking fun!
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
2006 Feb 23
0
urgently help - critical error.
Hi all, By some days around 12:00 o'clock I have the following problem with my SUSE Linux 2.6.11.4-21.9-default i686 i386 GNU/Linux, with Samba Version 3.0.21a-0.1-SUSE: xxx:~ # tail /var/log/samba/log.machine01 [2006/02/23 12:05:54, 1] smbd/sesssetup.c:reply_spnego_kerberos(180) Failed to verify incoming ticket! [2006/02/23 12:06:04, 0] tdb/tdbutil.c:tdb_log(772)
2002 Dec 08
1
Sudden Bug
High I'm using samba in my private network since 1 year. Since yesterday I fi nd the mesg in the appendix when I trie to print. File transfer works fine, you find all printers but its not possible to print anything. Where to search ? Thanks a lot Bernd -------------- next part -------------- [1995/12/08 12:52:10, 0] tdb/tdbutil.c:tdb_log(342) tdb(/var/lib/samba/printing.tdb):
2002 Feb 13
0
"could not open file /var/lock/samba/unexpected.tdb"
When I start winbindd (Samba v2.2.3a on Linux), I get the entries in log.winbindd shown below. What's the story on all those complaints about file "unexpected.tdb"? There is no general problem with Samba writing to that subdirectory: # ll /var/lock/samba/ total 288 -rw-r--r-- 1 root root 696 Feb 12 22:01 brlock.tdb -rw-r--r-- 1 root root 231 Feb 13
2007 Oct 17
2
tdb/tdbutil.c:tdb_chainlock_with_timeout_internal (rev_2)
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)
2003 Oct 16
0
Cann't get Samba 3.0.0 installed on a SuSE 8.2
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
2004 Nov 09
3
3.0.8 compile warnings and link error
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
2005 Aug 04
1
SAMBA LOG: tdb/tdbutil.c:tdb_log(725) tdb(unnamed): tdb_open_ex: /var/cache/samba/unexpected.tdb (835, 457947) is already open in this process
Please, What's this? Please, please, how to resolve ? [root@neosaldina-lj003 samba]# more nmbd.log tdb(unnamed): tdb_open_ex: /var/cache/samba/unexpected.tdb (835,457947) is alr eady open in this process [2005/08/04 00:12:51, 2] tdb/tdbutil.c:tdb_log(725) tdb(unnamed): tdb_open_ex: /var/cache/samba/unexpected.tdb (835,457947) is alr eady open in this process [2005/08/04
2005 Mar 04
0
Winbind Daemon dying
Samba 3.0.11 on SLES8 on z/VM The system will be running fine then every few days the Winbind daemon will stop. Below are the last lines of the log file. [2005/03/03 14:15:00, 0] sam/idmap_rid.c:rid_idmap_get_id_from_sid(475) rid_idmap_get_id_from_sid: no suitable range available for sid: S-1-5-32-545 [2005/03/03 14:15:00, 0] sam/idmap_rid.c:rid_idmap_get_id_from_sid(475)
2005 Mar 29
1
Problem with pdf printing
Hello, I'm hoping someone can help me. I have several pdf printers set up and when I print to them samba becomes unstable and several errors are dumped to the log. These pdf printers were working when I was using version 3.0.6. When I went to a newer version of samba the queue would not clear on the windows side and no errors were logged. Yesterday I upgraded to version 3.0.13-1 and the
2005 Mar 30
2
Problem with pdf printing (SOLVED)
Urs Rau wrote: >>I start to wonder what "dammage" it would do to set lpq to >>lpq command =/bin/true >>for my pdf printer? ;-) > > > > Well, wonder no more sir!!!!!! I set my lpq command = /bin/true and > ALL QUEUES CLEAR AND ACT PROPERLY!!!!!!!!!!!! I could kiss you! That was all I did, I can't believe it worked......thank you!!!!!! >
2005 Jan 24
0
len xxxxx deyond eof at 8192
Dear all, The server log is filled with entries "xxx len xxxxx deyond eof at 8192" I have search on google but can't found a solution for it, please advise. The server is running FC2 with samba-3.0.7-2.FC2 Jan 24 14:49:16 smb nmbd[30183]: [2005/01/24 14:49:16, 0] tdb/tdbutil.c:tdb_log(725) Jan 24 14:49:16 smb nmbd[30183]: tdb(/var/cache/samba/gencache.tdb): tdb_oob len
2004 Nov 04
0
Problem in restarting samba server
Hello, I am using Red-hat Linux Application Server 3.0. I have installed and successfully configured samba server & thus able to connect from windows m/c....It works perfectly fine. But when I install our product( Its a java application and one kernel loadable module) on the same machine The samba server does not restart. Following are the messages in /var/log/samba/smbd.log. after
2002 Aug 03
0
Samba 2.2.5 under Debian 3.0 i386: Still frequent connections.tdb corruption
[CC to Debian package maintainer] Hi there, I'm still experiencing this worrysome tdb corruption even after I upgraded to 2.2.5. I built this package myself from the officially released 2.2.5 source. Here's a log snippet: Aug 3 11:15:04 Server smbd[23307]: [2002/08/03 11:15:04, 0] tdb/tdbutil.c:tdb_log(492) Aug 3 11:15:04 Server smbd[23307]: tdb(/var/run/samba/connections.tdb):
2004 Feb 04
1
tdb(unnamed): tdb_brlock failed (fd=12) at offset 4 rw_type=1 lck_type=13
Some times I have in log : [2004/02/04 12:00:06, 5] lib/gencache.c:gencache_init(59) Opening cache file at /var/lock/samba/gencache.tdb [2004/02/04 12:00:06, 5] tdb/tdbutil.c:tdb_log(724) tdb(unnamed): tdb_brlock failed (fd=12) at offset 4 rw_type=1 lck_type=13: Ressource temporairement non disponible [2004/02/04 12:00:06, 5] libsmb/namecache.c:namecache_enable(58) namecache_enable:
2005 Oct 27
9
Overloaded samba server. Is it a bug?
Experts, We've just migrated from samba 2.2.8a to samba 3.0.20b in a very large corporate environment. Everything was really fine in our lab, but we began experiment serious load problems on the productive servers the morning after the procedure took place. I'll try (briefly) to describe the characteristics of the scenario: Resources: Old Environment: Hardware:
2004 Jan 08
0
tdb access problem - tdb_brlock failed
Hi I my smbd.log, I can find these lines. How to resolv this problem ? [2004/01/08 12:03:11, 5] lib/gencache.c:gencache_init(59) Opening cache file at /var/cache/samba/gencache.tdb [2004/01/08 12:03:11, 5] tdb/tdbutil.c:tdb_log(724) tdb(unnamed): tdb_brlock failed (fd=12) at offset 4 rw_type=1 lck_type=13: Ressource temporairement non disponible [2004/01/08 12:03:11, 5]