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

Enable bbb-conf to set logging levels #1661

Open
bigbluebutton-issue-import opened this issue Aug 12, 2015 · 7 comments
Open

Enable bbb-conf to set logging levels #1661

bigbluebutton-issue-import opened this issue Aug 12, 2015 · 7 comments

Comments

@bigbluebutton-issue-import

Originally reported on Google Code with ID 906

Enable bbb-conf to set the logging levels for

  bigbluebutton (red5 application)
  bigbluebutton-sip (red5 application)
  biglbuebutton-video (red5 application)
  bigbluebutton (tomcat)
  deskshare (scala)

The syntax would be

   bbb-conf --setloglevel [DEBUG | INFO | WARN | ERROR]

This will reduce the logging on a production server and make it easier to spot errors.


Reported by ffdixon on 2011-03-22 02:11:51

@bigbluebutton-issue-import
Copy link
Author

bigbluebutton-issue-import commented Aug 12, 2015

Reported by ffdixon on 2013-12-15 15:46:21

  • Labels added: Milestone-Release0.9.0

@bigbluebutton-issue-import
Copy link
Author

bigbluebutton-issue-import commented Aug 12, 2015

This is much appreciated feature for servers with limited power. also people hosting.

Reported by girishsan101 on 2014-01-06 21:53:22

@bigbluebutton-issue-import
Copy link
Author

bigbluebutton-issue-import commented Aug 12, 2015

Reported by ffdixon on 2014-05-20 13:25:25

@bigbluebutton-issue-import
Copy link
Author

bigbluebutton-issue-import commented Aug 12, 2015

Reported by ritzalam on 2014-06-26 19:30:21

  • Labels removed: Milestone-Release0.9.0

@bigbluebutton-issue-import
Copy link
Author

bigbluebutton-issue-import commented Aug 12, 2015

Reported by ffdixon on 2015-04-04 13:38:31

@stale
Copy link

stale bot commented Dec 28, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale
Copy link

stale bot commented Oct 7, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the status: stale label Oct 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants