After 100% capture failed on database updaet.
-
My setup:
Fog server is on one server. Located in place A.Fog Nod server is separate and located in place B. This nod server is set as master old master died so i set this up and enabled as Master. Firewall is disabled on this server but our infrastructure has firewall (hardware).
When i installed storage node i entered ‘FOG Storage Nodes’ credentials from FOG System Settings.
When installation finished he gave me username and password which i used when i added this storage node.Until now fog system never worked.
When i run image capture at the end i see this:
What i’m missing her?
-
@raimonds said in After 100% capture failed on database updaet.:
Fog Nod server is separate and located in place B. This nod server is set as master old master died so i set this up and enabled as Master.
Please be more precise on what you mean by that. I have not heard of a “Nod” server und can only guess.
The error in the picture clearly shows an issue with the
fogproject
service account. Have you used this account to logon and maybe changed its password? Don’t use this account!Search the forums on how to resync the password. There are many topics on this.
-
Fog server is setup on server A how is located in different country.
Idea is that i will setup local storage node in place B. So i don’t upload image file over internet.I created linux machine and i installed Fog server as storage at the end installation created this user
fogproject
which i never opened or used. On Linux machine i only using admin account (different thenfogproject
). After installation i tookfogproject
credentials and entered them in main fog server.Does this mean i need to reset password for
fogproject
user and then i update storage settings password in main Fog server? -
If by chance someone fiddled with the password on the fog linux service accounted called
fog
on 1.5.5 and earlier versions of FOG orfogproject
and 1.5.6 and later versions of FOG this error will be thrown. The linux service account is not the same as the default web ui account. The linux service account is owned and managed by the FOG code. If this service account gets out of sync with the fog settings there is a tutorial on getting everything back inline: https://forums.fogproject.org/topic/11203/resyncing-fog-s-service-account-password -
@raimonds said in After 100% capture failed on database updaet.:
Idea is that i will setup local storage node in place B. So i don’t upload image file over internet.
Upload of images always go to the master node.
-
@Sebastian-Roth said in After 100% capture failed on database updaet.:
Upload of images always go to the master node.
From what I’m told, there is a way to configure fog to send its images to a storage node.
You need to have the location plugin installed and you need to create a new storage group. Place the remote server (i.e. storage node) in its own storage group as a master node. It can remain part of the default storage group as a storage node so it gets image pushed down to it.
Then make sure when you setup the image you pick the remote storage group to place the image. I think that’s how it goes.
-
@george1421 That is because the separate storage group has a master. It’s a “work around” to the “Images are always captured to the master node” because you, quite literally, are making the storage node, now, a master node. It works of course for this reason.