[Samba] odd swat issues, odd printer issue, odd crashes..

[Mark Rutherford]

Before I start, can you CC me if you respond as im not subscribed. thanks!

(this is samba 3.0.4 on suse enterprise linux, kernel 2.6.5)

first, the swat issue.
I had a machine that had 2 network interface cards in it.
I have since removed one card, mainly because it caused weird performace 
issues unrelated to samba.
the interface addresses were 192.168.0.200 and 192.168.0.201
another machine now resides on .200 and the original samba fileserver is 
on .201

everything works just fine, samba ran before and after..
now. swat reports all the daemons as 'not running' even tho they are 
actually running.
I googled around trying to find out why this is, most of what I found 
were related to the interfaces, ect.
ive tried making sure 127.0.0.1 and 192.168.0.201 are in the list, ect.
this wasnt the issue, so i thought that maybee it loks for pidfiles.. 
checked those, and they have not moved.
I made sure the daemons were all shut down, then made sure the pidfiles 
were deleted, and they were.
so, its not a pidfile issue...
that left me with putting swat in debug, and this is where I got my 
first clue...
this is what I saw in the logfile.... :

[2005/02/06 01:05:30, 2] libsmb/namequery.c:name_query(491)
  Got a positive name query response from 127.0.0.1 ( 192.168.0.200 
192.168.0.201 )
[2005/02/06 01:05:30, 2] lib/util_sock.c:open_socket_out(772)
  error connecting to 192.168.0.200:445 (Connection refused)
[2005/02/06 01:05:30, 2] lib/util_sock.c:open_socket_out(772)
  error connecting to 192.168.0.200:139 (Connection refused)
[2005/02/06 01:05:30, 1] libsmb/cliconnect.c:cli_connect(1297)
  Error connecting to 192.168.0.200 (Connection refused)
[2005/02/06 01:05:30, 2] lib/util_sock.c:open_socket_out(772)
  error connecting to 192.168.0.200:445 (Connection refused)
[2005/02/06 01:05:30, 2] lib/util_sock.c:open_socket_out(772)
  error connecting to 192.168.0.200:139 (Connection refused)
[2005/02/06 01:05:30, 1] libsmb/cliconnect.c:cli_connect(1297)
  Error connecting to 192.168.0.200 (Connection refused)
[2005/02/06 01:05:30, 0] libsmb/nmblib.c:send_udp(788)
  Packet send failed to 192.168.0.200(137) ERRNO=Invalid argument
[2005/02/06 01:05:30, 0] libsmb/nmblib.c:send_udp(788)
  Packet send failed to 192.168.0.200(137) ERRNO=Invalid argument

so, my first reaction, OK! I missed a hosts or lmhosts entry someplace 
when I nuked that other network card..
but, I couldnt find any reference on the whole machine to that address 
BUT.. the file 'wins.dat' that resides in
/var/lib/samba

so, I figured that I would simply copy these files out then remove them 
and let it regenerate all of them, and perhaps
the entries that had references to the old ip would dissapear....
fat chance. it bit me hard when it simply regenerated the files, and 
they contained the same data as before!
the daemons were not running when I did this, either.
there are no other samba or windows servers on the network that it could 
contact to get this data from...
so, im stuck there. somehow it still wants to hold onto that ip address. 
I need it to let go. its not a REAL major issue,
but at this point its more of an academic excercise. I suppose I can 
adjust to swat not reporting the statuses correctly. thing is that
I have to log into the machine and manually restart the daemons or wait 
for samba to reload on its own.

is this a bug?
anyone have any idea what a fix would be? im clear out of ideas on that 
one...


NOW, the printers issue...
I am attempting to install printer drivers on the samba server, it has 6 
print queues, and uses the cups backend.
all printing works fine, just that your prompted for drivers. so I 
figured I would take a stab at it.
I use the windows add printer stuff to do this, and it all goes fine, as 
in it copies the files, ect
when its done copying the files, it says 'printer settings could not be 
saved, access is denied'
this is what I see after the file copy log entries:

[2005/02/06 01:07:26, 2] 
rpc_server/srv_spoolss_nt.c:find_printer_index_by_hnd(268)
  find_printer_index_by_hnd: Printer handle not found: 
find_printer_index_by_hnd: Printer handle not found: 
close_printer_handle: Invalid handle (OTHER:23299:23755)
[2005/02/06 01:07:26, 2] 
rpc_server/srv_spoolss_nt.c:find_printer_index_by_hnd(268)
  find_printer_index_by_hnd: Printer handle not found: 
find_printer_index_by_hnd: Printer handle not found: 
close_printer_handle: Invalid handle (OTHER:23053:23755)


clueless on this one.... again, its really not all that important...



Last but not least I see these on the logs at times:

[2005/02/06 01:33:54, 0] lib/fault.c:fault_report(37)
  INTERNAL ERROR: Signal 11 in pid 23755 (3.0.4-SUSE)
  Please read the appendix Bugs of the Samba HOWTO collection
[2005/02/06 01:33:54, 0] lib/fault.c:fault_report(39)
  ===============================================================
[2005/02/06 01:33:54, 0] lib/util.c:smb_panic2(1398)
  PANIC: internal error
[2005/02/06 01:33:54, 0] lib/util.c:smb_panic2(1406)
  BACKTRACE: 17 stack frames:
   #0 /usr/sbin/smbd(smb_panic2+0x120) [0x8202870]
   #1 /usr/sbin/smbd(smb_panic+0x26) [0x8202a36]
   #2 /usr/sbin/smbd [0x81ee000]
   #3 [0xffffe420]
   #4 /usr/sbin/smbd [0x813f392]
   #5 /usr/sbin/smbd(api_rpcTNP+0x29e) [0x817331e]
   #6 /usr/sbin/smbd(api_pipe_request+0xe0) [0x8173780]
   #7 /usr/sbin/smbd [0x816d7ec]
   #8 /usr/sbin/smbd(write_to_pipe+0x127) [0x816bf37]
   #9 /usr/sbin/smbd [0x808ef2c]
   #10 /usr/sbin/smbd(reply_trans+0xb9b) [0x808fc3b]
   #11 /usr/sbin/smbd [0x80e2327]
   #12 /usr/sbin/smbd(process_smb+0x1aa) [0x80e28ca]
   #13 /usr/sbin/smbd(smbd_process+0x16b) [0x80e2d3b]
   #14 /usr/sbin/smbd(main+0x526) [0x827d0c6]
   #15 /lib/tls/libc.so.6(__libc_start_main+0xe0) [0x402b2250]
   #16 /usr/sbin/smbd [0x8078bb1]


Should I just update this myself and not rely on the suse builds of samba?
think some of my issues will go away?

thanks for reading all of this, hope someone has an idea!