https://news.fogproject.org/fog-1-3-5-and-client-0-11-11-officially-released/

https://news.fogproject.org/fog-1-5-0-rc-11/

TLDR; Rerun the fog installer if you have lost “Database Connectivity” to your fog server, or run the ALTER USER syntax shown below.

So Ubuntu 16, among others I suppose, enable a “security updates” to be applied automatically as a “default” to things. Why, well it makes it simpler to ensure your Ubuntu systems are in compliance and patched for any potential exploits. This causes unknown and unexpected issues.

I figured it’d be a safe thing to express that there could be problems (as many of you have already experienced) that when these updates go up (with or without your knowledge) it can break functionality in unexpected and inopportune ways.

The quickest fix is to simply rerun the fog installer which should correct the problem.

As a note, it seems this problem is specific only when the mysql account is the 'root' user AND the password is blank.

The “fix” if you must do it manually is to open a terminal and obtain root:
Super (Windows Key) + T then sudo -i (in most cases).

From there, open mysql with mysql -u root

NOTE: MySQL MUST be run with ROOT.

Run:

ALTER USER 'root'@'127.0.0.1' IDENTIFIED WITH mysql_native_password BY ''; AND
ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY '';

It’s okay if one of them fails. This is going to fix Most people’s issues.

I would highly recommend removing the unattended-upgrades as many of these “sudden” issues came as a security patch ubuntu pushed out. By default Ubuntu typically set’s this for you as enabled and it can cause havoc on you as you (the admin) may not have “done” anything.

To prevent this problem from happening in the future you could run:

apt-get -y remove unattended-upgrades (AS Root again).

FOG is still actively being developed. It’s not necessarily readily apparent, but we can assure you things are still being worked on. These updates may not be communicated in a way that everybody just knows, but can easily be seen if one were to look at our repository site.

Between our own schedules and lives, we can get very busy. We try to keep things updated and help out on the forums even during lull periods. This might mean we aren’t pushing an RC or release as frequently. It may mean we’re working on other things for the project, such as can be seen if looking at our github site.

Our forums are heavily active, and this should point as an indicator to our “status” as well.

If anybody would like to see an increase in developers donating their time to making this free software, consider donating either with monetary support or by spending personal time to help with development.

FOG is an open source project - it’s even in the name. It is driven by people donating their time and resources. The releases of FOG revolve around when developers can spare a few hours throughout the week. Sometimes that will mean releases will be further, sometimes that will mean releases will be faster. That’s just the nature of our project, and many other open source projects.

Hey everybody,

I know you see me here on occasion from time to time. Life decisions have made it more difficult for me to do things I would normally be doing. Rest assured, I am still around, and while I’m not quite as active as I was in the past, it’s not because I don’t want to be.

I had to move, and as part of that I have none of my normal development stuff readily available. Part of the move made me not have a laptop, until today.

I need to setup my dev environment again, so it may take a little bit, but I will be back up.

That’s correct. The main reason fog is constantly moving forward is because the codebase is improved upon. Major bugs tend to be addressed for the next release. We don’t do an LTS because there’s really two main people working on fog in a consistent manor. Those two are @Joe-Schmitt and myself. Debian and Libreoffice have the team too be able to perform such a feat. Their product is Opensource but they have an employment team which can afford them that luxury. FOG has a team but we make no money and as such are required to work full time jobs. We work on FOG in our free time. I’ve had the ability to even work on it from work because we used the software.

Maintaining many different versions is difficult. And we don’t have a support team. WYSIWYG and I think we’ve done pretty well on support, even if we don’t have the ability to do dedicated support for our product. 1.5 was a major step toward modernizing the GUI. 1.6 will vastly improve on this. It was only recently we kind of came up with a road map on how best to proceed. Of note, 1.5 will be maintained until 1.6 is released. 1.6 is focused on making he GUI much more modern. 1.7 will be focused mostly toward fixing and refactoring the FOG client. 1.8 will focus on making the FOS system more modular and usable. I don’t know yet for 1.9. 2.0 will bridge the gap for our rewrite based on the work from 1.5 and up. While we do plan to try to do backports where possible, it’s much easier to ask people to update to the latest version than it is to try to maintain many different versions with backports in mind. At least for what FOG does.

I doubt this will appease anybody, but it’s what I think needs to be said. We are working hard and provide support for our product as best we can. The community makes fogs support system, I think, one of the best around. Add to that and you can almost always have a developer working side by side to help and fix issues as they come up, I don’t think it’s unfair to ask users to update to a specific version. Even if there are bugs, we will always try to correct what we can, when we can. (And normally it’s a pretty quick turn around).

I’m not perfect and I’ll give you that. We don’t even have a test suite to know if things are working as intended. We have to rely on the community and suggestions are great, just understand our answers won’t always be what people want to hear.

https://news.fogproject.org/fog-1-4-0-officially-released/

https://news.fogproject.org/fog-1-4-4-officially-released/

https://news.fogproject.org/fog-1-5-0-rc-12/

https://news.fogproject.org/fog-1-5-3/

@robertkwild yes, it can.

@bruz35 What version of FOG did you install?

Are there 2 network cards on the machine?

Did you IP address change recently?

Is there firewall on the Server machine?

Is there a firewall between the client you’re using to access the UI and the FOG Server?

Was this a fresh install or an existing one?

@mnsk We don’t know what will error when. So if you see “empty response” the process is usually to view the error logs which will lead you in the direction the same way.

I have added some try/catches to the api information but this is in working-1.6 which I still think is not ready for prime time (though it is still functional in most areas).

@mnsk If the mac address already exists, and the host exists, then I would search the GUI for the mac address.

@mnsk Also the “macs” is an array. So you should have:

curl --max-time 30 \
-H "fog-api-token: $FOG_API_TOKEN" \
-H "fog-user-token: $FOG_USER_API_TOKEN" \
-H "Content-Type: application/json" \
-X POST \
-d {"name":"testing", "macs":["2c:94:64:01:70:f4"], "imageID": 3}\
http://$FOG_SERVER/fog/host/create

@mnsk I’m going to make few assumptions here:

$FOG_SERVER is a variable that’s already preset with the FOG Server’s item?
$FOG_API_TOKEN is a variable that’s got the api token as taken from the fog server gui?
$FOG_USER_API_TOKEN is a variable that’s got the api token as taken from the fog server gui under the user?

What’s the error you’re seeing?

I’d remove imagename as this is not needed to be defined for the host to be created. This will be set based on the “imageID” value (3 in your case)

All you should need is the hostname and primary mac address:

https://news.fogproject.org/simplified-api-documentation/

@sebastian-roth I was thinking Catalan was a type of translated like po. Not the language being translated into Catalan. Don’t mind my stupidity

@sebastian-roth I don’t understand.

We use gettext for translation which, as far as I understand, uses po files for generating the translated binaries.

So If catalan can generate the po so we can build the binaries it should work.

@pep The reason we use poedit is PHP is using gettext. So as long as catalan can generate binaries that php gettext can work with, you should be fine.

As for what files should be modified? You will likely want to use one of the existing languages as a template, and convert as necessary for catalan.

That being said, it’s unlikely we are going to incorporate catalan based files. This is because we generate the relevant binaries for language translation at install. This works because we are using a standard method of generating the files to be translated. The return of the translated files are also standard and our binaries can be built properly.

@fmohammed And you ran the steps to rebuild the ipxe binaries?

Based on the permission denied, I am more suspect that the user who owns the file is root:root, which would explain why you’re seeing the permission denied error.

I would suggest by starting to run:

chown -R www-data:www-data /var/www/fog # to ensure even the custom srvpublic.crt and ca.cert.pem are owned by apache2 user for pass on
chown -R www-data:fogproject /var/www/fog/service/ipxe

This will adjust the files so that permissions are back to that of the web user for ubuntu (apache2) and the fog user to allow you to download new kernels.

I don’t know that this will guarantee this will work, but it surely will not hurt.