Best posts made by Tom Elliott
Ubuntu is FOG's enemy
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.
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 Activity - Status
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.
I'm away, but back?
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.
RE: Release plan for FOG
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.
Latest posts made by Tom Elliott
RE: Mysql groups table corrupted, other table problems ?
So, change your query from:
mysql -u root -p -D fog -e "select * from groups"
mysql -u root -p -D fog -e "select * from `groups`"
mysql has made
groupsa keyword now, so you will need to escape the word when referencing it in the future.
RE: Change FTP on fog server to SFTP??
There’s SFTP which uses ssh ports to transfer files. This would already exist on most Linux servers.
There’s FTPS which works by using certificates.
Which are you trying to do? Vsftp can do ftp and ftps I believe, but don’t think it would do sftp.
Essentially SFTP most likely is already set and configured on your machine. Just use the user and password you would use to logon to the machine and you should be good to go.
RE: Upgrade to master with git
Master branch is on 1.5.9-RC2
To get specifically 1.5.8 you would run:
cd /root/fogproject git checkout tag/1.5.8 -b master cd bin ./installfog.sh -y
I would highly recommend not doing this in your main branch though.
git clone https://github.com/fogproject/fogproject /root/fog-1.5.8 cd /root/fog-1.5.8 git checkout tag/1.5.8 -b master cd bin ./installfog.sh
This way your /root/fogproject folder can be updated easily.
RE: Wakeonlan where ?
I don’t mind giving up the code (it is GPL after all), but is there a particular reason you’re looking for it?
Why I ask? If you’re looking to implement something similar in a separate project, copying FOG’s code probably isn’t going to be very helpful. It can give you an idea of what to do and how to do it, if you understand how to read between the lines in the code.
Is there something in particular you’re needing to change? Again, you can review the code and make changes as you want. (Just search for wake on the html folder for fog –
grep -rl 'wake' /var/www/fog/) If you’re trying to fix a bug, why not report what you found so we may look at it.
Context is always a good thing to give.