I am searching from where is called this query and I have seen that it seems an error or a bug.

 <?php
 class UserTrackingManager extends FOGManagerController
 {
     public $tablename = 'dirCleaner';
     public function install()
     {
         $this->uninstall();
         $sql = Schema::createTable(
             $this->tablename,
             true,
             array(
                 'dcID',
                 'dcPath'
             ),
             array(
                 'INTEGER',
                 'LONGTEXT'
             ),
             array(
                 false,
                 false
             ),
             array(
                 false,
                 false
             ),
             array(
                 'dcID',
                 'dcPath'
             ),
             'MyISAM',
             'utf8',
             'dcID',
             'dcID'
         );
         return self::$DB->query($sql);
     }
 }

¿¿tablename= dirCleaner??

Of course I don’t find who does this query XD

Hello @neiliob1973 ,

which version of dnsmasq are you using? Do you use dnsmasq as proxy?

Some info about this problem:

Please enter the TFTP issues with Cisco WS-C2960X-48TS-L
Compiling dnsmasq 2.76 if you need uefi support

@Sebastian-Roth Yes.
I deployed, before update the version 1.5.2 to 1.5.4, without problems one partition using a multicast tasks, but with 1.5.4 doesn’t deploy well.

With unicast d1p3.img --> /dev/sda3
With multicast d1p1.img --> /dev/sda3

Hi,

I have updated the FOG server version recently from 1.5.2 to 1.5.4 and in this version when I try to deploy an only partition image (for example only the second partition) using a multicast task, if I deploy it with an unicast tasks, works fine, the partclone download in /dev/sda2 the d1p1.img file.
Always the d1p1.img, if you want to deploy the 4th partition, parclone download the d1p1.img in /dev/sda4.

FOG version: 1.5.4
Server OS: RHEL 7

@Tom-Elliott Then, in this case, is the FOG client who do this query? The query shows a lot of info, is all necessary? Maybe is possible to put a flag on the service which do the query and make it configurable for webUI?

Do a “SELECT * FROM” query is possibe use a sledgehammer to crack nuts.

@Tom-Elliott I prefer not clean or delete userTracking table. Once my boss asked about it to investigate the bad use of the computers :0 The slow query log shows userTracking queries, but are select queries and not insert queries, who or which process asks about it?

# Time: 181003 16:37:01
# User@Host: root[root] @ localhost []
# Thread_id: 12427592  Schema: fog  QC_hit: No
# Query_time: 83.091067  Lock_time: 0.000094  Rows_sent: 155086  Rows_examined: 536104
SET timestamp=1538577421;
SELECT * FROM `userTracking`  LEFT OUTER JOIN `hosts` ON `hosts`.`hostID`=`userTracking`.`utHostID`  LEFT OUTER JOIN `hostMAC` ON `hostMAC`.`hmHostID`=`hosts`.`hostID`  LEFT OUTER JOIN `images` ON `images`.`imageID`=`hosts`.`hostImage`  LEFT OUTER JOIN `os` ON `os`.`osID`=`images`.`imageOSID`  LEFT OUTER JOIN `imagePartitionTypes` ON `imagePartitionTypes`.`imagePartitionTypeID`=`images`.`imagePartitionTypeID`  LEFT OUTER JOIN `imageTypes` ON `imageTypes`.`imageTypeID`=`images`.`imageTypeID`  LEFT OUTER JOIN `hostScreenSettings` ON `hostScreenSettings`.`hssHostID`=`hosts`.`hostID`  LEFT OUTER JOIN `hostAutoLogOut` ON `hostAutoLogOut`.`haloHostID`=`hosts`.`hostID`  LEFT OUTER JOIN `inventory` ON `inventory`.`iHostID`=`hosts`.`hostID`    WHERE `hostMAC`.`hmPrimary` = '1'  ORDER BY `userTracking`.`utID` ASC;
# Time: 181003 16:46:07
# User@Host: root[root] @ localhost []
# Thread_id: 12448399  Schema: fog  QC_hit: No
# Query_time: 48.331137  Lock_time: 0.000105  Rows_sent: 155135  Rows_examined: 536251
SET timestamp=1538577967;
SELECT * FROM `userTracking`  LEFT OUTER JOIN `hosts` ON `hosts`.`hostID`=`userTracking`.`utHostID`  LEFT OUTER JOIN `hostMAC` ON `hostMAC`.`hmHostID`=`hosts`.`hostID`  LEFT OUTER JOIN `images` ON `images`.`imageID`=`hosts`.`hostImage`  LEFT OUTER JOIN `os` ON `os`.`osID`=`images`.`imageOSID`  LEFT OUTER JOIN `imagePartitionTypes` ON `imagePartitionTypes`.`imagePartitionTypeID`=`images`.`imagePartitionTypeID`  LEFT OUTER JOIN `imageTypes` ON `imageTypes`.`imageTypeID`=`images`.`imageTypeID`  LEFT OUTER JOIN `hostScreenSettings` ON `hostScreenSettings`.`hssHostID`=`hosts`.`hostID`  LEFT OUTER JOIN `hostAutoLogOut` ON `hostAutoLogOut`.`haloHostID`=`hosts`.`hostID`  LEFT OUTER JOIN `inventory` ON `inventory`.`iHostID`=`hosts`.`hostID`    WHERE `hostMAC`.`hmPrimary` = '1'  ORDER BY `userTracking`.`utID` ASC;

@george1421 Hi George,

sorry for my late answer, I was out of the forums these days.

Scenario:
FOG Version: 1.5.4
Server OS: RHEL 7
7000 hosts in the server (we only use one server to manege them). No nodes.
Client checkout time: 275 seconds. We began with 900 seconds and after the update to PHP 7.0, we have been decreasing the chechout time to 275. With this configuration the mysql process uses 140-160% of the CPU.

We are testing the server configuration (cores and RAM) to optimize them. We see that 6 vCores (before we had 8 vCores) are few because the server load is great, we will increase them to 8 vCores. To do this we need shutdown the server and we will take in advantage this to increase the hardware profile from 10 to 13 (I think that is the last one in the Vcenter). This, maybe, can increase a few the performance of the server.

After this we will try to optimize the mysql config.

 >>  MySQLTuner 1.7.10 - Major Hayden <major@mhtx.net>
 >>  Bug reports, feature requests, and downloads at http://mysqltuner.com/
 >>  Run with '--help' for additional options and output filtering

[--] Skipped version check for MySQLTuner script
[OK] Currently running supported MySQL version 5.5.60-MariaDB
[OK] Operating on 64-bit architecture
 
-------- Log file Recommendations ------------------------------------------------------------------
[--] Log file: /var/log/mariadb/mariadb.log(218K)
[OK] Log file /var/log/mariadb/mariadb.log exists
[OK] Log file /var/log/mariadb/mariadb.log is readable.
[OK] Log file /var/log/mariadb/mariadb.log is not empty
[OK] Log file /var/log/mariadb/mariadb.log is smaller than 32 Mb
[!!] /var/log/mariadb/mariadb.log contains 429 warning(s).
[!!] /var/log/mariadb/mariadb.log contains 477 error(s).
[--] 89 start(s) detected in /var/log/mariadb/mariadb.log
[--] 1) 180925 16:48:01 [Note] /usr/libexec/mysqld: ready for connections.
[--] 2) 180920 18:36:46 [Note] /usr/libexec/mysqld: ready for connections.
[--] 3) 180920 18:32:57 [Note] /usr/libexec/mysqld: ready for connections.
[--] 4) 180920 18:32:29 [Note] /usr/libexec/mysqld: ready for connections.
[--] 5) 180919 18:14:02 [Note] /usr/libexec/mysqld: ready for connections.
[--] 6) 180919 18:03:47 [Note] /usr/libexec/mysqld: ready for connections.
[--] 7) 180919 14:11:52 [Note] /usr/libexec/mysqld: ready for connections.
[--] 8) 180918 18:57:39 [Note] /usr/libexec/mysqld: ready for connections.
[--] 9) 180918 18:54:57 [Note] /usr/libexec/mysqld: ready for connections.
[--] 10) 180918  9:18:59 [Note] /usr/libexec/mysqld: ready for connections.
[--] 65 shutdown(s) detected in /var/log/mariadb/mariadb.log
[--] 1) 180925 16:45:39 [Note] /usr/libexec/mysqld: Shutdown complete
[--] 2) 180920 18:35:51 [Note] /usr/libexec/mysqld: Shutdown complete
[--] 3) 180920 18:32:53 [Note] /usr/libexec/mysqld: Shutdown complete
[--] 4) 180920 18:32:25 [Note] /usr/libexec/mysqld: Shutdown complete
[--] 5) 180919 18:12:16 [Note] /usr/libexec/mysqld: Shutdown complete
[--] 6) 180919 18:03:44 [Note] /usr/libexec/mysqld: Shutdown complete
[--] 7) 180918 18:57:17 [Note] /usr/libexec/mysqld: Shutdown complete
[--] 8) 180918 18:54:55 [Note] /usr/libexec/mysqld: Shutdown complete
[--] 9) 180917 19:03:31 [Note] /usr/libexec/mysqld: Shutdown complete
[--] 10) 180907 18:15:30 [Note] /usr/libexec/mysqld: Shutdown complete
 
-------- Storage Engine Statistics -----------------------------------------------------------------
[--] Status: +ARCHIVE +Aria +BLACKHOLE +CSV +FEDERATED +InnoDB +MEMORY +MRG_MYISAM +MyISAM +PERFORMANCE_SCHEMA 
[--] Data in MyISAM tables: 56.9M (Tables: 67)
[--] Data in InnoDB tables: 26.8M (Tables: 7)
[OK] Total fragmented tables: 0
 
 
-------- CVE Security Recommendations --------------------------------------------------------------
[OK] NO SECURITY CVE FOUND FOR YOUR VERSION
 
-------- Performance Metrics -----------------------------------------------------------------------
[--] Up for: 7d 23h 44m 8s (373M q [541.025 qps], 12M conn, TX: 626G, RX: 83G)
[--] Reads / Writes: 99% / 1%
[--] Binary logging is disabled
[--] Physical Memory     : 15.5G
[--] Max MySQL memory    : 972.2M
[--] Other process memory: 8.2G
[--] Total buffers: 416.0M global + 2.8M per thread (200 max threads)
[--] P_S Max memory usage: 0B
[--] Galera GCache Max memory usage: 0B
[OK] Maximum reached memory usage: 644.1M (4.05% of installed RAM)
[OK] Maximum possible memory usage: 972.2M (6.12% of installed RAM)
[OK] Overall possible memory usage with other process is compatible with memory available
[OK] Slow queries: 0% (398/373M)
[OK] Highest usage of available connections: 41% (82/200)
[OK] Aborted connections: 0.00%  (1/12420260)
[!!] name resolution is active : a reverse name resolution is made for each new connection and can reduce performance
[!!] Query cache may be disabled by default due to mutex contention.
[!!] Query cache efficiency: 0.0% (0 cached / 334M selects)
[OK] Query cache prunes per day: 0
[OK] Sorts requiring temporary tables: 0% (1K temp sorts / 97M sorts)
[OK] No joins without indexes
[!!] Temporary tables created on disk: 67% (7M on disk / 10M total)
[!!] Thread cache is disabled
[!!] Table cache hit rate: 1% (400 open / 20K opened)
[OK] Open file limit used: 44% (455/1K)
[OK] Table locks acquired immediately: 99% (614M immediate / 617M locks)
 
-------- Performance schema ------------------------------------------------------------------------
[--] Performance schema is disabled.
[--] Memory used by P_S: 0B
[--] Sys schema isn't installed.
 
-------- ThreadPool Metrics ------------------------------------------------------------------------
[--] ThreadPool stat is enabled.
[--] Thread Pool Size: 6 thread(s).
[--] Using default value is good enough for your version (5.5.60-MariaDB)
 
-------- MyISAM Metrics ----------------------------------------------------------------------------
[!!] Key buffer used: 24.6% (33M used / 134M cache)
[OK] Key buffer size / total MyISAM indexes: 128.0M/26.9M
[OK] Read Key buffer hit rate: 100.0% (5B cached / 45K reads)
[!!] Write Key buffer hit rate: 4.5% (13M cached / 615K writes)
 
-------- InnoDB Metrics ----------------------------------------------------------------------------
[--] InnoDB is enabled.
[--] InnoDB Thread Concurrency: 0
[!!] InnoDB File per table is not activated
[OK] InnoDB buffer pool / data size: 128.0M/26.8M
[!!] Ratio InnoDB log file size / InnoDB Buffer pool size (7.8125 %): 5.0M * 2/128.0M should be equal 25%
[OK] InnoDB buffer pool instances: 1
[--] InnoDB Buffer Pool Chunk Size not used or defined in your version
[OK] InnoDB Read buffer efficiency: 100.00% (1698149490 hits/ 1698149871 total)
[OK] InnoDB Write log efficiency: 99.83% (41391992 hits/ 41460907 total)
[OK] InnoDB log waits: 0.00% (0 waits / 68915 writes)
 
-------- AriaDB Metrics ----------------------------------------------------------------------------
[--] AriaDB is enabled.
[OK] Aria pagecache size / total Aria indexes: 128.0M/1B
[!!] Aria pagecache hit rate: 84.7% (167M cached / 25M reads)
 
-------- TokuDB Metrics ----------------------------------------------------------------------------
[--] TokuDB is disabled.
 
-------- XtraDB Metrics ----------------------------------------------------------------------------
[--] XtraDB is disabled.
 
-------- RocksDB Metrics ---------------------------------------------------------------------------
[--] RocksDB is disabled.
 
-------- Spider Metrics ----------------------------------------------------------------------------
[--] Spider is disabled.
 
-------- Connect Metrics ---------------------------------------------------------------------------
[--] Connect is disabled.
 
-------- Galera Metrics ----------------------------------------------------------------------------
[--] Galera is disabled.
 
-------- Replication Metrics -----------------------------------------------------------------------
[--] Galera Synchronous replication: NO
[--] No replication slave(s) for this server.
[--] Binlog format: STATEMENT
[--] XA support enabled: ON
[--] Semi synchronous replication Master: Not Activated
[--] Semi synchronous replication Slave: Not Activated
[--] This is a standalone server
 
-------- Recommendations ---------------------------------------------------------------------------
General recommendations:
    Control warning line(s) into /var/log/mariadb/mariadb.log file
    Control error line(s) into /var/log/mariadb/mariadb.log file
    Configure your accounts with ip or subnets only, then update your configuration with skip-name-resolve=1
    When making adjustments, make tmp_table_size/max_heap_table_size equal
    Reduce your SELECT DISTINCT queries which have no LIMIT clause
    Set thread_cache_size to 4 as a starting value
    Increase table_open_cache gradually to avoid file descriptor limits
    Read this before increasing table_open_cache over 64: http://bit.ly/1mi7c4C
    This is MyISAM only table_cache scalability problem, InnoDB not affected.
    See more details here: https://bugs.mysql.com/bug.php?id=49177
    This bug already fixed in MySQL 5.7.9 and newer MySQL versions.
    Beware that open_files_limit (1024) variable 
    should be greater than table_open_cache (400)
    Consider installing Sys schema from https://github.com/mysql/mysql-sys
    Before changing innodb_log_file_size and/or innodb_log_files_in_group read this: http://bit.ly/2wgkDvS
Variables to adjust:
    query_cache_size (=0)
    query_cache_type (=0)
    query_cache_limit (> 1M, or use smaller result sets)
    tmp_table_size (> 16M)
    max_heap_table_size (> 16M)
    thread_cache_size (start at 4)
    table_open_cache (> 400)
    innodb_file_per_table=ON
    innodb_log_file_size should be (=16M) if possible, so InnoDB total log files size equals to 25% of buffer pool size.

Works fine adding the remi-php70 repository! Please close the ticket

Well, I have tested the installer og FOG 1.5.4 and works fine but first you need something.

Add the remi-php70 repository
rpm -Uvh http://rpms.remirepo.net/enterprise/remi-release-7.rpm (I had installed it)
yum-config-manager --enable remi-php70
yum -y update

The last command update the php70 to the remi-php70 version (in my case php 7.0.32) and desinstalled the php70w version (I installed the php 7.0 version from webtonic repository)

I run the installer and works fine. I will test it again in the production server, if it is success, please, close the ticket

Hi,

My FOG 1.5.2 server had php 5.6 version installed and after upgrade the php version to 7.0 and mariadb to 5.5.60, the performance is better, super better XD.

The consume of mysql had decrease a lot of and the RAM memory too.

I use redHat7, more info about this in:
Is FOG installer ready to install php70 under RedHat 7
Installation - Centos 7 & PHP 7?
PHP 7.0.0 finally Released