Freeswitch error after upgrade

Status
Not open for further replies.

ropeguru

New Member
Feb 28, 2019
25
1
3
55
Hey all... After a long time with not updating my system, like 6 months or so, I went through the process.

First issue I had was the one back from May with the web page not coming back up and I have that fixed. Now I have an issue with freeswitch not wanting to start and complaing about a line in the xml.

Here is the freeswitch error:

2020-07-18 14:07:12.709531 [INFO] switch_event.c:710 Activate Eventing Engine.
2020-07-18 14:07:12.719938 [WARNING] switch_event.c:680 Create additional event dispatch thread 0
Cannot Initialize [[error near line 894]: unexpected <]


Here is the config in the area of that line number:

<fifos>
<<<<<<< HEAD
<fifo name="cool_fifo@" importance="0">
<!--<member timeout="60" simo="1" lag="20">{member_wait=nowait}user/1005@</member>-->
</fifo>
=======
<!--
<fifo name="cool_fifo@" importance="0">
<member timeout="60" simo="1" lag="20">{member_wait=nowait}user/1005@</member>
</fifo>
-->
>>>>>>> 1b38c9541d5334ac92c4262700b068be3d1696c6
</fifos>


Has there been an issue from earlier in the year that I just have not found? On my original update and running the upgrade.php from the command line of the OS, it was hitting a syntax error due to the same bit of code with "<<<<<<< HEAD" in it.

Appreciate any help..
 

ropeguru

New Member
Feb 28, 2019
25
1
3
55
For what its worth, here is the pup error I was receiving before the FusionPBX fix.

2020/07/18 13:34:24 [error] 4451#4451: *4 FastCGI sent in stderr: "PHP message: PHP Parse error: syntax error, unexpected '<<' (T_SL), expecting end of file in /var/www/fusionpbx/resources/require.php on line 70" while reading response header from upstream, client: 192.168.1.113, server: fusionpbx, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php/php7.1-fpm.sock:", host: "192.168.1.80"
 

ropeguru

New Member
Feb 28, 2019
25
1
3
55
FInally got it sorted...

Apparently the '<<<<<<< HEAD', ' ======= ', and ' >>>>>>> 1b38c9541d5334ac92c4262700b068be3d1696c6 ' text had found its way into several of the Freeswitch xml files. Once I tracked all those down and deleted them, freeswitch started right up...

Sorry for the noise..
 
Status
Not open for further replies.