some global settings being cleared during group settings update

[gwhitfield]

@gwhitfield said in some global settings being cleared during group settings update:

Ubuntu 14.0.4, Trunk SVN 7597 - just updated today

I updated Service Settings for all machines using group update and now all of the service settings for all the machines in the group are blanked out.

The last report of this I see was 11 months ago, has it possibly come back?

An update - seems that if I update Service Settings they stick but when I update Screen Resolution Settings, everything gets blanked out again.

[Tom Elliott]

I’m unable to replicate at all. Anything in the Apache error logs?

[gwhitfield]

@Tom-Elliott I’ve never looked at them so I have to figure that out but I did do an update to SVN 7649 and can say this is still happening on my server. In Group Service Settings, whenever I click the update button for host screen resolution of a group, it clears all the general settings AND sets all screen resolution settings to zero for all machines in the group.

[Wayne Workman]

@gwhitfield said in some global settings being cleared during group settings update:

I’ve never looked at them so I have to figure that out

We need the errors, if any.

[gwhitfield]

@Wayne-Workman I looked in \var\log\apache2\error.log (I hope that’s the right place?) and see the following:

[Mon May 16 14:14:26.269143 2016] [mpm_prefork:notice] [pid 1122] AH00169: caught SIGTERM, shutting down
[Mon May 16 14:15:44.311350 2016] [mpm_prefork:notice] [pid 7074] AH00163: Apache/2.4.20 (Ubuntu) OpenSSL/1.0.2h configured – resuming normal operations
[Mon May 16 14:15:44.311448 2016] [core:notice] [pid 7074] AH00094: Command line: ‘/usr/sbin/apache2’
[Mon May 16 14:15:58.332978 2016] [:error] [pid 7078] [client 192.168.1.53:52076] PHP Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/fog/lib$
[Mon May 16 14:32:47.779094 2016] [mpm_prefork:notice] [pid 7074] AH00169: caught SIGTERM, shutting down
[Mon May 16 14:33:17.005862 2016] [mpm_prefork:notice] [pid 1084] AH00163: Apache/2.4.20 (Ubuntu) OpenSSL/1.0.2h configured – resuming normal operations
[Mon May 16 14:33:17.019303 2016] [core:notice] [pid 1084] AH00094: Command line: ‘/usr/sbin/apache2’
[Mon May 16 15:02:10.146640 2016] [mpm_prefork:notice] [pid 1084] AH00169: caught SIGTERM, shutting down
[Mon May 16 15:02:42.854884 2016] [mpm_prefork:notice] [pid 1100] AH00163: Apache/2.4.20 (Ubuntu) OpenSSL/1.0.2h configured – resuming normal operations
[Mon May 16 15:02:42.856884 2016] [core:notice] [pid 1100] AH00094: Command line: ‘/usr/sbin/apache2’

I did a couple reboots to try to segregate the logs. Hope I’m getting what you’re asking for, I’m not real linux savvy. I did the last test after the last reboot (about 15:05) and doesn’t appear to have logged any problems.

[Wayne Workman]

@gwhitfield So, that’s one place to get them when the interface fails. You can get logs from Web interface -> FOG Configuration -> Log Viewer -> Apache Error Logs We need the errors (if any) that happen immediately after you try to set settings via a group as you’ve described in your OP.

[gwhitfield]

@Wayne-Workman - Here’s exactly what I’m seeing. It is consistent, happens every time I click screen resolution update when there are existing group settings configured. No errors logged in Apache log.

------------ Apache error logs BEFORE updating screen resolution --------
[Mon May 16 15:02:10.146640 2016] [mpm_prefork:notice] [pid 1084] AH00169: caught SIGTERM, shutting down
[Mon May 16 15:02:42.854884 2016] [mpm_prefork:notice] [pid 1100] AH00163: Apache/2.4.20 (Ubuntu) OpenSSL/1.0.2h configured – resuming normal operations
[Mon May 16 15:02:42.856884 2016] [core:notice] [pid 1100] AH00094: Command line: ‘/usr/sbin/apache2’

------------ Screenshot of GROUP settings BEFORE updating screen resolution--------

------------ Screenshot of group MEMBER settings BEFORE updating screen resolution--------

------------ Apache error logs AFTER updating screen resolution (didn’t change at all) --------
[Mon May 16 15:02:10.146640 2016] [mpm_prefork:notice] [pid 1084] AH00169: caught SIGTERM, shutting down
[Mon May 16 15:02:42.854884 2016] [mpm_prefork:notice] [pid 1100] AH00163: Apache/2.4.20 (Ubuntu) OpenSSL/1.0.2h configured – resuming normal operations
[Mon May 16 15:02:42.856884 2016] [core:notice] [pid 1100] AH00094: Command line: ‘/usr/sbin/apache2’

------------ Screenshot of GROUP settings AFTER updating screen resolution --------

------------ Screenshot of group MEMBER after updating GROUP screen resolution --------

[Wayne Workman]

@gwhitfield Good job at documenting the issue. Can you go to MySQL via CLI on the FOG server and run this select command and give us the results? select * from hosts where hostID=0 \G

[gwhitfield]

@Wayne-Workman said in some global settings being cleared during group settings update:

select * from hosts where hostID=0 \G

No idea what I’m doing in MySQL but this is result:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
administrator@PC-FOGSERVER:/$ mysql -u root -p fog
Enter password:
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 101
Server version: 5.5.49-0ubuntu0.14.04.1 (Ubuntu)

Copyright 2000, 2016, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type ‘help;’ or ‘\h’ for help. Type ‘\c’ to clear the current input statement.

mysql> select * from hosts where hostID=0 \G
Empty set (0.00 sec)

mysql>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

[Wayne Workman]

@gwhitfield The output looks good. It was just a shot in the dark. I’m not sure what’s going on with your setup but if this was a bug in fog trunk, we would have many people saying the same thing… we’re not… so this leads me to believe there’s something in your DB that is causing this issue. If you have time, I’d be willing to look around and see if anything stands out via team viewer.

[gwhitfield]

@Wayne-Workman Wow, that’s very nice of you! I would be happy to let you look but I don’t know that it’s necessary for you to go through all that just yet considering I never really update the screen resolution settings. If you feel that it would be beneficial to YOU then I’m all for it but otherwise it’s not necessary for you to do that. I’ll explain -

I’m honestly not sure how I even stumbled on this though I WAS trying to figure out how the settings got cleared and I was clicking and checking everything until I found it. Seeing that I usually don’t touch that setting it was probably an accident that it happened at all. Sure, it’s reproduceable but I guess as long as I keep not touching that setting I shouldn’t have any further problems. The odd thing is that it seems to be a “feature” on each system of mine that I’ve checked, 3 or 4 out of 15. I’m going to check the rest, it may be a few days before I know the results.

Thank you again for your quick responses!!!

[gwhitfield]

@Wayne-Workman One other thought comes to mind. You mentioned possibly something in the DB. I did notice that on a couple recent SVN updates I was not prompted to update/upgrade the DB. Is this normal or should there ALWAYS be a DB update prompt when executing the install of new svn?

[Tom Elliott]

What if you run:

DELETE FROM hostMAC WHERE hmHostID NOT IN (SELECT hostID FROM hosts)

You may also need to delete invalid host entries (without a hostname, or now a hostname without a proper MAC address). To do so, run:

DELETE FROM hosts WHERE hostID NOT IN (SELECT hmHostID FROM hostMAC)

[gwhitfield]

@Tom-Elliott - Since I know zilch about MySQL I can’t talk what-ifs but I take it on faith so I’ll give that a try tomorrow.I’ll send the response as soon as I get a chance to do this step.

[Wayne Workman]

@gwhitfield said in some global settings being cleared during group settings update:

Is this normal or should there ALWAYS be a DB update prompt when executing the install of new svn?

It’s normal.

And Tom might be on to something, that’s the command we came up with way back where there was an issue with hosts disappearing…

[Tom Elliott]

I’ve found the issue as described and it is now fixed in the latest.

[gwhitfield]

@Tom-Elliott @Wayne-Workman - No way!! That was like watching a sweet give-an-go with a slam dunk finish. SCORE!! Can’t wait to try it out, thanks guys!!!

[gwhitfield]

@Tom-Elliott - Tried it out this morning and the general settings stay when host screen resolution is updated in group settings. However, something else is now happening, the AD settings for all group members are being wiped out screenshot below):

Here are Apache error logs:
…
[Tue May 17 08:29:19.953590 2016] [evasive20:error] [pid 5543] [client 192.168.0.112:59972] client denied by server configuration: /var/www/html/fog/service/updates.php
[Tue May 17 08:31:09.092720 2016] [mpm_prefork:notice] [pid 5539] AH00169: caught SIGTERM, shutting down
[Tue May 17 08:31:42.023880 2016] [mpm_prefork:notice] [pid 1080] AH00163: Apache/2.4.20 (Ubuntu) OpenSSL/1.0.2h configured – resuming normal operations
[Tue May 17 08:31:42.038242 2016] [core:notice] [pid 1080] AH00094: Command line: ‘/usr/sbin/apache2’
[Tue May 17 08:38:17.629592 2016] [:error] [pid 1103] [client 192.168.1.251:56181] PHP Warning: Missing argument 4 for Group::setAD(), called in /var/www/html/fog/lib/pages/groupmanagementpage.class.php on line 490 and defined in /var/www/html/fog/lib/fog/group.class.php on line 163, referer: http://192.168.1.53/fog/management/index.php?node=group&sub=edit&id=3
[Tue May 17 08:38:17.629634 2016] [:error] [pid 1103] [client 192.168.1.251:56181] PHP Warning: Missing argument 5 for Group::setAD(), called in /var/www/html/fog/lib/pages/groupmanagementpage.class.php on line 490 and defined in /var/www/html/fog/lib/fog/group.class.php on line 163, referer: http://192.168.1.53/fog/management/index.php?node=group&sub=edit&id=3
[Tue May 17 08:38:17.629644 2016] [:error] [pid 1103] [client 192.168.1.251:56181] PHP Warning: Missing argument 6 for Group::setAD(), called in /var/www/html/fog/lib/pages/groupmanagementpage.class.php on line 490 and defined in /var/www/html/fog/lib/fog/group.class.php on line 163, referer: http://192.168.1.53/fog/management/index.php?node=group&sub=edit&id=3
[Tue May 17 08:38:17.629653 2016] [:error] [pid 1103] [client 192.168.1.251:56181] PHP Warning: Missing argument 7 for Group::setAD(), called in /var/www/html/fog/lib/pages/groupmanagementpage.class.php on line 490 and defined in /var/www/html/fog/lib/fog/group.class.php on line 163, referer: http://192.168.1.53/fog/management/index.php?node=group&sub=edit&id=3
[Tue May 17 08:38:58.572637 2016] [:error] [pid 1102] [client 192.168.1.251:56202] PHP Warning: Missing argument 4 for Group::setAD(), called in /var/www/html/fog/lib/pages/groupmanagementpage.class.php on line 490 and defined in /var/www/html/fog/lib/fog/group.class.php on line 163, referer: http://192.168.1.53/fog/management/index.php?node=group&sub=edit&id=3
[Tue May 17 08:38:58.572683 2016] [:error] [pid 1102] [client 192.168.1.251:56202] PHP Warning: Missing argument 5 for Group::setAD(), called in /var/www/html/fog/lib/pages/groupmanagementpage.class.php on line 490 and defined in /var/www/html/fog/lib/fog/group.class.php on line 163, referer: http://192.168.1.53/fog/management/index.php?node=group&sub=edit&id=3
[Tue May 17 08:38:58.572693 2016] [:error] [pid 1102] [client 192.168.1.251:56202] PHP Warning: Missing argument 6 for Group::setAD(), called in /var/www/html/fog/lib/pages/groupmanagementpage.class.php on line 490 and defined in /var/www/html/fog/lib/fog/group.class.php on line 163, referer: http://192.168.1.53/fog/management/index.php?node=group&sub=edit&id=3
[Tue May 17 08:38:58.572702 2016] [:error] [pid 1102] [client 192.168.1.251:56202] PHP Warning: Missing argument 7 for Group::setAD(), called in /var/www/html/fog/lib/pages/groupmanagementpage.class.php on line 490 and defined in /var/www/html/fog/lib/fog/group.class.php on line 163, referer: http://192.168.1.53/fog/management/index.php?node=group&sub=edit&id=3
…

Edit: For clarity sake, the AD settings are wiped out only when the host screen resolution settings are updated, not when the general settings are updated.

[gwhitfield]

Any ideas on what can be done to correct this new wrinkle?

[Tom Elliott]

@gwhitfield Almost have a fix.