error creating epoll fd: Function not implemented

[ethan7888]

Hi,
Fog version: 1.5.5
OS: Ubuntu 18.04 lts server
3 hosts:
srv-fog (where fog server is installed)
srv-dhcp (dhcp server)
host-client (host that serves as an image deployment test)

When registering the host-client, I have the following message:

“populating / dev using udev: udevd [2447]: error creating epoll fd: Function not implemented”

on the management interface fog, I see that the file is bytes, would you have an idea?

Thank you in advance

[Sebastian Roth]

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

populating / dev using udev: udevd [2447]: error creating epoll fd: Function not implemented

This is an unrelated kernel message. You can simply ignore this. Or if you want to get rid of those you can manually load the latest kernels from our webserver (32 bit and 64 bit) as I finally got around to fix this warning two weeks ago.

on the management interface fog, I see that the file is bytes, would you have an idea?

I don’t get what you are saying here? Do you mean “0 bytes”? Please tell us if you see other messages on the screen after the “creating epoll fd: Function not implemented” when uploading an image from the client. There should be heaps more saying that it captures the partitions (as well screens with blue background). Do you see all that?

[ethan7888]

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

I don’t get what you are saying here? Do you mean “0 bytes”? Please tell us if you see other messages on the screen after the “creating epoll fd: Function not implemented” when uploading an image from the client. There should be heaps more saying that it captures the partitions (as well screens with blue background). Do you see all that?

Thanks for your feedback,

Sorry my english is very bad. What I wanted to say that actually when creating the image, the file is almost empty, much too light and especially too fast (it takes just two minutes to create the image for a partition of 10GB) when the finalization of the image so that it is functional. But I send you the rest of the information in screenshot as soon as possible

[Sebastian Roth]

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

it takes just two minutes to create the image for a partition of 10GB

FOG can do this, depending on the network speed (assuming Gigabit ethernet) and drives (assuming SSD) you have.

[ethan7888]

@Sebastian-Roth

Hi,

Hi,
Here screenshots that I could take during the creation of the image by clicking on the option: "quick registration and inventory"

[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??