I have much bigger problems than this right now, the hard disk swap and restore is not going well at all. However, this is bad enough, I can't even get SSH installed!

The first time I upgraded SSH when I initially got this box I just used...

# up2date openssh

and it was done but now when I try to use up2date for this or anything else I get this error...

Error Message:
Abuse of Service detected for server localhost.localdomain (1000638861)
Error Class Code: 49
Error Class Info:
You are getting this error because RHN has detected an abuse of
service from this system and account. This error is triggered when
your server makes too many connections to Red Hat Network. This
error can not be triggered under a normal use of the Red Hat Network
service as configured by default on Red Hat Linux.

The Red Hat Network services for this server will remain disabled
until you will reduce the RHN network traffic from your system to
acceptable limits.

Please contact rhn-feedback@redhat.com if you think you have
received this message in error.

I did write them last night and have not received an answer. I have changed my hostname from the default (plesk.rackshack.net) using linuxconf and the hostname command reports the change ok after a reboot. I can not run the reconfigurator.sh program because of major sql password problems related to plesk that the RS techs have not been able to correct yet so I don't know if the hostname has been completely changed in PSA or not.

Ok, fine, if I can't use up2date I thought I would download the RPM file from RHN and install it myself.

[root@plesk /tempdl]# rpm -Fvh openssh-3.1p1-1.i386.rpm
error: failed dependencies:
openssh = 2.9p2-11.7 is needed by openssh-clients-2.9p2-11.7

Ok, fine, I went and got the source from openssh.org (the RPM's there are for 7.2) and tried to do a build on my box...

[root@plesk /tempdl]# rpm --rebuild openssh-3.2.2p1-1.src.rpm
Installing openssh-3.2.2p1-1.src.rpm
error: failed build dependencies:
XFree86-devel is needed by openssh-3.2.2p1-1
gnome-libs-devel is needed by openssh-3.2.2p1-1

Question #1: Why can't RS clients access RHN up2date
Question #2: Any ideas on how I can install openssh?

Rick

1. You can just give in and download all the dependencies rpm tells you you need and install them.

2. You can do an install that doesn't verify dependencies - add --nodeps to the command.

3. You can download the tarball for OpenSSH, and compile it. It installs easily over an rpm version, uses the same directories, and works fine. Does break the ability to do rpm in the future for that program though...

4. As for the Rackshack block, there must be many machines that are identified as plesk.rackshack.net, so you're on the right track in changing the name. But - did you restart everyting afterwards? Or better yet - reboot - just to make sure the new name is being used?

yes, I did a reboot, needed for the hostname change in linuxconf. However, since I can not run the reconfigurator program, I am not sure if Plesk has the hostname correct. A hostname command from shell does report the new one. Thanks for the advice, I will try installing ssh from the source.

Rick

You need more than just openssh-3.1..., you need openssh, openssh-clients, and openssh-server. Download all three, then do:
rpm -Uhv openssh*

Yes meballard, that worked fine, thank you!

The restore from hell is over and everything is looking fine. Up2date still will not work though, same error. Is anyone else on RS having problems connecting to RHN? It is not my hostname, that change is finished and double checked.

Rick

I have been quite frequently in recent times (pathetically slow), although when I tried it just now it worked just fine.

Yes I am having this problem. Registered
a week ago. Got the first two updates right off
and have not connected since. I have several
updates listed as needed but unable to connect.
RHN is running at 120 intervals but no updates.

I don't know if you mean that you are being refused because of your server ID or if you just can't get on because of high traffic and your not a "premium" member.

My problem was the server name and I ended up having to re-register with RHN (rhn_register at the command prompt) before it would apply the the correct hostname on our server and allow access. I tried editing the config and half a dozen other things but nothing worked.

Once re-registered I deleted the system on the account from the original registration and everything has worked fine since. It has been very busy lately though so if that is your problem, try doing your up2date commands late, late at night and you should be able to get through.

Hope that helps.

Rick

I don't think the server name is the problem since I changed it
long before registering.
The registeration went well. I received two updates in the first
two hours but have not received any since. When I go to schedule
for updates it tells me:
This system has not checked into the Red Hat Network recently. Since a system cannot be updated if it does not check in to RHN, it is unlikely that this action will succeed.
The last check in was 2002-06-30 15:47:17 -0800 (PST).
It is supposed to check in every 120 minutes.
It does seem to check in but no updates.

Heck, I don't have a clue what that is all about, to my knowledge, ours never "checks in" automatically for updates. This may be a setting you control from your account on the RHN web site or through the config util on your box. (rhn_configure I think but don't quote me on that, might have to do a locate if that is not the correct command).

When I need something or when I get an RHN notice I manually use up2date from shell to grab the package, ie...

# up2date open_ssh

I don't just grab a package because it is available and I would not let it update everything on the system that it says is out of date. For instance, there is no reason to update xwindows stuff when you never use it and remote x should be disabled anyway.

Try logging into your account from the RHN site and see if you can fix your problem through the interface there.

Rick

Ric
I must be stupid but I can't figure out how to do
manual downloads and installs.
Do you have a how to?

Thanks

Oh common, if you you were stupid you wouldn't be here, most of us fight this stuff daily, it's just a learning process.

to use up2date from the command line just type in this command...

# up2date [package to update]

If I needed to update open ssh the command would be...

# up2date open_ssh

You may have to do a locate command and use the full path to up2date, ours is in /usr/sbin/up2date

# locate up2date

to find it (probably in the same dir as ours) and then

# /usr/sbin/up2date [package to update]

to use it. You will have to be logged in as root (su) to use up2date, hope that helps.

Rick

I've noticed that up2date is more trouble than it's worth

Stick with the good and trusty RPM.

I am always up working late late so seldom have a problem getting connected even though RHN has been very busy recently.

I have found that for some things up2date works really well, quick and easy. You have a valid point though, it is nearly as easy to obtain the RPMs from RHN or rpmfind... a wget and rpm command takes no time at all.

My biggest complaint about RHN is the amount of time it takes them to get a package released unless it is a real serious security issue. On most important stuff I have compiled the thing from source long before the rpm file was available from RHN.

Rick

Rick, ever since we first updated that pgm from RH nework it has stopped working on our Ensim box. I doubt its your hostname. Its got to be something else. I never use the update feature anymore. Its more of a hassle than anything.

I did get that fixed, had to remove the existing system from RHN and redo the rhn_register. I do use up2date ocasionally but see the previous post to see why I don't care for RHN in general, they take far to long to get packages out.

Rick

Hmmm so it's not me who's having problems with RHN.... rhn_register seems to randomly crash at various stages of the registration process and kill my ssh session

The one time RHN appeared to show my box being registered I waited 3 days for rhnsd to upload a list of my packages and it never did. I'm relying on RHN to upgrade my apache as I'm on the RPM version of Plesk now and the standard RPM provided by Red Hat has huge dependency problems

I know this won't help people with remote access to RS servers but if you have a local linux box, the Red Carpet app under gnome blows the RHN up2date app away. It does the same thing, is way faster and does not produce the errors that occasionally occur using up2date locally. Plus, it offers packages that can not be obtained through up2date.

I don't know if Red Carpet is installed on our boxes here and I don't know if it can be used from the command line in text mode, never looked into it.

More importantly, you should know that upgrading Apache on a Plesk enabled box is a recipe for disaster. I would strongly advise against it. Apache and Plesk are deeply intertwined and other than the Apache updates that come with and are installed automatically with Plesk updates, you should not touch it. [IMHO]

Rick

Yeah it is on the Standard version but the RPM version of Plesk just integrates with a default install of the apache RPM, Plesk tell users to download apache from Red Hat themselves and especially now with the recent bug found in Apache.

Ahhh, I have not a clue on the RPM version of Plesk... is RS installing that now?

I would have a big problem with it if that was the case on the new server we intend to buy soon just because of all the issues I see about it in this forum and the Plesk forum. I want nothing to do with it and will opt for Ensim or straight redhat over it.

Rick

For some reason Plesk has got a bad rep... but it's by far the most stable of all the CP's... some of the things I've heard about say Cpanel and Ensim make me very glad I'm using Plesk. I've been using it with others for a few years now and believe me Plesk v2.5 is by far better than v1.3

Once you get your head around the different way it sets everything up you get used to it. The only reason I moved to the RPM version was to be able to upgrade each piece of software as and when I want to and not have to wait for a Plesk upgrade that does the same job.

I agree with you, I like plesk although now I would just buy it for the convienience it gives resellers/clients on the box. It gets in my way more than anything these days.

I just don't like the RPM version because I see issue after issue on it in the Plesk forum. Many posts start out with "this won't work on the RPM version" ...

Rick

I just had an issue today that makes me so greatful that I use Ensim! Ensim actually follows the standards that have been agreed upon -- Plesk is just a piece of junk.

I wouldn't be so quick to judge Plesk... Ensim are on uncertain ground over modifying software released under the GPL and not providing the source code for it. At least with the RPM version of Plesk your only running their system on top of standard RPM's provided by Red Hat.

Plesk isn't GPL.

Never said it was

But both use apache which is open source... I'm merely pointing out that Ensim have been accused of modifying open source software but not making the modified source code available which breaks the GPL licence.

http://www.webhostingtalk.com/showthread.p...&threadid=56499

You said in your post "Ensim actually follows the standards"... which is 100% true.

A successful installation of Ensim 3.1 includes source RPMs for any GPL product included with Ensim.

I'm not having a go I'm just correcting you... "Ensim actually follows the standards"... if that's the case then so does Plesk. I downloaded all the RPM's for v2.5 from Red Hat apart from the base PSA package... if that's not "following standards" then I don't know what is

I have Ensim 3.1, and I can verify that it DOES install the src RPMs.

I'm merely correcting what you said about Plesk... it also does follow the standards. (I'm ok to defend a product I think is quite good aren't I? )

Of course, and Plesk is a fine product.

However, Plesk doesn't follow standards.

Where is apache?
Where is content?
What happened to the "service" command?
etc.

Plesk just doesn't do things the way they should be done... But I'm not saying not to use it, Plesk is a great product for some, and for others, Ensim is the product for them.

Your not confusing the Standard version with the RPM version are you? My apache is installed direct from the RPM's provided by Red Hat.

Whichever way RS installs it...

There lies the problem.... that's Rackshack's choice to install the Standard version. Plesk provide the easier Standard install which is great to start off with... and for those users who want the normal control over their system they provide the RPM version. With their backup/restore utilities it's a sinch to switch from either version. From my experience with Plesk since v1.3, the Standard version gave me the starting platform I needed.

By The Way... Which *is* RS installing these days, the source or the RPM version?

It does make a difference to me, when we get another server I will not get Plesk if it comes with the RPM version.

The "standards" do not interest me one way or the other, I don't have time to learn another set of quirks and then keep them straight in my head with the quirks I already have to remember on our source version. My time is better spent learning Linux than front ends.

There is no doubt a debate about which is better Ensim/Plesk/CP but to be honest, they all have to be decent or there would not be such a strong following for each. I have read things about Ensim that make me wish I had it and I have read things that make me glad I don't. I would certainly be willing to give it (or cpanel for that matter) a try and reserve judgement until I had experience with them all.

Rick

RS have always installed the Standard version... which places all software under /usr/local/psa/

Fair comment (see I can be reasonable as well as argumentitive - lol)

I tried Ensim about 9 months ago through a friend who was using it... and it does have a few more features than Plesk... although it did lack the reseller ability. For me the part which I like most is the clean professional look Plesk has over Cpanel/Ensim etc. Learning the quirks is something I've learnt to live with.... as I'm a win2k server admin in my fulltime job

hahaha...

You never miss an opportunity to jab uncle Bill in the ribs do you, carry on!

Rick

Yeah the only valid complaint I've heard about Ensim is the lack of a reseller feature, which has been addressed now in version 3.1.

Anyone know what:

[root@cosmos root]# up2date
Traceback (innermost last):
File "/usr/sbin/up2date", line 18, in ?
from up2date_client import clap
File "/usr/share/rhn/up2date_client/clap.py", line 7, in ?
ImportError: No module named popt


Means when trying to use up2date.. The registration went fine
but the box hasn't connected again since..

I recommend you stay AWAY from using up2date with ensim -- unless you know exactly what package your updating, and that it'll work. This utility has proven more trouble than it's worth in many situations.

OK: I've read EVERY relevant post i could find out of the 50,000+ contained in this jungle of pleas and answers. We just rented a plain rh 72 celery on Friday, so i've been digging... and digging... and digging; after 5 days of looking at literally thousands of posts and making a hefty TO DO list of crap to update, secure, batten down, etc I decided to risk up2date (it just sounds, you know, perfect)

==============================
First of all, Richard, if you search for your error in these forums, you'll be directed to the RPM you need to run up2date (python something or other - i had the same problem)

Secondly, you'll want to update up2date before running it
(again, handy links elsewhere in these forums)

Thirdly, you may want to explore some of the other alternatives to up2date (again, just do a search for up2date in the forums)
==============================

I registered successfully from the cli with rhn_register

then i utilized the system software module in Webmin to run up2date

(i did spend plenty of time getting here, including your error, registering, updating up2date, and waiting for the RHN servers to respond)

So its running... everythings looking smooth, i come back (mello yello and taquitos... mmm) and ERROR 51, Sorry we're too busy... it looked like it died updating Perl

Webmin is all Perl, so it vanishes as soon as i click anywhere in it, taking my up2date feedback with it (maybe its stored elsewhere?)

Argh. I'm thinkin, LightHouse is right (I don't think he likes up2date)! But I'm not ready to reboot the box or anything just yet, so i try to run up2date manually and get the CONSTANT Error 51, too busy msg (i'm cursin redhat for um droppin me mid update)

I'm a newb, i like top... so i pull it up and there's up2date in my processes list; can't kill it, read and read, try a few things and realize that it is a ZOMBIE process... a stalled child of miniserve.pl which was a child of webmin.pl. I killed the grandparent process (the ppid of the ppid of my zombie pid)

AS SOON AS I DID THAT, my up2date connected, confirmed there was nothing left to update and exited; confused, i ran it a few more times. Nothing to update. Apparently it finished successfully and gave me a false error message instead of Success!

I started Webmin back up, rebooted my box with it (anyone ever gotten a bash: shutdown: command not found error - i got that trying shutdown -r now, so confusing) and everything seems grand. Apache, patched; BIND, updated and about a gazillion other things (i skipped kernel and sendmail)

Um... like i said, I posted this just in case there are other ppl that get stuck where I did... maybe this will help the next person in these plain shoes.

Good luck,

'boom!

If you have a Plain RH box, then up2date is your best friend =). However, if you own a box with a CP, such as a RaQ/Ensim/Plesk, then up2date will most-likey break your CP.

So you're actually talking about an entirely different situation.