[Samba] Need help with SWAT

Ryan Novosielski novosirj at umdnj.edu
Wed Jan 9 19:27:16 GMT 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

No problem. In that case, it was probably trying to exec the directory
(which unsurprisingly did not work).

Donald Woeltje wrote:
> Thanks, everyone (especially Ryan and Vickie). That correction in my inetd.conf file took care of the problem. I hand the path but not path/filename in the swat entry in inetd.conf. Once I corrected that, it started working. I appreciate all the help.
> 
> ________________________________
> From: Vickie L. Kidder [mailto:Vickie.Kidder at TABASCO.com]
> Sent: Wednesday, January 09, 2008 12:53
> To: Donald Woeltje
> Cc: samba at lists.samba.org
> Subject: RE: [Samba] Need help with SWAT
> 
> 
> Do you have entries for swat in
> /etc/services file?
> swat            901/tcp
> 
> /etc/inetd.conf file?
> swat    stream  tcp     nowait.400      root    /usr/local/samba/sbin/swat swat
> 
> 
> samba-bounces+vickie.kidder=tabasco.com at lists.samba.org wrote on 01/09/2008 11:34:53 AM:
> 
>>  Telnet attempt returned "Connection to <public ip address> closed
>> by foreign host." When I attempted the same thing to the loopback
>> address, I got the same thing (just a different IP address, of
>> course); "Connection to 127.0.0.1 closed by foreign host."
>>
>> As for documentation on swat, there is precious little of it that I
>> could find. No significant details or detailed explanations of swat
>> command line options or information about any swat logfiles. I
>> checked all the files in /var/log (including all iterations of
>> syslog) and no entries mentioning swat. Nor could I find (or find
>> any mention of in any doc) any swat configuration file. There is an
>> smb.conf but that is for samba configuration (I also could not find
>> a man page or doc that describes and explains ALL of the various
>> entries that can be put into the smb.conf file).
>>
>> After rooting around, though, I did find in /usr/local/samba/var a
>> log file called log.swat. Here is what I found in it:
>>
>>  [2008/01/07 15:38:37, 0] printing/pcap.c:pcap_cache_reload(159)
>>   Unable to open printcap file /etc/printcap for read!
>> [2008/01/07 15:38:37, 0] lib/util_sock.c:get_peer_addr(1232)
>>   getpeername failed. Error was Socket operation on non-socket
>> [2008/01/07 15:39:39, 0] printing/pcap.c:pcap_cache_reload(159)
>>   Unable to open printcap file /etc/printcap for read!
>> [2008/01/07 15:39:39, 0] lib/util_sock.c:get_peer_addr(1232)
>>   getpeername failed. Error was Socket operation on non-socket
>> [2008/01/07 16:22:09, 0] printing/pcap.c:pcap_cache_reload(159)
>>   Unable to open printcap file /etc/printcap for read!
>> [2008/01/07 16:22:09, 0] lib/util_sock.c:get_peer_addr(1232)
>>   getpeername failed. Error was Socket operation on non-socket
>> [2008/01/07 16:22:09, 0] lib/access.c:check_access(327)
>> [2008/01/07 16:22:09, 0] lib/util_sock.c:get_peer_addr(1232)
>>   getpeername failed. Error was Socket operation on non-socket
>>   Denied connection from  (0.0.0.0)
>> [2008/01/08 08:32:11, 0] printing/pcap.c:pcap_cache_reload(159)
>>   Unable to open printcap file /etc/printcap for read!
>> [2008/01/08 08:32:12, 0] lib/util_sock.c:get_peer_addr(1232)
>>   getpeername failed. Error was Socket operation on non-socket
>> [2008/01/08 08:32:12, 0] lib/access.c:check_access(327)
>> [2008/01/08 08:32:12, 0] lib/util_sock.c:get_peer_addr(1232)
>>   getpeername failed. Error was Socket operation on non-socket
>>   Denied connection from  (0.0.0.0)
>> [2008/01/08 08:57:00, 0] printing/pcap.c:pcap_cache_reload(159)
>>   Unable to open printcap file /etc/printcap for read!
>> [2008/01/08 08:57:00, 0] lib/util_sock.c:get_peer_addr(1232)
>>   getpeername failed. Error was Socket operation on non-socket
>> [2008/01/08 08:57:00, 0] lib/access.c:check_access(327)
>> [2008/01/08 08:57:00, 0] lib/util_sock.c:get_peer_addr(1232)
>>   getpeername failed. Error was Socket operation on non-socket
>>   Denied connection from  (0.0.0.0)
>> [2008/01/08 10:32:26, 0] printing/pcap.c:pcap_cache_reload(159)
>>   Unable to open printcap file /etc/printcap for read!
>> [2008/01/08 10:32:26, 0] lib/util_sock.c:get_peer_addr(1232)
>>   getpeername failed. Error was Socket operation on non-socket
>> [2008/01/08 10:32:26, 0] lib/access.c:check_access(327)
>> [2008/01/08 10:32:26, 0] lib/util_sock.c:get_peer_addr(1232)
>>   getpeername failed. Error was Socket operation on non-socket
>>   Denied connection from  (0.0.0.0)
>>
>> I also found this in the log.smbd file:
>>
>> [2008/01/07 11:18:51, 0] smbd/server.c:main(944)
>>   smbd version 3.0.25a started.
>>   Copyright Andrew Tridgell and the Samba Team 1992-2007
>> [2008/01/07 11:18:51, 0] printing/pcap.c:pcap_cache_reload(159)
>>   Unable to open printcap file /etc/printcap for read!
>> [2008/01/07 11:18:51, 0] printing/pcap.c:pcap_cache_reload(159)
>>   Unable to open printcap file /etc/printcap for read!
>> [2008/01/07 11:18:51, 0] lib/debug.c:reopen_logs(625)
>>   Unable to open new log file /usr/local/samba/log/log.smbd: No such
>> file or directory
>> [2008/01/07 11:18:51, 0] lib/debug.c:reopen_logs(625)
>>   Unable to open new log file /usr/local/samba/log/log.smbd: No such
>> file or directory
>> [2008/01/07 11:18:51, 0] passdb/pdb_smbpasswd.c:startsmbfilepwent(241)
>>   startsmbfilepwent_internal: file
>> /usr/local/samba/private/smbpasswd did not exist. File successfully created.
>> [2008/01/07 11:18:51, 1] lib/account_pol.c:account_policy_get(286)
>>   account_policy_get: tdb_fetch_uint32 failed for field 1 (min
>> password length), returning 0
>> [2008/01/07 11:18:51, 1] lib/account_pol.c:account_policy_get(286)
>>   account_policy_get: tdb_fetch_uint32 failed for field 2 (password
>> history), returning 0
>> [2008/01/07 11:18:51, 1] lib/account_pol.c:account_policy_get(286)
>>   account_policy_get: tdb_fetch_uint32 failed for field 3 (user must
>> logon to change password), returning 0
>> [2008/01/07 11:18:51, 1] lib/account_pol.c:account_policy_get(286)
>>   account_policy_get: tdb_fetch_uint32 failed for field 4 (maximum
>> password age), returning 0
>> [2008/01/07 11:18:51, 1] lib/account_pol.c:account_policy_get(286)
>>   account_policy_get: tdb_fetch_uint32 failed for field 5 (minimum
>> password age), returning 0
>> [2008/01/07 11:18:51, 1] lib/account_pol.c:account_policy_get(286)
>>   account_policy_get: tdb_fetch_uint32 failed for field 6 (lockout
>> duration), returning 0
>> [2008/01/07 11:18:51, 1] lib/account_pol.c:account_policy_get(286)
>>   account_policy_get: tdb_fetch_uint32 failed for field 7 (reset
>> count minutes), returning 0
>> [2008/01/07 11:18:51, 1] lib/account_pol.c:account_policy_get(286)
>>   account_policy_get: tdb_fetch_uint32 failed for field 8 (bad
>> lockout attempt), returning 0
>> [2008/01/07 11:18:51, 1] lib/account_pol.c:account_policy_get(286)
>>   account_policy_get: tdb_fetch_uint32 failed for field 9
>> (disconnect time), returning 0
>> [2008/01/07 11:18:51, 1] lib/account_pol.c:account_policy_get(286)
>>   account_policy_get: tdb_fetch_uint32 failed for field 10 (refuse
>> machine password change), returning 0
>> [2008/01/07 11:18:51, 0] passdb/pdb_interface.c:guest_user_info(256)
>>   guest_user_info: Unable to locate guest account [guest]!
>> [2008/01/07 11:18:51, 0] smbd/server.c:main(1059)
>>   ERROR: failed to setup guest info.
>> [2008/01/07 11:35:09, 0] smbd/server.c:main(944)
>>   smbd version 3.0.25a started.
>>   Copyright Andrew Tridgell and the Samba Team 1992-2007
>> [2008/01/07 11:35:09, 0] printing/pcap.c:pcap_cache_reload(159)
>>   Unable to open printcap file /etc/printcap for read!
>> [2008/01/07 11:35:09, 0] printing/pcap.c:pcap_cache_reload(159)
>>   Unable to open printcap file /etc/printcap for read!
>> [2008/01/07 11:35:09, 0] lib/debug.c:reopen_logs(625)
>>   Unable to open new log file /usr/local/samba/log/log.smbd: No such
>> file or directory
>> [2008/01/07 11:35:09, 0] lib/debug.c:reopen_logs(625)
>>   Unable to open new log file /usr/local/samba/log/log.smbd: No such
>> file or directory
>> [2008/01/07 11:35:09, 0] passdb/pdb_interface.c:guest_user_info(256)
>>   guest_user_info: Unable to locate guest account [guest]!
>> [2008/01/07 11:35:09, 0] smbd/server.c:main(1059)
>>   ERROR: failed to setup guest info.
>> [2008/01/07 11:36:13, 0] smbd/server.c:main(944)
>>   smbd version 3.0.25a started.
>>   Copyright Andrew Tridgell and the Samba Team 1992-2007
>> [2008/01/07 11:36:13, 0] printing/pcap.c:pcap_cache_reload(159)
>>   Unable to open printcap file /etc/printcap for read!
>> [2008/01/07 11:36:13, 0] printing/pcap.c:pcap_cache_reload(159)
>>   Unable to open printcap file /etc/printcap for read!
>> [2008/01/07 11:36:13, 0] lib/debug.c:reopen_logs(625)
>>   Unable to open new log file /usr/local/samba/log/log.smbd: No such
>> file or directory
>> [2008/01/07 11:36:13, 0] lib/debug.c:reopen_logs(625)
>>   Unable to open new log file /usr/local/samba/log/log.smbd: No such
>> file or directory
>> [2008/01/07 11:36:13, 0] passdb/pdb_interface.c:guest_user_info(256)
>>   guest_user_info: Unable to locate guest account [guest]!
>> [2008/01/07 11:36:13, 0] smbd/server.c:main(1059)
>>   ERROR: failed to setup guest info.
>> [2008/01/07 11:56:04, 0] smbd/server.c:main(944)
>>   smbd version 3.0.25a started.
>>   Copyright Andrew Tridgell and the Samba Team 1992-2007
>> [2008/01/07 11:56:04, 0] printing/pcap.c:pcap_cache_reload(159)
>>   Unable to open printcap file /etc/printcap for read!
>> [2008/01/07 11:56:04, 0] printing/pcap.c:pcap_cache_reload(159)
>>   Unable to open printcap file /etc/printcap for read!
>> [2008/01/07 13:39:38, 0] smbd/server.c:main(944)
>>   smbd version 3.0.25a started.
>>   Copyright Andrew Tridgell and the Samba Team 1992-2007
>> [2008/01/07 13:39:38, 0] printing/pcap.c:pcap_cache_reload(159)
>>   Unable to open printcap file /etc/printcap for read!
>> [2008/01/07 13:39:38, 0] printing/pcap.c:pcap_cache_reload(159)
>>   Unable to open printcap file /etc/printcap for read!
>> [2008/01/07 13:47:25, 0] smbd/server.c:main(944)
>>   smbd version 3.0.25a started.
>>   Copyright Andrew Tridgell and the Samba Team 1992-2007
>> [2008/01/07 13:47:26, 0] printing/pcap.c:pcap_cache_reload(159)
>>   Unable to open printcap file /etc/printcap for read!
>> [2008/01/07 13:47:26, 0] printing/pcap.c:pcap_cache_reload(159)
>>   Unable to open printcap file /etc/printcap for read!
>> [2008/01/07 15:39:05, 0] smbd/server.c:main(944)
>>   smbd version 3.0.25a started.
>>   Copyright Andrew Tridgell and the Samba Team 1992-2007
>> [2008/01/07 15:39:05, 0] printing/pcap.c:pcap_cache_reload(159)
>>   Unable to open printcap file /etc/printcap for read!
>> [2008/01/07 15:39:05, 0] printing/pcap.c:pcap_cache_reload(159)
>>   Unable to open printcap file /etc/printcap for read!
>> [2008/01/07 15:39:05, 0] smbd/server.c:main(986)
>>   standard input is not a socket, assuming -D option
>> [2008/01/07 15:39:06, 0] lib/util_sock.c:open_socket_in(830)
>>   bind failed on port 139 socket_addr = 0.0.0.0.
>>   Error = Address already in use
>>
>> (I think most of these entries were from when I was just having
>> trouble getting the smbd working, but it is working now)
>>
>> And I found this in the log.nmbd:
>>
>> [2008/01/07 11:19:35, 0] nmbd/nmbd.c:main(697)
>>   Netbios nameserver version 3.0.25a started.
>>   Copyright Andrew Tridgell and the Samba Team 1992-2007
>> [2008/01/07 11:25:01, 0] nmbd/nmbd_become_lmb.c:
>> become_local_master_stage2(396)
>>   *****
>>
>>   Samba name server ISSNSSX86SLRS is now a local master browser for
>> workgroup ISSNSSSOLARIS on subnet <public ip address>
>>
>>   *****
>> [2008/01/07 11:53:02, 0] nmbd/nmbd.c:process(559)
>>   Got SIGHUP dumping debug info.
>> [2008/01/07 11:53:02, 0] nmbd/nmbd_workgroupdb.c:dump_workgroups(282)
>>   dump_workgroups()
>>    dump workgroup on subnet  <public ip address>: netmask=  255.255.255.0:
>>         CJC(8) current master browser = CJC10151646
>>         ISS(7) current master browser = ISS10150894
>>         ISSNAS(6) current master browser = MPORTER
>>         WORKGROUP(5) current master browser = CAITLIN001
>>         PBCFL(4) current master browser = ISS10130079
>>         PBCGOV(3) current master browser = ISS10160459
>>         MSHOME(2) current master browser = ISSXXXXXX
>>         ISSNSSSOLARIS(1) current master browser = ISSNSSX86SLRS
>>                 ISSNSSX86SLRS 40849a03 (Solaris Samba Server V3.0.6)
>> [2008/01/07 11:55:45, 0] nmbd/nmbd.c:main(697)
>>   Netbios nameserver version 3.0.25a started.
>>   Copyright Andrew Tridgell and the Samba Team 1992-2007
>> [2008/01/07 11:55:45, 0] /bigdisk/SOURCES/I9/samba-3.0.
>> 25a/source/lib/pidfile.c:pidfile_create(111)
>>   ERROR: nmbd is already running. File
>> /usr/local/samba/var/locks/nmbd.pid exists and process id 642 is running.
>> [2008/01/07 13:47:19, 0] nmbd/nmbd.c:main(697)
>>   Netbios nameserver version 3.0.25a started.
>>   Copyright Andrew Tridgell and the Samba Team 1992-2007
>> [2008/01/07 14:51:09, 0] nmbd/nmbd.c:process(559)
>>   Got SIGHUP dumping debug info.
>> [2008/01/07 14:51:09, 0] nmbd/nmbd_workgroupdb.c:dump_workgroups(282)
>>   dump_workgroups()
>>    dump workgroup on subnet  <public ip address>: netmask=  255.255.255.0:
>>         ISSNSSSLRS(1) current master browser = UNKNOWN
>>                 ISSNSSX86SLRS 40809a03 (Solaris Samba Server V3.0.6)
>>
>> How do you get swat to listen on 127.0.0.1?
>>
>> -----Original Message-----
>> From: Ryan Novosielski [mailto:novosirj at umdnj.edu]
>> Sent: Wednesday, January 09, 2008 11:36
>> To: Donald Woeltje; samba
>> Subject: Re: [Samba] Need help with SWAT
>>
> Please keep replies on-list, for various reasons.
> 
> What message do you get after a telnet to port 901? Always give
> messages. For example, can't connect could mean "connection refused"
> or "connection timed out" -- completely different problems. Provide
> ALL information if you want a good answer. Sometimes folks will
> think they can help, but can't be bothered to draw this information
> out and will ignore the message.
> 
> If it is running via inetd, you should not expect to see swat. Look
> for messages in your syslog/messages file. Look at the documentation
> for SWAT to see if there is a debug mode to launch it in (probably
> an option you'd throw in inetd). inetd does not require a reboot, just a kill
> -HUP/kill -1 or on some platforms inetd -c. There are other ways.
> 
> Make sure SWAT is listening on 127.0.0.1. It may be listening only
> on your machine's public interface.
> 
> Some things to start you off. Others can chime in (provided the
> replies stay on-list!) :)
> 
> Donald Woeltje wrote:
>>>> Just one system. No other systems. Swat is installed on the same
>>>> system that is running samba. I'm just trying to use the web browser
>>>> on that system to go to http://localhost:901/ or
>>>> http://<ipaddress>:901/ and I'm unable to get into swat. With swat
>>>> supposed to be started by inetd, with the correct entry in the
>>>> inetd.conf file, I would think that all I'd need to do is reboot and
>>>> inetd should start swat. But if I do a ps -A and look through the
>>>> list, swat isn't running. So, let's say that inetd doesn't start swat
>>>> until a call is made to tcp port 901. That being the case, when I try
>>>> to connect with telnet or the web browser, inetd should start swat and
>>>> I should get a response. But I don't. I even tried starting swat
>>>> manually (I'm used to the Windows environment, where I can start
>>>> applications or services manually) but maybe that's not possible to do
>>>> because when I tried it, it just sat there and sat there and sat there
>>>> and then it finally said, "Alarm clock" and went back to a console
>>>> prompt.
>>>>
>>>> Maybe there a re library files that it needs, to be able to run, and
>>>> even though they may be on my system, it's not able to locate them, so
>>>> it can't start? I know I had that problem when I installed KDE and
>>>> tried to start it from the dtlogin screen. Then someone gave me some
>>>> commands to put into the startkde file, for debugging purposes (the
>>>> debugging output went into a log file), and I was able to find out
>>>> what library files were missing, one by one, until I had them all
>>>> installed and KDE started working. I don't know if that could be the
>>>> same issue here.....and I don't even know how to go about checking to
>>>> see if that is the problem.
>>>>
>>>> -----Original Message----- From: Ryan Novosielski
>>>> [mailto:novosirj at umdnj.edu] Sent: Tuesday, January 08, 2008 23:01 To:
>>>> Donald Woeltje Cc: samba at lists.samba.org Subject: Re: [Samba] Need
>>>> help with SWAT
>>>>
>>>>
>>>>
>>>> Donald Woeltje wrote:
>>>>> No matter what I try, I cannot get SWAT to work. No, I'm new to
>>>>> solaris, so maybe I'm not doing something that should be done prior
>>>>> to trying to use SWAT. Samba does seem to be working, somewhat. I can
>>>>> connect to a share using the smbclient on the same solaris system
>>>>> that I installed samba on....but I cannot connect to the share on the
>>>>> solaris system with my Windows XP system. Since it is part of a
>>>>> domain, it's possible that the sysadmins may have some sort of AD
>>>>> policy in affect that is preventing me from connecting to the solaris
>>>>> system's Windows-compatible resources. So, until I try at home, I
>>>>> can't say definitively that Windows to Samba functionality isn't
>>>>> working at all. It just isn't working from my Windows client to my
>>>>> Solaris Samba network shares. But the smbclient program does connect
>>>>> to the shares successfully.
>>>>> But no matter what I do, I cannot get SWAT to work. I've read the
>>>>> FAQ's and HOWTO's; I can't find anything on troubleshooting SWAT
>>>>> problems. Maybe I don't have inetd setup properly? Or maybe there is
>>>>> something else I've missed.
>>>>> I could really use some help.
>>>> Can't get SWAT to work is very non-specific. It does not tell me what
>>>> to say for you to lead off with. You need to try the standard UNIX
>>>> tests (telnet to the port it's supposed to be running on, etc.) and
>>>> see what exactly is not happening.
>>>>
- --
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

- --
 ---- _  _ _  _ ___  _  _  _
 |Y#| |  | |\/| |  \ |\ |  | |Ryan Novosielski - Systems Programmer II
 |$&| |__| |  | |__/ | \| _| |novosirj at umdnj.edu - 973/972.0922 (2-0922)
 \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHhSATmb+gadEcsb4RAuX4AJ9NN6aGoYT3mVjFHX16NbsAMuRZPACg4xxW
pWYfEsV1OjvQmqLN8352TNQ=
=fNWH
-----END PGP SIGNATURE-----


More information about the samba mailing list