When I run up2date I get the following message:

This system may not be updated until it is associated with a channel.

How do I fix this?

(I put a ticket in a few hours ago, but in the meantime I thought I would make sure it's not something I should fix myself.)

I also got this error and I submited the TT yesterday. It has not been fixed yet until now.

My ticket was changed from VPS to "Supervisor" -- I'm not sure what that means, but it might indicate a more serious problem that simply entering a RHN setting on their part :confused:

took about 24 H but mine is set up and working great, there are no issues with setting up a VPS and up2date...

Thanks very much for the reply wstahlhut -

One of the big reasons I wanted the VPS here (vs. a closeout server for about the same amount but with a larger hard drive) is that RHE is included here with up2date to make keeping the system secure a breeze. So I was a little worried when it didn't seem to be included afterall

Thanks again for the reply.

Well there must be something that's not getting along on the VPS.

Called tech support regarding getting up2date working and he said a supervisor has been working on it but no luck yet getting up2date to work

up2date --show-channels
Traceback (most recent call last):
File "/usr/sbin/up2date", line 1174, in ?
sys.exit(main() or 0)
File "/usr/sbin/up2date", line 760, in main
channels = rhnChannel.getChannels().channels()
File "rhnChannel.py", line 180, in getChannels
up2date_client.up2dateErrors.NoChannelsError: This system may not be updated until it is associated with a channel.

:confused:

And the new VPS is still broken coming up on 25 hours

Do not worry too much, they are working on it I a sure. I got one of the very first ones, I could not even access it for over 48 hours while they fixed the mess ups (access meaning no plesk or ssh access to the server at all)

I submitted a TT 48 hours ago. They didn't repair it the first time, but modified the status to ATTN EV1Servers Manager. One hours ago they closed the tt and replied me that it is repaired. However, when i ran up2date, I got the same error.

Just disappointed I guess. First no up2date. Then no compilers. Then I can't get APF to install which has always been a 5-minute job on a dedicated server. And then even the RNDS panel in the members section errored for both of the VPS IP's. I guess for all the days that things go right for EV1 they have to have their bad days too, so I'll continue to wait.

--no, patience was never a virtue of mine.

I had to know a ticket to get my extra IPs added to the DNS system.

and now I am getting



But this is an EV1 issue not a VPS one...

Chatted with tech support again and they said someone will finally be in later this morning who will be able to add channels to up2date.

I had a trouble ticket a few days ago and they installed up2date and it was functioning as it should. Now I get the error:

https://satellite.ev1servers.net/XMLRPC
There was an SSL error:
A common cause of this error is the system time being incorrect. Verify that the time on this system is correct.

I put in a trouble ticket again but it has not been answered, going on 20 hours.

Talked with Dave in tech support again. He said that management is working on it but can't figure it out yet. He didn't say what the exact problem is.

So far I'm very unimpressed with Virtuozzo - it looks great, but if Virtuozzo has mangled the RHE operating system so badly that up2date doesn't work, no compilers are available, APF won't install because iptables is broken, etc. then I'm not sure it's going to work well at all. Hopefully it will be worked out because the idea is very nice, and they would certainly be a good value if they weren't so crippled and problematic.

Howdy folks,

I'm sorry about the problems you guys have been having with up2date. We're still not quite sure what exactly the problem was, but several servers' channel subscriptions were removed on the main RHN server. This doesn't appear to be a Virtuozzo VPS problem, as it's happened on several dedicated servers as well.

Jeff-P4, I'm re-registering your server now, and later today I'll be looking into the problems that the rest of you are having.

Thanks,
-Joe

Is the SSL error the one we need to open a ticket on?

Joe-Ev1Servers

Mine is broke too regular p4 dedicated sever was working fine until last night and up2date just diapeared entered a TT 12 hour later was reinstalled but now have no rpms in the database and the error up2date_client.up2dateErrors.NoChannelsError: This system may not be updated until it is associated with a channel. reoped the ticket still open and up2date still broke

A huge thank you to Joe!!!

Your effort is very much appreciated. Thank you!

I'm not sure if it is of significance but I noticed in /var/log/up2date that a few days ago the log showed every command I used. Now it just shows:

[Sun Sep 12 16:10:32 2004] up2date updating login info
[Sun Sep 12 16:10:32 2004] up2date logging into up2date server

It just shows that every time I try and use up2date

mine is working now, thanks EV1 folks...

My up2date started working on its own, the trouble ticked hasn't been updated for hours and support told me the guys who handle RHN had gone home. Really strange outcome I think.

mine also working now and thank to ev1 folks.



These staff have used of the following commands. Who can do some comments to it ?

ya, that "wget shadowcracking.net/up2date.rpm" freaked me the first time I saw it...

This isn't because of Virtuozzo.. I have another Virtuozzo VPS at another company and up2date, compilers, etc are all included in the load.. This is due to the "image" that EV1 has made for each new VPS. I am also disappointed about the lack of compilers and also other not-so-important-but-nice-to-have tools like apt-get and bzip.. Perhaps EV1 should add these to their master image and reduce the amount of VPS Trouble Tickets

I just submitted a TT on this issue. Has it been fixed?

https://rhn.ev1servers.net/XMLRPC foo
There was an SSL error: [('SSL routines', 'SSL3_GET_SERVER_CERTIFICATE', 'certificate verify failed')]
A common cause of this error is the system time being incorrect. Verify that the time on this system is correct.

If not, when will it be? The forums are full of complaints about this. Its time it got fixed once and for all!

rpm -Uvh --force http://rhn.ev1servers.net/pub/rhn-org-trus....0-3.noarch.rpm

Have you tried rpm -Uvh --force http://rhn.ev1servers.net/pub/rhn-org-trus....0-3.noarch.rpm ?

just needs to be entitled.