problem on the beacond-v0.2.0-alpha.5-linux-amd64

[reza-bcw]

when I update to newversion I mean beacond-v0.2.0-alpha.5 I got error in the below

Aug 27 12:14:01 berachain-testnet beacond[2149241]: Global Flags:
Aug 27 12:14:01 berachain-testnet beacond[2149241]:       --home string   directory for config and data (default "/root/.beacond")
Aug 27 12:14:01 berachain-testnet beacond[2149241]: 2024/08/27 12:14:01 ERROR startup failure error="unknown flag: --log_level"
Aug 27 12:14:01 berachain-testnet systemd[1]: beacond.service: Main process exited, code=exited, status=1/FAILURE
Aug 27 12:14:01 berachain-testnet systemd[1]: beacond.service: Failed with result 'exit-code'.
Aug 27 12:14:01 berachain-testnet systemd[1]: beacond.service: Scheduled restart job, restart counter is at 5.
Aug 27 12:14:01 berachain-testnet systemd[1]: Stopped Beacon Daemon Service.
Aug 27 12:14:01 berachain-testnet systemd[1]: beacond.service: Start request repeated too quickly.
Aug 27 12:14:01 berachain-testnet systemd[1]: beacond.service: Failed with result 'exit-code'.
Aug 27 12:14:01 berachain-testnet systemd[1]: Failed to start Beacon Daemon Service.
^C
root@berachain-testnet:/home/reza_bcw_group# systemctl status beacond
× beacond.service - Beacon Daemon Service
     Loaded: loaded (/etc/systemd/system/beacond.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Tue 2024-08-27 12:14:01 UTC; 19s ago
    Process: 2149241 ExecStart=/usr/bin/beacond start --pruning=nothing --log_level info --api.enabled-unsafe-cors --api.enable --api.swagger --minimum-gas-prices=0.0001abgt --home /data/ --beacon>
   Main PID: 2149241 (code=exited, status=1/FAILURE)
        CPU: 75ms

Aug 27 12:14:01 berachain-testnet systemd[1]: beacond.service: Scheduled restart job, restart counter is at 5.
Aug 27 12:14:01 berachain-testnet systemd[1]: Stopped Beacon Daemon Service.
Aug 27 12:14:01 berachain-testnet systemd[1]: beacond.service: Start request repeated too quickly.
Aug 27 12:14:01 berachain-testnet systemd[1]: beacond.service: Failed with result 'exit-code'.
Aug 27 12:14:01 berachain-testnet systemd[1]: Failed to start Beacon Daemon Service.

[kalidux]

@reza-bcw, in the logs, I noticed the error: error="unknown flag: --log_level". It looks like there might be a typo. The correct flag could be --log-level ?

You can try the following steps to test this:

Open the systemd service file for beacond. The file should be located at /etc/systemd/system/beacond.service.

Find the ExecStart line and modify the command to use the correct flag (try using --log-level instead of --log_level).

Once you've made the change, run the following commands to reload the systemd daemon and restart the service:

sudo systemctl daemon-reload
sudo systemctl start beacond
sudo systemctl status beacond

This should help troubleshoot the startup issue.

[reza-bcw]

not fixed

root@berachain-testnet:/home/reza_bcw_group# sudo systemctl status beacond
× beacond.service - Beacon Daemon Service
     Loaded: loaded (/etc/systemd/system/beacond.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Tue 2024-09-03 04:49:43 UTC; 17s ago
    Process: 2166213 ExecStart=/usr/bin/beacond start --pruning=nothing --log-level info --api.enabled-unsafe-cors --api.enable --api.swagger --minimum-gas-prices=0.0001abgt --home /data/ --beacon>
   Main PID: 2166213 (code=exited, status=1/FAILURE)
        CPU: 75ms

Sep 03 04:49:43 berachain-testnet systemd[1]: beacond.service: Scheduled restart job, restart counter is at 5.
Sep 03 04:49:43 berachain-testnet systemd[1]: Stopped Beacon Daemon Service.
Sep 03 04:49:43 berachain-testnet systemd[1]: beacond.service: Start request repeated too quickly.
Sep 03 04:49:43 berachain-testnet systemd[1]: beacond.service: Failed with result 'exit-code'.
Sep 03 04:49:43 berachain-testnet systemd[1]: Failed to start Beacon Daemon Service.
lines 1-12/12 (END)

[reza-bcw]

ERROR startup failure error="unknown flag: --log-level"

[reza-bcw]

I think this version has problem becsue I don't have any problme with v4

[kalidux]

Thanks @reza-bcw Weird, probably a binary issue. If you want you can try and remove "--log_level info" in /etc/systemd/system/beacond.service and see if it will start ?

[reza-bcw]

I removed it but it doesn't work also I check it v6 but it doesn't work I mean new version

root@berachain-testnet:/home/reza_bcw_group# journalctl -u beacond -f
Sep 06 06:10:01 berachain-testnet beacond[2174909]: Global Flags:
Sep 06 06:10:01 berachain-testnet beacond[2174909]:       --home string   directory for config and data (default "/root/.beacond")
Sep 06 06:10:01 berachain-testnet beacond[2174909]: 2024/09/06 06:10:01 ERROR startup failure error="unknown flag: --api.enabled-unsafe-cors"
Sep 06 06:10:01 berachain-testnet systemd[1]: beacond.service: Main process exited, code=exited, status=1/FAILURE
Sep 06 06:10:01 berachain-testnet systemd[1]: beacond.service: Failed with result 'exit-code'.
Sep 06 06:10:01 berachain-testnet systemd[1]: beacond.service: Scheduled restart job, restart counter is at 5.
Sep 06 06:10:01 berachain-testnet systemd[1]: Stopped Beacon Daemon Service.
Sep 06 06:10:01 berachain-testnet systemd[1]: beacond.service: Start request repeated too quickly.
Sep 06 06:10:01 berachain-testnet systemd[1]: beacond.service: Failed with result 'exit-code'.
Sep 06 06:10:01 berachain-testnet systemd[1]: Failed to start Beacon Daemon Service.

[reza-bcw]

I can not update to v6 because of this issue

[abi87]

Hello @reza-bcw, you should set the log level via --beacon-kit.logger.log-level=info flag. This is what make start also does. Please update your flag and let me know if it works for you.

[chuck-bear]

@reza-bcw I believe that this has been resolved? As your node seems to be working and no message from you about that on Discord.

[reza-bcw]

yes it resolved