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.

Sign up for GitHub

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

Jump to bottom

Update to have Hedera node use the output directory instead of the logs directory #134

Closed
1 task
Tracked by #47
jeromy-cannon opened this issue Mar 6, 2024 · 0 comments · Fixed by #274
Closed
1 task
Tracked by #47

Update to have Hedera node use the output directory instead of the logs directory #134

jeromy-cannon opened this issue Mar 6, 2024 · 0 comments · Fixed by #274
Assignees
@JeffreyDallas
Labels
P2 Required to be completed in the assigned milestone, but may or may not impact release schedule.

Comments

@jeromy-cannon
Copy link
Contributor

jeromy-cannon commented Mar 6, 2024 •
edited

The output directory is part of the PersistentVolumeClaims when enabled, and output is what is used for production.

Therefore, we should update the log4j2.xml and any other reference to use the output directory instead of the logs directory.

Also remove references to Network Nodes logs directory from Solo. If it is still created from the charts side, open a similar issue for getting this updated in the full-stack-testing repo.
@jeromy-cannon jeromy-cannon mentioned this issue Mar 6, 2024
Open
@jeromy-cannon jeromy-cannon self-assigned this Mar 6, 2024
@jeromy-cannon jeromy-cannon added the P2 Required to be completed in the assigned milestone, but may or may not impact release schedule. label Mar 6, 2024
This was referenced May 7, 2024
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JeffreyDallas JeffreyDallas

Labels
P2 Required to be completed in the assigned milestone, but may or may not impact release schedule.
Projects
Solo
Status: ✅ Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore: update log4j2 to align with hedera repo hashgraph/solo
3 participants
@jeromy-cannon @JeffreyDallas @matteriben