Posts made by Daniel Miller

Can you link the directions you followed?
Which version of FOG?
What are the settings for your storage node(s)?
What are the settings in FOG Configuration \ Fog Settings \ Web Server? nvm

Yes, you can either mount the filesystem contained on the second disk under /images or change the image path and ftp path of the storage node to the mount point of the filesystem for the second disk. If you are adding this storage after installation, you will want to double check that your directory permissions and ownership matches the existing /images directory and that you create the .mntcheck files. More detailed guidance can be found on the Wiki: Adding Storage to a FOG Server.

@texturtle It should use the full block device path, /dev/sdb for example.
It looks like that tidbit didn’t make it onto the Managing FOG page in the wiki during the last revision.

Have you tried setting the Host Primary Disk in the host settings?

You might be able to use hostinfo.php to pull down the variables for the machine. I would think it would have those fields available.
https://forums.fogproject.org/topic/6463/expose-fog-host-and-image-properties-to-post-install-scripts

If you didn’t want FOG to manage the hostname, you could disable that in the service settings. I also remember something about a FOG API someplace, but haven’t played with it yet… https://news.fogproject.org/simplified-api-documentation/

@Greg-Plamondon said in FOG User Tracking -Search:

what repo is 1.6 in?

should be able to do a git checkout working-1.6, if I recall.

@Greg-Plamondon said in FOG User Tracking -Search:

I checked the userTracking table in the fog database and it has 22104 records

You can keep pushing execution time out, but it is quite possible that you may have too many entries for php to handle the data in a reasonable time frame, especially if this instance has been running for a while. If you don’t need the historical data, truncating the userTracking table (truncate table fog.usertracking) as suggested in https://forums.fogproject.org/topic/11713/503-service-unavailable-error/54 should get it up and running and will show data going forward until it gets too ungainly again.

Good, the values are changing.

there is also an execution time limit that should be set in one of the ini / conf files as well. I believe the setting is max_execution_time which I think takes a value in seconds and defaults to 30. you may want to play with that value to see if you can get a response in a reasonable time. It may take upwards of a minute or two depending on how many entries are getting pulled.

Actually, if the allocated memory size in the exhaustion messages is remaining constant at 268435456 across all changes and you have yet to see anything referencing a memory size of 256MB, it might be time to go digging for where that value is set. It may be worth running a sudo grep -r memory_limit /etc/* to see in which ini that 256M is set and modify the value there. If it is in the fpm php.ini, you will need to restart the php fpm service.

@Greg-Plamondon did you restart the fpm service? Command to do so will be similar to sudo systemctl restart php7.1-fpm.service.

That log file may be /var/log/php7.1-fpm.log on Debian / Ubuntu

Which version of FOG?
What is the host operating system?

Edit:
Also, approximately how many users and how many hosts are you expecting to be searching through?

To what end? The bind user is there to allow an authenticated search for the authenticating user’s DN so that an authentication check can occur for that user. The purpose of this technique is to permit the binding of users from arbitrary OUs and this user is often intentionally only given sufficient privilege so that they can do that search (principle of least privilege). In general, it would be considered a security risk to have the search functionality fall to an actual user’s account, and depending on how the LDAP domain was configured, doing so may break the login function as there is not a general requirement for user accounts to be able to search on an LDAP domain.

Now, if you happen to know what the DN suffix will be, an alternative to the search and bind method would be a direct bind where the required static information is added to the username to create the DN that is proffered to LDAP for the bind request. This authentication method would require changes to the LDAP plugin as it exists in 1.5.7 as I do not believe it is currently coded to support it. There has been a bit of work done to the LDAP plugin in dev-branch, but I’m not sure if they have looked at adding other binding methods.

@Gilberto-Ferraz said in Boot Option Issue (PXE booting):

Hello @Brendan-Clemente!
I have the same problem I tried to solve with the suggestion of @george1421 using Dell CCTK tool kit. But I could not. Are all your machines from Dell for this tool to work? Do you have any tutorials to follow?

Tools for working with BIOS configuration options are both manufacturer dependent and model dependent. Most manufacturers are moving toward some kind of wmi-acpi support, but each manufacturer has their own timetable for switching and that switch requires a new tool. You will likely want to consult the support pages for the manufacturer(s) of your machines as there is no universal solution.

@Sebastian-Roth without logs, dumps, or the ability to replicate, options for doing so are getting kinda thin…

@mpatel said in Windows 10 issues:

“WebCacheLock.dat” … “WebCacheV01.dat”

Both are related to caching and history mechanisms in IE / Edge and may be safely deleted.

@MHImager If it works reliably with another machine of the same model, I would start questioning the integrity of the problematic machine. Being things seem to be failing inconsistently, it might be worth it to run a memtest and run it through dell’s onboard diagnostics. While not at all common, I have received a couple of machines with dodgy RAM that have done weird things over the years.

@SBrady If you are using the gparted live cd, you should have access to dd. Provided your new small disk is the same size as, or larger than, the original disk and both the new and old disks are attached to said VM, you could do something along the lines of sudo dd if=/dev/xvda of=/dev/xvdb bs=1M where xvda is the old disk and xvdb is the new disk. it will error when it reaches the end of the smaller disk with a message indicating there is no more space left on the device. I’m sure there are more graceful means of doing it, but it will get the job done.

Note: if you get the disk identifiers backwards, you will wipe the content of the original disk. It is best to confirm the disk identifiers are mapped to the disks you think they are before running dd.

@SBrady Does Xen not let you shrink virtual disks?
Well, if you can’t shrink the disk, you could ways create a new 25GB (or whatever your original disk size was) virtual disk, use some kind of disk cloning solution to copy the original disk data to the new volume, then shuffle things around so the new volume is in the same device position as it was originally, then re-partition and format the 250GB disk.

With the way your partitions are situated, if you want to simply expand xvda1 to take up the new space you allocated, you will have to do so through a live cd or something similar; the extra space is not currently contiguous with xvda1, so something is going to have to move. You could also create a new volume to mount, but that will require modifying the partition table on a running system … not my favorite thing to do. Safest is still to do it with a live cd.

Alternatively, adding the additional storage as a new virtual disk and then mounting that virtual disk under /images would give you the storage separate from your system volume (always a plus in case you don’t realize you don’t have enough room for a capture) and would give you greater operational flexibility, for instance when you need to add storage later or need to migrate to a new VM.