Results 1 to 11 of 11
-
08-05-2002, 09:47 AM #1Registered User
- Join Date
- Mar 2002
- Posts
- 125
*ouch* my webmin stopped working as it should
Hello,
I'd be very happy if somebody out there could help me. I do really not understand whats going on.
System: Red Hat 7.2
Webmin: 0.9x - 0.990
2 weeks ago I've tried to change the password of one of my "linux user accounts". After seeing the browser loading for about 4 minutes the browser hang and told me error 500.
Since then, every time I try to add a new user I get error 500! I did update webmin (directly by using the webmin update feature) hoping this stuff would be fixed... but nothing.
I've no idea where to start looking, all I get is error 500 when trying to add a new user or change the password of a already created user.
Any help? Thanks a lot in advance!
p.s. I did never play around with the sourcecode, I can not think of one thing I've done which could have messed webmin up.
-
08-05-2002, 02:19 PM #2Linux Problems Solved.
- Join Date
- Dec 2001
- Location
- Los Angeles, CA
- Posts
- 1,337
Did you install the RPM or the source ?
Ronny Fang
Linux Problems Solved. | Built for the Hosting Industry
Server Management. Node Management. Helpdesk Management.
( AcuNett, Est. 15 Years, RateLobby 5 Stars )
-
08-05-2002, 04:21 PM #3Registered User
- Join Date
- Mar 2002
- Posts
- 125
first time installation: rpm
updates: rpm
please note that webmin did always work fine until this problem come out. The problem was not caused by an update
-
08-06-2002, 12:27 AM #4Junior Guru Wannabe
- Join Date
- Aug 2002
- Posts
- 56
Protector... I have used Webmin for a long time and have NEVER had a 500 error. I cannot imagine what happened. Then again I have never installed the rpm version. Try removing the rpm and reinstalling it in case file permissions got hosed.
-
08-06-2002, 02:53 AM #5Registered User
- Join Date
- Mar 2002
- Posts
- 125
Indy, thanks a lot for your reply!
In fact this is wired coz I know so many webmasters using webmin without any problem....
Is there a suggested method for uninstalling webmin? I'm quite worried about not beeing able to do a clean uninstall... and to cause further problems on my box.
Thanks indeed for any suggestion.
-
08-06-2002, 03:21 AM #6Web Hosting Master
- Join Date
- Jan 2002
- Location
- Melbourne, AU
- Posts
- 740
According to the FAQ, its:
Just run the command /etc/webmin/uninstall.sh .
If you have installed the RPM version of Webmin, you can also use rpm -e webmin, or if you have installed the Solaris package you can use pkgrm WSwebmin
Lats...
-
08-06-2002, 04:14 AM #7Registered User
- Join Date
- Mar 2002
- Posts
- 125
linux help
hello again,
thanks for the info. did some of you already try the uninstall? I did check out the webmin documentation as well.... but would be nice to know if some of you had any trouble with it.
something else...
due to the fact I'm without webmin right now. could you please tell me the commands to:
- create a new group
- create a new user without shell access
thanks a lot
chris
-
08-06-2002, 02:29 PM #8Web Hosting Master
- Join Date
- Aug 2002
- Posts
- 655
Chris,
I have never come across with a 500 error with webmin in my 3+ years of exp. with it but have many a time removed and re-installed both the rpm and source, take lats advice and re-install, may some file permissions are messed up.
As for creating a new group do a "man groupadd" and "man useradd" for adding a use, allocating a /bin/false would diable shell access.
Hope that helps.
Viv
-
08-06-2002, 05:16 PM #9Registered User
- Join Date
- Mar 2002
- Posts
- 125
hi Viv,
thanks a lot for your advice. going to create the needed users manually.... and than I'll follow Lats advice.
cheers
chris
-
08-07-2002, 08:15 AM #10Web Hosting Master
- Join Date
- Apr 2002
- Location
- Auckland - New Zealand
- Posts
- 1,575
2 weeks ago I've tried to change the password of one of my "linux user accounts". After seeing the browser loading for about 4 minutes the browser hang and told me error 500
-
08-07-2002, 05:10 PM #11Registered User
- Join Date
- Mar 2002
- Posts
- 125
nope... no info in the error_log