PDA

View Full Version : SMT Issue: Client is not up-to-date



netzpks
19-Sep-2013, 13:30
on myhost:
zypper up

nothing to do

myhost:
SLES11 SP3 with all SP3 relevant Repositories (only SP3 Repos are activ)
myhost was upgraded from SP1, SP2

-------------------------------------------------------------------------


SMT Managent / Client Status

Status.....HostName....LastContact
Critical..... myhost......2013-09-19 14:16:39

Recommended patches: 1, Security patches: 1

--------------------------------------------------------------------------


How can I see which patches myhost needs?



Thank you!

malcolmlewis
19-Sep-2013, 13:54
On Thu 19 Sep 2013 12:34:02 PM CDT, netzpks wrote:


on myhost:
zypper up

nothing to do

myhost:
SLES11 SP3 with all SP3 relevant Repositories (only SP3 Repos are
activ)
myhost was upgraded from SP1, SP2

-------------------------------------------------------------------------


SMT MANAGENT / CLIENT STATUS

STATUS[/B].....*HOSTNAME*....[B]LASTCONTACT
Critical..... myhost......2013-09-19 14:16:39

Recommended patches: 1, Security patches: 1

--------------------------------------------------------------------------


How can I see which patches myhost needs?



Thank you!




Hi
Run;


zypper ref -f
zypper lu -t patch

That will force a metadata refresh and list the patches.

Or to patch the system


zypper patch


--
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 12.3 (x86_64) GNOME 3.8.4 Kernel 3.7.10-1.16-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below... Thanks!

netzpks
19-Sep-2013, 14:36
Hi Malcolm! Thank you very much for your reply
i did what you recommended but SMT has not changed the status (1 recommended patch, 1 security patch)





myhost:~ # zypper ref -f
Aktualisierung der Rohmetadaten wird erzwungen
Metadaten von Repository 'SLE11-SDK-SP3-Pool' werden abgerufen [fertig]
Erzwinge Erstellung des Repository-Zwischenspeichers
Zwischenspeicher fr Repository 'SLE11-SDK-SP3-Pool' wird erzeugt [fertig]
Aktualisierung der Rohmetadaten wird erzwungen
Metadaten von Repository 'SLE11-SDK-SP3-Updates' werden abgerufen [fertig]
Erzwinge Erstellung des Repository-Zwischenspeichers
Zwischenspeicher fr Repository 'SLE11-SDK-SP3-Updates' wird erzeugt [fertig]
Aktualisierung der Rohmetadaten wird erzwungen
Metadaten von Repository 'SLE11-SP3-Debuginfo-Pool' werden abgerufen [fertig]
Erzwinge Erstellung des Repository-Zwischenspeichers
Zwischenspeicher fr Repository 'SLE11-SP3-Debuginfo-Pool' wird erzeugt [fertig]
Aktualisierung der Rohmetadaten wird erzwungen
Metadaten von Repository 'SLE11-SP3-Debuginfo-Updates' werden abgerufen [fertig]
Erzwinge Erstellung des Repository-Zwischenspeichers
Zwischenspeicher fr Repository 'SLE11-SP3-Debuginfo-Updates' wird erzeugt [fertig]
Aktualisierung der Rohmetadaten wird erzwungen
Metadaten von Repository 'SLES11-SP3-Extension-Store' werden abgerufen [fertig]
Erzwinge Erstellung des Repository-Zwischenspeichers
Zwischenspeicher fr Repository 'SLES11-SP3-Extension-Store' wird erzeugt [fertig]
Aktualisierung der Rohmetadaten wird erzwungen
Metadaten von Repository 'SLES11-SP3-Pool' werden abgerufen [fertig]
Erzwinge Erstellung des Repository-Zwischenspeichers
Zwischenspeicher fr Repository 'SLES11-SP3-Pool' wird erzeugt [fertig]
Aktualisierung der Rohmetadaten wird erzwungen
Metadaten von Repository 'SLES11-SP3-Updates' werden abgerufen [fertig]
Erzwinge Erstellung des Repository-Zwischenspeichers
Zwischenspeicher fr Repository 'SLES11-SP3-Updates' wird erzeugt [fertig]
Alle Repositories wurden aktualisiert.
You have new mail in /var/mail/root
...
myhost:~ # zypper lu -t patch
Daten des Repositorys laden ...
Installierte Pakete lesen ...

Repository | Name | Version | Kategorie | Status
-------------------+-------------------+---------+-----------+-------------
SLES11-SP3-Updates | slessp3-libgcrypt | 8201 | security | erforderlich

myhost:~ # zypper patch
Daten des Repositorys laden ...
Installierte Pakete lesen ...
Paketabhngigkeiten auflsen ...

Der folgende NEUE Patch wird installiert:
slessp3-libgcrypt

Das folgende Paket wird GELSCHT:
libgcrypt11

1 zu entfernendes Paket.
Nach dem Vorgang werden 532,0 KiB freigegeben.
Fortfahren? [j/n/?] (j):
libgcrypt11-1.4.1-6.7 wird entfernt [fertig]

myhost:~ # smt-agent
myhost:~ # zypper lu -t patch
Daten des Repositorys laden ...
Installierte Pakete lesen ...
Keine Aktualisierungen gefunden.

jmozdzen
19-Sep-2013, 16:43
Hi netzpks,

> i did what you recommended but SMT has not changed the status (1 recommended patch, 1 security patch)

it takes some cycles until SMT catches the updated status.

Regard,
Jens

netzpks
27-Sep-2013, 08:24
Status has not changed yet.
SMT say's: 1 recommended patch, 1 security patch

I did:
zypper ref -f -------------> all activated repos refreshed
zypper lu -t patch --------> nothing to do

How can I recognize which patch smt mean?

regard
netzpks

jmozdzen
29-Sep-2013, 22:42
Hi netzpks,

> i did what you recommended but SMT has not changed the status (1 recommended patch, 1 security patch)

it takes some cycles until SMT catches the updated status.

Regard,
Jens

just for the records: You can add a job at the smt server to have the client report back the current patch state:

root@smtserver # smt-job -t patchstatus -c -g <guid of your client, see "smt-client" command>

You then need to manually invoke the smt client to fetch & process that job:

root@smtclient # smt-agent

Now your smt server should report the proper client patch state

root@smtserver # smt-client -g <guid of your client, see "smt-client" command>

Just in case anyone stumbles across this thread.

Regards,
Jens

jmozdzen
29-Sep-2013, 22:46
Hi netzpks,

> Status has not changed yet.

does "smt-client" report a client contact at least 24 hours since you first hit this (I'd say more recent that Sept. 21st)?

Have a look at my other response on how to manually trigger a patch status update - it's a job you create on the SMT server, then invoke the client agent to run the job. After the client run, the server should reflect the current status. If it doesn't, you might want to check the smt job queue (see other options of "smt-job") to see if there's a job backlog for your client.

Regards,
Jens

netzpks
30-Sep-2013, 07:36
just for the records: You can add a job at the smt server to have the client report back the current patch state:

root@smtserver # smt-job -t patchstatus -c -g <guid of your client, see "smt-client" command>

You then need to manually invoke the smt client to fetch & process that job:

root@smtclient # smt-agent

Now your smt server should report the proper client patch state

root@smtserver # smt-client -g <guid of your client, see "smt-client" command>

Just in case anyone stumbles across this thread.

Regards,
Jens


Hi Jens!

many thanks - it works