[GELÖST] Netboot Problem

MEFE
Beiträge: 6
Registriert: 26 Mär 2012, 08:33

[GELÖST] Netboot Problem

Beitragvon MEFE » 26 Mär 2012, 09:24

Hallo,

Ich habe opsi 4.0 auf einer openSuse 11.3-Maschine installiert. Die Softwareverteilung klappt soweit super, jedoch funktioniert meine Netboot-Installationen nicht.
Ich lasse den Client via Netzwerk booten, dann ladet er über DHCP ziemlich lange und fährt nach einiger Zeit einfach Windows hoch.
Anbei meine dispatch.conf (Der opsi-Server ist auch der DHCP-Server).

dispatch.conf

Code: Alles auswählen

# -*- coding: utf-8 -*-
# = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
# =      backend dispatch configuration                                                                         =
# = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
#
# This file configures which methods are dispatched to which backends.
# Entries has to follow the form:
# <regular expression to match method name(s)> : <comma separated list of backend name(s)>
#
# Backend names have to match a backend configuraton file basename <backend name>.conf beneath /etc/opsi/backends.
# For every method executed on backend dispatcher the first matching regular expression will be decisive.
#
# Typical configurations:
#    file, opsipxeconfd and dhcpd backend:
#       backend_.*         : file, opsipxeconfd, dhcpd
#       host_.*            : file, opsipxeconfd, dhcpd
#       productOnClient_.* : file, opsipxeconfd
#       configState_.*     : file, opsipxeconfd
#       .*                 : file
#
#    jsonrpc, opsipxeconfd and dhcpd backend:
#       backend_.*         : jsonrpc, opsipxeconfd, dhcpd
#       .*                 : jsonrpc
#
#    ldap as main backend, mysql as hw/sw invent and license management backend, opsipxeconfd and dhcpd backend:
#       backend_.*         : ldap, mysql, opsipxeconfd, dhcpd
#       host_.*            : ldap, opsipxeconfd, dhcpd
#       productOnClient_.* : ldap, opsipxeconfd
#       configState_.*     : ldap, opsipxeconfd
#       license.*          : mysql
#       softwareLicense.*  : mysql
#       audit.*            : mysql
#       .*                 : ldap
#

backend_.*         : file, opsipxeconfd, dhcpd
host_.*            : file, opsipxeconfd, dhcpd
productOnClient_.* : file, opsipxeconfd
configState_.*     : file, opsipxeconfd
.*                 : file



Die Dienste opsiconfd und opsipxeconfd laufen beide ebenfalls.

Ich hoffe mir kann jm. helfen :)

Edit:
hier noch ein Auszug meiner opsipxeconfd.log:

Code: Alles auswählen

[5] [Mar 26 11:45:54] Starting opsipxeconfd main thread (opsipxeconfd|163)
[5] [Mar 26 11:45:54] Ignoring module 'OpsiPXEConfd', backend 'opsipxeconfd' (BackendManager.py|328)
[5] [Mar 26 11:45:55] Creating unix socket '/var/run/opsipxeconfd/opsipxeconfd.socket' (opsipxeconfd|120)
[5] [Mar 26 11:45:55] Start setting needed boot configurations (opsipxeconfd|421)
[5] [Mar 26 11:45:55] PXE boot configuration for host edv-pc.drktg.opsi is now set at '/tftpboot/linux/pxelinux.cfg/01-50-e5-49-14-d9-14' (opsipxeconfd|393)
[5] [Mar 26 11:45:55] Finished setting needed boot configurations (opsipxeconfd|447)
[5] [Mar 26 12:12:01] Got connection from client (opsipxeconfd|143)
[5] [Mar 26 12:12:02] PXE boot configuration for host 'edv-pc.drktg.opsi' removed (opsipxeconfd|258)
[5] [Mar 26 12:12:07] Got connection from client (opsipxeconfd|143)
[5] [Mar 26 12:12:07] PXE boot configuration for host edv-pc.drktg.opsi is now set at '/tftpboot/linux/pxelinux.cfg/01-50-e5-49-14-d9-14' (opsipxeconfd|393)
Zuletzt geändert von MEFE am 03 Apr 2012, 08:20, insgesamt 2-mal geändert.

Benutzeravatar
d.oertel
uib-Team
Beiträge: 3276
Registriert: 04 Jun 2008, 14:27

Re: Netboot Problem

Beitragvon d.oertel » 26 Mär 2012, 17:50

Hi,


bitte mal die Meldungen des tftpd aus der /var/log/syslog sichten bzw. posten.

gruss
d.oertel
opsi support - uib gmbh

For productive opsi installations we recommend support contracts.
http://www.uib.de
http://www.opsi.org

Benutzeravatar
wolfbardo
uib-Team
Beiträge: 1157
Registriert: 01 Jul 2008, 12:10

Re: Netboot Problem

Beitragvon wolfbardo » 26 Mär 2012, 20:08

und mal nach der Firewall schauen,

Gruss
Bardo Wolf


!!! ANMELDEN !!! opsi-Konferenz in Mainz am 02. / 03. März 2020 https://opsiconf.org

opsi workshops

https://uib.de/de/support-schulung/schulung/

Basis
23.-26.3.2020


opsi support by uib gmbh

http://www.uib.de

MEFE
Beiträge: 6
Registriert: 26 Mär 2012, 08:33

Re: Netboot Problem

Beitragvon MEFE » 27 Mär 2012, 08:01

Hallo,

die Firewall ist aus, daran hatte ich auch schon gedacht.

Leider kann ich die Meldungen des tftp aus var/log/syslog nicht posten, weil es ihn nicht gibt: :oops:

Code: Alles auswählen

slsopsi:/var/log # ls
acpid     boot.omsg   kdm.log        mail.err   NetworkManager  pk_backend_zypp   wtmp            zypp
apparmor  ConsoleKit  krb5           mail.info  news            pm-powersave.log  xinetd.log      zypper.log
audit     cups        lastlog        mail.warn  ntp             rc.dhcpd.log      Xorg.0.log
boot.log  faillog     localmessages  messages   opsi            samba             Xorg.0.log.old
boot.msg  firewall    mail           mysql      PackageKit      warn              YaST2


Edit:
Der syslog-Dienst läuft.

Benutzeravatar
d.oertel
uib-Team
Beiträge: 3276
Registriert: 04 Jun 2008, 14:27

Re: Netboot Problem

Beitragvon d.oertel » 27 Mär 2012, 10:27

Hi,

dann schau mal in die Datei
messages

gruss
d.oertel
opsi support - uib gmbh

For productive opsi installations we recommend support contracts.
http://www.uib.de
http://www.opsi.org

MEFE
Beiträge: 6
Registriert: 26 Mär 2012, 08:33

Re: Netboot Problem

Beitragvon MEFE » 27 Mär 2012, 11:27

Hallo,

kein einziger Eintrag über tftp zu finden, hier ein Ausschnitt von einem Zeitraum, in dem ich versucht habe, ein Netboot-Product auf dem Client zu installieren:

Code: Alles auswählen

Mar 27 10:43:16 slsopsi dhcpd: DHCPDISCOVER from 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:17 slsopsi dhcpd: DHCPOFFER on 192.168.45.53 to 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:18 slsopsi dhcpd: DHCPDISCOVER from 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:18 slsopsi dhcpd: DHCPOFFER on 192.168.45.53 to 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:20 slsopsi dhcpd: DHCPDISCOVER from 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:20 slsopsi dhcpd: DHCPOFFER on 192.168.45.53 to 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:22 slsopsi dhcpd: DHCPDISCOVER from 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:22 slsopsi dhcpd: DHCPOFFER on 192.168.45.53 to 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:24 slsopsi dhcpd: DHCPDISCOVER from 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:24 slsopsi dhcpd: DHCPOFFER on 192.168.45.53 to 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:26 slsopsi dhcpd: DHCPDISCOVER from 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:26 slsopsi dhcpd: DHCPOFFER on 192.168.45.53 to 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:28 slsopsi dhcpd: DHCPDISCOVER from 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:28 slsopsi dhcpd: DHCPOFFER on 192.168.45.53 to 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:30 slsopsi dhcpd: DHCPDISCOVER from 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:30 slsopsi dhcpd: DHCPOFFER on 192.168.45.53 to 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:32 slsopsi dhcpd: DHCPDISCOVER from 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:32 slsopsi dhcpd: DHCPOFFER on 192.168.45.53 to 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:34 slsopsi dhcpd: DHCPDISCOVER from 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:34 slsopsi dhcpd: DHCPOFFER on 192.168.45.53 to 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:37 slsopsi dhcpd: DHCPDISCOVER from 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:37 slsopsi dhcpd: DHCPOFFER on 192.168.45.53 to 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:39 slsopsi dhcpd: DHCPDISCOVER from 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:39 slsopsi dhcpd: DHCPOFFER on 192.168.45.53 to 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:41 slsopsi dhcpd: DHCPDISCOVER from 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:41 slsopsi dhcpd: DHCPOFFER on 192.168.45.53 to 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:43 slsopsi dhcpd: DHCPDISCOVER from 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:43 slsopsi dhcpd: DHCPOFFER on 192.168.45.53 to 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:45 slsopsi dhcpd: DHCPDISCOVER from 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:45 slsopsi dhcpd: DHCPOFFER on 192.168.45.53 to 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:47 slsopsi dhcpd: DHCPDISCOVER from 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:47 slsopsi dhcpd: DHCPOFFER on 192.168.45.53 to 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:49 slsopsi dhcpd: DHCPDISCOVER from 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:49 slsopsi dhcpd: DHCPOFFER on 192.168.45.53 to 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:51 slsopsi dhcpd: DHCPDISCOVER from 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:51 slsopsi dhcpd: DHCPOFFER on 192.168.45.53 to 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:53 slsopsi dhcpd: DHCPDISCOVER from 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:53 slsopsi dhcpd: DHCPOFFER on 192.168.45.53 to 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:55 slsopsi dhcpd: DHCPDISCOVER from 50:e5:49:14:d9:14 via eth0
Mar 27 10:43:55 slsopsi dhcpd: DHCPOFFER on 192.168.45.53 to 50:e5:49:14:d9:14 via eth0
Mar 27 10:44:15 slsopsi dhcpd: DHCPREQUEST for 192.168.45.50 from 50:e5:49:14:d9:14 (edv-PC) via eth0
Mar 27 10:44:15 slsopsi dhcpd: DHCPACK on 192.168.45.50 to 50:e5:49:14:d9:14 (edv-PC) via eth0
Mar 27 10:44:19 slsopsi dhcpd: DHCPINFORM from 192.168.45.50 via eth0: not authoritative for subnet 192.168.45.0
Mar 27 10:44:22 slsopsi dhcpd: DHCPINFORM from 192.168.45.50 via eth0: not authoritative for subnet 192.168.45.0


Ich hab nochmals überprüft, ob der opsi-atftp installiert ist, laut YAST ist er das. Wenn ich versuche über zypper zu installieren, sagt er mir, dass dieses Paket schon installiert ist.

Benutzeravatar
d.oertel
uib-Team
Beiträge: 3276
Registriert: 04 Jun 2008, 14:27

Re: Netboot Problem

Beitragvon d.oertel » 27 Mär 2012, 13:13

Hi,

dann gibt es zwei wahrscheinliche Möglichkeiten:

a) dhcp ist nicht korrekt konfiguriert:
http://download.uib.de/opsi4.0/doc/html/opsi-getting-started/opsi-getting-started.html#opsi-getting-started-installation-config-dhcp
b) tftp ist nicht in ordnung

Um das zu prüfen empfehle ich zu schauen ob beim Server tftp Anfragen vom client ankommen z.B.
tcpdump port tftp

Wenn nicht - dann a)
Wenn ja - dann b)

gruss
d.oertel
opsi support - uib gmbh

For productive opsi installations we recommend support contracts.
http://www.uib.de
http://www.opsi.org

uncle_scrooge
Beiträge: 596
Registriert: 21 Feb 2012, 12:03
Wohnort: Mainz

Re: Netboot Problem

Beitragvon uncle_scrooge » 27 Mär 2012, 13:42

Mar 27 10:44:19 slsopsi dhcpd: DHCPINFORM from 192.168.45.50 via eth0: not authoritative for subnet 192.168.45.0
Mar 27 10:44:22 slsopsi dhcpd: DHCPINFORM from 192.168.45.50 via eth0: not authoritative for subnet 192.168.45.0


Mal spaßeshalber in der dhcpd.conf die Direktive 'authoritative' auskommentieren.
Und den dhcpd neu starten

MEFE
Beiträge: 6
Registriert: 26 Mär 2012, 08:33

Re: Netboot Problem

Beitragvon MEFE » 27 Mär 2012, 16:39

Hallo,

@uncle_scrooge: Hab es auskommentiert, hat aber auch nichts gebracht.

Leider hat mir

Code: Alles auswählen

tcpdump port tftp -vv

keine tftp-Anfragen geliefert.

Also liegt wohl an meinem dhcp-Konfigurationen. Ich weiß zwar jetzt, dass Ihr damit nichts
am Hut habt, aber ich selbst kann mir nicht mehr helfen, für mich sieht die dhcpd.conf okay aus:

Code: Alles auswählen

#
# Define RFC 3442 classless static route option (121);
# the following _example_ routes:
#    192.168.2.254/32 via 0.0.0.0     (device route)
#    192.168.2.253/32 via 192.168.1.2 (255.255.255.255)
#    192.2.0.128/25   via 192.168.1.2 (255.255.255.128)
#    192.168.2.0/24   via 192.168.1.2 (255.255.255.0)
#    172.16.0.0/12    via 192.168.1.2 (255.240.0.0)
#    10.0.0.0/8       via 192.168.1.2 (255.0.0.0)
#    default          via 192.168.1.1
# have to be written as:
#    option rfc3442-classless-static-routes
#           32,  192, 168, 2, 254,    0,   0, 0, 0,
#           32,  192, 168, 2, 253,  192, 168, 1, 2,
#           25,  192,   2, 0, 128,  192, 168, 1, 2,
#           24,  192, 168, 3,       192, 168, 1, 2,
#           12,  172, 16,           192, 168, 1, 2,
#            8,   10,               192, 168, 1, 2,
#            0,                     192, 168, 1, 1;
#
# Note: you have to specify the default gateway here
# as well, because when classless routes are in use,
# the 'routers' option is ignored by the dhcp client.
#
option rfc3442-classless-static-routes code 121 = array of unsigned integer 8;
option domain-name "drktg.opsi";
option domain-name-servers 192.168.45.10;
option routers 192.168.45.2;
max-lease-time 7200;
# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
authoritative;
# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
log-facility local7;
default-lease-time 600;
include "/etc/named.d/dns.key";
ddns-update-style interim;
ignore client-updates;
ddns-updates on;
use-host-decl-names on;
subnet 192.168.45.0 netmask 255.255.255.0 {
  range dynamic-bootp 192.168.45.50 192.168.45.100;
  default-lease-time 14400;
  max-lease-time 172800;
  zone drktg.opsi. {      primary 192.168.45.10;      key dhcp_updates;   }
  zone 45.168.192.in-addr.arpa. {      primary 192.168.45.10;      key dhcp_updates;   }
  group {
    next-server 192.168.45.10;
    filename "linux/pxelinux.0";
  }
}



Meine opsipxeconf hat sich jetzt auch verändert:

Code: Alles auswählen

7] [Mar 27 16:03:03] Parsing ini file '/var/lib/opsi/config/depots/slsopsi.drktg.opsi.ini' (__init__.py|489)
[7] [Mar 27 16:03:03] Trying to lock file '/var/lib/opsi/config/depots/slsopsi.drktg.opsi.ini' (0/2000) (__init__.py|190)
[7] [Mar 27 16:03:03] File '/var/lib/opsi/config/depots/slsopsi.drktg.opsi.ini' locked after 0 millis (__init__.py|212)
[7] [Mar 27 16:03:03] Finished reading file after 0.018 seconds (__init__.py|565)
[7] [Mar 27 16:03:03] Testing match of filter 'slsopsi.drktg.opsi' of attribute 'objectId' with value 'slsopsi.drktg.opsi' (Backend.py|194)
[7] [Mar 27 16:03:03] Value 'slsopsi.drktg.opsi' matched filter 'slsopsi.drktg.opsi', attribute 'objectId' (Backend.py|242)
[7] [Mar 27 16:03:03] Testing match of filter '[u'winxppro']' of attribute 'productId' with value 'winxppro' (Backend.py|194)
[7] [Mar 27 16:03:03] Value 'winxppro' matched filter '[u'winxppro']', attribute 'productId' (Backend.py|242)
[7] [Mar 27 16:03:03] Getting config file for 'ProductPropertyState', '{'objectId': u'slsopsi.drktg.opsi', 'propertyId': u'additional_drivers', 'productId': u'winxppro'}', 'ini' (File.py|295)
[7] [Mar 27 16:03:03] Testing match of filter 'slsopsi.drktg.opsi' of attribute 'objectId' with value 'slsopsi.drktg.opsi' (Backend.py|194)
[7] [Mar 27 16:03:03] Value 'slsopsi.drktg.opsi' matched filter 'slsopsi.drktg.opsi', attribute 'objectId' (Backend.py|242)
[7] [Mar 27 16:03:03] Testing match of filter '[u'winxppro']' of attribute 'productId' with value 'winxppro' (Backend.py|194)
[7] [Mar 27 16:03:03] Value 'winxppro' matched filter '[u'winxppro']', attribute 'productId' (Backend.py|242)
[7] [Mar 27 16:03:03] Getting config file for 'ProductPropertyState', '{'objectId': u'slsopsi.drktg.opsi', 'propertyId': u'i386_dir', 'productId': u'winxppro'}', 'ini' (File.py|295)
[7] [Mar 27 16:03:03] Testing match of filter 'slsopsi.drktg.opsi' of attribute 'objectId' with value 'slsopsi.drktg.opsi' (Backend.py|194)
[7] [Mar 27 16:03:03] Value 'slsopsi.drktg.opsi' matched filter 'slsopsi.drktg.opsi', attribute 'objectId' (Backend.py|242)
[7] [Mar 27 16:03:03] Testing match of filter '[u'winxppro']' of attribute 'productId' with value 'winxppro' (Backend.py|194)
[7] [Mar 27 16:03:03] Value 'winxppro' matched filter '[u'winxppro']', attribute 'productId' (Backend.py|242)
[7] [Mar 27 16:03:03] Getting config file for 'ProductPropertyState', '{'objectId': u'slsopsi.drktg.opsi', 'propertyId': u'askbeforeinst', 'productId': u'winxppro'}', 'ini' (File.py|295)
[7] [Mar 27 16:03:03] Testing match of filter 'slsopsi.drktg.opsi' of attribute 'objectId' with value 'slsopsi.drktg.opsi' (Backend.py|194)
[7] [Mar 27 16:03:03] Value 'slsopsi.drktg.opsi' matched filter 'slsopsi.drktg.opsi', attribute 'objectId' (Backend.py|242)
[7] [Mar 27 16:03:03] Testing match of filter '[u'winxppro']' of attribute 'productId' with value 'winxppro' (Backend.py|194)
[7] [Mar 27 16:03:03] Value 'winxppro' matched filter '[u'winxppro']', attribute 'productId' (Backend.py|242)
[7] [Mar 27 16:03:03] Getting config file for 'ProductPropertyState', '{'objectId': u'slsopsi.drktg.opsi', 'propertyId': u'windows_partition_size', 'productId': u'winxppro'}', 'ini' (File.py|295)
[7] [Mar 27 16:03:03] Testing match of filter 'slsopsi.drktg.opsi' of attribute 'objectId' with value 'slsopsi.drktg.opsi' (Backend.py|194)
[7] [Mar 27 16:03:03] Value 'slsopsi.drktg.opsi' matched filter 'slsopsi.drktg.opsi', attribute 'objectId' (Backend.py|242)
[7] [Mar 27 16:03:03] Testing match of filter '[u'winxppro']' of attribute 'productId' with value 'winxppro' (Backend.py|194)
[7] [Mar 27 16:03:03] Value 'winxppro' matched filter '[u'winxppro']', attribute 'productId' (Backend.py|242)
[7] [Mar 27 16:03:03] Getting config file for 'ProductPropertyState', '{'objectId': u'slsopsi.drktg.opsi', 'propertyId': u'productkey', 'productId': u'winxppro'}', 'ini' (File.py|295)
[7] [Mar 27 16:03:03] Testing match of filter 'slsopsi.drktg.opsi' of attribute 'objectId' with value 'slsopsi.drktg.opsi' (Backend.py|194)
[7] [Mar 27 16:03:03] Value 'slsopsi.drktg.opsi' matched filter 'slsopsi.drktg.opsi', attribute 'objectId' (Backend.py|242)
[7] [Mar 27 16:03:03] Testing match of filter '[u'winxppro']' of attribute 'productId' with value 'winxppro' (Backend.py|194)
[7] [Mar 27 16:03:03] Value 'winxppro' matched filter '[u'winxppro']', attribute 'productId' (Backend.py|242)
[7] [Mar 27 16:03:03] Getting config file for 'ProductPropertyState', '{'objectId': u'slsopsi.drktg.opsi', 'propertyId': u'fullname', 'productId': u'winxppro'}', 'ini' (File.py|295)
[7] [Mar 27 16:03:03] Testing match of filter 'slsopsi.drktg.opsi' of attribute 'objectId' with value 'slsopsi.drktg.opsi' (Backend.py|194)
[7] [Mar 27 16:03:03] Value 'slsopsi.drktg.opsi' matched filter 'slsopsi.drktg.opsi', attribute 'objectId' (Backend.py|242)
[7] [Mar 27 16:03:03] Testing match of filter '[u'winxppro']' of attribute 'productId' with value 'winxppro' (Backend.py|194)
[7] [Mar 27 16:03:03] Value 'winxppro' matched filter '[u'winxppro']', attribute 'productId' (Backend.py|242)
[7] [Mar 27 16:03:03] Getting config file for 'ProductPropertyState', '{'objectId': u'slsopsi.drktg.opsi', 'propertyId': u'store_i386', 'productId': u'winxppro'}', 'ini' (File.py|295)
[7] [Mar 27 16:03:03] Testing match of filter 'slsopsi.drktg.opsi' of attribute 'objectId' with value 'slsopsi.drktg.opsi' (Backend.py|194)
[7] [Mar 27 16:03:03] Value 'slsopsi.drktg.opsi' matched filter 'slsopsi.drktg.opsi', attribute 'objectId' (Backend.py|242)
[7] [Mar 27 16:03:03] Testing match of filter '[u'winxppro']' of attribute 'productId' with value 'winxppro' (Backend.py|194)
[7] [Mar 27 16:03:03] Value 'winxppro' matched filter '[u'winxppro']', attribute 'productId' (Backend.py|242)
[6] [Mar 27 16:03:03] Creating thread for pxeconfig 1 (opsipxeconfd|387)
[6] [Mar 27 16:03:03] PXEConfigWriter initializing: templatefile '/tftpboot/linux/pxelinux.cfg/install', pxefile '/tftpboot/linux/pxelinux.cfg/01-50-e5-49-14-d9-14', hostId 'edv-pc.drktg.opsi', append {'dn': u'drktg.opsi', 'product': u'winxppro', 'hn': u'edv-pc', 'pckey': u'*** confidential ***', 'service': u'https://192.168.45.10:4447/rpc'} (opsipxeconfd|471)
[5] [Mar 27 16:03:03] PXE boot configuration for host edv-pc.drktg.opsi is now set at '/tftpboot/linux/pxelinux.cfg/01-50-e5-49-14-d9-14' (opsipxeconfd|393)
[5] [Mar 27 16:03:03] Finished setting needed boot configurations (opsipxeconfd|447)


"winxppro" ist das Paket, dass ich installieren möchte. Aber trotz der Veränderung der opsipxeconfd bleibt das Urproblem noch bestehen.

Benutzeravatar
d.oertel
uib-Team
Beiträge: 3276
Registriert: 04 Jun 2008, 14:27

Re: Netboot Problem

Beitragvon d.oertel » 27 Mär 2012, 17:01

Hi,

die einträge nextserver und filename müssen auf der selben oder einer höheren ebene stehen wie die an der die IP-Nummern vergeben werden und das ist bei Dir der range befehl.

gruss
d.oertel
opsi support - uib gmbh

For productive opsi installations we recommend support contracts.
http://www.uib.de
http://www.opsi.org