Posts made by dustindizzle11

@Tom-Elliott I honestly do not know what the location plugin is. So I am guessing no, unless its something I should be using and I am just ignorant lol

@Tom-Elliott There are 7 total nodes and 4 groups. . I hope I am not missing something ridiculously obvious haha. If I upgrade to revision, do I need to do anything to the nodes? I have a .32 server that is “disconnected”. This server is the SVN with the same database that I imported so I could test stuff.

@Tom-Elliott The image is located in the “Images2” storage group, where this node is located. Since I can verify that the directory and file actually exist, is it possible it is looking somewhere else? Thanks for your help!

The fog node has the directory. Here is a putty screenshot.

Testing Windows 10, so I upgraded my test fog server to SVN and uploaded my Win10 Image to fog. Now when I try to download the image, I get this message in the picture that says “ls: cannot access /images/myimage/d1.mbr: Not a Directory” . I realize that what it is specifying is not a directory but a file, but I don’t know why it thinks it needs to be a directory. The file exists and everything (d1.mbr). Any thoughts?

@Tom-Elliott
It’s the same type of image. Some of the text looks different in spots.

@Tom-Elliott

Just tested another model and got the same results.

Hi Tom,
Thanks for your quick response and sorry about the late reply. I will get back to you on the imaging issue here soon. I put the old .31 server back in place just for the time being because Apache keeps having issues. Computers in the network are unable to boot to PXE, so I just swapped the server for the time being. This has happened for a few days in a row now. I would get apache working, but it would eventually fail (I would come into work in the morning and computers would be having issues starting up because they were not able to PXE boot). I would get errors similar to the ones below.

[Mon Jun 08 10:37:42 2015] [error] [client 192.168.69.85] PHP Warning: mysqli::mysqli(): (HY000/2002): Can’t connect to local MySQL server through socket '/var/run/mysq$
[Mon Jun 08 10:37:42 2015] [error] [client 192.168.69.85] PHP Warning: mysqli::select_db(): Couldn’t fetch mysqli in /var/www/fog/lib/db/MySQL.class.php on line 165
[Mon Jun 08 10:37:42 2015] [error] [client 192.168.69.85] PHP Warning: mysqli::query(): Couldn’t fetch mysqli in /var/www/fog/lib/db/MySQL.class.php on line 89
[Mon Jun 08 10:37:42 2015] [error] [client 192.168.69.85] PHP Warning: MySQL::sqlerror(): Couldn’t fetch mysqli in /var/www/fog/lib/db/MySQL.class.php on line 180
[Mon Jun 08 10:37:42 2015] [error] [client 192.168.69.85] PHP Warning: array_key_exists() expects parameter 2 to be array, null given in /var/www/fog/lib/db/MySQL.class$
[Mon Jun 08 10:37:42 2015] [error] [client 192.168.77.50] PHP Warning: mysqli::mysqli(): (HY000/2002): Can’t connect to local MySQL server through socket '/var/run/mysq$
[Mon Jun 08 10:37:42 2015] [error] [client 192.168.77.50] PHP Warning: mysqli::select_db(): Couldn’t fetch mysqli in /var/www/fog/lib/db/MySQL.class.php on line 165

Regarding the imaging issue, I just hooked up the SVN 3530 server in a separate network where I can troubleshoot apache and the imaging screen mentioned in the post. Apache seems to be working again. I will test a few different models to see if it’s just this one model that has that weird screen.

Quick question when anyone has time. I upgraded my fog unit to SVN 3530 from 1.2, and I noticed now after downloading an image, after it gets to about 5% the progress screen gets all wacked out and the imaging doesn’t finish. Below is a picture of the normal screen along with the screen it changes to at about 5%. I appreciate any help, Thanks!

@Tom-Elliott
Makes perfect sense. Thanks again Tom!

@Tom-Elliott
I increased it to 256M, and it is working perfectly fine now, Thanks so much! I did notice after running a report though, that it said all the past “downloads” are “uploads”. Unless I am misunderstanding it, I would think they should be downloads. (picture attached) . I may be looking at it wrong, and it’s not a big deal, I just thought I would throw it out there incase this is incorrect. The image is showing times when I sent an image to a computer, “downloaded” to it. In the picture it shows as “Upload”.

Hi Tom,
Just checked it and you are right, it is 128M. I am assuming I can safely increase this because this is the default limit. Is that correct? Thanks for the quick reply!

This might be a quick one, but I cannot seem to get the FOG imaging log report to show anything in the web GUI. What happens is I will click the “Imaging Log” button in the GUI, then it will proceed to “(server)/fog/management/index.php?node=report&sub=imaging-log” I have version 1.2.0, which was upgraded from .31. I tried to search for any documentation about this, but came up empty. Has anyone experienced this problem with the FOG reports? If anyone has any ideas let me know, Thanks!

Dustin Olson

@Trevelyan Yes, I just restarted it to test, and it came right back up and I was able to login. So it looks good so far! Thanks for trying to help so much btw, I really appreciate it.

I installed a fresh copy of 12.04 server with the same version of Fog that my current server had (0.31) and imported the database. After importing the database I installed the upgrade to 1.2.0. It was Friday evening and I was doing work on the Fog server through a VPN connection, so when I tried to upgrade the Schema it did it’s usual “hang”. I thought I would just figure it out on Tuesday when I came in for work. When I came in for work, to my surprise the test box had upgraded. My only theory is that it took some time to do, not sure why, but it ended up upgrading over the weekend.

This can be closed for now, but I am still unsure why the Schema would hang for such a long period of time to update the tables in the SQL database.

A quick note to anyone installing an older version (like 0.31) on ubuntu server 12.04, you will need to install SQL server BEFORE you run the install. I had to run “sudo rm -rf /var/lib/apt/lists/*” and “sudo apt-get update” before SQL server would install properly.

Just to Note - Tom Elliott was taking a look earlier. Ran into some issues with the distro being old (10.10). I will plan on upgrading to 12.04 and updating this when the upgrade has finished. Since it was 10.10 and not 10.04, I will clean install 12.04 and import the database.

I can’t seem to get past the “Database Schema Installer/Updater” when upgrading Fog. I work for a school district, and to make sure the upgrade will work on our live Fog server, I been testing the upgrade to 1.2.0. Every time I try to upgrade, the web Gui either hangs, or will fail. I current have tested a fresh install of 0.31, imported our database and tried the upgrade. The most recent test was me using clonezilla on the live Fog server, copying it to another box so I have an identical copy and trying the upgrade. Both times I get the same exact results, the Gui either hangs, or will give me the database Failed! messed showing a bunch of tables below that it wanted to alter.

-I have tried making sure the password is correct in /var/www/fog/lib/fog/Config.class.php, which it is.
-I have completely wiped the password for mysql, changed Config.class.php and get the same results
-I have tried both “localhost” and the IP of the server in Config.class.php for DATABASE_HOST.
-I have tried putting all the settings in /opt/fog/.fogsettings before running the installer, still with the same results.

When I am saying that the Gui will either “hang” (just sits there, bottom left of browser says waiting for “server IP”) or Fail, I am meaning that as I change settings and run the installer, I get both of those results. I have no problems logging into mysql with “mysql -u root -p” with my password. Currently the password is wiped (I thought as a last resort deleting the password may fix it), so I am able to login with “mysql -u root fog” successfully.

I know a decent amount about Fog, just enough to get myself in trouble. Has anyone experienced this issue or have any ideas as to what might be going on? I was wondering if maybe there was another config file I am needing to edit? If you need more info, let me know. I appreciate any feedback that can help me get past the Schema Updater.Thanks!