/var/log/php-fpm/error.log
[10-Apr-2018 11:43:21] NOTICE: Terminating ...
[10-Apr-2018 11:43:21] NOTICE: exiting, bye-bye!
[10-Apr-2018 11:43:50] NOTICE: fpm is running, pid 20233
[10-Apr-2018 11:43:50] NOTICE: ready to handle connections
[10-Apr-2018 11:43:50] NOTICE: systemd monitor interval set to 10000ms
@sebastian-roth Indeed this is from installer error log file
Apr 10 11:25:31 fog-server systemd[1]: Starting The PHP FastCGI Process Manager$
Apr 10 11:25:31 fog-server systemd[1]: Started The PHP FastCGI Process Manager.
--2018-04-10 11:25:33-- http://x.x.x.x//fog//maintenance/backup_db.php
Connecting to x.x.x.x:80... connected.
HTTP request sent, awaiting response... 503 Service Unavailable
2018-04-10 11:25:33 ERROR 503: Service Unavailable.
php-fpm/error.log
[10-Apr-2018 11:43:21] NOTICE: Terminating ...
[10-Apr-2018 11:43:21] NOTICE: exiting, bye-bye!
[10-Apr-2018 11:43:50] NOTICE: fpm is running, pid 20233
[10-Apr-2018 11:43:50] NOTICE: ready to handle connections
[10-Apr-2018 11:43:50] NOTICE: systemd monitor interval set to 10000ms
none other than my 3000 hosts complaining about not being able to connect to backend at 127.0.0.1
PHP 7.1.16 (cli) (built: Mar 28 2018 07:11:55) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.1.0, Copyright (c) 1998-2018 Zend Technologies
with Zend OPcache v7.1.16, Copyright (c) 1999-2018, by Zend Technologies
@wayne-workman Both are working from server with additional -u root -p options (since I have password)
@tom-elliott Using Fedora 26 still failing with working branch and master…was working with 1.5.0 though. I’ll also add that I can create a backup via GUI just fine and this only occurs during installation.
**Extra information. I tried running the installer with the -X option to continue on fail. After finishing with backup db…failed being the only error, I try going to GUI and get
Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Error differs slightly
* Setting up Apache virtual host (no SSL).....................OK
* Starting and checking status of web services................OK
* Changing permissions on apache log files....................OK
* Backing up database.........................................Failed!
[root@fog-server bin]#
Running MariaDB 10.1.32
@joe-schmitt you can close this sorry to waste your time…it is working correctly.
Running 1.5 RC-10 on Fedora 26 7 nodes and one main server. Currently the clients are showing the sleep times correctly ;however they are not corresponding in actual sleep times.
-----------------------------------------------------------------------------
----------------------------------UserTracker---------------------------------
------------------------------------------------------------------------------
11/21/2017 4:16 PM Client-Info Client Version: 0.11.12
11/21/2017 4:16 PM Client-Info Client OS: Windows
11/21/2017 4:16 PM Client-Info Server Version: 1.5.0-RC-10
11/21/2017 4:16 PM Middleware::Response Success
------------------------------------------------------------------------------
11/21/2017 4:16 PM Service Sleeping for 4823 seconds
11/21/2017 5:11 PM Main Overriding exception handling
11/21/2017 5:11 PM Main Bootstrapping Zazzles
11/21/2017 5:11 PM Controller Initialize
11/21/2017 5:11 PM Controller Start
11/21/2017 5:11 PM Service Starting service
11/21/2017 5:12 PM Bus Became bus server
11/21/2017 5:12 PM Bus Emmiting message on channel: Status
11/21/2017 5:12 PM Service Invoking early JIT compilation on needed binaries
------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Power\
Value
HiberbootEnabled
REG_DWORD set to 0 hex
@hanz WOL verified with wireshark being sent and found the culprit to be fastboot with Windows 10.
Registry gpo and viola ! Thanks fellas for ruling some things out.
@wayne-workman I’m actually curious how I could verify that the nodes are sending the packets on command ? I have 7 nodes in different subnets, and not 100% certain this was working on this version (although I’ve not seen any issues posted). I can verify at the beginning of summer it was working, but not sure what version and when beyond that scope.
Can you verify that power management and Wake via Basic Tasks–> Advanced --> Wake-Up are the exact same ?
@wayne-workman Manually this is the page it took me to.
#!ipxe
set fog-ip X.X.X.X
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
cpuid --ext 29 && set arch x86_64 || set arch i386
iseq ${platform} efi && set key 0x1b || set key 0x1b
iseq ${platform} efi && set keyName ESC || set keyName Escape
prompt --key ${key} --timeout 5000 Booting… (Press ${keyName} to access the menu) && goto menuAccess || chain -ar ${boot-url}/service/ipxe/grub.exe --config-file=“rootnoverify (hd0);chainloader +1”
:menuAccess
login
params
param mac0 ${net0/mac}
param arch ${arch}
param platform ${platform}
param username ${username}
param password ${password}
param menuaccess 1
param debug 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:bootme
chain -ar http://X.X.X.X/fog/service/ipxe/boot.php##params
I subbed the ips for X, and no wake, nor with WakeOnLan though so not sure…No change in network at all, but we are running SCCM current branch now, which was the only change now that I think about it.
::Update
WakeMeOnLan isn’t even working locally, although I was told otherwise earlier today. Might have some issues…I believe it was still 1.4.4 end of summer was still working. Upgraded OS to fedora 26 and moved server from physical to Hyper-V, but all other aspects working of course.
I have fedora 26 running FOG 1.4.4. Wol used to work fine from the nodes as they are all in there own subnets, and I have a node installed on that subnet. Recently it seems that WOL just stopped working and I’m not sure why. This is what I get from apache error log.
[Mon Oct 23 12:15:00.904516 2017] [http2:warn] [pid 30424] AH10034: The mpm module (prefork.c) is not supported by mod_http2. The mpm determines how things are processed in your server. HTTP/2 has more demands in this regard and the currently selected mpm will just not do. This is an advisory warning. Your server will continue to work, but the HTTP/2 protocol will be inactive.
is this error worth worrying about or are there any fixes. I’ve tried the manual wake up with the url to no avail either.
Please help.
@Tom-Elliott The client is what I suspect is different as I haven’t actually been pushing the client for the last 3 months as I was instructed to remove the client from all but a couple labs. So this is the first attempt for a couple months to have the clients pushed to computers before we image them in order to take full advantage of multicasting from the local nodes. Now it seems that the process used before isn’t working completely together. If I push a client to a computer, it registers with fog, and I see the machine, I suppose (as I haven’t tested) that the snapins and power management will work on these hosts just as they always have. The problem is when I pxe boot the laptops, they show as not registered.
Now I have been running this system here for a couple years since trunk became available so it’s possible I have junk clients registered already, but I didn’t see these machines as I deleted them after removing the clients (at least not in the gui). I can verify this issue does not arise on desktop machines. I just don’t understand why the client would think it wasn’t registered.
I have no idea how any macs could be shared, as we haven’t done anything to initiate that. All clients are currently running Windows 7 so the “randomizing” of any wireless nics isn’t the issue here, but rather in the manner the client registers the hosts.
Quickreg works flawlessly, but it uses different mechanisms to register the nics I’m assuming since it’s still in a pre-boot environment.
@Avaryan Apparently that used to be the case, but now if the client registers the laptop with the wrong primary device, it shows as unregistered when pxe booting…so if you were to deploy an image to said laptop, it would bypass the task altogether since it believes the host is not registered. That is a huge issue, at least in reference to imaging.
@Avaryan @Developers What is the process for the client to register the nics on the machines, and can it be made/forced to choose the onboard lan as the primary by default ( for laptops) ?
@Avaryan Thanks for that, I’ll look to see which one it is allocating as the primary…will post back soon. Quick reg seems to work fine, but I don’t know how the client actually chooses which nic should be primary (these are laptops) I’ll also double to check to see if they are the only ones affected.
Client has been installed both via gpo and manually on machines, but when booted to pxe the screen states that client is not registered. The machine shows in database and in every aspect via FOG GUI correctly, but pxe screen not so much making it impossible to have the machines task from pxe boot. Please help
Fog running on Fedora 25
Clients have Win 7 pro installed.
@austin_g IPXE.kpxe is needed now for VMs as this wasn’t always the case. I’ve found that recently i have run into this more frequently as of late. That (I can confirm) is the only change necessary for sure pxe boot with Virtualbox VM. Probably on Virtualbox’s end I’d imagine given the timing.