Mark will (probably) be at knams this Friday, to do various things including
installing the new switch and database server. while this is going on there
will be some downtime as the network is being rearranged; it should be less
than an hour, some time in the afternoon (UTC).
if this doesn't happen on Friday, it will be Monday instead.
after the new server is installed, i will need to set up the OS and import the
s1 database. i'll probably leave it running for a bit to make sure
everything's good, so it won't be available immediately.
once the new server is working, i will be reinstalling zedler to fix the
current database issues.
if this goes as planned, i will submit to the Verein a proposal to replicate
the external text to the toolserver as well.
MySQL has stopped working for my cloak request script: I am getting
Warning: mysql_connect() [function.mysql-connect]: Lost connection to
MySQL server at 'reading initial communication packet', system error:
111 in /home/swhitton/public_html/includes/cloaks.inc on line 3
Could not establish connection to MySQL server. when I try to retrieve
the list of requests.
Also, someone reported that it wasn't working at all for submitting
requests at one point. Also, I sometimes find that dates are recorded
as 1970-01-01 or somesuch, which is a bit mysterious as it only
—Sean Whitton (seanw)
Can anyone suggest how to improve the performance of a query like this:
CREATE TABLE u_mashiah.pagelinks (
`pl_from` int(8) unsigned NOT NULL default '0',
`pl_namespace` int(11) NOT NULL default '0',
`pl_title` varchar(255) binary NOT NULL default '',
KEY `pl_from` (`pl_from`,`pl_namespace`)
) TYPE=MyISAM AS /* SLOW_OK */
This is the complete copying of a table from readonly database to personal
one with some altering on keys, not sufficient I suppose. It looks like if
copying like this is much slower than access to the same amount of data in
Thank you, Connel, it worked exactly as you described.
I had to strip some extra data from the newly generated
key and add "ssh-rsa " in front of it when inserting it
in ~/.ssh/authorized_keys , which was pretty obvious.
Importing the key of secureCRT to putty did not work.
UTF-8 support in putty seems less broken than in SecureCRT,
but it is far from working correctly :-( at first sight.
Maybe I need some tweaking with linux' terminal settings,
but I have no clue which selections to make.
> Message: 2
> Date: Mon, 18 Jun 2007 11:58:58 +0200
> From: toolserver-l.wikipedia.org(a)publi.purodha.net
> Subject: [Toolserver-l] Key poblem logging in with putty
> To: toolserver-l(a)lists.wikimedia.org
> Message-ID: <109213064793.20070618115858(a)purodha.net>
> Content-Type: text/plain; charset=us-ascii
> I am usually using secureCRT - http://vandyke.com/ - to
> log in to the toolserver.
> putty refuses secureCRTs key file ("this is not a key file")
> which is the only one I have.
> Can I convert the key file, which was generated by openssh,
> to a format that makes putty happy?
> If so, how do I do that, or where to find appropriate infos?
> Or should I rather generate a different key pair for putty?
> How would that be done, and how to implemet it, without
> superseeding the one already in use with secureCRT?
> Thank you for your help!
> Toolserver-l mailing list
> End of Toolserver-l Digest, Vol 20, Issue 9
Yes, PuTTY can import "regular" SSH keys. Run "puttygen.exe" then
"Conversions" --> "Import"...
Yes, you can alternately use puttygen.exe to generate (and export) fresh
keys then use SecureCRT to add them to ~/.ssh/authorized_keys
Remember to save your putty settings before connecting. Remember to use
SSH2. Remember to fiddle with "Window" --> "Translation" to get UTF-8.
If I recall correctly, you still can't save "default settings" but if you
give the connection a name (e.g. "toolserver") before saving, they persist.
I am usually using secureCRT - http://vandyke.com/ - to
log in to the toolserver.
putty refuses secureCRTs key file ("this is not a key file")
which is the only one I have.
Can I convert the key file, which was generated by openssh,
to a format that makes putty happy?
If so, how do I do that, or where to find appropriate infos?
Or should I rather generate a different key pair for putty?
How would that be done, and how to implemet it, without
superseeding the one already in use with secureCRT?
Thank you for your help!
I am having a problem similar to Mashiah Davisons.
I am Using http://vandyke.com/ SecureCRT which usually worked fine
for me. (I would like to give putty a test run, but it does not log
me in, see separate message, "Key poblem logging in with putty")
My problems are currently related to interwiki.py - a python
program dealing with links between languages.
A - reporting page titles in various languages/scripts, and
B - requiring command line parameters, and interactive responses,
in UTF-8 encoding
Problem Group A - messages:
Messages do strange things to the terminal emulation, e.g. they
display garbage, scroll backwards, suppress output, trigger an
automated response (you can never type a correct answer to a
prompt, when the backspace key has been redefined at the same time,
I tried every terminal emulation, SecureSCT has to offer, I tried
with and without UTF-8 enabled. Results varied slightly, but the
general behaviour remains - it's not usable.
I pipe messages into a file which I read over the web with a
When the web server is instructed to tell that it sends UTF-8,
everything is marvellous.
Drawbacks: huge overhead, rather time consuming, pretty unsuited for
hihgly interactive tasks. While I can read <g!> every foreign
script, and copy it locally, I cannot paste it back to the
I tried to alter Linux terminal type settings, and other such
settings. I have not found any of general usefulness, but some
allow 'some' operability at times.
My knowledge and experience in this field is, however, very
limited. I would like to find a reference + tutorial on
character encodig issues and settings under Linux / bash,
so as to understand the logic at work,
but could not find any yet.
(-: neither logic, nor tutorial, that is :-)
Problem Group B - interactive input, and command lines.
In short: with the SecureCRT Terminal set to UTF-8, you can
successfull copy and paste "some" (i.e. few) national characters
into command lines (luckily, the lower case German Umlauts are
among them, which I need often) but you cannot use bashs line
editing tool when you have exotic characters in a line buffer.
Everything else usually does not work; results are unpredictable.
Avoid interactivity entierly. Find the needed strings somewhere,
and pipe them into files where they do what you need. When editing
is unavoidable, scp your data elsewhere, edit e.g. under Windows,
which is bad enough, and scp the result back.
Obviously, this is not a solution.
I have a question related to national characters support. At home I'm
working on Windows machine and when I select Russian UTF-8 strings I see
data of doubled length. Unfortunately, strings I have for some category
names and pagenames do not work on the toolserver. When I select the same
data from a database, the symbols encoding I see in ssh terminal is
Who knows the common way to use national strings extracted on windows
machine in queries on toolserver? Or maybe this is just a ssh client issue?
I have created a pure sql script (
for orphaned articles collection according to Russian wikipedia rules.
This script cannot be run as is on the toolserver because it creates some
new temporary tables during execution, so my primary goal is to understand
how can I adapt this script to run on the toolserver. May be it is a way to
create my own little database and grant me writing rights on it or maybe
there is some other ways to work it out without rewriting it in perl or
python and working with hashes instead of sql tables.
One more thing, I am ok with running the script on my local machine but I
need an sql dump of some tables for this. Maybe there is a way to create a
little dump for tables I need on the toolserver on a daily basis instead of
waiting during two-three weeks when the dump of ruwiki will be available
again. I tried to dump a table on the toolserver without any success because
this requires table locking and I again have no rights for this. Is there a
way to create an sql dump without locking a table? I tried
'--skip-lock-table' option but got the following message:
mysqldump: Couldn't execute 'show create table `...`': SHOW VIEW command
denied to user '...' for table '...' (1142)