[caasp-beta] read only fs on caasp kubernetes nodes

Flavio Castelli fcastelli at suse.com
Fri Feb 23 00:57:11 MST 2018 

Which release of caasp are you currently using?

Thanks
Flavio

On 02/22/2018 06:55 PM, Le Bihan Stéphane (AMUNDI-ITS)  wrote:
> Hello,
> 
> Strange. I never have problem with Velum deployement. After yes ....
> 
> I the same log for MariaDB containers, but Velum works.
> 
> Creating MySQL privilege database...
> Installing MariaDB/MySQL system tables in '/var/lib/mysql' ...
> 180222 16:33:50 [Note] /usr/sbin/mysqld (mysqld 10.0.31-MariaDB) starting as process 51 ...
> OK
> Filling help tables...
> 180222 16:33:53 [Note] /usr/sbin/mysqld (mysqld 10.0.31-MariaDB) starting as process 78 ...
> OK
> 
> PLEASE REMEMBER TO SET A PASSWORD FOR THE MariaDB root USER !
> To do so, start the server, then issue the following commands:
> 
> '/usr/bin/mysqladmin' -u root password 'new-password'
> '/usr/bin/mysqladmin' -u root -h velum-private-127.0.0.1 password 'new-password'
> 
> Alternatively you can run:
> '/usr/bin/mysql_secure_installation'
> 
> which will also give you the option of removing the test
> databases and anonymous user created by default.  This is
> strongly recommended for production servers.
> 
> See the MariaDB Knowledgebase at http://mariadb.com/kb or the
> MySQL manual for more instructions.
> 
> You can start the MariaDB daemon with:
> rcmysql start
> 
> You can test the MariaDB daemon with mariadb-test package
> 
> Please report any problems at http://mariadb.org/jira
> 
> The latest information about MariaDB is available at http://mariadb.org/.
> You can find additional information about the MySQL part at:
> http://dev.mysql.com
> Consider joining MariaDB's strong and vibrant community:
> https://mariadb.org/get-involved/
> 
> ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2 "No such file or directory")
> ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2 "No such file or directory")
> MySQL init process in progress...
> 180222 16:33:56 [Note] /usr/sbin/mysqld (mysqld 10.0.31-MariaDB) starting as process 122 ...
> Setting root password...
> Password updated successfully!
> Reloading privilege tables..
>  ... Success!
> Removing anonymous users...
>  ... Success!
> Removing remote root access...
>  ... Success!
> Removing test database...
>  - Dropping test database...
>  ... Success!
>  - Removing privileges on test database...
>  ... Success!
> Reloading privileges...
>  ... Success!
> /usr/local/bin/entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
> 
> 
> MySQL init process done. Ready for start up.
> 
> Cleaning up...
> 180222 16:33:58 [Note] /usr/sbin/mysqld (mysqld 10.0.31-MariaDB) starting as process 1 ...
> 
> Regards,
> 
> Stéphane Le Bihan
> SDE/DSI/IPR/SSD/UNX
> 90, Boulevard Pasteur - 75015 Paris
> Web: www.amundi.com
> Tel: +33 1 76 32 32 08
> Tel Unix Team: +33 1 76 32 02 30
> @: stephane.lebihan at amundi.com
> @: sits.unix at amundi.com
> 
> Visit us on: 
> 
>         
> 
> 
> -----Message d'origine-----
> De : caasp-beta-bounces at lists.suse.com [mailto:caasp-beta-bounces at lists.suse.com] De la part de Simeon Bobylev
> Envoyé : jeudi 22 février 2018 15:37
> À : caasp-beta at lists.suse.com
> Objet : Re: [caasp-beta] read only fs on caasp kubernetes nodes
> 
> Thank you Thorsten.
> 
> I have another weird issue when trying de deploy CaaSP Admin node :
> 
> The machine has booted after the initial installation but Velum is still not inaccessible 20min later. I rebooted the node but same problem.
> By checking log files, it seems that some services are waiting for mariadb :
> 
> ==>
> /var/log/containers/velum-public-127.0.0.1_default_velum-dashboard-7c256d89831570117d416a2761ace54ebc682afd44c1c66270f4acd2158aa616.log
> <==
> {"log":"Waiting for mariadb to be ready in 5 seconds\n","stream":"stdout","time":"2018-02-22T14:28:15.93480394Z"}
> 
> ==>
> /var/log/containers/velum-public-127.0.0.1_default_salt-master-8f4b5411619cea0b94257ec7b299f16ca00f681a609d6217060b1924f9d8a972.log
> <==
> {"log":"[ERROR   ] Could not store events - returner 'mysql.event_return' 
> raised exception: MySQL returner could not connect to database: (1045, \"Access denied for user 'salt'@'localhost' (using password: 
> YES)\")\n","stream":"stderr","time":"2018-02-22T14:29:51.824838923Z"}
> 
> And if I look into mariadb container logs, it seems mariadb is starting... 
> but never starts.
> 
> c002-caasadmin-01:~ # docker logs -f
> k8s_velum-mariadb_velum-private-127.0.0.1_default_bf640ab62f9d8d01fa0c2f7e66744787_1
> ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2 "No such file or directory") ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2 "No such file or directory") MySQL init process in progress...
> 180222 14:25:42 [Note] /usr/sbin/mysqld (mysqld 10.0.31-MariaDB) starting as process 40 ...
> ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using
> password: NO)
> Setting root password...
> Root password already set, nothing to do here
> 
> Removing anonymous users...
>  ... Success!
> Removing remote root access...
>  ... Success!
> Removing test database...
>  - Dropping test database...
>  ... Success!
>  - Removing privileges on test database...
>  ... Success!
> Reloading privileges...
>  ... Success!
> /usr/local/bin/entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
> 
> 
> MySQL init process done. Ready for start up.
> 
> Cleaning up...
> 180222 14:25:45 [Note] /usr/sbin/mysqld (mysqld 10.0.31-MariaDB) starting as process 1 ...
> 
> 
> Do you know any workaround to fix that ?
> 
> 
> Siméon Bobylev ¦ System Engineer ¦ Cortex IT SA ¦ Route de l'Ile aux Bois 1A 
> ¦ 1870 Monthey ¦ Switzerland
> Direct: +41 24 524 1204 ¦ Main: +41 24 524 1200 ¦ Email: 
> simeon.bobylev at cortex-it.ch <mailto:simeon.bobylev at cortex-it.ch>
> 
> http://www.cortex-it.ch/ <http://www.cortex-it.ch/>  ¦ A WIRD Group Company
> 
> -----Original Message-----
> From: caasp-beta-bounces at lists.suse.com 
> [mailto:caasp-beta-bounces at lists.suse.com] On Behalf Of Thorsten Kukuk
> Sent: mercredi, 21 février 2018 14:28
> To: caasp-beta at lists.suse.com
> Subject: Re: [caasp-beta] read only fs on caasp kubernetes nodes
> 
> On Wed, Feb 21, Simeon Bobylev wrote:
> 
>> Hi all,
>>
>>
>>
>> Is there a specific reason that /dev/sda2 is mounted in read only into
>> / on CaaSP Kubernetes nodes ?
> 
> Yes, that's part of the concept and needed for transactional updates.
> 
>> c002-caasnode-01:~ # mkdir /var/lib/controller
>>
>> mkdir: cannot create directory ‘/var/lib/controller’: Read-only
>> file system
> 
> # transactional-update shell
> #> mksubvolume /var/lib/controller
> #> exit
> # systemctl reboot
> 
> 
>   Thorsten
> 
> --
> Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP SUSE 
> LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
> GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG 
> Nuernberg) _______________________________________________
> caasp-beta mailing list
> caasp-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/caasp-beta
> _______________________________________________
> caasp-beta mailing list
> caasp-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/caasp-beta
> _______________________________________________
> caasp-beta mailing list
> caasp-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/caasp-beta
>

More information about the caasp-beta mailing list