Can no longer pxe boot to any of the prods

[Space_Cowboy1985]

Ive been setting up my server for a while, and I was able to use the net boot products with no problems. Ive been creating loads of software packages for the past week and finished today. Wouldnt you know it I go to do my first production machine and pxe products no longer work.

I set the job in the manager, and boot the client with pxe. It finds the opsi server ok but instead of booting say memtest it goes to setup. The job stays there like its never been touched.

Ive looked in the pxe log and it shows the client and the requested product but then a index error takes place. Im pretty stumped any ideas.

[5] [Nov 01 14:44:34] Got connection from client (opsipxeconfd|143)
[5] [Nov 01 14:44:34] Special pxe config template 'memtest86' will be used used for host 'proxmox-test.st-anselms.local', product 'memtest86' (opsipxeconfd|314)
[2] [Nov 01 14:44:34] Traceback: (Logger.py|742)
[2] [Nov 01 14:44:34] line 361 in 'updateBootConfiguration' in file '/usr/bin/opsipxeconfd' (Logger.py|742)
[2] [Nov 01 14:44:34] ==>>> list index out of range (opsipxeconfd|403)
[3] [Nov 01 14:44:34] list index out of range (opsipxeconfd|596)
adminuser@opsi:/var/log/opsi$ [5] [Nov 01 14:44:34] Got connection from client (opsipxeconfd|143)
bash: syntax error near unexpected token `('
adminuser@opsi:/var/log/opsi$ [5] [Nov 01 14:44:34] Special pxe config template 'memtest86' will be used used for host 'proxmox-test.st-anselms.local', product 'memtest86' (opsipxeconfd|314)
bash: syntax error near unexpected token `('
adminuser@opsi:/var/log/opsi$ [2] [Nov 01 14:44:34] Traceback: (Logger.py|742)
bash: syntax error near unexpected token `('
adminuser@opsi:/var/log/opsi$ [2] [Nov 01 14:44:34] line 361 in 'updateBootConfiguration' in file '/usr/bin/opsipxeconfd' (Logger.py|742)
bash: syntax error near unexpected token `('
adminuser@opsi:/var/log/opsi$ [2] [Nov 01 14:44:34] ==>>> list index out of range (opsipxeconfd|403)
bash: syntax error near unexpected token `>'
adminuser@opsi:/var/log/opsi$ [3] [Nov 01 14:44:34] list index out of range (opsipxeconfd|596)
bash: syntax error near unexpected token `('
adminuser@opsi:/var/log/opsi$

[d.oertel]

Hi,

please give us a listing of your opsi packages e.g.:

Code: Alles auswählen

dpkg -l | grep opsi
opsi-package-manager -l

try :

Code: Alles auswählen

opsi-setup --set-rights /tftpboot

regards

d.oertel

[Space_Cowboy1985]

ii opsi-atftpd 0.7.dfsg-1.7 advanced TFTP server - opsi version with pcre, fifo and max-blksize patches
ii opsi-configed 4.0.1.24-1 OPSI config editor
ii opsi-depotserver 4.0.2.1-1 opsi depotserver configuration package
ii opsi-linux-bootimage 20120119-1 opsi linux bootimage
ii opsi-utils 4.0.2.1-1 opsi utils
ii opsiconfd 4.0.2.1-1 opsi configuration service
ii opsipxeconfd 4.0.2.1-1 opsi pxe configuration daemon
ii python-opsi 4.0.2.1-1 opsi python library
ii whoopsie 0.1.32 Ubuntu crash database submission daemon

ERROR: Backend configuration error: Dispatch config file '/etc/opsi/backendManager/dispatch.conf' not found

[Space_Cowboy1985]

Hi,

Thanks for getting back to me...

Ive looked for the file that has errored, heres the permissions for it:

lrwxrwxrwx 1 root root 46 Oct 11 14:45 dispatch.conf -> /etc/opsi/backendManager/dispatch.conf.default
-rw-rw---- 1 opsiconfd opsiadmin 1898 May 31 11:16 dispatch.conf.default

Does the link need changing to opsiadmin or something along those lines?

[d.oertel]

Hi,

try:

Code: Alles auswählen

opsi-setup --set-rigths

and - you should update to the newest packages:
viewtopic.php?f=10&t=3971

Code: Alles auswählen

aptitude update
aptitude dist-upgrade
opsi-produt-updater -i -vv

regards

d.oertel

[Space_Cowboy1985]

Hi,

The opsi package manager has displayed the following

Product ID Version Name
=======================================================
adobereader 10.1.4-1 Adobe Read
config-win-base 4.0.1-1 Windows Cu
dotnet4 4.0.30319.1-1 .net4
flash 11.4.402.287-1 Flash
hwaudit 4.0.5-1 Client Har
hwinvent 4.0-1 Hardware I
java 7.0.90.5-1 Java
javavm 1.6.0.33-2 Oracle Jav
jedit 4.5.2-2 jEdit prog
kaspersky 6.0.4.1424-1 Kaspersky
memtest86 3.5b-1 Memtest86+
ntfs-restore-image 4.0-1 NTFS Image
ntfs-write-image 4.0-1 NTFS Image
office2010 14.0.4755.1000-1 Office2010
opsi-adminutils 4.0.2.1-2 some admin
opsi-client-agent 4.0.2.1-2 opsi.org c
opsi-template 4.0.2-2 opsi templ
opsi-template-with-admin 4.0.2-2 opsi templ
opsi-winst 4.11.3.3-1 winst
opsi-winst-test 4.11.3-3 opsi-winst
shutdownwanted 1.0-4 shutdown w
sims 7.146-1 Sims
smart11 11-1 Smart 11
swaudit 4.0.2-1 Client sof
vlc 2.0.3-1 VLC
win2003 4.0.2-1 Windows 20
win2003-r2-x64 4.0.2-1 Windows Se
win2008 4.0.2-1 Windows Se
win2008-r2 4.0.2-1 Windows Se
win2008-x64 4.0.2-1 Windows Se
win2k 4.0.2-1 Windows 20
win7 4.0.2-1 Windows 7
win7-x64 4.0.2-1 Windows 7
winvista 4.0.2-1 Windows Vi
winvista-x64 4.0.2-1 Windows Vi
winxppro 4.0.2-1 Windows XP
winxppro-x64 4.0.2-1 Windows XP
wipedisk 1.0-2 Festplatte

Ive been through all your suggestions, but its still the same...

[d.oertel]

Hi,

what is the output of:

Code: Alles auswählen

opsi-setup --init-current-config
opsi-setup --set-rights
/etc/init.d/opsiconfd restart
/etc/init.d/opsipxeconfd restart

regards

d.oertel

[Space_Cowboy1985]

opsi-setup --init-current-config wont run under adminuser account, I dont know wether thats an issue, it was the same for opsi-setup --set-rights and the restarts also

using root it gives:

[5] [Nov 02 13:18:51] Creating base path: '/var/lib/opsi/config' (File.py|222)
[5] [Nov 02 13:18:51] Try to find a Configserver. (opsi-setup|2462)
[5] [Nov 02 13:18:51] Getting current system config (opsi-setup|76)
[5] [Nov 02 13:18:51] System information: (opsi-setup|126)
[5] [Nov 02 13:18:51] distributor : Ubuntu (opsi-setup|127)
[5] [Nov 02 13:18:51] distribution : Ubuntu 12.04.1 LTS (opsi-setup|128)
[5] [Nov 02 13:18:51] ip address : 10.84.8.126 (opsi-setup|129)
[5] [Nov 02 13:18:51] netmask : 255.255.252.0 (opsi-setup|130)
[5] [Nov 02 13:18:51] subnet : 10.84.8.0 (opsi-setup|131)
[5] [Nov 02 13:18:51] broadcast : 10.84.11.255 (opsi-setup|132)
[5] [Nov 02 13:18:51] fqdn : opsi.st-anselms.local (opsi-setup|133)
[5] [Nov 02 13:18:51] hostname : opsi (opsi-setup|134)
[5] [Nov 02 13:18:51] domain : st-anselms.local (opsi-setup|135)
[5] [Nov 02 13:18:51] win domain : WORKGROUP (opsi-setup|136)
[5] [Nov 02 13:18:51] Creating base path: '/var/lib/opsi/config' (File.py|222)
[5] [Nov 02 13:18:51] Configuring client user pcpatch (opsi-setup|359)
[5] [Nov 02 13:18:51] Creating RSA private key for user pcpatch in '/var/lib/opsi/.ssh/id_rsa' (opsi-setup|373)
[5] [Nov 02 13:18:51] Setting rights (opsi-setup|422)
[5] [Nov 02 13:18:52] Setting rights on directory '/var/lib/opsi/.ssh' (opsi-setup|503)

[5] [Nov 02 13:21:06] Setting rights (opsi-setup|422)
[5] [Nov 02 13:21:06] Getting current system config (opsi-setup|76)
[5] [Nov 02 13:21:06] System information: (opsi-setup|126)
[5] [Nov 02 13:21:06] distributor : Ubuntu (opsi-setup|127)
[5] [Nov 02 13:21:06] distribution : Ubuntu 12.04.1 LTS (opsi-setup|128)
[5] [Nov 02 13:21:06] ip address : 10.84.8.126 (opsi-setup|129)
[5] [Nov 02 13:21:06] netmask : 255.255.252.0 (opsi-setup|130)
[5] [Nov 02 13:21:06] subnet : 10.84.8.0 (opsi-setup|131)
[5] [Nov 02 13:21:06] broadcast : 10.84.11.255 (opsi-setup|132)
[5] [Nov 02 13:21:06] fqdn : opsi.st-anselms.local (opsi-setup|133)
[5] [Nov 02 13:21:06] hostname : opsi (opsi-setup|134)
[5] [Nov 02 13:21:06] domain : st-anselms.local (opsi-setup|135)
[5] [Nov 02 13:21:06] win domain : WORKGROUP (opsi-setup|136)
[5] [Nov 02 13:21:06] Setting rights on directory '/tftpboot/linux' (opsi-setup|503)
[5] [Nov 02 13:21:06] Setting rights on directory '/home/opsiproducts' (opsi-setup|503)
[5] [Nov 02 13:21:07] Setting rights on directory '/var/log/opsi' (opsi-setup|503)
[5] [Nov 02 13:21:07] Setting rights on directory '/etc/opsi' (opsi-setup|503)
[5] [Nov 02 13:21:07] Setting rights on directory '/var/lib/opsi' (opsi-setup|503)
[5] [Nov 02 13:21:07] Setting rights on directory '/var/lib/opsi/depot' (opsi-setup|503)

The restarts both completed fine

Stopping opsi pxe configuration service... .(done).
Starting opsi pxe configuration service..... (done).

[Space_Cowboy1985]

I dont know wether this will help its from the clients opsiconfd.log

[4] [Nov 02 13:49:16] Failed to read opsi modules file '/etc/opsi/modules': [Errno 2] No such file or directory: u'/etc/opsi/modules' (Backend.py|371)
[5] [Nov 02 13:49:16] Application 'opsiclientd version 4.0.71' on client '10.84.9.126' did not send cookie (workers.py|161)
[5] [Nov 02 13:49:16] New session created (session.py|75)
[5] [Nov 02 13:49:16] Authorization request from host proxmox-test.st-anselms.local@10.84.9.126 (application: opsiclientd version 4.0.71) (workers.py|186)
[4] [Nov 02 13:49:16] Failed to read opsi modules file '/etc/opsi/modules': [Errno 2] No such file or directory: u'/etc/opsi/modules' (Backend.py|371)
[5] [Nov 02 13:49:16] -----> Executing: backend_getInterface() (JsonRpc.py|123)
[4] [Nov 02 13:49:16] Failed to read opsi modules file '/etc/opsi/modules': [Errno 2] No such file or directory: u'/etc/opsi/modules' (Backend.py|371)
[5] [Nov 02 13:49:16] -----> Executing: backend_info() (JsonRpc.py|123)
[4] [Nov 02 13:49:16] Failed to read opsi modules file '/etc/opsi/modules': [Errno 2] No such file or directory: u'/etc/opsi/modules' (Backend.py|371)
[4] [Nov 02 13:49:16] Failed to read opsi modules file '/etc/opsi/modules': [Errno 2] No such file or directory: u'/etc/opsi/modules' (Backend.py|371)
[5] [Nov 02 13:49:16] -----> Executing: backend_info() (JsonRpc.py|123)
[4] [Nov 02 13:49:16] Failed to read opsi modules file '/etc/opsi/modules': [Errno 2] No such file or directory: u'/etc/opsi/modules' (Backend.py|371)
[4] [Nov 02 13:49:16] Failed to read opsi modules file '/etc/opsi/modules': [Errno 2] No such file or directory: u'/etc/opsi/modules' (Backend.py|371)
[5] [Nov 02 13:49:16] -----> Executing: dispatcher_getConfig() (JsonRpc.py|123)
[4] [Nov 02 13:49:16] Failed to read opsi modules file '/etc/opsi/modules': [Errno 2] No such file or directory: u'/etc/opsi/modules' (Backend.py|371)
[5] [Nov 02 13:49:16] -----> Executing: accessControl_authenticated() (JsonRpc.py|123)
[4] [Nov 02 13:49:20] Failed to read opsi modules file '/etc/opsi/modules': [Errno 2] No such file or directory: u'/etc/opsi/modules' (Backend.py|371)
[5] [Nov 02 13:49:20] -----> Executing: backend_setOptions({u'addConfigStateDefaults': True}) (JsonRpc.py|123)
[4] [Nov 02 13:49:20] Failed to read opsi modules file '/etc/opsi/modules': [Errno 2] No such file or directory: u'/etc/opsi/modules' (Backend.py|371)
[5] [Nov 02 13:49:20] -----> Executing: configState_getObjects([], {'objectId': u'proxmox-test.st-anselms.local'}) (JsonRpc.py|123)
[4] [Nov 02 13:49:20] Failed to read opsi modules file '/etc/opsi/modules': [Errno 2] No such file or directory: u'/etc/opsi/modules' (Backend.py|371)
[5] [Nov 02 13:49:21] -----> Executing: productOnClient_getObjects([u'actionRequest'], {'actionRequest': [u'setup', u'uninstall', u'update', u'always', u'once', u'custom'], 'clientId': u'proxmox-test.st-anselms.local', 'productType': u'LocalbootProduct'}) (JsonRpc.py|123)
[4] [Nov 02 13:49:24] Failed to read opsi modules file '/etc/opsi/modules': [Errno 2] No such file or directory: u'/etc/opsi/modules' (Backend.py|371)
[5] [Nov 02 13:49:24] -----> Executing: backend_setOptions({u'addConfigStateDefaults': True}) (JsonRpc.py|123)
[4] [Nov 02 13:49:24] Failed to read opsi modules file '/etc/opsi/modules': [Errno 2] No such file or directory: u'/etc/opsi/modules' (Backend.py|371)
[5] [Nov 02 13:49:24] -----> Executing: configState_getObjects([], {'objectId': u'proxmox-test.st-anselms.local'}) (JsonRpc.py|123)
[4] [Nov 02 13:49:24] Failed to read opsi modules file '/etc/opsi/modules': [Errno 2] No such file or directory: u'/etc/opsi/modules' (Backend.py|371)
[5] [Nov 02 13:49:24] -----> Executing: log_write(u'clientconnect', u'[6] [Nov 02 13:49:06] [ opsiclientd ] Setting config value event_sync_completed{cache_ready}.reboot (Config.pyo|197)\r\n[6] [Nov 02 13:49:06] [ opsiclientd ...) (JsonRpc.py|123)
[4] [Nov 02 13:49:24] Failed to read opsi modules file '/etc/opsi/modules': [Errno 2] No such file or directory: u'/etc/opsi/modules' (Backend.py|371)
[5] [Nov 02 13:49:24] User 'proxmox-test.st-anselms.local' asked to close the session (workers.py|434)
[5] [Nov 02 13:49:24] Session 'F3qKHqJ9oLsa2EuHLpGucgKyDd5p8H9j' from ip '10.84.9.126', application 'opsiclientd version 4.0.71' deleted (Session.py|211)

It takes at the same time I try to a pxe boot to a product..

[d.oertel]

Hi,

looks good so far.
The /etc/opsi/modules file warnings should be ignored.
The commands mentioned in my last post have to be started using the root account.

What is the log of the opsipxeconfd if you set the actionrequest setup for the netbootproduct hwinvent and then start your client.

regards

d.oertel