It looks better afin reinstall of the clients ! 🙂

I had to do several times the mysql command :

UPDATE hosts SET hostPubKey="", hostSecToken="", hostSecTime="2018-05-29 09:47:07";

BUT it works.

Thanks.

NB : i don’t know how to mark the topic as “solved”

@sebastian-roth
Thanks to the suggestion, the tcpdump software helped me to understand that the host did not send any data packet to the FOG server during the closing phase of the snap-in. All this was due to the fact that my script assigns a static IP to the Host when certain parameters occur, so, in the IP assignment phase, the Host was offline and the snap-in was unable to communicate with the FOG server. So I solved the problem by inserting a 10-second pause in the script with the powershell start-sleep command, allowing the Host to return online before closing the snap-in.
I wanted to thank you for your availability and tell you that you are doing a great job with FOG.

@george1421 That is good to know, I will then probably try to update the kernel every once in a while…

I currently have Win 1709 and use Proxmox, let’s hope that there will be no problems 😉

What goes wrong with your storage node?

What are you trying to accomplish? Deploy from different storage nodes in different locations? (read up on location plugin if you haven’t already)

How did I miss this??
Thanks man, it was the password thing.

Simple fix. awesome I’m up and running.

how do I mark as resolved?

@Sebastian-Roth Yes it does return. I even see a ton of data being downloaded. I have cut off the data towards the end due to the length of the capture.

563 13.682607 10.86.96.177 10.85.195.199 TCP 74 50514 > 8080 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=1729539897 TSecr=0 WS=128 569 13.742557 10.85.195.199 10.86.96.177 TCP 78 8080 > 50514 [SYN, ACK] Seq=0 Ack=1 Win=65535 Len=0 MSS=1460 SACK_PERM=1 TSval=400875488 TSecr=1729539897 WS=64 570 13.742594 10.86.96.177 10.85.195.199 TCP 66 50514 > 8080 [ACK] Seq=1 Ack=1 Win=29312 Len=0 TSval=1729539912 TSecr=400875488 571 13.742693 10.86.96.177 10.85.195.199 HTTP 161 CONNECT fogproject.org:443 HTTP/1.1 575 13.801898 10.85.195.199 10.86.96.177 TCP 66 [TCP Window Update] 8080 > 50514 [ACK] Seq=1 Ack=1 Win=771008 Len=0 TSval=400875548 TSecr=1729539912 576 13.864407 10.85.195.199 10.86.96.177 HTTP 105 HTTP/1.1 200 Connection established 577 13.864424 10.86.96.177 10.85.195.199 TCP 66 50514 > 8080 [ACK] Seq=96 Ack=40 Win=29312 Len=0 TSval=1729539942 TSecr=400875608 579 13.87112 10.86.96.177 10.85.195.199 TLSv1.2 583 Client Hello 582 13.992592 10.85.195.199 10.86.96.177 TLSv1.2 1414 Server Hello 583 13.992609 10.85.195.199 10.86.96.177 TCP 166 8080 > 50514 [PSH, ACK] Seq=1388 Ack=613 Win=771008 Len=100 TSval=400875738 TSecr=1729539944 [TCP segment of a reassembled PDU] 584 13.992616 10.86.96.177 10.85.195.199 TCP 66 50514 > 8080 [ACK] Seq=613 Ack=1488 Win=32128 Len=0 TSval=1729539974 TSecr=400875738 585 13.992893 10.85.195.199 10.86.96.177 TCP 1414 8080 > 50514 [ACK] Seq=1488 Ack=613 Win=771008 Len=1348 TSval=400875738 TSecr=1729539944 [TCP segment of a reassembled PDU] 586 13.992908 10.85.195.199 10.86.96.177 TCP 166 8080 > 50514 [PSH, ACK] Seq=2836 Ack=613 Win=771008 Len=100 TSval=400875738 TSecr=1729539944 [TCP segment of a reassembled PDU] 587 13.992916 10.86.96.177 10.85.195.199 TCP 66 50514 > 8080 [ACK] Seq=613 Ack=2936 Win=35072 Len=0 TSval=1729539974 TSecr=400875738 588 13.992928 10.85.195.199 10.86.96.177 TLSv1.2 640 Certificate, Server Key Exchange, Server Hello Done 589 13.995298 10.86.96.177 10.85.195.199 TLSv1.2 192 Client Key Exchange, Change Cipher Spec, Encrypted Handshake Message 593 14.114585 10.85.195.199 10.86.96.177 TLSv1.2 117 Change Cipher Spec, Encrypted Handshake Message 594 14.114752 10.86.96.177 10.85.195.199 TLSv1.2 182 Application Data 598 14.237584 10.85.195.199 10.86.96.177 TCP 1414 8080 > 50514 [ACK] Seq=3561 Ack=855 Win=771008 Len=1348 TSval=400875988 TSecr=1729540005 [TCP segment of a reassembled PDU] 599 14.237599 10.85.195.199 10.86.96.177 TCP 166 8080 > 50514 [PSH, ACK] Seq=4909 Ack=855 Win=771008 Len=100 TSval=400875988 TSecr=1729540005 [TCP segment of a reassembled PDU] 600 14.237607 10.86.96.177 10.85.195.199 TCP 66 50514 > 8080 [ACK] Seq=855 Ack=5009 Win=40704 Len=0 TSval=1729540036 TSecr=400875988 ...... ..... .... ...

@FlareImp I guess you need to elaborate a bit more on how your whole network is structured for us to be able to understand and give appropriate information.

@kermit1991 this is most likely the php version you’re using. I’m just guessing it’s 7.2? The message won’t hurt anything and some work has gone in to limit these messages too.

@tom-elliott Thank you, I will follow the step and let you know if I run into problems.

Tom

@tywyn Glad you got it working. There’s been a whole lot of improvements around partitions and resizing in the last year, so it must be an issue with 1.4.4 in your case.

@tom-elliott THANK YOU! No, I didn’t do that. I simply reinstall/refresh fog with those settings. After reinstall, fog keep settings and run ok!thank you again!

It also appears you’re missing the actual FOG-API-TOKEN header.
E.G. Try:

curl -H 'fog-api-token: YourFOGAPITokenHere' -H 'Content-type: application/json' -u api:password 'http://fog.home/fog/task/active' -vvv

@sarge_212 Once you have the git repo locally then when fog 1.5.3 is released you can follow my initial instructions about git pull to download the updates.

@tom-elliott dumb question found how to enable plugins.

@tneuber What server OS is this? Did you change php.ini settings? Are you able to use the Web UI without issue? The message seen on screen is a PHP message. Take a look at the PHP ini file on your system an set an appropriate timezone. Depending on your OS the INI can be in different locations. On my debian server I have it in /etc/php/7.0/apache2/php.ini. Should be somewhere along this line on yours as well.

OU Drop Down option is kind of confusing to setup, but it does work.

Each OU is separated with a |

The “default” OU is marked with a ; at the end.

What this means is:

OU1|OU2;|OU3|OU4

Will create a dropdown of:
OU1
OU2
OU3
OU4
with OU2 being the default selected one.

Hopefully this helps.

Mind you all this is is a dropdown, you still have to make the choices and update the hosts/groups in question for this to apply.

@sebastian-roth The issue was changing the LAN boot selection from UEFI to CSM Boot. Thanks all!

@george1421 said in Feasibility of upgrading from 1.3.5 - Network issues:

@joshghz said in Feasibility of upgrading from 1.3.5 - Network issues:

So to clarify, RSTP has to be enabled on all client ports/switches, not just the one the FOG server is connected to?

Yes client ports only, (typically) the fog server never winks the network link at all while running. This issue is exactly between the pxe booting computer and the building switch.

Yeahhhhhh, that’s what I was afraid of. I’ll have a chat with him at some stage, but I’m going to guess this endeavour may have to wait until we get the Merakis.

Thanks anyway! It was really helpful to suss this out. 🙂

@coxm said in Dashboard Bandwidth graph not showing traffic:

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

Though I am not an expert on the inter FOG node communication I’d advise you to run the same version of FOG on all your nodes and see if that helps.

@vince-villarreal Try to add a group and see what the ID is.