ZLM Agent IR3 Registration During Installation Fails

Question

Greetings,
We've recently started to look into using Novell's ZENworks Linux
Management product, but have run into a slight snag that has prevented
us from being able to continue evaluating the product. We had no issues
with the ZLM install, but have been unable to get past the initial
installation of the ZLM Agent on the servers we want to manage. We are
using the latest Interim Release 3 version in both cases.
Servers involved:
* ZLM installed via ZLM73_Server_with_IR3.iso on a Red Hat Enterprise
Linux 5.5 64bit server.
* ZLM Agent install attempt via ZLM73_Agent_with_IR3.iso on a SUSE Linux
Enterprise Server 10 SP3 64bit server.
* ZLM Agent install attempt via ZLM73_Agent_with_IR3.iso on a Red Hat
Enterprise Linux 5.5 64bit server.
In either of the two ZLM Agent installation situations, we receive the
same errors during the installation, though we also tried to use a
registration key on the second attempt with the RHEL server.
Additionally, we are currently using the 90-day evaluation license with
the ZLM server, and it has not expired yet. The errors produced during
the install of the agent, as seen in the /var/log/zmd-messages.log, have
been attached to this reply. The most obvious issue, unless we're
mistaken, seems to be the following:
11 Aug 2010 00:07:53 INFO ZenService Registration failed:
System.InvalidOperationException: Not supported Content-Type in the
response: 'text/html;charset=utf-8' Response error message:
Any assistance with this would be greatly appreciated.
QC

Answer 1

Thank you for the speedy response. We actually managed to correct this
with a re-install of zlm using the standard ports, as we suspected the
setup of zlm to run on an alternate port, 8443, may have had something
to do with our issue (when registering the zlm agent, we were able to
successfully use $host:8443, with the exception of xml content-type error
during the registration portion of the zlm agent install of course).
Sorry, some of this information was left out of our previous reply, as
the attachment that was mentioned has this information but was left out,
and we had issues replying to our original post, due to post filter
errors from the nntp server, when trying to include it.
To address some of your recommendations, for the benefit of others
running into a similar situation:
On Wed, 18 Aug 2010, brunold wrote:
>
> QC,
>
> that sounds all good except the registration problem.
>
> Okay first a note on how you can check the registration of the systems.
> Run "rug sl" and if there is a registration, it shows you the ZLM server
> as active, pending or something. If there is not registration you can
> add it via "rug sa -t zenworks https://<DNS or IP address> -k
> <registration key>".
* This would not show our system as being "registered".
> So now to your problems:
>
> Depending if you try to register the ZLM server via a DNS name or the
> IP address I would try to ping it from the client to see if the
> communication / name resolution works.
>
> I assume you use a DNS name. Correct ?
* Well, there didn't seem to be any connectivity issues going over the
zlm agent log, and we could connect to the zlm server just fine whether
via fully qualified domain name or IP. Our initial attempts, which
didn't account for the alternate 8443 port the zlm server was setup up
on would log obvious connections errors which disappeared when we
specified the port.
> The next question would be if you have configured a proxy on those
> systems you use for internet access that needs a proxy login. In case
> the system has one configured, the zlm client would use it as well. You
> could check that by running "rug get" and check the proxy url. If there
> is one set, you can remove it from rug by using "rug set proxy-url ''".
> Then try registering again.
* We weren't using a proxy, it was a direct connection from the zlm
agent to the zlm server.
> If that is not the case next you can open a browser on such a server
> and enter the DNS name or IP you use for the registration in and see
> what you get. If you have no graphical environment you can use wget for
> that as well:
>
> wget --no-check-certificate https://<DNS anme or IP address of the ZLM
> server>
>
> When the client registers, it also simply uses the https protocol to
> communicate to the ZLM server. Therefor a biowser or wget can test the
> general access very well.
>
> So see what you get with this test.
* We were able to access the zlm server just fine, the (web)
administration interface as well. The "registration" issues we were
having seemed to be the registration done in the course of the zlm agent
install, after mounting the zlm agent iso, cd'ing to the mounted
directory, and running: ./zlm-install -a
>
> Ahhh, not sure if that could make problems, but time is synchronized
> within your server environment ?
* Well, time is off by no more than a few minutes between the servers
currently, and will be corrected via ntpd, but in this case, we did
manage to get this working despite this.
>
> Rainer
>
>
> --
> brunold
> ------------------------------------------------------------------------
> brunold's Profile: http://forums.novell.com/member.php?userid=562
> View this thread: http://forums.novell.com/showthread.php?t=418630
>
>
QC