Summary: | cant connect to swat (500 Server Error) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Iain Buchanan <iaindb> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | CC: | pete4abw |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Iain Buchanan
2006-02-02 15:59:31 UTC
Uhm, it might be a good idea to enable swat in /etc/xinetd.d/swat first, restart xinetd and configure the thing. For support questions, use forums.gentoo.org, mailing lists or #gentoo on freenode - not bugzilla. umm.... > Uhm, it might be a good idea to enable swat in /etc/xinetd.d/swat first, Correct me if I'm wrong, but if swat was disabled in /etc/xinetd.d/swat, then I would get a "connection refused". The 500 server error is coming from swat, hence it must be enabled in xinetd: $ grep disable /etc/xinetd.d/swat disable = no > restart xinetd and configure the thing. the "thing"? What thing? xinetd? What is there to configure apart from the above line already? > For support questions, use > forums.gentoo.org, mailing lists or #gentoo on freenode - not bugzilla. I have. I try and keep bug reports concise. I don't usually add "I've asked on gentoo-user" or similar, but if you like: 1. I asked on gentoo user. The suggestions were to make sure swat was uncommented from /etc/services (it always was) and to make sure "disable=no" in /etc/xinetd.d/swat (it is). 2. google. Not many hits, the only almost-useful one referencing a non-existant section of a 900+ page manual. Another one solved the problem by upgrading from 3.0.10 to 3.0.11 (I have 3.0.20b). I just spent another 1/2 hour looking and still couldn't find anything to help me. Hence, I think it is a bug. I only just installed my machine, if I install xinetd, install samba, enable swat, start xinetd, I should be able to connect to localhost:901 yeah? Reopen with relevant log entries you get when you are trying to use swat. Hi, I added the line server_args = --debuglevel=10 to /etc/xinetd.d/swat (and restart xinetd of course ;) /var/log/messages: Feb 3 20:45:48 orpheus xinetd[8804]: START: swat pid=12397 from=127.0.0.1 Feb 3 20:45:48 orpheus xinetd[8804]: EXIT: swat status=0 pid=12397 duration=0(sec) /var/log/samba/log.swat - nothing! That's all I could find - it doesn't look very helpful! Any other log files I might have missed? thanks. Reopen with something useful, please... --logfile=logdirectory Did you actually set USE=swat for net-fs/samba? OK, sorry about the delay, I've been busy :) I added the swat use flag to samba, and upgraded to samba-3.0.21b, and I can now use swat (without editing /etc/xinetd.d/swat or anything else). If you want to chase it, I can re-compile _without_ the swat use flag, as IMHO if swat isn't supposed to work without the swat use flag, then swat shouldn't be installed, neither should /etc/xinetd.d/swat. So, what would you like me to do next? I just noticed the note at the end of the emerge (of course, since I don't sit and watch it, I did not see it while compiling): einfo "As of 3.0.20b: New USE flags: ldapsam, swat (default: disabled)" I _am_ glad to see swat as a use flag. This is something long overdue. See bug # 81387. Good work. |