Hi

I’ve just tested this an it worked without issues - Thank you. I will try to post the contents of those files shortly. My question is, is this new init file good to be made the default somehow?

@imagingmaster21 IMO you have multiple things wrong here, all of them giving you a different error.

I would nuke the fogproject git repo directory and reclone it from github then rerun the fog installer.

Beyond that you need to confirm the FOG server ip address has not changed since fog was installed. You can do this by viewing the hidden config file /opt/fog/.fogsettings if that file contains a different IP address than is currently set you need to fix that too.

Once you have all of that fixed then you need to ensure you have the 5.6.18 FOS Linux kernel installed.

If you still have issues, open a new thread for each issue so we can keep the problems isolated.

@Sebastian Roth , thank you problem solved using your commands 👏

@cyannella Ok here is an updated init that calculates the MD5 sum of the captured image file. https://drive.google.com/file/d/13eknbYjZhpnsbfi7B_JpVY7KRe_n2xTw/view?usp=sharing

Download that file as init_md5.xz and copy it to /var/www/html/fog/service/ipxe directory on the fog server. It has a unique name so it will not overwrite anything FOG.

Now take ONE host where you can recapture an image. Go into the host definition and for the host init field enter init_md5.xz and then save the settings. Configure a capture task and then recapture your image. For every d1pX.img file there should be a d1pX.md5 file that contains the md5 hash of the file.

Just a note, a 16GB partition took about 15 seconds to calculate the md5 hash.

Lets see how this runs in your environment.

@cedre2 We didn’t mean to ignore you question. Though printers is not an easy topic. The fog-client was developed by someone not being in the team anymore and while I am trying to work on this as good as I can I don’t have the equipment to even test printer stuff.

Looking through the code I can see that currently the fog-client would only restart the printer spooler if a new printer would be added. From other situations I know that Windows 10 can be a real pain with updating printer information and you need to restart the spooler more often than not. Though I don’t think it’s a good idea to just do a restart of the spooler every time the fog-client looks at the printers.

Not really sure what to do about this.

@julianc said in Database unavailable:

The master node storage is my synology nas: 192.168.190.250

Did that setup work before? Or did you setup this just now?

Did you follow the tutorial to the point? Enabled FTP as well? Do you see the folder mentioned in the error message on you NAS in the images share?

@adrian-a since you are using a qnap device you might consider converting it into a FOG Storage node. You will give up some flexability but in a way you will make the qnap device the storage location for FOG. Here is an overview. https://forums.fogproject.org/topic/10973/add-a-nas-qnap-ts-231-as-a-storage-node-fog-v1-4

Just one limitation, if you use a qnap device as a storage node AND have all of your data on the qnap device, FOG will not replicate these image files to other storage nodes. Only a full FOG server can become a master node in the storage group.

@deblau73 Hello,
It’s perfect with set tftp-path tftp://${storage-ip}

Thanks

I had to run chkdsk a couple of times, thx for the help!

@sebastian-roth Well, ive done it already!

Thanks both of you for your help! I could never been able to figure it out without you! Thanks!

problem solved
thank a lot 🙂

@jgeear Is there a question here? I read this as you are stating facts.

Linux will not see any hard drive behind the intel RAID adapter. You must change it to ahci mode. Since the hard drive is not found FOG see the usb drive as a valid drive and will image it no problem.

Found and fixed - the .fogsettings file was clearly corrupted causing this issue. Very sure this was due to manual editing.

@george1421 Thanks for the information on this. Also, what is the process for updating the kernel? I know it is on the GUI side of FOG but not sure if the is a specific process to avoid any unexpected errors. I have 2 storage servers and not sure if this would affect the connection or settings.

Another thing is that I have already set up Windows 10 on this Dell 3410 laptop using the RAID settings on the BIOS. So how can I fix Windows 10 since when changing to AHCI I get a blue screen?

Any tips or suggestions would be greatly appreciated.

Thanks

@sebastian-roth thank you!

@mrawesome987 that is crazy obsecure, but I’m glad you found it.

This sounds like a perfect tip to add to the wiki @Wayne-Workman

@jacques-olivier said in Installation of FOG with external MySQL base:

Do you mean we can’t have a priviledge root user with another name to access our external database ? For example we would like to use theboss instead of root as this priviledge user already exists.

The FOG installer is programmed to do all the DB user and database setup for you. It will ask your root DB password (but not store it anywhere!) just to set the user and database up for you.

With the installer we try to help people and sometimes we have gone “too far”. I can see this is not perfect for people like you who have a custom setup and know what they are doing.

Looking through the installer scripts I think I found a way for you to get around this:

Create the database on your other server - e.g. named ourfogdb Create a DB user with all rights on that DB: GRANT ALL PRIVILEGES ON ourfogdb.* TO 'theboss'@'x.x.x.x'; Create a less privileged DB user called fogstorage (sorry this is still hard coded) that would be used by external storage nodes - you might not need that but the installer will check for it, sorry. Grant access rights for the fogstorage DB user: GRANT SELECT ON ourfogdb.* TO 'fogstorage'@'%' ; GRANT INSERT,UPDATE ON ourfogdb.hosts TO 'fogstorage'@'%' ; GRANT INSERT,UPDATE ON ourfogdb.inventory TO 'fogstorage'@'%' ; GRANT INSERT,UPDATE ON ourfogdb.multicastSessions TO 'fogstorage'@'%' ; GRANT INSERT,UPDATE ON ourfogdb.multicastSessionsAssoc TO 'fogstorage'@'%' ; GRANT INSERT,UPDATE ON ourfogdb.nfsGroupMembers TO 'fogstorage'@'%' ; GRANT INSERT,UPDATE ON ourfogdb.tasks TO 'fogstorage'@'%' ; GRANT INSERT,UPDATE ON ourfogdb.taskStates TO 'fogstorage'@'%' ; GRANT INSERT,UPDATE ON ourfogdb.taskLog TO 'fogstorage'@'%' ; GRANT INSERT,UPDATE ON ourfogdb.snapinTasks TO 'fogstorage'@'%' ; GRANT INSERT,UPDATE ON ourfogdb.snapinJobs TO 'fogstorage'@'%' ; GRANT INSERT,UPDATE ON ourfogdb.imagingLog TO 'fogstorage'@'%' ;

Now with that being prepared you should be able to call the FOG installer like this (untested, keeping my fingers crossed I did not overlook the obvious):

mysqldbname='ourfogdb' snmysqlhost=‘192.168.1.1’ snmysqluser=‘theboss’ snmysqlpass='password_of_theboss_db_user' snmysqlstoragepass='password_of_the_fogstorage_db_user' ./installfog.sh

@lukekfrost the FOG install doesn’t like it when the ip address of the imaging interface is changed after FOG is installed. There are several locations where the static IP address is recorded. You linked to the wiki page, also this post addresses the same issue as you have today. https://forums.fogproject.org/topic/15112/changed-ip-reinstalling-not-an-option

My unoffical instructions are to

Update the hidden file /opt/fog/.fogsettings fix the IP address in there. Update the IP address in /tftpboot/default.ipxe Update the IP address in the web ui under fog configuration->fog settings->expand all. search for the old IP address and replace it with the new address. In the fog storage node default, change the IP address in there. Back in the fog server linux console, rerun the FOG installer to fix the remaining bits.

I ended up finding the fix.

Step 1: Change IP Address, then deactivate and activate the network interface.

Step 2: Run the UpdateIP.sh within the fog-community-scripts-master.zip found here https://github.com/FOGProject/fog-community-scripts

Step 3: Rerun the installer.
If you have NO INTERNET CONNECTION, like myself in this case,
rerun with the -X option like so,

./installfog -X

I verified it worked with my new subnet and I was able to boot off my Fog Server, register new hosts, as well as capture and deploy an encrypted Linux image.

This was successfully done on a Rhel 7.9 VM with no internet connection FYI.

@seppim said in Advanced Login:

I guess I need to set the “Advanced menu command”? But why is this not out of the box working?

Yes, you need to add some custom advanced menu that you want to see after the login. There is no default.

Here is some example code you can start working on:

menu item --gap -------------- iPXE advanced boot menu -------------- item DBAN Boot and Nuke item SHELL iPXE Shell item RETURN Return to previous menu choose --default RETURN --timeout 10000 target && goto ${target} :DBAN kernel ${boot_url}/dban/dban.bzi nuke="dwipe" silent vga=785 boot goto MENU :SHELL shell || goto MENU :RETURN chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} || prompt goto MENU autoboot

Here is more stuff if you need: https://forums.fogproject.org/topic/7329/sub-menu-within-fog-advanced-menu