Posts made by Tom Elliott

@fogcloud ssh in 1.5.10 and earlier isn’t required for anything but it will be required for 1.6.

After such a long time of using ftp I made a switch to prefer using ssh instead as it is generally more secure and can eventually (hopefully) be extended to allow Pki authentication which we cannot do for ftp based things. Plus it gives us much more utility than ftp provides.

I know you weren’t looking for a book on this all.

TLDR, no it’s not “required” but is effectively a default standard in dang near all operating systems now. It shouldn’t hurt anything, for now. In the future it absolutely will.

PS If you are worried of subnets gaining access to your fog server, use a firewall to block those subnets. I would highly recommend not blocking the specific port for ssh.

@JGeear Seems you still have some merge issues happening on your side.

You could try deleting the ~/fogproject directory and reclone the repository. That should fix any of the merge conflicts you’re seeing.

I think you can even do:

rm -rf ~/fogproject
git clone https://github.com/fogproject/fogproject.git --branch=dev-branch
cd fogproject/bin
./installfog.sh -y

the merge issues on your side are likely from our attempts to fix up the author commits, just so you don’t think I’m blaming you.

It should be fixed by just getting a fresh repository to work with though.

For all watching,

Yes permissions are set in multiple levels and I forgot one element on the FOS side, apparently it was being re-overwritten at the point of the moveUpload which I had missed on the UI side.

This should be adjusted accordingly now as well.

@AUTH-IT-Center I’m not sure I follow the issues? Edit: Well i think I got it now!

Thanks for bring this up.

If you can install the dev-branch of FOG git, this should be corrected as well. No need to update the init’s though not a bad idea either.

@HorizonG I also have another small request if you can:

please copy paste the text? Trying to locate things off an image is a bit … problematic when trying to use other elements to help find things. For example, I want to see if there’s anything I can do for the code error, so I would generally copy the text and paste in google trying to narrow what I’m looking for" but now I am kind of stuck typing and hoping I don’t mistype something lol

My problem I know, but just hoping for a little assist if possible.

If it’s text based (and you have to cat the file anyway, you can copy / paste it here instead of an screenshot/image.)

@HorizonG The snapin that’s attempting to run, does it have a storage group that has an enabled storage node on it?

I’m seeing the error is basically unable to find a master node to try to get the snapin from.

I’m not sure how best to address at this point, just pointing out what I’m seeing based on that error log

@HorizonG Also it seems your FOG Server version isn’t reporting appropriately in the fog client as if you are indeed on 1565, the FOG Client is seeing it as 1.5.10 (not .1565) and that might be playing into things?

I say this as we are not stripping the value on send to the FOG CLient, and from what I can tell of the FOG Client code, it also isn’t doing any stripping either (so it should be reporting the same version.)

This would make sense as to why you’re not seeing logs, potentially as the url I see for your FOG Server is:

https://fogserver.fr

While I do not know if that dns record points to 10.19.0.5, it almost seems not to be?

@HorizonG what OS is FOG running?

The reason I’m asking, is you have an error in the Client log saying 500 internal server error.

This effectively means that 500 error has been written somewhere.

In redhat distributions, this is generally written in /var/www/php-fpm/www-error.log where any httpd errors are written here now: /var/log/http/error_log

In Debian based (ubuntu, etc…) it’s generally written directly in the /var/log/apache2/error.log

I don’t know if this has changed recently though.

@AUTH-IT-Center So the permissions are handled from the FOS side of things, not the FOG side. The NFS bit was to try to ensure a bit more security but it seems this chmod effect was missed on the FOS side.

I have pushed this and am currently building expermental kernel/inits for this. Give it about 1-2 hours and you should be able to see the new inits from FOG Configuration->InitRD Update

If you can download the 64 bit (or 32 if the systems is i386 based) and replace the existing (init.xz or init_32.xz respectively) and give it a test? it should work properly moving forward.

Thank you for letting us know.

@HorizonG what version of fog are you running?

can you provide your fog servers php-fpm www-error logs please

@george1421 That’s true if using the fog installer to handle it.

@michaelkoch1811 There are methods to rebuild the binaries using your own binaries of course.

in the fogproject folder (where you normally run an installer) there’s a file under:
utils/FOGiPXE called buildipxe.sh

if you call this script with your <path/to/your/certificate.pem> it should build the ipxe binaries with your custom certificate.

./buildipxe.sh path/to/your/certificate.pem

By default it will try to use the CA pem we generated for FOG at install.

@JGeear @Fog_Newb We had a couple of author informations that was incorrect and those were updated with removing the old references.

That said, you should be able to just reclone and thing would work fine.

Unsure if there’s a way to reset appropriately:

Something like:

git fetch origin
git reset --hard origin/stable
git reflog expire --expire=now --all
git gc --prune=now

I typically do this on every update

gitBranch='stable'; #or 'dev-branch' or 'working-1.6'
git fetch --all
git reset --hard origin/$gitBranch
#if it's not all good at this point I might add
git checkout $gitBranch
git pull origin $gitBranch

I think the reflog and prune Tom gave here are good too, just wanted to throw in what I’ve always had success with

@theyikes I think you’re severly misunderstanding what FOG does and is.

FOG Doesn’t install Operating systems.

You install the operating system and all software/configuration, whatever. FOG Captures the state of the machine and allows you to deploy that to a fleet of machines.

FOG does not do the installation of an operation system (in the sense it seems you think it does).

@sideone 3007ee9f2 shoudl do that (latest commit.)

@Fog_Newb That’s an interesting fdrive you got there

Not sure how that would work but to your actual question:

Please try:

touch /images/.mntcheck

As that error is indicating that the /images mount (for deploy points) is missing that file.

@sideone So the warnings are just “empty” values it cannot find, which is nothign “bad”

the pdodb error you see is most likely from restarting of services during the install, so again, no big worries there.

Thank you!

So I realized I had attempted to forcibly add the php-pecl-ssh2 /php-ssh2 (where appropriate) but I used the wrong syntax and was inadvertently removing it if it existed.

THis should be fixed.

I’ve also pushed what i think should fix the issue of the base64encoding you’re seeing.

Please give it a try and let me know if its working again? Apologies in advance and thanks for testing.

@sideone I was able to replicate the error 500 updating the node, but because it was missing the php-pecl-ssh2 module. Please install that and you should be able to edit that. I’m attempting to find out how to fix (after validating) the base64decoding issue you’re seeing

@sideone Can you post the error log you’re seeing when you try to edit?

@sideone So 1.6 should be pretty speedy on even pretty (generally) basic specifications.

I use a dual core / 4gb tester laptop (cost $130 lol) for “showing” and simplistic development right now and it runs perfectly fine for the UI loading.

Now, we have heard occasionally people have UI loading slowdowns when they’re suing FOG Client in their environment and the number of machines and check in times are just too frequent for the FOG Server to keep up and respond to all of them.

In those cases, I don’t know if any amount of vertical scaling would help until you add a larger network interface.