Topic: no access to a particular website

[bugme]

thanks raymitchell.

i was doing the upgrade based on a printout of the postings, and the way that the contribs web pages print out poorly, because of the excessive menu column frame on the left, had word wrapped charlies 3 lines of instructions, making it incomprehensible for me.

i ran the 3rd command dnscache-conf as you mentioned, and we're back in action. sort of.

we tried the websites of problem, and they're still not working, so we're back to square 1.

I tried to update to dnscache-0.5.0-07 but it told me i need a lib file update dependency, which i tried to do, then the lib needed a perl and so on.

now i know what they mean when some users complain about linux dependency hassles.

So i tried to do the tinydns-0.5.0-13 update and that took, and i did a /etc/e-smith/events/actions/tinydns-conf command afterwards to be sure, and seems ok.

what is that conf command for anyway?

Should I do the dnscache-0.5.0-07 to see if that will solve our problem not accessing www.nissan-usa.com?

where do i get the perl PAM thingy?

We did the browser cache bypass/clearing wiki you pointed us to and that didnt matter.

Thanks.


[root]# rpm -Uvh e-smith-dnscache-0.5.0-07.noarch.rpm
error: failed dependencies:
        e-smith-lib >= 1.15.1-19 is needed by e-smith-dnscache-0.5.0-07

[root]# rpm -Uvh e-smith-tinydns-0.5.0-13.noarch.rpm
Preparing...                ########################################### [100%]
   1:e-smith-tinydns        ########################################### [100%]
[root@qube root]# /etc/e-smith/events/actions/tinydns-conf

[root@qube root]# rpm -Uvh e-smith-lib-1.15.1-36.noarch.rpm  
error: failed dependencies:
        perl(Authen::PAM) is needed by e-smith-lib-1.15.1-36

[bugme]

thanks raymitchell.

i was doing the upgrade based on a printout of the postings, and the way that the contribs web pages print out poorly, because of the excessive menu column frame on the left, had word wrapped charlies 3 lines of instructions, making it incomprehensible for me.

i ran the 3rd command dnscache-conf as you mentioned, and we're back in action. sort of.

we tried the websites of problem, and they're still not working, so we're back to square 1.

I tried to update to dnscache-0.5.0-07 but it told me i need a lib file update dependency, which i tried to do, then the lib needed a perl and so on.

now i know what they mean when some users complain about linux dependency hassles.

So i tried to do the tinydns-0.5.0-13 update and that took, and i did a /etc/e-smith/events/actions/tinydns-conf command afterwards to be sure, and seems ok.

what is that conf command for anyway?

Should I do the dnscache-0.5.0-07 to see if that will solve our problem not accessing www.nissan-usa.com?

where do i get the perl PAM thingy?

We did the browser cache bypass/clearing wiki you pointed us to and that didnt matter.

Thanks.


[root]# rpm -Uvh e-smith-dnscache-0.5.0-07.noarch.rpm
error: failed dependencies:
        e-smith-lib >= 1.15.1-19 is needed by e-smith-dnscache-0.5.0-07

[root]# rpm -Uvh e-smith-tinydns-0.5.0-13.noarch.rpm
Preparing...                ########################################### [100%]
   1:e-smith-tinydns        ########################################### [100%]
[root@qube root]# /etc/e-smith/events/actions/tinydns-conf

[root@qube root]# rpm -Uvh e-smith-lib-1.15.1-36.noarch.rpm  
error: failed dependencies:
        perl(Authen::PAM) is needed by e-smith-lib-1.15.1-36

[CharlieBrady]

In fact I found :

e-smith-tinydns-0.5.0-13.noarch.rpm

Thanks for SME 7. Don't try to use that.

[raem]

bugme

> making it incomprehensible for me.

If you don't understand what you are doing then you should not be doing it.
At least learn the basics of an instruction like the one Charlie posted and then you will be able to more accurately interpret/read what the command is.

Read some of the many howtos that are around to see what the sequence of events is.

I would advise against randomly installing other rpms just because they are there and have a newer version number and look like they might do something for you. As Charlie said, that rpm is for sme7 and will most likely cause problems on other version sme servers.

Uninstall the newer
e-smith-tinydns-0.5.0-13.noarch.rpm
and reinstall the earlier version from the CD.

You should always look at the changelog of an rpm before installing it to see what version it is for and what changes have been made etc & whether they are applicable to your situation.

You can do this a number of ways. An easy one is to use mc, highlight the file, press enter and then select info/changelog/view

do man rpm to find out more about using the rpm command in many ways.

The command of Charlies was really 2 parts, one to download the file from a site and the second to expand templates, configure and restart services etc (very generally speaking).

If in doubt for any situation you can always do
/sbin/e-smith/signal-event post-upgrade
/sbin/e-smith/signal-event reboot


> .... they're still not working...

Not working is very poor information, it tells us nothing. You need to give the exact error message you receive.

You have possibly stuffed things up by installing other unneccessary (and wrong) rpms).

In my case after updating the e-smith-dnsache rpm and running the conf command and clearimg the browsers caches, the non working sites then worked OK for me.


> now i know what they mean when some users complain > about linux dependency hassles.

Especially users who don't know what they are doing !

If you are getting those sorts of problems then you are generally installing something wrongly or inappropriately.
Most released rpms packages will also have the required dependencies with them, so if they don't then you are on your own and need to know what you are doing.
It just means that a certain rpm requires other rpms in order to function, and the rpm command is advising you of that (and protecting you too). You would need to manually locate those other dependent rpms and install those too, and in the correct order.

By having all the required rpms in the same folder and issuing a rpm -Uvh *.rpm
then the rpm command will install them in the correct order and take care of depedency issues.

Only do this though if you understand what and why you are doing it. If you don't iunderstand it then you probably should not be doing it.


> did the browser cache clearing & that didnt matter.

I think that was your remaining problem, after clearing (Ctrl F5 etc) try restarting your browser.

Here's what I have on my sme 6.0 server

rpm -q e-smith-dnscache
e-smith-dnscache-0.3.0-04

rpm -q e-smith-tinydns
e-smith-tinydns-0.5.0-12

rpm -q e-smith-lib
e-smith-lib-1.14.0-07

I can access the site http://www.nissanusa.com/
quite OK


Good luck
Ray

[bugme]

Ray,

Thanks for all your newbie guidance.

I was pretty much aware of those issues, as i have had to have all the dependencies in order to install spam assassin and clamav previously.

its just that i do it so seldom, that i pretty much forget and start all over again.

I am currently studying for the LPI institute Linux Admin exam so I hope to be more proficient.

i wish i had more sme's deployed, but at this time, i only have 1 office that was willing to give it a go.

i had an office on a linux server and switched to a ms sbs 2003 for $8k, and 3 months later, found they needed large email attachment support, and had to spend another $4k for ms exchange enterprise edition.
i was not involved in their entire ms sbs decision and switchover, so it's really up to them now.


anyway, i did a search in the forums but can't seem to find a way to bypass or disable squid proxy.

that might be my best shot to have our web designers be able to access www.nissan-usa.com as part of their job requirement.

i installed squidproperties and have flushed cache, and entered url to bypass squid, but its not helping us to access these problematic sites.

thanks again!

[CharlieBrady]

anyway, i did a search in the forums but can't seem to find a way to bypass or disable squid proxy.

that might be my best shot to have our web designers be able to access www.nissan-usa.com as part of their job requirement.

Bypassing squid will not help. If the hostname is not resolvable in DNS for squid, it won't be for the client's browser either. You need to discover why dnscache is not resolving the name. The dnscache log files will likely contain the answers to that.