I've implemented Solr on an Ubuntu 14.04 server and it works - I can login, see the dashboard, the core, no errors, etc…
Now I'm trying to install/config "Open Semantic Search" - looks like a promising tool! - and when try to hit the main page I get this error:
Error:
exception 'Apache_Solr_HttpTransportException' with message ''404' Status: Not Found' in /var/www/html/search/Apache/Solr/Service.php:338 Stack trace: #0 /var/www/html/search/Apache/Solr/Service.php(1170): Apache_Solr_Service->_sendRawGet('http://localhos...') #1 /var/www/html/search/index.php(749): Apache_Solr_Service->search('*:*', 0, 10, Array) #2 {main}
I've messed about with the "Open Semantic Search" config file, changed localhost to the ip, tried different paths, looked through the service.php and index.php, used the domain vs. localhost - I'm just at a loss. I think it's a path issue - maybe permissions?
If anyone has a solution - great! But if someone could just explain that error to me like I was born in the 60's ;) that would be awesome.
Related
I uploaded an ASP.net MVC project to Plesk. On the very first page. I get this error:
Server Error in '/' Application
>
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
I searched the Plesk forum and found a thread on the same topic (an older one but reviewed it anyway). But I didn't get any help as the KB link given in this thread is broken.
https://talk.plesk.com/threads/server-error-in-application.339898/
Since the error described, doesn't provide much detail, I checked 'Log' on the Plesk control panel and found that repeated error is given as
DateTime - 2022-06-05 07:48:21
IP - 1.18X.XXX.1X6
Status Code - 500
Error Code - GET / - HTTP/1.1
I tried searching Stack Overflow but questions are only pointing towards HTTP1.1 enablement or custom error in web.config.
Please help
All of a sudden we are seeing this random error / exception in our web application.
Failed to load resource: the server responded with a status of 502 (Bad Gateway).
In the Log Stream, we are seeing the following details, with specific error code as 502.3 - Bad Gateway: Forwarder Connection Error (ARR).
Also, sometimes in the browser itself we see "The CGI application did not return a valid set of HTTP errors." getting displayed.
Most of the searches for these error codes refer to "IIS / Proxy Server" configuration. But, we haven't changed any such settings.
The error happens very randomly and not specific to any user action/function. Same functionality works first and on second execution immediately after first one throws this error.
How to figure out what is causing this and how to fix?
I google this question, because the program was normal at the beginning, and the subsequent 502.3 error. After I checked the information on the Internet, I feel that it can only give us an inspiration, and it cannot solve your problem immediately.
So my suggestion is that first you browse post1 and post2 I provided.
Next, proceed to Troubleshoot according to the steps of the official documentation. Specific errors require specific analysis.
I am using Yii 1.x, Yii internal log file is showing an exception for wp-login.php, however, I don't have WordPress installed on my server. (I get this message on my local as well)
XXXX/XX/XX XX:XX:XX [error] [exception.CHttpException.404] exception 'CHttpException' with message 'Unable to resolve the request "wp-login.php".' in /var/www/html/framework/web/CWebApplication.php:286
Stack trace:
#0 /var/www/html/framework/web/CWebApplication.php(141): CWebApplication->runController('wp-login.php')
#1 /var/www/html/framework/base/CApplication.php(180): CWebApplication->processRequest()
#2 /var/www/html/index.php(18): CApplication->run()
#3 {main}
REQUEST_URI=/wp-login.php
Can anyone tell me why I am receiving such error?
This is log for 404 Not Found error. So this only means that someone is trying to access /wp-login.php URL in your domain. WordPress is the most popular CMS and internet is full of bots which searches WordPress installation on every server/domain and tries to brute-force login form. So you should not worry about it - if you don't have a WordPress installation, then bot definitely will not be able to login into it. :)
But it may be good idea to exclude 404 HTTP errors from regular application logs - bots will generate hundreds of such logs in your app, and usually you want to ignore it (as opposed to regular logs).
[
'class' => 'CFileLogRoute',
'levels' => 'error, warning',
'except' => [
'exception.CHttpException.404',
],
],
i have the following simple script to list the ftp accounts
but i am unable to get it to work as i have the following error as soon as it tries to call the constructor
include '/usr/local/cpanel/php/cpanel.php';
$cpanel = new CPANEL(); // Connect to cPanel - only do this once.
// List FTP account information.
$list_ftp_accts = $cpanel->uapi('Ftp', 'list_ftp');
echo "<pre>";
print_r($list_ftp_accts);
Fatal error: Uncaught exception 'RuntimeException' with message 'There
was a problem fetching the env variable containing the path to the
socket' in /usr/local/cpanel/php/cpanel.php:146 Stack trace: #0
/public_html/uapi.php(4): CPANEL->__construct() #1
{main} thrown in /usr/local/cpanel/php/cpanel.php on line 146
Line 146 in cpanel.php
$socketfile = getenv('CPANEL_PHPCONNECT_SOCKET');
According to a post on the cPanel forums, you can only use LiveAPI from within cPanel's document root, meaning your code would need to be in either /usr/local/cpanel/base/frontend/ or /usr/local/cpanel/base/3rdparty/. I ran into this while trying to use it in a WHM plugin (which would reside in /usr/local/cpanel/whostmgr/docroot/), and apparently that causes the same problem. If you're trying to run this from within cPanel or WHM, this page has some debugging steps you can try walking through.
If you're trying to run this code on a different server or from within a normal website's hosting account, you'll definitely need to use a different interface, such as the XML or JSON API. These are unfortunately somewhat confusingly documented, but the Guide to WHM API 1 page should get you started.
Me too got the same error.
Try changing your file extension to your_file.live.php, instead of your_file.php. It solved the issue for me.
Referred the documentation here.
A lot of people have ask this question but it was 2 month ago with another gitlab version,
I'm using gitlab 5.2 in a fresh debian 7.0 serveur
everything looks Okay on the website but when I run /home/git/gitlab-shell/bin/check I've got this error :
Check GitLab API access: FAILED. code: 302
Check directories and files:
/home/git/repositories: OK
/home/git/.ssh/authorized_keys: OK:
I'm running on a custum ssh port but I'm able to connect.
When pushing I've got this error:
git push -vu origin master
Pushing to ssh://git#apps.ndd.fr:2232/Users/test.git
fatal: The remote end hung up unexpectedly
Thanks for your answers!
I've just got the same error and go look onto the code.
The thing I've found the gitlab_net module going for answer at #{host}/check (gitlab-shell/lib/gitlab_net.rb)
host method is defined as "#{config.gitlab_url}/api/v3/internal", and at the same time config.gitlab_url defined in ./gitlab-shell/config.yml "Should end with a slash" (c) So my web server just returns 302 on a request to remove double slashes.
FYI: That fail is about API and not about web service. So it's non-critical in many cases anyway.
I think it's a minor bug in code and there is a close issue to this: https://github.com/gitlabhq/gitlabhq/issues/3483