I have installed Apache Solr and run 2 times manually cron but I have a problem that 0% was sent to server:
The search index is generated by running cron. 0% of the site content has been sent to the server. There are 2884 items left to send.
Using schema.xml version: drupal-1.1
The server has a 2 min. delay before updates are processed.
Number of documents in index: 220
Number of pending deletions: 0
All messages seems to be ok:
* Apache Solr: Your site has contacted the Apache Solr server.
* Apache Solr PHP Client Library: Correct version "Revision: 22".
I replaced solrconfig.xml and schema.xml in /solr/example/solr/conf with those from Apache Solr Drupal module.
Could somebody give me advice, what should I check?
Regards
I've just fixed the same problem. The problem was with sites/default/files folder and folder permissions.
Try to set 775 for files/ folder and etc, I guess on /admin/reports/status you'll see lots of warnings for misconfigured perms.
After resolving this stuff, solr indexed content properly.
Related
Been fighting with the problem for a month now. Have Drupal 9 set up on Azure App service with docker images running php8 (base image drupal:9.1.7-php8.0-apache)
I have found out that there are two ways to have the "sites/default/files" public files directory served in azure:
Symlink "sites/default/files" folder to "/home/files" folder and set WEBSITES_ENABLE_APP_SERVICE_STORAGE to true in application settings.
Mount Azure file share directly on top of "sites/default/files" folder using Path mappings (currently in preview).
Both options works, my files are uploaded successfully and I can see them in the storages. Drupal also sees those files, BUT every time I try to access any of the uploaded files, I get 500 error with the only error being Failed to forward request to application. Encountered a System.Net.Http.HttpRequestException exception after 119.915ms with message: Received an invalid status line: 'anges: bytes'.. Check application logs to verify the application is properly handling HTTP traffic. If I delete the uploaded file, the app reacts and shows that file not found instead.
If I disable persistent storage (any of the options mentioned above), the files are uploaded correctly, no errors are shown, but the problem is that every time the app is restarted or deployed, the files are gone.
Drupal has no errors in its log. Apache logs have no more useful info (GET seems to be ok and returns 200). Have tried messing with apache.conf, with php.ini, with both .htaccess files allowing all kinds of nasty things, but still have no clue. Had multiple colleagues look into this and nothing seems to work.
Adding EnableSendfile On into Dictionary block resolved the problem.
Example:
<Directory /media/share/www/>
EnableSendfile On
Options Indexes FollowSymLinks Includes ExecCGI
AllowOverride None
Require all granted
</Directory>
Quick update: Tried every last thing I could imagine. Had numerous people try and help, but the same error 500 or 502 appears. Two weeks no answer from microsoft support.
Created new app service not with docker containers but php 7.4 and manually uploaded all drupal files to /home/site/wwwroot, also set WEBSITES_ENABLE_APP_SERVICE_STORAGE to true so that /home dir stays persistant and the web seems to be working just fine, files are all good.
In previous attempts and now azure ssh shows all files inside /home dir as nobody:nogroup 777, will investigate this further as this might lead to some security issues if this is true (but checked settings.php etc. files and they are protected atleast from web access)
I am having an issue posting a large file using IIS 10 and .Net.
The error code i receive is from IIS:
HTTP Error 413.1 - Request Entity Too Large
The request filtering module is configured to deny a request that exceeds the request content length.
I found many solutions online that are not working. Here are the changes i have made to IIS.
These changes were done under the default website which hosts the application where i'm having this issue. The changes made to the default website have propagated to all the sites contained within.
I have also set the uploadReadAheadSize to 2147483647:
The file i am attempting to upload is 97 MB.
What am i missing?
Set the uploadReadAheadSize value in the configuration file, here are the steps:
Select the site under Default Web Site
Select Configuration Editor
Within Section Dropdown, select "system.webServer/serverRuntime"
Enter a higher value for "uploadReadAheadSize" such as 1048576
bytes. Default is 49152 bytes.
I am using drupal 7 solr search module for search.While searching am receiving an error "The website encountered an unexpected error. Please try again later." and css is not applied.In log messages I can see two errors
1. ApAche Tomcat The request sent by the client was syntactically incorrect
2. ApAche Tomcat The request sent by the client was syntactically incorrect in DrupalApacheSolrService->checkResponse() (line 368 of/data/www/drupal/factory/sites/all/modules/search/apachesolr/Drupal_Apache_Solr_Service.php).
Solutions Tried
1. Reindexed site
2.ran the cron
3.Cleared cache
4.Indexed site
Could anyone say some solutions.Thanks in Advance!
I've copied & installed the database for a Magento site for a client. I don't have much experience in Magento but I get a strange error condition
When you type in www.example.com it automatically re-writes the URL to www.example.com/sites/example.com/index.php
It also produces a 500 error as well.
Anyone got any clue on how to fix this? Please remember I am a Magento newbie.
EDIT
The problem was down to the server setup :( There was an issue with the "webroot"
go to core_config_data table. There are a couple of fields you need to edit so the urls match your http://localhost/mysite/ but make sure you have the trailing slash on the site path.
base urls
Edit these base urls
These tell the database where to point your links between pages and content.
moving files and database
I assume these two steps are obvious:
copy all of your local files to production server
dump your magento local db and import it into your production server db
editing in production server
now on your production server you need to follow these two steps:
edit app/etc/local.xml file and change database info
in production db,in its core_config_data table, you should find every records containing the url of your local installation, then you need to update those values;which can be found with this query:
SELECT *
FROM `core_config_data`
WHERE `value` LIKE 'http://%';
edit (thanks to comments):
Do not forget to delete var folder contents
this is a weird one. I have a site deployed on a web server. (Win 2003, IIS 6)
For some reason, I can do an HTTP GET on a file if I specify it with "camel casing".. i.e. Styles.css, but I cannot get the same file using "small cap" i.e. styles.css
In the later case I get a 401.3 exception.
I know that 401.3 is a security issue but I'm confused because as far as I know ACL has nothing to do with case sensitivity.
What is even more weird is that I have (in the same folder) other files that I cannot GET (small cap or camel cap) and they have the exact same security settings.
Any ideas on what the issue could be?
Regards,
Alex
Can you check your web log or possibly use Process Monitor to see what happens when that file is requested?
The problem was related to a proxy server in front of my server. This box caches the files so it was not really hitting the IIS server all the time.
Thanks Micky for your help.