WCS Service getting failed

revanreddy · May 9, 2022

Hi,

When we start WCS service, the service is getting started successfully but after few seconds it's getting failed.

When we check the health status through logs as below:

[2022-03-30 11:26:36] ERROR start - FlashphonerWebCallServer started, but is not healthy, please try to restart

We have enclosed the server logs , startup logs and client logs for your reference

In addition to the above issue ..We are able access the WCS portal through https but it fails through http (8081 in firewall port is allowed )

Max · May 9, 2022

Hello

1. It seems you have permission issues

[2022-04-26 09:59:03] ERROR startServer - FlashphonerWebCallServer cannot be started from user flashphoner, please fix the permissions to the folders or run 'webcallserver set-permissions'!

Try before starting:

Code:

cd /usr/local/FlashphonerWebCallServer/bin
sudo ./webcallserver set-permissions

2. Make sure port 8081 is listening and not bound by another software

Code:

netstat -nlp | grep 8081

3. Make sure port 8081 is available from localhost

Code:

netstat -nlp | grep 8081

4. Ping port 8081 using telnet

Code:

telnet localhost 8081

5. Make sure your localhost is resolved to proper address:

Code:

ping localhost

Max · May 9, 2022

If the recommendations above did not help, please provide SSH access to the instance using this private form.

Max · May 10, 2022

If you cannot provide SSH access to the server, please collect a report as described here. Use report.sh script to collect the report

Code:

cd /usr/local/FlashphonerWebCallServer/tools
sudo ./report.sh --sysinfo --conf --stats --tar

Then, send the report archive using this private form.

revanreddy · May 10, 2022

Hi Max,

Max said:
Then, send the report archive using this private form.

As requested we have shared the report collected from the flashphoner server

When we start or restart the WCS server it failed immediately and showing the status as active(exited ) as referred in the following screenshot

Thanks.

Max · May 11, 2022

revanreddy said:
As requested we have shared the report collected from the flashphoner server

We checked the report.
Seems like you've changed HTTP port in flashphoner.properties file

Please remove the line

Code:

http.port  =18081

then server should work correctly

revanreddy said:
When we start or restart the WCS server it failed immediately and showing the status as active(exited ) as referred in the following screenshot

We do not see this in report provided.
Please uninstall WCS completely

Code:

sudo /usr/local/FlashphonerWebCallServer/bin/uninstall.sh

Then download the latest build 5.2.1193 and install it

Code:

tar -xzf FlashphonerWebCallServer-5.2.1193.tar.gz
cd FlashphonerWebCallServer-5.2.1193
sudo ./install.sh

Activate your license key on the instance: Activation using web interface
If the issue still persists, provide SSH access to the instance using this private form.

revanreddy · May 17, 2022

Hi Max,

We are still facing the same issue as mentioned earlier

"webcallserver.service: New main PID 777123 does not belong to service and PID file is not owned by root. refusing "

Do we need to have root privileges to install the WCS?

And we are getting an error as shown in attached image

Max · May 18, 2022

revanreddy said:
Do we need to have root privileges to install the WCS?

You must have a root privileges to install, uninstall or start WCS.
By default, WCS Java process is running as flashphoner user. You can run it as root user by changing

Code:

WCS_NON_ROOT=true

to

Code:

WCS_NON_ROOT=false

in /usr/localk/FlashphonerWebCallServer/bin/setenv.sh file. Then WCS must be restarted.

revanreddy said:
And we are getting an error as shown in attached image

Please collect and send the report as described in this post above.
Check also if you revert HTTP port changes as recommended above.

revanreddy · May 20, 2022

Hi Max,

Max said:
Please remove the line

As suggested above to remove the line "http.port =18081" but we have added it as 8081 used by some other process.

FYI, with 18081 port we are able to access the portal but streaming not working.

Otherwise, is there any alternative way to change the port to access WCS portal ?

Max · May 22, 2022

Hello

Port 8081 is used in two places.

1. As a web http port.
Example: http://demo.flashphoner.com:8081/admin/login.html

2. As internal REST hook endpoint.
For example, when you play stream, WCS will send REST hook to internal URL http://localhost:8081/apps/EchoApp/playStream

Therefore if you change http.port to 18081, then REST hook URL should be also changed to http://localhost:18081/apps/EchoApp

1. Sign in to CLI
ssh -p 2001 admin@localhost

2. show apps

3. update app -l "http://localhost:18081/apps/EchoApp" defaultApp

4. show apps

to control changes

Done.

Please note. If you change http.port you must change the URL via CLI. And back if you change URL you must change http.port.

Docs:

CLI
CLI - update app
CLI - commands
REST Hooks

revanreddy · May 26, 2022

Hi Max,

We have configured the port as suggested above, now we are getting following error when we tried streaming

Uncaught (in promise) TypeError: Cannot set properties of null (setting 'muted')
at flashphoner.js:14398:414617

We have collected the report to trace the issue . but we couldn't attach here please provide the link to attach the report

Max · May 27, 2022

revanreddy said:
We have configured the port as suggested above, now we are getting following error when we tried streaming

Uncaught (in promise) TypeError: Cannot set properties of null (setting 'muted')
at flashphoner.js:14398:414617

This is client side issue. Please chek if it is reproducing in Player example https://your_server:8888/client2/examples/demo/streaming/player/player.html. Please also clarify what WCS build and WebSDK build do you use, this is shown on admin page https://your_server:8888/admin/demo.html#

If the problem is reproducing in Player example, please show the browser console output.

Max · May 27, 2022

We removed the post with report attached because it contains license information. Use Report button to send any reports

The report itself shows that you're trying to play VOD, and it is successfully captured. Seems like WebRTC playback does not work because you're using HTTP to open a player page. WebRTC will work only via secure connection, so you must use HTTPS (port 8444 or 8888) to open player page.

revanreddy · May 30, 2022

Max said:
Seems like WebRTC playback does not work because you're using HTTP to open a player page. WebRTC will work only via secure connection,

That means WebRTC won't work in case of HTTP ? if webrtc works only in secure mode, how come I am able to play back this same video using non secure http connection?

Max · May 31, 2022

revanreddy said:
That means WebRTC won't work in case of HTTP ?

Yes. WebRTC requires a secure connection to work in browser.

revanreddy said:
if webrtc works only in secure mode, how come I am able to play back this same video using non secure http connection?

You can play a stream via MSE, but not all the browsers support it (for example, Safari does not). So we recommend to register a domain and get a valid SSL certificate to play WebRTC.

revanreddy · May 31, 2022

Max said:
You can play a stream via MSE, but not all the browsers support it (for example, Safari does not).

We are using chrome only now but still getting error

Max · May 31, 2022

This is how MSE works in Chrome browser.

1. Port 8081 for the demo page.

http://demo.flashphoner.com:8081/client2/examples/demo/streaming/player/player.html

2. Port 8080 for websocket connection
ws://demo.flashphoner.com:8080

3. Binary Message

in the Network > Messages > demo.flashphoner.com

Make sure your default ports are 8081 and 8080

revanreddy · May 31, 2022

Max said:
Make sure your default ports are 8081 and 8080

As 8081 used by another service so that we have changed the http port to 18081 as recommended

now we tried same as shown above..but still we are facing the same issue

Build Version v.2.0.218-5.2.1200-8a16f02d1e11e0f86f5f4e3d4199c2ed37556276

Max · Jun 1, 2022

revanreddy said:
now we tried same as shown above..but still we are facing the same issue

Please update WCS to the latest build 5.2.1228.
Try to open the Player example with the following parameters:
http://your_server_url:18081/client2/examples/demo/streaming/player/player.html?mediaProvider=MSE
If a stream still does not playing, please provide SSH access and web admin access to the server using this form
If you can't, the only alternative is to collect a report as described here including client debug logs and traffic dump:
1. Enable client debug logs

Code:

client_log_level=DEBUG 
enable_extended_logging=true

2. Restart WCS

Code:

sudo systemctl restart webcallserver

3. Start traffic dump collection

Code:

sudo tcpdump -i any -s 0 -B 10240 -w log.pcap

4. Play the stream in Player example

Code:

http://your_server_url:18081/client2/examples/demo/streaming/player/player.html?mediaProvider=MSE

5. When the issue is reproduced, stop playback
6. Stop tcpdump
7. Collect a report

Code:

cd /usr/local/FlashphonerWebCallServer/tools
sudo ./report.sh --sysinfo --conf --tar

8. Pack the report archive and traffic dump into one archive and send it using this form. If the archive size exceeds 30 M, share the archive on some cloud drive (Google Drive, OneDrive etc) and send the link using Comment field in this form

WCS Service getting failed

Member

Attachments

Administrator

Administrator

Administrator

Member

Administrator

Member

Attachments

Administrator

Member

Administrator

Member

Administrator

Administrator

Member

Administrator

Member

Administrator

Member

Administrator