search for: process_local_message

...on a Sun E450 running Samba 2.0.6. I'm not totally convinced that the problem is caused by the server, but may be the network. However, I've had a look at the log.smb file and I'm seeing some error messages that I've not come across before: [2001/02/23 18:20:40, 0] smbd/oplock.c:process_local_message(581) process_local_message: unsolicited oplock break reply from pid 23624, port 56684, dev = 2580006, inode = 3264116 [2001/02/23 18:20:40, 0] smbd/oplock.c:process_local_message(566) process_local_message: Received unsolicited break reply - dumping info. [2001/02/23 18:20:40, 0] smbd/oplock.c...

...exlusive oplock left by process 14556 after break ! For file PC-BIB/PC_BIB.EXE, dev = 6911, inode = 680216880. Deleting it to continue... [2005/07/29 09:43:43, 0] smbd/open.c:open_mode_check(747) open_mode_check: Existent process 14556 left active oplock. [2005/07/29 09:44:28, 0] smbd/oplock.c:process_local_message(420) process_local_message: Received unsolicited break reply - dumping info. [2005/07/29 09:44:28, 0] smbd/oplock.c:process_local_message(435) process_local_message: unsolicited oplock break reply from pid 14748, port 59668, dev = 6911, inode = 680216880, file_id = 3491 For another one, it sa...

...: receive_smb timed out after 30 seconds. oplock_break failed for file XXXXXXXXX/GLB/FLAG.GLB (dev = 806, inode = 348174). [2000/05/02 10:05:22, 0] smbd/oplock.c:oplock_break(1050) oplock_break: client failure in oplock break in file XXXXXXXXX/GLB/FLAG.GLB [2000/05/02 10:05:22, 0] smbd/oplock.c:process_local_message(568) process_local_message: Received unsolicited break reply - dumping info. [2000/05/02 10:05:22, 0] smbd/oplock.c:process_local_message(583) process_local_message: unsolicited oplock break reply from pid 27365, port 1432, dev = 806, inode = 348174 [2000/05/02 10:05:22, 0] smbd/oplock.c:proces...

I have a level 10 debug of the smbd/oplock process_local_message problem but can still not figure out what causes the unknown UDP message command code. I checked the source but could only see that this is an invalid opcode command. Anyone a clue what is happening here ? Might wrong opcode commands crash samba ? Peter [2003/09/04 11:50:12, 3] smbd/process.c...

...nt log files show messages like this about oplock break issues. [2003/10/09 12:50:39, 0] smbd/oplock.c:(1008) request_oplock_break: no response received to oplock break request to pid 2907 on port 61752 for dev = 40240002, inode = 29, file_id = 2 64 [2003/10/09 12:51:03, 0] smbd/oplock.c:(395) process_local_message: Received unsolicited break reply - dumping info. [2003/10/09 12:51:03, 0] smbd/oplock.c:(409) process_local_message: unsolicited oplock break reply from pid 982, port 61752, dev = 40240002, inode = 29, file_id = 264 [2003/10/09 12:55:35, 0] smbd/oplock.c:(1008) request_oplock_break: no respons...

...ight be the pertinent logs: [2005/03/03 19:49:53, 10] smbd/process.c:async_processing(281) async_processing: Doing async processing. [2005/03/03 19:49:53, 5] smbd/oplock.c:receive_local_message(107) receive_local_message: doing select with timeout of 1 ms [2005/03/03 19:49:53, 5] smbd/oplock.c:process_local_message(350) process_local_message: Got a message of length 18 from port (1817) [2005/03/03 19:49:53, 5] smbd/oplock.c:process_local_message(388) process_local_message: (exclusive) oplock break request from pid 5434, port 1817, dev = 40d04, inode = 1753087, file_id = 5269 [2005/03/03 19:49:53, 3] smbd/...

When trying to delete or copy over certain files on my Samba server, Windows hangs for some time and then gives "access denied". I can delete these files directly from the server, so it's a Samba or Windows problem. There seems to be nothing special about these files, other than that Samba doesn't like touching them. Upon checking the Samba logs, I find this message or

...s fine .... Today the customer called and mentioned that there are additional problems. He had fixed the nmbd problem everyday by rebooting .... :-) Now the smbds also start to die. Again no pattern. No way to reproduce. But there were strange entries in the logs linux smbd[8311]: smbd/oplock.c process_local_message(418) linux smbd[8311]: process localmessage: unknown UDP message command code (e393) ignoring with different command codes i.e. 1e73, 2b94 and others. After some of these messages have arrived the smbd processes start to panic with internal errors. one after the other. I could locate the machin...

I have configured Samba on both a RH Linux 7.2 box and Solaris 8 box and am not able to remove print jobs. The lprm command is not getting called. I know that for a fact because I changed lprm command to equal a script which will log when it is called. And that script is never called. There are no errors in any log files - system or samba. The printing parts of the smb.conf file are:

...a4 [2001/07/26 10:09:10, 0] smbd/oplock.c:request_oplock_break(997) request_oplock_break: no response received to oplock break request to pid 11026 on port 33068 for dev = 900, inode = 81783 for dev = 900, inode = 81783, tv_sec = 3b6021cd, tv_usec = 192a4 [2001/07/26 11:41:07, 0] smbd/oplock.c:process_local_message(357) process_local_message: Received unsolicited break reply - dumping info. [2001/07/26 11:41:07, 0] smbd/oplock.c:process_local_message(372) process_local_message: unsolicited oplock break reply from pid 13649, port 33068, dev = 900, inode = 81783 [2001/07/26 11:41:07, 0] smbd/oplock.c:proce...

...b/util_sock.c:set_socket_options(151) Failed to set socket option SO_RCVBUF (Error Socket operation on non-socket) [2000/08/11 23:02:54, 0] lib/util_sock.c:set_socket_options(151) Failed to set socket option SO_SNDBUF (Error Socket operation on non-socket) [2000/08/11 23:02:58, 0] smbd/oplock.c:process_local_message(607) process_local_message: Received unsolicited break reply - dumping info. [2000/08/11 23:02:58, 0] smbd/oplock.c:process_local_message(622) process_local_message: unsolicited oplock break reply from pid 2714, port 1071, dev = 305, inode = 1785 ***********************************************...

.../30 12:02:12, 0] lib/util_sock.c:read_socket_data(479) read_socket_data: recv failure for 4. Error = Connection timed out [2001/06/30 13:26:13, 0] lib/util_sock.c:read_socket_data(479) read_socket_data: recv failure for 4. Error = Connection reset by peer [2001/06/30 13:28:50, 0] smbd/oplock.c:process_local_message(357) process_local_message: Received unsolicited break reply - dumping info. [2001/06/30 13:28:50, 0] smbd/oplock.c:process_local_message(372) process_local_message: unsolicited oplock break reply from pid 1107, port 32900, dev = 811, inode = 196017 [2001/06/30 15:37:27, 0] lib/util_sock.c:read...

...s : [2001/09/10 11:37:30, 0] smbd/oplock.c:request_oplock_break(997) request_oplock_break: no response received to oplock break request to pid 4715 on port 1046 for dev = 804, inode = 83759 for dev = 804, inode = 83759, tv_sec = 3b9c89ba, tv_usec = 3e163 [2001/09/10 11:37:42, 0] smbd/oplock.c:process_local_message(357) process_local_message: Received unsolicited break reply - dumping info. [2001/09/10 11:37:42, 0] smbd/oplock.c:process_local_message(372) process_local_message: unsolicited oplock break reply from pid 4728, port 1046 , dev = 804, inode = 83759 After a whlie (from 5 seconds to 30) the prog...

..., 0] smbd/oplock.c:request_oplock_break(997) > request_oplock_break: no response received to oplock break request to > pid 4715 > on port 1046 for dev = 804, inode = 83759 > for dev = 804, inode = 83759, tv_sec = 3b9c89ba, tv_usec = 3e163 > [2001/09/10 11:37:42, 0] smbd/oplock.c:process_local_message(357) > process_local_message: Received unsolicited break reply - dumping > info. > [2001/09/10 11:37:42, 0] smbd/oplock.c:process_local_message(372) > process_local_message: unsolicited oplock break reply from pid 4728, > port 1046 > , dev = 804, inode = 83759 > > After...