Forum IT Tranquillo

Contattaci
su https://forum.tranquil.it/

[RISOLTO] Pacchetti installati ma ancora necessari

https://forum.tranquil.it/viewtopic.php?t=3218

Pagina 1 di 1

[RISOLTO] Pacchetti installati ma ancora necessari

Pubblicato: 29 settembre 2022 - 15:39
di chaudebault
Buongiorno,
Con le seguenti configurazioni:
Server: 2.2.2.12405
agente: 2.2.2.12405
console: 2.2.2.12405

Su alcune macchine, i pacchetti vengono installati senza problemi, ma le macchine rimangono nello stato "Da aggiornare" e i pacchetti vengono ancora visualizzati come "necessari da installare":
Senza titolo.png
Untitled.png (2,96 KB) Visualizzato 4001 volte
Se elimino il post, riappare senza alcun pacchetto visibile:
Untitled2.png
Untitled2.png (1,44 KB) Visualizzato 4001 volte
Avete qualche idea su come ripristinare il normale funzionamento?

Grazie in anticipo per le vostre risposte

Re: Pacchetti installati ma ancora necessari

Pubblicato: 3 ottobre 2022 - 09:55
di chaudebault
Ok, avevo un database in esecuzione su PostgreSQL versione 9.4, che ho aggiornato alla versione 13 (Debian 10.12). Purtroppo, non ci sono cambiamenti... Ho notato che l'inventario delle workstation non si aggiorna più. Ad esempio, quando installo Firefox 105, funziona correttamente sulla workstation, ma nell'inventario della console rimane alla versione 102 con la dicitura "Need-upgrade".
In waptserver.log ho questo output ciclico:

Codice: Seleziona tutto

Oct  3 09:50:10 scd-wapt waptserver[1995]: 2022-10-03 09:50:10,478 [waptdb         ] CRITICAL Unable to update installed_softwares for 64BC2342-DE32-4536-0C40-2EE0F3B48AB0: ProgrammingError: ERREUR:  il n'existe aucune contrainte unique ou contrainte d'exclusion correspondant à la spécification ON CONFLICT
Oct  3 09:50:10 scd-wapt waptserver[1995]: 2022-10-03 09:50:10,481 [waptdb         ] CRITICAL Unable to update installed_packages for 64BC2342-DE32-4536-0C40-2EE0F3B48AB0: ProgrammingError: ERREUR:  il n'existe aucune contrainte unique ou contrainte d'exclusion correspondant à la spécification ON CONFLICT
Hai qualche idea?

Re: Pacchetti installati ma ancora necessari

Pubblicato: 3 ottobre 2022 - 10:35
di sfontenau
Buongiorno

Per verificare quale versione di PostgreSQL è in esecuzione, puoi fare quanto segue:

Codice: Seleziona tutto

ps aux |grep postgres
Inoltre, quale versione del database viene visualizzata nell'interfaccia web?

Simone

Re: Pacchetti installati ma ancora necessari

Pubblicato: 3 ottobre 2022 - 11:02
di chaudebault
Buongiorno,

Ecco la versione di PostgreSQL in esecuzione:

Codice: Seleziona tutto

postgres    2377  0.0  2.9 256440 58076 ?        Ss   09:27   0:00 /usr/lib/postgresql/13/bin/postgres -D /var/lib/postgresql/13/main -c config_file=/etc/postgresql/13/main/postgresql.conf
postgres    2379  0.0  2.5 256852 51160 ?        Ss   09:27   0:03 postgres: checkpointer 
postgres    2380  0.0  0.5 256700 10004 ?        Ss   09:27   0:00 postgres: background writer 
postgres    2381  0.0  0.5 256440 10280 ?        Ss   09:27   0:01 postgres: walwriter 
postgres    2382  0.0  0.4 257712  8876 ?        Ss   09:27   0:00 postgres: autovacuum launcher 
postgres    2383  0.0  0.2  68824  5760 ?        Ss   09:27   0:01 postgres: stats collector 
postgres    2384  0.0  0.3 257560  6816 ?        Ss   09:27   0:00 postgres: logical replication launcher 
postgres    3638  0.2  3.0 262256 60204 ?        Ss   10:54   0:00 postgres: wapt wapt [local] idle
Ed ecco le versioni sull'interfaccia web:
Versione del server WAPT: 2.2.3
Versione dell'agente WAPT: 2.2.3.12463
Versione di installazione WAPT: 2.2.3.12463
Versione di distribuzione WAPT: 2.2.3.12463
Stato di base: OK (2.2.6.2)

Re: Pacchetti installati ma ancora necessari

Pubblicato: 3 ottobre 2022 - 11:30
di dcardon
Buongiorno,

Stai usando Debian 10 o Debian 11? La versione di Samba inclusa in Debian 10 è la 11, non la 13.

Quale versione utilizzavi prima di passare alla 2.2? Avevi già utilizzato la versione 1.8.2?

Potresti eseguire il seguente comando per vedere dove l'aggiornamento del database non riesce?

Codice: Seleziona tutto

cd /opt/wapt
sudo -u wapt PYTHONPATH=/opt/wapt /opt/wapt/bin/python -c "from waptserver.model import *; logging.basicConfig(format='%(asctime)s %(levelname)s %(message)s'); logger.setLevel(logging.DEBUG); load_db_config(); set_db_version('2.1.0'); print(upgrade_db_structure())"
Sinceramente,

Denis

Re: Pacchetti installati ma ancora necessari

Pubblicato: 3 ottobre 2022 - 13:36
di chaudebault
Buongiorno,

Mi dispiace Debian 11, avevo dimenticato di aver aggiornato il server secondo la documentazione per la transizione da 1.8.2 a 2.2.

Ecco il resoconto dell'ordine:

Codice: Seleziona tutto

2022-10-03 13:33:37,297 INFO Initializing a DB connection pool for db host None:5432 db_name:wapt. Size:90
2022-10-03 13:33:37,297 INFO Connecting to waptdb explicitely. Count: 0
2022-10-03 13:33:37,306 DEBUG Disconnecting from waptdb explicitely. Count: 1
2022-10-03 13:33:37,308 INFO Connecting to waptdb explicitely. Count: 0
2022-10-03 13:33:37,309 DEBUG Disconnecting from waptdb explicitely. Count: 1
2022-10-03 13:33:37,309 INFO Current DB: {'host': None, 'port': 5432, 'user': 'wapt', 'password': None} version: 2.1.0.0
2022-10-03 13:33:37,309 INFO Connecting to waptdb explicitely. Count: 0
2022-10-03 13:33:37,310 DEBUG Disconnecting from waptdb explicitely. Count: 1
2022-10-03 13:33:37,310 INFO Connecting to waptdb explicitely. Count: 0
2022-10-03 13:33:37,311 DEBUG Disconnecting from waptdb explicitely. Count: 1
2022-10-03 13:33:37,311 INFO Connecting to waptdb explicitely. Count: 0
2022-10-03 13:33:37,312 DEBUG Disconnecting from waptdb explicitely. Count: 1
2022-10-03 13:33:37,312 INFO Connecting to waptdb explicitely. Count: 0
2022-10-03 13:33:37,313 DEBUG Disconnecting from waptdb explicitely. Count: 1
2022-10-03 13:33:37,313 INFO Connecting to waptdb explicitely. Count: 0
2022-10-03 13:33:37,314 DEBUG Disconnecting from waptdb explicitely. Count: 1
2022-10-03 13:33:37,314 INFO Connecting to waptdb explicitely. Count: 0
2022-10-03 13:33:37,315 DEBUG Disconnecting from waptdb explicitely. Count: 1
2022-10-03 13:33:37,315 INFO Connecting to waptdb explicitely. Count: 0
2022-10-03 13:33:37,316 DEBUG Disconnecting from waptdb explicitely. Count: 1
2022-10-03 13:33:37,316 INFO Connecting to waptdb explicitely. Count: 0
2022-10-03 13:33:37,317 DEBUG Disconnecting from waptdb explicitely. Count: 1
2022-10-03 13:33:37,317 INFO Connecting to waptdb explicitely. Count: 0
2022-10-03 13:33:37,317 DEBUG Disconnecting from waptdb explicitely. Count: 1
2022-10-03 13:33:37,318 INFO Connecting to waptdb explicitely. Count: 0
2022-10-03 13:33:37,318 DEBUG Disconnecting from waptdb explicitely. Count: 1
2022-10-03 13:33:37,318 INFO Connecting to waptdb explicitely. Count: 0
2022-10-03 13:33:37,319 DEBUG Disconnecting from waptdb explicitely. Count: 1
2022-10-03 13:33:37,319 INFO Connecting to waptdb explicitely. Count: 0
2022-10-03 13:33:37,320 DEBUG Disconnecting from waptdb explicitely. Count: 1
2022-10-03 13:33:37,320 INFO Connecting to waptdb explicitely. Count: 0
2022-10-03 13:33:37,321 DEBUG Disconnecting from waptdb explicitely. Count: 1
2022-10-03 13:33:37,321 INFO Connecting to waptdb explicitely. Count: 0
2022-10-03 13:33:37,323 DEBUG Disconnecting from waptdb explicitely. Count: 1
2022-10-03 13:33:37,323 INFO Connecting to waptdb explicitely. Count: 0
2022-10-03 13:33:37,324 DEBUG Disconnecting from waptdb explicitely. Count: 1
2022-10-03 13:33:37,324 INFO Connecting to waptdb explicitely. Count: 0
2022-10-03 13:33:37,326 DEBUG Disconnecting from waptdb explicitely. Count: 1
2022-10-03 13:33:37,326 INFO Connecting to waptdb explicitely. Count: 0
2022-10-03 13:33:37,326 DEBUG Disconnecting from waptdb explicitely. Count: 1
2022-10-03 13:33:37,327 INFO Connecting to waptdb explicitely. Count: 0
2022-10-03 13:33:37,327 DEBUG Disconnecting from waptdb explicitely. Count: 1
2022-10-03 13:33:37,328 INFO Migrating from 2.1.0.0 to 2.1.0.1
2022-10-03 13:33:37,328 INFO Switch column type (CharField -> TextField) for normalization table
2022-10-03 13:33:37,344 INFO Migrating from 2.1.0.1 to 2.2.3.0
2022-10-03 13:33:37,349 INFO Migrating from 2.2.3.0 to 2.2.3.7
2022-10-03 13:33:37,355 INFO Migrating from 2.2.3.7 to 2.2.4.3
2022-10-03 13:33:37,355 INFO Switch column type (CharField -> TextField) for reporting table
2022-10-03 13:33:37,361 INFO Migrating from 2.2.4.3 to 2.2.4.6
2022-10-03 13:33:37,402 INFO Migrating from 2.2.4.6 to 2.2.4.7
2022-10-03 13:33:37,406 INFO Migrating from 2.2.4.7 to 2.2.4.10
2022-10-03 13:33:37,426 INFO Migrating from 2.2.4.10 to 2.2.5.1
2022-10-03 13:33:37,469 INFO Migrating from 2.2.5.1 to 2.2.5.2
2022-10-03 13:33:37,479 INFO Migrating from 2.2.5.2 to 2.2.6.0
2022-10-03 13:33:37,479 INFO Switch column type (TextField -> BinaryJsonField) for audit data
2022-10-03 13:33:37,498 INFO Migrating from 2.2.6.0 to 2.2.6.1
2022-10-03 13:33:37,504 INFO Migrating from 2.2.6.1 to 2.2.6.2
None
L'aggiornamento del database sembra aver risolto il problema: gli inventari si stanno aggiornando!

Grazie mille per il tuo aiuto.

Sinceramente
Fuso orario impostato su UTC+02:00
Pagina 1 di 1

Sviluppato da phpBB® Forum Software © phpBB Limited

Traduzione ufficiale francese © Qiaeru