I removed the folder and reran the installer and it still fails. It doesn’t create any files in /var/www/fog or /var/www/html/fog
How do I change the installer so that it doesn’t overwrite my myslqd init file?
I removed the folder and reran the installer and it still fails. It doesn’t create any files in /var/www/fog or /var/www/html/fog
How do I change the installer so that it doesn’t overwrite my myslqd init file?
I’m trying to update from RC2 to the latest (RC13 but this happend on RC11 as well).
The installation fails when trying to restart mysql. The error looks like this:
* Setting up and starting MySQL...............................Failed!
When I try to manually start mysql after that I get this:
/etc/init.d/mysqld: line 103: syntax error near unexpected token `fi'
/etc/init.d/mysqld: line 103: ` fi'
So I go into the mysqld init file and I see the following:
# If startsos
if [ "$1" = "sos" ] ; then
# MYOPTIONS="$MYOPTIONS --skip-grant-tables --skip-networking"
fi
When I remove the comment from the MYOPTIONS line, everything starts correctly, but fog is still on RC2.
Any thoughts?
@Tom-Elliott said in Fog Trunk Autologging Out Immediately:
I did not update the text because I think it’s simpler to enter values in the form of “720 minutes” vs having users run calculations on their own (no offense anybody).
That said, I was unaware the logout time was being done in seconds and not performing the calculation as it had under the legacy client. (Oversight I suppose, for that i’m sorry).
This has been patched and pushed though. Thanks for letting us know.
I agree wholeheartedly and I can confirm that this is now working as it should on the latest 1.3.0-RC2 version.
thanks!
Thanks for your reply. This is the log I was looking for. It appears that the machine is being set to logout after 720 SECONDS, not minutes as the GUI says. So is this a bug or is the GUI wrong?
------------------------------------------------------------------------------
----------------------------------AutoLogOut----------------------------------
------------------------------------------------------------------------------
7/15/2016 3:20 PM Client-Info Client Version: 0.11.3
7/15/2016 3:20 PM Client-Info Client OS: Windows
7/15/2016 3:20 PM Client-Info Server Version: 8595
7/15/2016 3:20 PM Middleware::Response Success
7/15/2016 3:20 PM AutoLogOut Time set to 720 seconds
7/15/2016 3:20 PM AutoLogOut Inactive for 1 seconds```
Hi Everybody,
Apologies if this has been answered but I have looked everywhere and cannot find where somebody has had this issue. I’m running the latest version of FOG Trunk and 11.3 of the client on my Windows machines. I have Auto Logout selected with a default setting of 720 minutes.
The issue I face is that the clients are logging out immediately upon going idle. The client log doesn’t show AutoLogout logs at all, so I’m having a difficult time trying to troubleshoot.
Any help would be greatly appreciated.
thanks
88
Nobody has ever seen this before?
To add to this, if I set a task, it doesn’t restart the computer.
The Fog Service is running but the client isn’t responding.
What’s going on here?
Hi Everybody,
The Fog Client is not logging my clients out. They are registered and they can be pinged when I List All Hosts in the Host Management page.
I have set AutoLogout to on and set it to 720 minutes but nothing is happening.
fog.log:
[CODE] 7/17/2014 9:46 AM FOG::HostnameChanger Sleeping for 1 minute.
7/17/2014 9:47 AM FOG Service Engine Version: 3
7/17/2014 9:47 AM Starting all sub processes
7/17/2014 9:48 AM 14 modules loaded
7/17/2014 9:48 AM * Starting FOG.AutoLogOut
7/17/2014 9:48 AM * Starting FOG.SnapinClient
7/17/2014 9:48 AM * Starting FOG.DirCleaner
7/17/2014 9:48 AM * Starting FOG.DisplayManager
7/17/2014 9:48 AM * Starting FOG.GreenFog
7/17/2014 9:48 AM * Starting FOG.GUIWatcher
7/17/2014 9:48 AM * Starting FOG.HostNameChanger
7/17/2014 9:48 AM FOG::GUIWatcher Starting GUI Watcher…
7/17/2014 9:48 AM * Starting FOG.HostRegister
7/17/2014 9:48 AM FOG::DisplayManager Starting display manager process…
7/17/2014 9:48 AM FOG::AutoLogOut Starting process…
7/17/2014 9:48 AM FOG::HostRegister Starting host registration process…
7/17/2014 9:48 AM FOG::DirCleaner Sleeping for 40 seconds.
7/17/2014 9:48 AM FOG::HostnameChanger Starting hostname change process…
7/17/2014 9:48 AM FOG::HostnameChanger Yielding to other subservices for 7 seconds.
7/17/2014 9:48 AM FOG::ClientUpdater Sleeping for 62 seconds.
7/17/2014 9:48 AM * Starting FOG.PrinterManager
7/17/2014 9:48 AM FOG::MODDebug Sleeping for 100 Seconds
7/17/2014 9:48 AM * Starting FOG.SnapinClient
7/17/2014 9:48 AM * Starting FOG.TaskReboot
7/17/2014 9:48 AM FOG::PrinterManager Starting interprocess communication process…
7/17/2014 9:48 AM * Starting FOG.UserCleanup
7/17/2014 9:48 AM FOG::PrinterManager interprocess comm startup: OK
7/17/2014 9:48 AM * Starting FOG.UserTracker
7/17/2014 9:48 AM FOG::TaskReboot Starting Task Reboot…
7/17/2014 9:48 AM FOG::UserCleanup Sleeping for 12 seconds.
7/17/2014 9:48 AM FOG::UserTracker Starting user tracking process…
7/17/2014 9:48 AM FOG::SnapinClient Starting snapin client process…
7/17/2014 9:48 AM FOG::UserCleanup Starting user cleanup process…
7/17/2014 9:48 AM FOG::DirCleaner Starting directory cleaning process…
7/17/2014 9:48 AM FOG::GreenFog Starting green fog…
7/17/2014 9:49 AM N/A Call was canceled by the message filter. (Exception from HRESULT: 0x80010002 (RPC_E_CALL_CANCELED))
7/17/2014 9:49 AM FOG::AutoLogOut Unable to continue, MAC is null!
7/17/2014 9:49 AM FOG::MODDebug Reading config settings…
7/17/2014 9:49 AM FOG::MODDebug Reading of config settings passed.
7/17/2014 9:49 AM FOG::MODDebug Starting Core processing…
7/17/2014 9:49 AM FOG::MODDebug Operating System ID: 6
7/17/2014 9:49 AM FOG::MODDebug Operating System Minor: 1
7/17/2014 9:52 AM FOG::UserTracker Unable to determine MAC address, exiting…
7/17/2014 9:52 AM FOG::TaskReboot Attempting to connect to fog server…
7/17/2014 9:52 AM FOG::MODDebug MAC ID 0 80:EE:73:3A:DB:FD
7/17/2014 9:52 AM FOG::MODDebug MAC POST String: 80:EE:73:3A:DB:FD
7/17/2014 9:52 AM FOG::MODDebug A user is currently logged in
7/17/2014 9:52 AM FOG::MODDebug Username: DOMAIN\user
7/17/2014 9:52 AM FOG::MODDebug Hostname: COMPUTER
7/17/2014 9:52 AM FOG::MODDebug Attempting to open connect to: http://192.168.1.184/fog/service/debug.php
7/17/2014 9:52 AM FOG::UserCleanup Module is disabled globally on the FOG Server, exiting.
7/17/2014 9:52 AM FOG::ClientUpdater Module is active…
7/17/2014 9:52 AM FOG::DirCleaner Module is active…
7/17/2014 9:52 AM FOG::DirCleaner Determining which directories should be cleaned…
7/17/2014 9:52 AM FOG::DirCleaner No directories are configured to be cleaned.
7/17/2014 9:52 AM FOG::DirCleaner Starting directory cleaning loop…
7/17/2014 9:52 AM FOG::DirCleaner Module has finished work and will now exit.
7/17/2014 9:52 AM FOG::ClientUpdater Checking Status : AutoLogOut.dll
7/17/2014 9:52 AM FOG::ClientUpdater Zero byte response returned
7/17/2014 9:52 AM FOG::ClientUpdater Checking Status : ClientUpdater.dll
7/17/2014 9:52 AM FOG::ClientUpdater Zero byte response returned
7/17/2014 9:52 AM FOG::ClientUpdater Checking Status : DirCleaner.dll
7/17/2014 9:52 AM FOG::ClientUpdater Zero byte response returned
7/17/2014 9:52 AM FOG::ClientUpdater Checking Status : DisplayManager.dll
7/17/2014 9:52 AM FOG::ClientUpdater Zero byte response returned
7/17/2014 9:52 AM FOG::ClientUpdater Checking Status : GreenFog.dll
7/17/2014 9:52 AM FOG::ClientUpdater Zero byte response returned
7/17/2014 9:52 AM FOG::ClientUpdater Checking Status : GUIWatcher.dll
7/17/2014 9:52 AM FOG::ClientUpdater Zero byte response returned
7/17/2014 9:52 AM FOG::ClientUpdater Checking Status : HostRegister.dll
7/17/2014 9:52 AM FOG::ClientUpdater Zero byte response returned
7/17/2014 9:52 AM FOG::ClientUpdater Checking Status : MODDebug.dll
7/17/2014 9:52 AM FOG::ClientUpdater Zero byte response returned
7/17/2014 9:52 AM FOG::ClientUpdater Checking Status : PrinterManager.dll
7/17/2014 9:52 AM FOG::ClientUpdater Zero byte response returned
7/17/2014 9:52 AM FOG::GreenFog Module is active…
7/17/2014 9:52 AM FOG::GreenFog No actions were found.
7/17/2014 9:52 AM FOG::GreenFog No tasks found after validation!
7/17/2014 9:52 AM FOG::TaskReboot Module is active…
7/17/2014 9:52 AM FOG::TaskReboot Attempting to connect to fog server…
7/17/2014 9:52 AM FOG::HostnameChanger Module is active…
7/17/2014 9:52 AM FOG::MODDebug Server responded with: Hello FOG Client
7/17/2014 9:52 AM FOG::MODDebug Module has finished work and will now exit.
7/17/2014 9:52 AM FOG::TaskReboot No task found for client.
7/17/2014 9:52 AM FOG::HostnameChanger Hostname is up to date
7/17/2014 9:52 AM FOG::ClientUpdater Checking Status : SnapinClient.dll
7/17/2014 9:52 AM FOG::ClientUpdater Zero byte response returned
7/17/2014 9:52 AM FOG::ClientUpdater Checking Status : TaskReboot.dll
7/17/2014 9:52 AM FOG::ClientUpdater Zero byte response returned
7/17/2014 9:52 AM FOG::ClientUpdater Checking Status : UserCleanup.dll
7/17/2014 9:52 AM FOG::ClientUpdater Zero byte response returned
7/17/2014 9:52 AM FOG::ClientUpdater Checking Status : UserTracker.dll
7/17/2014 9:52 AM FOG::ClientUpdater Zero byte response returned
7/17/2014 9:52 AM FOG::ClientUpdater Checking Status : config.ini
7/17/2014 9:52 AM FOG::ClientUpdater Zero byte response returned
7/17/2014 9:52 AM FOG::ClientUpdater Zero byte response returned
7/17/2014 9:52 AM FOG::ClientUpdater 0 new modules found!
7/17/2014 9:52 AM FOG::ClientUpdater Client update will be applied during next service startup.
7/17/2014 9:52 AM FOG::ClientUpdater Client update process complete, exiting…
[/CODE]
What am I doing wrong?
I’ve solved this. I hadn’t configured dhcpd.conf correctly in my pfSense router.
Apparently, [CODE]option tftp-server-name “ipaddressofserver”;[/CODE] doesn’t do anything, which I find weird. Only the [CODE]next-server[/CODE] seems to work.
Thanks for your help everybody.
option 67 was set to undionly.kpxe.
[CODE] tftp x.x.x.x get undionly.kpxe[/CODE]
gives me a server error:
tftpd: read(ack): Connection refused
selinux is set to permissive and iptables is off. Permissions on /tftpboot are 777.
Forgive me if this has been answered before but I couldn’t find the solution. I used to have v.32 working just fine.
I keep getting a TFTP Open Timeout error when a client tries to boot. I can’t get this thing to boot from the server.
CentOS 6 Server running FOG 1.1.1 (TFTP without DHCP)
PFsense router with DHCP correctly configured. The clients are given DHCP addresses properly.
firewall is disabled
Option 67 is set as /undionly.kpxe.
Am I doing this right? I can’t tell if TFTP is running because it’s under xinet. That part is new to me.
Okay, so I read more and figured out that sysprep does what I need it to do. Questions though:
1.) What is sysprep actually doing?
2.) Can I only use it a max of 3 times?
Hi everybody,
so far I think FOG is amazing, but I’m having a bit of trouble deploying an image.
I’m using FOG to bare-metal backup all of our workstations. They are mostly different hardware so I’m looking for a way to deploy the backed-up image to a new machine if needed (eg. the old hardware dies and cannot be replaced). The problem I’m having is that the image will deploy fine, but the system reboots at the Windows 7 startup screen and I cannot get it to boot.
Now, I’ve seen this before and I’ve never had a way to get around it. If the drivers configured in the original image don’t jive with the new hardware, I can’t get the system to boot.
Is there any way of imaging the workstations such that their images can be deployed to any type of hardware? Or am I looking for something that’s impossible?
thanks for any help.
Thanks for the info. That’s useful.
Hi Everybody,
I’m posting this as a problem and a solution. I hope it helps somebody:
I now have FOG working really well with most of my clients; however, I have one client that simply refuses to get an IP address from the DHCP server. It exits out with a PXE-E51 “No DHCP or DHCP Proxy Offers received” error.
I found this weird because the rest of the clients get an IP from the DHCP server no problem. The solution I found was something I knew nothing about before I researched it.
[URL=‘http://h30499.www3.hp.com/t5/ITRC-ProLiant-Deployment/PXE-E51-quot-No-DHCP-or-DHCP-Proxy-Offers-received-quot-error/td-p/3057862#.UgKOmqLktz8’]The answer was HERE[/URL]
If you have manageable switch and you have Spanning-Tree enabled on it. You’ll need to enable Port-Fast (Cisco lingo) or Fast-Link (Netgear lingo) on each port that’s giving you trouble. It may be called something else on your switch, so it’s worth looking at your manual.
YMMV with this. I have no idea if it breaks anything else in the network but I haven’t noticed anything yet.
okay, I solved this.
The issue was in my apache settings. This server was being used to serve other webpages using VirtualHost containers. I had “deny from all” set on my VirtualHost and that was causing some issues. I also had a permanent https redirect that might have been causing issues too.
Once I fixed that I got the hosts to register and now I can image them.
I hope this helps somebody.
Okay, so I can boot to the debug mode command line just fine. I get an IP address and everything, so the NIC is working with the latest kernel but I simply cannot register the host.
When I type in the “fog” command I get:
[QUOTE]Error detected.
Cannot determine Operating System type[/QUOTE]
The fog.man.reg command gives the same ioctl error as above.
PLEASE somebody help me debug this.
I’ve tried this with three other computers: A Dell Dimension C521 circa 2004, a Shuttle XH61V which is fairly new and an ANCIENT HP Pavilion a1106n.
They all give the same errors. I have a hard time believing that not one of these computers is compatible.
Is there another reason why this could be happening?
Thanks for the quick reply. I tried the bzImage file that you point to but it immediately gives me a “flags mismatch” error and then the same thing happens.
How can I tell what driver isn’t working? There has to be an easier way than this, no?
Also, those fixes seem to be for an Atheros NIC but these computers are all Broadcom.
Hi Everybody,
I think I’m going to love FOG if I can ever get it set up correctly.
I cannot seem to register any hosts onto the server. Most of the computers are Vostro 230s which are compatible as per the [URL=‘http://www.fogproject.org/wiki/index.php/WorkingDevices’]working devices page[/URL]. I can get to the FOG boot page, but that’s it.
I have tried multiple different kernels, editing /tftpboot/pxelinux.cfg/default and making sure the ip address is correct but nothing works.
I consistently get an “inappropriate ioctl” error.
What am I doing wrong?