Spoke too soon. This was a result of conflicting packages being pushed (or NOT
being) out to the client on kickstart. Only when I tried to refresh the repo
zipper would log something informative:
2013-06-05 02:04:11 <5> linux(12185) [zypp] Exception.cc(log):137
PluginScript.cc(receive):379 THROW: Receive: script died unexpectedly
2013-06-05 02:04:11 <5> linux(12185) [zypp] Exception.cc(log):137 History:
2013-06-05 02:04:11 <5> linux(12185) [zypp] Exception.cc(log):137 -
[11-Resource temporarily unavailable]
2013-06-05 02:04:11 <5> linux(12185) [zypp] Exception.cc(log):137
2013-06-05 02:04:11 <2> linux(12185) [PLUGIN]
PluginScript.cc(~PluginDumpStderr):72 ! Traceback (most recent call last):
2013-06-05 02:04:11 <2> linux(12185) [PLUGIN]
PluginScript.cc(~PluginDumpStderr):72 ! File
"/usr/lib/zypp/plugins/urlresolver/spacewalk", line 39, in <module>
2013-06-05 02:04:11 <2> linux(12185) [PLUGIN]
PluginScript.cc(~PluginDumpStderr):72 ! from zypp_plugin import Plugin
2013-06-05 02:04:11 <2> linux(12185) [PLUGIN]
PluginScript.cc(~PluginDumpStderr):72 ! ImportError: No module named zypp_plugin
2013-06-05 02:04:11 <1> linux(12185) [zypp++] PluginScript.cc(close):227
Close:PluginScript[12194] /usr/lib/zypp/plugins/urlresolver/spacewalk()
2013-06-05 02:04:11 <1> linux(12185) [zypp++] PluginScript.cc(send):270 ->send
PluginFrame[_DISCONNECT](0){0}
2013-06-05 02:04:11 <3> linux(12185) [zypp] PluginScript.cc(send):324 write():
[32-Broken pipe]
2013-06-05 02:04:11 <5> linux(12185) [zypp] Exception.cc(log):137
PluginScript.cc(send):326 THROW: Send: script died unexpectedly
No Module?
rpm -e rhn-setup-1.9.10-4.1.noarch
rpm -e zypp-plugin-spacewalk-0.9.1-4.1.x86_64
rpm -e rhn-check-1.9.10-4.1.noarch
rpm -e rhnsd-5.0.9-4.1.x86_64
rpm -e rhn-check-1.9.10-4.1.noarch
rpm -e zypp-plugin-spacewalk-0.9.1-4.1.x86_64
zypper zypper in libxml2-python dbus-1-python rhnlib rhn-client-tools
zypp-plugin-spacewalk rhnsd rhn-setup rhn-check
zypper ref spacewalk\:sles11_sp2_core_x86_64
zypper ref spacewalk:sles11_sp2_updates_x86_64
zypper lu
repodata was then queried in spacewalk with 404 error then rebuilt as per usual
Client was then able to receive updates from spacewalk.
Regards,
Steve
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Reed, Steven
Sent: Wednesday, 5 June 2013 11:37 AM
To: '[email protected]'
Subject: [Spacewalk-list] SLES connected to spacewalk through rhn client but
can't access repository
This was working but after a few kickstarts it would not update packages from
the Web interface or by running rhn_check or by using zipper.
I saw a previous post on the list where someone had a similar problem but their
resolution was to upgrade from spacewalk 1.7 to 1.8. I am currently running
1.9.
I have tried to rebuild the repo data with no success. There is no information
in any log file except httpd/access.log which is trivial.
Below is the output ferom rhn_check -vvv
------------------------------------------
D: check_action{'action': "<?xml
version='1.0'?>\n<methodCall>\n<methodName>errata.update</methodName>\n<params>\n<param>\n<value><array><data>\n<value><int>244</int></value>\n</data></array></value>\n</param>\n</params>\n</methodCall>\n",
'version': 2, 'id': 352}
updateLoginInfo() login info
D: login(forceUpdate=True) invoked
D: opening db environment /var/lib/rpm/Packages create:cdb:mpool:private
D: opening db index /var/lib/rpm/Packages rdonly mode=0x0
D: opening db index /var/lib/rpm/Providename rdonly:nofsync mode=0x0
logging into up2date server
D: rpcServer: Calling XMLRPC up2date.login
D: writeCachedLogin() invoked
D: Wrote pickled loginInfo at 1370391638.82 with expiration of 1370395238.82
seconds.
successfully retrieved authentication token from up2date server
D: logininfo:{'X-RHN-Server-Id': 1000010008, 'X-RHN-Auth-Server-Time':
'1370395238.24', 'X-RHN-Auth': 'MZUr8wa+btlyRnpttSdtTw==',
'X-RHN-Auth-Channels': [['sles11_sp2_core_x86_64', '20130605110458', '1', '1'],
['sles11_sp2_updates_x86_64', '20130605110906', '0', '1']],
'X-RHN-Auth-User-Id': '', 'X-RHN-Auth-Expire-Offset': '3600.0'}
D: handle_action{'action': "<?xml
version='1.0'?>\n<methodCall>\n<methodName>errata.update</methodName>\n<params>\n<param>\n<value><array><data>\n<value><int>244</int></value>\n</data></array></value>\n</param>\n</params>\n</methodCall>\n",
'version': 2, 'id': 352}
D: handle_action actionid = 352, version = 2
D: do_call errata.update([244],){'cache_only': None}
D: rpcServer: Calling XMLRPC registration.welcome_message
D: rpcServer: Calling XMLRPC errata.getErrataNamesById Called patch
install['slessp2-softwaremgmt-201210-6967']
Executing: ['LANG=C', 'zypper', '-n', '-x', 'install',
'patch:slessp2-softwaremgmt-201210-6967']
<?xml version='1.0'?>
<stream>
<message type="info">Refreshing service 'spacewalk'.</message>
<progress id="raw-refresh" name="Retrieving repository 'SLES11 SP2 Core
x86_64' metadata" value="0"/> <progress id="raw-refresh" name="Retrieving
repository 'SLES11 SP2 Core x86_64' metadata" done="1"/> <message
type="error">Repository 'SLES11 SP2 Core x86_64' is invalid.
[|] Valid metadata not found at specified URL(s) Please check if the URIs
defined for this repository are pointing to a valid repository.
</message>
<message type="warning">Disabling repository 'SLES11 SP2 Core x86_64'
because of the above error.</message> <progress id="raw-refresh"
name="Retrieving repository 'SLES11 SP2 Updates x86_64' metadata"
value="0"/> <progress id="raw-refresh" name="Retrieving repository 'SLES11
SP2 Updates x86_64' metadata" done="1"/> <message type="error">Repository
'SLES11 SP2 Updates x86_64' is invalid.
[|] Valid metadata not found at specified URL(s) Please check if the URIs
defined for this repository are pointing to a valid repository.
</message>
<message type="warning">Disabling repository 'SLES11 SP2 Updates
x86_64' because of the above error.</message> <message type="info">Loading
repository data...</message> <message type="info">Reading installed
packages...</message> <message
type="info">'patch:slessp2-softwaremgmt-201210-6967' not found in
package names. Trying capabilities.</message> <message type="error">No provider
of 'patch:slessp2-softwaremgmt-201210-6967' found.</message> </stream>
D: Sending back response(104, u"<pre>Refreshing service
'spacewalk'.\nRepository 'SLES11 SP2 Core x86_64' is invalid.\n[|] Valid
metadata not found at specified URL(s)\nPlease check if the URIs defined for
this repository are pointing to a valid repository.\n\nDisabling repository
'SLES11 SP2 Core x86_64' because of the above error.\nRepository 'SLES11 SP2
Updates x86_64' is invalid.\n[|] Valid metadata not found at specified
URL(s)\nPlease check if the URIs defined for this repository are pointing to a
valid repository.\n\nDisabling repository 'SLES11 SP2 Updates x86_64' because
of the above error.\nLoading repository data...\nReading installed
packages...\n'patch:slessp2-softwaremgmt-201210-6967' not found in package
names. Trying capabilities.\nNo provider of
'patch:slessp2-softwaremgmt-201210-6967' found.</pre>", {})
------------------------------------------------------
And result from web gui for an individual package
----------------------
lient execution returned "
Refreshing service 'spacewalk'.
Repository 'SLES11 SP2 Core x86_64' is invalid.
[|] Valid metadata not found at specified URL(s) Please check if the URIs
defined for this repository are pointing [...]
Disabling repository 'SLES11 SP2 Core x86_64' because of the above error.
Repository 'SLES11 SP2 Updates x86_64' is invalid.
[|] Valid metadata not found at specified URL(s) Please check if the URIs
defined for this repository are pointing to a valid repository.
Disabling repository 'SLES11 SP2 Updates x86_64' because of the above error.
Repository 'SLES11 Spacewalk 1.9 tools' is invalid.
[|] Valid metadata not found at specified URL(s) Please check if the URIs
defined for this repository are pointing to a valid repository.
Disabling repository 'SLES11 Spacewalk 1.9 tools' because of the above error.
Loading repository data...
Reading installed packages...
'patch:slessp2-kernel-7767' not found in package names. Trying capabilities.
No provider of 'patch:slessp2-kernel-7767' found.
" (code 104)
Errata Affected:
slessp2-kernel-7767 (Security update for Linux kernel)
----------------------------
Which is basically the same.
Any ideas ?
Regards,
Steve
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Benedetto Vassallo
Sent: Wednesday, 5 June 2013 7:41 AM
To: Jan Hutař
Cc: [email protected]
Subject: Re: [Spacewalk-list] Spacewalk notifications
Def. Quota Jan Hutař <[email protected]>:
> On Sat, 01 Jun 2013 14:56:53 +0200 Benedetto Vassallo
> <[email protected]> wrote:
>
>>
>> Def. Quota Benedetto Vassallo <[email protected]>:
>>
>> > Def. Quota Benedetto Vassallo <[email protected]>:
>> >
>> >> Def. Quota Michael Mraka <[email protected]>:
>> >>
>> >>> Benedetto Vassallo wrote:
>> >>> %
>> >>> % Hi all,
>> >>> % I have an issue on spacewalk notifications.
>> >>> % Starting 2 weeks ago, my spacewalk server don't send any %
>> >>> notification e-mail regarding monitoring probes, and I find the %
>> >>> following message in my
>> >>> /var/log/nocpulse/NotifEscalator-error.log % file:
>> >>> %
>> >>> % 2013-05-06 10:29:25 7052 Unable to acquire lock on %
>> >>> /var/tmp/01_1367828964_007780_001 /usr/bin/notifier-7115 at %
>> >>> /usr/share/perl5/vendor_perl/NOCpulse/Notif/AlertFile.pm
>> >>> line 111. % % Yesterday I upgraded my spacewalk installation to
>> >>> 1.9 but nothing is changed.
>> >>> %
>> >>> % What I can do to solve this issue?
>> >>>
>> >>> Hi Benedetto,
>> >>>
>> >>> Does /var/tmp/01_1367828964_007780_001 file exists?
>> >>> What are its permissions?
>> >>> Are there any relevant selinux errors?
>> >>>
>> >>> Regards,
>> >>>
>> >>> --
>> >>> Michael Mráka
>> >>> Satellite Engineering, Red Hat
>> >>>
>> >>> _______________________________________________
>> >>> Spacewalk-list mailing list
>> >>> [email protected]
>> >>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>> >>
>> >> Hi Michael,
>> >>
>> >> As I wrote in my previous e-mail, all files in /var/tmp exists.
>> >>
>> >> Their permissions are:
>> >>
>> >> -rw-rw-r-- 1 nocpulse nocpulse 3396 14 mag 16:52
>> >> 01_1367828964_007780_001
>> >>
>> >> Selinux is disabled.
>> >>
>> >> Today I tried to reinstall spacewalk from zero, using the same
>> >> database (skipping database polupation when executing
>> >> spacewalk-setup --disconnected) and I have the same situation.
>> >>
>> >> Can you help me, please?
>> >>
>> >> Thank you.
>> >>
>> >>
>> >> --
>> >> Benedetto Vassallo
>> >> Sistema Informativo di Ateneo
>> >> Settore Gestione Reti Hardware e Software U.O.B. Sviluppo e
>> >> manutenzione dei sistemi Università degli studi di Palermo
>> >>
>> >> Phone: +3909123860056
>> >> Fax: +390916529124
>> >>
>> >>
>> >> _______________________________________________
>> >> Spacewalk-list mailing list
>> >> [email protected]
>> >> https://www.redhat.com/mailman/listinfo/spacewalk-list
>> >
>> > Hi all,
>> > Can anyone help me to solve this issue?
>> > What I have to investigate to understand where is the problem?
>> > Maybe I miss some perl module?
>> > The strange thing is it has stopped working from one day to
>> > another. All my 829 probes are still working, just spacewalk don't
>> > send e-mails Please help me.
>> > Thank you.
>> >
>> >
>> >
>> > --
>> > Benedetto Vassallo
>> > Sistema Informativo di Ateneo
>> > Settore Gestione Reti Hardware e Software U.O.B. Sviluppo e
>> > manutenzione dei sistemi Università degli studi di Palermo
>> >
>> > Phone: +3909123860056
>> > Fax: +390916529124
>> >
>> >
>> > _______________________________________________
>> > Spacewalk-list mailing list
>> > [email protected]
>> > https://www.redhat.com/mailman/listinfo/spacewalk-list
>>
>> Hi again,
>> I re-installed my spacewalk from scratch on a new linux box.
>>
>> I also used a fresh oracle schema on the same db machine where is the
>> production db (different from both the spacewalk-production and
>> spacewalk-new box).
>> My oracle db is 10.2.0.5 and (of course) spacewalk version is
>> 1.9
>>
>> I registered a system on the new spacewalk instance, created a
>> monitoring probe and all is working fine.
>>
>> So, I guess, there must be something in the production schema
>> database making my spacewalk-production box not sending notification
>> e-mails.
>>
>> I checked my db for invalid objects but found nothing.
>>
>> My production DB schema was created with spacewalk 1.0 and updated
>> every new release.
>>
>> What I have to check on my DB in order to solve that issue?
>> Alternatively, can I export my production schema data in the new
>> schema without broken the new schema?
>> Keep present that change the spacewalk IP, hostname and certificate.
>>
>> I have 180 registered systems and 829 configured monitoring probes in
>> my production spacewalk instance, and I use spacewalk to manage,
>> deploy configuration files and monitoring, so, if it's possible, I
>> prefer don't move my systems manually in the new spacewalk
>> installation.
>>
>> Keep also present, all is working in my production installation, even
>> monitorig probes (from the web gui I see the correct status for every
>> probe). Just notification e-mail don't work.
>>
>> Can you help me?
>> Best regards.
>
> You can check that relevant packages were not altered:
>
> # rpm -qV `rpm -qa | grep -i -e noc -e monitoring -e perl`
> .M....... /var/lib/nocpulse/NPkernel.out
> S.5....T. c /etc/NOCpulse.ini
>
> (you can compare output from your new and old box)
>
> Regards,
> Jan
>
>
>
> --
> Jan Hutar Systems Management QA
> [email protected] Red Hat, Inc.
Hi,
Both my old and new box have the same output:
old box
# rpm -qV `rpm -qa | grep -i -e noc -e monitoring -e perl` S.5....T. c
/etc/NOCpulse.ini
.M....... /var/lib/nocpulse/NPkernel.out
new box
# rpm -qV `rpm -qa | grep -i -e noc -e monitoring -e perl` S.5....T. c
/etc/NOCpulse.ini
.M....... /var/lib/nocpulse/NPkernel.out
Any other idea?
Thanks
--
Benedetto Vassallo
Sistema Informativo di Ateneo
Settore Gestione Reti Hardware e Software U.O.B. Sviluppo e manutenzione dei
sistemi Università degli studi di Palermo
Phone: +3909123860056
Fax: +390916529124
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
This email (including any attachments) may contain confidential and/or legally
privileged information and is intended only to be read or used by the
addressee(s). If you have received this email in error, please notify the
sender by return email, delete this email and destroy any copy. Any use,
distribution, disclosure or copying of this email by a person who is not the
intended recipient is not authorised.
Views expressed in this email are those of the individual sender, and are not
necessarily the views of Transport for New South Wales, Department of Transport
or any other NSW government agency. Transport for NSW and the Department of
Transport assume no liability for any loss, damage or other consequence which
may arise from opening or using an email or attachment.
Please visit us at http://www.transport.nsw.gov.au or http://www.131500.com.au
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
This email (including any attachments) may contain confidential and/or legally
privileged information and is intended only to be read or used by the
addressee(s). If you have received this email in error, please notify the
sender by return email, delete this email and destroy any copy. Any use,
distribution, disclosure or copying of this email by a person who is not the
intended recipient is not authorised.
Views expressed in this email are those of the individual sender, and are not
necessarily the views of Transport for New South Wales, Department of Transport
or any other NSW government agency. Transport for NSW and the Department of
Transport assume no liability for any loss, damage or other consequence which
may arise from opening or using an email or attachment.
Please visit us at http://www.transport.nsw.gov.au or http://www.131500.com.au
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
