Posts made by JGallo

@wayne-workman

Tried that and still get the database connection message.

@wayne-workman

I know that I went from 1.4.4 to 1.5.0 RC1 if I recalled. I know when I upgraded I made a huge leap. New interface and all. During that time there were replication issues and eventually updated to 1.5.0 RC7 which still had replication issues. I then upgraded to 1.5.0 RC9 which replication had major issue that was resolved in a working branch. So I have been on working branch 57 until about an hour ago I went to 64 with all nodes and fog server. I have been observing this issue since I have been on 1.5.0 from the new interface. I never had this issue in 1.4.4

@wayne-workman

on working branch 57 it was very consistent even with all the changes made to fog and the vCPU’s. I have been updating all the storage nodes and fog to working branch 64 today and the problem is still persistent. The only pattern I have observed is that upon rebooting the fog sever, the valid connection messages do not appear for about an hour or so. Then the messages begin to appear for random nodes that I have the graph enabled. At random times, the messages tend to go away but then come back upon selecting another storage node on the dashboard.

@wayne-workman

At the secondary schools, the connection speed to our district office is 1Gb and the primary schools are at 100mb. The FOG IMAGE REP SLEEP TIME is set to 10800.

@wayne-workman

I don’t have any. We use Group Policy to manage printers, settings, etc. Back in the day we used the FOG Client when autojoin domain features were utilized. We don’t anymore due to large amounts of chromebooks replacing aging PC’s.

@wayne-workman

I don’t have too many VM’s. I do have 4 but each of those has either 1 or 2 vCPU’s allocated to them. I have now set 4 vCPU’s for the fog server VM and I still have that issue. I also set the client checkin time to 300 with same issue.

Here is what I noticed. I see that the FOG server disk I/O is about 15% give or take on a constant basis. I also noticed that all the disk activity is from apache2 with user www-data and mysql is using up to 5GB of memory at times just on idle. Could this be some programming bug or my database needs to be cleared?

@wayne-workman

Ok so I have tried to decrease the client checkin time and it seems like it helps but eventually ends up causing that message. I even went to the extent of not sitting on the homepage just to make sure and after an hour I go back and check and still have those connections messages.

I will try one more thing and if this doesn’t work i will just deal with it but could I raise the number of vCPU on Hyper-V from 2 to 4? Will this help improve performance? That’s basically the only thing left to do to improve performance on the fog server. I did make the change from dynamic memory to static. thanks.

@wayne-workman

Cool. Makes perfect sense. I must say I don’t think it’s the storage node servers as they mostly consists of Dell R410’s and R210’s with at least 8GB to 16GB of memory. I will try to decrease the check in time. Is the value in seconds or minutes for the check in time in FOG?

Could it be something on my end with the network where packets are being lost and FOG server isn’t receiving responses to those check ins? Or if it’s a timeout script could we increase it manualy? What things should I be looking for if it’s network related?

@george1421

I have Ubuntu Server 16.04.03 LTS

Here is a screenshot of my dashboard so you can better understand what’s going on. When you click on a storage node, the information gets refreshed and it works as with the Storage Groups. They go blank and when you refresh they come back.

Hello,

I have been searching around the forums about configuring slack in FOG. I currently am on working branch 57. The plug in use to work but someone kind of disabled the slackbot and messed things up. So I started from scratch by regenerating the Access Token and when I go to the plug in to set the parameters for User/Channel it keeps saying that username/channel is incorrect. Could someone explain to me the format or example for the User/Channel parameter? I have tried the following:

@user/#slackchannel
@user /#slackchannel
@user / #slackchannel
@user #slackchannel

and none are successful. Thank you.

@sebastian-roth

Here is the top header from this am:

top - 07:47:12 up 16:00,  2 users,  load average: 0.01, 0.05, 0.07
Tasks: 166 total,   1 running, 165 sleeping,   0 stopped,   0 zombie
%Cpu(s):  5.5 us,  3.9 sy,  0.0 ni, 90.1 id,  0.0 wa,  0.0 hi,  0.5 si,  0.0 st
KiB Mem :  4035292 total,  2814336 free,   500232 used,   720724 buff/cache
KiB Swap:  4190204 total,  4190204 free,        0 used.  3219104 avail Mem

The imaging aspect of it is fine. The web UI becomes sluggish when I begin to create storage nodes and storage groups. I have updated all the nodes to working branch 57 to be consistent across the board.

@george1421

I will check tomorrow and place the results here.

@george1421

Last login: Thu Oct  5 13:44:58 2017 from 10.215.57.57
administrator@VUSD-FOG:~$ top
top - 15:03:19 up  5:18,  2 users,  load average: 0.21, 0.19, 0.11
Tasks: 174 total,   1 running, 165 sleeping,   0 stopped,   8 zombie
%Cpu(s):  5.5 us,  3.2 sy,  0.0 ni, 90.3 id,  0.0 wa,  0.0 hi,  1.0 si,  0.0 st
KiB Mem :  4035292 total,  3074368 free,   514096 used,   446828 buff/cache
KiB Swap:  4190204 total,  4190204 free,        0 used.  3223812 avail Mem

Client check interval was set to 60 but I doubled that just in case. The FOG server is on a Hyper-V with 2 vCPU and 4GB-16GB of allocated memory. top shows the following:

MYSQL - 5 -13% CPU usage 6 - 8% mem usage
FOGMulticast - 3-5% CPU usage 1% mem usage
Apache - 1 - 3% CPU usage 1% mem sage

So nothing crazy out of the ordinary I think according to top. Should I raise the vCPU on the hyper-v? To 4? Or change some other setting in FOG?

Hello,

I’m noticing that after some time the fog server is running that it begins to have issues with the nodes. On the dashboard, it shows a message that “a valid connection cannot be established” to all nodes. So when you click on the storage node, it will refresh and it works but then other nodes have the same issue. I came across a post to increase the memory limit for the php file in fog settings. that seem to help but not sure if it will fix it. I have also noticed that the FOG server itself is having a lot of activity at least by the graph and it’s currently not needing to replicate.

My question is there areas in the FOG settings to improve web UI speeds? I have read @george1421 post about php-fpm making web UI faster but I’m not sure if this is ready or experimental. Is there anything I can do to improve the speeds currently on the working branch? I have about 18 storage nodes with 6 storage groups on network of roughly 2500 PC’s. Currently the fog database only has about 60 computers as I have had to start from scratch. I have disabled the host lookup option and increased the imagerepsleeptime so it’s not so taxing on the web ui as also for replication.

Thank you.

@TomcatKZN When I run into issues like that, I would uninstall fog completely including the fog database and restart the process. The step where it asks to go to the management site, that is to update the schema.

Tip: If you are starting fresh install with 16.04, you still need to create the FOG database first and if you set a password, remember to use that password during the installer of FOG. I learned this because it kept popping up errors with that install/update = fail and it was because from a fresh install you must create the FOG database first.

Tested and updated this morning. Works fine. Thank you guys.

@Tom-Elliott

I just update about 10 minutes ago and came across the same issue. I needed to be on the working branch for replication issues but when I went to update and did a git pull then re ran installer, it failed to install init.xz I’m reading the error log and it shows access denied to ‘root’@‘localhost’ Can I go back to dev-branch? It says it’s still RC9 and I know I ran into issues with replication. Thanks.

@Tom-Elliott

I have been keeping an eye out on this issue with replication myself, im running V52 of working branch, should I wait until RC10 to come out to update? So far I think everything is functioning normally for replication but figured I could wait until RC10.