Меню Рубрики

Установка drupal ошибка при установке

Drupal Русскоязычное сообщество

Ребят такая проблема.
При установке модуля или шаблона выбрасывает на страницу
http://s1.ipicture.ru/uploads/20130325/15O2RG4R.png

Помогите. никак не могу разобраться. как можно обойти это подтверждение.
Потому что при вводе данных она выдает ошибку
http://s1.ipicture.ru/uploads/20130325/YRsxCKM3.png

Вложение Размер
bezymyannyy.png 19.35 КБ
bezymyannyy1.png 23.09 КБ

Комментарии

Была подобная проблема — криво был настроен хостинг. Возможно, в вашем случае тоже самое.
Если шаред хостинг — попробуйте в саппорт написать.

А так — ручками, через фтп все отлично грузится.

ААА. ток хотел про эту ошибку у себя написать как лечить Ща точно напишу, ибо решал её уже и у самого сейчас такая.

Спасибо за ответы. Никлан если можно ссылочку скинешь сюда=)

Не знаю как на Windows, есть ли там вообще такая ошибка, если есть то, скорее всего, проблема в папке temp.

И что-то ваша команда не очень похожа на это.

На виндовс у друпала папка sites называется точно также и права на запись тоже есть.

В данном случае пользователь-сервер просто получает все права на эту папку и становится её владельцем. Так что все норм.

Там сервера иначе ставятся.

И я советую написать про вариант с зиллой, имхо самый простой и универсальный (на шаред хостинге вам никто консоль не даст).

777 ля-ля-ля 444
Где-то на орге валяется подобная инструкция.
Надо снова запрещать для безопасности.

Ой, это я про settings.php блин, для files — 775.

П.С. На блоге нет уведомления куда делся мой коммент — косяк.

1. www-data дать доступ ко всем своим сайтам на сервере вы должны понять какая это дыра в безопасности.
2. При указании настроек FTP вы сказали что ничего не получится — «не правда», все работает если указать нужного пользователя.

ПС: Я думаю что подойдет решение добавление каждого пользователя (Web) на сервере в группу www-data. Сам не пробовал. И тоже надо выяснять с безопасностью.

А вообще решение более сложное и сводится к настройке https протокола и сертификатов на сервере.
Которое пока нет времени разбирать.

Я думаю что подойдет решение добавление каждого пользователя (Web) на сервере в группу www-data.

Решение писал для локального сервера. Надо указать, а то дыра действительно получается, но и такую дыру на хостинге не сделать ибо тупо команда не сработает.

При указании настроек FTP вы сказали что ничего не получится — «не правда», все работает если указать нужного пользователя.

Решение писал для локального сервера.

Так, давайте еще раз по-порядку, через FileZilla выставляем следующие права доступа:
1. у папки . /www/[site_catalog_name]/sites — 755
2. у файла . /www/[site_catalog_name]/sites/default/settings.php — 444
3. у папки . /www/[site_catalog_name]/sites/default/files — 775

Я тут почитал, получается для решения данной проблемы на шаредах достаточно прописать 755 на папку sites/default/files?

Дайте уже кто-нибудь ссылку на инструкцию по этому поводу на орге, там где-то в гайде по установке должна быть.

4. у папки . /www/[site_catalog_name]/includes должно быть 755 (у меня так)

Думаю лучше сказать для выделенного сервера, кому спрашивается нужен локальный сервер и его безопасность?

Тут вообще выходит дело не в правах. У автора чистый друпал так ерорит. Тут дело в сервере походу.

У автора чистый друпал так ерорит.

Была подобная проблема — криво был настроен хостинг. Возможно, в вашем случае тоже самое.
Если шаред хостинг — попробуйте в саппорт написать.

Да нет, там приветы от зенда. Большой вопрос возникает после чего все это началось? А вообще решение еще в первом посте написали

Да и мне он в личку писал и если б не фатал еррор, который он там выдал, то все это можно было бы «вылечить» подавлением вывода конкретно этих ошибок как предлогают в инете.
В общем проблема оказалась не в правах как мы тут наугад решили)), а поинтересней немного пока ничего не скажу, копаю отсюда.

Короче все просто, подробности тут.
fel0n, если проблемма еще актуальна, то вот порядок действий:
1. Чтобы срочно решить проблему для одного сайта: по адресу . /www/[site_catalog_name]/ находим файл .htaccess и в конце пишем
php_value open_basedir none
Если стало только хуже, то удаляем взад.

источник

Drupal Русскоязычное сообщество

Здравствуйте! Прошу помощи, уже третий раз устанавливаю друпал и никак не могу решить проблему.
При установке и настройке друпал на хотинг такая проблема:

Комментарии

Если пароль верный вводите и на правильном языке, обращайтесь к хостеру.

Дак я уже 2 раза регал то же само было. то там что то сменил, то там. Сейчас два сайта уже работают. Только вот я не помню что делал. Хостер американский обратится не смогу. Пожалуйста помогите.

А если поставить айпи то пишет такое :
Ошибка при соединении с сервером базы данных. Сообщение сервера: SQLSTATE[HY000] [2013] Lost connection to MySQL server at ‘reading initial communication packet’, system error: 111.

Ну или вот такое если написать freehostia.com ^
Ошибка при соединении с сервером базы данных. Сообщение сервера: SQLSTATE[28000] [1045] Access denied for user ‘esrmm_1’@’66.40.52.27’ (using password: YES).

В чем проблема открыть конфиг вашего прошлого проекта и сравнить ?

Хостер американский обратится не смогу.

Бесплатная ссылка

Дак я уже 2 раза регал то же само было. то там что то сменил, то там. Сейчас два сайта уже работают

что означает слово конфиг знаю но где посмотреть?

Вам надо найти файл и отрыть его редактором .

Вот если смотреть с хостинга:

/**
* @file
* Drupal site-specific configuration file.
*
* IMPORTANT NOTE:
* This file may have been set to read-only by the Drupal installation program.
* If you make changes to this file, be sure to protect it again after making
* your modifications. Failure to remove write permissions to this file is a
* security risk.
*
* The configuration file to be loaded is based upon the rules below. However
* if the multisite aliasing file named sites/sites.php is present, it will be
* loaded, and the aliases in the array $sites will override the default
* directory rules below. See sites/example.sites.php for more information about
* aliases.
*
* The configuration directory will be discovered by stripping the website’s
* hostname from left to right and pathname from right to left. The first
* configuration file found will be used and any others will be ignored. If no
* other configuration file is found then the default configuration file at
* ‘sites/default’ will be used.
*
* For example, for a fictitious site installed at
* http://www.drupal.org:8080/mysite/test/, the ‘settings.php’ file is searched
* for in the following directories:
*
* — sites/8080.www.drupal.org.mysite.test
* — sites/www.drupal.org.mysite.test
* — sites/drupal.org.mysite.test
* — sites/org.mysite.test
*
* — sites/8080.www.drupal.org.mysite
* — sites/www.drupal.org.mysite
* — sites/drupal.org.mysite
* — sites/org.mysite
*
* — sites/8080.www.drupal.org
* — sites/www.drupal.org
* — sites/drupal.org
* — sites/org
*
* — sites/default
*
* Note that if you are installing on a non-standard port number, prefix the
* hostname with that number. For example,
* http://www.drupal.org:8080/mysite/test/ could be loaded from
* sites/8080.www.drupal.org.mysite.test/.
*
* @see example.sites.php
* @see conf_path()
*/

/**
* Database settings:
*
* The $databases array specifies the database connection or
* connections that Drupal may use. Drupal is able to connect
* to multiple databases, including multiple types of databases,
* during the same request.
*
* Each database connection is specified as an array of settings,
* similar to the following:
* @code
* array(
* ‘driver’ => ‘mysql’,
* ‘database’ => ‘databasename’,
* ‘username’ => ‘username’,
* ‘password’ => ‘password’,
* ‘host’ => ‘localhost’,
* ‘port’ => 3306,
* ‘prefix’ => ‘myprefix_’,
* ‘collation’ => ‘utf8_general_ci’,
* );
* @endcode
*
* The «driver» property indicates what Drupal database driver the
* connection should use. This is usually the same as the name of the
* database type, such as mysql or sqlite, but not always. The other
* properties will vary depending on the driver. For SQLite, you must
* specify a database file name in a directory that is writable by the
* webserver. For most other drivers, you must specify a
* username, password, host, and database name.
*
* Some database engines support transactions. In order to enable
* transaction support for a given database, set the ‘transactions’ key
* to TRUE. To disable it, set it to FALSE. Note that the default value
* varies by driver. For MySQL, the default is FALSE since MyISAM tables
* do not support transactions.
*
* For each database, you may optionally specify multiple «target» databases.
* A target database allows Drupal to try to send certain queries to a
* different database if it can but fall back to the default connection if not.
* That is useful for master/slave replication, as Drupal may try to connect
* to a slave server when appropriate and if one is not available will simply
* fall back to the single master server.
*
* The general format for the $databases array is as follows:
* @code
* $databases[‘default’][‘default’] = $info_array;
* $databases[‘default’][‘slave’][] = $info_array;
* $databases[‘default’][‘slave’][] = $info_array;
* $databases[‘extra’][‘default’] = $info_array;
* @endcode
*
* In the above example, $info_array is an array of settings described above.
* The first line sets a «default» database that has one master database
* (the second level default). The second and third lines create an array
* of potential slave databases. Drupal will select one at random for a given
* request as needed. The fourth line creates a new database with a name of
* «extra».
*
* For a single database configuration, the following is sufficient:
* @code
* $databases[‘default’][‘default’] = array(
* ‘driver’ => ‘mysql’,
* ‘database’ => ‘databasename’,
* ‘username’ => ‘username’,
* ‘password’ => ‘password’,
* ‘host’ => ‘localhost’,
* ‘prefix’ => ‘main_’,
* ‘collation’ => ‘utf8_general_ci’,
* );
* @endcode
*
* You can optionally set prefixes for some or all database table names
* by using the ‘prefix’ setting. If a prefix is specified, the table
* name will be prepended with its value. Be sure to use valid database
* characters only, usually alphanumeric and underscore. If no prefixes
* are desired, leave it as an empty string ».
*
* To have all database names prefixed, set ‘prefix’ as a string:
* @code
* ‘prefix’ => ‘main_’,
* @endcode
* To provide prefixes for specific tables, set ‘prefix’ as an array.
* The array’s keys are the table names and the values are the prefixes.
* The ‘default’ element is mandatory and holds the prefix for any tables
* not specified elsewhere in the array. Example:
* @code
* ‘prefix’ => array(
* ‘default’ => ‘main_’,
* ‘users’ => ‘shared_’,
* ‘sessions’ => ‘shared_’,
* ‘role’ => ‘shared_’,
* ‘authmap’ => ‘shared_’,
* ),
* @endcode
* You can also use a reference to a schema/database as a prefix. This maybe
* useful if your Drupal installation exists in a schema that is not the default
* or you want to access several databases from the same code base at the same
* time.
* Example:
* @code
* ‘prefix’ => array(
* ‘default’ => ‘main.’,
* ‘users’ => ‘shared.’,
* ‘sessions’ => ‘shared.’,
* ‘role’ => ‘shared.’,
* ‘authmap’ => ‘shared.’,
* );
* @endcode
* NOTE: MySQL and SQLite’s definition of a schema is a database.
*
* Advanced users can add or override initial commands to execute when
* connecting to the database server, as well as PDO connection settings. For
* example, to enable MySQL SELECT queries to exceed the max_join_size system
* variable, and to reduce the database connection timeout to 5 seconds:
*
* @code
* $databases[‘default’][‘default’] = array(
* ‘init_commands’ => array(
* ‘big_selects’ => ‘SET SQL_BIG_SELECTS=1’,
* ),
* ‘pdo’ => array(
* PDO::ATTR_TIMEOUT => 5,
* ),
* );
* @endcode
*
* WARNING: These defaults are designed for database portability. Changing them
* may cause unexpected behavior, including potential data loss.
*
* @see DatabaseConnection_mysql::__construct
* @see DatabaseConnection_pgsql::__construct
* @see DatabaseConnection_sqlite::__construct
*
* Database configuration format:
* @code
* $databases[‘default’][‘default’] = array(
* ‘driver’ => ‘mysql’,
* ‘database’ => ‘databasename’,
* ‘username’ => ‘username’,
* ‘password’ => ‘password’,
* ‘host’ => ‘localhost’,
* ‘prefix’ => »,
* );
* $databases[‘default’][‘default’] = array(
* ‘driver’ => ‘pgsql’,
* ‘database’ => ‘databasename’,
* ‘username’ => ‘username’,
* ‘password’ => ‘password’,
* ‘host’ => ‘localhost’,
* ‘prefix’ => »,
* );
* $databases[‘default’][‘default’] = array(
* ‘driver’ => ‘sqlite’,
* ‘database’ => ‘/path/to/databasefilename’,
* );
* @endcode
*/
$databases = array ( ) ;

/**
* Access control for update.php script.
*
* If you are updating your Drupal installation using the update.php script but
* are not logged in using either an account with the «Administer software
* updates» permission or the site maintenance account (the account that was
* created during installation), you will need to modify the access check
* statement below. Change the FALSE to a TRUE to disable the access check.
* After finishing the upgrade, be sure to open this file again and change the
* TRUE back to a FALSE!
*/
$update_free_access = FALSE ;

/**
* Salt for one-time login links and cancel links, form tokens, etc.
*
* This variable will be set to a random value by the installer. All one-time
* login links will be invalidated if the value is changed. Note that if your
* site is deployed on a cluster of web servers, you must ensure that this
* variable has the same value on each server. If this variable is empty, a hash
* of the serialized database credentials will be used as a fallback salt.
*
* For enhanced security, you may set this variable to a value using the
* contents of a file outside your docroot that is never saved together
* with any backups of your Drupal files and database.
*
* Example:
* $drupal_hash_salt = file_get_contents(‘/home/example/salt.txt’);
*
*/
$drupal_hash_salt = » ;

/**
* Base URL (optional).
*
* If Drupal is generating incorrect URLs on your site, which could
* be in HTML headers (links to CSS and JS files) or visible links on pages
* (such as in menus), uncomment the Base URL statement below (remove the
* leading hash sign) and fill in the absolute URL to your Drupal installation.
*
* You might also want to force users to use a given domain.
* See the .htaccess file for more information.
*
* Examples:
* $base_url = ‘http://www.example.com’;
* $base_url = ‘http://www.example.com:8888’;
* $base_url = ‘http://www.example.com/drupal’;
* $base_url = ‘https://www.example.com:8888/drupal’;
*
* It is not allowed to have a trailing slash; Drupal will add it
* for you.
*/
# $base_url = ‘http://www.example.com’; // NO trailing slash!

/**
* PHP settings:
*
* To see what PHP settings are possible, including whether they can be set at
* runtime (by using ini_set()), read the PHP documentation:
* http://www.php.net/manual/en/ini.list.php
* See drupal_environment_initialize() in includes/bootstrap.inc for required
* runtime settings and the .htaccess file for non-runtime settings. Settings
* defined there should not be duplicated here so as to avoid conflict issues.
*/

/**
* Some distributions of Linux (most notably Debian) ship their PHP
* installations with garbage collection (gc) disabled. Since Drupal depends on
* PHP’s garbage collection for clearing sessions, ensure that garbage
* collection occurs by using the most common settings.
*/
ini_set ( ‘session.gc_probability’ , 1 ) ;
ini_set ( ‘session.gc_divisor’ , 100 ) ;

/**
* Set session lifetime (in seconds), i.e. the time from the user’s last visit
* to the active session may be deleted by the session garbage collector. When
* a session is deleted, authenticated users are logged out, and the contents
* of the user’s $_SESSION variable is discarded.
*/
ini_set ( ‘session.gc_maxlifetime’ , 200000 ) ;

/**
* Set session cookie lifetime (in seconds), i.e. the time from the session is
* created to the cookie expires, i.e. when the browser is expected to discard
* the cookie. The value 0 means «until the browser is closed».
*/
ini_set ( ‘session.cookie_lifetime’ , 2000000 ) ;

/**
* If you encounter a situation where users post a large amount of text, and
* the result is stripped out upon viewing but can still be edited, Drupal’s
* output filter may not have sufficient memory to process it. If you
* experience this issue, you may wish to uncomment the following two lines
* and increase the limits of these variables. For more information, see
* http://php.net/manual/en/pcre.configuration.php.
*/
# ini_set(‘pcre.backtrack_limit’, 200000);
# ini_set(‘pcre.recursion_limit’, 200000);

/**
* Drupal automatically generates a unique session cookie name for each site
* based on its full domain name. If you have multiple domains pointing at the
* same Drupal site, you can either redirect them all to a single domain (see
* comment in .htaccess), or uncomment the line below and specify their shared
* base domain. Doing so assures that users remain logged in as they cross
* between your various domains. Make sure to always start the $cookie_domain
* with a leading dot, as per RFC 2109.
*/
# $cookie_domain = ‘.example.com’;

/**
* Variable overrides:
*
* To override specific entries in the ‘variable’ table for this site,
* set them here. You usually don’t need to use this feature. This is
* useful in a configuration file for a vhost or directory, rather than
* the default settings.php. Any configuration setting from the ‘variable’
* table can be given a new value. Note that any values you provide in
* these variable overrides will not be modifiable from the Drupal
* administration interface.
*
* The following overrides are examples:
* — site_name: Defines the site’s name.
* — theme_default: Defines the default theme for this site.
* — anonymous: Defines the human-readable name of anonymous users.
* Remove the leading hash signs to enable.
*/
# $conf[‘site_name’] = ‘My Drupal site’;
# $conf[‘theme_default’] = ‘garland’;
# $conf[‘anonymous’] = ‘Visitor’;

/**
* A custom theme can be set for the offline page. This applies when the site
* is explicitly set to maintenance mode through the administration page or when
* the database is inactive due to an error. It can be set through the
* ‘maintenance_theme’ key. The template file should also be copied into the
* theme. It is located inside ‘modules/system/maintenance-page.tpl.php’.
* Note: This setting does not apply to installation and update pages.
*/
# $conf[‘maintenance_theme’] = ‘bartik’;

/**
* Reverse Proxy Configuration:
*
* Reverse proxy servers are often used to enhance the performance
* of heavily visited sites and may also provide other site caching,
* security, or encryption benefits. In an environment where Drupal
* is behind a reverse proxy, the real IP address of the client should
* be determined such that the correct client IP address is available
* to Drupal’s logging, statistics, and access management systems. In
* the most simple scenario, the proxy server will add an
* X-Forwarded-For header to the request that contains the client IP
* address. However, HTTP headers are vulnerable to spoofing, where a
* malicious client could bypass restrictions by setting the
* X-Forwarded-For header directly. Therefore, Drupal’s proxy
* configuration requires the IP addresses of all remote proxies to be
* specified in $conf[‘reverse_proxy_addresses’] to work correctly.
*
* Enable this setting to get Drupal to determine the client IP from
* the X-Forwarded-For header (or $conf[‘reverse_proxy_header’] if set).
* If you are unsure about this setting, do not have a reverse proxy,
* or Drupal operates in a shared hosting environment, this setting
* should remain commented out.
*
* In order for this setting to be used you must specify every possible
* reverse proxy IP address in $conf[‘reverse_proxy_addresses’].
* If a complete list of reverse proxies is not available in your
* environment (for example, if you use a CDN) you may set the
* $_SERVER[‘REMOTE_ADDR’] variable directly in settings.php.
* Be aware, however, that it is likely that this would allow IP
* address spoofing unless more advanced precautions are taken.
*/
# $conf[‘reverse_proxy’] = TRUE;

/**
* Specify every reverse proxy IP address in your environment.
* This setting is required if $conf[‘reverse_proxy’] is TRUE.
*/
# $conf[‘reverse_proxy_addresses’] = array(‘a.b.c.d’, . );

/**
* Set this value if your proxy server sends the client IP in a header
* other than X-Forwarded-For.
*/
# $conf[‘reverse_proxy_header’] = ‘HTTP_X_CLUSTER_CLIENT_IP’;

/**
* Page caching:
*
* By default, Drupal sends a «Vary: Cookie» HTTP header for anonymous page
* views. This tells a HTTP proxy that it may return a page from its local
* cache without contacting the web server, if the user sends the same Cookie
* header as the user who originally requested the cached page. Without «Vary:
* Cookie», authenticated users would also be served the anonymous page from
* the cache. If the site has mostly anonymous users except a few known
* editors/administrators, the Vary header can be omitted. This allows for
* better caching in HTTP proxies (including reverse proxies), i.e. even if
* clients send different cookies, they still get content served from the cache.
* However, authenticated users should access the site directly (i.e. not use an
* HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid
* getting cached pages from the proxy.
*/
# $conf[‘omit_vary_cookie’] = TRUE;

/**
* CSS/JS aggregated file gzip compression:
*
* By default, when CSS or JS aggregation and clean URLs are enabled Drupal will
* store a gzip compressed (.gz) copy of the aggregated files. If this file is
* available then rewrite rules in the default .htaccess file will serve these
* files to browsers that accept gzip encoded content. This allows pages to load
* faster for these users and has minimal impact on server load. If you are
* using a webserver other than Apache httpd, or a caching reverse proxy that is
* configured to cache and compress these files itself you may want to uncomment
* one or both of the below lines, which will prevent gzip files being stored.
*/
# $conf[‘css_gzip_compression’] = FALSE;
# $conf[‘js_gzip_compression’] = FALSE;

/**
* String overrides:
*
* To override specific strings on your site with or without enabling locale
* module, add an entry to this list. This functionality allows you to change
* a small number of your site’s default English language interface strings.
*
* Remove the leading hash signs to enable.
*/
# $conf[‘locale_custom_strings_en’][»] = array(
# ‘forum’ => ‘Discussion board’,
# ‘@count min’ => ‘@count minutes’,
# );

/**
*
* IP blocking:
*
* To bypass database queries for denied IP addresses, use this setting.
* Drupal queries the table by default on every page request
* for both authenticated and anonymous users. This allows the system to
* block IP addresses from within the administrative interface and before any
* modules are loaded. However on high traffic websites you may want to avoid
* this query, allowing you to bypass database access altogether for anonymous
* users under certain caching configurations.
*
* If using this setting, you will need to add back any IP addresses which
* you may have blocked via the administrative interface. Each element of this
* array represents a blocked IP address. Uncommenting the array and leaving it
* empty will have the effect of disabling IP blocking on your site.
*
* Remove the leading hash signs to enable.
*/
# $conf[‘blocked_ips’] = array(
# ‘a.b.c.d’,
# );

Not Found

The requested URL «@path» was not found on this server.

источник

Читайте также:  Установка коренных вкладышей скания

Добавить комментарий

Adblock
detector