The software updater ?

Chris

unread,

Feb 3, 2010, 11:07:59 AM2/3/10

to

Hi all: This may be a coincidence but since upgrading the evms last week, I cannot get software updater to function properly. Just get the big question mark. I followed several TIDs suggesting various solutions (such as deleting some xml files).

Any ideas?

Joseph Marton

unread,

Feb 3, 2010, 11:23:24 AM2/3/10

to

Which particular application are you using? rug, zypper, zen-updater, YOU?

--
Joe Marton
Novell Knowledge Partner

Joseph Marton

unread,

Feb 3, 2010, 2:44:46 PM2/3/10

to

On Wed, 03 Feb 2010 19:28:05 +0000, Chris wrote:

> Forgive my obtuseness, but I have no idea which service the updater
> uses.

Please give the steps on how you were performing the updates. That will
tell us what software you were using to do the update. Just saying
"software updater" is very generic as there are multiple applications for
updating SLES & OES.

Joseph Marton

unread,

Feb 3, 2010, 3:02:30 PM2/3/10

to

On Wed, 03 Feb 2010 19:54:20 +0000, Chris wrote:

> AS I am not yet fully fluent with all the shell commands, I still use
> the GUI. When I log in I am usually greeted by System Updater (either
> globe or ! ) indicating the status of needed updates. I then click on
> the updater icon to see what updates are available and to kick off the
> update process.

Oh ok, so you are using zen-updater.

> With that said, checked the "Services" associated with Updater. the
> service https://nu.novell.com is listed as inactive. If I remove this
> service and rerun the customer care setup I will get this error message:
>
> ERROR: Could not add 'https://nu.novell.com': Failed to parse XML
> metadata: .......

Might want to do several things.

1) Stop the novell-zmd service (/etc/init.d/novell-zmd stop).
2) Delete /etc/zmd/deviceid, /etc/zmd/secret, and /var/lib/zmd.db.
3) Start the novell-zmd service (/etc/init.d/novell-zmd start)
4) Within YaST, try running the Novell Customer Center Configuration
utility to reregister your server (make sure you have both your SLES &
OES activation codes).

Joseph Marton

unread,

Feb 5, 2010, 8:14:43 AM2/5/10

to

On Fri, 05 Feb 2010 02:24:48 +0000, Chris wrote:

> No joy.

From a terminal session, please post the output of the following commands.

rug sl
rug ca

Joseph Marton

unread,

Feb 9, 2010, 10:18:27 AM2/9/10

to

On Sat, 06 Feb 2010 03:15:11 +0000, Chris wrote:

> here is the output. BTW, I am having issues with novell-named and
> 3 | Inactive | NU | https://nu.novell.com
> | https://nu.novell...

There's the problem. That should be active. I'll see if I can find out
why.

Joseph Marton

unread,

Feb 9, 2010, 11:16:53 AM2/9/10

to

On Tue, 09 Feb 2010 15:57:48 +0000, Chris wrote:

> I solved this issue. Seems ZCM 10.2 installs a version of mono that
> completely breaks micasa. Why this version has not been pulled is
> beyond me. But there is a published fix which worked well.

Thanks for the update. Do you mind sharing a couple things with me just
for my knowledge? Just curious which specific version of 10.2 you're
using (10.2, 10.2.1, 10.2.2) and where you found the fix? I'm assuming
it's in a TID.

Joseph Marton

unread,

Feb 9, 2010, 1:53:58 PM2/9/10

to

On Tue, 09 Feb 2010 17:53:43 +0000, Chris wrote:

> Sure, not a problem. I installed 10.2 from the Novell Evaluation
> Library DVD 3A, dated July 2009. TID 7003707 describes the issue and
> provides the fix.

Thanks.