Posts made by JGallo

@dpotesta50

looks like your FTP credentials are not matching properly. The error is not on the Windows 10 machine but on the fog server ftp credentials.

@nrg

Possibly could be a bug. Wouldn’t be the first time LOL. Curiously what browser are you on and what size screen are you on? If you try to narrow the window on super wide screen I have seen the dashboard get all weird so I usually keep the window expanded.

@dpotesta50

Prior to uploading the image, in Windows 10, proper shutdown? Win 10 has that weird sleep boot and depending on which build it is you might have to disable it in the power options FYI. Also there is cmd option to use to properly shut it down prior to uploading the image.

@dpotesta50

Is that a Windows 10 image you are trying to save?

@nrg

Just realized your node is on 1.2 and your FOG server is on 1.5 RC10. I would update your storage node first if that’s an option. Many changes since 1.2

@nrg

I also had the valid database connection error which turned out to be a limit that I was hitting with mysql. Could be related and you could go into mysql and check to see if you are hitting that provided your credentials for your nodes are correct. It sounds like they are because replication is working.

Discussion about valid database connection

If you go into mysql, you could check by running the following command:

mysql> show variables like 'max_connections';

that max value if it’s being hit will show in the following command:

mysql> show status like '%onn%';

If the output of that is higher than the max connections then there is your problem. Read through the discussion and see if it can help what your dealing with.

@nrg

1.5.0-RC9 had some issues with storage nodes. I would update to 1.5.0-RC10 as it was just release yesterday and many improvements from RC9. Most of those issues were resolved in working branch and hence RC10 should resolve your issues. I had the same problem and those issues were resolved now.

@bardwood

I ran into an Windows 10 Creators Update issue with FOG that had to do with the bitlocker message on FOG. The FOG team pushed some updates and it works now on the working branch. Then again I only was on legacy mode and I was working with a 9020 also. Can’t say if the issue is resolved with UEFI now.

@bardwood

Sorry I misread your post. I meant to say is we use 7010’s and I am currently on the working branch. I use legacy mode instead of UEFI and it works fine. Are you trying to stay with UEFI?

@wayne-workman

Very true but making the change in the live DB is a great plan B until a long term plan A is found. I checked the mysql mem calc link and I compared the mysqld.cnf settings for those calculations but many of those variables are not there. I think at this point it works and I don’t foresee needing many more storage nodes in the future for this fog server. I’m happy it’s working now. Thank you both for all your help.

@bmorine

I utilize the MSI packager that comes with DeepFreeze. You could however utilize the DeepFreeze seed instead and place that on the image. Then on the DeepFreeze console, create a group and use a filter. The computers will populate and from there you can install the executable. Just incase the snapins don’t work.

@wayne-workman

I’m following the steps in Wiki but mysql is on Ubuntu 16.04.3 LTS and when I go to /etc/mysql/my.cnf and try to add the increase of max connections, it errors out. Modifying the mysqld.cnf in /etc/mysql/mysql.conf.d and removing the comment on the line with max connections works. However it’s really odd that when you restart mysql and go into mysql to check the max connections it would show a smaller value then defined in the mysqld.cnf file. Am I right to modify the mysqld.cnf? I’m lost at this but I know that at least the value is increased so it works as intended but with the incorrect value I defined.

@sebastian-roth

I did a git pull and updated FOG to address a Windows 10 issue and upon the update the issue I had with database connections returned. It would appear that mysql goes back to default max connections of 151 after the update. Does the fog installer/updater have mysql update settings? If it does, could I suggest an increase on that max connection limit be part of the fog installer/updater? Or is this something that needs to be manually entered in mysql with the amount of storage nodes and groups I have which was done already to address my issue. Thank you again for your help on this.

@cnkpadobi

You might want to switch to the working branch.

FOG Install instructions on wiki

Here you will see instructions on how to install Git and switch to working branch. Hope this helps.

@jj-fullmer

It works now. I did a git pull from working branch and don’t have problems now.

I’ve encountered this as well and funny thing is this only happens to the Windows 10 Creators Update build that came out in September. I’m on working branch 69 and this was not an issue on an older build of Windows 10. Not sure which one but I can check. Has the bitlocker detection issue been patched on working branch?

@Wayne-Workman

@Sebastian-Roth remoted in and looks like mysql was limited to 150 connections. He raised it to 250 and now it would appear fixed so far. I’m keeping an eye on the max used connections and it hasn’t gone over 161 so I must have been hitting that 150 max. Thanks for all your help here. Greatly appreciate it.

Another observation is that upon the sudo service mysql restart on the fog server, the error goes away for DefaultMember in the dashboard. I tried the same thing on other storage nodes but the message is still in the dashboard. Maybe this could be something with remote connections with the mysql database.

@wayne-workman

So after several different attempts to see this issue be resolved, the issue continues to persist. The patterns I have observed is that it now takes about an hour for the issue to begin. I have gone into the /etc/mysql/mysql.conf.d/mysqld.cnf file and edited the bind address to each node because on a seperate post it was recommended to use the IP of the node instead of the loopback. Don’t think this worked because I restarted server and node after these changes and problems persist. I also went into the /var/www/fog/lib/fog/fogurlrequests.class.php and edited the aconntimeout = 2000 to 10000 as well as the counttimeout = 15; to 30. Would it be possible @Tom-Elliott or someone to remote in to check this out remotely? I know all the passwords for fogstorage accounts are accurate because imaging works fine. Registering computers at sites works fine as well as image replication to storage groups work fine. I could start from scratch and add one node at a time but I could not be able to place a test fog server in place due to this being a production FOG system in place. I have back ups of the images so starting from scratch is not a problem. I have a strange feeling this could be related to Ubuntu and updates with PHP7. Thank you

@sebastian-roth

Sweet. The default setting for the loglevel is 4. Taking it down to 3 no longer produces those USB errors. Thank you. The computer does register and I can image but those USB errors were extremely annoying. Seems like this will suppress those messages and works just fine now.