You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "Appdev (Jira)" <ji...@apache.org> on 2020/04/05 00:23:00 UTC

[jira] [Created] (OPENMEETINGS-2224) Multimedia Server Is Inaccessible (CentOS 7)

Appdev created OPENMEETINGS-2224:
------------------------------------

             Summary: Multimedia Server Is Inaccessible (CentOS 7)
                 Key: OPENMEETINGS-2224
                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2224
             Project: Openmeetings
          Issue Type: Bug
          Components: Audio/Video, Recordings
    Affects Versions: 5.0.0-M3
         Environment: Here are my basic specs: CentOS Linux release 7.7.1908, MySQL version: 10.1.44-MariaDB. 
            Reporter: Appdev
            Assignee: Maxim Solodovnik


Hi:

I notice this issue has been discussed in a number of previous threads but I do not see a resolution in those threads. Sorry to have to open this up again. I have installed OM5.0.0-M3 on Centos7. I followed the [instructions|https://cwiki.apache.org/confluence/download/attachments/27838216/Installation%20OpenMeetings%205.0.0-M3%20on%20Centos%207.pdf?version=3&modificationDate=1579175324000&api=v2]  and the process completed "successfully". I was able to log into the application and effect the customizations. No problem there. 

KMS is running. (I have started, stopped and restarted it to confirm it is running.) I have changed permissions on the OM files to the user account.

1) However, when I start a conferencing session I get "Multimedia Server Is Inaccessible". There are usually several warnings at once indicating that several processes are failing. (You can go through the setup of a conference but once you enter a room, that failure occurs, and does so frequently during a session.)

2) Also I am unable to get the video feed of ANY participants in a conferencing session to work.

Please assist on how to resolve this. Clearly this is an issue with KMS but it's unclear how to proceed.

Thanks.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)