[Testnet][Devops] Rework on zk server setup

[thomas-nguy]

Current setup use a basic linux service with auto restart

[Unit]
Description=zkSync Server
After=network.target

[Service]
WorkingDirectory=/chain/data
Environment="ZKSYNC_HOME=/chain/data/zksync-era"
ExecStart=/bin/bash /chain/data/zk-binaries/run-server.sh
Restart=always
User=crypto

[Install]
WantedBy=multi-user.target

The log is using stdout, not ideal for debugging. It would be better to send them to files or remote log viewer

Different processed and alert systems needs to be defined :

• In case the circuit breaker is trigered, the server will be unable to restart unless it is deblocked by admin.
• In case the eth sender wallet to L1 run out of fund, the server will stop operating.

[thomas-nguy]

Node url

10.202.3.175

[JayT106]

the linux systemd will put the stdout/stderr into journal logs. we can export the journal log to the designated file or location.

I added a journal service for zksync-server and put it into /chain/data/script folder it will export output to /chain/data/log/zksync-server

[JayT106]

pushed commit to https://github.com/cronos-labs/l2-testnets/commit/88c3f6aec60c5c92e59c33f1f537280a69ff5b18

[thomas-nguy]

for alert & monitoring, we can maybe use of grafana (https://github.com/cronos-labs/zksync-era/issues/18) which support slack notification

[thomas-nguy]

closing because this task will be moved to devops