PXE + 'MAC-address-file' owned by root.root

Antworten
EricT
Beiträge: 20
Registriert: 18 Nov 2011, 12:49

PXE + 'MAC-address-file' owned by root.root

Beitrag von EricT »

Hello,

we recently bought the image-backup-module, configured PXE-boot so clients can connect en pickup their config from the OPSI-server.

The issue we have:
- clients have a 'requested action' set through 'opsi config editor'
- a 'MAC-address-file' was created in /tftpboot/linux/pxelinux.cfg/ for that client
- client PXE-boots, connects the OPSI-server but it's doesn't pickup the 'MAC-address-file

In /tftpboot/linux/pxelinux.cfg I noticed that the MAC-address-file is owned by root.root, which is probably the problem. If I chown the file to opsiconfd.pcpatch the client receives it's MAC-address-file and the requested-action is executed.

Is the owner of the file owned by root.root by design or did I miss a configuration step?

Thanks in advance for your help.

Regards, Eric
Benutzeravatar
n.wenselowski
Ex-uib-Team
Beiträge: 3194
Registriert: 04 Apr 2013, 12:15

Re: PXE + 'MAC-address-file' owned by root.root

Beitrag von n.wenselowski »

Hello Eric,

permissions root:root must not necessarily be a problem - this works fine in our local environment.

What tftpd do you use?
Does /var/log/syslog show any signs of problems with tftp?


With kind regards

Niko

Code: Alles auswählen

import OPSI
EricT
Beiträge: 20
Registriert: 18 Nov 2011, 12:49

Re: PXE + 'MAC-address-file' owned by root.root

Beitrag von EricT »

Hi Niko,

thanks for your reply.

Unfortunately nothing is logged to /var/log/syslog, but I'm now starting to doubt myself anyway.

The second time I set a 'requested action' for a netboot product for this client (with 'opsi config editor'), it successfully picks up the MAC-address-file and starts the requested action.

I've removed the client from the opsi server, removed all log-files of this client, added the client again and, when PXe-booting, it picks up the MAC-adress-file the first time it connects the server..

Apparently (and really annoying) the problem solved itself somehow. I'm going to try to reproduce the issue.

Thanks again.

Regards, Eric
Antworten