[Moderator’s Note] Moving topic to General Topics/General. This question does not belong in this forum.
Posts made by george1421
-
RE: N00b_Here: Plz help! New Setup for a company imaging solution
-
RE: Building a somewhat large cluster. Can FOG help?
First let me say I have no clue about crypto currency. But after reading this thread and having a general understanding of the setup here is what I would do.
Use buildroot to create a custom linux kernel, much like FOG’s FOS operating system. If one was ingenious, they could reverse engineer FOS and then possibly load the program needed for the crypto mining into the init.zx and also reconfigure the master
fog
script in FOS to call the crypto mining program. FOS boots and runs out of memory, no hard drive is needed.Now the cleaner way would be to use buildroot to create your own custom linux OS with all of the required applications. Once you have your bzImage and init.zx you can launch with FOG by creating a custom iPXE menu.
You could use some of the concepts here:
https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-imagesand here:
https://forums.fogproject.org/topic/11194/poc-using-fog-as-a-netboot-serverwith the custom linux OS.
Or you could either create or use an existing live OS and pxe boot it using FOG.
There are a number of ways to get a live boot linux OS running on a diskless workstation.
-
RE: Error in SetupComplete.cmd
@wayne-workman According to the EULA you must install OEM images using the vendor supplied OEM media only. You can use FOG to PXE boot an OEM image for deployment, but you can NOT clone an existing OEM system using any deployment solution.
My friend Chris over on the Spiceworks Community wrote a article about reimaging rights. What is allowed and what isn’t. While this one is from 2015 MS hasn’t changed the rules in regards to what you can do.
Ref: https://community.spiceworks.com/how_to/124056-reimaging-rights-for-windows-10-licensing-how-to
But in regards to the OP’s post, he is right on the / vs -. Its more common and generally accepted by applications to use the forward slash. Many application also except the minus key switch. Us lazy linux guys probably just used the minus key switch because that is what unix expects. I don’t have a windows system handy to see if shutdown accepts both or only the forward slash.
As for the unattend.xml, it is a pretty good one. We from time to time have people ask for a generic unattend.xml file so uploading it to the wiki may not be a bad idea, just be aware its currently configured for The Netherlands in the internationalization bits. The rest are OK.
-
RE: Storage nodes opening multiple mySQL connections to Master DB
@dsloan-ethra So just to recap what was done here to adjust Debian 9 (where the referenced article also implies it is an issue for any Debian variant like Ubuntu) for others that might find the thread:
- Edit /etc/mysql/mysql.conf.d/mysqld.cnf
vi /etc/mysql/mysql.conf.d/mysqld.cnf
- Insert the following line in the [mysqld] section
max_connections = 8000
- Copy the systemd service descriptor file so you can customize it
cp /lib/systemd/system/mysql.service /etc/systemd/system/
- Append the following lines to this file: /etc/systemd/system/mysql.service
LimitNOFILE=infinity LimitMEMLOCK=infinity
- Reload systemd processor
systemctl daemon-reload
- Reload the mysql service
systemctl restart mysqld
- Login to mysql as root and run the following command.
mysql> show variables like 'max_connections';
- The response should be something like
+-----------------+-------+ | Variable_name | Value | +-----------------+-------+ | max_connections | 8000 | +-----------------+-------+ 1 row in set (0.01 sec)
- Done.
These are not my words, only restated from the accepted solution here that Sebastian found and referenced: https://www.rfc3092.net/2017/06/mysql-max_connections-limited-to-214-on-ubuntu-foo/
- Edit /etc/mysql/mysql.conf.d/mysqld.cnf
-
RE: Building a test environment
@foglalt The default.ipxe is a fog supplied config file. It is chained by undionly.kpxe or ipxe.efi.
The failed to get an up via dhcp error message is sometimes related to networking. More specifically the network switch having spanning tree enabled but not one of the fast spanning tree protocols like (RSTP, MSTP, Fast-STP, or what ever your switch port vendor calls it). A quick test to find out if its a spanning tree issue is to place an unmanaged switch between the pxe booting computer and the building switch. If the target computer boots correctly then you have a spanning tree issue with your building switch.
Also a clear picture of the error taken with a mobile and posted here would help to see the exact spot the error is being generated. The context of the error is almost as important as the error message itself.
-
RE: Building a test environment
I remember seeing a similar issue over the holidays (sorry too much celebration to remember exactly when). But I think the issue/key was a problem with Debian 9 causing tftp to not install correctly. Let me see if I can find that. I don’t think there was a resolution with it. I know the FOG Project test the distros daily to ensure they install properly.
Let me see if I can find that post.
[Edit] Not a solid resolution: https://forums.fogproject.org/topic/11253/cant-pxe-boot-pxe-t01-file-not-found
Now if you don’t have Debian 9 installed, we will need to dig a bit deeper.
-
RE: Storage nodes opening multiple mySQL connections to Master DB
Sorry for the delay. You might need to check the other directories to see if one of them are overriding your max connections.
You could search them quickly with
grep -R -e "max_connections" /etc/mysql
The newer versions of mysql don’t populate the my.cnf file, but use the .d directories to hold the configs. My bet is that mysql is finding what it needs in the .d directories and then just ignores your 500 value.
-
RE: Storage nodes opening multiple mySQL connections to Master DB
@dsloan-ethra said in Storage nodes opening multiple mySQL connections to Master DB:
max_connections
I guess lets start with what does your /etc/my.cnf file look like?
-
RE: Location Plugin - enhancement of behavior
Issues that will need to be addressed is location cidr addresses eclipsing other addresses.
i.e. Location A = 192.168.0.0/23
Location B = 192.168.1.0/24Or location A = 10.0.0.0/24
Location B = 10.0.3.0/21Also a quick google search finds php code to find if IP address is in a specific CIDR range.
/** * Check if a given ip is in a network * @param string $ip IP to check in IPV4 format eg. 127.0.0.1 * @param string $range IP/CIDR netmask eg. 127.0.0.0/24, also 127.0.0.1 is accepted and /32 assumed * @return boolean true if the ip is in this range / false if not. */ function ip_in_range( $ip, $range ) { if ( strpos( $range, '/' ) == false ) { $range .= '/32'; } // $range is in IP/CIDR format eg 127.0.0.1/24 list( $range, $netmask ) = explode( '/', $range, 2 ); $range_decimal = ip2long( $range ); $ip_decimal = ip2long( $ip ); $wildcard_decimal = pow( 2, ( 32 - $netmask ) ) - 1; $netmask_decimal = ~ $wildcard_decimal; return ( ( $ip_decimal & $netmask_decimal ) == ( $range_decimal & $netmask_decimal ) );
ref and thanks to: https://gist.github.com/tott/7684443
If this has to be done in Ash (FOS environment) then maybe a tool from RHEL (ipcalc) could be implemented in buildroot for FOS. ref: https://arstechnica.com/civis/viewtopic.php?p=23215698
-
RE: Cant PXE Boot = PXE-T01: File not Found
@404 You can do something similar but not exactly.
FOG does have a Deploy menu on the FOG iPXE boot menu. From the Deploy, you can select an image to send to target systems without needing to register the target system first. A hardware remanufacturer may use this route if they never planned on seeing the target system again. If the system was going to remain on your campus then I would suggest going the registration route because you have some post imaging capabilities not available when you just quick image a system. FWIW: registration has nothing to do with AD.
You can create submenus in FOG, actually iPXE if you hand code the submenus. Its not that difficult if you read up on iPXE and then create the menus in fog and test them for structure by using this url path on your fog server http://<fog_server_ip>/fog/service/ipxe/boot.php?mac=000000000001
-
RE: FreeNas FTP error
We do have two (three) tutorials for using a traditional NAS as a FOG storage node.
Synology
https://forums.fogproject.org/topic/9430/synology-nas-as-fog-storage-nodeQNAP
https://forums.fogproject.org/topic/10973/add-a-nas-qnap-ts-231-as-a-storage-node-fog-v1-4Windows 2012
https://forums.fogproject.org/topic/10097/setting-up-a-windows-2012-server-as-a-fog-storage-nodeThe point being you may be able to glean what is needed from those tutorials to make freenas work for you. I have not personally tried to setup a freenas image as a fog storage node, but on the surface it should be possible as long as it has NFS and FTP support.
-
RE: Location Plugin - enhancement of behavior
I do a modification of this (CIDR extraction) for my post install script for proper OU placement.
myip=`ip route get 8.8.8.8 | awk 'NR==1 {print $NF}' | cut -d "." -f1-2`; case "${myip}" in 10.1) sitecode="NYC"; timezone="Eastern Standard Time"; oupath="ou=computers,ou=nyc,dc=domain,dc=com"; ;; 10.2) sitecode="LA"; timezone="Western Standard Time"; oupath="ou=computers,ou=la,dc=domain,dc=com"; ;; *) # Default code for the unknowns sitecode="CORP"; timezone="Eastern Standard Time"; oupath="ou=computers,ou=corp,dc=domain,dc=com"; ;; esac
I think it would be a great idea. Any time we can eliminate system errors its a great plan.
Ref: https://forums.fogproject.org/topic/7740/the-magical-mystical-fog-post-download-script/6
-
RE: Unable to UEFI boot to Fog Server
@rboan Two things here.
-
If Windows 2008 DHCP doesn’t support automatic uefi/bios (I know it doesn’t) you can install dnsmasq on your fog server to supply the needed dynamic booting options. Basically you install and setup dnsmasq and then remove dhcp boot option 66 and 67 from your 2008 server.
-
It looks like you created some kind of advanced menu options. What the error is saying is the command you used in the advanced menu is not a keyword that iPXE knows or understands. What exactly did you add under the advanced menu?
-
-
RE: Setting fog's password
[MOD Note] Forking topic since the issue doesn’t directly relate to this tutorial.
-
RE: Latest Trunk build running on CentOS 7 - Snapin Create Fail
While I’m not familiar with the snapin system, that error makes me think that someone edited / changed the fog service account (
fog
’s) password. Understand this is the linux user calledfog
not the default webgui password of the same name. If you have happened to change the linux userfog
password there is a sequence you need to follow to reset it back to a known value. https://forums.fogproject.org/topic/11203/resyncing-fog-s-service-account-password -
RE: Unable to PXE boot on an isolated network
@kevindm82 Lets ensure that isc-dhcp is running.
You can use this command to see if its running in memory
ps aux|grep dhcp
It should responded with something like isc-dhcp-server and some command line switches.If its not there you can start with
systemctl start isc-dhcp-server
and check the status if its running withsystemctl status isc-dhcp-server
And finally ensure that it starts every time with ubuntu startup withsystemctl enable isc-dhcp-server
If you changed the IP address of the FOG server after installing the fog program you will have to fix or fog will not image. There are hard coded IP addresses that will need to be fixed.
-
RE: Unable to PXE boot on an isolated network
@kevindm82 Looking at your pcap file, I only see dhcp discover packets (i.e. your pxe booting client asking for dhcp information). There is no response from a dhcp server. On your isolated network what is providing your dhcp services?
-
RE: Chainloading failed. DHCP is OK.
Well here is what I see. You have a dhcp server at 192.168.244.254 and you have a dnsmasq server at 192.168.244.131, which is also your fog server.
The 192.168.244.254 is probably the vmware NAT dhcp server running on the NAT’d network. 192.168.244.254 is providing a next server value that is confusing iPXE when it tries to load the fog iPXE boot menu.
So how do you fix this?
Well it depends on what your final configuration needs.
- You can stop the vmware dhcp server, stop dnsmasq, and run the isc-dhcp server on the fog server.
- Remove NAT. Depending on your final environment if its on a totally isolated network then just run isc-dhcp server on your fog server.
- Remove NAT and if your business network has a dhcp server, you can configure it to send the right pxe boot names to the target computer, or turn on dnsmasq to supply the pxe boot information.
There are a number of things you can do to fix this setup. It helps to know what your needed configuration will be to choose the right options.
-
RE: Chainloading failed. DHCP is OK.
@marco-antonio Ah I see what might be going on, please look at the IM chat bubble in the fog forums tool tray.
-
RE: Chainloading failed. DHCP is OK.
@marco-antonio Ok let me take a peek at the pcap and see what it says. I may chat with you via FOG chat if I have many questions about what I see.