Re: Error from SMT

Werner Flamme <[email protected]> Fri, 17 Dec 2010 18:40:39 +0100
Newsgroups gmane.linux.suse.oracle.general
Message-ID <[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Marcus Meissner [17.12.2010 17:35]:
> On Fri, Dec 17, 2010 at 04:12:00PM +0100, Werner Flamme wrote:
>> Marcus Meissner [17.12.2010 13:46]:
>>> On Thu, Dec 16, 2010 at 03:14:28PM +0100, Werner Flamme wrote:
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> Hash: SHA1
>>>>
>>>> Hi everyone,
>>>>
>>>> for some days now SMT sends
>>>>
>>>> Undefined subroutine &SMT::Agent::Config::error called at
>>>> /usr/lib/perl5/vendor_perl/5.10.0/SMT/Agent/Config.pm line 52.
>>>>
>>>> to me every three hours.
>>>>
>>>> I am not aware of a cange to SMT coding on my host, so I wonder what
>>>> mi�ght be the reason of this... Anyone can help me here?
>>>
>>> We are investigating the error, it seems however to happen only if
>>> /etc/suseRegister.conf is missing.
>>>
>>> Ciao, Marcus
>>
>> Marcus,
>>
>> now that you said it...
>>
>> ll /etc/suseRegister.*
>> -rw-r--r-- 1 root root 461 Aug  4 09:26 /etc/suseRegister.conf-2010-08-04
>> -rw-r--r-- 1 root root 473 Oct 18 16:03 /etc/suseRegister.conf-2010-10-18
>> -rw-r--r-- 1 root root 474 Oct 18 16:03 /etc/suseRegister.conf.alt
>>
>> very funny. I started YaST2 and selected "Online Update Configuration",
>> and no /etc/suseRegister.conf. I added the SDK as an AddOn, had to
>> register this, but still no /etc/suseRegister.conf. Why?
>>
>> All the existing backups of former suseRegister.conf hold the host
>> itself as value for url - I think, I tried to register the host with
>> itself, as it is the SMT host.
>>
>> When registering, I get
>>
>> Disabled catalog: nu_novell_com:SLE11-HAE-SP1-Pool (nu_novell_com)
>> Disabled catalog: nu_novell_com:SLE11-HAE-SP1-Updates (nu_novell_com)
>> Enabled catalog: nu_novell_com:SLE11-SDK-SP1-Pool (nu_novell_com)
>> Enabled catalog: nu_novell_com:SLE11-SDK-SP1-Updates (nu_novell_com)
>> Enabled catalog: nu_novell_com:SLE11-SMT-Updates (nu_novell_com)
>> Disabled catalog: nu_novell_com:SLES11-SP1-Pool (nu_novell_com)
>> Disabled catalog: nu_novell_com:SLES11-SP1-Updates (nu_novell_com)
>>
>> Why does this strange piece of software disable the HAE repos and the
>> SP1-Updates? We paid for it!
> 
> I am pretty sure this means:
> 
> The service or catalog is there, it is just not default enabled (which can be done
> on your side).
> 
> zypper sl
> 	See "Enabled" column.
> zypper ms  ...
> 	for modifying a service to be enabled.
> 
> 
>> Even after running suse_register by hand (telling me "Registration
>> finished successfully"), there is no /etc/suseRegister.conf. I created
>> one manually, now I'll watch if there are still the error mails.
> 
> (There is additionaly currently some Novell Customer Center trouble
>  with registration, but it shouldnt have been there on first occurence.)
> 
> 
> The config file comes from the suseRegister package itself and is modified
> by YAST, it should just not vanish. I think someone or something on your system
> might have removed it. (our software just seems to adjust the URL line in the YAST module)
> 
> Ciao, Marcus

Marcus,

I used url=nu.novell.com in my version of the file, but the YaST2 module
complained that it can't connect there. I changed it to
secure-www.novell.com, YaST was content with it, but now the error
changed. Now I get "Error: Configuration doesn't allow to connect to
https://secure-www.novell.com".

So it might be best to uninstall and reinstall the suseRegister package.
I did the "rpm -e suseRegister-1.4-1.9.1 --nodeps" and "zypper in
suseRegister" - and it's the same URL as before,
<https://secure-www.novell.com/center/regsvc/>. Nice. So it should be
the line "smturlmodified = true" that offends suse_register. But it is
not. With the freshly installed /etc/suseRegister.conf, smt-agent still
tells me
"Error: Configuration doesn't allow to connect to
https://secure-www.novell.com".

I just found out that I had to uninstall the smt-client package (in
<http://forums.novell.com/novell-product-support-forums/suse-linux-enterprise-server-sles/sles-updates/394564-smt-agent-error.html>).
As a side effect, /usr/sbin/smt-agent is gone now, so the error won't
occur again...

Let's see what happens. But not today, It's gonna be a snowy weekend now ;-)

Regards,
Werner
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/

iEYEARECAAYFAk0LoJcACgkQk33Krq8b42NAHQCfRO9b1gOKdHFXS8gwigKTcd/E
EdQAnRrUOiujot8hgd/3u+gVVlUT6oU/
=CUeK
-----END PGP SIGNATURE-----
_______________________________________________
suse-sles-e mailing list
[email protected]
http://listx.novell.com/mailman/listinfo/suse-sles-e