I'm trying to run my symfony 3.3 project in the docker. It's working fine out of docker. All containers are running: nginx:alpine, php-fpm 7.2, PostgreSQL, rabbitMQ.
I'm receiving this error:
(1/1) FatalErrorException
Error: Maximum execution time of 30 seconds exceeded
in AnalyzeServiceReferencesPass.php (line 71)
at AnalyzeServiceReferencesPass->processValue()
in AnalyzeServiceReferencesPass.php (line 118)
dev.log
request.CRITICAL: Uncaught PHP Exception
Symfony\Component\Debug\Exception\FatalErrorException: "Error: Maximum
execution time of 30 seconds exceeded" at
/var/www/html/vendor/twig/twig/lib/Twig/Extension/Core.php line 710
{"exception":"[object]
(Symfony\Component\Debug\Exception\FatalErrorException(code: 0):
Error: Maximum execution time of 30 seconds exceeded at
/var/www/html/vendor/twig/twig/lib/Twig/Extension/Core.php:710)"}
Its means that your request is very slowly, so you need to increase your max_execution time
max_execution_time = 900 or ini_set('max_execution_time', 900);
or change driver of request
also check if you have a infinite cycles
RUN echo "max_execution_time=900" >> /usr/local/etc/php/conf.d/docker-php-ext-xdebug.ini line added to Docker file made it work.
Related
A bazel binary that I am building completes unsuccessfully during the analysis phase. What flags and tools can I use to debug why it fails during analysis.
Currently, clean builds return the following output
ERROR: build interrupted
INFO: Elapsed time: 57.819 s
FAILED: Build did NOT complete successfully (133 packages loaded)
If I retry building after failed completion, I receive the following output
ERROR: build interrupted
INFO: Elapsed time: 55.514 s
FAILED: Build did NOT complete successfully (68 packages loaded)
What flags can I use to identify
what packages are being loaded
what package the build is being interrupted on
whether the interruption is coming from a timeout or an external process.
Essentially, something similar to --verbose_failures but for the analysis phase rather than the execution phrase.
So far I have ran my build through the build profiler, and have not been able to glean any insight. Here is the output of my build:
WARNING: This information is intended for consumption by Blaze developers only, and may change at any time. Script against it at your own risk
INFO: Loading /<>/result
INFO: bazel profile for <> at Mon Jun 04 00:10:11 GMT 2018, build ID: <>, 49405 record(s)
INFO: Aggregating task statistics
=== PHASE SUMMARY INFORMATION ===
Total launch phase time 9.00 ms 0.02%
Total init phase time 91.0 ms 0.16%
Total loading phase time 1.345 s 2.30%
Total analysis phase time 57.063 s 97.53%
Total run time 58.508 s 100.00%
=== INIT PHASE INFORMATION ===
Total init phase time 91.0 ms
Total time (across all threads) spent on:
Type Total Count Average
=== LOADING PHASE INFORMATION ===
Total loading phase time 1.345 s
Total time (across all threads) spent on:
Type Total Count Average
CREATE_PACKAGE 0.67% 9 3.55 ms
VFS_STAT 0.69% 605 0.05 ms
VFS_DIR 0.96% 255 0.18 ms
VFS_OPEN 2.02% 8 12.1 ms
VFS_READ 0.00% 5 0.01 ms
VFS_GLOB 23.74% 1220 0.93 ms
SKYFRAME_EVAL 24.44% 3 389 ms
SKYFUNCTION 36.95% 8443 0.21 ms
SKYLARK_LEXER 0.19% 31 0.29 ms
SKYLARK_PARSER 0.68% 31 1.04 ms
SKYLARK_USER_FN 0.03% 5 0.27 ms
SKYLARK_BUILTIN_FN 5.91% 349 0.81 ms
=== ANALYSIS PHASE INFORMATION ===
Total analysis phase time 57.063 s
Total time (across all threads) spent on:
Type Total Count Average
CREATE_PACKAGE 0.30% 138 3.96 ms
VFS_STAT 0.05% 2381 0.03 ms
VFS_DIR 0.19% 1020 0.35 ms
VFS_OPEN 0.04% 128 0.61 ms
VFS_READ 0.00% 128 0.01 ms
VFS_GLOB 0.92% 3763 0.45 ms
SKYFRAME_EVAL 31.13% 1 57.037 s
SKYFUNCTION 65.21% 32328 3.70 ms
SKYLARK_LEXER 0.01% 147 0.10 ms
SKYLARK_PARSER 0.03% 147 0.39 ms
SKYLARK_USER_FN 0.20% 343 1.08 ms
As far as my command, I am running
bazel build src:MY_TARGET --embed_label MY_LABEL --stamp --show_loading_progress
Use the --host_jvm_debug startup flag to debug Bazel itself during a build.
From https://bazel.build/contributing.html:
Debugging Bazel
Start creating a debug configuration for both C++ and
Java in your .bazelrc with the following:
build:debug -c dbg
build:debug --javacopt="-g"
build:debug --copt="-g"
build:debug --strip="never"
Then you can rebuild Bazel with bazel build --config debug //src:bazel and use your favorite debugger to start debugging.
For debugging the C++ client you can just run it from gdb or lldb as
you normally would. But if you want to debug the Java code, you must
attach to the server using the following:
Run Bazel with debugging option --host_jvm_debug before the command (e.g., bazel --batch --host_jvm_debug build //src:bazel).
Attach a debugger to the port 5005. With jdb for instance, run jdb -attach localhost:5005. From within Eclipse, use the remote
Java application launch configuration.
Our IntelliJ plugin has built-in debugging support
Intermittently getting error when doing bundle install for this and also on Continuous Integration server.
Retrying dependency api due to error (4/4): Bundler::HTTPError Network error while fetching https://rails-assets.org/api/v1/dependencies?gems=rails-assets-angular%2Crails-assets-bootstrap-2.3.2%2Crails-assets-bootstrap-3%2Crails-assets-jasmine%2Crails-assets-jqueryjs%2Crails-assets-rainbow%2Crails-assets-typeahead.js (too many connection resets (due to Net::ReadTimeout - Net::ReadTimeout) after 0 requests on 70190348894440, last used 22.186127 seconds ago)
It's likely maintenance happens every once and awhile (especially this late) although they have definitely had downtime before (see https://github.com/tenex/rails-assets/issues/329).
Doing a simple curl you can see they simply aren't responding to any requests:
$ curl 'https://rails-assets.org/api/v1/dependencies?gems=rails-assets-angular%2Crails-assets-bootstrap-2.3.2%2Crails-assets-bootstrap-3%2Crails-assets-jasmine%2Crails-assets-jqueryjs%2Crails-assets-rainbow%2Crails-assets-typeahead.js' -D - --max-time 10
curl: (28) Operation timed out after 10004 milliseconds with 0 bytes received
I am working on siege 4.0.2 on ubuntu 16.04 environment. I need get a failed transaction when I simulate more than 1100 user, I know that if failed transaction comes means so there is a problem in server memory may be maemory out of failure. How to understand the failed transaction ? And how to solve the problem for failed transaction comes ?
siege -c1190 -t1m http://192.168.1.11:8080/
HTTP/1.1 200 7.02 secs: 57 bytes ==> GET /kiosk/start
HTTP/1.1 200 7.01 secs: 57 bytes ==> GET /kiosk/start
siege aborted due to excessive socket failure; you
can change the failure threshold in $HOME/.siegerc
Transactions: 3263 hits
Availability: 76.11 %
Elapsed time: 9.34 secs
Data transferred: 0.18 MB
Response time: 1.98 secs
Transaction rate: 349.36 trans/sec
Throughput: 0.02 MB/sec
Concurrency: 691.94
Successful transactions: 3263
Failed transactions: 1024
Longest transaction: 7.75
Shortest transaction: 0.03
When I simulate 1100 users , I got a error discriptor tables full sock. c 119: Too many open files and then I do ulimit - n 10000 and the error went.
Then I again simulate 1100 users, I got a new error
[error] socket: read error Connection reset by peer sock.c:539: Connection reset by peer
Could not able to throw the error . How to remove this error ? Anybody please help me
edited
I try to install cgynus-ngsi firstly i install the ready made image and tested that it's worked fine,
but when try to reconfigure agent.conf i edit the file and try to install cgynus-ngsi from scratch it found this problem
Trying other mirror.
Setting up Install Process
http://ftp.uma.es/mirror/CentOS/6.9/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://ftp.uma.es/mirror/CentOS/6.9/os/x86_64/repodata/repomd.xml: (28, 'Operation too slow. Less than 1 bytes/sec transfered the last 30 seconds')
Trying other mirror.
http://sunsite.rediris.es/mirror/CentOS/6.9/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://sunsite.rediris.es/mirror/CentOS/6.9/os/x86_64/repodata/repomd.xml: (28, 'Operation too slow. Less than 1 bytes/sec transfered the last 30 seconds')
Trying other mirror.
http://mirror.trueinter.net/centos/6.9/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://mirror.trueinter.net/centos/6.9/os/x86_64/repodata/repomd.xml: (28, 'Operation too slow. Less than 1 bytes/sec transfered the last 30 seconds')
Trying other mirror.
http://mirror.uv.es/mirror/CentOS/6.9/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://mirror.uv.es/mirror/CentOS/6.9/os/x86_64/repodata/repomd.xml: (28, 'Operation too slow. Less than 1 bytes/sec transfered the last 30 seconds')
Trying other mirror.
http://ftp.cica.es/CentOS/6.9/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://ftp.cica.es/CentOS/6.9/os/x86_64/repodata/repomd.xml: (28, 'Operation too slow. Less than 1 bytes/sec transfered the last 30 seconds')
Trying other mirror.
http://mirror.tedra.es/CentOS/6.9/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://mirror.tedra.es/CentOS/6.9/os/x86_64/repodata/repomd.xml: (28, 'Operation too slow. Less than 1 bytes/sec transfered the last 30 seconds')
Trying other mirror.
http://centos.uvigo.es/6.9/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://centos.uvigo.es/6.9/os/x86_64/repodata/repomd.xml: (28, 'Operation too slow. Less than 1 bytes/sec transfered the last 30 seconds')
Trying other mirror.
http://mirror.airenetworks.es/CentOS/6.9/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://mirror.airenetworks.es/CentOS/6.9/os/x86_64/repodata/repomd.xml: (28, 'Operation too slow. Less than 1 bytes/sec transfered the last 30 seconds')
Trying other mirror.
http://centos.cadt.com/6.9/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://centos.cadt.com/6.9/os/x86_64/repodata/repomd.xml: (28, 'Operation too slow. Less than 1 bytes/sec transfered the last 30 seconds')
Trying other mirror.
ftp://ftp.cesca.cat/centos/6.9/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on ftp://ftp.cesca.cat/centos/6.9/os/x86_64/repodata/repomd.xml: (28, 'Operation too slow. Less than 1 bytes/sec transfered the last 30 seconds')
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: base. Please verify its path and try again
/bin/sh: java: command not found
then
i run tis commad
docker build -t cygnus-common .
it git this logs
INFO: Java version <1.7.0>
INFO: Apache domain <http://archive.apache.org/dist/>
INFO: URL MAVEN <http://archive.apache.org/dist/maven/maven-3/3.3.9/binaries/apache-maven-3.3.9-bin.tar.gz>
INFO: URL FLUME <http://archive.apache.org/dist/flume/1.4.0/apache-flume-1.4.0-bin.tar.gz>
INFO: Download and install Maven and Flume...
but get timeout
It seems to be a network problem. Are your host behind a proxy?
You can try to access the mirrors manually, from the same host, as stated in this question on ServerFault, and see what happens:
time wget http://sunsite.rediris.es/mirror/CentOS/6.9/os/x86_64/repodata/repomd.xml
If you also get problems, maybe you'll have to get in touch with your cloud provider.
If you are running in a CentOS, as explained in this link from CentOS forum, you can add http_caching=packages to /etc/yum.conf file and run the command again.
Please read the link above for more details.
All,
I'm learning to do benchmark testing using the Siege tool against our Rails app. I'm running Siege on my OS X box against a website hosted on another server. When I run it I always get zero hits and zero failed transactions no matter which site I run it against.
Because of the limitations of OS X, I've configured more ports with sudo sysctl -w net.inet.tcp.msl=1000 and more open files with launchctl limit maxfiles 10000 10000. I've also configured proxy variables in .siegerc since I'm running behind a proxy. Sample command line is:
siege -c1 -b -t10S 'www.google.com'.
But no matter which website I hit, I always get zero hits, zero failures and zero successful transactions. The Siege log file does not show any errors. What am I doing wrong?
siege -c1 -b -t10S 'www.google.com'
** SIEGE 3.0.5
** Preparing 1 concurrent users for battle.
The server is now under siege...
Lifting the server siege... done.
Transactions: 0 hits
Availability: 0.00 %
Elapsed time: 9.84 secs
Data transferred: 0.00 MB
Response time: 0.00 secs
Transaction rate: 0.00 trans/sec
Throughput: 0.00 MB/sec
Concurrency: 0.00
Successful transactions: 0
Failed transactions: 0
Longest transaction: 0.00
Shortest transaction: 0.00