Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How many log files to keep archived setting is set to 0 #14889

Open
anastasiyaig opened this issue May 23, 2024 · 4 comments
Open

How many log files to keep archived setting is set to 0 #14889

anastasiyaig opened this issue May 23, 2024 · 4 comments
Assignees
Labels
backend-team bug Something isn't working
Milestone

Comments

@anastasiyaig
Copy link
Contributor

Bug Report

Description

How many log files to keep archived setting is set to 0

Steps to reproduce

  1. install the last 2.29 / master from scratch
  2. open advanced and check the logs item

Expected behavior

Should be defaulted to 1

Actual behavior

Screenshot 2024-05-23 at 12 47 27 Screenshot 2024-05-23 at 12 47 30

Additional Information

  • Status desktop version: 2.29 or master from may-23-2024
  • Operating System: macOS Sonoma 14.4.1
@anastasiyaig anastasiyaig added bug Something isn't working ui-team labels May 23, 2024
@caybro
Copy link
Member

caybro commented May 23, 2024

For a new user, this is coming back as 0. As part of testing, I also tried changing it to 2 but it results in:

image

Something is definitely wrong with the node config, meaning I can no longer log in :/

Console output:

DBG 2024-05-23 12:52:12.528+02:00 app state changed                          tid=567346 file=view.nim:130 state=AppLoadingState
DBG 2024-05-23 12:52:12.537+02:00 database reencryption scheduled            topics="accounts-service" tid=567346 file=service.nim:693
DBG 2024-05-23 12:52:12.537+02:00 [threadpool task thread] initiating task   topics="task-threadpool" tid=567510 file=threadpool.nim:54 messageType=TimerTaskArg:ObjectType threadid=567510 task="{\"$type\":\"TimerTaskArg:ObjectType\",\"timeoutInMilliseconds\":1000,\"reason\":\"\",\"vptr\":35714448,\"slot\":\"onWaitForReencryptionTimeout\",\"tptr\":9988080}"
DBG 2024-05-23 12:52:13.539+02:00 starting database reencryption             topics="accounts-service" tid=567346 file=service.nim:716
failed to set `journal_mode` pragma: file is not a database
DBG 2024-05-23 12:52:13.804+02:00 account logged in                          topics="accounts-service" tid=567346 file=service.nim:677
ERR 2024-05-23 12:52:14.340+02:00 node.crashed                               topics="signals-manager" tid=567346 file=signals_manager.nim:58 error="{\"type\":\"node.crashed\",\"event\":{\"error\":\"TorrentConfig.DataDir and TorrentConfig.TorrentDir cannot be \\\"\\\"\"}}"
ERR 2024-05-23 12:52:14.340+02:00 node.login                                 topics="signals-manager" tid=567346 file=signals_manager.nim:54 error="TorrentConfig.DataDir and TorrentConfig.TorrentDir cannot be \"\""
DBG 2024-05-23 12:52:14.340+02:00 app state changed                          tid=567346 file=view.nim:130 state=StartupState
ERR 2024-05-23 12:52:14.342+02:00 login error                                topics="app-controller" tid=567346 file=module.nim:419 methodName=onNodeLogin errDesription="TorrentConfig.DataDir and TorrentConfig.TorrentDir cannot be \"\""

@caybro
Copy link
Member

caybro commented May 23, 2024

CC @jrainville

@friofry
Copy link
Contributor

friofry commented May 23, 2024

I think it will be fixed after #12918 because setMaxLogBackups may corrupt the NodeConfig

(currently I'm working on this)

@jrainville jrainville added this to the 2.30.0 Beta milestone May 23, 2024
@caybro
Copy link
Member

caybro commented May 23, 2024

I think it will be fixed after #12918 because setMaxLogBackups may corrupt the NodeConfig

(currently I'm working on this)

Great, this is what I ran into above I think

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend-team bug Something isn't working
Projects
Status: Done
Development

No branches or pull requests

4 participants