forum.opsi.org

Hallo Zusammen

Ich habe gem. Handbuch versucht auf das MySQL Backend umzustellen indem ich zuerst das MySQL Backend initialisiert habe (hat auch soweit geklappt) und dann per opsi-convert file mysql das Backend konvertiert habe. Wenn ich anschliessend jedoch opsi-setup --init-current-config ausführe erhalte ich folgende Fehlermeldung:

[2] [Feb 13 14:09:49] Traceback: (Logger.py|742)
[2] [Feb 13 14:09:49] line 3122 in '<module>' in file '/usr/bin/opsi-setup' (Logger.py|742)
[2] [Feb 13 14:09:49] line 3078 in 'main' in file '/usr/bin/opsi-setup' (Logger.py|742)
[2] [Feb 13 14:09:49] line 412 in 'configureClientUser' in file '/usr/bin/opsi-setup' (Logger.py|742)
[2] [Feb 13 14:09:49] line 245 in 'addConfidentialString' in file '/usr/lib/pymodules/python2.6/OPSI/Logger.py' (Logger.py|742)
[2] [Feb 13 14:09:49] ==>>> Cannot use empty string as confidential string (opsi-setup|3130)


Hat jemand eine Idee wie ich das beheben kann?

Gruss
Yves

Hi,

hast Du für das mysql Backend eine gültige Freischaltung (/etc/opsi/modules) ?

Hast Du die dispatch.conf angepasst ?

gruss
d.oertel

Hallo d.oertel

die dispatch.conf sieht wie folgt aus:

backend_.* : mysql, opsipxeconfd
host_.* : mysql, opsipxeconfd
productOnClient_.* : mysql, opsipxeconfd
configState_.* : mysql, opsipxeconfd
softwareLicense.* : mysql
audit.* : mysql
.* : mysql

Lizenz ist vorhanden, habe die neue Lizenz letzte Woche erhalten!

root@swihqop001:~# opsi-admin -d method backend_info
{
"opsiVersion" : "4.0.1.36",
"realmodules" :
{
"vpn" : "850",
"mysql_backend" : "850"
},
"modules" :
{
"customer" : "XXX",
"dynamic_depot" : false,
"vista" : true,
"treeview" : true,
"monitoring" : false,
"license_management" : false,
"swondemand" : true,
"expires" : "never",
"roaming_profiles" : false,
"valid" : true,
"multiplex" : false,
"signature" : "XXX",
"vpn" : true,
"mysql_backend" : true,
"high_availability" : false
}
}

Hi,

PN's sind bei mir abgeschaltet.

Linux Distribution und Version ?
Installierte opsi Server Pakete ?

gruss
d.oertel

Das hab ich soeben festgestellt

Ich verwende die Demo VM ab eurer Seite aktualisiert, neu gestartet mit den normalen Packeten ausser einem neuen opsi-client welcher ein Fehler behebt mit der modules Datei!


Linux swihqop001 2.6.32-21-generic #32-Ubuntu SMP Fri Apr 16 08:10:02 UTC 2010 i686 GNU/Linux


Zsync command found: /usr/bin/zsync
Modules file signature verified (customer: XXXX)
Reading config file '/etc/opsi/opsi-product-updater.conf'
Getting installed products
Getting info for local packages in '/var/lib/opsi/repository'
Getting package infos from repository 'http://download.uib.de'
hwaudit_4.0.4-1.opsi - installation not required: installed version '4.0.4-1' of product 'hwaudit' is up to date
javavm_1.6.0.20-2.opsi - installation not required: installed version '1.6.0.20-2' of product 'javavm' is up to date
jedit_4.4.1-2.opsi - installation not required: installed version '4.4.1-2' of product 'jedit' is up to date
opsi-adminutils_4.0.1.12-1.opsi - installation not required: installed version '4.0.1.12-1' of product 'opsi-adminutils' is up to date
opsi-client-agent_4.0.1-25.opsi - installation not required: installed version '4.0.1-26' of product 'opsi-client-agent' is up to date
opsi-template-with-admin_1.0-8.opsi - installation not required: installed version '1.0-8' of product 'opsi-template-with-admin' is up to date
opsi-template_4.0.1-3.opsi - installation not required: installed version '4.0.1-3' of product 'opsi-template' is up to date
opsi-winst-test_4.11.2-1.opsi - installation not required: installed version '4.11.2-1' of product 'opsi-winst-test' is up to date
opsi-winst_4.11.2.3-1.opsi - installation not required: installed version '4.11.2.3-1' of product 'opsi-winst' is up to date
shutdownwanted_1.0-4.opsi - installation not required: installed version '1.0-4' of product 'shutdownwanted' is up to date
swaudit_4.0-11.opsi - installation not required: installed version '4.0-11' of product 'swaudit' is up to date
xpconfig_2.6-1.opsi - installation not required: installed version '2.6-1' of product 'xpconfig' is up to date
hwinvent_4.0-1.opsi - installation not required: installed version '4.0-1' of product 'hwinvent' is up to date
memtest86_3.5b-1.opsi - installation not required: installed version '3.5b-1' of product 'memtest86' is up to date
ntfs-restore-image_4.0-1.opsi - installation not required: installed version '4.0-1' of product 'ntfs-restore-image' is up to date
ntfs-write-image_4.0-1.opsi - installation not required: installed version '4.0-1' of product 'ntfs-write-image' is up to date
win2k_4.0.1-3.opsi - installation not required: installed version '4.0.1-3' of product 'win2k' is up to date
win7-x64_4.0.1-5.opsi - installation not required: installed version '4.0.1-5' of product 'win7-x64' is up to date
win7_4.0.1-5.opsi - installation not required: installed version '4.0.1-5' of product 'win7' is up to date
win2003-r2-x64_4.0.1-3.opsi - installation not required: installed version '4.0.1-3' of product 'win2003-r2-x64' is up to date
win2003_4.0.1-3.opsi - installation not required: installed version '4.0.1-3' of product 'win2003' is up to date
win2008-r2_4.0.1-5.opsi - installation not required: installed version '4.0.1-5' of product 'win2008-r2' is up to date
win2008-x64_4.0.1-5.opsi - installation not required: installed version '4.0.1-5' of product 'win2008-x64' is up to date
win2008_4.0.1-5.opsi - installation not required: installed version '4.0.1-5' of product 'win2008' is up to date
winvista-x64_4.0.1-5.opsi - installation not required: installed version '4.0.1-5' of product 'winvista-x64' is up to date
winvista_4.0.1-5.opsi - installation not required: installed version '4.0.1-5' of product 'winvista' is up to date
winxppro-x64_4.0.1-3.opsi - installation not required: installed version '4.0.1-3' of product 'winxppro-x64' is up to date
winxppro_4.0.1-3.opsi - installation not required: installed version '4.0.1-3' of product 'winxppro' is up to date
wipedisk_1.0-2.opsi - installation not required: installed version '1.0-2' of product 'wipedisk' is up to date


Besten Dank für die Unterstützung.

Hi,

bitte mal probieren:
Hilft das ?

gruss
d.oertel

Hallo d.oertel

Hat funktioniert Ich habe den setPcppatchPassword jedoch vorher schon einmal ausgeführt! Kann es sein, dass durch die Umstellung von file auf mysql diese Einstellung verloren ging?

Besten Dank für den tollen Support.

Lg
Yves