gemba

Forum Replies Created

Viewing 6 posts - 1 through 6 (of 6 total)
  • Back to forum
    Posted in: Current progress and more – 9.5 status
  • gemba
    27th January 2020 at 9:46 am #28229

    Hi Leonardo,

    Ticket Created

    Thank you.

    gemba
    27th January 2020 at 8:56 am #28225

    Hi Leonardo,

    Thanks for your reply.

    Currently the main version is V9 (9.0.13),
    We will switch to V9 LTS (9.0.14-11518).
    In addition, we are testing the operation this time with V9 LTS.

    gemba
    27th January 2020 at 5:37 am #28217

    Hi Leonardo,

    Thanks for your reply.

    Since it was any port of 7,9,40000 / UDP, I tried to capture with the following pattern.
    Also, taking into account the possibility of jumping to a random port, we tried to capture the entire UDP packet, rewrite the filter of tcpdump to filter only some UDP / SSH packets, and tried to capture.
    The result is as follows:
    tcpdump command:
    tcpdump -i eth0 -ne src host 172.16.203.182 and udp port not \(137 or 138 or 546 or 5355 or 5353 or 1947 or 4679 \) and tcp port not 22 and not arp

    Note:
    　172.16.203.182 ― Dispatcher IP
    　172.16.203.88 ― Node IP

    Result:
    – “When the farm is at full load” Only　-> Success

    Dispatcher log: 12:50:02 Waking up host gem88(172.16.203.88) - Farm at full load
tcpdump log: 12: 50: 03.890666 26: c6: cb: 9e: a8: 39> Broadcast, ethertype IPv4 (0x0800), length 144: 172.16.203.182.33749> 255.255.255.255.safetynetp: UDP, length 102

    – “When the client is required by a job pool” Only -> Success

    Dispatcher log: 13:05:10 Waking up host gem88(172.16.203.88) - required pool
tcpdump log: 13: 05: 11.276099 26: c6: cb: 9e: a8: 39> Broadcast, ethertype IPv4 (0x0800), length 144: 172.16.203.182.51160> 255.255.255.255.safetynetp: UDP, length 102

    – Schedule Only -> Failure
      Day range, Mon-Fri, 10: 00-20: 00, wake up

     Dispatcher log: 12:03:55 Waking up host gem88(172.16.203.88) - Host matched time rule 
  tcpdump log: not logging

    – Schedule and Available match rule. -> Failure
    Day range, Mon-Fri, 10: 00-20: 00, wake up
    　(Wake-up schedule and available schedule are at the same time.)
    tcpdump log : not logging
    `

    Considering the possibility of our environmental problems, we set up another server,
    The result was the same as above.
    Are others working?

    Thanks.
    Wakabayashi

    gemba
    20th January 2020 at 5:55 am #27877

    Hi Leonardo,

    Thanks for your reply.

    We have confirmed that the dispatcher server (CentOS 7) can be started from the server using Ether-Wake or a self-made script that sends WoL packets to UDP port 7 or 9.

    At the timing when the log that executed WoL by the dispatcher was output, packets could not be captured by tcpdump, and it was not possible to confirm whether or not they were being executed.

    Packet capture command
    tcpdump -UlnXi eth0 ether proto 0x0842 or udp port 9 or udp port 7

    Is it possible to check in other ways?

    As additional information,
    Two options, “When the farm is at full load” and “When the client is required by a job pool”, performed WoL and confirmed that the node started.
    However, packets cannot be captured by tcpdump.

    Best regards.

    gemba
    5th September 2019 at 11:45 am #21401

    Hi Leonard.

    Thanks for your reply.

    One client was upgraded to 9.0.14 and it worked the same way, but the results were the same.

    – domain\render : User Locked # Account registered for service
    – domain\userA : idle # Designer account
    – admin : idle # Local Administrator account

    Can I send an email to “vinfo@vvertex.com”?

    Best regards.

    gemba
    5th September 2019 at 10:30 am #21395

    Hi Leonardo

    When “make client unavailable on user login” is enabled, the client status is as follows.

    – domain\render : User Locked # Account registered for service
    – domain\userA : idle # Designer account
    – admin : idle # Local Administrator account

    The version of Muster used is 9.0.13 for both Dispatcher and Client.

    Best regards.

Viewing 6 posts - 1 through 6 (of 6 total)