RE: MySQL: Readiness probe failed

[Den Cowboy]

imestamp server option (see 
documentation for more details).
2016-06-21 16:20:02 0 [Note] /opt/rh/rh-mysql56/root/usr/libexec/mysqld (mysqld 
5.6.26) starting as process 1 ...
2016-06-21 16:20:02 1 [Note] Plugin 'FEDERATED' is disabled.
2016-06-21 16:20:02 6c4828a2d840 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.
2016-06-21 16:20:02 1 [Note] InnoDB: Using atomics to ref count buffer pool 
pages
2016-06-21 16:20:02 1 [Note] InnoDB: The InnoDB memory heap is disabled
2016-06-21 16:20:02 1 [Note] InnoDB: Mutexes and rw_locks use GCC atomic 
builtins
2016-06-21 16:20:02 1 [Note] InnoDB: Memory barrier is not used
2016-06-21 16:20:02 1 [Note] InnoDB: Compressed tables use zlib 1.2.7
2016-06-21 16:20:02 1 [Note] InnoDB: Using Linux native AIO
2016-06-21 16:20:02 1 [Note] InnoDB: Using CPU crc32 instructions
2016-06-21 16:20:02 1 [Note] InnoDB: Initializing buffer pool, size = 32.0M
2016-06-21 16:20:02 1 [Note] InnoDB: Completed initialization of buffer pool
2016-06-21 16:20:02 1 [Note] InnoDB: Highest supported file format is Barracuda.
2016-06-21 16:20:02 1 [Note] InnoDB: 128 rollback segment(s) are active.
2016-06-21 16:20:02 1 [Note] InnoDB: Waiting for purge to start
2016-06-21 16:20:02 1 [Note] InnoDB: 5.6.26 started; log sequence number 1625997
2016-06-21 16:20:02 1 [Note] RSA private key file not found: 
/var/lib/mysql/data//private_key.pem. Some authentication plugins will not work.
2016-06-21 16:20:02 1 [Note] RSA public key file not found: 
/var/lib/mysql/data//public_key.pem. Some authentication plugins will not work.
2016-06-21 16:20:02 1 [Note] Server hostname (bind-address): '*'; port: 3306
2016-06-21 16:20:02 1 [Note] IPv6 is available.
2016-06-21 16:20:02 1 [Note]   - '::' resolves to '::';
2016-06-21 16:20:02 1 [Note] Server socket created on IP: '::'.
2016-06-21 16:20:02 1 [Warning] 'user' entry 'root@mysql-1-irei5' ignored in 
--skip-name-resolve mode.
2016-06-21 16:20:02 1 [Warning] 'user' entry '@mysql-1-irei5' ignored in 
--skip-name-resolve mode.
2016-06-21 16:20:02 1 [Warning] 'proxies_priv' entry '@ root@mysql-1-irei5' 
ignored in --skip-name-resolve mode.
2016-06-21 16:20:02 1 [Note] Event Scheduler: Loaded 0 events
2016-06-21 16:20:02 1 [Note] /opt/rh/rh-mysql56/root/usr/libexec/mysqld: ready 
for connections.
Version: '5.6.26'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL 
Community Server (GPL)

From: bpar...@redhat.com
Date: Tue, 21 Jun 2016 11:20:22 -0400
Subject: Re: MySQL: Readiness probe failed
To: dencow...@hotmail.com
CC: users@lists.openshift.redhat.com

can you provide the logs from the postgres pod?


On Tue, Jun 21, 2016 at 10:44 AM, Den Cowboy <dencow...@hotmail.com> wrote:



I'm using the MySQL template and started it with the right environment variables
The MySQL is running fine but I got this error and I'm not able to access my 
mysql on its service name:

mysql -u myuser -h mysql -p
password:xxx


Readiness probe failed: sh: cannot set terminal process group (-1): 
Inappropriate ioctl for device
sh: no job control in this shell
ERROR 2003 (HY000): Can't connect to MySQL server on '127.0.0.1' (111)

  

___

users mailing list

users@lists.openshift.redhat.com

http://lists.openshift.redhat.com/openshiftmm/listinfo/users




-- 
Ben Parees | OpenShift


  ___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: MySQL: Readiness probe failed

[Philippe Lafoucrière]

Have you tried to raise initialDelaySeconds ?
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: MySQL: Readiness probe failed

[Martin Nagy]

Ah, ignore that, I didn't realize the warnings about ioctl are irrelevant.

On Tue, Jun 21, 2016 at 4:56 PM, Martin Nagy  wrote:
> Are you referring to templates in origin/examples/db-templates?
> Can you edit the template and remove the '-i' passed to /bin/sh
> and see if it helps?
>
> On Tue, Jun 21, 2016 at 4:44 PM, Den Cowboy  wrote:
>> I'm using the MySQL template and started it with the right environment
>> variables
>> The MySQL is running fine but I got this error and I'm not able to access my
>> mysql on its service name:
>>
>> mysql -u myuser -h mysql -p
>> password:xxx
>>
>>
>> Readiness probe failed: sh: cannot set terminal process group (-1):
>> Inappropriate ioctl for device sh: no job control in this shell ERROR 2003
>> (HY000): Can't connect to MySQL server on '127.0.0.1' (111)
>>
>>
>> ___
>> users mailing list
>> users@lists.openshift.redhat.com
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: MySQL: Readiness probe failed

[Martin Nagy]

Are you referring to templates in origin/examples/db-templates?
Can you edit the template and remove the '-i' passed to /bin/sh
and see if it helps?

On Tue, Jun 21, 2016 at 4:44 PM, Den Cowboy  wrote:
> I'm using the MySQL template and started it with the right environment
> variables
> The MySQL is running fine but I got this error and I'm not able to access my
> mysql on its service name:
>
> mysql -u myuser -h mysql -p
> password:xxx
>
>
> Readiness probe failed: sh: cannot set terminal process group (-1):
> Inappropriate ioctl for device sh: no job control in this shell ERROR 2003
> (HY000): Can't connect to MySQL server on '127.0.0.1' (111)
>
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users