@HorizonG What is the version of FOG you’re using?
If I had to guess it’s the 1.5.10, but I believe this may have been addressed later (though admittedly I’m not for sure that it was.)
Another option, if you’re willing, is to install working-1.6 where I’m pretty confident this isn’t an issue. Though (to be fair) I’m not certain the translation systems are 100% updated anymore. (so many things may show up as plain US English, but hopefully that’s not a complete hinderance).
@dvorak You’d need it in the ISO.
PXE is before the system is loaded, and as such cannot trigger actions at the HDD level beyond loading a Disk, Boot Rom, or whatever.
https://news.fogproject.org/fog-1-5-10-41-officially-released/
While this maybe spur of the moment, it should officially release 1.5.10 with all relevant bug/security fixes encapsulated (among a few other features.)
This has brought a new methodology of releases in that bug/security releases should be done much more regularly.
dev-branch, historically, was a place where new development occurred (hence its name) but over the last couple of years or so it’s mainly been a bug/security thing, not really a true development approach.
This is OKAY, in my head. Why:
Well we have the master branch which is the ‘baseline’ of a verions. We have the dev-branch, which allows us to work on bugs/security issues. We have the working branches for what will eventually become master. Working is our “dev branch” but keeps proper seperation of things in my opinion.
Basically:
master -> basis for dev-branch (which merges into stable on a regular cadence - still being worked out)
working -> basis of forward development
So we effectively have:
production
staging
development well seperated.
THis may mean on the regular automated releases, no announcement or news article will be created, and I think that’s okay.
Hopefully exciting we have a release after 1.25 years 
Thank you!
@sideone Assuming that was the case, I have pushed code that should try to right trim the directory seperators from the paths being looked for.
Hopefully that might help you as well.
@sideone Can you look at your storage node list and validate that the image paths on all of them, do not have that trailing slash?
I suspect the DB is storing with the slash and that’s returning the empty set you’re seeing which is why you’re seeing the error.
I can try to take care of that myself as well, but for the moment, it will help with suspicions of the cause you’re seeing.
@HorizonG What’s the exact error you’re getting?
Can you provide pictures of the issue?
Do you have logs you can inform us with?
Do you have information about what fog version you’re using?
@sideone No problems, it seems (based on what I can tell), you are having issues with getting files off the server possible.
That error is trying to get the files for snapins, logs, or images. (It’s a common function)
but the response is returning nothing.
Specifically the url to get it would be:
‘<schema|http|https>://<FOG-IP>/fog/status/getfiles.php?path=<path to get items>’
So if you’re willing in a browser try to acces probably /images/
@JJ-Fullmer But should it just be a backup, or just a history that can be reverted between?
How many iterations should we allow? (So we have to track by version number/date, and that there are those different versions, and where they’re located, and dynamically update the “location” path to which ever is the most current version.)
Just thoughts out there, but complicated and too simple to screw up. It really needs a schema thought process (maybe a plugin could do this?)
@paranoid64 I understand it’s just a request, just wanting to expectation set a little as well.
I don’t want a person thinking I’m simply putting your request out of hand vs another having been brought it with seemingly little thought.
I like the idea of the clone approach, when to add is a different question, but I feel like it could be useful to have a definition cloning feature for more than just “images”, but for hosts, groups, etc…
So implementation of such a thing and how best to go about it is the part I have to figure out.
@paranoid64 I think that’s the subjectivity of the admin I’m afraid.
For you, it doesn’t make sense to schedule a task that is an image capture unless you have the 2/3 latest backups available.
To another, they never would schedule a capture task, and only ever capture when physically approved and agreed.
To yet another, they don’t care that the scheduled capture overwrites because that’s how the manual system works anyway.
Which path should I take as the programmer trying to implement things?
To the idea of “backup”. FOG was never intended to be a backup solution, nor does it pretend to be one. I’m not saying you cannot use it for such a purpose, but us programming these things without a real “useful to all” approach just makes it happy for your usecase, but horrible for the next person (who may just well ask for a feature requesting we do away with that ability altogether.)
A copy/clone method could be useful, though it’d be more toward the definition instead of the actual phsycial files being copied no?
@paranoid64 I don’t understand your request very much.
While it could be done, should it really be done?
You’re asking us to put in a feature to effectively use 2/3 times the amount of storage for each image capture task. Versioning is one method of handling things but generally only useful in small pieces. Ultimately I don’t think this is something that should be added to FOG as it is difficult to manage, and puts your disks in potential danger if you forget that you have 2/3 of the same image.
Can you add more context of how this should be the standard for everyone who uses fog?
@sideone That 500 means I will need your error log.
Assuming you’re using ubuntu it will be in:
/var/log/apache2/error.log I believe.
Assuming redhat version:
/var/log/php-fpm/www-error.log
@sideone @MatMurdock @JJ-Fullmer Should be fixed in latest.
@sideone For the ssh2 error I think/hope I’ve added the ability to install the php package necessary automatedly.
It is in the main config but never really required it being installed for usability. Apologies on that bit.
Please update and try again? I cannot say it will fix the hiddenmenu issue you’re seeing but it should address the ssh2_connect error you’re seeing.
@MatMurdock If you look at my signature it will show different places for the log files.
@fogcloud FOG is a web based system. The same points that a machine needs to get to for imaging, pxe boot, etc… hit’s the same “place” as the going to the FOG UI. You could block it (not with a firewall mind you) by editing your fog’s base.php.
While not a perfect system, you could potentially change it by adding to the end of the file:
$ip = $_SERVER['REMOTE_ADDR'] ?? (
$_SERVER['HTTP_CLIENT_IP'] ?? (
$_SERVER['HTTP_X_FORWARDED_FOR'] ?? false
)
);
// If the IP is found and ip is not your machine and we have a useragent string - from browser usually - don't allow access.
if (!($ip === false) && $ip != '<your system IP here>' && FOGCore::$useragent) {
die();
}
@tomas-voboril The button would still be visible, but I am fairly sure it would not work.
@sweeperdave So a machine of the same make model (and roll out) works perfectly fine, but this one machine has an issue?
(Not in windows of course, but just trying to understand the issue.) I see @fogcloud has written, and I apologize for missing this sooner.
I suppose “details” are what we need to potentially be able to help.
If suddenly ALL of the same make model (equipment roll out) are acting up, I would have to ask:
“Did you update kernels recently?” but if that’s not the case we are pretty sure it’s limited to this one machine.
At that point, I would say take a known working system, look at the bios configuration and see if there’s anything different in this strangly acting system. (If I had to guess it’s related to VTx technology enabled or something like that on this machine vs the other machines.)
Be cognizant of BIOS/Hardware Firmware versions and what not as well as those can also play a role in the overall operation of the device. Since replacing the drive and testing the same machine produces the same problem I’m leaning more specifically to the BIOS itself here.
This is just my experience.
If everythign else is effectively 1:1 from another, then this could just really be a faulty machine that only presents itself in the imaging process.
@tomas-voboril There’s a plugin called access control that I think you’re effectively looking for?