Highlighted
cac4 Absent Member.
Absent Member.
1811 views

red carpet broken

OESsp2 on sles9. Linux neophyte; I'm a netware guy.

Set up this server just for running freeradius. Its running on a dell workstation...gx280, not "server" hardware, but its not being asked to do much.

Only big problem is that its been locking up at random intervals. It just freezes. no errors, no nothing...just stops. not much to go on.

Before digging deeper, I decided to make sure everything is all updated one more time, so I went into red carpet, and ran a bunch of patches. It wouldn't do them all without crashing, so I started doing them one at a time. Got most all of the recommended patches on, but the last few just won't go, without red carpet crashing altogether, with the error "lost contact with the daemon". click "ok"...red carpet closes. try to restart it, and it tells me that there is no daemon running, do I want to start one? to which I say "yes", and it proceeds. still can't run any of the remaining updates, without the same thing happening.

I tried doing it from the command line, and the error says "connection reset by peer".

no idea how to proceed from here.
Labels (2)
0 Likes
14 Replies
Anonymous_User Absent Member.
Absent Member.

Re: red carpet broken

cac4 wrote:
> OESsp2 on sles9. Linux neophyte; I'm a netware guy.
>
> Set up this server just for running freeradius. Its running on a dell
> workstation...gx280, not "server" hardware, but its not being asked to
> do much.
>
> Only big problem is that its been locking up at random intervals. It
> just freezes. no errors, no nothing...just stops. not much to go on.
>
>
> Before digging deeper, I decided to make sure everything is all updated
> one more time, so I went into red carpet, and ran a bunch of patches.
> It wouldn't do them all without crashing, so I started doing them one at
> a time. Got most all of the recommended patches on, but the last few
> just won't go, without red carpet crashing altogether, with the error
> "lost contact with the daemon". click "ok"...red carpet closes. try to
> restart it, and it tells me that there is no daemon running, do I want
> to start one? to which I say "yes", and it proceeds. still can't run
> any of the remaining updates, without the same thing happening.
>
> I tried doing it from the command line, and the error says "connection
> reset by peer".
>
> no idea how to proceed from here.
>
>


I ran into this.

Gave up and put in OES2 -- well worth the time money and effort.


0 Likes
Brunold Rainer Absent Member.
Absent Member.

Re: red carpet broken

cac4,

what happens when you run the following commands:

# rug sl
# rug bl
# rug ca

If you get any error message regarding a not running daemon try to start it with "/etc/init.d/rcd start".

You can also provide the information about the installed versions using:

# rpm -q rcd
# rpm -q rug

Rainer
0 Likes
cac4 Absent Member.
Absent Member.

Re: red carpet broken

rug sl: shows the update server address. (https://update.novell.com/data |Novell_update_server).

the other 2, it doesn't know. (unknown command).


# rpm -q rcd: 2.4.9-1.18

# rpm -q rug: 2.4.9-1.14


is "OES2" not the same thing as "OESsp2"??, (which is what it says on the iso/cd images that I downloaded to install this thing, originally).
0 Likes
Brunold Rainer Absent Member.
Absent Member.

Re: red carpet broken

is "OES2" not the same thing as "OESsp2"??



OESsp2 was the initial OES 1 release including the servcie pack 2. This is based on SLES 9 but is it's own distribution. That's whyt you have so many cd's of it.

OES2 is the next version based on SLES 10. OES 2 is no more a full distribution, it's just like a application that is installed on a sles 10 server. Therefor OES2 consists of just one or two cd's depending if the source packages are on it.

So you want to continue to work on the red carpet problem or do you want to upgrade to the latest version ? Yesterday there was the OES 2 service pack 1 release. The OES version you have will go end of support June or July 2009.

Rainer
0 Likes
cac4 Absent Member.
Absent Member.

Re: red carpet broken

maybe the solution to the problem IS to upgrade to OES2 on SLES10...if it comes to that. For now, I'm happy to just get what I have to work. Trying to update it seems to have made the problem worse.
0 Likes
cac4 Absent Member.
Absent Member.

Re: red carpet broken

bump.

still broken.

any ideas of how to untangle this knot?
0 Likes
Brunold Rainer Absent Member.
Absent Member.

Re: red carpet broken

cac4,

I need to install a pure oes1 sp2 server to verify that one.
Do you know the name of the last missing update ?

We have about 250 oes 1 sp2 servers in our environment, but all have the zenworks linux management client installed. Therefor they do not help me to check the red carpet stuff. Please give me one day ...

Rainer
0 Likes
cac4 Absent Member.
Absent Member.

Re: red carpet broken

brunold;1698864 wrote:
cac4,

I need to install a pure oes1 sp2 server to verify that one.
Do you know the name of the last missing update ?



not sure what you mean.

I just checked, and red carpet found a few more updates...it let me install them. still wouldn't do them all. One of the one's it crashes on is a red carpet update. makes the daemon unload, altogether.
0 Likes
Brunold Rainer Absent Member.
Absent Member.

Re: red carpet broken

Okay, the oes 1 sp2 server is installed now.
As we always remove the red carpet server and install the zenworks linux client I can't remember where the logfiles were.
Now I have a default installation with red carpet and can check.

When you run the update and the daemon crashes, can you check the logfiles in /var/log/rcd and see which changed as the last one and check the last maybe 20 lines in that file ?

Rainer
0 Likes
cac4 Absent Member.
Absent Member.

Re: red carpet broken

well...at this point, I can't even get into the /var/logs folder. as soon as I click on the logs folder, the file manager app crashes. tried using the editor's browser...same thing. logged in as "root".

??
0 Likes
Brunold Rainer Absent Member.
Absent Member.

Re: red carpet broken

cac4,

can you switch to a text console of that server and check it there ?
If you are at the server console press <ctrl><alt><F1> to switch to terminal one, then login as root, run the following commands:

# cd /var/log/rcd
# ls -rtl
# less <logfilename>

The ls command gives you a reverse time sorted list of files in that directory.
The less can be closed by pressing !q!.

Rainer
0 Likes
cac4 Absent Member.
Absent Member.

Re: red carpet broken

brunold;1701473 wrote:
cac4,

can you switch to a text console of that server and check it there ?
If you are at the server console press <ctrl><alt><F1> to switch to terminal one, then login as root, run the following commands:

# cd /var/log/rcd
# ls -rtl
# less <logfilename>

The ls command gives you a reverse time sorted list of files in that directory.
The less can be closed by pressing !q!.

Rainer

Dec 11 16:06:13 [11240] Unable to verify package signature for 'red-carpet'
Dec 11 16:06:13 [11240] Checking for stale mounts...
Dec 11 16:06:13 [11240] Transaction starting. 3 steps
Dec 11 16:06:13 [11240] Transaction step. seqno 1 (prepare)
Crash!
[Thu 11 16:06:13 PM] rcd has crashed.
Attempting to write backtrace to /tmp/rcd-crash.11283
Error while mapping shared library sections:
/tmp/rc-rpm-DAu4X0/rc-{rpm_rpmio_rpmdb}-4.1-popt.so.1.so: No such file or directory.
(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 1075316416 (LWP 11240)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
rcd-messages lines 63140-63173/63234 99%

this is the last few lines of rcd-messages.

There is another file in there called "rcd-package-history". the last few lines:

Thu Dec 11 15:52:19 2008 |49417d83|local|root|install|_|_|_|_|patch-12206|_|12206|
Thu Dec 11 15:53:11 2008 |49417db7|local|root|install|_|_|_|_|patch-12258|_|12258|
Thu Dec 11 15:53:38 2008 |49417dd2|local|root|install|_|_|_|_|patch-12206|_|12206|
Thu Dec 11 15:55:31 2008 |49417e43|local|root|install|_|_|_|_|patch-12206|_|12206|
Thu Dec 11 15:55:31 2008 |49417e43|local|root|install|_|_|_|_|patch-12273|_|12273|
Thu Dec 11 15:55:31 2008 |49417e43|local|root|install|_|_|_|_|patch-12275|_|12275|
Thu Dec 11 15:55:31 2008 |49417e43|local|root|install|_|_|_|_|patch-12279|_|12279|
Thu Dec 11 15:56:19 2008 |49417e73|local|root|install|_|_|_|_|patch-12273|_|12273|
Thu Dec 11 15:56:19 2008 |49417e73|local|root|install|_|_|_|_|patch-12282|_|12282|
Thu Dec 11 15:56:19 2008 |49417e73|local|root|install|_|_|_|_|patch-12283|_|12283|
Thu Dec 11 15:56:19 2008 |49417e73|local|root|install|_|_|_|_|patch-12284|_|12284|
Thu Dec 11 16:00:29 2008 |49417f6d|local|root|install|_|_|_|_|patch-12273|_|12273|
Thu Dec 11 16:00:29 2008 |49417f6d|local|root|install|_|_|_|_|patch-12286|_|12286|
Thu Dec 11 16:00:29 2008 |49417f6d|local|root|install|_|_|_|_|patch-12291|_|12291|
Thu Dec 11 16:00:29 2008 |49417f6d|local|root|install|_|_|_|_|patch-12295|_|12295|
Thu Dec 11 16:00:29 2008 |49417f6d|local|root|install|_|_|_|_|patch-12299|_|12299|
Thu Dec 11 16:00:29 2008 |49417f6d|local|root|install|_|_|_|_|patch-12300|_|12300|
Thu Dec 11 16:00:53 2008 |49417f85|local|root|install|_|_|_|_|patch-12273|_|12273|
Thu Dec 11 16:05:03 2008 |4941807f|local|root|upgrade|nscd|_|2.3.3|98.98|nscd|_|2.3.3|98.101
Thu Dec 11 16:05:21 2008 |49418091|local|root|upgrade|timezone|_|2.3.3|98.98|timezone|_|2.3.3|98.1
01
0 Likes
Brunold Rainer Absent Member.
Absent Member.

Re: red carpet broken

I register my oes 1 box know and start updating it ....

Rainer
0 Likes
Brunold Rainer Absent Member.
Absent Member.

Re: red carpet broken

cac4,

the update has finished on that test box and everything was installed.

Can you cehck on your system which patches are still missing, that should be the one that gets installed. When you run"rug pa" you should have some patches listed with a "v" in front. That would indicate that some other versions of this files are installed on that system and indicate mostly that there are old versions and this patch contains newer version. So can you please run the following:

# rug üa | grep "^v"

That should list at least one package. Then query the files in that package by running the following command:

# rug fl <package from output before>

I think it might be a rug/rcd patch that might be listed. In this case we could try to download it without automatic installation and try to install it manually.

The download only could be donw by using "rug up --download-only <patch>" whereas the file were just downloaded to /var/cache/rcd/packages. There we could use native rpm commands to do the upgrade.

Can you check that ?

Rainer
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.