10:42 p.m.
For those who are interested in the full issue with the website and it's
background: http://osuosl.org/blog/mysql1-vip-post-mortem
Best Regards, Martin Owens
4:27 a.m.
On Sat, Aug 08, 2015 at 09:42:46AM -0400, Martin Owens wrote:
For those who are interested in the full issue with the website and
it's
background: http://osuosl.org/blog/mysql1-vip-post-mortem
Best Regards, Martin Owens
Should we implement some of our own additional contingency plans, or are
our existing processes already up to snuff?
I'm thinking like identifying a temporary web host that could serve as
an independent cold fall-over in a worst case scenario like this?
Bryce
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAABAgAGBQJVxgdWAAoJEOVbsiwf4qcgq44QAKIiQUpr68Y6Hra0UEWqwz+4
sJVsz4opnTfHFV1VkJg1q/PxrQCQ5PEiukt2pFkJjOW9uLqYyCqyEEt7xz17g2OG
BrP3DyauMXtBprGWOdPMFegDjPf75Cwn42cYUy/FJBoOOy/siKZPTgiZUALnZUeP
precfL6g3qb/RMHYRGTsdJ//CBoFwoJELe/LclS64icnr0zLxG2peVRPz6NkJOvF
Hrkb4vcD69Nr8gJCRpwLlnbM5eYDsPp8ENw/O+GHCKUfW9njDNg8nRSvFIKEgFhP
+vREhJ1uK1cls9QY6flF44YSsPVWovH4KpsFAsCJ8OeVZlhQThE2n47o/umoZQjS
XwzYmiRSULIBxRhVc7TibDa/jwqvweiS9sylfhzhVN2uOnVddsiQSjXs1NaCexfv
+HLHzS0juQWJQp0m8IUYrFLnxJOJ5ap7xoC+3YkP9DbBvyeX+zwbMB8yVDvH/Sq8
nly9Xr5btLYc2px9r8EFjF/HfqwaFX2b4q5i45BP08qElvSg34B6LRJBIZapX/5C
h6eQv8T49mfYJLC9/niK/TfKurIZ+j+NwXWFoK8E8dhGQeuSAMkupE1y16MkYZsk
PO08r2gB/lvbuXqSVUpbNcxCe5zSMchrtyfZ8lFx2Dezz8FxXsoBHMZIpbkeanHT
7bKhkr2a3wiALc14RkPf
=1GfK
-----END PGP SIGNATURE-----
------------------------------------------------------------------------------
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel(a)lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
5:08 a.m.
On Sun, 2015-08-09 at 12:27 -0700, Bryce Harrington wrote:
Should we implement some of our own additional contingency plans, or
are our existing processes already up to snuff?
We have a non-zero contingency, which you saw in action. It's an sqlite
db which is in read-only mode and it has issues up the wazzoo; the most
significant being the downloads being missing from that db.
I'm thinking we need to get a regular backup going, but recent attempts
to dump our database fail with the server killing the process (must be
some sort of load protection maybe)
Our staging site could/should operate as a proof for the backups.
I'm thinking like identifying a temporary web host that could
serve as
an independent cold fall-over in a worst case scenario like this?
Not sure bout web host; that's something beyond these issues with the
db. The web server was working well the whole time. It's just our cms
and other data is rather db dependent.
Martin,
6:05 a.m.
On Sun, Aug 09, 2015 at 04:08:55PM -0400, Martin Owens wrote:
On Sun, 2015-08-09 at 12:27 -0700, Bryce Harrington wrote:
> Should we implement some of our own additional contingency plans, or
> are our existing processes already up to snuff?
We have a non-zero contingency, which you saw in action. It's an sqlite
db which is in read-only mode and it has issues up the wazzoo; the most
significant being the downloads being missing from that db.
I'm thinking we need to get a regular backup going, but recent attempts
to dump our database fail with the server killing the process (must be
some sort of load protection maybe)
After the dust settles, if this remains an issue make sure to follow up
with OSUOSL about it. Not being able to make our own backup is
obviously a big roadblock for establishing contingency.
Our staging site could/should operate as a proof for the backups.
That's a good idea.
> I'm thinking like identifying a temporary web host that
could serve as
> an independent cold fall-over in a worst case scenario like this?
Not sure bout web host; that's something beyond these issues with the
db. The web server was working well the whole time. It's just our cms
and other data is rather db dependent.
It would be ironic (although hardly unrealistic) if they fix the
database up great and next time it's something else like the vm host,
that gets hosed. An ideal contingency would be completely independent
of OSUOSL (and probably best housed outside the PNW and maybe outside
the US.)
Bryce
Martin,
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAABAgAGBQJVx7NXAAoJEOVbsiwf4qcgE7YQAKERInHnBWq4iFx9vEufruAi
uS/t+m3P7qlKokNIapOVoPIOF/TMFgnFAzQuZerGjXx1Rk2UCtT5++fB1dE/jxgw
AoGTHBk4L9r/BL2ckP6JdaccfThvd5qtB68keQGf/iVUbFykhbZ7pLztWrkH0Nmv
wFGbBmw39Q2jyjk2On4R+vc3+/QqrPNfG2dkEft5XyvJCqQFq7iVq580s9+iZUB0
yZpxWuiSnbMOd/QYTgdHWXJcqAgdmOcEbWuJPAg10NT3P33m33FRmzXVqe0yUuue
fsjJ5oooBEW0QyaXMW9KgwO41Nv/YtYWONEhEEs1hBgeN5FTzPL27puDzW8Lzez4
8yOc0XdvhPig+VONOUtw/rxt8brmy5zSu4kKD+i1gGLnzwmF/QWSQ4EnVBURdfFO
QW0OCChHSsGznBnahqorMruQzJzmePgtCgTdUz2tim/dS9sw0X6yNgCv0CyyG27a
uwlzxk2ragldaBaVt/5/j+QCxX6HwWEpZ/MC0V37Tl3giK8kBdWHVahW2aKe9UHG
nypuokYH3hO84IgTLouPUjrOEWkUIavlPPDBIwi+qaMsZkec46tPySgLs1cc0RHP
NzWoSzG28bUG8PN1V2jZu8yqY3GeTSlbF7KT0KR0bSuzznxxQ+OCEUecW0zh2aK1
s1VRnBzfcQBKHKulJy+8
=Ydop
-----END PGP SIGNATURE-----
2789
days inactive
2790
days old
inkscape-devel@lists.inkscape.org
3 comments
2 participants
participants (2)
-
Bryce Harrington -
Martin Owens