Can't get SWAT to work
I'm running Fedora Core 5 x86_64.
I just installed the rpm for swat and have been trying to follow the installation notes in the man page, but with no success. Firstly, it said to Quote:
Quote:
However, when I navigate to http://127.0.0.1:901/, I just get a "page not found" error. I tried Quote:
Quote:
Thanks |
xinetd has a different syntax from inetd. You can't just add the inetd line to it. This page describes the proper way to set it up:
http://docsrv.sco.com:507/en/samba_help/swat.8.html BTW, It's likely that the distro has already set the proper entry up for you and you just have to edit the last line to say "no" instead of "yes". |
I tried the xinetd installation notes (the man page in the fc5 rpm must be rather outdated, did not have this section).
However, I checked /etc/xinetd.d/swat, and couldn't see anything wrong... Quote:
Switching iptables and firestarter services off makes no difference. What else could be wrong? |
You still have "disable = yes" in the configuration. You need to change that to "no" and restart the service before it will work.
|
Whoops. sorry.
Was about 1 am when I wrote that [EDIT]: For everyone else out there using fedora, I just found this neat feature in system-config-services: If you click the "On Demand Services" tab you can edit all the xinetd services, such as swat, without needing to manually edit files. Swat of course must be checked to enable it. |
Hmmm, no wait
I'm still having problems. I edited /etc/xinetd.d/swat to "disable = no" but though swat is running I still can't access it... I just thought to check the swat log /var/log/samba/swat.log, and this is all there was: Quote:
Now trying "service xinetd reload" as I just read somewhere gets me that Quote:
|
Have you checked iptables again, now you've fixed the other problem?
|
Well, here is the list of commands I use:
Quote:
I tried Eiphany, but that just refused to connect at all (though it did not report a "connection refused" as it would for other blocked ports). I also noticed that I get this firefox message whether or not Swat is actually running!! Alternatively, if I do not "chkconfig swat on/manually edit /etc/xinetd.d/swat "disable" to "no", then I just get a "connection refused" like I would for any blocked port. Here is service --status-all; would this be relevant? Quote:
|
Sorry looks like you're better at this than me, but I've checked my core1 and core3 books, that have swat instructions in them, unfortunately they don't shed any light on your problem. What you've done agrees with what they say.
I've managed to get by without swat, using the RH Samba server configuration gui. |
Yeah.
I actually managed to get it working quite straightforwardly on a Fedora Core 6 i386 machine, so I guess the rather unique problems on my FC5 x86_64 must be the result of some fiddling I've done at some point or other. Would be nice if I knew how to fix it, as some guru once said, there is always a way to fix things on linux (supposedly!). But then I guess you can't have everything... If nobody knows, and it hasn't affected anyone else, then I'm not going to spend the next 4 weeks wrapping my head around it! But thanks for your time... |
All times are GMT -5. The time now is 05:11 AM. |