Posts made by Dave Wolf

@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.

@george1421 It’s the same password used by the default storage node. I used WinSCP to connect via FTP to the fog server using the same credentials and was able to upload a file, download a file, and delete a file. Not sure what else I can try, it would be nice to see if there is some error being spit out in a log file somewhere, or maybe on the client screen? I didn’t see anything thing that indicated an error, just a rather long delay at the end of the upload (which smells like a timeout to me).

I decided to work on a new server in a jail on our FreeNAS server while I debug this issue. I’m going to experiment with LVM as well, so I can hopefully prevent this issue in the future when we run out of space.

Thanks!
Dave.

@george1421 I don’t think fdisk will allow me to extend the partition beyond 2TB, so I think I’m stuck with that on the existing system.

I’m very close with the second storage node concept, it’s just not being moved from the /images2/dev directory at the end of the transfer. Is there some way I can enable debug and step through the upload on the client system to hopefully get some more information as to why the transfer is failing? I see a long pause when the upload is complete, like it’s trying to move the files, but they remain in the MAC address named directory under dev.

If I create a new image in the default storage group (that points to /images) it can upload and move the files properly. The permissions on /images and /images2 match exactly. I’m just not sure what’s different/missing.

Thanks again for your help, and if anyone else can chime in, I’d appreciate it very much.

Thanks,
Dave.

@george1421 My FOG server isn’t using LVM at the moment, unfortunately, and I would probably have to rebuild it if I wanted to convert it, since I only have the one 2TB volume. It’s deployed on an older ESXi server which had a little over 2TB left on it which I just wanted to add. My existing disk was created using fdisk and I believe it’s limited to 2TB. So, to do things “the right way”, I would have to scrub this installation and start over, unless I’m missing an easy way to convert. This server is used daily by my development team to deploy images for automated testing. I am looking for an easy way to add capacity without taking the system offline for any extended period. I will keep LVM in mind when the time comes to move to a better FOG hardware platform. Thanks for the suggestion to use LVM, I do appreciate it.

Cheers,
Dave.

Hi all,

I’ve added a new drive to our existing FOG server and followed the instructions from the post below to get it added as a storage node on the existing server.

Re: [I need to add additional storage on an already running FOG server](can I get some help?)

Background:

FOG 1.2 installation on Debian 7.6 - in operation since 9/2014
2TB drive with images in the standard /image directory

We have about 450GB free on the existing drive, so I added another 2TB drive and it’s mounted at /images2 (I’m not very creative in that regard). I created empty .mntcheck files in /images2 and /images2/dev.

I added a new storage group and added a storage node, set the IP address to the FOG Server IP, set the path to /images2 and set the Management username to “fog” and the password to the one I used when installing Fog.

I manually edited the /etc/exports file to export /image2 and /image2/dev.

I rebooted the Fog server for good measure and created a new image to reside on the new storage node. I began an upload. During the upload, I noticed that the temporary MAC-based directory for the upload in the dev directory was in /images/dev rather than in /images2/dev. I thought “hmmmm”, but let it continue. After the transfer completed, the files were not moved to their place in the /images2 directory and are still in /images/dev under the MAC directory.

I’ve checked the permission on the folders, they’re all set to 777 and root is the owner. This is what was set on the original /images folder. If I login using FTP with the fog account and password it is successful. I can even see the additional storage available on the dashboard. I’ve looked at the debugging info for FTP here in the forums, but I think I have it set properly. Is it perhaps a file ownership issue? Any other ideas?

Thanks for any help you can provide!

Cheers,
Dave Wolf

Hmmm, does that do anything different from manually deleting the partition using fdisk in a debug download? Just curious.

Thanks!
Dave.

Forgot to mention, FOG version 1.2.0 on Debian 7.6…

Hi all,

I am experiencing an issue with loading our Dell R200 servers with a Windows XP Embedded image that FOG has uploaded just fine. The R200 has an 80GB SATA drive, and I also have a pfSense image that loads on it with no issues. The process errors when restoring the image to /dev/sda1 with an “error exit” and the system reboots. I fired up a debug download so I could take a look at the partition during the process. Here is a screen shot at the first stopping point of the debug after running a “gdisk -l /dev/sda”:
[ATTACH]1316[/ATTACH]

I ran fixparts /dev/sda and let it fix the partition (or so I thought), but it would finish with the same error again. So, I used fdisk to delete the partition (see the following screen shot):
[ATTACH]1317[/ATTACH]

Here is what it looks like stepping through the debug download after deleting the partition:
[ATTACH]1318[/ATTACH]

and then typing “fog” to continue, here is the error:
[ATTACH]1319[/ATTACH]

Any ideas what else I can try? The initial Windows XP Embedded image that is on the disk was put there by Ghost (we’re trying to eliminate Ghost here and soley run FOG for our test lab).

Thanks!
Dave Wolf

[url=“/_imported_xf_attachments/1/1316_IMG_20140826_125614.png?:”]IMG_20140826_125614.png[/url][url=“/_imported_xf_attachments/1/1317_IMG_20140826_125645.png?:”]IMG_20140826_125645.png[/url][url=“/_imported_xf_attachments/1/1318_IMG_20140826_125711.png?:”]IMG_20140826_125711.png[/url][url=“/_imported_xf_attachments/1/1319_IMG_20140826_125737.png?:”]IMG_20140826_125737.png[/url]

Hi Tom,

I performed the upload-debug operation and ran the gdisk -l /dev/sda and it reported an issue with GPT being corrupt and did I want to use MBR. I answered yes and now I’m able to upload. I did run the fixparts /dev/sda command but when it reported that it would overwrite the existing partition, I opted out. I’m going to run the system through a couple of upload/download cycles to make sure it’s working ok, but it’s gotten farther than it did before. Thanks, once again, for your assistance!

Cheers,
Dave.

Hi Tom,

Based on another post in the forums regarding the Z230 (I should have searched first before posting), I pulled the hard drive and put a different one in the system in question and it works fine now. However, I will put the old one in there and try the upload-debug with the gdisk command you suggested to see if I can resurrect the original drive.

Thanks!
Dave.

Hi all,

Here’s another one: We have an HP Z230 workstation with Windows Server 2012 installed. The system registers with FOG just fine (version 1.2.0). The image I have created in FOG is a Windows 8.1, multiple partition - single disk (not resizable). I’ve used this image configuration for other hardware platforms with Windows Server 2012 with no issues. In this case, when the system boots and begins the upload, I get the following error in the screen cap below. I even reinstalled the OS after deleting the partitions, but it still gives the same error. Any ideas on this one? How can I repair the disk? (I tried a chkdsk /f), but I’m thinking that’s not what’s required here.

[ATTACH]1241[/ATTACH]

Please let me know if additional details are needed. This is the last system we need to get inventoried in FOG.

Thanks!
Dave.

[url=“/_imported_xf_attachments/1/1241_IMG_20140730_135124.jpg?:”]IMG_20140730_135124.jpg[/url]