Project

General

Profile

WRun either core dumps or "WServer/wthttp: start(): server already started!"

Added by Rathnadhar K V about 5 years ago

Namaskara,

I built the hello.c example application successfully. I ran the application with standard command line: ---docroot . ---http-address 127.0.0.1 ---http-port 8080

however when it first executes it core dumps. Segmentation fault (core dumped), though I cannot locate the core anywhere.

Then when I rerun the application, I get the following message:

[2019-Feb-12 19:52:41.806] 5770 - [info] "config: reading Wt config file: /etc/wt/wt_config.xml (location = './qrcode_generator')"

[2019-Feb-12 19:52:41.810] 5770 - [error] "WServer/wthttp: start(): server already started!"

its confusing. However much I try to run the application it either throws either of the above two messages.

I checked the memory for traces of the program running, but drew a blank.

I use OpenSuSE - Tubleweed - linux 64 version.

Please let me know what is going wrong....and how to correct it.

Regards

Rathnadhar K V


Replies (2)

RE: WRun either core dumps or "WServer/wthttp: start(): server already started!" - Added by Roel Standaert about 5 years ago

Which version of Wt are you using, and how are you installing it? How are you building the hello example? Is this the example from examples/hello in the Wt source code repository, or one you wrote yourself following the tutorial? Can you maybe share the code you ended up with? Can you maybe also do ldd qrcode_generator and paste the output?

RE: WRun either core dumps or "WServer/wthttp: start(): server already started!" - Added by Rathnadhar K V about 5 years ago

I am using Wt 4 (very latest version, i will pull git everyday!!).

Yes its the same hello example, no changes.

I got rid of the problem after getting clue from your answer.

I had included other libraries (wttest etc and non wt) by mistake. I started removing the non required libraries. Somehow it clicked. The example is running fine now.

I now have to regress by adding libraries and find out which of the library or library combination is behaving like a bad boy.

Thank you so much for your quick response.

I still have a suggestion: If the application is exiting due to memory issue or library issue, it should display death notice rather than alive (started) notice. That will help us to fix the issue faster.

Regards

Rathnadhar K V

    (1-2/2)