I installed Mantis BT 1.2.19 on my server and it works well. To benefit from it in my Eclipse-IDE (Mars) I installed the Task-Repo Plugin for Mantis and tried to add the connection.
When I click on "Validate settings" in Eclipse I get the following error:
SOAP-ERROR: Parsing WSDL: Couldn't load from '/var/www/vhosts/{myhost}/httpdocs/mantis/api/soap/mantisconnect.wsdl' : failed to load external entity "/var/www/vhosts/{myhost}/httpdocs/mantis/api/soap/mantisconnect.wsdl"
In my error-log on the server are the following entries
[14-Oct-2015 11:25:05 Europe/Berlin] [mantisconnect.php] Error Type: SYSTEM WARNING,
Error Description: SoapServer::SoapServer(): I/O warning : failed to load external entity "/var/www/vhosts/{myhost}/httpdocs/mantis/api/soap/mantisconnect.wsdl"
Stack Trace:
mantisconnect.php L121 SoapServer(<string>'mantisconnect.wsdl', <Array> { ['features'] => 5 })
[14-Oct-2015 11:25:05 Europe/Berlin] PHP Warning: Uncaught SoapFault exception: [Server] Error Type: SYSTEM WARNING,
Error Description: SoapServer::SoapServer(): I/O warning : failed to load external entity "/var/www/vhosts/{myhost}/httpdocs/mantis/api/soap/mantisconnect.wsdl" in /var/www/vhosts/{myhost}/httpdocs/mantis/api/soap/mc_api.php:107
Stack trace:
#0 /var/www/vhosts/{myhost}/httpdocs/mantis/api/soap/mc_api.php(530): SoapActions::sendSoapFault('Server', 'Error Type: SYS...')
#1 [internal function]: mc_error_handler(2, 'SoapServer::Soa...', '/var/www/vhosts...', 121, Array)
#2 /var/www/vhosts/{myhost}/httpdocs/mantis/api/soap/mantisconnect.php(121): SoapServer->SoapServer('mantisconnect.w...', Array)
#3 {main}
thrown in /var/www/vhosts/{myhost}/httpdocs/mantis/api/soap/mc_api.php on line 107
[14-Oct-2015 11:25:05 Europe/Berlin] PHP Fatal error: SOAP-ERROR: Parsing WSDL: Couldn't load from '/var/www/vhosts/{myhost}/httpdocs/mantis/api/soap/mantisconnect.wsdl' : failed to load external entity "/var/www/vhosts/{myhost}/httpdocs/mantis/api/soap/mantisconnect.wsdl"
in /var/www/vhosts/{myhost}/httpdocs/mantis/api/soap/mantisconnect.php on line 121
The errors above are produced by the Mantis plugin on accessing the URL
188.109.171.76 - - [14/Oct/2015:11:25:05 +0200] "POST /mantis/api/soap/mantisconnect.php HTTP/1.0" 500 1067 "-" "Mylyn/3.17.0 Mylyn-Mantis Connector/3.10.1 Apache Axis/1.4 Eclipse (org.eclipse.epp.package.jee.product) HttpClient/3.1 Java/1.8.0_60 (Oracle) Windows 7/6.1 (amd64; de_DE)"
But even a "normal" GET-access to the URL mentioned above produces the same error
https://{myhost}/mantis/api/soap/mantisconnect.php
No error is produced on accessing
https://{myhost}/mantis/api/soap/mantisconnect.php?wsdl
To solve the problem on my own I checked several ideas:
The file IS existant ... {myhost} is just a placeholder here obviously - placed by me
I switched to the context of the webserver www-data and tried accessing the file ... it IS accessible
So I´ve no idea...
PHP version is 5.5.9-1ubuntu4.13 on Ubuntu 14.04.3 LTS
€dit:
Tracked down the error to the following PHP-line in mantis/api/soap/mantisconnect.php
$server = new SoapServer("mantisconnect.wsdl",
array('features' => SOAP_USE_XSI_ARRAY_TYPE + SOAP_SINGLE_ELEMENT_ARRAYS)
);
I don´t understand why there an error is thrown - because as I said: it exists and is readable by the webserver...
€edit2:
I replaced the line
$server = new SoapServer("mantisconnect.wsdl",
with
$server = new SoapServer("http://{myhost}/mantis/api/soap/mantisconnect.wsdl",
THIS works... so I´ve a "solution" but I don´t know why the access via file does not work
I Think I found the answere on my own (my workaround failed some hours later - with same error again).
Seems to be a bug in PHP (on Ubuntu) as mentioned here
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1160336
Unresolved since 2013
:-(
My current workaround is disabling soap.wsdl_cache_enabled in php.ini which seems to help for the moment.
Related
We started to have an issue on our prestashop backoffice. First, everything was super slow and now it isn´t even possible to access administration because of error 503.
I tried to delete the cache, checked all resources in cpanel (everything good). I found something in error_log, but have no idea if this can be cause by this.
[04-Feb-2023 23:03:03 US/Central] PHP Fatal error: Uncaught InvalidArgumentException: Invalid resource type: array in /home/plexrgvc/public_html/modules/ps_eventbus/vendor/guzzlehttp/psr7/src/Utils.php:337
//UPDATED:
Stack trace: #0 /home/plexrgvc/public_html/modules/ps_eventbus/vendor/guzzlehttp/psr7/src/Request.php(57): GuzzleHttp\Psr7\Utils::streamFor(Array)
#1 /home/plexrgvc/public_html/modules/ps_eventbus/src/Api/GenericClient.php(178): GuzzleHttp\Psr7\Request->__construct('POST', Object(GuzzleHttp\Psr7\Uri), Array, Array)
#2 /home/plexrgvc/public_html/modules/ps_eventbus/src/Api/EventBusProxyClient.php(138): PrestaShop\Module\PsEventbus\Api\GenericClient->post(Array)
#3 /home/plexrgvc/public_html/modules/ps_eventbus/src/Service/ProxyService.php(76): PrestaShop\Module\PsEventbus\Api\EventBusProxyClient->uploadDelete('repeat:9740b8b0...', '{"collection":"...')
#4 /home/plexrgvc/public_html/modules/ps_eventbus/src/Service/DeletedObjectsService.php(51): PrestaShop\Module\PsEventbus\Service\ProxyService->delete('repeat:9740b8b0...', Array)
#5 /home/plexrgvc/public_html in /home/plexrgvc/public_html/modules/ps_eventbus/vendor/guzzlehttp/psr7/src/Utils.php on line 337
[04-Feb-2023 23:03:04 US/Central] PHP Fatal error: Uncaught InvalidArgumentException: Invalid resource type: array in /home/plexrgvc/public_html/modules/ps_eventbus/vendor/guzzlehttp/psr7/src/Utils.php:337
I tried to manually disable this module in phpmyadmin, but didn´t work. Any idea? Thanks
Since upgrading to PHP 8.1, Symfony 6.1, Monolog 3.2, I have been seeing a PHP fatal error while constructing the Symfony DI container:
2022/12/12 04:10:02 [error] 31#31: *919 FastCGI sent in stderr: "PHP message: PHP Fatal error: Uncaught TypeError: Monolog\Logger::getLevelName(): Argument #1 ($level) must be of type Monolog\Level|int, Symfony\Bridge\Monolog\Handler\ConsoleHandler given, called in /app/vendor/monolog/monolog/src/Monolog/Logger.php on line 196 and defined in /app/vendor/monolog/monolog/src/Monolog/Logger.php:437
Stack trace:
#0 /app/vendor/monolog/monolog/src/Monolog/Logger.php(196): Monolog\Logger::getLevelName()
#1 /app/var/cache/prod/ContainerOqglp2q/App_KernelProdContainer.php(1441): Monolog\Logger->pushHandler()
#2 /app/var/cache/prod/ContainerOqglp2q/App_KernelProdContainer.php(1103): ContainerOqglp2q\App_KernelProdContainer->getMonolog_Logger_RequestService()
#3 /app/vendor/symfony/dependency-injection/Container.php(218): ContainerOqglp2q\App_KernelProdContainer->getHttpKernelService()
#4 /app/vendor/symfony/dependency-injection/Container.php(198): Symfony\Component\DependencyInjection\Container->make()
#5 /app/vendor/symfony/http-kernel/Kernel.php(195): Symfony\Compone" while reading response header from upstream, client: 172.27.0.16, server: _, request: "POST /job-engine-client/execute HTTP/1.0", upstream: "fastcgi://192.168.64.5:9000", host: "x"
I have not been able to reproduce the error manually, as it only happens in my staging environment, and very inconsistent.
It is currently only visible in HTTP requests triggered by a cronjob every 5 minutes. In the past 4 days, it only happened 2 times.
The application is deployed using docker compose, with a custom Ubuntu Dockerfile.
The application is deployed to multiple hosts, and shows the same random occurence of errors on each host.
When looking at the Monolog Logger.php file, it is really hard to understand how the stack trace that is logged can be ever triggered.
I'm suspecting some kind of PHP opcache or JIT issue, or perhaps an issue with the docker filesystem returning some other cached (older) versions of files.
Has anyone seen similar errors, or perhaps other suggestions how to debug & resolve this issue?
Octane is installed with roadrunner while following the official guide, on the Ubuntu 18.04 server. Each step works as expected until the server is started:
php artisan octane:start --server=roadrunner --port=8181
Then, an error is received and the command exits. The complete stacktrace is attached:
INFO Server running…
Local: http://127.0.0.1:8181
Press Ctrl+C to stop the server
INFO [INFO] RoadRunner server started; version: 2.6.3, buildtime: 2021-12-03T11:37:00+0000
PHP Warning: require(/path/vendor/bin/bootstrap.php): Failed to open stream: No such file or directory in /path/vendor/bin/roadrunner-worker on line 18
PHP Fatal error: Uncaught Error: Failed opening required '/path/vendor/bin/bootstrap.php' (include_path='.:/usr/share/php') in /path/vendor/bin/roadrunner-worker:18
Stack trace:
#0 {main}
thrown in /path/vendor/bin/roadrunner-worker on line 18
INFO error occurred: WorkerAllocate:
INFO goridge_frame_receive: EOF, plugin: http.Plugin
ERROR 2021-12-07T12:01:53.048Z ERROR container/poller.go:16 vertex got an error {"id": "http.Plugin", "error": "WorkerAllocate:\n\tgoridge_frame_receive: EOF"}
ERROR github.com/spiral/endure/pkg/container.(*Endure).poll.func1
ERROR github.com/spiral/endure#v1.0.10/pkg/container/poller.go:16
ERROR handle_serve_command: WorkerAllocate:
ERROR goridge_frame_receive: EOF
Since roadrunner is based on go, I don't have much insights on how to navigate through the error. Please let me know if anyone has solved this issue before, thanks.
You should fix all warnings like this one: PHP Warning: require(/path/vendor/bin/bootstrap.php): Failed to open stream: No such file or directory in /path/vendor/bin/roadrunner-worker on line 18
These warnings appear in the stdout, but stdout is used as a process fd to communicate with the RR. That means if some data is sent to the stdout (like PHP warning) before RR initializes all processes (aka worker), RR will stop allocating the workers and exit with code 1.
After executing the following URL from SOAP API concept, getting error of WSDL.
URL: http://139.5.19.140:7047/DynamicsNAV71/WS/B.%20Jain%20Pharma-2017/Codeunit/customer
I getting a common error of WSDL :
Fatal error: Uncaught SoapFault exception: [WSDL] SOAP-ERROR: Parsing WSDL: Couldn't load from 'http://139.5.19.140:7047/DynamicsNAV71/WS/B.%20Jain%20Pharma-2017/Codeunit/customer' : Document is empty in /home/Useracbglm9a/public_html/nav_con/php_nav_lib/Navision.php:11 Stack trace: #0 /home/Useracbglm9a/public_html/nav_con/php_nav_lib/Navision.php(11): SoapClient->SoapClient('http://139.5.19...', Array) #1 /home/Useracbglm9a/public_html/nav_con/my_customer.php(135): NTLMSoapClient->__construct('http://139.5.19...') #2 {main} thrown in /home/axbl3cbglm9a/public_html/nav_con/php_nav_lib/Navision.php on line 11
After Researching for this error i got that mainly this problem is of openssl extension of PHP.
I'm using PHP version: 7.1 with centOS 7.0
But i didn't get this extension of openssl in phpIniEditor.
Now i got confused that what exactly the problem is.!!!
Please Help & require your valuable support and feedback. Thanks in advance. Your Support is really appreciable.
I have a task (query) running some php code that retrieves data from gmail mailboxes. It has been working fine until last friday (April 10th, 2015) and now I'm getting this error log:
E 11:58:26.094 2015-04-15 200 3.38 KB 14.2s /code.php
0.1.0.2 - - [15/Apr/2015:07:58:26 -0700] "POST /code.php HTTP/1.1" 200 3462 "https://xxxxxxxxx.appspot.com/start.php?email=test#email.com" "AppEngine-Google; (+http://code.google.com/appengine)" "mailroof-test.appspot.com" ms=14201 cpu_ms=407 cpm_usd=0.001221 queue_name=worker task_name=13657588804765054031 instance=00c61b117c031f6c5ded2e3d1653abac0f4b87fa app_engine_release=1.9.19
E 11:58:26.088 PHP Fatal error: Uncaught exception 'Google_IO_Exception' with message 'HTTP Error: Unable to connect: 'fopen(https://www.googleapis.com/gmail/v1/users/me/messages?maxResults=100&labelIds=INBOX&pageToken=12866883594511227777): failed to open stream: Unsupported SSL context options are set. The following options are present, but have been ignored: cafile
Fetch error'' in /base/data/home/apps/xxxxxxxxx/1.383623356139435513/google-api-php-client/src/Google/IO/Stream.php:140
Stack trace:
#0 /base/data/home/apps/xxxxxxxxx/1.383623356139435513/google-api-php-client/src/Google/IO/Abstract.php(133): Google_IO_Stream->executeRequest(Object(Google_Http_Request))
#1 /base/data/home/apps/xxxxxxxxx/1.383623356139435513/google-api-php-client/src/Google/Http/REST.php(61): Google_IO_Abstract->makeRequest(Object(Google_Http_Request))
#2 [internal function]: Google_Http_REST::doExecute(Object(Google_Client), Object(Google_Http_Request))
#3 /base/data/home/apps/xxxxxxxxx/1.383623356139435513/google-api-php-client/src/Goo in /base/data/home/apps/xxxxxxxxx/1.383623356139435513/google-api-php-client/src/Google/IO/Stream.php on line 140
This is becoming an issue since it happens once every so often.
If anyone has any idea what might be going on or how to catch the error, that will be most appreciated.
Use the latest version of the API as of 25 April I think, and do this action:
https://stackoverflow.com/a/30719310/1834922.
I´m testing it right now as I have the same issue but for a Drive app. So far it's working but a 10 GB file takes a long time to really know. Will update.