Dzisiejsze problemy z forum

[Nikonem]

A myślałem, że to u mnie jakiś problem Potwierdzam, jakby wczytywała się jakaś "ciężka" strona- wolno

[Cordor]

Po pewnie przez Największy cyberatak w historii! Wielka blokada sieci jak sprawne oko Bogdana raczyło zauważyć

[Mion]

Ale teraz już jest wszystko w normie, czyli szybko

[nrm]

To musiało być coś z siecią po polskiej stronie bo na serwerze dzień jak co dzień, żadnych problemów, pełna moc.

[Nikonem]

Dlaczego gdy jestem zalogowany nie widzę swojej i innych stopek? Gdy się wyloguję wszystko jest widoczne jak dawniej... Taka mała pierdoła a wkurza

[MaxPan]

chyba kliknąłeś 'ignoruj wszystkie sygnaturki"

[Nikonem]

Racja Max! Trzeba edytować profil, wejść w ustawienia ignorowania i od kliknąć "ignoruj wszystkie sygnaturki kiedy czytam tematy". Załatwione. Musiałem to kliknąć niechcący gdy dokładałem pacjenta do "ignorowanych"

[krzysiek_web]

An error occurred.

Sorry, the page you are looking for is currently unavailable.

Please try again later.

If you are the system administrator of this resource then you should check the error log for details.

Faithfully yours, nginx.

[Nikonem]

Dzisiaj miałem delikatny problem z przeglądaniem PiO (około 12:00):

An error occured with the SQL server:

This is not a problem with the IPS Community Suite but rather with your SQL server. Please contact your host and copy the message shown above.

[Gość]

@Up

Wszyscy mieli

[jimmi]

ja też miałem, ale już wszystko działa.

[M0drzew]

ja też miałem, ale już wszystko działa.

A od wczoraj takie coś losowo sie pojawia:

An error occurred.

Sorry, the page you are looking for is currently unavailable.

Please try again later.

If you are the system administrator of this resource then you should check the error log for details.

Faithfully yours, nginx.

o co chodzi?

[kamilp7]

no dzisiaj długa przerwa, coraz częściej forum ma pady

[ar4]

U mnie coś takiego wali:

Join our upcoming user conference, nginx.conf 2014.
Learn, share, and celebrate 10 years of NGINX! Oct. 20-22, Hyatt Regency San Francisco Airport.
	nginx
Core functionality
	
english
русский

简体中文
עברית
日本語
türkçe
italiano

news
about
download
security advisories
documentation
pgp keys
faq
links
books
support
donation

trac
wiki
twitter
nginx.com
blog
Example Configuration
Directives
     accept_mutex
     accept_mutex_delay
     daemon
     debug_connection
     debug_points
     error_log
     env
     events
     include
     lock_file
     master_process
     multi_accept
     pcre_jit
     pid
     ssl_engine
     timer_resolution
     use
     user
     worker_aio_requests
     worker_connections
     worker_cpu_affinity
     worker_priority
     worker_processes
     worker_rlimit_core
     worker_rlimit_nofile
     worker_rlimit_sigpending
     working_directory
Example Configuration

    user www www;
    worker_processes 2;

    error_log /var/log/nginx-error.log info;

    events {
        use kqueue;
        worker_connections 2048;
    }

    ...

Directives
Syntax: 	accept_mutex on | off;
Default: 	

accept_mutex on;

Context: 	events

If accept_mutex is enabled, worker processes will accept new connections by turn. Otherwise, all worker processes will be notified about new connections, and if volume of new connections is low, some of the worker processes may just waste system resources.

    The use of rtsig connection processing method requires accept_mutex to be enabled. 

Syntax: 	accept_mutex_delay time;
Default: 	

accept_mutex_delay 500ms;

Context: 	events

If accept_mutex is enabled, specifies the maximum time during which a worker process will try to restart accepting new connections if another worker process is currently accepting new connections.
Syntax: 	daemon on | off;
Default: 	

daemon on;

Context: 	main

Determines whether nginx should become a daemon. Mainly used during development.
Syntax: 	debug_connection address | CIDR | unix:;
Default: 	—
Context: 	events

Enables debugging log for selected client connections. Other connections will use logging level set by the error_log directive. Debugged connections are specified by IPv4 or IPv6 (1.3.0, 1.2.1) address or network. A connection may also be specified using a hostname. For connections using UNIX-domain sockets (1.3.0, 1.2.1), debugging log is enabled by the “unix:” parameter.

    events {
        debug_connection 127.0.0.1;
        debug_connection localhost;
        debug_connection 192.0.2.0/24;
        debug_connection ::1;
        debug_connection 2001:0db8::/32;
        debug_connection unix:;
        ...
    }

    For this directive to work, nginx needs to be built with --with-debug, see “A debugging log”. 

Syntax: 	debug_points abort | stop;
Default: 	—
Context: 	main

This directive is used for debugging.

When internal error is detected, e.g. the leak of sockets on restart of working processes, enabling debug_points leads to a core file creation (abort) or to stopping of a process (stop) for further analysis using a system debugger.
Syntax: 	error_log file | stderr | syslog:server=address[,parameter=value] [debug | info | notice | warn | error | crit | alert | emerg];
Default: 	

error_log logs/error.log error;

Context: 	main, http, server, location

Configures logging. Several logs can be specified on the same level (1.5.2).

The first parameter defines a file that will store the log. The special value stderr selects the standard error file. Logging to syslog can be configured by specifying the “syslog:” prefix.

The second parameter determines the level of logging. Log levels above are listed in the order of increasing severity. Setting a certain log level will cause all messages of the specified and more severe log levels to be logged. For example, the default level error will cause error, crit, alert, and emerg messages to be logged. If this parameter is omitted then error is used.

    For debug logging to work, nginx needs to be built with --with-debug, see “A debugging log”. 

Syntax: 	env variable[=value];
Default: 	

env TZ;

Context: 	main

By default, nginx removes all environment variables inherited from its parent process except the TZ variable. This directive allows preserving some of the inherited variables, changing their values, or creating new environment variables. These variables are then:

    inherited during a live upgrade of an executable file;
    used by the ngx_http_perl_module module;
    used by worker processes. One should bear in mind that controlling system libraries in this way is not always possible as it is common for libraries to check variables only during initialization, well before they can be set using this directive. An exception from this is an above mentioned live upgrade of an executable file.

The TZ variable is always inherited and available to the ngx_http_perl_module module, unless it is configured explicitly.

Usage example:

    env MALLOC_OPTIONS;
    env PERL5LIB=/data/site/modules;
    env OPENSSL_ALLOW_PROXY_CERTS=1;

    The NGINX environment variable is used internally by nginx and should not be set directly by the user. 

Syntax: 	events { ... }
Default: 	—
Context: 	main

Provides the configuration file context in which the directives that affect connection processing are specified.
Syntax: 	include file | mask;
Default: 	—
Context: 	any

Includes another file, or files matching the specified mask, into configuration. Included files should consist of syntactically correct directives and blocks.

Usage example:

    include mime.types;
    include vhosts/*.conf;

Syntax: 	lock_file file;
Default: 	

lock_file logs/nginx.lock;

Context: 	main

nginx uses the locking mechanism to implement accept_mutex and serialize access to shared memory. On most systems the locks are implemented using atomic operations, and this directive is ignored. On other systems the “lock file” mechanism is used. This directive specifies a prefix for the names of lock files.
Syntax: 	master_process on | off;
Default: 	

master_process on;

Context: 	main

Determines whether worker processes are started. This directive is intended for nginx developers.
Syntax: 	multi_accept on | off;
Default: 	

multi_accept off;

Context: 	events

If multi_accept is disabled, a worker process will accept one new connection at a time. Otherwise, a worker process will accept all new connections at a time.

    The directive is ignored if kqueue connection processing method is used, because it reports the number of new connections waiting to be accepted. 

    The use of rtsig connection processing method automatically enables multi_accept. 

Syntax: 	pcre_jit on | off;
Default: 	

pcre_jit off;

Context: 	main

This directive appeared in version 1.1.12.

Enables or disables the use of “just-in-time compilation” (PCRE JIT) for the regular expressions known by the time of configuration parsing.

PCRE JIT can speed up processing of regular expressions significantly.

    The JIT is available in PCRE libraries starting from version 8.20 built with the --enable-jit configuration parameter. When the PCRE library is built with nginx (--with-pcre=), the JIT support is enabled via the --with-pcre-jit configuration parameter. 

Syntax: 	pid file;
Default: 	

pid nginx.pid;

Context: 	main

Defines a file that will store the process ID of the main process.
Syntax: 	ssl_engine device;
Default: 	—
Context: 	main

Defines the name of the hardware SSL accelerator.
Syntax: 	timer_resolution interval;
Default: 	—
Context: 	main

Reduces timer resolution in worker processes, thus reducing the number of gettimeofday() system calls made. By default, gettimeofday() is called each time a kernel event is received. With reduced resolution, gettimeofday() is only called once per specified interval.

Example:

    timer_resolution 100ms;

Internal implementation of the interval depends on the method used:

    the EVFILT_TIMER filter if kqueue is used;
    timer_create() if eventport is used;
    setitimer() otherwise.

Syntax: 	use method;
Default: 	—
Context: 	events

Specifies the connection processing method to use. There is normally no need to specify it explicitly, because nginx will by default use the most efficient method.
Syntax: 	user user [group];
Default: 	

user nobody nobody;

Context: 	main

Defines user and group credentials used by worker processes. If group is omitted, a group whose name equals that of user is used.
Syntax: 	worker_aio_requests number;
Default: 	

worker_aio_requests 32;

Context: 	events

This directive appeared in versions 1.1.4 and 1.0.7.

When using aio with the epoll connection processing method, sets the maximum number of outstanding asynchronous I/O operations for a single worker process.
Syntax: 	worker_connections number;
Default: 	

worker_connections 512;

Context: 	events

Sets the maximum number of simultaneous connections that can be opened by a worker process.

It should be kept in mind that this number includes all connections (e.g. connections with proxied servers, among others), not only connections with clients. Another consideration is that the actual number of simultaneous connections cannot exceed the current limit on the maximum number of open files, which can be changed by worker_rlimit_nofile.
Syntax: 	worker_cpu_affinity cpumask ...;
Default: 	—
Context: 	main

Binds worker processes to the sets of CPUs. Each CPU set is represented by a bitmask of allowed CPUs. There should be a separate set defined for each of the worker processes. By default, worker processes are not bound to any specific CPUs.

For example,

    worker_processes    4;
    worker_cpu_affinity 0001 0010 0100 1000;

binds each worker process to a separate CPU, while

    worker_processes    2;
    worker_cpu_affinity 0101 1010;

binds the first worker process to CPU0/CPU2, and the second worker process to CPU1/CPU3. The second example is suitable for hyper-threading.

    The directive is only available on FreeBSD and Linux. 

Syntax: 	worker_priority number;
Default: 	

worker_priority 0;

Context: 	main

Defines the scheduling priority for worker processes like it is done by the nice command: a negative number means higher priority. Allowed range normally varies from -20 to 20.

Example:

    worker_priority -10;

Syntax: 	worker_processes number | auto;
Default: 	

worker_processes 1;

Context: 	main

Defines the number of worker processes.

The optimal value depends on many factors including (but not limited to) the number of CPU cores, the number of hard disk drives that store data, and load pattern. When one is in doubt, setting it to the number of available CPU cores would be a good start (the value “auto” will try to autodetect it).

    The auto parameter is supported starting from versions 1.3.8 and 1.2.5. 

Syntax: 	worker_rlimit_core size;
Default: 	—
Context: 	main

Changes the limit on the largest size of a core file (RLIMIT_CORE) for worker processes. Used to increase the limit without restarting the main process.
Syntax: 	worker_rlimit_nofile number;
Default: 	—
Context: 	main

Changes the limit on the maximum number of open files (RLIMIT_NOFILE) for worker processes. Used to increase the limit without restarting the main process.
Syntax: 	worker_rlimit_sigpending number;
Default: 	—
Context: 	main

On systems that support rtsig connection processing method, changes the limit on the number of signals that may be queued (RLIMIT_SIGPENDING) for worker processes. Used to increase the limit without restarting the main process.
Syntax: 	working_directory directory;
Default: 	—
Context: 	main

Defines the current working directory for a worker process. It is primarily used when writing a core-file, in which case a worker process should have write permission for the specified directory.

[Marches]

ja mam taki problem

"

There appears to be an error with the database.

If you are seeing this page, it means there was a problem communicating with our database. Sometimes this error is temporary and will go away when you refresh the page. Sometimes the error will need to be fixed by an administrator before the site will become accessible again.

You can try to refresh the page by clicking here"

kiedy zostanie to naprawione bo psycha mi siada