Best posts made by Tom Elliott

Tom Elliott

Figured out the problem.

This is because of 4k disks. I won’t go into the specifics, but I can try to show the math that equates out exactly what was happening:.

I was taking the size, making it a multiple of 1024:

9637387 * 1024 = 9868684288

On a 512 block disk (normal sized from long ago) The math than goes:
9868684288 / 512 = 19274774

Then we align it as needed (no need to show that work here).

On a 4096 block disk (4k) the math was being presented as:
9868684288 / 4096 = 2409346.75

Now if you make that number an int, you can immediately see it EXACTLY equals the number sectors trying to be copied.

Take that 2409346 and multiple it by 512 and you get about 1.2 GB of disk.

I’ve taken correction action on this and hope this will no longer be present.

As always, please re-run the installer and this capture issue (which appears to me to be only related to 4k disks) should be fixed.

Tom Elliott

@jj-fullmer @Wayne-Workman I’m of the belief we keep centos/rhel support.

You’re right that many may not be using CentOS anymore, but I still believe it’s far more stable than even ubuntu/debian. People Seem to be using it because it is supported, but please don’t forget all the changes we have to make to our installation scripts each new release of Ubuntu/Debian.

Compared to RHEL, we rarely need to make any major adjustments it seems in my experience.

Plus, the installer seems to work for Rocky/Alma, because these are following with RHEL as well. Removing the one installation portion that seems to actually just work with limited intervention seems like a bad move. Plus it still allows the administrators to use different variants of linux.

Limiting specifically to Ubuntu/Debian would leave all of that out. Now, of course, the scripts could be cleaned up and should be, but I’m not kidding about each new Debian/Ubuntu release still has so many new issues that we still need to make up for.

Tom Elliott

Can you please try rechecking?

https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP

Tom Elliott

So I’ve basically not failed to create a snapin due to spaces in the filename, rather i’ve told it to change all special characters in the filename to become underscores. This should prevent all the issues of delete/filenaming issue, etc…

Thanks for reporting.

Tom Elliott

https://news.fogproject.org/fog-1-4-0-rc-2/

Tom Elliott

@THEMCV

#!/bin/bash

#----- MySQL Credentials -----#
snmysqluser="root"
snmysqlpass=""
snmysqlhost="10.4.200.150"
# If user and pass is blank, leave just a set of double quotes like ""
# if the db is local, set the host to just double quotes "" or "127.0.0.1" or "localhost"


#----- Begin Program -----#

selectAllSnapinIDs="SELECT sID FROM snapins ORDER BY sID"
selectLowestSnapinID="SELECT sID FROM snapins ORDER BY sID ASC LIMIT 1"
selectHighestSnapinID="SELECT sID FROM snapins ORDER BY sID DESC LIMIT 1"

options="-sN"
if [[ $snmysqlhost != "" ]]; then
       options="$options -h$snmysqlhost"
fi
if [[ $snmysqluser != "" ]]; then
       options="$options -u$snmysqluser"
fi
if [[ $snmysqlpass != "" ]]; then
       options="$options -p$snmysqlpass"
fi
options="$options -D fog -e"


#Information gathering.
lowestID=$(mysql $options "$selectLowestSnapinID")
highestID=$(mysql $options "$selectHighestSnapinID")
newAutoIncrement=$((highestID + 1))


####### Basic logic flow ########

#If there is a snapin id of 1, move it to the new auto increment number.
#After re-numbering is complete, the new auto increment number will not be taken.
#Then reset the auto-increment to the new auto increment number, which is the first free number.



#Move any snapins that have an ID of 1 to the next free number.
if [[ "$lowestID" -eq "1" ]]; then
   echo "-------------------"
   echo "Attempting to change Snapin ID $lowestID to $newAutoIncrement"
   mysql $options "UPDATE snapins SET sID = $newAutoIncrement WHERE snapinID = $lowestID"
   mysql $options "UPDATE snapinGroupAssoc SET sgaSnapinID = $newAutoIncrement WHERE sgaSnapinID = $lowestID"
   #mysql $options "UPDATE hosts SET hostImage = $newAutoIncrement WHERE hostImage = $lowestID"
   echo "Attempt completed"
fi


#Re-number all snapins sequentially.
count=1
mysql $options "$selectAllSnapinIDs" | while read snapinID; do
   echo "-------------------"
   echo "Attempting to change Snapin ID $snapinID to $count"
   mysql $options "UPDATE snapins SET sID = $count WHERE sID = $snapinID"
   mysql $options "UPDATE snapinGroupAssoc SET sgaSnapinID = $count WHERE sgaSnapinID = $snapinID"
   #mysql $options "UPDATE hosts SET hostImage = $count WHERE hostImage = $imageID"
   echo "Attempt completed"
   count=$((count + 1))
done


#set new auto-increment.
echo "-------------------"
highestID=$(mysql $options "$selectHighestSnapinID")
newAutoIncrement=$((highestID + 1))
echo "Attempting to change the auto_increment for the snapins table to $newAutoIncrement"
mysql $options "ALTER TABLE snapins AUTO_INCREMENT = $newAutoIncrement"
echo "Attempt completed"

Tom Elliott

The issue, for others who may stumble across.

If you’re getting Private key not found but all the data seems to point that you do have a Private key file. Make sure the node (ip address or whatever) is actually a node within the system.

In @raumin’s case fog-server was not the node he was working with. The node he had defined was a NAS. NAS’s suck (plain and short) but have their own uses. (No offense to anybody using one, just they’re a bit of a pain to play with to get working with fog).

So the clients were looking at the thing @raumin is using as the GUI access point for private key. This was not a defined node (and I will try to come up with a better approach).

The fix, for now, is to always have a node for the GUI as well. You do not need to have the node enabled for things to work, and I would highly recommend against using in such a setup (NAS->Central GUI) trying to make the GUI node a “master” of the group it’s working with, unless you want it setup in such a way.

For our fix. We created a definition for the node and gave it the proper ip address. All started working immediately.

Tom Elliott

I’ve solved this thread so I don’t go nuts thinking I have keep finding and fixing this issue. Filenames with spaces (as well as other special characters) will be replaced with _ and this will be available to the next RC release.

Tom Elliott

https://news.fogproject.org/fog-1-4-0-rc-4/

Tom Elliott

I’ll be honest, I wasn’t aware anybody even used that script. Give me a bit, probably tomorrow, and I hope I’ll have that script back to operational.

Tom Elliott

My magic is fixing it now.

Will be in for RC-27.

Tom Elliott

Sorry for the quick update here.

I found that there was a relatively significant issue with the API system handling accounts. It went unnoticed and I just happened across the problem. This is namely pushed up to address this potential Security flaw. If you’ve already updated to RC 7, Please update as soon as you can.

Tom Elliott

When you create the tasking, you can choose to have the system shutdown when complete.

Tom Elliott

I confirmed and fixed the issue in 1.6 now. Thanks for reporting.

Tom Elliott

I’ve been reworking the display elements of the FOG GUI to be a little bit more professional. In my endeavor I’ve also made the GUI much more Windows friendly. (See Screenshot)

You’ll notice a bunch of things have changed, as I’m working to make FOG a little more friendly and professional looking. It’s a cleaner layout, I think. Of course I’m far from perfect.

If any decent web devs are around and feel like playing around, please install the working branch.
Update your FOG_THEME in FOG Settings and change it to read as clean/fog.css

The file to look over/review is located in /var/www/fog/management/css/clean/fog.css (You’ll notice there isn’t an equivalent images folder. This is intentional for now.)

Tom Elliott

Should now be fixed, thanks for reporting.

Tom Elliott

How about this for a login page:

Tom Elliott

When you say is being written to, are you manually uploading the file yourself? Capture will work out of dev which is not replicated. However, moving from dev into /images would work. Most cases I think /images and dev are on the same disk. Probably often times on a spinner vs an ssd. If it’s to a spinner via San I imagine that being slowest form of all as not only is it running on spinner but also redirecting across network.

As dev is not replicated and you’re seeing this issue, it would seem to me this problem is not related to upload tasking. If you’re manually uploading the files to the server, as Wayne suggested, either don’t create an image definition or when creating the definition disable the replicate by unchecking the box. Perform your manual steps and once complete re-enable replication.

Tom Elliott

Here’s what I’ve done so far:
Topbar:

Collapsed Nav bar.

Tom Elliott

@ttrammell https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP