MYSQL docker file - docker

I have a mysql docker file as follows:
FROM mysql:latest
ENV MYSQL_ROOT_PASSWORD password
ENV MYSQL_DATABASE database
ENV MYSQL_USER root
ENV MYSQL_PASSWORD mysql007
ENV COMPOSE_CONVERT_WINDOWS_PATHS 1
COPY init.sql /docker-entrypoint-initdb.d/
RUN chmod a+x /docker-entrypoint-initdb.d/init.sql && chown root:root /docker-entrypoint-initdb.d/init.sql
EXPOSE 3306
CMD ["mysqld"]
I build the file using the following command on docker terminal:
docker build --build-arg http_proxy=<value> --build-arg https_proxy=<value> -f mySQL_Dockerfile -t mysql .
Whenever I run the docker file it gives me the following log and exits:
Initializing database
2017-03-14T08:58:57.139375Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-03-14T08:58:57.538155Z 0 [Warning] InnoDB: New log files created, LSN=45790
2017-03-14T08:58:57.667334Z 0 [Warning] InnoDB: Creating foreign key constraint system tables.
2017-03-14T08:58:57.726216Z 0 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: 757aecb4-0894-11e7-9b9f-0242
ac110002.
2017-03-14T08:58:57.729630Z 0 [Warning] Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.
2017-03-14T08:58:57.732463Z 1 [Warning] root#localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.
2017-03-14T08:59:02.299741Z 1 [Warning] 'user' entry 'root#localhost' ignored in --skip-name-resolve mode.
2017-03-14T08:59:02.299874Z 1 [Warning] 'user' entry 'mysql.sys#localhost' ignored in --skip-name-resolve mode.
2017-03-14T08:59:02.299916Z 1 [Warning] 'db' entry 'sys mysql.sys#localhost' ignored in --skip-name-resolve mode.
2017-03-14T08:59:02.299950Z 1 [Warning] 'proxies_priv' entry '# root#localhost' ignored in --skip-name-resolve mode.
2017-03-14T08:59:02.300070Z 1 [Warning] 'tables_priv' entry 'sys_config mysql.sys#localhost' ignored in --skip-name-resolve mode.
Database initialized
Initializing certificates
Generating a 2048 bit RSA private key
.....+++
.......................................+++
unable to write 'random state'
writing new private key to 'ca-key.pem'
-----
Generating a 2048 bit RSA private key
...............+++
..........+++
unable to write 'random state'
writing new private key to 'server-key.pem'
-----
Generating a 2048 bit RSA private key
..............................+++
............+++
unable to write 'random state'
writing new private key to 'client-key.pem'
-----
Certificates initialized
MySQL init process in progress...
2017-03-14T08:59:05.114256Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-03-14T08:59:05.118407Z 0 [Note] mysqld (mysqld 5.7.17) starting as process 77 ...
2017-03-14T08:59:05.121736Z 0 [Note] InnoDB: PUNCH HOLE support available
2017-03-14T08:59:05.121870Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-03-14T08:59:05.121904Z 0 [Note] InnoDB: Uses event mutexes
2017-03-14T08:59:05.121942Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-03-14T08:59:05.121958Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-03-14T08:59:05.121974Z 0 [Note] InnoDB: Using Linux native AIO
2017-03-14T08:59:05.122514Z 0 [Note] InnoDB: Number of pools: 1
2017-03-14T08:59:05.122715Z 0 [Note] InnoDB: Using CPU crc32 instructions
2017-03-14T08:59:05.124223Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2017-03-14T08:59:05.135947Z 0 [Note] InnoDB: Completed initialization of buffer pool
2017-03-14T08:59:05.137985Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2017-03-14T08:59:05.150094Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2017-03-14T08:59:05.161065Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2017-03-14T08:59:05.161215Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2017-03-14T08:59:05.337319Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2017-03-14T08:59:05.341242Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2017-03-14T08:59:05.341492Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2017-03-14T08:59:05.345441Z 0 [Note] InnoDB: Waiting for purge to start
2017-03-14T08:59:05.395911Z 0 [Note] InnoDB: 5.7.17 started; log sequence number 2534561
2017-03-14T08:59:05.397917Z 0 [Note] Plugin 'FEDERATED' is disabled.
2017-03-14T08:59:05.405692Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2017-03-14T08:59:05.431196Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.
2017-03-14T08:59:05.431990Z 0 [Warning] CA certificate ca.pem is self signed.
2017-03-14T08:59:05.434311Z 0 [Note] InnoDB: Buffer pool(s) load completed at 170314 8:59:05
2017-03-14T08:59:05.444568Z 0 [Warning] 'user' entry 'root#localhost' ignored in --skip-name-resolve mode.
2017-03-14T08:59:05.444699Z 0 [Warning] 'user' entry 'mysql.sys#localhost' ignored in --skip-name-resolve mode.
2017-03-14T08:59:05.444743Z 0 [Warning] 'db' entry 'sys mysql.sys#localhost' ignored in --skip-name-resolve mode.
2017-03-14T08:59:05.444773Z 0 [Warning] 'proxies_priv' entry '# root#localhost' ignored in --skip-name-resolve mode.
2017-03-14T08:59:05.446269Z 0 [Warning] 'tables_priv' entry 'sys_config mysql.sys#localhost' ignored in --skip-name-resolve mode.
2017-03-14T08:59:05.451149Z 0 [Note] Event Scheduler: Loaded 0 events
2017-03-14T08:59:05.451397Z 0 [Note] Executing 'SELECT * FROM INFORMATION_SCHEMA.TABLES;' to get a list of tables using the deprecated partition engine. You may use the startup option '--disable-parti
tion-engine-check' to skip this check.
2017-03-14T08:59:05.451433Z 0 [Note] Beginning of list of non-natively partitioned tables
2017-03-14T08:59:05.460184Z 0 [Note] End of list of non-natively partitioned tables
2017-03-14T08:59:05.460451Z 0 [Note] mysqld: ready for connections.
Version: '5.7.17' socket: '/var/run/mysqld/mysqld.sock' port: 0 MySQL Community Server (GPL)
Warning: Unable to load '/usr/share/zoneinfo/iso3166.tab' as time zone. Skipping it.
Warning: Unable to load '/usr/share/zoneinfo/leap-seconds.list' as time zone. Skipping it.
Warning: Unable to load '/usr/share/zoneinfo/zone.tab' as time zone. Skipping it.
2017-03-14T08:59:08.290703Z 5 [Warning] 'user' entry 'root#localhost' ignored in --skip-name-resolve mode.
2017-03-14T08:59:08.290960Z 5 [Warning] 'user' entry 'mysql.sys#localhost' ignored in --skip-name-resolve mode.
2017-03-14T08:59:08.291016Z 5 [Warning] 'db' entry 'sys mysql.sys#localhost' ignored in --skip-name-resolve mode.
2017-03-14T08:59:08.291115Z 5 [Warning] 'proxies_priv' entry '# root#localhost' ignored in --skip-name-resolve mode.
2017-03-14T08:59:08.291157Z 5 [Warning] 'tables_priv' entry 'sys_config mysql.sys#localhost' ignored in --skip-name-resolve mode.
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 1396 (HY000) at line 1: Operation CREATE USER failed for 'root'#'%'
Any idea what the problem could be? It says the root user creation failed and exits!
Thanks.

Turns out the suggested answer works but on a different version of the mysql image. It doesn't seem to be working for mysql:latest. I changed to mysql:5.7 and the suggested solution worked just fine.

I encountered the same problem, the fix is easy, If you want to use root as your user, just set MYSQL_ROOT_PASSWORD, don't set MYSQL_PASSWORD, checkout this post.

Related

Crunchy Postgres log messages

I am new to Crunchy Postgres, and recently I installed a Crunchy PostgresCluster on an openshift environment. After the cluster was started, I had a look at the container log messages.
I also checked script startup.sh , which is called during Postgresql startup. In this shell script, there are some lines (begin with echo_info) used for log messsages, for example:
echo_info "Starting PostgreSQL.."
But I could not see this message in the logs.
NAME READY STATUS RESTARTS AGE ROLE
demo-instance1-4vtv-0 5/5 Running 0 7h36m replica
demo-instance1-dg7j-0 5/5 Running 0 7h36m replica
demo-instance1-f696-0 5/5 Running 0 7h36m master
:~$ oc logs -f demo-instance1-f696-0 -c database | more
2022-07-08 07:42:31,064 INFO: No PostgreSQL configuration items changed, nothing to reload.
2022-07-08 07:42:31,068 INFO: Lock owner: None; I am demo-instance1-f696-0
2022-07-08 07:42:31,383 INFO: trying to bootstrap a new cluster
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.
The database cluster will be initialized with locale "en_US.utf-8".
The default text search configuration will be set to "english".
Data page checksums are enabled.
fixing permissions on existing directory /pgdata/pg14 ... ok
creating directory /pgdata/pg14_wal ... ok
creating subdirectories ... ok
selecting dynamic shared memory implementation ... posix
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default time zone ... UTC
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
syncing data to disk ... ok
initdb: warning: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run initdb.
Success. You can now start the database server using:
/usr/pgsql-14/bin/pg_ctl -D /pgdata/pg14 -l logfile start
2022-07-08 07:42:35.953 UTC [92] LOG: pgaudit extension initialized
2022-07-08 07:42:35,955 INFO: postmaster pid=92
/tmp/postgres:5432 - no response
2022-07-08 07:42:35.998 UTC [92] LOG: redirecting log output to logging collector process
2022-07-08 07:42:35.998 UTC [92] HINT: Future log output will appear in directory "log".
/tmp/postgres:5432 - accepting connections
/tmp/postgres:5432 - accepting connections
2022-07-08 07:42:37,038 INFO: establishing a new patroni connection to the postgres cluster
2022-07-08 07:42:37,334 INFO: running post_bootstrap
2022-07-08 07:42:37,754 INFO: initialized a new cluster
2022-07-08 07:42:38,039 INFO: no action. I am (demo-instance1-f696-0), the leader with the lock
2022-07-08 07:42:48,504 INFO: no action. I am (demo-instance1-f696-0), the leader with the lock
2022-07-08 07:42:58,476 INFO: no action. I am (demo-instance1-f696-0), the leader with the lock
2022-07-08 07:43:08,497 INFO: no action. I am (demo-instance1-f696-0), the leader with the lock

I'm having the following issues when trying to access MySQL on my Win10

MySQL Service detected with wrong path
10:34:59 a. m. [mysql] Change XAMPP MySQL and Control Panel settings or
10:34:59 a. m. [mysql] Uninstall/disable the other service manually first
10:34:59 a. m. [mysql] Found Path: "C:\Program Files (x86)\MySQL\MySQL Server 6.0\bin\mysqld" --defaults-file="C:\Program Files (x86)\MySQL\MySQL Server 6.0\my.ini" MySQL
10:34:59 a. m. [mysql] Expected Path: c:\xampp\mysql\bin\mysqld.exe --defaults-file=c:\xampp\mysql\bin\my.ini mysql
10:34:59 a. m. [main] Starting Check-Timer
And the MySQL error log
2015-11-10 15:26:56 10fc InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-11-10 15:26:56 4348 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2015-11-10 15:26:56 4348 [Note] InnoDB: The InnoDB memory heap is disabled
2015-11-10 15:26:56 4348 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-11-10 15:26:56 4348 [Note] InnoDB: Memory barrier is not used
2015-11-10 15:26:56 4348 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-11-10 15:26:56 4348 [Note] InnoDB: Not using CPU crc32 instructions
2015-11-10 15:26:56 4348 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-11-10 15:26:56 4348 [Note] InnoDB: Completed initialization of buffer pool
2015-11-10 15:26:56 4348 [Note] InnoDB: Highest supported file format is Barracuda.
2015-11-10 15:26:57 4348 [Note] InnoDB: 128 rollback segment(s) are active.
2015-11-10 15:26:57 4348 [Note] InnoDB: Waiting for purge to start
2015-11-10 15:26:57 4348 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.26-74.0 started; log sequence number 1835027
2015-11-10 15:26:57 6140 [Note] InnoDB: Dumping buffer pool(s) not yet started
2015-11-10 15:26:57 4348 [Note] Plugin 'FEEDBACK' is disabled.
2015-11-10 15:26:57 4348 [Note] Server socket created on IP: '::'.
2015-11-10 15:26:57 4348 [Note] Event Scheduler: Loaded 0 events
2015-11-10 15:26:57 4348 [Note] C:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.8-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
2015-11-10 15:27:11 5152 [Note] C:\xampp\mysql\bin\mysqld.exe: Normal shutdown
2015-11-10 15:27:11 5152 [Note] Event Scheduler: Purging the queue. 0 events
2015-11-10 15:27:11 5732 [Note] InnoDB: FTS optimize thread exiting.
2015-11-10 15:27:11 5152 [Note] InnoDB: Starting shutdown...
2015-11-10 15:27:13 5152 [Note] InnoDB: Shutdown completed; log sequence number 1835037
2015-11-10 15:27:13 5152 [Note] C:\xampp\mysql\bin\mysqld.exe: Shutdown complete
2017-10-03 11:25:56 2118 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2017-10-03 11:25:56 8472 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
2017-10-03 11:25:56 8472 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-10-03 11:25:56 8472 [Note] InnoDB: The InnoDB memory heap is disabled
2017-10-03 11:25:56 8472 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-10-03 11:25:56 8472 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-10-03 11:25:56 8472 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-10-03 11:25:56 8472 [Note] InnoDB: Using generic crc32 instructions
2017-10-03 11:25:56 8472 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-10-03 11:25:56 8472 [Note] InnoDB: Completed initialization of buffer pool
2017-10-03 11:25:57 8472 [Note] InnoDB: Highest supported file format is Barracuda.
2017-10-03 11:26:00 8472 [Note] InnoDB: 128 rollback segment(s) are active.
2017-10-03 11:26:00 8472 [Note] InnoDB: Waiting for purge to start
2017-10-03 11:26:00 8472 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.34-79.1 started; log sequence number 1835037
2017-10-03 11:26:00 8028 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-10-03 11:26:00 8472 [Note] Plugin 'FEEDBACK' is disabled.
2017-10-03 11:26:01 8472 [Note] Server socket created on IP: '::'.
2017-10-03 11:26:03 8472 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.21-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
2017-10-03 13:51:17 574 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2017-10-03 13:51:17 1396 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
2017-10-03 13:51:17 1396 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-10-03 13:51:17 1396 [Note] InnoDB: The InnoDB memory heap is disabled
2017-10-03 13:51:17 1396 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-10-03 13:51:17 1396 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-10-03 13:51:17 1396 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-10-03 13:51:17 1396 [Note] InnoDB: Using generic crc32 instructions
2017-10-03 13:51:17 1396 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-10-03 13:51:17 1396 [Note] InnoDB: Completed initialization of buffer pool
2017-10-03 13:51:17 1396 [Note] InnoDB: Highest supported file format is Barracuda.
2017-10-03 13:51:17 1396 [Note] InnoDB: The log sequence numbers 1835037 and 1835037 in ibdata files do not match the log sequence number 1836205 in the ib_logfiles!
2017-10-03 13:51:17 1396 [Note] InnoDB: Database was not shutdown normally!
2017-10-03 13:51:17 1396 [Note] InnoDB: Starting crash recovery.
2017-10-03 13:51:17 1396 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-10-03 13:51:18 1396 [Note] InnoDB: Restoring possible half-written data pages
2017-10-03 13:51:18 1396 [Note] InnoDB: from the doublewrite buffer...
2017-10-03 13:51:20 1396 [Note] InnoDB: 128 rollback segment(s) are active.
2017-10-03 13:51:20 1396 [Note] InnoDB: Waiting for purge to start
2017-10-03 13:51:20 1396 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.34-79.1 started; log sequence number 1836205
2017-10-03 13:51:20 236 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-10-03 13:51:20 1396 [Note] Plugin 'FEEDBACK' is disabled.
2017-10-03 13:51:20 1396 [Note] Server socket created on IP: '::'.
2017-10-03 13:51:21 1396 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.21-MariaDB' socket: '' port: 3306 mariadb.org binary distribution

WAMP server 3.0.6 error "The service 'wampmysqld64' is NOT started"

Wamp server icon is not turned to green. Apache server is started successfully but my wampmysqld64 is not started. Below is the Mysql error log.
2016-11-16T18:56:08.140148Z 0 [Warning] InnoDB: New log files created, LSN=45790
2016-11-16T18:56:09.740961Z 0 [Warning] InnoDB: Creating foreign key constraint system tables.
wampmysqld64: Table 'mysql.plugin' doesn't exist
2016-11-16T18:56:10.232737Z 0 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
2016-11-16T18:56:10.354885Z 0 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: 56a59712-ac2e-11e6-99ca-208984e4e31f.
2016-11-16T18:56:10.436871Z 0 [Warning] Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.
2016-11-16T18:56:10.446880Z 0 [Warning] Failed to open optimizer cost constant tables
2016-11-16T18:56:10.448881Z 0 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist
2016-11-16T18:56:10.449881Z 0 [ERROR] Aborting

Lighttpd error sockets disabled, out-of-fds

I have used lighttpd for a long, since its very fast for busy webapplications ins fast-cgi(PHP)
2 or 3 months ago sometimes I got this erro:
2015-07-06 17:58:55: (server.c.1398) [note] sockets enabled again
2015-07-06 17:58:55: (server.c.1446) [note] sockets disabled, out-of-fds
2015-07-06 17:58:59: (server.c.1398) [note] sockets enabled again
2015-07-06 17:58:59: (server.c.1446) [note] sockets disabled, out-of-fds
2015-07-06 17:59:05: (server.c.1398) [note] sockets enabled again
2015-07-06 17:59:05: (server.c.1446) [note] sockets disabled, out-of-fds
2015-07-06 17:59:10: (server.c.1398) [note] sockets enabled again
2015-07-06 17:59:10: (server.c.1446) [note] sockets disabled, out-of-fds
2015-07-06 17:59:14: (server.c.1398) [note] sockets enabled again
2015-07-06 17:59:14: (server.c.1446) [note] sockets disabled, out-of-fds
2015-07-06 17:59:18: (server.c.1398) [note] sockets enabled again
2015-07-06 17:59:18: (server.c.1446) [note] sockets disabled, out-of-fds
2015-07-06 17:59:22: (server.c.1398) [note] sockets enabled again
2015-07-06 17:59:22: (server.c.1446) [note] sockets disabled, out-of-fds
2015-07-06 17:59:26: (server.c.1398) [note] sockets enabled again
2015-07-06 17:59:26: (server.c.1446) [note] sockets disabled, out-of-fds
I was using version 1.4.29 and now after upgrade to 1.4.35 the problem persists. Since then I've been looking very different solutions and found nothing that could help me.
Some relevant config info:
h2. lighttpd.conf
server.username = "lighttpd"
server.groupname = "lighttpd"
server.event-handler = "linux-sysepoll"
server.max-fds = 4096 #same as ulimit -n
server.max-connections = 2048
server.stat-cache-engine = "simple"
server.max-keep-alive-idle = 5
server.max-keep-alive-requests = 4
server.max-read-idle = 30
server.max-write-idle = 360
h2. fast-cgi.conf
server.modules += ( "mod_fastcgi" )
fastcgi.server = ( ".php" =>
( "php-local" =>
(
"socket" => "/tmp/php-fastcgi-1.socket",
# "socket" => "/tmp/php-fastcgi-1.socket"+var.PID,
"bin-path" => "/usr/bin/php-cgi",
"max-procs" => 30,
"broken-scriptfilename" => "enable",
)
),
( "php-tcp" =>
(
"host" => "127.0.0.1",
"port" => 9999,
"check-local" => "disable",
"broken-scriptfilename" => "enable",
)
),
( "php-tcp2" =>
(
"host" => "127.0.0.1",
"port" => 9998,
"check-local" => "disable",
"broken-scriptfilename" => "enable",
)
),
( "php-num-procs" =>
(
"socket" => "/tmp/php-fastcgi-2.socket",
"bin-path" => "/usr/bin/php-cgi",
"max-procs" => 30,
"bin-environment" => (
"PHP_FCGI_CHILDREN" => "30",
"PHP_FCGI_MAX_REQUESTS" => "2048",
),
"broken-scriptfilename" => "enable",
)
),
)
This server is dedicated to that application.
Is running at more than four years with at least 2 lighttpd php applications with large volumes of access, the record was in 2013 with 14,000 unique visits and 85,000 page views, then this record had no problems with the limit.
Today keep the average 8,000 visitors and 44,000 page views per day.
:
What's wrong?
lighttpd 1.4 keeps an internal count of (some of the) file descriptors it has opened. lighttpd 1.4 disables the server sockets when its internal count (cur_fds + want_fds -- line 1408 of src/server.c) reaches 90% of server.max-fds from lighttpd.conf
It is possible (unsubstantiated) that the internal count does not match the actual number of file descriptors in use.
If this happens again, would you check how many fds are actually used by the lighttpd server process? If the lighttpd server process has pid 1234, then check the number of open fds of a process on Linux with
ls -1 /proc/1234/fd/ | wc -l
If the result is much less than 90% of server.max-fds (which you have set to 4096), then that would suggest a bug in lighttpd internal fd count. You can go to http://redmine.lighttpd.net/projects/lighttpd/issues and Register for an account. Then, you'll be able to submit a bug report.
Again, if this is the problem, you might also look at your application to see how frequently it is encountering fatal errors, dying, and being restarted.

Wampserver error to initialize

I am trying to start wampserver and pulls me error. Try changing the port 80 by 8080 but did not work. Also change the port skype.
Anyone know what the problem is?
Error Log
2014-12-12 09:25:39 4460 [Note] Plugin 'FEDERATED' is disabled.
2014-12-12 09:25:40 4460 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-12-12 09:25:40 4460 [Note] InnoDB: The InnoDB memory heap is disabled
2014-12-12 09:25:40 4460 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-12-12 09:25:40 4460 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-12-12 09:25:40 4460 [Note] InnoDB: Not using CPU crc32 instructions
2014-12-12 09:25:40 4460 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-12-12 09:25:40 4460 [Note] InnoDB: Completed initialization of buffer pool
2014-12-12 09:25:40 4460 [Note] InnoDB: Highest supported file format is Barracuda.
2014-12-12 09:25:48 4460 [Note] InnoDB: 128 rollback segment(s) are active.
2014-12-12 09:25:49 4460 [Note] InnoDB: Waiting for purge to start
2014-12-12 09:25:49 4460 [Note] InnoDB: 5.6.17 started; log sequence number 1626213
2014-12-12 09:25:49 4460 [Note] Server hostname (bind-address): '*'; port: 3306
2014-12-12 09:25:49 4460 [Note] IPv6 is available.
2014-12-12 09:25:49 4460 [Note] - '::' resolves to '::';
2014-12-12 09:25:49 4460 [Note] Server socket created on IP: '::'.
2014-12-12 09:25:49 4460 [Note] Event Scheduler: Loaded 0 events
2014-12-12 09:25:49 4460 [Note] wampmysqld: ready for connections.
Version: '5.6.17' socket: '' port: 3306 MySQL Community Server (GPL)
This is the last event in error log of apache:
[Tue Dec 09 06:46:54.906225 2014] [mpm_winnt:notice] [pid 5160:tid 292] AH00422: Parent: Received shutdown signal -- Shutting down the server.
[Tue Dec 09 06:46:58.906453 2014] [mpm_winnt:notice] [pid 4620:tid 312] AH00364: Child: All worker threads have exited.
[Tue Dec 09 06:47:00.838564 2014] [mpm_winnt:notice] [pid 5160:tid 292] AH00430: Parent: Child process 4620 exited successfully.
But today (15/12) nothing

Resources