Koozali.org: home of the SME Server
Legacy Forums => General Discussion (Legacy) => Topic started by: Neil Hart on September 10, 2001, 06:47:30 PM
-
Hello
I think that I've broken the e-smith-manager :-(
When I try and use the text browser from the admin screen, it asks me for the admin password, launches lynx and then lynx reports the following...
Forbidden 403
You don't have permission to access /common/noframes on this server.
When I try and log into http://192.168.1.1/e-smith-manager from a windows machine on the network, it doesn't ask for a username and password, I just reports that access is denied.
I was working fine on Friday (it's now Monday).
What I did do this morning however, was to install some contributed RPMs (e-smith-isp and LinkStatus). I uninstalled them with 'rpm -e', but still doesn't work.
What did I do wrong? Or, how can I fix it?
Cheers
Neil
-
Neil,
Here's a link to the answer which helped me (when I had a similar problem a few weeks back), seems you have to run some chmod commands.
http://forums.contribs.org/index.php?topic=2157.msg7235#msg7235
Good luck, hope it fixes your problem as well.
Regards,
Patrick
-
Thanks
It did the trick :-)
Neil
-
Neil Hart wrote:
> What I did do this morning however, was to install some
> contributed RPMs (e-smith-isp and LinkStatus). I uninstalled
> them with 'rpm -e', but still doesn't work.
>
> What did I do wrong?
You installed some faulty contrib RPMs (or ones which are compatible with e-smith 3.1, but not 4.x).
> Or, how can I fix it?
Remove the contrib RPMs. Then do:
/sbin/e-smith/signal-event post-upgrade
/sbin/e-smith/signal-event reboot
Regards
Charlie
-
Thanks for the reply.
Would it, therefore, be a good idea for e-smith to include a 'built-for-version' or 'tested-on-version' entry somewhere on the download pages?
Neil
-
Neil Hart wrote:
> Would it, therefore, be a good idea for e-smith to include a
> 'built-for-version' or 'tested-on-version' entry somewhere on
> the download pages?
Most of the packages already have this information listed. However, since these are publically contributed modules, this does *NOT* guarantee that these modules will work properly. They're all "install at your own risk".