Hi, Seems like [1] happens again: "Login error oVirt_Wiki uses cookies to log in users. You have cookies disabled. Please enable them and try again." Could you please handle it ? [1] http://lists.ovirt.org/pipermail/infra/2012-November/001365.html Thanks, Moti
--+9faIjRurCDpBc7U Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 09/01, Moti Asayag wrote:
Hi, =20 Seems like [1] happens again: =20 "Login error oVirt_Wiki uses cookies to log in users. You have cookies disabled. Pleas= e enable them and try again." =20 Could you please handle it ?=20
Same issue as last time, I see that the database is occupying most of the space, I see 2 possible solutions (can be applied together): * Shrink database: - Regenerating the ibdata: This requires dumping, deleting and recreating the database to regenerate the ibdata file. We can also separate that file per table during the process. - Cleaning up temporary and unnecessary data from the database: This requires knowledge of the internal structure of the database of the wiki, anyone has knowledge on that? * Expand space: - Not sure how to proceed here, but we can ask for a bigger gear to hold the wiki, we are using 8GB now. In any case, bkp, misc, any ideas?
=20 [1] http://lists.ovirt.org/pipermail/infra/2012-November/001365.html =20 Thanks, Moti _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
--=20 David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro@redhat.com Web: www.redhat.com RHT Global #: 82-62605 --+9faIjRurCDpBc7U Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJUBD+pAAoJEEBxx+HSYmnDXNEH/2YDVm2AZemkEjrmROvLiVM5 7LerdDC3CU2K9/McTsApFwrzre9VE0JJD1LEaoG5f9ZCGK5W3m9N6xAdf64Up7QX gcGmqGzD05B46aJHePNMEyqxrtzwIR6YLQ2xdbPux35OIedRZ1jHk+Mh4JkD7CQC xhrq4Wl2IzheaR10xkBqkHDV89GyEDBJJMzbODclSVq0D2sBZQEJx9d+UZgTFOzI YIB4BMMI0+F2xkO2I+Tr+0hgwXqy0tzbK3eFaWPTvwc/gS/3ZUnhsxF2AlS6mOwt z9suiVdBmDOEYwkmlxSHBsYOBVsXcEPfn3LsAGLGxrlZzU560aZb0wIoN42lK98= =lJAt -----END PGP SIGNATURE----- --+9faIjRurCDpBc7U--
--=-phFeFMusshFzx+Jk/D4z Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Le lundi 01 septembre 2014 =C3=A0 11:43 +0200, David Caro a =C3=A9crit :
Hi, =20 Seems like [1] happens again: =20 "Login error oVirt_Wiki uses cookies to log in users. You have cookies disabled. Ple= ase enable them and try again." =20 Could you please handle it ?=20 =20 Same issue as last time, I see that the database is occupying most of
On 09/01, Moti Asayag wrote: the space, I see 2 possible solutions (can be applied together): =20 * Shrink database: - Regenerating the ibdata: This requires dumping, deleting and recreating the database to regenerate the ibdata file. We can also separate that file per tabl= e during the process. - Cleaning up temporary and unnecessary data from the database: This requires knowledge of the internal structure of the database of the wiki, anyone has knowledge on that? * Expand space: - Not sure how to proceed here, but we can ask for a bigger gear to hold the wiki, we are using 8GB now. =20 In any case, bkp, misc, any ideas?
I would rather migrate the wiki out of openshift when we can have a server for that in phx2. We will no longer be constrained by hosting, and we will be able to administer it in a more conventional way. Openshift is made to deploy software that you deploy and write yourself, not really to host stuff made by others who are not made for this. We shoehorn mediawiki on it, and we start to see the limit of the approach :/ Migrating to a set of 2 gears would only work for scaled gears, which mean reinstalling the whole setup almost from scratch. So I would prefer, if we need to do that, to move to a regular VM ( where then we can enable cache, varnish, etc to make things faster ) --=20 Michael Scherer Open Source and Standards, Sysadmin --=-phFeFMusshFzx+Jk/D4z Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAABAgAGBQJUBGZ1AAoJEE89Wa+PrSK9b0cQAIbfU2RwTlakLXrYFuEB+hFv tdnco2foJiToatRIp+6lrekHulEMLew30R6Rwm68/E660pQhUCYqyD0edKKPe2ap W/qLhdhtq3ICU2PGg/RI/pjoRAwTFz+XkUYBoJOwDRVeZ4O8bJck08/1nWUWY4aq jcARXMO4bxWdu+8WQTzFt2I7NmCndOrlaKeEtTf7CJkk8dmrZsEADvs+l9lPk8Az qNskiZo7BWxqTRsHSrR+1N7mVSCTYEopbsgFA4pW3/bbJ+zoyPa42E2RluPBRgE/ mAlrdvFb7aYdPttQnhvpfp4abovGZnr49kJFX0/7ziIrjLSxFiNqTzkYpWm+TWdQ 7kh6lrei7KRHjXcW5Sgco+ONiQf13leN+Be8Jk863ew25N/zQwC7NykJO0YCXbJ0 6kf1SDgqo0P24C/MFMOnLX7HBz8/9dW1NeEitKNtLvCnPMS7Oae7PU7h+ZIrGmdz jpOtKlRFOl015gawPO9rY2eyeqlGMZdJ8syib01Vi0flAVU8U4HHT3aSa2CZulEo gHTsSLxBu8KzjEcD+TKRuf4Uciq/WrnPy/px5ZDz4sICx/BhrNjJZXMR+9cjiY7U De5d71lYi9Yaz22MqJP2YGRJtynbIeCJ1PIzM6n6xywVEdqkjPBgJw3F+Q6n2jc+ OMc4hLoC9hhbeFZs1AiJ =LvPw -----END PGP SIGNATURE----- --=-phFeFMusshFzx+Jk/D4z--
--=-VzTYbKzaZghjVDlqxZsL Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Le lundi 01 septembre 2014 =C3=A0 11:43 +0200, David Caro a =C3=A9crit :
Hi, =20 Seems like [1] happens again: =20 "Login error oVirt_Wiki uses cookies to log in users. You have cookies disabled. Ple= ase enable them and try again." =20 Could you please handle it ?=20 =20 Same issue as last time, I see that the database is occupying most of
On 09/01, Moti Asayag wrote: the space, I see 2 possible solutions (can be applied together): =20 * Shrink database: - Regenerating the ibdata: This requires dumping, deleting and recreating the database to regenerate the ibdata file. We can also separate that file per tabl= e during the process. - Cleaning up temporary and unnecessary data from the database: This requires knowledge of the internal structure of the database of the wiki, anyone has knowledge on that? * Expand space: - Not sure how to proceed here, but we can ask for a bigger gear to hold the wiki, we are using 8GB now. =20 In any case, bkp, misc, any ideas?
in the meantime, I removed logs, and copied them offline, this give us 400 M. --=20 Michael Scherer Open Source and Standards, Sysadmin --=-VzTYbKzaZghjVDlqxZsL Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAABAgAGBQJUBe2cAAoJEE89Wa+PrSK9eOYQAKfyqhnbPhnzi749xCk4NOi4 IjRKgtU1IjcsUZWaC1DFk1vhONzQUkXiw8orDpx830y8n/YX6AjXnQ9CM5oUN40n iympGVeN0ZDEKW59NEy7UvM7EMrOOYYi1Pv6fkpo4NHBgwMfY1BuRqQQIEW/IGaf 3DwquqqE8R4+LH3A8cmdZtF70nDq4n7nHcJI6UD92y0YbRIGJJt4lV+/ZHai4V7+ qMPs85Qf+2orLHdBuIO/MBIre08jcr1ldYWWLuz+hx2Ey99wywygatz29iBtTurI wURBhDRbmigRuYebj8/XHOL2zTb8jambi8bRMwW4J+wl5qnMWgCaAwd9WJt+l4wJ T0tUTNuW7zT9GwssVtJvfDZlzmQ9mxQbNew7aMPer3CiQ8RGAPC/MTBLLerC/Zy0 vXngpS5yWvnR4Af9wIxlm/EFxac1qomWufmh3PXjbI1myTbtgycSanE8wSUuHbu7 yZnlUNDQFppblM9/u5Dcs0pEXJeS3cAdXFBOKnTGnpO9O7zdsut9me4fypS7DL4i xD3O0cN+rUsrePaAf8VEFVfBEqBnD5thCgjfO6le6w/rE9IljoWRWfilyiTR66a0 rXBrND9YsFQdDjXb18r+pLgqpIENLQFCBZ9hNsTWpfrENUsMRqRSW6e6AoOUmdRG YJjgIGkqe8fr+OtWTdlx =/R89 -----END PGP SIGNATURE----- --=-VzTYbKzaZghjVDlqxZsL--
--=-8lxvgLz9XEYCHbEsCTtj Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Le mardi 02 septembre 2014 =C3=A0 18:17 +0200, Michael Scherer a =C3=A9crit= :
Le lundi 01 septembre 2014 =C3=A0 11:43 +0200, David Caro a =C3=A9crit :
Hi, =20 Seems like [1] happens again: =20 "Login error oVirt_Wiki uses cookies to log in users. You have cookies disabled. P= lease enable them and try again." =20 Could you please handle it ?=20 =20 Same issue as last time, I see that the database is occupying most of
On 09/01, Moti Asayag wrote: the space, I see 2 possible solutions (can be applied together): =20 * Shrink database: - Regenerating the ibdata: This requires dumping, deleting and recreating the database to regenerate the ibdata file. We can also separate that file per ta= ble during the process. - Cleaning up temporary and unnecessary data from the database: This requires knowledge of the internal structure of the database of the wiki, anyone has knowledge on that? * Expand space: - Not sure how to proceed here, but we can ask for a bigger gear to hold the wiki, we are using 8GB now. =20 In any case, bkp, misc, any ideas? =20 in the meantime, I removed logs, and copied them offline, this give us 400 M.
I would love to say that it took me 3h to restart the wiki, but the reality is more "someone came and asked me a urgent question" and I forgot to restart the wiki after the interruption (and went back home) :/ So now, it should be working fine.=20 I still recommend to migrate it out of openshift since this would make the maintenance a bit easier, but we need to have the lab ready. --=20 Michael Scherer Open Source and Standards, Sysadmin --=-8lxvgLz9XEYCHbEsCTtj Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAABAgAGBQJUBhUKAAoJEE89Wa+PrSK9y+8QAKYd4m/aMfkKyO9Xr8GexoRe gx8LVHTKZi++Ls9SRK+6iVjAHl8VuF2yHeeet3l7inG7OWN+dpjrDU45ByPMOi9x 4fIKW1A5lV4/Nbw9mjXMWbAS/qcOnnhG6dIKz9TcSFb6zM9batmQRKoOv3z0k46K ekZa495gFeIsru8bFTnyUMZUPV2DyW0PyuqqcM6Cs3+nL0uk2PQ2jUspwAHSqExE devn3lrRD4XIm1qZx0fbSf+6JLKljEVMaM7fS9ivt4Uyp37UF+DffdA7ZJhBWKh+ 4rciIZ7U0DDZm9CPwVUDusggIKheUB5iMIve9V/ZF8O+2xb2QGW0APRmvd7q2udY 3CSwMYXiwjQjJKK+xupTy2cg1gpnWAFt5A9/1Kt7+HIOQRLdIQm/ufc5JJXel94n n3OBzO8CEnkv+X/g5qji/Y77V3dJgo3wKCbRNc2ljw7bjqfmZEd2WB4RCl1J7IZV AF5Tpc7DBviBGVPR0K4sEghpeF6gyA+144IBkkFwRrTAfuFy3fdgd1EBvwJ0xqSN m5PQZdAMcfHPowrLUrrZ5hsF81CkmV7lfvo61oyn4neFhInJIPLC1i2w3SkagYk6 mdX1kDojEmtATV6Kd9Y8OHD/1RJ4J0NJgdEtgCTSsbkuyO8ag2YwybrHWGfJV07n MYbnJA3T9VpSFsuL+AU2 =ZR69 -----END PGP SIGNATURE----- --=-8lxvgLz9XEYCHbEsCTtj--
participants (3)
-
David Caro -
Michael Scherer -
Moti Asayag