Website BURP Fatal error


Advanced search

Message boards : Problems and Help : Website BURP Fatal error

Author Message
JZD
Send message
Joined: 30 Dec 11
Posts: 89
Credit: 3,284,288
RAC: 7,153
Message 12156 - Posted: 8 Dec 2013, 17:15:12 UTC

Hi, began to discover the error conditions.

Warning: fsockopen() [function.fsockopen]: unable to connect to 127.0.0.1:8080 (Connection refused) in /mnt/hosting/www/burp_production/libraries/php-java-bridge/Java.inc on line 995 Fatal error: Uncaught Could not connect to the JEE server 127.0.0.1:8080. Please start it. Error message: Connection refused (111) thrown in /mnt/hosting/www/burp_production/libraries/php-java-bridge/Java.inc on line 990

In the menu Serverstatus, the data account elsewhere.
http://burp.renderfarming.net/show_user.php?userid=10309

JZD
Send message
Joined: 30 Dec 11
Posts: 89
Credit: 3,284,288
RAC: 7,153
Message 12157 - Posted: 8 Dec 2013, 18:31:38 UTC

I see that the bug is fixed and everything is fine.

Profile Janus
Volunteer moderator
Project administrator
Avatar
Send message
Joined: 16 Jun 04
Posts: 4487
Credit: 2,094,806
RAC: 0
Message 12159 - Posted: 8 Dec 2013, 19:16:45 UTC
Last modified: 8 Dec 2013, 19:17:06 UTC

There's actually funny story to be told here. I was working on the Sunflower project, making ready to do the first 4K encode tests and was setting up the correct commandline parameters for the video encoder.
When I hit to test the first few seconds suddenly all hell broke lose: The terminal that I was using vanished, the whole backend for BURP disappeared and I got an SMS saying important services are down/failing and that the kernel was spewing errors.

In another terminal that magically survived I managed to figure out what happened:
[3278115.663287] Out of memory: Kill process 17353 (mencoder) score 314 or sacrifice child
[3278115.663290] Killed process 17353 (mencoder) total-vm:12890200kB, anon-rss:6244248kB, file-rss:0kB

The video encoder had been using 13GB of memory to encode the small test video. Other tasks were using quite a lot of memory too at the time. In panic the kernel started to kill random stuff to free up memory. Eventually it killed the encoder and things could return to normal.

Usually video encoding isn't particularly memory intensive in the encoder itself (unpacking the frames from BURP can be quite another thing). There's probably a lesson to be learned: "When working with 4K nothing is what you would expect".


Post to thread

Message boards : Problems and Help : Website BURP Fatal error