(standar_in) syntax error

Developers Misc Dev Talk
,
1

We have this problem, BP and other relay no issue, but afterupgrade to 1,35,2 and gliveview update, the trouble started, we rolled back to 1.34 and reverted glive back to 1.26.5 and we get this error. we are really struggling to figure out the cause, any switches or setting that could help identify the problem? As far as we can ascertain, the files and servers are identical, apart from topology and env port number.
Apart from ideas on what might be the problem, some clues on any settings in the glive view would be great to help point the finger.

    > Cardano Node - (Relay - Mainnet) : 1.34.0 [c23d5d31] < 

> ┌────────────────────────────────┬────────────┬────────────────────────┐
> │ Uptime: 19230d 08:09:33        │ Port: 3001 │ Guild LiveView v1.26.4 │
> │--------------------------------└────────────┴────────────────────────┤
> │ Epoch 0 [0.0%], 2d 13:35:18 remaining                                │
> │ ▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖ │
> │                                                                      │
> │ Block      : 0         Tip (ref)  : 69935082  Forks      :           │
> │ Slot       : 0         Status     : starting  Total Tx   : 0         │
> │ Slot epoch : 0         Density    : 0.0       Pending Tx : 0/0K      │
> │- CONNECTIONS --------------------------------------------------------│
> │ P2P        : disabled  Incoming   : 0         Outgoing   : 0         │
> │- BLOCK PROPAGATION --------------------------------------------------│
> │ Last Delay : 0.00s     Served     :           Late (>5s) :           │
> (standard_in) 1: syntax error
> │ Within 1s  : 0.00%     (standard_in) 1: syntax error
> Within 3s  : 0.00%                              (standard_in) 1: syntax error
> Within 5s  : 0.00%                                                     │
> │- NODE RESOURCE USAGE ------------------------------------------------│
> │ CPU node   : 241%      Mem (Live) : 4.5G      GC Minor   : 40022     │
> │ Mem (RSS)  : 8.3G      Mem (Heap) : 8.3G      GC Major   : 160       │
> └──────────────────────────────────────────────────────────────────────┘
>  TG Announcement/Support channel: t.me/guild_operators_official
2

You should not use 1.35.2 as it has a serious bug. You’ll have to upgrade to 1.35.3 as this is the one ready for Vasil. Because of this bug 1.35.2 should not (!!!) run on mainnet. Please upgrade immediately!

Regarding your issue: it is just a problem with the gLiveView script. I’m using v1.26.2 together with 1.35.3 node release. In that combination there are no syntax errors.

1 Like
3

Thanks, the upgrade basicly destroyed the env file. we rolled back to 1.34, we are smart enough only to do it on 1 relay till we confirm all working, so no damage, just experience. on saying that. we may stay on 1.34 until we see a more reliable roll out of 1.35.

4

Since over 70% of nodes have been upgraded to 1.35.3 - which is also the official release for the Vasil hard fork - the hard fork itself will happening rather sooner than later. It is even possible that it happens with the next epoch. This will make your nodes stop minting blocks as 1.34 is not ready for Babbage era.