PDA

View Full Version : SlimServer under E-Smith killed access



Storm Dragon
2005-01-05, 14:21
Okay, I'm impressed with the software.
I decided to try it in advance, as I have a line on a good deal on the
hardware ;)

The install went without a hitch, but problems occured afterwards:

Distro: Mitel SME Server (E-Smith)
Kernel: 2.4.20-18.7
File used: slimserver-5.4.0-1.noarch.rpm

When I installed it, it immediately told me to point my browser to
/myserver:9000 to configure everything. The configuration worked like
a charm, but then...

I use iptable redirection to send port 7080 to port 80. That got nuked.

Services httpd and httpd-admin were stopped. Manually restarting
httpd-admin returned my ability to use SME's Server Manager.

Shortly after, users were unable to access my site. After reboot,
access came back, but httpd-admin got shutdown again! Gah!

Excellent playlist manager, but I *do* need that server to stay up for
other things as well :)

Any suggestions?
--
-= Storm Dragon =-
www.StormDragonProductions.com

kdf
2005-01-05, 14:43
Quoting Storm Dragon <stormdragon (AT) gmail (DOT) com>:

> Okay, I'm impressed with the software.
> I decided to try it in advance, as I have a line on a good deal on the
> hardware ;)
>
> The install went without a hitch, but problems occured afterwards:
>
> Distro: Mitel SME Server (E-Smith)
> Kernel: 2.4.20-18.7
> File used: slimserver-5.4.0-1.noarch.rpm
>
> When I installed it, it immediately told me to point my browser to
> /myserver:9000 to configure everything. The configuration worked like
> a charm, but then...
>
> I use iptable redirection to send port 7080 to port 80. That got nuked.
>
> Services httpd and httpd-admin were stopped. Manually restarting
> httpd-admin returned my ability to use SME's Server Manager.
>
> Shortly after, users were unable to access my site. After reboot,
> access came back, but httpd-admin got shutdown again! Gah!
>
> Excellent playlist manager, but I *do* need that server to stay up for
> other things as well :)
>
> Any suggestions?

I'm confused. Maybe I'm reading this wrong, but why do you suspect that a crash
caused by redirecting port 7080 to 80 using iptables has something to do with
slimserver?

Slimserver runs its web server for all things on port 9000. This is
configurable, but it can't be set to 80, nor can you access slimserver web UI
through port 80 unless you manually edit the config files. Mainly, this is to
prevent just such conflicts with other servers using port 80.

-kdf

mherger
2005-01-05, 14:46
[..]
> The install went without a hitch, but problems occured afterwards:
>
> Distro: Mitel SME Server (E-Smith)
> Kernel: 2.4.20-18.7
> File used: slimserver-5.4.0-1.noarch.rpm
>
> When I installed it, it immediately told me to point my browser to
> /myserver:9000 to configure everything. The configuration worked like
> a charm, but then...
>
> I use iptable redirection to send port 7080 to port 80. That got nuked.
>
> Services httpd and httpd-admin were stopped. Manually restarting
> httpd-admin returned my ability to use SME's Server Manager.
>
> Shortly after, users were unable to access my site. After reboot,
> access came back, but httpd-admin got shutdown again! Gah!
>
> Excellent playlist manager, but I *do* need that server to stay up for
> other things as well :)
>
> Any suggestions?

I doubt the relation of your problems to the slimserver installation.
Slimserver IMHO does not touch any of the components you mentioned. Did
you go through your log files to see whether apache left some information
about the reason for its crash? Or did you simply mess up your iptable
rules yourself ;-)?

I have been running slimserver on e-smith for more than a year with no
serious problem at all.

--

Michael

-----------------------------------------------------------
Help translate SlimServer by using the
SlimString Translation Helper (http://www.herger.net/slim/)

Storm Dragon
2005-01-05, 15:10
Exactly right...
Why would any of those simply "conk out?"

Logs didn't show anything out of the ordinary, either.
....and no, I didn't mess up my tables :)

I even had a friend who works for Mitel show up, and he couldn't
figure it out either. I have some maintenance to do on the server
(just uploading MP3s :) tonight, but I'm going to take up my courage
again and reinstall Slim!

Just for my own edification, exactly *how* did you install it yourself?
I saved the rpm to a dir named "installers" in my ibays, but I
couldn't fathom the directory making any difference...


On Wed, 05 Jan 2005 22:46:32 +0100, Michael Herger <slim (AT) herger (DOT) net> wrote:
> [..]
> > The install went without a hitch, but problems occured afterwards:
> >
> > Distro: Mitel SME Server (E-Smith)
> > Kernel: 2.4.20-18.7
> > File used: slimserver-5.4.0-1.noarch.rpm
> >
> > When I installed it, it immediately told me to point my browser to
> > /myserver:9000 to configure everything. The configuration worked like
> > a charm, but then...
> >
> > I use iptable redirection to send port 7080 to port 80. That got nuked.
> >
> > Services httpd and httpd-admin were stopped. Manually restarting
> > httpd-admin returned my ability to use SME's Server Manager.
> >
> > Shortly after, users were unable to access my site. After reboot,
> > access came back, but httpd-admin got shutdown again! Gah!
> >
> > Excellent playlist manager, but I *do* need that server to stay up for
> > other things as well :)
> >
> > Any suggestions?
>
> I doubt the relation of your problems to the slimserver installation.
> Slimserver IMHO does not touch any of the components you mentioned. Did
> you go through your log files to see whether apache left some information
> about the reason for its crash? Or did you simply mess up your iptable
> rules yourself ;-)?
>
> I have been running slimserver on e-smith for more than a year with no
> serious problem at all.
>
> --
>
> Michael
>
> -----------------------------------------------------------
> Help translate SlimServer by using the
> SlimString Translation Helper (http://www.herger.net/slim/)
>
>

mherger
2005-01-05, 15:34
[..]
> Just for my own edification, exactly *how* did you install it yourself?
> I saved the rpm to a dir named "installers" in my ibays, but I
> couldn't fathom the directory making any difference...

I download
http://www.slimdevices.com/downloads/SlimServer_v5.4.0/slimserver-5.4.0-1.noarch.rpm
to some folder on that machine (the folder isn't important at all). Then I
did a
rpm -Uvh slimserver-5.4.0-1.noarch.rpm
as root. I'm not sure whether I had to start the service manually
(/etc/init.d/slimserver start).

That's it. Pretty basic... But do not even try to install the 6.0 branch:
it needs perl 5.8 which is not installed on e-smith.

--

Michael

-----------------------------------------------------------
Help translate SlimServer by using the
SlimString Translation Helper (http://www.herger.net/slim/)

Kirk Ferguson
2005-01-06, 09:01
Quoting kdf <slim-mail (AT) deane-freeman (DOT) com>:

> Quoting Storm Dragon <stormdragon (AT) gmail (DOT) com>:
>
> > Okay, I'm impressed with the software.
> > I decided to try it in advance, as I have a line on a good deal on the
> > hardware ;)
> >
> > The install went without a hitch, but problems occured afterwards:
> >
> > Distro: Mitel SME Server (E-Smith)
> > Kernel: 2.4.20-18.7
> > File used: slimserver-5.4.0-1.noarch.rpm
> >
> > When I installed it, it immediately told me to point my browser to
> > /myserver:9000 to configure everything. The configuration worked like
> > a charm, but then...
> >
> > I use iptable redirection to send port 7080 to port 80. That got nuked.
> >
> > Services httpd and httpd-admin were stopped. Manually restarting
> > httpd-admin returned my ability to use SME's Server Manager.
> >
> > Shortly after, users were unable to access my site. After reboot,
> > access came back, but httpd-admin got shutdown again! Gah!
> >
> > Excellent playlist manager, but I *do* need that server to stay up for
> > other things as well :)
> >
> > Any suggestions?
>
> I'm confused. Maybe I'm reading this wrong, but why do you suspect that a
> crash
> caused by redirecting port 7080 to 80 using iptables has something to do
> with
> slimserver?
>
> Slimserver runs its web server for all things on port 9000. This is
> configurable, but it can't be set to 80, nor can you access slimserver web
> UI
> through port 80 unless you manually edit the config files. Mainly, this is
> to
> prevent just such conflicts with other servers using port 80.
>
> -kdf

FWIW, I'm running that same slimserver rpm on an SME 6.0.1 box without problems.
I suspect that something else is going on.

Kirk