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

bbb_recordings_published error #23

Closed
penguennoktanet opened this issue May 5, 2020 · 9 comments
Closed

bbb_recordings_published error #23

penguennoktanet opened this issue May 5, 2020 · 9 comments
Labels
support

Comments

@penguennoktanet
Copy link

One of my servers declare bbb_recordings_published is 0. But bbb-record shows published records and /var/bigbluebutton/published/presentation has 996 folders.

If you reqire any additional data, please let me know...
@greenstatic
Copy link
Owner

bbb_recordings_published 0 does Grafana report this or the raw metrics of the exporter?

The correct way to approach this is to figure out of BBB is reporting the wrong value in it's XML API or if the exporter has a bug.

I just updated the documentation with the instructions how to view the XML API responses the exporter gets from BBB. I suggest you take a look if the XML API response contains these published recordings or not.

@greenstatic
Copy link
Owner

Have you managed to figure out your issue?

@penguennoktanet
Copy link
Author

Sorry for late response. I was too busy with other stuff.

bbb_recordings_published 0 does Grafana report this or the raw metrics of the exporter?

They both report the same value. But here is the catch (output from the BBB-exporter);
bbb_recordings_published 0.0 bbb_recordings_deleted 0.0 bbb_api_latency_count{endpoint="getRecordings",parameters="state=published"} 8187.0 bbb_api_latency_count{endpoint="getRecordings",parameters="state=unpublished"} 8187.0 bbb_api_latency_count{endpoint="getRecordings",parameters="state=deleted"} 8187.0

I just updated the documentation with the instructions how to view the XML API responses the exporter gets from BBB. I suggest you take a look if the XML API response contains these published recordings or not.

Seems like I could not enable the debug mode (I hate docker, never care to learn it in detail). But when I traced logs of it, I saw this;

bbb-exporter | 2020-05-13 07:45:16,396 [INFO]: Collecting metrics from BigBlueButton API bbb-exporter | 2020-05-13 07:45:36,340 [INFO]: Collecting metrics from BigBlueButton API bbb-exporter | 2020-05-13 07:46:21,859 [ERROR]: Non 2xx HTTP status code response bbb-exporter | 2020-05-13 07:46:21,859 [ERROR]: <html> bbb-exporter | <head><title>404 Not Found</title></head> bbb-exporter | <body bgcolor="white"> bbb-exporter | <center><h1>404 Not Found</h1></center> bbb-exporter | <hr><center>nginx/1.10.3 (Ubuntu)</center> bbb-exporter | </body> bbb-exporter | </html>

@greenstatic
Copy link
Owner

I suggest you update to the recently released v0.3.0 and if you don't like Docker, we have a Systemd installation guide. You can also add DEBUG=true to the Systemd installation to enable detailed logs.

The error you posted seems like:

  1. The exporter is visiting the wrong API endpoint. This could be caused by a miss configured API_BASE_URL, but if you are getting proper metric values for other metrics this shouldn't be the case.
  2. You have a miss configured Nginx config that has some weird location rewrite rules.

@penguennoktanet
Copy link
Author

penguennoktanet commented May 13, 2020 •
edited
Loading

I suggest you update to the recently released v0.3.0 and if you don't like Docker, we have a Systemd installation guide. You can also add DEBUG=true to the Systemd installation to enable detailed logs.

I always deploy with "BBB_EXPORTER_VERSION=latest docker-compose up -d".

Nice touch on systemd installation. That wasn't there when I setup the systems (or I missed them). If I got some spare time, I will switch to systemd (old habits die hard, I still miss SysVinit scripts :) )

The error you posted seems like:

  1. The exporter is visiting the wrong API endpoint. This could be caused by a miss configured API_BASE_URL, but if you are getting proper metric values for other metrics this shouldn't be the case.

That's right. bbb_meetings, bbb_meetings_participants, bbb_meetings_listeners etc seems to be fine.

  1. You have a miss configured Nginx config that has some weird location rewrite rules.

Don't think that's the issue because of 2 reasons;

  1. That metric was good after the installation and for following 6 weeks.
  2. Some of the servers' published counts seem ok with no meeting on going. But when the meetings start and servers CPU usage raises (notting critical, %30-40 usage only) number seems to be malfunctioning.
    If I have some time, I will switch to systemd and debug the code..

@greenstatic
Copy link
Owner

Im not sure if BBB_EXPORTER_VERSION=latest docker-compose up -d" pulls the latest docker image every time.

Yes you are correct, the systemd installation guide was added recently.

Good luck debugging, do report back with your findings :).

@penguennoktanet penguennoktanet mentioned this issue May 19, 2020
Closed
@greenstatic
Copy link
Owner

Are you still experiencing this issue in v0.4.0?

@greenstatic
Copy link
Owner

Closing this for now. If you experience the issue again, reopen this issue or open another one.

@SimonBrigadier
Copy link

We have a similar problem. bbb_recordings_deleted has the following value: -4481.0, but the folders in /var/bigbluebutton/deleted/presentation/: 7 and API https:///bigbluebutton/api/getRecordings?state=deleted also give 7 records. I turned on the debug mode, I do not see anything problematic in the logs. I used the v0.6.0 exporter image, I also tried to run both v0.5.1 and v0.5.2, but the result is the same. The path /var/bigbluebutton is available to the exporter because bbb_recordings_published and bbb_recordings_unpublished are correct. Before that, we migrated the bbb server from the bbb22 version to the bbb24 version and copied only /var/bigbluebutton/published/, /var/bigbluebutton/unpublished/ and /var/bigbluebutton/recording/raw/ from the old server due to the large volume of records. Could this somehow affect bbb_recordings_deleted? What else can be done to solve this problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
support
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@greenstatic @penguennoktanet @SimonBrigadier