Swat SOS

[lovswr]

Hello, Until yesterday (7 nov 03) I had a mostly working 2.27 samba running on my redhat 9 box that I configured via SWAT. Now I can not get back into SWAT & I also (in a useless attempt to make it work) upgraded to samba 3.0 I get the following when trying to start SWAT:


An error occured while loading http://matrix1:901/:


Could not connect to host matrix1 (port 901)



here is my /etc/hosts file:


# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost localhost.localdomain matrix1
192.168.2.147 philip
192.168.2.145 robert
192.168.1.148 pc2
192.168.1.149 freebsd
0.0.0.0 ads.osdn.com
0.0.0.0 claria.com
0.0.0.0 www.gator.com


Also /etc/services does have the correct port 901 set up & /etc/xinetd/d/swat

description: swat is the Samba Web Administration Tool, which
# allows an administrator to configure Samba using a web
# browser interface, with the URL http://localhost:901
service swat.
{
disable = no
socket_type = stream
wait = no
protocol = tcp
only_from = matrix1
user = root
log_on_failure += USERID
server = /usr/sbin/swat
port = 901
}
& /etc/pam.d/samba

#%PAM-1.0
auth required pam_nologin.so
auth required pam_stack.so service=system-auth
account required pam_stack.so service=system-auth
session required pam_stack.so service=system-auth
password required pam_stack.so service=system-auth
# added by me in a panic attempt to get swat working again on 7 nov 03
samba auth required /lib/security/pam_pwdb.so nullok shadow
samba account required /lib/security/pam_pwdb.so


I dont't know if this is related but,my trouble started yesterday after I actually got vnc-server working. I just left it at default so it started on matrix1:1 I went to work (yes I puched a hole through turtlefirewall just for this) & connected from my laptop at work via vnc to the redhat box. I did not do anything & then jsut logged off. when I got home I had to reboot the redhat box becuase konq would not work. Kept complaing aobut something like the DHOCP server or other could not be contactacted/(connected?). Well SWAT has not worked ever since. Now the samba 2.7 still worked with a manual start, but this morning I did a rpm -U| to 3.0 & now that too is not working Any help ir direction pointing would be greatly appreciated.

[Void Main]

Are all of the necessary services set to start at bootup?

Code: Select all

# chkconfig --list swat
# chkconfig --list smb
# chkconfig --list xinetd


and are they running?

Code: Select all

# service xinetd status
# service smb status


If the answer to any of the above is no then you need to determin why they are not running and get them running. Usually log files are instrumental in solving these issues, most notably /var/log/messages and /var/log/samba/*. Restart the services while watching the end of the logs.

e.g. In one shell window:

Code: Select all

# tail -f /var/log/messages


In another:

Code: Select all

# service xinetd restart


Watch for error messages etc. Also use your "smbstatus" command. You can increase the Samba debugging level using that command as well as other useful functions. See "man smbstatus". If you see error messages, plug them into a Google prompt and see what comes back.

[lovswr]

Thks for the prompt reply Void. I did as you suggested & I get divirgent results. The chkcong --list show xinetd & smb to be off on consoles 0 thru 6. The service status of the same show them both to be running.

[Void Main]

xinetd (and all other services for that matter) should be off for runlevel 0 and 6. The xinetd service should be on in at least the runlevel that you have set as your default, but usually you turn it on for runlevel 3, 4, and 5 by:

Code: Select all

# chkconfig xinetd on


Now, if it really is running you should be able to telnet to port 901 and not get an error:

Code: Select all

# telnet localhost 901


Also, I assume you are trying to access swat from the same machine it is running on. If you are not then you'll need to change the xinetd access (comment out the only_from line or modify it accordingly). Do you get any "xinetd" messages at the end of /var/log/messages after trying a restart?

# service xinetd restart

[lovswr]

Below is everyting that popped up in the messages window after I restarted xinetd. The only thing that I can make out (I think) is that at the bottom it says that I do not have tcp/901 is /etc/services....that is false, 'cause it is.

Yes I am running smb on the same machine & no, it will not let me telnet...it tells me connection refused


Nov 8 17:18:45 localhost kernel: TFW FIREWALL-waplan:IN= OUT=eth2 SRC=192.168.2
.1 DST=192.168.2.255 LEN=241 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=138
DPT=138 LEN=221
Nov 8 17:18:45 localhost nmbd[14543]: send_netbios_packet: send_packet() to I
P 192.168.2.255 port 137 failed
Nov 8 17:18:45 localhost kernel: TFW FIREWALL-wirelan:IN= OUT=eth1 SRC=192.168.
1.1 DST=192.168.1.255 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137
DPT=137 LEN=58
Nov 8 17:18:45 localhost nmbd[14543]: [2003/11/08 17:18:45, 0] nmbd/nmbd_namequ
ery.c:query_name(237)
Nov 8 17:18:45 localhost kernel: TFW FIREWALL-waplan:IN= OUT=eth2 SRC=192.168.2
.1 DST=192.168.2.255 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137
DPT=137 LEN=58
Nov 8 17:18:45 localhost nmbd[14543]: query_name: Failed to send packet tryin
g to query name MATRIX<1d>
Nov 8 17:18:54 localhost kernel: TFW internet-FIREWALL:IN=ppp0 OUT= MAC= SRC=66
.149.223.242 DST=edited static ip LEN=92 TOS=0x00 PREC=0x00 TTL=119 ID=36859 PROTO=
ICMP TYPE=8 CODE=0 ID=512 SEQ=15796
Nov 8 17:20:12 localhost su(pam_unix)[15948]: session opened for user root by l ovswr(uid=500)
Nov 8 17:20:12 localhost kernel: TFW internet-FIREWALL:IN=ppp0 OUT= MAC= SRC=66 .0.202.47 DST=edited static ip LEN=48 TOS=0x00 PREC=0x00 TTL=117 ID=48526 DF PROTO= TCP SPT=4564 DPT=135 WINDOW=8760 RES=0x00 SYN URGP=0
Nov 8 17:20:15 localhost kernel: TFW internet-FIREWALL:IN=ppp0 OUT= MAC= SRC=66 .149.14.50 DST=edited static ip LEN=92 TOS=0x00 PREC=0x00 TTL=124 ID=59326 PROTO=IC MP TYPE=8 CODE=0 ID=768 SEQ=57469
Nov 8 17:20:54 localhost su(pam_unix)[16022]: session opened for user root by l ovswr(uid=500)
Nov 8 17:20:55 localhost kernel: TFW internet-FIREWALL:IN=ppp0 OUT= MAC= SRC=66 .151.200.244 DST=edited static ip LEN=92 TOS=0x00 PREC=0x00 TTL=117 ID=58638 PROTO= ICMP TYPE=8 CODE=0 ID=768 SEQ=19807
Nov 8 17:21:03 localhost su(pam_unix)[16022]: session closed for user root
Nov 8 17:21:17 localhost xinetd[15049]: Exiting...
Nov 8 17:21:17 localhost xinetd: xinetd shutdown succeeded
Nov 8 17:21:17 localhost xinetd[16080]: service/protocol combination not in /et c/services: swat./tcp
Nov 8 17:21:18 localhost xinetd[16080]: xinetd Version 2.3.11 started with libw rap loadavg options compiled in.
Nov 8 17:21:18 localhost xinetd[16080]: Started working: 2 available services
Nov 8 17:21:20 localhost xinetd: xinetd startup succeeded

[Void Main]

Change "service swat." in your /etc/xinetd.d/swat to "service swat" (get rid of the "." at the end) then restart xinetd.

[lovswr]

Change "service swat." in your /etc/xinetd.d/swat to "service swat" (get rid of the "." at the end) then restart xinetd.

I was just about to tell you that I had noticed that syntax error upon further examination myself

Now since I destoyed my old smb.conf when I upgraded from 2.7 to 3.0 it keeps saying it can not initilize the SAM_ACCOUNT for my users. I know that I have to chmod my users or the password file or something like that. I'll keep looking.

[lovswr]

Well it looks like even thoughg pam is installed it is now set up for anything as /ect/pam/conf is just a blank file. I guess that would explain the SAM_ACCOUNT error I get whenever I try to add any samba users via SWAT.

Man pam made me even more confused. Is there some kind of way to use samba 3.0 without the pam stuff?