error creating epoll fd: Function not implemented

[george1421]

@ethan7888 What is the target computer you are trying to pxe boot?

You can ignore the error about /etc/target. That is only a warning message an it has been removed in the next release of FOG.

I believe you can ignore the Spectre V2 error message. That should not be an issue here. Updating the firmware on the target computer should address that issue. But it’s probably safe to ignore.

The telling error message is actually at the very top. The fog.postinit no such file or directory, that kind of makes me think you don’t have a complete FOG installation or something happened to the /images directory post FOG install. What is the output of the following command? find /images fog.postinit Does it locate the file? If not lets see the output of ls -la /images These commands are executed on the FOG server’s linux console.

[ethan7888]

@george1421

What is the target computer you are trying to pxe boot? >> Sorry, I did not quite understand the question? I’m trying to create an image of a client ubuntu virtual machine via pxe

For both orders, here are the attachments

Best regards

[Sebastian Roth]

@ethan7888 Some of the messages you can ignore as George said. About the fog.postinit, please try this command: find /images -name "fog.*" and post a picture of the output here.

As well I am wondering what you see on screen after the “Attempting to register host …” message? Does it say “Done” or does it fail?

[george1421]

@ethan7888 In your screen shot reply to Sebastian, the one with the errors, what computer (manufacturer and model) was those errors created on? I understand from your response that was a virtual machine? If so what hypervisor?

For the screen shots I asked about, I’m getting the idea that your fog install (/images directory) is not complete. Because in /images there should be a postinstall script directory, but you do have the .mntcheck file. This is a not normal condition.

The fog.postinstall script wasn’t found (which should be in a directory under /images/dev) this is because I forgot the -name switch in the command I gave you (sorry).

The command that Sebastian asked you to run will give us a better idea how your /images directory is configured. But I have to ask you did you/have you changed the directory path where the images are stored in your FOG server (there are reasons to do this, I just want to make sure you haven’t done this intentionally)?

[ethan7888]

@george1421

Hi,

What is your screen shot? Reply to Sebastian, the one with the errors, what computer? I understand from your response that was a virtual machine? If so what hypervisor? >> Excuse me for the lack of clarity. Indeed, it is a virtual machine that I created with virtualbox

For the screen shots I asked about, I’m getting the idea that your fog install (/ images directory) is not complete. Because in / images there should be a postinstall script directory, but you do have the .mntcheck file. This is a normal condition.

The fog.postinstall script was not found (which should be in a directory under / images / dev) This is because I forgot the -name switch in the command I gave you (sorry). >> So I type the following command: “find -name /images/fog.postinit”? I’m going in / images / and there is no file “fog.postinit” ^^

The command that gives you a better idea. But I have to ask you if you have changed the directory path where the images are stored in your FOG server (there are reasons to do this, I just want to make sure you intentionally)? >> I did it once to test, but I put it back in / images /

[george1421]

@ethan7888 I think the picture is a bit clearer now.

Please rerun the FOG installer to rebuild the /images directory. You have missing files. If you installed fog using the git method change into the bin directory in the cloned git repo and run ./installfog.sh to run the script. It will use the parameters you used last time you installed fog.

If you use the tar method change to the bin directory in the directory path where you extracted the tar file and run the installfog.sh script.

When the installer is finished you should have a directory /images/postinstallscript and /images/dev/postinitscripts (the scripts part may not be on the directory name, I can’t remember for sure). If those are in place, then rerun the capture of your reference image.

[ethan7888]

@george1421 Hi,

If you use the tar method change to the bin directory where you extracted the tar file and run the installfog.sh script. >> I chose this method there. So if I understand correctly, I download the .tar package. Then I extracted. I go to / bin and execute “./installfog.sh”, is that it?

Thanks you very much !

[george1421]

@ethan7888 Yes, just rerun the installer it will rebuild your /images directory. I hope that addresses your issues. If not then we take the next error until your problem is resolved. Understand that the bin directory is inside the expanded tar file path not /bin.

[ethan7888]

@george1421

Hi,

Thanks, I try to do your procedure quickly. I’ll come back to you as soon as possible

[ethan7888]

@george1421

Hi,

I restart the script (see screenshot) but I still do not have the file fog.postinit?

Also when I restart my management console, I still have the existing configuration "with my reference image) as if nothing had been reset? Would I still miss something after you?

[Sebastian Roth]

@ethan7888 The /images directory looks a bit better now. The file we were talking about is in one of the sub-directories. So please run find /images -name "fog.*" command again to see if it’s there. Please use the command exactly as suggested here.

[ethan7888]

@Sebastian-Roth

Hi,

Here is the result of the command line

Best regards

[Sebastian Roth]

@ethan7888 There you go. The installer created those and your images directory looks fine now. Now when you register a client (PXE boot and select register from the menu) what happens?

[ethan7888]

@Sebastian-Roth

Hi,

When I boot in pxe from the client host, I check: “quick registration and inventory”

I have the messages as before (see screenshot):

Then another screenshot via the web console management,

or I see written “no data” after the quick resgistration and inventory “.It normally I have to see one or more files corresponding to my image of my client host, in the directory” / images "?

[Sebastian Roth]

@ethan7888 Please take a new picture of what you see on screen. I highly doubt that you still get the “line 22: fog.postinit: No such file or directory” message.

So when you say it’s the same, do you mean it just hangs at “Attempting to register host…” ??? Never gets past that saying “Done”?

About your other question. The “No Data” means FOG never deployed an image to that client. But then I am wondering why you want to do registration if the client seems to be registered in the host list already?!?! This doesn’t make sense.

When you PXE boot that client, do you get the FOG PXE menu? Does it say “Host is NOT registered” or “Host is registered as …” in the headline of the menu??

[ethan7888]

@Sebastian-Roth said in error creating epoll fd: Function not implemented:

About your other question. The “No Data” means FOG never deployed an image to that client. But then I am wondering why you want to do registration if the client seems to be registered in the host list already?!?! This doesn’t make sense.
When you PXE boot that client, do you get the FOG PXE menu? Does it say “Host is NOT registered” or “Host is registered as …” in the headline of the menu??

Ok, it’s quite possible that I did not understand at all how fog server worked

When I boot in pxe, here is the list of choices in screenshot:

---

I thought it was then necessary to create the image of the client host by clicking on “quick registration and inventory”. After that I went to my web management console and I saw my registered host.

[george1421]

@Sebastian-Roth If we ignore the spectre and other kernel warning, it looks like the last thing FOS tried to do is register with the FOG server. If we also consider that it still can’t find the fog postinit stuff. Wouldn’t this kind of be the same condition if the FOG server changed IP addresses after FOG was installed? Typically the FOG server would have a static IP address, but if that was missed…

I would expect it to fail sooner with the default.ipxe file pointing in the wrong location. But if in the fog configuration settings the IP address there did not match the FOG server’s IP address FOS may be trying to reach out to a host no longer at its location.

When FOG typically errors out it will display the kernel parameters but it doesn’t appear to be doing it here. I wonder if the OP didn’t wait long enough for the attempting to register host… to timeout before snapping the picture.???

[george1421]

@ethan7888 When you setup your fog server. For the linux OS did you define a static IP address for your server or are you using dhcp to assign the IP address for your FOG server?

Is to also safe to assume that you are running your fog server as a VM under virtual box too?

[ethan7888]

@george1421 said in error creating epoll fd: Function not implemented:

When you setup your fog server. For the linux OS did you define a static IP address for your server or are you using dhcp to assign the IP address for your FOG server?
Is to also safe to assume that you are running your fog server as a VM under virtual box too?

Hi,

Yes, my test environment is fully realized under virtual machines via virtualbox (fog-rsv, host client, srv-dchp: three virtualbox machines)

I am using a DHCP server that provides my client host and fog server
But I fixed the IP on my fog server and the client host

[george1421]

@ethan7888 So did you fix the IP address on your FOG server before or after you installed FOG for the first time?

If you go into FOG Configuration -> FOG settings and then expand all. Confirm the IP address listed like under tftp server and one other match the current IP address of your FOG server. Also in the Storage Configuration for the default storage node, make sure the IP address listed there is correct too.