@pdit I am farily sure this is not an issue with your FOG server but more a network card/driver issue on that E73!!! Don’t think building a new FOG server will help at all.

Try other Linux Live systems to see if they have the same issue or not.

@pdit said in dhcp issue:

anything to do with Ethernet port name ? in centos 7 port is named as eno1 and that is what FOG picked up.

Nope! Some Linux systems use the “old” style ethX while others use names like enoX or even enp0sX. But it’s just the naming and does not have anything to do with carrier/link status.

@george1421 said in The future of partclone and therefore FOG as it is:

If the two formats are not compatible we might have to supply both version in FOS and then have a key file, db flag, or something to denote the version of partclone being used.

More or less exactly along the line of what I have been thinking about this. But I don’t actually like the idea. It’ll cause us all so much trouble I fear.

@Rebelman I still can’t replicate this issue unless I enable the hidden menu. Please check in the database to make sure the web UI is not playing tricks on us.

shell> mysql -u root -p
Enter password:
...
mysql> use fog;
...
mysql> SELECT * FROM globalSettings WHERE globalSettings.settingKey LIKE '%HID%';
...
mysql> quit

Please take a picture of the output and post here.

@TaTa Can you please post more information on the “Advanced menu issue” you see with current dev-branch. I’d like to fix this before we push out the next release.

@kafluke Good news, I figured out what is causing this. Will fix as soon as I can. Definitely before the next release is coming out (soon).

@george1421 Thanks heaps for testing. I think you are on the right track and doing a great job!

Just a few comments: sure 0.2.89 patch wouldn’t work anymore, good to know that we need dpkg and therefore epel to build on CentOS (might need to address this in build.sh - @Quazz yours is working on RHEL without epel?), BR2_LARGEFILE was removed long time ago (we should have fixed that in Config.in as well), yes build.sh kind of merges the files into the buildroot source before compiling.

Well a follow up on this shows that while the partitoins are on the disk, they are not in any usable state. I can’t even mount the partitions.

That sounds horrible!

@pdit said in dhcp issue:

My fog server is running on centos 7 in minimal installation. can this cause the issue i am having?

Definitely not! FOG server system is not causing this I am fairly sure!

@probbier Please run ls -al /var/www/ ; ls -al /var/www/html/ ; ls -al /var/www/fog/ ; ls -al /var/www/html/fog/ and post the full output here!

@mwolfe60 Thanks for the log. Unfortunately there is only one loop of the replicator in the log and therefore we don’t really see what it’s doing further on. Need more of the log!

What I see in the log so far is that only one single file is not matching (file size different) and it tries to re-transfer that. My guess is that this will take a fair amount of time to transfer as it is roughly 45 GB in size. What speed is the link between your two nodes??

As well, can you post the contents of /opt/fog/log/fogreplicator.Automation_TB_CF54.transfer.Greenville.log or send me a link again?

@Rebelman Taking a look at the code I can confirm that this part of the menu is related to the “hide menu” setting. Though I am still not sure if we see a bug here or if there is something going wrong only in your particular situation (maybe update problem, but really shouldn’t be).

Did you enable the hidden menu intentionally? Is is enabled at all when you look at the settings in the web UI?

@Rebelman See if the option for hidden menu is checked for example.

I need to take a look at the code later on to hopefully get an idea where this might be coming from. Will do that on the way home soon.

@pdit Linux usually names the first (Ethernet) network interface eth0. As we see when doing a debugging session the interface comes up later on and it just seems to take hell of a lot of time. I have no idea why. Suppose this is some kind of driver issue with this particular model.

Can you do me a favor? We should see the same effect when you boot any kind of Live Linux system. Download and boot Ubuntu Live DVD for example and see if it can bring up the network in the first 120 seconds of booting.

You can find some information on the boot process here: https://wiki.fogproject.org/wiki/index.php?title=Booting_into_FOG_and_Capturing_your_first_Image#PXE_booting

@pdit Well if you connected those directly, then I would assume both don’t have a link.

In the old days there were cross over cables for connecting PCs/server directly without switch. But that was 15 years ago. Do you see a link up LED on the server or desktop when both are connected to each other and switched on??

@nvdp2002 said in Downloading binaries needed..... Failed!:

ERROR 1396 (HY000) at line 1: Operation ALTER USER failed for ‘root’@‘127.0.0.1’

This might be ok on Ubuntu. I am not exactly sure at the moment. We try different mysql commands at that stage and one or the other might fail.

Please take a picture of the installer output you see on screen as well so we know exactly where it fails.

@mwolfe60 said:

are there any logs that I could provide that would help figure out what is going on here.

Yes, simply post the full fogreplication.log! If you fear to share this with the whole world you can upload to a private share and send me a link or password protect it and send me the PW. Whatever you like.

@Rebelman said in Fog Menu loop:

:menuAccess
login

Please take a look through the iPXE menu options in the web UI. Maybe there is something wrong there.

@Quazz said:

Seems like build errors complaining about legacy options, will see if I can fix that before I go home.

Are you surely using the new configs I pushed to the repo? 64 bit and 32 bit - those shouldn’t cause any legacy option issues.

But if they do, simply manually run:

cd fssource...
make ARCH... menuconfig

Go to the last menu item (legacy…) and deselect every option that might still be selected. Quit, save, make ARCH...

@george1421 said in Fog Menu loop:

http://x.x.x.x/fog/service/ipxe/boot.php&mac=00:00:00:00:00:00

There is a typo in the URL… & should be ? -> http://x.x.x.x/fog/service/ipxe/boot.php?mac=00:00:00:00:00:00

@Rebelman said:

I also just tested on an older machine that still uses Legacy and I have no problems imaging it. Problem is only happening on newer machines that have I have to use UEFI images.

Well that’s interesting. I need to think about this a bit more and look through the code. Not sure why this would make a difference at that stage yet.

@Rebelman said in Fog Menu loop:

Ubuntu 14.03.

Quite old. Hope you are aware if it went out of support just these days.

About the issue. Please open the following URL in your browser and post full output here: http://x.x.x.x/fog/service/ipxe/boot.php (put in the FOG xerver IP instead of x.x.x.x)