VPF::Ошибки апатча - Форум программистов

Nightwalker

Дата 11.1.2007, 21:02 (ссылка)

(нет голосов)

Загрузка ...

Опытный

Профиль
Группа: Участник
Сообщений: 505
Регистрация: 15.9.2005

Репутация: -1
Всего: -18

Всем привет!Кто знает что за ошибки в логах.

Файл Error
[Thu Jan 11 16:15:55 2007] [notice] Apache/2.2.4 (Win32) configured -- resuming normal operations
[Thu Jan 11 16:15:55 2007] [notice] Server built: Jan 9 2007 23:17:20
[Thu Jan 11 16:15:55 2007] [notice] Parent: Created child process 5132
[Thu Jan 11 16:15:57 2007] [notice] Child 5132: Child process is running
[Thu Jan 11 16:15:57 2007] [notice] Child 5132: Acquired the start mutex.
[Thu Jan 11 16:15:57 2007] [notice] Child 5132: Starting 250 worker threads.
[Thu Jan 11 16:15:57 2007] [notice] Child 5132: Starting thread to listen on port 80.
[Thu Jan 11 16:16:57 2007] [error] [client 127.0.0.1] (OS 3)Системе не удается найти указанный путь. : couldn't create child process: 720003: test.cgi
[Thu Jan 11 16:16:57 2007] [error] [client 127.0.0.1] (OS 3)Системе не удается найти указанный путь. : couldn't spawn child process: D:/localhost/cgi/test.cgi
[Thu Jan 11 16:17:02 2007] [error] [client 127.0.0.1] (OS 3)Системе не удается найти указанный путь. : couldn't create child process: 720003: test.cgi
[Thu Jan 11 16:17:02 2007] [error] [client 127.0.0.1] (OS 3)Системе не удается найти указанный путь. : couldn't spawn child process: D:/localhost/cgi/test.cgi
[Thu Jan 11 16:17:03 2007] [error] [client 127.0.0.1] (OS 3)Системе не удается найти указанный путь. : couldn't create child process: 720003: test.cgi
[Thu Jan 11 16:17:03 2007] [error] [client 127.0.0.1] (OS 3)Системе не удается найти указанный путь. : couldn't spawn child process: D:/localhost/cgi/test.cgi
[Thu Jan 11 16:17:04 2007] [error] [client 127.0.0.1] (OS 3)Системе не удается найти указанный путь. : couldn't create child process: 720003: test.cgi
[Thu Jan 11 16:17:04 2007] [error] [client 127.0.0.1] (OS 3)Системе не удается найти указанный путь. : couldn't spawn child process: D:/localhost/cgi/test.cgi
[Thu Jan 11 16:17:05 2007] [error] [client 127.0.0.1] (OS 3)Системе не удается найти указанный путь. : couldn't create child process: 720003: test.cgi
[Thu Jan 11 16:17:05 2007] [error] [client 127.0.0.1] (OS 3)Системе не удается найти указанный путь. : couldn't spawn child process: D:/localhost/cgi/test.cgi
[Thu Jan 11 16:17:09 2007] [error] [client 127.0.0.1] File does not exist: D:/localhost/www/cgi
[Thu Jan 11 16:17:13 2007] [error] [client 127.0.0.1] (OS 3)Системе не удается найти указанный путь. : couldn't create child process: 720003: test.cgi
[Thu Jan 11 16:17:13 2007] [error] [client 127.0.0.1] (OS 3)Системе не удается найти указанный путь. : couldn't spawn child process: D:/localhost/cgi/test.cgi
[Thu Jan 11 16:17:16 2007] [error] [client 127.0.0.1] (OS 3)Системе не удается найти указанный путь. : couldn't create child process: 720003: test.cgi
[Thu Jan 11 16:17:16 2007] [error] [client 127.0.0.1] (OS 3)Системе не удается найти указанный путь. : couldn't spawn child process: D:/localhost/cgi/test.cgi
[Thu Jan 11 16:19:04 2007] [notice] Parent: Received shutdown signal -- Shutting down the server.
[Thu Jan 11 16:19:04 2007] [notice] Child 5132: Exit event signaled. Child process is ending.
[Thu Jan 11 16:19:05 2007] [notice] Child 5132: Released the start mutex
[Thu Jan 11 16:19:06 2007] [notice] Child 5132: Waiting for 250 worker threads to exit.
[Thu Jan 11 16:19:06 2007] [notice] Child 5132: All worker threads have exited.
[Thu Jan 11 16:19:06 2007] [notice] Child 5132: Child process is exiting
[Thu Jan 11 16:19:06 2007] [notice] Parent: Child process exited successfully.

Файл access

127.0.0.1 - - [11/Jan/2007:16:16:57 +0000] "GET /cgi-bin/test.cgi HTTP/1.1" 500 521
127.0.0.1 - - [11/Jan/2007:16:17:02 +0000] "GET /cgi-bin/test.cgi HTTP/1.1" 500 521
127.0.0.1 - - [11/Jan/2007:16:17:03 +0000] "GET /cgi-bin/test.cgi HTTP/1.1" 500 521
127.0.0.1 - - [11/Jan/2007:16:17:04 +0000] "GET /cgi-bin/test.cgi HTTP/1.1" 500 521
127.0.0.1 - - [11/Jan/2007:16:17:05 +0000] "GET /cgi-bin/test.cgi HTTP/1.1" 500 521
127.0.0.1 - - [11/Jan/2007:16:17:09 +0000] "GET /cgi/test.cgi HTTP/1.1" 404 210
127.0.0.1 - - [11/Jan/2007:16:17:13 +0000] "GET /cgi-bin/test.cgi HTTP/1.1" 500 521
127.0.0.1 - - [11/Jan/2007:16:17:16 +0000] "GET /cgi-bin/test.cgi HTTP/1.1" 500 521

Апач не запускается.что это за ошибки?как их исправить?

Nicholas_S

Дата 11.1.2007, 21:49 (ссылка)

(нет голосов)

Загрузка ...

Опытный

Профиль
Группа: Участник
Сообщений: 486
Регистрация: 12.10.2006
Где: Санкт-Петербург

Репутация: нет
Всего: 19

Скорее всего проблема в путях к интерпретатору (Perl?)

"File does not exist: D:/localhost/www/cgi"

Пропиши полный путь в cgi-скрипте, а также в httpd.conf.
Может быть поможет.

--------------------

...все в мире относительно

Nightwalker

Дата 12.1.2007, 15:28 (ссылка)

(нет голосов)

Загрузка ...

Опытный

Профиль
Группа: Участник
Сообщений: 505
Регистрация: 15.9.2005

Репутация: -1
Всего: -18

Прописал всё равно не помогает.

Nightwalker

Дата 12.1.2007, 20:19 (ссылка)

(нет голосов)

Загрузка ...

Опытный

Профиль
Группа: Участник
Сообщений: 505
Регистрация: 15.9.2005

Репутация: -1
Всего: -18

Вот прикрепил конфиг файл.Посмотрите что ту не так плизз.

Присоединённый файл ( Кол-во скачиваний: 2 )

config.txt 17,98 Kb

marykone

Дата 18.1.2007, 15:56 (ссылка)

(нет голосов)

Загрузка ...

Эксперт

Профиль
Группа: Комодератор
Сообщений: 2722
Регистрация: 2.5.2006
Где: Краснодар

Репутация: 1
Всего: 67

не уверен но попробуй мой вариант

Цитата

  ScriptInterpreterSource registry

LoadModule php5_module D:\Webserver\php\php5apache2.dll
AddType Application/x-httpd-php php php3 php4 php5 phtml

#
# This is the main Apache HTTP server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.2/> for detailed information.
# In particular, see
# <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
# for a discussion of each configuration directive.
#
# Do NOT simply read the instructions in here without understanding
# what they do.  They're here only as hints or reminders.  If you are unsure
# consult the online docs. You have been warned.
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path.  If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
# with ServerRoot set to "D:/Webserver/Apache" will be interpreted by the
# server as "D:/Webserver/Apache/logs/foo.log".
#
# NOTE: Where filenames are specified, you must use forward slashes
# instead of backslashes (e.g., "c:/apache" instead of "c:\apache").
# If a drive letter is omitted, the drive on which Apache.exe is located
# will be used by default.  It is recommended that you always supply
# an explicit drive letter in absolute paths, however, to avoid
# confusion.
#

# ThreadsPerChild: constant number of worker threads in the server process
# MaxRequestsPerChild: maximum  number of requests a server process serves
ThreadsPerChild 250
MaxRequestsPerChild  0

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# Do not add a slash at the end of the directory path.  If you point
# ServerRoot at a non-local disk, be sure to point the LockFile directive
# at a local disk.  If you wish to share the same ServerRoot for multiple
# httpd daemons, you will need to change at least LockFile and PidFile.
#
ServerRoot "D:/Webserver/Apache"

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses (0.0.0.0)
#
#Listen 12.34.56.78:80
Listen 80

#
# Dynamic Shared Object (DSO) Support
#
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
#
# Example:
# LoadModule foo_module modules/mod_foo.so
#
LoadModule actions_module modules/mod_actions.so
LoadModule alias_module modules/mod_alias.so
LoadModule asis_module modules/mod_asis.so
LoadModule auth_basic_module modules/mod_auth_basic.so
#LoadModule auth_digest_module modules/mod_auth_digest.so
#LoadModule authn_anon_module modules/mod_authn_anon.so
#LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authn_file_module modules/mod_authn_file.so
#LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_host_module modules/mod_authz_host.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule autoindex_module modules/mod_autoindex.so
#LoadModule cern_meta_module modules/mod_cern_meta.so
LoadModule cgi_module modules/mod_cgi.so
#LoadModule dav_module modules/mod_dav.so
#LoadModule dav_fs_module modules/mod_dav_fs.so
#LoadModule deflate_module modules/mod_deflate.so
LoadModule dir_module modules/mod_dir.so
LoadModule env_module modules/mod_env.so
#LoadModule expires_module modules/mod_expires.so
#LoadModule file_cache_module modules/mod_file_cache.so
#LoadModule headers_module modules/mod_headers.so
LoadModule imagemap_module modules/mod_imagemap.so
LoadModule include_module modules/mod_include.so
#LoadModule info_module modules/mod_info.so
LoadModule isapi_module modules/mod_isapi.so
LoadModule log_config_module modules/mod_log_config.so
LoadModule mime_module modules/mod_mime.so
#LoadModule mime_magic_module modules/mod_mime_magic.so
#LoadModule proxy_module modules/mod_proxy.so
#LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
#LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
#LoadModule proxy_connect_module modules/mod_proxy_connect.so
#LoadModule proxy_http_module modules/mod_proxy_http.so
#LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule negotiation_module modules/mod_negotiation.so
#LoadModule rewrite_module modules/mod_rewrite.so
LoadModule setenvif_module modules/mod_setenvif.so
#LoadModule speling_module modules/mod_speling.so
#LoadModule status_module modules/mod_status.so
#LoadModule unique_id_module modules/mod_unique_id.so
LoadModule userdir_module modules/mod_userdir.so
#LoadModule usertrack_module modules/mod_usertrack.so
#LoadModule vhost_alias_module modules/mod_vhost_alias.so
#LoadModule ssl_module modules/mod_ssl.so

# 'Main' server configuration
#
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition.  These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
#
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#

#
# ServerAdmin: Your address, where problems with the server should be
# e-mailed.  This address appears on some server-generated pages, such
# as error documents.  e.g. [email protected]
#
ServerAdmin @

#
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If your host doesn't have a registered DNS name, enter its IP address here.
#
ServerName localhost:80

#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot "D:/localhost/www" ############## сдесь полный путь к Файлу для загрузки

#
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
#
# First, we configure the "default" to be a very restrictive set of
# features.
#
<Directory D: > #################
    Options FollowSymLinks
    AllowOverride None
    Order deny,allow
    Deny from all
    Satisfy all
</Directory>

<Directory "d:/localhost/www"> ######### сдесь попробуй без www
Options Indexes Includes
AllowOverride All
Order allow,deny
Allow from all
</Directory>

#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#

#
# This should be changed to whatever you set DocumentRoot to.
#
<Directory "D:/Webserver/Apache/htdocs">
    #
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    #   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    #
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    #
    # The Options directive is both complicated and important.  Please see
    # http://httpd.apache.org/docs/2.2/mod/core.html#options
    # for more information.
    #
    Options Indexes FollowSymLinks

    #
    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    #   Options FileInfo AuthConfig Limit
    #
    AllowOverride None

    #
    # Controls who can get stuff from this server.
    #
    Order allow,deny
    Allow from all

</Directory>

#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
<IfModule dir_module>
    DirectoryIndex index.html index.php
</IfModule>

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<FilesMatch "^\.ht">
    Order allow,deny
    Deny from all
</FilesMatch>

#
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog D:/localhost/www/logs/error.log

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

<IfModule log_config_module>
    #
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    #
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common

    <IfModule logio_module>
      # You need to enable mod_logio.c to use %I and %O
      LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
    </IfModule>

    #
    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here.  Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    #
    CustomLog D:/localhost/www/logs/access.log common

    #
    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #
    #CustomLog logs/access.log combined
</IfModule>

<IfModule alias_module>
    #
    # Redirect: Allows you to tell clients about documents that used to
    # exist in your server's namespace, but do not anymore. The client
    # will make a new request for the document at its new location.
    # Example:
    # Redirect permanent /foo http://localhost/bar

    #
    # Alias: Maps web paths into filesystem paths and is used to
    # access content that does not live under the DocumentRoot.
    # Example:
    # Alias /webpath /full/filesystem/path
    #
    # If you include a trailing / on /webpath then the server will
    # require it to be present in the URL.  You will also likely
    # need to provide a <Directory> section to allow access to
    # the filesystem path.

    #
    # ScriptAlias: This controls which directories contain server scripts.
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the target directory are treated as applications and
    # run by the server when requested rather than as documents sent to the
    # client.  The same rules about trailing "/" apply to ScriptAlias
    # directives as to Alias.
    #
    ScriptAlias /cgi-bin/ "D:/localhost/cgi/"

</IfModule>

#
# "D:/Webserver/Apache/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "D:/localhost/cgi/">
    AllowOverride None
    Options ExecCGI
    Order allow,deny
    Allow from all
</Directory>

#
# Apache parses all CGI scripts for the shebang line by default.
# This comment line, the first line of the script, consists of the symbols
# pound (#) and exclamation (!) followed by the path of the program that
# can execute this specific script.  For a perl script, with perl.exe in
# the C:\Program Files\Perl directory, the shebang line should be:

   #!c:/program files/perl/perl

# Note you _must_not_ indent the actual shebang line, and it must be the
# first line of the file.  Of course, CGI processing must be enabled by
# the appropriate ScriptAlias or Options ExecCGI directives for the files
# or directory in question.
#
# However, Apache on Windows allows either the Unix behavior above, or can
# use the Registry to match files by extention.  The command to execute
# a file of this type is retrieved from the registry by the same method as
# the Windows Explorer would use to handle double-clicking on a file.
# These script actions can be configured from the Windows Explorer View menu,
# 'Folder Options', and reviewing the 'File Types' tab.  Clicking the Edit
# button allows you to modify the Actions, of which Apache 1.3 attempts to
# perform the 'Open' Action, and failing that it will try the shebang line.
# This behavior is subject to change in Apache release 2.0.
#
# Each mechanism has it's own specific security weaknesses, from the means
# to run a program you didn't intend the website owner to invoke, and the
# best method is a matter of great debate.
#
# To enable the this Windows specific behavior (and therefore -disable- the
# equivilant Unix behavior), uncomment the following directive:
#
#ScriptInterpreterSource registry
#
# The directive above can be placed in individual <Directory> blocks or the
# .htaccess file, with either the 'registry' (Windows behavior) or 'script'
# (Unix behavior) option, and will override this server default option.
#

#
# DefaultType: the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value.  If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
#
DefaultType text/plain

<IfModule mime_module>
    #
    # TypesConfig points to the file containing the list of mappings from
    # filename extension to MIME-type.
    #
    TypesConfig conf/mime.types

    #
    # AddType allows you to add to or override the MIME configuration
    # file specified in TypesConfig for specific file types.
    #
    #AddType application/x-gzip .tgz
    #
    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    #
    #AddEncoding x-compress .Z
    #AddEncoding x-gzip .gz .tgz
    #
    # If the AddEncoding directives above are commented-out, then you
    # probably should define those extensions to indicate media types:
    #
    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz

    #
    # AddHandler allows you to map certain file extensions to "handlers":
    # actions unrelated to filetype. These can be either built into the server
    # or added with the Action directive (see below)
    #
    # To use CGI scripts outside of ScriptAliased directories:
    # (You will also need to add "ExecCGI" to the "Options" directive.)
    #
    AddHandler cgi-script .cgi .pl

    # For type maps (negotiated resources):
    #AddHandler type-map var

    #
    # Filters allow you to process content before it is sent to the client.
    #
    # To parse .shtml files for server-side includes (SSI):
    # (You will also need to add "Includes" to the "Options" directive.)
    #
    #AddType text/html .shtml
    #AddOutputFilter INCLUDES .shtml
</IfModule>

#
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type.  The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#
#MIMEMagicFile conf/magic

#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://localhost/subscription_info.html
#

#
# EnableMMAP and EnableSendfile: On systems that support it,
# memory-mapping or the sendfile syscall is used to deliver
# files.  This usually improves server performance, but must
# be turned off when serving from networked-mounted
# filesystems or if support for these functions is otherwise
# broken on your system.
#
#EnableMMAP off
#EnableSendfile off

# Supplemental configuration
#
# The configuration files in the conf/extra/ directory can be
# included to add extra features or to modify the default configuration of
# the server, or you may simply copy their contents here and change as
# necessary.

# Server-pool management (MPM specific)
#Include conf/extra/httpd-mpm.conf

# Multi-language error messages
#Include conf/extra/httpd-multilang-errordoc.conf

# Fancy directory listings
#Include conf/extra/httpd-autoindex.conf

# Language settings
#Include conf/extra/httpd-languages.conf

# User home directories
#Include conf/extra/httpd-userdir.conf

# Real-time info on requests and configuration
#Include conf/extra/httpd-info.conf

# Virtual hosts
#Include conf/extra/httpd-vhosts.conf

# Local access to the Apache HTTP Server Manual
#Include conf/extra/httpd-manual.conf

# Distributed authoring and versioning (WebDAV)
#Include conf/extra/httpd-dav.conf

# Various default settings
#Include conf/extra/httpd-default.conf

# Secure (SSL/TLS) connections
#Include conf/extra/httpd-ssl.conf
#
# Note: The following must must be present to support
#       starting without SSL on platforms with no /dev/random equivalent
#       but a statically compiled-in mod_ssl.
#
<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>

я поправки выделял ##### таким образом, надеюсь я правильно помню

Добавлено @ 15:57
да еще структуру папок(где файл загружаемый лежит) можно для наглядности

--------------------

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

Nightwalker

Дата 18.1.2007, 17:12 (ссылка)

(нет голосов)

Загрузка ...

Опытный

Профиль
Группа: Участник
Сообщений: 505
Регистрация: 15.9.2005

Репутация: -1
Всего: -18

Всем привет!Устанавил заново как по статье сказано.Даже такие пути как там прописывал.Всё работает.Но при запуске файла теста базы MYSQL появляется такая ошибка.

Current PHP version: 5.1.4
Fatal error: Call to undefined function mysql_connect() in C:\Program Files\Apache Group\Apache2\htdocs\test2.php on line 11

Скажите пожалуйста что не так сделанно?

Прикрепляю два конфига.Скажите плизз что не так.

Присоединённый файл ( Кол-во скачиваний: 3 )

config.rar 25,28 Kb

marykone

Дата 18.1.2007, 17:34 (ссылка)

(нет голосов)

Загрузка ...

Эксперт

Профиль
Группа: Комодератор
Сообщений: 2722
Регистрация: 2.5.2006
Где: Краснодар

Репутация: 1
Всего: 67

Цитата

test2.php

у тебя там ошибка в 11 строчке (это тебе компилятоор говорит а не апач)

--------------------

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

Nightwalker

Дата 18.1.2007, 18:00 (ссылка)

(нет голосов)

Загрузка ...

Опытный

Профиль
Группа: Участник
Сообщений: 505
Регистрация: 15.9.2005

Репутация: -1
Всего: -18

Да но у меня ничего что под базу джанных идёт ничего не работает.

marykone

Дата 18.1.2007, 18:10 (ссылка)

(нет голосов)

Загрузка ...

Эксперт

Профиль
Группа: Комодератор
Сообщений: 2722
Регистрация: 2.5.2006
Где: Краснодар

Репутация: 1
Всего: 67

почитай что нибуть про php и mysql наверное ты забыл что то объявить (mysql_connect())

а вообще советую создать новый топик а еще лучше почитать а потом создать

--------------------

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

cardinal777

Дата 8.6.2007, 01:32 (ссылка)

(нет голосов)

Загрузка ...

Новичок

Профиль
Группа: Участник
Сообщений: 10
Регистрация: 22.4.2007

Репутация: нет
Всего: нет

Цитата(Nightwalker @ 11.1.2007, 21:02)

Всем привет!Кто знает что за ошибки в логах.

[Thu Jan 11 16:19:04 2007] [notice] Parent: Received shutdown signal -- Shutting down the server.
[Thu Jan 11 16:19:04 2007] [notice] Child 5132: Exit event signaled. Child process is ending.
[Thu Jan 11 16:19:05 2007] [notice] Child 5132: Released the start mutex
[Thu Jan 11 16:19:06 2007] [notice] Child 5132: Waiting for 250 worker threads to exit.
[Thu Jan 11 16:19:06 2007] [notice] Child 5132: All worker threads have exited.
[Thu Jan 11 16:19:06 2007] [notice] Child 5132: Child process is exiting
[Thu Jan 11 16:19:06 2007] [notice] Parent: Child process exited successfully.

ну кто-нибудь подскажите чего делать-то?

Самое интересное в том, что файл исполнялся все тип-топ. Через какое-то время (в минутах) полезла ошибка. ничего не понимаю. smile

нужна помощь.

Добавлено через 1 минуту и 2 секунды
[Fri Jun 08 02:24:24 2007] [notice] Server built: Oct 9 2005 19:16:56
[Fri Jun 08 02:24:24 2007] [notice] Parent: Created child process 1140
[Fri Jun 08 02:24:24 2007] [notice] Child 1140: Child process is running
[Fri Jun 08 02:24:24 2007] [notice] Child 1100: Released the start mutex
[Fri Jun 08 02:24:24 2007] [notice] Child 1140: Acquired the start mutex.
[Fri Jun 08 02:24:24 2007] [notice] Child 1140: Starting 950 worker threads.
[Fri Jun 08 02:24:25 2007] [notice] Child 1100: Waiting for 250 worker threads to exit.
[Fri Jun 08 02:24:28 2007] [notice] Child 1100: All worker threads have exited.
[Fri Jun 08 02:24:28 2007] [notice] Child 1100: Child process is exiting
[Fri Jun 08 02:25:52 2007] [notice] Parent: Received restart signal -- Restarting the server.
[Fri Jun 08 02:25:53 2007] [notice] Child 1140: Exit event signaled. Child process is ending.
[Fri Jun 08 02:25:53 2007] [notice] Apache/2.0.55 (Win32) PHP/5.1.4 configured -- resuming normal operations
[Fri Jun 08 02:25:53 2007] [notice] Server built: Oct 9 2005 19:16:56
[Fri Jun 08 02:25:53 2007] [notice] Parent: Created child process 6800
[Fri Jun 08 02:25:53 2007] [notice] Child 6800: Child process is running
[Fri Jun 08 02:25:54 2007] [notice] Child 1140: Released the start mutex
[Fri Jun 08 02:25:54 2007] [notice] Child 6800: Acquired the start mutex.
[Fri Jun 08 02:25:54 2007] [notice] Child 6800: Starting 450 worker threads.
[Fri Jun 08 02:25:55 2007] [notice] Child 1140: Waiting for 950 worker threads to exit.
[Fri Jun 08 02:25:55 2007] [notice] Child 1140: All worker threads have exited.
[Fri Jun 08 02:25:55 2007] [notice] Child 1140: Child process is exiting

Добавлено через 8 минут и 17 секунд
вот прога optiperl стала выдавать ошибку:

syntax error at line 72, at EOF

вот скрипт:
70-72 строчки

Код


print <<END_of_Start;

</table></body></html>
END_of_Start

ЗЫ: поставить в конце ; не предлагать!!!

cardinal777

Дата 8.6.2007, 02:03 (ссылка)

(нет голосов)

Загрузка ...

Новичок

Профиль
Группа: Участник
Сообщений: 10
Регистрация: 22.4.2007

Репутация: нет
Всего: нет

Господа, проблема решилась сама собой. оно как перестало работать так и заработало. smile

0 Пользователей читают эту тему (0 Гостей и 0 Скрытых Пользователей)
0 Пользователей:
« Предыдущая тема \| Продвижение и оптимизация сайтов \| Следующая тема »