@Lee-Rowlett Thanks for the update. I have pulled commit 18be28c669b02a8372230d29de8524e24acc58ff on the dev-branch and the issue has either changed or a new issue has emerged. It is saying Invalid Mac Address. I have done a bit of a google and not found anything applicable to this situation. Is this just the new message for the same issue or something else entirely?
Posts made by tlawson
-
RE: Attempting To Send Inventory - Invalid Host?
-
RE: Attempting To Send Inventory - Invalid Host?
Hate to bump but this is still happening and I am not confident blaming it on the specific devices for an RMA but we cannot just waste the devices by not imaging them either.
-
RE: Attempting To Send Inventory - Invalid Host?
@Wayne-Workman FOG Version 3771 on ubuntu server 12.04 LTS using undionly.kpxe and have have checked and there is nothing conflicting and the server has been rebooted during this time period. Also this isn’t an inconsistent thing. These two specific machines are failing the same way over multiple days, though I do understand the need to ask and be sure.
-
Attempting To Send Inventory - Invalid Host?
Hi All,
Recently we have started getting an odd issue with a very select number of computers. Over the past week 2 out of 10 computers we have imaged with FOG have failed in the inventory stage and will not procede to imaging.
8 of the computers where the same hardware (from the same batch) of which 1 failed. The other 2 are laptops of the same hardware of which 1 failed in this following way.
Everything looks good when doing a full or quick registration however at the end of the inventory collection, when it attempts to send to the server, we get the error in picture linked below and it just sits there forever.
https://instagram.com/p/5IwSa2jKI-/The final line says:
- Attempting To Send Inventory … Invalid Host
The two machines that this is happening on have not been registered to FOG before and I have attempted updating FOG and updating (as well as downgrading) the kernel used as well, with no success.
Any advice what to try next or assistance in resolving this would be much appreciated.
-
RE: Cannot update image anymore
@RLane It does appear that may have been the issue as the permissions alteration has fixed it.
@Wayne-Workman All solved!Thanks for the assistance, really appreciated.
-
RE: Cannot update image anymore
@Wayne-Workman I did see that one. While the permissions are set to 777 /images is all root:root as the owner, along with previous failed attempts getting past that ntfs flag and getting stuck on “Stopping fog status reporter” however I was not able to bring that one up when I decided to write this post.
I will give that a go though and see if it resolves the issue.
Thanks Wayne.
-
RE: Cannot update image anymore
@Jbob: Sorry for leaving that out. It is indeed commit 8442096388f0e044f19bc18b9c9e6a3c86f1022a.
Although this was happening yesterday as well. Updated then too so that was a few commits behind what it is now.
-
Cannot update image anymore
Hi All,
I am using the latest “dev-branch” of the git repo for FOG that is available at the time I am posting this.
We love FOG and use it to image many computers however recently we have not done that much imaging. Upon returning to imaging yesterday I found that we cannot update any FOG images. The hardware of the server and clients has not changed since it worked.
The upload seems to work perfectly until it attempts to wrap up and I just get this screen.
That last part, the new line containing just an asterisk, just goes on forever. Every few minutes it just adds another one of those lines, forever.
Any assistance or tips as to what to do next would be much appreciated as we really need to update our images.
-
Ipxe error 1d0c6139
I have just updated to revision 2225 and i can no longer PXE boot into the fog interface as i get ipxe error 1d0c6139. After further investigation it seems to be because of this in the apache logs:
[CODE]File does not exist: /var/www/mod_pagespeed_beacon, referer: http://gxn-fog/fog/management/index.php?node=about&sub=kernel-update
PHP Fatal error: Call to undefined method BootMenu::HookManager() in /var/www/fog/lib/fog/BootMenu.class.php on line 408[/CODE]I am sure it will be fixed soon but i just wanted to make sure someone knew about it.
-
RE: PHP Failures
[quote=“Tom Elliott, post: 31923, member: 7271”]svn 1983 should fix this for you.[/quote]
Indeed it does.Just wanted to make sure that it was known.
Thanks.
-
PHP Failures
Hello,
After updating to the latest trunk today i lost access to the web interface entirely. After the database schema update it just had a blank page with the FOG branding at the top.
After looking at the apache logs i figured this was at least one of the offenders:
PHP Fatal error: Function name must be a string in /var/www/fog/management/index.php on line 71On line 71 on that file i found the following:
if ($currentUser && $currentUser())which, just to see what happened, i changed to:
if ($currentUser)Now the web interface gives me the standard fog homepage and its all working fine… Except, I cannot go to any other pages whatever. I cannot open tasks. Cannot view hosts. etc.
Any further assistance with this would be greatly appreciated as soon we are meant to be imaging a large shipment of computers with this system.
Kind Regards,
Taylor Lawson -
RE: Fog getting hung up on Database Schema Installer / Updater
However the extra steps mentioned here [url]http://fogproject.org/forum/threads/database-update-failed-1-1-0-to-1-1-1.10809/#post-30630[/url] did fix the issue. Seems like /var/www/fog/lib/fog/Config.class.php had a randomly generated password in it for the database the same as /opt/fog/.fogsettings.
-
RE: Fog getting hung up on Database Schema Installer / Updater
[quote=“Tom Elliott, post: 30629, member: 7271”]Can you give these steps a shot as well?
[url]http://howterrorisminindia.blogspot.com/2013/03/error-2002-hy000-cant-connect-to-local.html[/url][/quote]The path mentioned in this that needs to be linked already exists and the
ps -aux shows
up with no.socks
files.This part is a little out of my normal field so sorry if i am missing something.
-
RE: Fog getting hung up on Database Schema Installer / Updater
Hello,
I have this same issue however the suggested fix in [url]https://github.com/mastacontrola/fogproject/issues/1[/url] does not solve the issue.
EDIT: Also i can no longer see the iPXE boot menu as described here:
[url]http://fogproject.org/forum/threads/database-update-failed-1-1-0-to-1-1-1.10809/#post-30568[/url]and my apache error log shows the following when i try and run the update:
[Wed Jun 18 10:26:44 2014] [error] [client 10.50.253.181] PHP Warning: mysqli::query(): Couldn’t fetch mysqli in /var/www/fog/lib/db/MySQL.class.php on line 89
[Wed Jun 18 10:26:44 2014] [error] [client 10.50.253.181] PHP Warning: MySQL::sqlerror(): Couldn’t fetch mysqli in /var/www/fog/lib/db/MySQL.class.php on line 180 -
RE: Quick Inventory Group
I am a little daft. It seems i missed a crucial part of the FOG AD wiki ([url]http://www.fogproject.org/wiki/index.php/Active_Directory_-_FOG_Setting#Groups[/url]) where it states
[QUOTE][B]Note:[/B] This is a applied in a batch for each host in the group when saved. These settings are not stored in the group settings permanently, nor applied to future hosts automatically when added to the group.[/QUOTE]So this still does not solve my problem of wanting to auto add new machines to AD without intervention. Thanks anyways though.
-
RE: Quick Inventory Group
[quote=“Tom Elliott, post: 28179, member: 7271”]This is now added and functional in SVN 1731[/quote]
Love your work, thanks mate.
-
RE: Quick Inventory Group
[quote=“Tom Elliott, post: 28012, member: 7271”]I plan to add a feature where the init registration asks if you want to add it to a group, but not for Quick Inventory. The reason? Because quick registration/inventory is designed to be just that. Quick, if we start asking questions about what you want for both Full AND Quick registration processes, it defeats the purpose. I may, for this purpose, add a field to the QUICKREG_AUTOPOP that allows you to assign a default group to assign the Device though. Hopefully this would achieve the results you’re looking for?[/quote]
Sorry if i was not clear, i did not intend this to be a question inside the PXE boot part, i meant as an option in the webui where i can set other settings for quick reg such as image id. I by no means wish to break the quick part of quick registration and inventory.
-
RE: Hostname CHanger not working since moving to 1.0.1
[quote=“Junkhacker, post: 27815, member: 21583”]that’s what i wanted. that response looks exactly like what i would expect for a computer that does not have the “Join Domain after image task” option checked in “Active Directory” section of “Host Management”
can you verify that is set, and the information is filled out correctly?[/quote]I have disabled that because i cannot let them go on the domain yet with the wrong hostname. Currently we are not putting these new machines on the domain for awhile anyways. I just need the actual hostname changed regardless of the domain setting.
EDIT: Also if i do set the domain it usually does add to the domain but never changes the hostname either. Usually it will add to the domain as the correct hostname even though the local machine is not set to that.
-
RE: Quick Inventory Group
[quote=“Junkhacker, post: 27856, member: 21583”]though, i would put it in as part of “full” registration instead of quick.[/quote]
The only reason I ask for quick registration is because my current proccess for new machines is to simply plug them in and do a quick inventory which also images the machine. That is where i would like it to end. However currently i would have to then, after quick inventory, log into fog, move it to the group which AD’s and possibly re-image it as it seems before it gets added to the domain.
It would be great to be able to give quick inventory a default group so that once it images it just adds to the domain and is just done there and then.