@george1421 That is because the separate storage group has a master. It’s a “work around” to the “Images are always captured to the master node” because you, quite literally, are making the storage node, now, a master node. It works of course for this reason.
Best posts made by Tom Elliott
-
RE: After 100% capture failed on database updaet.
-
RE: Encryption error when clicking on "list hosts", just set AD password.
@Sebastian-Roth I think we just need to refine the code a bit more. I don’t know why it’s getting the error, I just know what we did int he past for the passwords. I’m sure we can make a more proper fix without limiting what passwords an admin can use.
-
RE: snapins not deploying from storage nodes: Version 1.5.7.4
@Sebastian-Roth Thank you for finding and fixing the issue.
@Greg-Plamondon Thanks for reporting. This fix is also set for 1.6 now too.Awesome job everybody!
Thank you,
-
RE: Encryption error when clicking on "list hosts", just set AD password.
I found and believe I may have fixed the issue. It was actually pretty simple. The error was coming from the unpacking of information.
Hopefully it helps. Just repull the dev-branch and install and all should be back to normal.
-
RE: Upload Image From HDD 500GB to SSD 120GB
I’m really confused by all of this.
Your Image definition displays as
/images/05_09_2019_si_essa
, but the warning message from the machine you’re having issues with is displaying/images/28_10_2019_si/
as the image location.Too me, this seems like the host you’re imaging has a different image assigned to it.
-
RE: Centos/rhel install problem
So the setup per redhat documentation:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/installation_guide/chap-anaconda-boot-optionsIn particular, remove the
//
as the installer documentation shows it’s not to be set with nfs://inst.repo=nfs:${fog-ip}:/images/os/centos7-dvd
-
RE: Centos/rhel install problem
@rockinhc At one time, maybe the nfs:// worked fine, but it’s since been deprecated and as a part of that, i imagine when @george1421 created that article, the OS version wasn’t at the version it is now. Even though it’s still CentOS 7, its incremental upgrades may have removed the deprecated options as well.
-
RE: Upload Image From HDD 500GB to SSD 120GB
On Ubuntu 18.04 it’s mariadb-server I think
-
RE: Blank Install Page
@dsoden @Sebastian-Roth @george1421
Please provide the error log from :
/var/log/php-fpm/www-error.log
This will provide the error causing your White Screen.
The issue with CentOS 8 is being addressed, but we need information.
You’re right that opensource works when it works, and believe me, we want to help and get this fixed.
Changing the hostname, for fog, does not change the hostname for the machine. This is more related to updating the SSL certificates based on the DNS Server.
The installer tries to do everything it can for you, but there are areas we try not to change, such as the physical machine hostname as there could be any number of reasons this is setup as such.
Can you explain how it’s things are worse?
I want to help, and I’m 100% sure we can get this fixed and running for you. I just need information to be able to do that. I actually have a CentOS 8 server running for testing at work.
No amount of bickering, backtalk, or anything (from anyone) is going to help that.
-
RE: Failed to upload image (Process Hung)
@Keating178 The Invalid Storage Group error you were seeing should be fixed if you can upgrade to the latest within the dev-branch from GIT.
Hopefully this will fix the issue you were seeing too.
-
RE: FOG 1.6, identified problems
I have identified a few more issues and been able to correct them.
-
Clicking on pages within the menu as opposed to full refresh on the same page, some elements such as list -> select items to delete, click delete, the modal not appearing requesting password to ensure you want to do this. On full refresh to link it worked. On clicking from the menu it didn’t. Fixed by causing reinitialization.
-
Import elements didn’t return proper notification items. Similarly warnings and info notifications always assumed error. This has been fixed
-
Added rudimentary file upload progress system. Will be working to implement a progress indicator.
-
Creating images when entering the name, the path didn’t auto populate. This has been re-implemented.
-
Snapin file uploads were already set to be operational, but did not work due to typo on the POST field to send up the files. Renamed and introduced.
-
Host export didn’t properly indicate the primac field. It didn’t even pull in the Mac at all and the values were improper. The host name appeared in description, and name field was the spot Mac was trying to populate. Added the primac field and properly pulling the data now.
-
Along with the reinitialization for the modal requesting passwords, this same reinitialization was causing table populating to be reinitialization and throw an error as it already existed. Set to retrieve so not to throw the error.
-
-
RE: Failure in Capturing an image
@Sebastian-Roth the Macs are being captured as raw, which captures the entire disk, not the partitions.
-
RE: Common WebUI pages takes minutes to load.
Would you mind trying on working-1.6? (Preferabbly the same database but on a test instance?) to see if performance is improved at all?
-
RE: FOG 1.6, identified problems
@maverick2041 I found the issue and was able to add a fix for it.
Please run a git pull and reinstall.
Of the fix also 2 little features come in:
A refresh button for the Data tables, so you can force a refresh of the data within the table being seen.
Added whoami route to the API. This returns a json formatted string with the following information:
{"ipaddress": "275.275.275.275", "hostname": "fogserver", "osid": "1", "osname": "Redhat", "installtype": "N"}
The 275 is meant to ensure nobody guesses a proper IP.
Hopefully this will allow snapins to work properly in 1.6
-
RE: DHCP FAILED
@jeremyvdv Spanning tree enables the ports to wait for a period of time between link up/link down before the switch will pass the information to the machine in case there’s a link connected back to itself on the switch.
This up/down time can be around 27 seconds in normal Spanning tree mode. This would explain why during the automated portion the device cannot get a link or IP, but once at the terminal and restarting the networking it will pick it up.
If your network is using spanning tree, if you can do so, disable it, or if not it’s best to use one of the Fast/Rapid stp methodologies as their up/down time is much more significantly reduced.
-
RE: Development FOG not capturing image - PartClone update
@ty900000 I just pushed another update, though it may be a little while before the artifacts are ready for testing.
I’m fairly sure the issue here has to be the FIFO. I’ve also gotten rid of the “Maybe check the fog server to ensure disk space is good to go” by providing the available disk space. It also adds the exact command that partclone is trying to use so we can see what’s going on.
2060 is just the case statement, so I don’t think it’s failing because of the case. I think it’s failing because the FIFO was still open. To combat this, I’ve added a 5 second wait to let the disk settle and release the information for the FIFO so we can remove it to recreate it later on.
-
RE: Default.IPXE-no such file or directory (2e008081)
@TOXYKILLER Here’s what I find for one of your IP’s (if this is you then cool, but still a bit on the “whoa wait a minute” side)
Source: whois.arin.net IP Address: 11.101.149.115 Name: DODIIS Handle: NET-11-0-0-0-1 Registration Date: 1/19/84 Range: 11.0.0.0-11.255.255.255 Org: DoD Network Information Center Org Handle: DNIC Address: 3990 E. Broad Street City: Columbus State/Province: OH Postal Code: 43218 Country: United States
What does this mean?
Well DoD own’s the IP Space in its entirety of 11.X.X.X (Including 11.101.X.X).
-
RE: Development FOG not capturing image - PartClone update
@ty900000 The problem with using 114, is it’s missing an argument. So the Segfault is double’d due to -c/-a0 and not likely due to either of the arguments, but rather the fact partclone is segfaulting as it cannot determine file size, as it is literally commented out of the code. This means, a raw (imager) image file will not be generated at all. (/images/<imagename>/d1p<#ofparttion_to_be_cloned_in_imager_format>.img will be missing comletely.)
In my case the partition number was 2, and in yours it appears the partition number is 3.
I have created a fork of the partclone repository and implemented what I would think should address the issue by reimplementing the filesize display capabilities. As @Sebastian-Roth learned, simply uncommenting the line allowed partclone to work properly (as far as we could tell).
Until we patch the issue on our side (either by using our forked copy of the repository or directly implementing it as a part of the build process), this is still going to be a problem. I think we have a way to fix it, just haven’t had time to implement and have you (or anybody else who’d be willing) to test it.
-
RE: Booting from SAN Device 0x80 hang
@lkisser in regards here it almost sounds like there could be 2 hard drives on the 3620? If so chances are the drive that is set to boot still has windows 7 installed, and the other drive actually has the windows 10 image on it. This is possible but again we’re left with too few details.
-
RE: Start in a special menu for a group or just an hosts
@Sebastian-Roth Yeah, this isn’t something readily available in the code.
@endia If you’re at least semi familiar with code, you might look into /var/www/fog/lib/fog/bootmenu.class.php
This isn’t currently coded for, but you might even be able to do what you want using a simple (relatively speaking) hook to alter the boot menu system.
There’s a template hook already created that should help get you started. By creating a hook, you aren’t altering the core code within FOG. Hooks are meant as a means to inject custom data specifically around what you’re requesting to happen.
The hook that’s setup is located in /var/www/fog/lib/hooks/bootitem.hook.php
Ultimately what you would do is make your changes and set the active flag to true. (it’s a variable named active)