Bugs in latest FOG Trunk 5360
-
Hi @george1421,
- Yes this FOG server is behind a proxy. I actually added http_proxy & https_proxy settings in /etc/wgetrc thinking it would resolve it but I guess not?
- I’m guessing you mean, has the FOG server worked prior? Yes. I did upgrade it from 1.2.0 to trunk 3590. So was now looking to upgrade it to the latest version. Apologies if you meant something else.
Hi Tom,
Thanks for the quick response.Thanks for clarifying about the multiple spawned services.
Apologies I should have known better and to have checked the Apache error log. This is the error log from apache…
[Tue Nov 17 21:09:59 2015] [error] [client 192.168.23.35] PHP Fatal error: Uncaught exception ‘Exception’ with message ‘FOGFTP: Login failed. Host: 192.168.23.176, Username: fog, Password: ******, Error: ftp_login(): Login incorrect.’ in /var/www/html/fog/lib/fog/FOGFTP.class.php:29\nStack trace:\n#0 /var/www/html/fog/lib/pages/FOGConfigurationPage.class.php(625): FOGFTP->connect()\n#1 [internal function]: FOGConfigurationPage->log()\n#2 /var/www/html/fog/lib/fog/FOGPageManager.class.php(67): call_user_func(Array)\n#3 /var/www/html/fog/management/index.php(24): FOGPageManager->render()\n#4 {main}\n thrown in /var/www/html/fog/lib/fog/FOGFTP.class.php on line 29, referer: http://192.168.23.176/fog/management/index.php?node=about
Note: I masqueraded the password with ******
So I’m guessing from the error above, it is because the FTP credentials are incorrect on the test server that I created?
Thanks for resolving the reported bugs so quickly and again, my apologies for not performing my own self checks with the http errors I was getting. Not quite sure why the display is like that in my Win7 IE11. I’ve even launched IE with no-addons and the page is still displayed same. It’s no big deal really because it is fine with Chrome & Firefox. I just thought I would mention it just in case.
I’ll update to the latest trunk now and give it another go. Thanks again!
-
@Toby777 This is probably helpful to you: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP
-
@Sebastian-Roth
Thanks for that. I will run though that wiki. -
There are a few things that you might do to clear this up (proxy server related). I run FOG on centos 6.7 behind a proxy server and this is what I needed to do.
In the bashrc file I placed the following commands.
export http_proxy=http://192.168.1.10:3128
export https_proxy=http://192.168.1.10:3128
export ftp_proxy=http://192.168.1.10:3128
export no_proxy=“192.168.1.88”In your wgetrc you can have the proxy settings too. The key is the no_proxy variable. That needs to be set to the IP address of the FOG server. Once these are set log out and back in. These new env variables will be set. From there FOG will install and backup correctly. If you look at the code for the backup, the script uses wget to pull the backup image. Well, wget isn’t that smart. Its trying to contact the proxy server instead of just connecting locally. The no_proxy statement tells wget to not proxy any requests for the FOG server.
As for the second question, that to find out if this was a new install that never worked, or a working install that broke after the upgrade.
-
Thanks for that @george1421.
I have added those entries though it kinda looks like Tom may have removed the Backing up of the database from the installer?
My FOG server has been a working fog server for about a year or so without any problem. It was originally set up on 0.32, then saw an upgrade to 1.2.0, then to a trunk version (32??). Unfortunately, I can’t remember what trunk version it was running at the time prior to upgrading it recently.
The only reason I thought to upgrade it was when I had installed a Storage Node (in another city) last week. The SN was running 1.2.0 and at the time, the images were being replicated to the SN without issue. When I then upgraded the SN to the latest trunk at that time, it seemed to have broken replication because any updated images would no longer transfer through to the SN. It even wasn’t showing up on the logs.
-
@Toby777 I think issues of replication were brought on by the way replication occurs now, compared to before.
Replication in 1.2.0 and earlier was only done Master Node to Other nodes in the same group. Images could only be assigned to one group.
For trunk, you can now assign images to multiple groups which will allow the image to replicate across groups as well as master->node replication.
It uses totally different methods for replicating and managing groups which was likely the reason you were seeing problems to begin with.
-
@Tom-Elliott
Hi Tom…
Have confirmed that all those items I mentioned have been resolved. (except for the IE view issue but that’s no big deal ;)) Thanks again!
I will try updating my production fog server to the latest trunk and test out image replication to the SN and imaging hosts and let you know how it all goes. -
Actually sorry, I lie… It looks like the Plugins icon has disappeared from the row of icons. I look in FOG Settings and it isn’t enabled. When I tick the box to enable Plugins and click Save, it doesn’t get enabled and the checbox is still clear, even though it says ‘Settings successfully stored’.
My previously activated Location plugin is still loaded and appears as an icon.
EDIT: Looks like it applies to all the checkboxes in the FOG Settings page.
I noticed a few were no longer checked , even though they were previously. When I try to check the boxes and click Save, the setting appears to not be saved even though it says it is saved.
-
@Toby777 Fixed this issue, I had a missing bracket in the line. I’d recommend, as you updated settings, using one of the db backups from /home/fogDBbackups please revert so your old settings are back in place. Then this should be fixed for you as well.
-
@Tom-Elliott
ok cool… thanks again Tom… will do.
FOG Settings page is all good. Plugins also.
-
I’ve marked this as solved and I hope it is. Please let me know if there’s still any issues. At least this one got a bunch of bugs involved and corrected.
-
Hi @Tom-Elliott
Yup all good to close this one as resolved.
Thanks for your awesome work!
