Slow UI High RAM usage.

[Wayne Workman]

@kagashe said in Slow UI High RAM usage.:

• Copying binaries where needed…Failed!

@Tom-Elliott this is the second recent occurrence of this error.

[george1421]

In your case its right to actually move off FOG 1.5.0 to 1.5.2 to eliminate the high CPU usage. BUT if you are still on 1.5.0 and its kind of working for you, please wait until 1.5.3 is released (in the next few days) there are some annoying issues with 1.5.2 that are already addressed in 1.5.3 (dev). The developers said that 1.5.3 should drop very soon.

[Kagashe]

Thanks @george1421 will give it a go, hopefully will fix the error highlighted by @Wayne-Workman.

[Tom Elliott]

@wayne-workman no change in how this works. Considering the number of people who updated and/or installed 1.5.2, 2 people having this issues does not mean there’s something wrong with the installer handling this.

[Kagashe]

@tom-elliott Any way to resolve the issue before the new version is out as I’ve got a bunch machines arriving that will need to be imaged?

[Tom Elliott]

@kagashe this is most likely something on your network preventing the download of the file. You could try deleting the current binaries1.5.2.zip file and rerun the installer. Are you behind a proxy?

[Tom Elliott]

This in regards to the downloading of the binaries file of course

[Kagashe]

@tom-elliott there was a 1.5.0 binaries folder sitting there which I deleted and that solved the binaries error, thanks for that, will monitor the ram usage as have upgraded to 1.5.2 and feedback the results.

[Kagashe]

Just an Update,

Ram Usage remains high however the UI has gone back to normal loading times so happy with that. One other issue I ran into is when adding or editing a snapin FOG says a name is required even though I have entered a name?

[mp12]

@kagashe check this thread. https://forums.fogproject.org/topic/5300/cant-upload-snapins-anymore

maybe it has something to do with the configuration of your php.ini file. post_max_size upload_max_filesize

what does apache error.log say?