@sebastian-roth Here is a new thread: https://forums.fogproject.org/topic/11393/chromium-image-issues-after-updating-server

Attached is a photo of the error that we’re still getting even after doing a fresh install of the latest version of FOG. I still can’t Capture a Chromium image without getting an error. Same FOG server works just fine with Windows images, etc, but not with Chromium.

@sebastian-roth Thanks Sebastian. I had since deleted the 2018CloudReady image, but later created another one with the exact same results. It is called NewCloudReady. Below is the contents of it’s directory and attached is a picture of the image setup:

total 1872496
32 d1.mbr
4 d1.original.uuids
4 d1p10.img
4 d1p11.img
4 d1p12.img
4 d1p13.img
4 d1p14.img
4 d1p15.img
407092 d1p16.img
6588 d1p17.img
713284 d1p18.img
6588 d1p19.img
4 d1p1.img
713284 d1p20.img
4 d1p21.img
4 d1p22.img
11860 d1p23.img
4 d1p24.img
4 d1p25.img
128 d1p26.img
13552 d1p27.img
4 d1p2.img
4 d1p3.img
4 d1p4.img
4 d1p5.img
4 d1p6.img
4 d1p7.img
4 d1p8.img
4 d1p9.img
8 d1.partitions
0 directory.txt

Screenshot: https://photos.app.goo.gl/BM5R39AVgvhvOBg32

@sebastian-roth Here is a new thread: https://forums.fogproject.org/topic/11393/chromium-image-issues-after-updating-server

New thread spawned from my previous post about upgrade issues. I’m not able to use my old Chromium issues after upgrade and also not able to successfully create and restore Chromium images after upgrade. Windows images seem to be working fine.

@tom-elliott Tried another Chromium image from scratch and still not working. However I also tried a new test Windows 10 image just to see what it would do and it worked fine. So the general process of imaging from creating to deployment is working, but not with any of the Chromium images.

@george1421 I do apologize for chasing multiple issues. I guess my original issue was just one issue that things broke after upgrading to a newer version, but it was definitely multiple things.

Fog Server is a VM running Ubuntu 16.04 I have 2 CPU’s dedicated to it and it’s a RAID configuration on the master VM Server which is a Dell Poweredge 2950 if I’m not mistaken.

I also have 8GB of Ram dedicated to it.

@tom-elliott Yes, I looked on the Node in the /images/2018CloudReady folder and it was filled with files that seemed similar to other images on the node. I just blew it away and trying it all from scratch again, now that our performance issues are better and will report back.

@george1421 @Wayne-Workman Setting the Client Check In to 900 has definitely helped the performance. Interfaces are acting more normal now and cpu usage has dropped significantly. Strange that it didn’t have that problem before, but does now, but glad to see it working better.

Still no luck with the Chromium image though. I thought since performance was fixed, I’d go ahead and upload a new image again and then try to download it to another laptop. Again, upload shows that it’s successful, but when I go to deploy it on another computer, I’m getting this error: https://photos.app.goo.gl/I75ORDRoDZqf24OU2

@george1421 It was set to 30. I changed it to 900.

@george1421 I’ll get the screenshot soon, but I did run the top command sorted by cpu usage a bit ago and it’s definitely mysqld that’s consuming it. Running 60-80% constantly with basically nothing going on with FOG.

I should throw in that there was never a performance problem before the upgrade to the newer version with the same amount of Clients, etc.