@Tom-Elliott - In looking at the error file again; I don’t see any more errors logged since the system booted this morning at 6:17. Perhaps clients were checking in after apache had been initialized, but before the mysql server was running, resulting in the errors? I hadn’t seen them in the logs before, but our FOG server has been running months at a time without rebooting, until the memory issue I was having with php caused me to look at mysql. So, now I’m not sure if there actually is an issue, since things are working as advertised.

Thanks for your continued support and for clarifying the account used for mysql - I really do love this product!

Cheers,
Dave.

@Tom-Elliott said in MySQL errors in apache error log file with 1.2.0:

@Dave-Wolf Storage Node Management User and Password are for FTP, not for MySQL.

I see that now, I just opened up the Config.class.php file and saw that it uses my root account and password.

I also checked the mysqld.sock file in the /var/run/mysqld directory and it’s there, with a 0 byte size and a modification date of this morning when I rebooted the server. The PID of the mysql process is in the mysqld.pid file in that same directory and the mysql process is running with that PID.

I am able to login to mysql with my root account and password. Is there a command I can run, other than ‘status’ to see if things are operational?

Thanks,
Dave.

@Tom-Elliott said in MySQL errors in apache error log file with 1.2.0:

What did you do to try to “fix” unrelated issues? If you were playing with mysql configuration settings, did you change where the .sock file is located? Maybe you updated the OS and that changed where the .sock file is generated?

We need the details to help you more accurately. Why I ask about the sock files is due to the first error you see (Can’t connect to local MySQL server through socket…)

Hi Tom,

I didn’t actually change any MyQSL settings, I thought my original problem was related to MySQL, so I was stepping through the MySQL troubleshooting steps trying to login with the fogstorage account. I couldn’t for some reason (access denied) so I changed the password, updated it in the Storage Nodes section, and began noticing the errors in the log. I thought the socket error was possibly due to failing credentials. I didn’t reinstall or update the OS during my troubleshooting, I just changed the fogstorage password. I have since changed it back to the original password, which was ‘fs9408241485’ and updated it in the Storage Nodes section of the configuration. Is this a hashed password? Is the hashed password stored in the configuration page? So maybe I need to hash it and change it in the mysql command prompt?

Thanks for the help!

Cheers,
Dave.

Server

• FOG Version: 1.2.0 (installed about 2 years ago, no updates)
• OS: Debian 7.6

Client

• Service Version: 0.1
• OS: Windows Server 2012 R2/Windows 7 Pro/Windows 10 Pro

Description

In the process of trying to fix an unrelated issue, I seem to have caused a problem with the FOG Client. Every time it checks in to the server I get these errors in the apache error log file below (all clients cause this error to be logged to the file). Looking through the MySQL troubleshooting wiki, I am able to connect with the following command:

mysql -u fogstorage -p***** -D fog

The fogstorage username and password are the ones in the FOG Storage Nodes section of the FOG System Settings section in the FOG Configuration page. My clients are able to up/download and they reboot when a job is pending. I just would like to fix this issue since I don’t know what the ramifications are. Any ideas?

[Wed Oct 05 06:17:47 2016] [error] [client 10.30.0.147] PHP Warning: mysqli::mysqli(): (HY000/2002): Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2) in /var/www/fog/lib/db/MySQL.class.php on line 64
[Wed Oct 05 06:17:47 2016] [error] [client 10.30.0.147] PHP Warning: mysqli::select_db(): Couldn’t fetch mysqli in /var/www/fog/lib/db/MySQL.class.php on line 165
[Wed Oct 05 06:17:47 2016] [error] [client 10.30.0.147] PHP Warning: mysqli::query(): Couldn’t fetch mysqli in /var/www/fog/lib/db/MySQL.class.php on line 89
.
.
.

Thanks,
Dave.

@Wayne-Workman said in Error 500 while trying to display Imaging Log:

@Dave-Wolf said in Error 500 while trying to display Imaging Log:

but if I try to use this name and password to access the mySQL database, it fails to login.

How are you trying to use it? Give us the command, replace the password with something else but ensure the structure of the command is the same.

@Dave-Wolf said in Error 500 while trying to display Imaging Log:

What should the FOG_STORAGE_MYSQLUSER actually be in the web config page?

It should be fogstorage

I initially thought that my report display problem was an issue with the SQL database, so I was following the “Testing MySQL” section of the “Troubleshooting MySQL” section of the wiki. I was using the following command:

mysql -u fogstorage -p****** -D fog

and I was getting an “access denied” message, though I just checked that again now and it is working fine. So I’m not sure what was wrong, maybe it was just Friday after a long week…

In any case, thank you so much again for your responses to help me resolve the imaging report issue.

Cheers,
Dave.

@Wayne-Workman Thanks! That change worked and got me to the date range selection page. If I select 2016-10-01 for the date range (both start and end), the report executes (after a looong time, maybe a minute or more) and shows me the imaging jobs for that date. Is there a way to clear out old entries to speed up the report? If not, no problem, I’m just glad I could get it to run again! I really appreciate the help, thanks again!

Cheers,
Dave.

Hi Tom,

Some more info; my FOG_STORAGENODE_MYSQLUSER is set to fogstorage with a long password, but if I try to use this name and password to access the mySQL database, it fails to login. I can login to the database with my root user and password. What should the FOG_STORAGE_MYSQLUSER actually be in the web config page?

Thanks,
Dave.

Hi Tom!

Hmmm, I don’t have an entry for FOG_MEMORY_LIMIT under General Settings on my 1.2.0 install (which has been running for a couple of years).

Thanks,
Dave.

Server

• FOG Version: 1.2.0
• OS: Debian 7.6

Client

• Service Version:
• OS:

Description

In the process of trying to add storage to my existing Fog server, I seemed to have corrupted something in the database. I can upload/download images just fine, but trying to display the imaging log returns an error 500. Attached is the error.log file from /var/log/apache2. It seemed to break when I did an installation of FOG on another system as a storage node for my main FOG server. I had an issue with the second system, so I deleted the storage node and went back to just the default.

A note about the error.log file. I’ve trimmed it to remove entries that occur when our Nessus vulnerability scanner hits the webserver, the errors in the log are from when I try to view the imaging log and it looks like there’s an issue when the FOG clients check in. Looks like my MySQL server is not accessible for some reason?

Any help you can provide would be greatly appreciated!

Thanks,
Dave.

For some reason, I couldn’t upload the file (no permissions), so here it is:

[Fri Sep 30 06:12:17 2016] [error] [client 10.30.0.88] PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 5 bytes) in /var/www/fog/lib/fog/FOGController.class.php on line 58, referer: http://fogserver/fog/management/index.php?node=report
[Fri Sep 30 06:12:20 2016] [error] [client 10.30.0.88] PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 9 bytes) in /var/www/fog/lib/fog/FOGController.class.php on line 66
[Fri Sep 30 06:16:33 2016] [error] [client 10.30.0.88] File does not exist: /var/www/fog/management/css/images/ui-bg_glass_75_e6e6e6_1x400.png, referer: http://fogserver/fog/management/css/jquery-ui.css
[Fri Sep 30 06:16:33 2016] [error] [client 10.30.0.88] File does not exist: /var/www/fog/management/css/images/ui-bg_highlight-soft_75_cccccc_1x100.png, referer: http://fogserver/fog/management/css/jquery-ui.css
[Fri Sep 30 06:16:33 2016] [error] [client 10.30.0.88] File does not exist: /var/www/fog/management/css/images/ui-bg_flat_75_ffffff_40x100.png, referer: http://fogserver/fog/management/css/jquery-ui.css
[Fri Sep 30 06:18:16 2016] [error] [client 10.30.0.88] PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 5 bytes) in /var/www/fog/lib/fog/FOGController.class.php on line 58, referer: http://fogserver/fog/management/index.php?node=report
[Fri Sep 30 06:19:25 2016] [error] [client 10.30.0.88] PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 16384 bytes) in /var/www/fog/lib/pages/ReportManagementPage.class.php on line 684, referer: http://fogserver/fog/management/index.php?node=report
[Fri Sep 30 06:21:02 2016] [error] [client 10.30.0.88] PHP Warning:  array_merge(): Argument #1 is not an array in /var/www/fog/lib/pages/ReportManagementPage.class.php on line 966, referer: http://fogserver/fog/management/index.php?node=report&sub=pend-mac
[Fri Sep 30 06:21:07 2016] [error] [client 10.30.0.88] PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /var/www/fog/lib/pages/ReportManagementPage.class.php on line 684, referer: http://fogserver/fog/management/index.php?node=report&sub=snapin-log
[Fri Sep 30 06:21:11 2016] [error] [client 10.30.0.88] PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 9 bytes) in /var/www/fog/lib/fog/FOGController.class.php on line 66, referer: http://fogserver/fog/management/index.php?node=report&sub=snapin-log
[Fri Sep 30 06:47:59 2016] [error] [client 10.30.0.125] PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /var/www/fog/lib/fog/FOGBase.class.php on line 53, referer: http://10.30.0.125/fog/management/index.php?node=report
[Fri Sep 30 06:48:12 2016] [error] [client 10.30.0.125] PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /var/www/fog/lib/pages/ReportManagementPage.class.php on line 684, referer: http://10.30.0.125/fog/management/index.php?node=report
[Fri Sep 30 06:54:01 2016] [notice] caught SIGTERM, shutting down
[Fri Sep 30 06:54:32 2016] [notice] Apache/2.2.22 (Debian) PHP/5.4.4-14+deb7u14 configured -- resuming normal operations
[Fri Sep 30 06:54:33 2016] [error] [client 10.30.3.184] PHP Warning:  mysqli::mysqli(): (HY000/2002): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) in /var/www/fog/lib/db/MySQL.class.php on line 64
[Fri Sep 30 06:54:33 2016] [error] [client 10.30.3.184] PHP Warning:  mysqli::select_db(): Couldn't fetch mysqli in /var/www/fog/lib/db/MySQL.class.php on line 165
[Fri Sep 30 06:54:33 2016] [error] [client 10.30.3.184] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /var/www/fog/lib/db/MySQL.class.php on line 89
[Fri Sep 30 06:54:33 2016] [error] [client 10.30.3.184] PHP Warning:  MySQL::sqlerror(): Couldn't fetch mysqli in /var/www/fog/lib/db/MySQL.class.php on line 180
[Fri Sep 30 06:54:33 2016] [error] [client 10.30.3.184] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in /var/www/fog/lib/db/MySQL.class.php on line 150
[Fri Sep 30 06:54:33 2016] [error] [client 10.30.3.184] PHP Warning:  mysqli::mysqli(): (HY000/2002): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) in /var/www/fog/lib/db/MySQL.class.php on line 64
[Fri Sep 30 06:54:33 2016] [error] [client 10.30.3.184] PHP Warning:  mysqli::select_db(): Couldn't fetch mysqli in /var/www/fog/lib/db/MySQL.class.php on line 165
[Fri Sep 30 06:54:33 2016] [error] [client 10.30.3.184] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /var/www/fog/lib/db/MySQL.class.php on line 89
[Fri Sep 30 06:54:33 2016] [error] [client 10.30.3.184] PHP Warning:  MySQL::sqlerror(): Couldn't fetch mysqli in /var/www/fog/lib/db/MySQL.class.php on line 180
[Fri Sep 30 06:54:33 2016] [error] [client 10.30.3.184] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in /var/www/fog/lib/db/MySQL.class.php on line 150

[Fri Sep 30 06:55:38 2016] [error] [client 10.30.0.88] PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /var/www/fog/lib/fog/FOGBase.class.php on line 53, referer: http://fogserver/fog/management/index.php?node=report

Mod edited to use code box, please use code boxes in the future.

@Wayne-Workman Hi Wayne - on the FOG server it’s ext3, but the images are typically less than 20GB and I haven’t experienced the error referenced in the link. Right now I’ve archived some of our lesser used images to another server and can restore them if we need them. This has freed up enough space for a bit while I can still try to get this working.

In addition, I’m still working on a possible solution of running FOG in a FreeNAS jail so I have access to an easily expandable amount of storage. I’ll need to test the performance, but it might be a better way to go for us. Has anyone else tried to run FOG in a FreeNAS jail?

Thanks for the continued support, Wayne!

Cheers,
Dave.