Should be solved in latest as we have re-worked the replication stuff a fair bit.
Posts made by Sebastian Roth
-
RE: storage node sha512sum at 100% CPU/HDD usage
-
RE: Minor display error in fog 1.5.4: progress bar when capturing/deploying
@tian Trying to catch up with older bug reports. Sorry for the late reply.
As we moved to bootstrap this is just how those progress bars look like. Probably not as easy to change.
I am marking this solved - won’t add.
-
RE: Weird Bug Numbers dont work anymore for session name multicast
@bretfred Trying to catch up with bug reports, sorry for the late response. I just tested creating multicast tasks with names like
123
and2
. Creating the task as well as multicasting worked like a charm. Possibly Tom has fixed that already. Marking as solved. -
RE: Product key bug with hostinfo.php in version 1.5.4
@nextechinc Thanks for posting! Sorry we have lost track of this. I just added your suggested change to the
dev-branch
. Will be in the next release. -
RE: 2 questions regarding image capture/creation.
@salted_cashews said in 2 questions regarding image capture/creation.:
If I only have one node does it just ignore the option even if checked then?
Yes, pretty much. Definitely does not use more space on your single node.
-
RE: Tablet with WINDOWS 10 and USB-LAN SMC 7500 adapter
@AndrewG78 said in Tablet with WINDOWS 10 and USB-LAN SMC 7500 adapter:
So, I suspect that the installer only checks if the files exist, but does not check if the checksums match.
So far we don’t do hash sum checking for the binaries archive. I will add that soon as we have that for other binaries being downloaded already and shouldn’t take much effort to add.
-
RE: Site plugin and 1.5
@Aur3l I am wondering if this was ever solved. If this is still an issue with current FOG 1.5.5 I will have a look and try to fix it.
-
RE: Clients PXE booting from another subnet
@jgiovann Ah sorry, just saw that I had miss-read one of your posts. Looking back to the older ones I see that your client seemed to try to connect to http://192.168.0.87/fog//index.php which is the right URL - not the one you posted last…
Now as I think of it it’s probably best you test this URL again and watch the apache access logs. On your FOG server run
tail -f /var/log/apache2/access.log
(debian/ubuntu) ortail -f /var/log/httpd/access_log
(centos/fedora/rhel), hit ENTER twice to see where the last state was and then open http://192.168.0.87/fog//index.php in your browser from the client in the 192.168.2.0/24 network. You probably see the request coming in. Now quickly PXE boot another client that you want to register, choose quick register and keep an eye on the access logs while it boots up. Keep hitting ENTER on the access log and see if you can find the entry that says the client. If you don’t see the client requesting on PXE boot we probably need to see if you have some weird firewall rules blocking only some of the 192.168.2.0/24 clients?! -
RE: Clients PXE booting from another subnet
@jgiovann said in Clients PXE booting from another subnet:
The URL is redirected from http://192.168.0.87//fog//management/index.php to http://192.168.0.87//fog//management/index.php
From what I see the URLs are exactly the same. So how would there be a redirect? Please post again those URLs. We do redirecting in some cases but I can’t think of that causing the issue for you.
Are the double slashes significant in the URL ?
No, should not necessarily be there but we had those in the scripts for a long time and did not seem to cause trouble.I have just had a look at the scripts again and I wonder why it is showing the URL including that “/management/” part. From what I remember that should not be the case. Cannot remember from the top of my head if it’s in the storage node or general fog settings. Think it’s the later. Please check if you have messed with those. Web root is usually just
fog
… -
RE: new ipxe entry
@6rilT @george1421 @jflippen Why not just use the AccesControl plugin as suggested in the other thread? If that is not yet suiting all the needs we might just modify that. It’s all there, why not use it instead of coming up with completely new things?
-
RE: I have installed FOG 1.5.5 on Ubuntu 18.04.1 LTS in windows enviorment .installed as per manual have configured 066 & 067 options in windows server 2012 R2 . issue is clients are not booting via PXE . i am not linux freak kindly help in this regard
@vinodjotshi The topic you linked is good 6 years old and talking about
pxelinux.0
which we don’t use anymore and would be causing an error! Please be so kind and give us more information on what exactly does not work? Have you set your clients to PXE boot in the BIOS?? What do you see on screen? Take a picture or even video of errors or the boot process. -
RE: Click by click upgrade guide?
@deckerta As well you might want to check out this wiki article: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG
It’s all not a click by click thing but I’d say you can learn a lot of things if you are keen to. We’ll definitely help you. Just ask specific questions, post error messages and we sure will be able to guide you the way.
-
RE: Issues during installation on Debian 9.6 stretch
@thegiantcat said in Issues during installation on Debian 9.6 stretch:
is there a way to start the installation and ignore this?
As mentioned earlier, you can simply run the installer like this:
./installfog.sh --exitFail
(actually means “don’t exit on failure”) -
RE: Issues during installation on Debian 9.6 stretch
@thegiantcat said in Issues during installation on Debian 9.6 stretch:
500 Internal Server Error
Please check your
/var/log/php-fpm/www-error.log
! -
RE: Printer Management Level for a group not working
@jflippen said in Printer Management Level for a group not working:
The group printer page still doesn’t reflect the settings applied, but it I go into the members it does seem to have the correct settings.
Be aware of the fact that groups in FOG are not persistent. You can read about this in several forum posts. It’s more or less a tool to apply a value to several hosts.
I just pushed a fix to the
dev-branch
. Will be in the next release. Marking as solved. -
RE: Printer Management Level for a group not working
@jflippen Sorry for taking so long but there were always other issues coming in and I just didn’t get the time to look into the printer stuff in the last weeks.
I can confirm this seems to not work as expected. But I might have found a workaround for you. In the group settings change to “No Printer Management” for example and then click the “Update Default Printer” button further down the page. It’s working for me and I can’t see why it should cause trouble to use this way until we have fixed it.
-
RE: new ipxe entry
@6rilT said in new ipxe entry:
I want to add the possibility to launch a capture from the client, as everyone is supposed to launch a capture from the server, I want to avoid that, so the least amount of people touches the server.
If you let people to a capture from the menu they can do this on purpose to overwrite your image (will be lost then!). I am not sure if that is wise if you worry about those same people using your FOG server.
The next step is to organize the pxe menu so the operations I want to make are available match my needs.
We need more information to help.
-
RE: Hosts drop out of Multicast Session on Partition switch
@Critchleyb said in Hosts drop out of Multicast Session on Partition switch:
I’m assuming 10 means Mins and not Secs
I think it’s 10 seconds! But this time should still be way enough for clients to join the next session, right?! If you think this is an issue. Go to the same file I mentioned earlier and you will find the value 10 in line 641. I forgot to mention that you need to restart the service after changes -
systemctl restart FOGMulticastManager
About the “rmem…” values. Here is an article, not related to UDPcast but pretty much to the point what you are looking for. It talks about setting the value as high as 25 MB (
26214400
) so definitely way higher than what you see as default. Now that I write this I remember that we had this in the forums some time ago: https://forums.fogproject.org/topic/11249/uncompleted-multicastAs well here is an interesting post you wanna read: https://forums.fogproject.org/topic/12252/multicast-deploy-terribly-slow-and-huge-re-xmits-percentage