Unable to register host: Invalid MAC adddress (2) (/bin/fog/man.reg)
-
Server
- FOG Version: 1.3.2
- OS: centos 6.8
Client
- Service Version:
- OS:
Description
Hello
Finally I try to upgrade a 0.32 fog server to 1.3.2.
So, I made a P2V of my fog server, to test on a little part of machines and check the procedure.
On my new virtual server (P2V from my server on production) I 've just changed IP, hostname and installed 1.3.2 version of fog.
Trying to rester a machine I get this error " Unable to register host: Invalid MAC address (2) (/bin/fog/man.reg)"
With an other machine, registered on the web interface, I get a similar error when I try a capture.Arnaud
-
tryed with a fresh 1.3.3 install, I get the same error
-
Resolved,
I’ve forgotten to change web server address -
hey man
same error with me, I am running redhat 5.3 and fog 1.2, newly installed FOG.
I know there is no reason leaving with redhat 5.3, but company policy, I have no choice. how can I check if my server address is correct? -
more info about LAMP environment
PHP 5.6.29 (cli) (built: Dec 10 2016 13:02:08)
Copyright 1997-2016 The PHP Group
Zend Engine v2.6.0, Copyright 1998-2016 Zend Technologies
httpd-tools-2.2.31-
httpd-2.2.31-1.8
mysql-server-5.5-1.3confirmed PC hardware compatible with FOG, NIC and HD recogized, kernal updated to newest. only one NIC, no wifi or additional network card.
from web console, manually register successfully , can start upload/download tasks.
mysql server root password left blank.
-
@jeremy-kou You have the same exact error as the OP? Did you change your FOG server IP address from when it was first installed?
-
@jeremy-kou
fog configuration > fog settings > web server -
@george1421 hey george, exact the same error. I just change fog passwd by sudo passwd fog after installation , after then I update tftp and storage node password from web, except this no more customization.
-
@lebrun78 verified , server ip address is correct. quite confused why manually regeneration from web working. some logs maybe used to dig deeper?
-
@jeremy-kou This seems to indicate that it cannot find a mac address on the device, is FOS recognizing the nic?
-
@jeremy-kou
what gives
tail -f /var/log/fog/* during registering ? -
@jeremy-kou said in Unable to register host: Invalid MAC adddress (2) (/bin/fog/man.reg):
@george1421 hey george, exact the same error. I just change fog passwd by sudo passwd fog after installation , after then I update tftp and storage node password from web, except this no more customization.
Just for clarification, you have not changed the FOG IP address since fog has been installed AND fog IP is set static?
-
@Tom-Elliott yes, I think so .first FOG compiable chekcing passed, second the same computer can upload/download image without problem.
-
@lebrun78 good idea, only see foginstall.log under /var/log, no fog folder found. will try tail tomorrow back office.
-
@jeremy-kou Then this seems that you may have missed a spot for changing the IP address.
You changed FOG Configuration Page->FOG Settings->Web Server-FOG_WEB_HOST ?
-
@george1421 no, fog server used static ip address, after bring fog up, no change about network part.
-
confirmed, webhost settings correct. attached my exactly the same screenshot
-
This post is deleted! -
@jeremy-kou said in Unable to register host: Invalid MAC adddress (2) (/bin/fog/man.reg):
I am running redhat 5.3 and fog 1.2, newly installed FOG.
FOG 1.2 is limited in how new of a kernel you can use with it. This invalid MAC error may be related to the old kernel you have in use. With an OS as old as that and FOG 1.2.0 being what it is, you’re going to run into a wall eventually with newer hardware. You should convince your company to allow you to use CentOS 7, it’s free and built from RHEL 7 source. Staying on 5.3 has major security & support implications. I don’t know if Red Hat still supports 5.3 or not, but I’ve never even used it before so I won’t be much help to you.
Here’s an article to help migrate to a newer OS should you choose that route: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG
-
@Wayne-Workman thanks for your post, I know it’s worth less to dig deeper in an very old OS. today I just see a totally same error, I thought someone may have some idea, will share your talking with my team members.