Bug 17264 - freeswitch service will not start
Summary: freeswitch service will not start
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Daniel Lucio
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-01 05:53 CET by Forrest White
Modified: 2018-10-07 15:36 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Forrest White 2015-12-01 05:53:40 CET
Description of problem:
freeswitch service wont start and fusionpbx wont create database's.

Version-Release number of selected component (if applicable):

1.4.15 current stable 1.6.5.
How reproducible:
worked with freewitch dev team via freenode requires many patches for it to install and work at all

Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 David Walser 2015-12-01 13:31:19 CET
An upstream developer on IRC said:
- all sources needed should be included as SOURCES so that they aren't downloaded during the build process
- it needs to build with its bundled apr library rather than the system one
- any patches in our package should be submitted upstream for review

Assignee: bugsquad => luis.daniel.lucio

David Walser 2015-12-01 13:31:53 CET

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=17252

David Walser 2015-12-01 13:32:21 CET

Summary: freeswitch => freeswitch service will not start

Comment 2 Marja Van Waes 2018-04-18 09:01:55 CEST
Hi Forrest,

Thank you for having taken the needed time to report this issue!

Did this bug get fixed? If so, please change its status to RESOLVED - FIXED

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues.

If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard.

Thanks,
Marja

CC: (none) => marja11

Comment 3 Marja Van Waes 2018-10-07 15:36:02 CEST
@ Forrest:

No reply, so closing as OLD since Mageia 5 is no longer maintained.

==> If you didn't reset your password after February 2018, then you'll need to reset it here https://identity.mageia.org/forgot_password to be able to log in and comment in this report. <==

Resolution: (none) => OLD
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.