It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×4,712
×1,192

question asked: Oct 21 '14, 7:44 p.m.
question was seen: 5,740 times
last updated: Jul 29 '15, 11:04 p.m.

Related questions

BuildForge 33G db.log

0
Jirong Hu (1.5k●9●295●258) | asked Oct 21 '14, 7:44 p.m.
In my production server, the D:\Program Files\IBM\Build Forge\db.log is 33G now. The doc says it's BF log and PHP log, can I just delete it? 

http://pic.dhe.ibm.com/infocenter/bldforge/v8r0/index.jsp?topic=%2Fcom.ibm.rational.buildforge.doc%2Ftopics%2Fpostinst_logs.html


One answer

Most liked answers ↑|Newest answers|Oldest answers

1
permanent link
Ryan Ruscett (1.0k●4●13) | answered Oct 22 '14, 8:09 a.m.
Hello, 

It is safe to go ahead and delete the log. Build Forge will auto-generate a new one and start logging from that point forward. 


The db.log is primarily only used to debug issue when Build Forge starts up or when using advanced debugging. It does record agent connectivity tests, but since the UI has agents with a red x when unavailable. It does not offer a whole lot in way of debugging anything else. 

If you have say 100 servers but only 25 are on at any given time and server test are set even semi frequent. Then the db.log can grow over time as it records failed server tests that you already know will fail because they are off. Although, you may want frequent server tests to occur so depending on the situation. You could delete the logs every few months to ensure they do not grow to large. 


Thanks!





Comments
Jirong Hu commented Jul 29 '15, 11:04 p.m.

 Hi Ryan


Thanks for the answer, why BF is generating so much log, is there a way to make it less or turn it off?

Thanks
Jirong

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.