1.4.1 Unable to register host (/bin/fog.man.reg)
-
There’s nothing you can do server side. We need to know what the nic is, if FOS is recognizing the nic (or failing to get an IP address), and/or if there’s actually a problem with the nic itself.
-
Fresh install of FOG 1.4.1 here. I am getting the same issue on multiple computers. I’m at a business so I have many types of computers to test with. I re-installed Ubuntu server 16.04,17.04, and FOG about 7 times so far because I thought it was something I was doing. I’m glad I saw this thread.
This issue is happening on each computer that I’ve tested and I cannot get around it.
-
@ddeatrich Can you show a picture of the message? I tested 1.4.1 registering and had no issues on myside.
-
@Tom-Elliott It is literally the same exact picture that User zclift15 submitted earlier. Everything is the exact same other than the IP addresses on there.
-
Please add:
isdebug=yesto FOG Configuration Page->FOG Settings->General Settings->FOG_KERNEL_ARGSLoad into registration please. (this will make the system drop into a terminal so we can debug more).
-
@Tom-Elliott Done. Debug mode set on kernel and ran quick registration on host computer. What would you like me to do?
-
@ddeatrich What’s output of:
ifconfig -a -
@Tom-Elliott http://i.imgur.com/BM6qDjx.jpg
Sorry for imgur. It kept giving me errors when I tried to upload the image.
-
So, for the IP Address, from there can you
ping <ipoffogserver>? -
@Tom-Elliott Yup. The server replies just fine. No issues
-
@ddeatrich Anything in your fog server’s Apache error log?
-
@Tom-Elliott Other than Apache shutting down and starting on restarts…
Edit… screenshoting. There may be a few things in here.
-
@ddeatrich Can you copy paste the text? It will be alot easier to read as your screenshot seems to be cutting off some of the text itself.
-
@ddeatrich Hint: Please use putty to connect to the FOG server using ssh. With putty you can copy and paste better than snapping screen images of logs and such.
With Putty just click and drag across the text like you can do in a windows console then you can paste it in.
-
@george1421 Yup, I know. Thanks though! I’m on the phone at work at the same time doing this. I’ll be able to copy and paste shortly.
-
@ddeatrich The php fatal error in your snap would be interesting to see the full error message. That may give the devs a clue to at lest what point it failing.
I just upgraded my dev server from 1.4.0 to 1.4.1 and created a new vm client to test registration and it worked as it should. But that is not a like for like test. If you installed 1.4.1 fresh. I’ll start building a new install of FOG on Cento 7 to see if its a fresh install thing or something else.
-
@Tom-Elliott
I’m following along here and so far had the same results. here is my error log[Thu Jun 01 12:37:11.809778 2017] [core:notice] [pid 11683] AH00094: Command line: '/usr/sbin/apache2' [Thu Jun 01 12:40:24.316027 2017] [mpm_prefork:notice] [pid 11683] AH00169: caught SIGTERM, shutting down [Thu Jun 01 12:42:42.516669 2017] [mpm_prefork:notice] [pid 26837] AH00163: Apache/2.4.10 (Debian) OpenSSL/1.0.1t configured -- resuming normal operations [Thu Jun 01 12:42:42.516750 2017] [core:notice] [pid 26837] AH00094: Command line: '/usr/sbin/apache2' [Thu Jun 01 14:06:45.487089 2017] [:error] [pid 32023] [client 131.128.53.29:54302] PHP Warning: ftp_rename(): Rename failed. in /var/www/html/fog/lib/fog/fogftp.class.php on line 769, referer: http://131.128.53.30/fog/management/index.php?node=about&sub=kernel&file=aHR0cHM6Ly9mb2dwcm9qZWN0Lm9yZy9rZXJuZWxzL0tlcm5lbC5Ub21FbGxpb3R0LjQuMTEuMC42NA==&arch=64 [Thu Jun 01 14:07:18.547598 2017] [mpm_prefork:notice] [pid 26837] AH00169: caught SIGTERM, shutting down [Thu Jun 01 14:07:46.810476 2017] [mpm_prefork:notice] [pid 621] AH00163: Apache/2.4.10 (Debian) OpenSSL/1.0.1t configured -- resuming normal operations [Thu Jun 01 14:07:46.815765 2017] [core:notice] [pid 621] AH00094: Command line: '/usr/sbin/apache2' [Fri Jun 02 00:28:09.222838 2017] [:error] [pid 24581] [client 139.162.78.135:43948] script '/var/www/html/echo.php' not found or unable to stat [Fri Jun 02 09:18:18.591258 2017] [:error] [pid 21306] [client 131.128.53.29:56037] PHP Warning: ftp_mkdir(): Create directory operation failed. in /var/www/html/fog/lib/fog/fogftp.class.php on line 492, referer: http://131.128.53.30/fog/management/index.php?node=about&sub=kernel&file=aHR0cHM6Ly9mb2dwcm9qZWN0Lm9yZy9rZXJuZWxzL0tlcm5lbC5Ub21FbGxpb3R0LjQuMTAuMTAuMzI=&arch=32``` -
@zclift15 That’s not the same error log as your picture. I see the php warnings about ftp (that is something else that needs to be addressed). What the devs will be interested in is the
PHP Fatal errorat 11:46 it may be nothing but it also could be something. Fatal generally means something bad.
-
@george1421
ddeatrich was the one who posted that -
@zclift15 said in 1.4.1 Unable to register host (/bin/fog.man.reg):
PHP Warning: ftp_rename(): Rename failed.
As for this one. Where we typically see this error is if someone mucks about with the FOG service account. This is a linux account called
fog. The installer manages this user account and password. The linux userfog(not the same as the web gui admin called fog) is used by FOG to move files around on the FOG server after image capture. The linux account password needs to match the password defined in the gui configuration for the storage node. If these are out of sync you will get the ftp errors like in your log.
