@tom-elliott said in Got Arch/Manjaro install to work:
I don’t know if you purposely deleted, but I will say our community isn’t as harsh as the arch community with questions.
Harsh is an understatement. I will never ask that community another question.
What would people think about a release? It’s been over a year since the last one. There are 248 adopters on version 1.5.9.111
I realize it’s not trivial to put a FOG release together. Perhaps all the steps can be captured to make it easier for others in the future to do it?
After a bit over one full year now, we are at 527 dev installations of fog.
For what it’s worth, I’d be interested in this also. I use nothing but LUKS at home. DD and RAW is slow, would be great for FOG to handle the creation of the needed LVM pieces /w encryption. I’d like to figure it out, but that’s probably a year or more away for me.
We’re at 534 dev installations of FOG that have reported wiithin the last week. We started tracking this about 10 months ago. Coming up on a year of version tracking.
The old and new fog versions do not need to be the same version. The only restriction here is that you cannot downgrade. You can go from older to newer, but not from newer to older.
@rets34 What are the output of the following two commands?
ls -laht /var/www
ls -laht /var/www/html
@matthew-wyneken Are you using the right address for the fog server during installation? Can you do a curl or wget of the certificate using Terminal on the MacOS system?
@jconway1006 Need more information. Fog version, screenshot of the issue. Number of fog clients, FOG Client checkin time, FOG Server hardware specs. Where is the fog server in relation to the node being imaged? What’s the network speed between the fog server and the node being imaged?
@tesparza This should happen automatically. If it’s not, you have some sort of configuration problem. There’s a replication log you can look at in the web UI. Check that for errors.
Also, there’s this article on the location plugin. While this is meant to cover location plugin functionality, it also explains default functionality pretty well. https://wiki.fogproject.org/wiki/index.php?title=Location_Plugin
@jyost Search the forums for snapin order. You’ll find several threads. Here’s one that probably will help:
https://forums.fogproject.org/topic/12784/snapin-order
@stu There’s a wiki article all about passwords: https://wiki.fogproject.org/wiki/index.php?title=Password_Central
Though, if you cannot log in via terminal or SSH, you might could try a Linux password reset boot utility. Use your favorite search engine to search for reset Linux password. Highly advise to backup / create snapshot before trying anything you find.
@stu If you have terminal access, log in, and just type reboot
@brmitmhart have you tried downgrading? Backup your DB first.
@george1421 said in Storage nodes or Master nodes?:
Storage nodes can only send images via unicast images.
What’s the technical reason for this? Just wondering. Like, why can’t it be done? Or, has it simply not been implemented?
@willingmost7 have you rebuilt your fog server? Or, is it possible the client installed in that Windows 7 image is super old? A while back (maybe years), fogproject replaced the certificate & signature in the client.
@makswojciech You might look here at the community contributed powershell modules, they might give you a good direction. https://github.com/FOGProject/fog-community-scripts/tree/master/PowershellModules
Though, sometimes it’s best to go look at the source code. Have a look-see at the files with the word image in their name here: https://github.com/FOGProject/fogproject/tree/master/packages/web/lib/fog
@willingmost7 That’s just one way. There are lots of ways. This is pretty beyond my skill set. Luckily, @george1421 has done an excellent job producing this tutorial about the topic: https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images/8
@omegaxis Because the root cause seems to be identified, I won’t pursue recreating the issue. Ping me directly if you find this to not be true. I’d need to know your Linux system layout & sizes, as well as source HDD size and destination HDD size. I can replicate all this stuff using VMs.