1.4.1 Unable to register host (/bin/fog.man.reg)
-
Are you sure it’s not “Unable to register host (/bin/fog
.
man.reg)”?Notice the (/) is missing. Any thing in apache error logs on the fog server?
-
Sorry, yes it is (/bin/fog.man.reg). And where would I find those logs? I saw people with a similar problem posted that but I tried looking for them but wasn’t sure where they were.
-
@zclift15 You can get them from multiple places.
Easiest:
FOG Configuration Page->Log Viewer->Apache Error Log./var/log/apache2/error.log
<—For Debian based OS’s
/var/log/httpd/error_log
<—For Redhat based OS’s -
[Thu Jun 01 14:07:46.815765 2017] [core:notice] [pid 621] AH00094: Command line: '/usr/sbin/apache2' [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:18.547598 2017] [mpm_prefork:notice] [pid 26837] AH00169: caught SIGTERM, shutting down [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 12:42:42.516750 2017] [core:notice] [pid 26837] AH00094: Command line: '/usr/sbin/apache2' [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:40:24.316027 2017] [mpm_prefork:notice] [pid 11683] AH00169: caught SIGTERM, shutting down [Thu Jun 01 12:37:11.809778 2017] [core:notice] [pid 11683] AH00094: Command line: '/usr/sbin/apache2' [Thu Jun 01 12:37:11.809697 2017] [mpm_prefork:notice] [pid 11683] AH00163: Apache/2.4.10 (Debian) configured -- resuming normal operations [Thu Jun 01 12:37:10.663707 2017] [mpm_prefork:notice] [pid 11583] AH00169: caught SIGTERM, shutting down [Thu Jun 01 12:37:09.261303 2017] [core:notice] [pid 11583] AH00094: Command line: '/usr/sbin/apache2' [Thu Jun 01 12:37:09.261173 2017] [mpm_prefork:notice] [pid 11583] AH00163: Apache/2.4.10 (Debian) configured -- resuming normal operations [Thu Jun 01 12:37:08.181637 2017] [mpm_event:notice] [pid 804:tid 140642725861248] AH00491: caught SIGTERM, shutting down [Thu Jun 01 12:17:12.261490 2017] [core:notice] [pid 804:tid 140642725861248] AH00094: Command line: '/usr/sbin/apache2' [Thu Jun 01 12:17:12.261359 2017] [mpm_event:notice] [pid 804:tid 140642725861248] AH00489: Apache/2.4.10 (Debian) configured -- resuming normal operations```
-
@Tom-Elliott
Thats it there, I don’t really know what I’m looking at. I wasn’t around when the original server was built so I’m sort of learning as I go here. -
@zclift15 Is the message something like:
'Unable to register host: Already registered as…?
Can you provide a screen shot of the error?
-
-
Just wanted to say that I’m experiencing the same error with 1.4.1. I recently set up a physical Ubuntu box with FOG 1.4.1 to do some testing and haven’t been able to register any hosts with it. Previously had version 1.3.5 on a virtual Ubuntu machine which was having no issues. I’m getting the same screen as the picture zclift15 posted.
-
@zclift15 It appears to me FOG is not recognizing your network adapter.
See where it says "Version: "? That should show “Version: 1.4.1” (Or whatever version you’re running.)
-
@Tom-Elliott
Do mean to say the network adapter on the computer or on the server? The server is a virtual box that is on bridged adapter eth4. -
@zclift15 The computer, not the server.
-
I’m getting the same error. I rebooted mine to get that error cleared. This is on ubuntu 17.04.
I’m also getting nfs failed, and unable to check in. Trying to send a image to the server. -
The same thing happens to me when I try send an image after manually registering the host
-
@Tom-Elliott
Would you have any suggestions on a fix on the server side? Because I have over 100 computers (not all the same model) and it doesn’t seem to work on any of them . -
I am having the same issues with Fog 1.4.1 on Ubuntu 16.04 LTS installed on a physical machine with an Intel NIC. Any suggestions?
-
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=yes
to 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).