General

• J

  [HELP WANTED] Client Internationalization
  • Joe Schmitt  

  47
  2
  Votes
  47
  Posts
  9748
  Views

  S

  @Valer Thanks! I just added your translations to the client. We hope to be able to release a new fog-client version in the next weeks.
• J

  Firewall Configuration
  • Joe Schmitt  

  24
  2
  Votes
  24
  Posts
  13130
  Views

  

  the firewalld configuration no longer works on Fedora 21. The commands succeed, but at least http is blocked still.
• J

  SELinux Policy
  • Joe Schmitt  

  19
  2
  Votes
  19
  Posts
  14949
  Views

  

  Bumping this - it would be so nice to have SELinux enabled as a standard configuration.
• C

  FOG Status
  • Chuck Syperski  

  59
  0
  Votes
  59
  Posts
  33809
  Views

  

  Nope it’s still heavily in the beta phase, I bet when we do have an idea we will post it on the forums or on the main site letting everyone know we are close. There is a thread you are more than welcome to monitor it can be located here ->[url]http://fogproject.org/forum/threads/latest-fog-0-33b.6476/[/url]
• S

  LDAP Plugin install
  • stuhad  

  22
  0
  Votes
  22
  Posts
  90
  Views

  S

  @Sebastian-Roth said in LDAP Plugin install: Did you see Tom’s post? There seemed to be an issue in the version check script on our webserver which led to it saying you are “up to date” eventhough you are running the years old 1.5.5 version. Tom fixed it. You can always be sure the version number in the bottom right corner is the one you have. Hey sorry about the confusion I did see his comment, but clearly did not understand. It’s a huge relief that we aren’t dealing with a failed upgrade. Thanks for all your help with this everyone, I have finally got the plugin working. As @Kiweegie suggested early on the password complexity seemed to be the issue. I had made sure there was no special characters in it, but I had made the password obscenely long. Changing it < 24 characters seems to have done the trick. Apologies for all the confusion and thanks again for all the help.
• 

  Fog Installer - Distro check
  • Wayne Workman  

  104
  3
  Votes
  104
  Posts
  14707
  Views

  

  I’ve removed Arch Linux from the automated tests due to complications within Terraform. These issues were sort of the final straw in my Arch testing efforts. The Arch community doesn’t supply an official AWS AMI. I had been relying on a privately built AMI that isn’t 1:1 with a manual Arch installation. For perhaps the last half year, my Arch tests were failing but the installer worked if you tested it against a manually setup Arch installation. This can only be due to differences between the AMI I was using and a manual installation. The Arch community is vehement about only providing help if you follow their installation instructions on their wiki exactly. Because of this, when I asked for some help sorting out the issues, they were not willing to help. Until someone with some Arch prowess can put some time into helping with this, Arch Linux will not be included in the automated tests.
• S

  Installing FOG on Centos
  • sascha735  

  6
  0
  Votes
  6
  Posts
  48
  Views

  

  @sascha735 If you installed FOG using the git method, switch to the dev branch and reinstall fog. That will put you on a prerelease version of 1.5.8 that does support Centos 8 and Debian 10.2 (I think). cd /root/fogproject git checkout dev-branch git pull cd bin ./installfog.sh That should put you on version 1.5.7.85 (or later) When FOG 1.5.8 is released (should be some time later this month) you will then need to do the following to switch back to the master branch. cd /root/fogproject git checkout master git pull cd bin ./installfog.sh
• 

  Does branch 1.6 not use the 0.11.17 client?
  • falko  

  3
  0
  Votes
  3
  Posts
  40
  Views

  

  @Tom-Elliott ok, no worries
• S

  Database security
  • Sebastian Roth  

  22
  1
  Votes
  22
  Posts
  273
  Views

  S

  Finally merged all the work into dev-branch. Done.
• T

  Possible Bug- GUIWatcher Windows 7
  • tiengdung90  

  3
  0
  Votes
  3
  Posts
  46
  Views

  

  @Sebastian-Roth if my memory serves correctly, GUI watcher was a part of the now very old client
• 

  CentOS 8
  • Wayne Workman  

  6
  0
  Votes
  6
  Posts
  134
  Views

  S

  @Quazz Not sure from the top of my head. Thanks for finding this!! I will take a look later on.
• I

  Thanks to the developers
  • ismith.hpu  

  2
  2
  Votes
  2
  Posts
  46
  Views

  S

  @ismith-hpu Don’t feel like you have to but you are welcome to post here as well: https://forums.fogproject.org/topic/4382/organizations-using-fog Thanks for your post, appreciate that!
• I

  Mac OSX renaming of Hostname & ComputerName post imaging
  • ismith.hpu  

  8
  0
  Votes
  8
  Posts
  73
  Views

  S

  @ismith-hpu said in Mac OSX renaming of Hostname & ComputerName post imaging: FOG Server CA NOT found in keystore You need to make sure you install and run the fog-client in the root context.
• M

  API updated?
  • maikBat  

  4
  0
  Votes
  4
  Posts
  70
  Views

  S

  @maikBat said in API updated?: I have updates from 2017 What do you mean by that??? Which version of FOG do you use?
• 

  FOG Client Last Check-in Report
  • fry_p  

  7
  0
  Votes
  7
  Posts
  97
  Views

  

  @fry_p Maybe too late, but in addition to complete a few: You can configure the fog client to delayed-auto and to reboot the service on each error with the commands below recommended before start it: sc.exe config FOGService start=delayed-auto sc.exe failure FOGService actions= restart/60000/restart/60000/restart/ reset= 120.
• A

  LDAP plugin - apache2/error.log - password in plaintext
  • antonionardella  

  6
  0
  Votes
  6
  Posts
  106
  Views

  S

  @antonionardella You are right this is not good that it prints the full credentials in the logs. But the error you have is caused by the php-ldap module not being installed I guess. That shouldn’t happen at all if you don’t mess with the FOG setup. I am not sure we can prevent if from showing this in the logs…
• 

  Arch install issue 06-29-2019
  • Wayne Workman  

  1
  2
  Votes
  1
  Posts
  46
  Views

  No one has replied

• M

  SOLVED PXE Boot could not boot
  • maikBat  

  3
  0
  Votes
  3
  Posts
  63
  Views

  M

  Today I learned that when adding a new item to PXE menu “Menu Item” cannot have spaces. Instead type “New Item” you should type “NewItem”. When I checked the PXE config file using the link was kind of evident that this was the problem and in effect it was. Thanks for the help
• M

  FOG install overwrites /etc/exports with no warning
  • mechalas  

  14
  0
  Votes
  14
  Posts
  145
  Views

  

  @Wayne-Workman said in FOG install overwrites /etc/exports with no warning: In what scenarios do you see having two? If you were to install fog side by side with another product that supports nfs. What is the likelihood of two installs creating an entry with fsid of 0 or 1? We see that issue today when someone wants to create a second nfs share on the fog server and clones what is currently there but updates the paths only.
• 

  New Plugin: Host Status plugin (1.5.6 FOG version)
  • Fernando Gietz  

  14
  4
  Votes
  14
  Posts
  275
  Views

  

  @fry_p You can change both, line 110 and 114. If all works fine, when you are in FOS, must return 111 code. If you are under windows, must return 0. which value return when you are under windows? 0 or 6? If the value is 6, which OS are you using (Windows 7,8,10)? Another oddity is that the built in host pinging on the host list page is working properly and even detecting these are windows clients. The hostStatus plugin uses the same code that FOGHostPing daemon, if the daemon detects fine the status, there is something that doesn´t work correctly. You have 1500 hosts, the daemon launchs one ping per second then the status is updated every 25 minutes, in your case the status info is not very reliable. In my opinion is better disable this daemon.