[Lerftest-ctrls] TZ/time issue with lcls-llrfcpu02
Slepicka, Hugo Henrique
slepicka at slac.stanford.edu
Fri Jun 1 15:30:41 EDT 2018
So here is what I did:
iocConsole lcls-llrfcpu02
>>> /etc/init.d/S49ntp stop
>>> ntpdate -s ntp1.jlab.org
>>> date
>>> /etc/init.d/S49ntp start
Now the date looks good too.
The history of lcls-llrfcpu01 shows that I did that also for that machine when we were first investigating this issue.
PS: I am done with the test that I needed to do.
Thank you,
Hugo
On 6/1/18, 12:17 PM, "Sonya Hoobler" <sonya at slac.stanford.edu> wrote:
Yes, fine with me, thanks.
Sonya
On Fri, 1 Jun 2018, Slepicka, Hugo Henrique wrote:
> Am I allowed to try something with lcls-llrfcpu02?
> I will need to eventually reboot it too.
>
> Thank you,
> Hugo
>
> On 6/1/18, 12:08 PM, "Lerftest-ctrls on behalf of Brobeck, Kenneth C." <lerftest-ctrls-bounces at jlab.org on behalf of brobeck at slac.stanford.edu> wrote:
>
> I didn't see anything about the NTP server.
>
> -----Original Message-----
> From: Lerftest-ctrls [mailto:lerftest-ctrls-bounces at jlab.org] On Behalf Of Wesley Moore
> Sent: Friday, June 01, 2018 11:53 AM
> To: lerftest-ctrls
> Subject: [Lerftest-ctrls] TZ/time issue with lcls-llrfcpu02
>
> Double checked the DHCP settings and cpu01/02 match (and the TZ is global to both, so no possible copy/paste errors). Here is the packet capture for cpu02. The TZ PCode looks right. However, only timezone is sent.
>
> Where does it get it's actual time? Are the config file on cpu01 and cpu02 the same?
>
> Bootstrap Protocol (Offer)
> Message type: Boot Reply (2)
> Hardware type: Ethernet (0x01)
> Hardware address length: 6
> Hops: 1
> Transaction ID: 0xf5a6e413
> Seconds elapsed: 5
> Bootp flags: 0x0000 (Unicast)
> 0... .... .... .... = Broadcast flag: Unicast
> .000 0000 0000 0000 = Reserved flags: 0x0000
> Client IP address: 0.0.0.0
> Your (client) IP address: 129.57.244.52
> Next server IP address: 129.57.244.200
> Relay agent IP address: 129.57.244.1
> Client MAC address: Advantec_28:bc:12 (74:fe:48:28:bc:12)
> Client hardware address padding: 00000000000000000000
> Server host name not given
> Boot file name: /usr/local/lcls/epics/iocCommon/lcls-llrfcpu02/startup.cmd
> Magic cookie: DHCP
> Option: (53) DHCP Message Type (Offer)
> Length: 1
> DHCP: Offer (2)
> Option: (54) DHCP Server Identifier
> Length: 4
> DHCP Server Identifier: 129.57.35.95
> Option: (51) IP Address Lease Time
> Length: 4
> IP Address Lease Time: (86400s) 1 day
> Option: (1) Subnet Mask
> Length: 4
> Subnet Mask: 255.255.255.0
> Option: (3) Router
> Length: 4
> Router: 129.57.244.1
> Option: (6) Domain Name Server
> Length: 12
> Domain Name Server: 129.57.236.40
> Domain Name Server: 129.57.212.60
> Domain Name Server: 129.57.90.255
> Option: (12) Host Name
> Length: 14
> Host Name: lcls-llrfcpu02
> Option: (15) Domain Name
> Length: 12
> Domain Name: acc.jlab.org
> Option: (17) Root Path
> Length: 36
> Root Path: 129.57.244.200:/usr/local:/usr/local
> Option: (28) Broadcast Address
> Length: 4
> Broadcast Address: 129.57.244.255
> Option: (100) PCode
> Length: 38
> TZ PCode: EST5EDT,M3.2.0/2:00:00,M11.1.0/2:00:00
> Option: (255) End
> Option End: 255
>
> Wesley
> _______________________________________________
> Mailing List: Lerftest-ctrls at jlab.org
> https://mailman.jlab.org/mailman/listinfo/lerftest-ctrls
> Wiki: https://wiki.jlab.org/lerf/index.php/Network
>
> _______________________________________________
> Mailing List: Lerftest-ctrls at jlab.org
> https://mailman.jlab.org/mailman/listinfo/lerftest-ctrls
> Wiki: https://wiki.jlab.org/lerf/index.php/Network
>
>
>
> _______________________________________________
> Mailing List: Lerftest-ctrls at jlab.org
> https://mailman.jlab.org/mailman/listinfo/lerftest-ctrls
> Wiki: https://wiki.jlab.org/lerf/index.php/Network
>
More information about the Lerftest-ctrls
mailing list