Surface Pro 4 unable to image

[Scott Adams]

@Tom-Elliott I should also add that I had the argument there from the beginning, as this was the fix the last time I had a thread on the surface (about 3 months ago). I have also set this host to use the kernel we were using at the time to see if that would help, and it did not.

[Tom Elliott]

@Scott-Adams The KERNEL_DEBUG and CONSOLE LOG LEVEL stuff will only impact the information printed on the client machine. There will be NO logs as we don’t store that information on the server. First it would BOG the server down especially when dealing with many tasks. Second, it would be quite difficult to filter out which log to actually look at.

If you up the levels and enable the DEBUG option, the simplest method to get us info is to take a picture and upload that here.

[Scott Adams]

@Tom-Elliott Ok. So, apparantly my changes are not being saved in the FOG Configuration > FOG Boot Settings. I select FOG_KERNEL_DEBUG and up my FOG_KERNEL_LOGLEVEL to 7, click Save Changes. It says that the settings were saved, but then I notice the check is not checked and the log level is still set to 4.

[Scott Adams]

@Tom-Elliott

[Tom Elliott]

@Scott-Adams What version of MySQL are you running? (5.7?)?

[Scott Adams]

@Tom-Elliott 5.5.49-0ubuntu0.14.04.1

[Scott Adams]

@Tom-Elliott Do I need to update? Are there credentials for mysql stored in the WEBui somewhere that I need to check?

If I log into mysql on my FOG server, I can manually edit tables and contents. Just can’t do it from the WebUI.

[Tom Elliott]

@Scott-Adams Can you get the output of mysql command:

show create table fog.globalSettings

[Scott Adams]

@Tom-Elliott

[Scott Adams]

@Tom-Elliott I have also checked .fogsettings, config.class.php and sql username/passwords match. I also tested the storage node mysql username/password (following the troubleshooting mysql wiki) and credentials worked. It is just something with the WebUI itself or how the WebUI communicates to the mysql database.

[Tom Elliott]

@Scott-Adams Can you check the schema out? It appears, from what I can see, you’re missing a few global settings from the table, though I have no idea what.

Would you be able to set the schemaVersion to say 200?

UPDATE fog.schemaVersion SET vValue=200;

Go to the gui and approve it to update.

[Scott Adams]

@Tom-Elliott I did. I then received the attached errors when I approved.

I have since logged in and am able to navigate the webui. However, I am still unable to save any changes within FOGSettings.

When I re-run the show create table fog.globalSettings, all settings look the same, only the AUTO_INCREMENT has changed to 188

[Scott Adams]

@Tom-Elliott This is the same issue I reported on a few weeks ago.
https://forums.fogproject.org/topic/7276/after-upgrade-to-trunk-7324-no-settings-available-under-fog-configuration-fog-settings

[Scott Adams]

Any thoughts or ideas yet? I am completely at a loss. Once again, I updated versions to see if that would fix. No go.

[Tom Elliott]

@Scott-Adams Anything under apache error logs?

[Scott Adams]

@Tom-Elliott It says “unable to open file for reading”. It does this for all the apache logs under log viewer…

[Tom Elliott]

@Scott-Adams So you can get to the GUI?

[Scott Adams]

@Tom-Elliott Yes sir! I can created hosts, create images (capture and deploy). From within FOG Configuration, I can change settings in the iPXE Menu Cusomtization. I can download new kernels.

The only restriction so far is for any changes I make to the FOG Settings under FOG Configuration. I know this is not the original topic of this thread, but the troubleshooting for this topic led us down this path.

[Tom Elliott]

@Scott-Adams The unable to read files is probably because ubuntu is extremely a PITA lately.

When they run logrotates, the change the permissions of the file to what they think should be set, rather than just move the file and continue on.

So you probably need to re-run the installer and have it try to see the files again.

[Scott Adams]

@Tom-Elliott What installer do I need to rerun? I just re-updated SVN yesterday.