Annoying SWAT oddity
I've observed that if I try to start up the Samba configuration tool SWAT in a web browser (any one), I get the message "Could not connect to host localhost (port 901)." What's both odd and interesting, however, is that if I do: /etc/init.d/xinetd restart I can then connect to and use SWAT just fine. There's clearly a bug here (I've told SuSE about it), but in the meantime, is there a way to patch the startup procedures (I'm running 9.0) to correct the problem? Paul Abrahams
On Thursday 22 January 2004 15:11, Paul W. Abrahams wrote:
I've observed that if I try to start up the Samba configuration tool SWAT in a web browser (any one), I get the message "Could not connect to host localhost (port 901)." What's both odd and interesting, however, is that if I do:
/etc/init.d/xinetd restart
I can then connect to and use SWAT just fine. There's clearly a bug here (I've told SuSE about it), but in the meantime, is there a way to patch the startup procedures (I'm running 9.0) to correct the problem?
Paul Abrahams
Are you sure xinetd is set to start at boot time? Check your Runlevel properties in Yast. Also occasionally there is a sequencing problem with the order in which services are started. Most of the time the services start in the proper order, but occasionally things get out of order if you switch from hard-wired networking to wireless for example. Then you _MAY_ have to manually adjust the start of samba after the pcmcia gets started. -- _____________________________________ John Andersen
On Thursday 22 January 2004 15:11, Paul W. Abrahams wrote:
I've observed that if I try to start up the Samba configuration tool SWAT in a web browser (any one), I get the message "Could not connect to host localhost (port 901)." What's both odd and interesting, however, is that if I do:
/etc/init.d/xinetd restart
I can then connect to and use SWAT just fine. There's clearly a bug here (I've told SuSE about it), but in the meantime, is there a way to patch
On Thursday 22 January 2004 7:46 pm, John Andersen wrote: the
startup procedures (I'm running 9.0) to correct the problem?
Are you sure xinetd is set to start at boot time? Check your Runlevel properties in Yast.
Also occasionally there is a sequencing problem with the order in which services are started. Most of the time the services start in the proper order, but occasionally things get out of order if you switch from hard-wired networking to wireless for example. Then you _MAY_ have to manually adjust the start of samba after the pcmcia gets started.
If xinetd hadn't started, a lot more things wouldn't be working. I'm more inclined to suspect a sequencing problem. Do you know where in the configuration files the startup sequence is specified? I'm also unsure as to whether starting Samba also starts SWAT. Paul Abrahams
The Thursday 2004-01-22 at 22:35 -0500, Paul W. Abrahams wrote:
If xinetd hadn't started, a lot more things wouldn't be working. I'm more inclined to suspect a sequencing problem. Do you know where in the configuration files the startup sequence is specified?
There is no single file specifying that. This has been recently (< 50 days) commented on the list. Read "man init.d" and the chapter "The SuSE boot concept" on the admin book. -- Cheers, Carlos Robinson
On Thursday 22 January 2004 18:35, Paul W. Abrahams wrote:
On Thursday 22 January 2004 7:46 pm, John Andersen wrote:
On Thursday 22 January 2004 15:11, Paul W. Abrahams wrote:
I've observed that if I try to start up the Samba configuration tool SWAT in a web browser (any one), I get the message "Could not connect to host localhost (port 901)." What's both odd and interesting, however, is that if I do:
/etc/init.d/xinetd restart
I can then connect to and use SWAT just fine. There's clearly a bug here (I've told SuSE about it), but in the meantime, is there a way to patch
the
startup procedures (I'm running 9.0) to correct the problem?
Are you sure xinetd is set to start at boot time? Check your Runlevel properties in Yast.
Also occasionally there is a sequencing problem with the order in which services are started. Most of the time the services start in the proper order, but occasionally things get out of order if you switch from hard-wired networking to wireless for example. Then you _MAY_ have to manually adjust the start of samba after the pcmcia gets started.
If xinetd hadn't started, a lot more things wouldn't be working. I'm more inclined to suspect a sequencing problem. Do you know where in the configuration files the startup sequence is specified?
I'm also unsure as to whether starting Samba also starts SWAT.
Paul Abrahams
Paul... Don't confuse xinitd with xinetd. xinetd is responsible for starting swat, and in xinit.d there would be the scripts for starting smb and nmb. The more secure your machine is, the less you have in xinetd, as services like qpopper, ftp, swat, telnet (horrers!) are all started by xinetd, and if it went missing one could run for a long time before noticing. The fact that the OP said /etc/init.d/xinetd restart solved his problem would seem to suggest it was not running. -- _____________________________________ John Andersen
On Thu, 2004-01-22 at 22:35, Paul W. Abrahams wrote:
If xinetd hadn't started, a lot more things wouldn't be working. I'm more inclined to suspect a sequencing problem. Do you know where in the configuration files the startup sequence is specified?
Not true, I don't even have it start at all and have no problems. Depends on what you need it for. -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)
On Thu, 2004-01-22 at 19:11, Paul W. Abrahams wrote:
I've observed that if I try to start up the Samba configuration tool SWAT in a web browser (any one), I get the message "Could not connect to host localhost (port 901)." What's both odd and interesting, however, is that if I do:
/etc/init.d/xinetd restart
This really looks like you don't have xinetd starting when you boot the machine. I would check there first. Just to check issue /etc/init.d/xinetd status before you issue the restart command. -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)
On Friday 23 January 2004 6:53 am, Kenneth Schneider wrote:
On Thu, 2004-01-22 at 19:11, Paul W. Abrahams wrote:
I've observed that if I try to start up the Samba configuration tool SWAT in a web browser (any one), I get the message "Could not connect to host localhost (port 901)." What's both odd and interesting, however, is that if I do:
/etc/init.d/xinetd restart
This really looks like you don't have xinetd starting when you boot the machine. I would check there first.
Just to check issue /etc/init.d/xinetd status before you issue the restart command.
Just did that, and indeed, xinetd is unused. Thanks, Ken. Now the question is: What's the cleanest way to get SWAT going? I could, of course, just ensure that xinetd is started on bootup. But is there a better approach, given that I might not need xinetd's other functions? I'm particularly interested in doing it in a way that would survive a system upgrade. Paul Abrahams
On Fri, 2004-01-23 at 11:35, Paul W. Abrahams wrote:
On Friday 23 January 2004 6:53 am, Kenneth Schneider wrote:
On Thu, 2004-01-22 at 19:11, Paul W. Abrahams wrote:
I've observed that if I try to start up the Samba configuration tool SWAT in a web browser (any one), I get the message "Could not connect to host localhost (port 901)." What's both odd and interesting, however, is that if I do:
/etc/init.d/xinetd restart
This really looks like you don't have xinetd starting when you boot the machine. I would check there first.
Just to check issue /etc/init.d/xinetd status before you issue the restart command.
Just did that, and indeed, xinetd is unused. Thanks, Ken.
Now the question is: What's the cleanest way to get SWAT going?
The safest way is to start xinetd when you want ot run swat and turn it off when youo are through. -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)
* Kenneth Schneider;
Now the question is: What's the cleanest way to get SWAT going?
The safest way is to start xinetd when you want ot run swat and turn it off when youo are through.
or using "only_from " parameter in your configuration is another alternative along with binding it to local addresses . See man xinetd.conf for further deatils -- Togan Muftuoglu | Unofficial SuSE FAQ Maintainer | Please reply to the list; http://susefaq.sf.net | Please don't put me in TO/CC. Nisi defectum, haud refiecendum
On Friday 23 January 2004 11:57 am, Kenneth Schneider wrote:
On Fri, 2004-01-23 at 11:35, Paul W. Abrahams wrote:
Now the question is: What's the cleanest way to get SWAT going?
The safest way is to start xinetd when you want ot run swat and turn it off when you are through.
That'll work, no doubt. But I wonder what the disadvantage would be of leaving xinetd running. Paul Abrahams
On Fri, 2004-01-23 at 15:26, Paul W. Abrahams wrote:
On Friday 23 January 2004 11:57 am, Kenneth Schneider wrote:
On Fri, 2004-01-23 at 11:35, Paul W. Abrahams wrote:
Now the question is: What's the cleanest way to get SWAT going?
The safest way is to start xinetd when you want ot run swat and turn it off when you are through.
That'll work, no doubt. But I wonder what the disadvantage would be of leaving xinetd running.
Paul Abrahams
Security comes to mind. The fewer services you offer the more secure the server. -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)
On Friday 23 January 2004 07:35, Paul W. Abrahams wrote:
Just did that, and indeed, xinetd is unused. Thanks, Ken.
Now the question is: What's the cleanest way to get SWAT going?
The cleanest way is make sure xinetd is running. At the command line (as root) type insserv -d /etc/inid.d/xinetd You can do the same with the runlevel editor in Yast2. -- _____________________________________ John Andersen
The Friday 2004-01-23 at 11:35 -0500, Paul W. Abrahams wrote:
Just to check issue /etc/init.d/xinetd status before you issue the restart command.
Just did that, and indeed, xinetd is unused. Thanks, Ken.
Notice that you might have instead "inetd" running, which was used as default up till SuSE 8.1, and on upgraded systems. Either is usually (and preferably) enabled from Yast/Network Services/Network Services (inetd). But of course, also from services setup, with insserv, with chkconfig... Not a single way. On yast you can also choose which services will inetd/xinetd enable/dissable. -- Cheers, Carlos Robinson
participants (5)
-
Carlos E. R.
-
John Andersen
-
Kenneth Schneider
-
Paul W. Abrahams
-
Togan Muftuoglu