Posts made by CoxM

@Sebastian-Roth Thanks

@Sebastian-Roth

@Padcotton Sorry, I don’t understand your comment. I was replying to @Sebastian-Roth, no one else.

Thanks for the info @Sebastian-Roth. I have tried both re-running the installer and manually issuing the ALTER commands. They appear to run correctly but not resolve the issue.

Fora little more background.
I do have another storage node (SN), as yet not upgraded that is still running fine, it’s only the SN I upgraded that’s failing. however, the fogsettings file on both the working and failed SN are the same bar the version and IP details, all the mysql info is the same and is mirrored by the master node.
From previous troubleshooting I recall there being another file which contains credential info, is that correct? If so, where is it, might it be the problem?

Thanks,
Matt.

Hi All,

As the title says I have no valid DB connection from my newly upgraded storage node.

So far I have updated the master fog server to 1.5.4 (from 1.5.3) and one node, which is the one I have this error on.

I have had this before and needed to get the various passwords configured correctly across the servers but from what I can see the fogsettings file is correct.

Any advice on where best to start looking for the problem?

Thanks,

Matt

@tom-elliott Great, thanks for the update. Cant wait to give 1.6 a go.

Re: Can I change the colors of the Tx/Rx graph?

Did this ever get pushed through to a release? Due to some other problems we have had I have upgraded all our fog servers to 1.5.3 but now the bandwidth graphs are the same colour for all 4

Thanks.

Our master server and one storage node is on 1.4.4
the two newer storage nodes, both having the same problem as described, are on 1.5.2

We have had issues in the past upgrading hence the mixed versions.

Thanks.

Hi All,
I have a new storage node configured which appears to be working correctly however once the image replication is complete it seems to be starting again. This mean you will se the image file increase in size to the the full size of the image hosted on the master. It will then seem to delete it as the folder returns to 0 in size before it begins to replicate again.

Any ideas why it might be doing this?

Thanks.

Hi All,
Just setup and got working our new storage node. It appears to be working and I can see the image getting replicated over to it but the bandwidth graph isn’t showing any traffic in or out and there is no option for it in the log drop down menu.
Any info would be great.
Here are some images to go with it

!

On the bandwidth graph I have set it to show received data and it should be PHX that is getting sent the image but this seems to show POR, the master node, sending.

For reference POR (Master) and ATL (Storage Node) are on 1.4.4
PHX (Storage Node) is on 1.5.2

Thanks.

I have found the problem, it was the type of speech mark round the password.
Thanks to those that viewed.

Hi All,
I have a Fog server and one storage node that are running 1.4.4.

I have just build another storage node in a new location and it has installed at 1.5.2, will this work?

I can see the new SN on my dashboard but with a DB error

Any help would be really appreciated.

Thanks.

Hi,

Currently running 1.4.4

I saw there were some issues with the current release so didnt upgrade but will hopefully be able to hold out for 1.6 as the upgrade process can be awkward.

Thanks.

Hi All,

I currently have 3 office locations with a single master fog server and two storage locations (one being the master server and one being just a storage node)

Until I have time to build my 3rd storage node i want to direct the location without a local node to the nearest one. When I make the setting change in the web portal it tell me the location has updated but isn’t holding on to the setting.

I am trying to set Phoenix to uses the Atlanta node for now but even after setting it it remains “NOT SET”

Any ideas?

Thanks all.

Hi All,
I have seen pending MACs on your system before which as I understand is when devices such as laptops have two NICs and it wants to assign the additional NIC MAC to a host.

We now seem to have a Pending Host, whats this please?

Thanks.

Hi,
I need to get an image to resync over to our storage node. If I manually delete the specific image folder from the room images folder (running on ubuntu) will it resync?

At the moment it seems not but dont know if it should.

Here are my image replication logs from the master

[02-21-18 3:51:40 pm] | There are no other members to sync to.
[02-21-18 3:51:40 pm] | Image Name: Win10-Desktop
[02-21-18 3:51:40 pm] * Not syncing Image between nodes
[02-21-18 3:51:40 pm] | There are no other members to sync to.
[02-21-18 3:51:40 pm] | Image Name: rep_test
[02-21-18 3:51:40 pm] * Not syncing Image between nodes
[02-21-18 3:51:40 pm] | There are no other members to sync to.
[02-21-18 3:51:40 pm] | Image Name: Generic_Win10
[02-21-18 3:51:40 pm] * Not syncing Image between nodes
[02-21-18 3:51:40 pm] * Attempting to perform Group -> Nodes image replication.
[02-21-18 3:51:40 pm] | Replication already running with PID: 27013
[02-21-18 3:51:40 pm] | Image Name: Win10-Desktop
[02-21-18 3:51:40 pm] * Found Image to transfer to 2 groups
[02-21-18 3:51:40 pm] * Started sync for Image rep_test
			lftp -e 'set xfer:log 1; set xfer:log-file "/opt/fog/log/fogreplicator.rep_test.transfer.ATL-FOG.log";set ftp:list-options -a;set net:max-retries 10;set net:timeout 30; mirror -c -r -R --ignore-time -vvv --exclude ".srvprivate" "/images/rep_test" "/images/rep_test"; exit' -u fog,[Protected] 10.0.0.23
[02-21-18 3:51:40 pm] | CMD:
[02-21-18 3:51:40 pm] * Starting Sync Actions
[02-21-18 3:51:39 pm] * Deleting remote file: /images/rep_test/
[02-21-18 3:51:39 pm] | Files do not match.
[02-21-18 3:51:39 pm] | 0 0 /images/rep_test/test2.img ftp://fog:********@10.0.0.23/images/rep_test/

I can see that it has copied test_rep and updated the files within that folder after the intial sync which created it.

Having deleted Window10-Desktop it has not re created it.

Thanks.

Thanks @george1421 and @Sebastian-Roth with you help and some trial and error it is now working and the remote client try to image via the storage node.

Felt like the answer was obvious so changed the Fog UI path to match the mount point path.

So both read Data not Data1.

This is what we get.

@george1421
Hi,
I have updates the script as you suggested so it now looks like this when doing a showmount -e

but when I run a deply task against a remote machine, that is in the right location group to use the storage node rather than the main fog server it get this.

Notice the difference in path from the showmount output to the path in the image screen grab - this suggest that the path is being pulled from the path entered in the Fog UI, not the mount point.