Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 121371 - cant connect to swat (500 Server Error)
Summary: cant connect to swat (500 Server Error)
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-02 15:59 UTC by Iain Buchanan
Modified: 2006-03-29 03:35 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Iain Buchanan 2006-02-02 15:59:31 UTC
Hi,

I have net-fs/samba-3.0.20b and sys-apps/xinetd-2.3.14

When I connect to http://localhost:901/ from firefox, I get this error:

500 Server Error
chdir failed - the server is not configured correctly

I also tried netcat (note, I typed the GET line below):
$ nc localhost 901
GET /
HTTP/1.0 500 Server Error
Connection: close
Content-Type: text/html

<HTML><HEAD><TITLE>500 Server Error</TITLE></HEAD><BODY><H1>500 Server Error</H1>chdir failed - the server is not configured correctly<p></BODY></HTML>

The samba service is started.  I have a basic smb.conf file, but I also tried with an empty smb.conf file.

A user suggestiod trying swat (/usr/sbin/swat --debuglevel=9) from the comand line.  Again, I typed "GET /" and I get the same response as netcat.

I am stumped!

$ emerge --info
Portage 2.1_pre4-r1 (default-linux/x86/2005.0, gcc-3.3.6, glibc-2.3.6-r2, 2.6.15-suspend2-r4 i686)
=================================================================
System uname: 2.6.15-suspend2-r4 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz
Gentoo Base System version 1.12.0_pre15
distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled]
dev-lang/python:     2.3.4-r1, 2.4.2
sys-apps/sandbox:    1.2.17
sys-devel/autoconf:  2.13, 2.59-r7
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.16.1-r1
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r3
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -march=pentium4 -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/texmf/web2c /etc/env.d"
CXXFLAGS="-O2 -march=pentium4 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks fixpackages parallel-fetch sandbox sfperms strict"
GENTOO_MIRRORS="ftp://arion/pub/gentoo-portage/ ftp://mirror.isp.net.au/pub/gentoo/ ftp://gg3.net/pub/linux/gentoo/ ftp://gentoo.ccccom.com ftp://ftp.ussg.iu.edu/pub/linux/gentoo"
LANG="en_AU.UTF-8"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 X alsa arts avi berkdb bitmap-fonts crypt cups eds emboss encode foomaticdb fortran gdbm gif gnome gpm gstreamer gtk gtk2 imlib ipv6 jpeg kde libg++ libwww mad mikmod motif mp3 mpeg ncurses nls ogg oggvorbis opengl pam pdflib perl png python quicktime readline sdl spell ssl tcpd truetype truetype-fonts type1-fonts vorbis xml2 xv zlib elibc_glibc kernel_linux userland_GNU"
Unset:  ASFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2006-02-02 16:56:58 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.
Comment 2 Iain Buchanan 2006-02-02 18:01:17 UTC
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?
Comment 3 Jakub Moc (RETIRED) gentoo-dev 2006-02-02 23:45:59 UTC
Reopen with relevant log entries you get when you are trying to use swat.
Comment 4 Iain Buchanan 2006-02-03 03:26:07 UTC
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.
Comment 5 Jakub Moc (RETIRED) gentoo-dev 2006-02-03 04:33:16 UTC
Reopen with something useful, please...

--logfile=logdirectory
Comment 6 Maximilian Grothusmann 2006-02-03 14:49:17 UTC
Did you actually set USE=swat for net-fs/samba?
Comment 7 Iain Buchanan 2006-02-08 22:31:23 UTC
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?
Comment 8 Peter Hyman 2006-03-29 03:35:11 UTC
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.