Hi all
I'm chairing a panel about the Toolserver at wikimania. So far I'm on my own
(well, Mark might come along). Who will be there and would like to talk about
what the toolserver is, how it works, or what coll stuff we have?
I'd of course like to have some other admin with me, but "normal" users are
welcome too. Having perhaps four people on stage would be nice.
-- daniel
Hi!,
I recently got my toolserver account. Looking for a way to set my bots
(using pywikipedia framework) to run, I noticed many people using the
framework haven't set the correct access flags to their "login-data" dir
(inside your /home dir). This could lead to someone using those files to run
your bot accounts.Although only other toolserver users can see these files,
its still an issue . Please make at least that dir "not readable" for anyone
but "owner".
--Pyr0.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
there was an unscheduled outage at ~17:20 UTC for around 15 minutes, caused by
a kernel panic on the NFS server (hyacinth). the cause is currently unknown.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkpSNW0ACgkQIXd7fCuc5vIXJwCcC6X/KSoRQxbw7Hhx9Pg5IMVo
RGMAnixFovl7Sel53XoEQvvcTOw7dF/2
=fYOt
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
the new s2 server (daphne) is online, and should have caught up with
replication later today. however, it is using a new MySQL build (version
5.1.35), which contains a critical InnoDB bug causing server crashes when
innodb_locks_unsafe_for_binlog is enabled. since we need this option to
support long queries, we won't switch servers until a patch is available.
(this is a new bug, unrelated to the previous one.) i hope this will happen
later this week.
when we switch, user databases currently on the s2 server will _not_ be moved,
and the 'sql' alias will continue to point at the old server (zedler).
therefore, if you have created tables on the old server which you need to join
to s2 databases, you will need to move these to the new server yourself. do
not move normal user databases, they should remain on 'sql' as before.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAko+R7MACgkQIXd7fCuc5vIV9gCdGvqGabLQCienTQOB3Lk5ClyP
l3EAoIZebLgBV8X6zeUIspNZNn1C8mlE
=uYxB
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
we lost power for unknown reasons last night, causing an outage of the
Toolserver. most of the platform is back up, but s3 (yarrow) remains down.
as we had downtime anyway, i took the opportunity to move stable to the new
server. the old stable server (willow) is now offline.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAkpNUyQACgkQIXd7fCuc5vLYgACgvU7x5J12wdvK7epJLqX7iLnA
U/sAn2CvLg0tJTpc+mTBjieNFlXqvdnj
=E+ap
-----END PGP SIGNATURE-----