-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
hello,
the new login server (nightshade.toolserver.org) is now ready for use. this server is for everything except web serving. all your bots, tools, etc. must now be run here.
the login alias 'login.toolserver.org' will be updated shortly. this might cause host keys warnings from your SSH client. the fingerprints of the new server are:
RSA: 81:64:c8:f8:29:d1:ed:d7:b5:96:7a:5c:fa:d3:f5:61 DSA: e2:4a:07:58:36:ec:9c:0a:73:b4:f8:49:8f:ff:1a:d0
/home is shared between both servers, so there is no need to copy any files over. http://toolserver.org/ URLs still point to hemlock.
if you find any problems with the new server, please file a bug at https://jira.toolserver.org in the Toolserver project.
after 1 week from today (June 19), we will start killing all tools which run on hemlock.
- river.
this server is for everything except web serving. all your bots, tools, etc. must now be run here.
[..]
/home is shared between both servers, so there is no need to copy any files over. http://toolserver.org/ URLs still point to hemlock.
[..]]
after 1 week from today (June 19), we will start killing all tools which run on hemlock.
So people who use user-crontabs must check the hostname now?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Daniel Schwen:
So people who use user-crontabs must check the hostname now?
i don't understand what you mean. crontabs are not shared between servers. so just install the crontab on the server you want it to run on.
- river.
Hopefully this is the right procedure (it's what I did at least)
ssh username@hemlock.toolserver.org crontab -e <copy crontab; erase> exit
ssh username@nightshade.toolserver.org crontab -e <paste crontab> exit
HTH
SQL
Daniel Schwen wrote:
this server is for everything except web serving. all your bots, tools, etc. must now be run here.
[..]
/home is shared between both servers, so there is no need to copy any files over. http://toolserver.org/ URLs still point to hemlock.
[..]]
after 1 week from today (June 19), we will start killing all tools which run on hemlock.
So people who use user-crontabs must check the hostname now?
Toolserver-l mailing list Toolserver-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Cheers, by the way, for moving all our stuff from Hemlock to Nightshade. (Hah -- I just got now that the successor to a toxic plant is another toxic plant). I greatly appreciate it.
On Wed, Jun 18, 2008 at 7:49 PM, SQL sxwiki@gmail.com wrote:
Hopefully this is the right procedure (it's what I did at least)
ssh username@hemlock.toolserver.org crontab -e <copy crontab; erase> exit
ssh username@nightshade.toolserver.org crontab -e
<paste crontab> exit
HTH
SQL
Daniel Schwen wrote:
this server is for everything except web serving. all your bots, tools, etc. must now be run here.
[..]
/home is shared between both servers, so there is no need to copy any
files
over. http://toolserver.org/ URLs still point to hemlock.
[..]]
after 1 week from today (June 19), we will start killing all tools which run on hemlock.
So people who use user-crontabs must check the hostname now?
Toolserver-l mailing list Toolserver-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Toolserver-l mailing list Toolserver-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/toolserver-l
On Wed, Jun 18, 2008 at 7:52 PM, James Hare messedrocker@gmail.com wrote:
Cheers, by the way, for moving all our stuff from Hemlock to Nightshade. (Hah -- I just got now that the successor to a toxic plant is another toxic plant). I greatly appreciate it.
On Wed, Jun 18, 2008 at 7:49 PM, SQL sxwiki@gmail.com wrote:
Hopefully this is the right procedure (it's what I did at least)
ssh username@hemlock.toolserver.org crontab -e <copy crontab; erase> exit
ssh username@nightshade.toolserver.org crontab -e
<paste crontab> exit
HTH
SQL
Daniel Schwen wrote:
this server is for everything except web serving. all your bots,
tools,
etc. must now be run here.
[..]
/home is shared between both servers, so there is no need to copy any
files
over. http://toolserver.org/ URLs still point to hemlock.
[..]]
after 1 week from today (June 19), we will start killing all tools
which
run on hemlock.
So people who use user-crontabs must check the hostname now?
Toolserver-l mailing list Toolserver-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Toolserver-l mailing list Toolserver-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Toolserver-l mailing list Toolserver-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Note that you can do magic stuff to transfer crontabs: (hopefully this eases headaches) @hemlock: crontab -l > crontab.txt @nightshade: cat crontab.txt | crontab -e Then just blank your crontab at hemlock. No need to be copying and pasting.
Oh, sure, do everything the easy way!
SQL
Dan Collins wrote:
On Wed, Jun 18, 2008 at 7:52 PM, James Hare <messedrocker@gmail.com mailto:messedrocker@gmail.com> wrote:
<snip>Note that you can do magic stuff to transfer crontabs: (hopefully this eases headaches) @hemlock: crontab -l > crontab.txt @nightshade: cat crontab.txt | crontab -e Then just blank your crontab at hemlock. No need to be copying and pasting.
-- DCollins/ST47 Administrator, en.wikipedia.org http://en.wikipedia.org Channel Operator, irc.freenode.net/#wikipedia http://irc.freenode.net/#wikipedia Maintainer, Perlwikipedia module
Toolserver-l mailing list Toolserver-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Hi River,
Can I please confirm that nightshade's IP address is 91.198.174.201? I'd like to put a notice on its user page denoting it is in fact the toolserver.
Thank you.
Regards,
James R. Administrator - English Wikipedia Online Team Member - Wikimania 2008 (Alexandria, Egypt) e.wikimedia@gmail.com
-----Original Message----- From: toolserver-l-bounces@lists.wikimedia.org [mailto:toolserver-l-bounces@lists.wikimedia.org] On Behalf Of River Tarnell Sent: Thursday, 19 June 2008 9:42 AM To: toolserver-announce@lists.wikimedia.org Cc: toolserver-l@lists.wikimedia.org Subject: [Toolserver-l] new login server
hello,
the new login server (nightshade.toolserver.org) is now ready for use. this server is for everything except web serving. all your bots, tools, etc. must now be run here.
the login alias 'login.toolserver.org' will be updated shortly. this might cause host keys warnings from your SSH client. the fingerprints of the new server are:
RSA: 81:64:c8:f8:29:d1:ed:d7:b5:96:7a:5c:fa:d3:f5:61 DSA: e2:4a:07:58:36:ec:9c:0a:73:b4:f8:49:8f:ff:1a:d0
/home is shared between both servers, so there is no need to copy any files over. http://toolserver.org/ URLs still point to hemlock.
if you find any problems with the new server, please file a bug at https://jira.toolserver.org in the Toolserver project.
after 1 week from today (June 19), we will start killing all tools which run on hemlock.
- river.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
James R.:
Can I please confirm that nightshade's IP address is 91.198.174.201?
yes, it is.
- river.
If I understand correctly, the new server does not allow using httpd for serving files through the web. If that's the case, what will happen to the tools which use HTTP to interface with users (e.g. editcounter and such)?
On Thu, Jun 19, 2008 at 1:41 AM, River Tarnell river@wikimedia.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
hello,
the new login server (nightshade.toolserver.org) is now ready for use. this server is for everything except web serving. all your bots, tools, etc. must now be run here.
the login alias 'login.toolserver.org' will be updated shortly. this might cause host keys warnings from your SSH client. the fingerprints of the new server are:
RSA: 81:64:c8:f8:29:d1:ed:d7:b5:96:7a:5c:fa:d3:f5:61 DSA: e2:4a:07:58:36:ec:9c:0a:73:b4:f8:49:8f:ff:1a:d0
/home is shared between both servers, so there is no need to copy any files over. http://toolserver.org/ URLs still point to hemlock.
if you find any problems with the new server, please file a bug at https://jira.toolserver.org in the Toolserver project.
after 1 week from today (June 19), we will start killing all tools which run on hemlock.
- river.-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (SunOS)
iEYEARECAAYFAkhZnT0ACgkQIXd7fCuc5vL/XQCgsnEhOZ8xpvz4FxDi7ORAeSi/ iHUAoJfi1svrS9XnXz94Fb7SIS0NtRmj =YQmA -----END PGP SIGNATURE-----
Toolserver-l mailing list Toolserver-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/toolserver-l
On Thu, Jun 19, 2008 at 9:57 AM, Mohd Tarmizi tarmiziaffandi@gmail.com wrote:
If I understand correctly, the new server does not allow using httpd for serving files through the web. If that's the case, what will happen to the tools which use HTTP to interface with users (e.g. editcounter and such)?
That's what hemlock was for, as I recall. You still have only one
/home/username/public_html that is shared over the two servers, so simply leave the scripts where they are and it should Work.
Hello,
at first: the command "faq" doesn't work on nightshade (but I'm told to use this command to find the documentation.
Am 19.06.2008, 01:41 Uhr, schrieb River Tarnell river@wikimedia.org:
after 1 week from today (June 19), we will start killing all tools which run on hemlock.
I want to point at a problem with WikiSense. Some of my tools need access to the full text of some articles and they use the WikiProxy located at http://toolserver.org/~daniel/WikiSense/WikiProxy.php. I think I'm not the only one using the WikiProxy. But this tool now isn't at "localhost" anymore and so some of my tools are broken... Maybe there is a possibility to fix this.
Sincerelly, Christian Thiele / apper
Christian Thiele wrote:
I want to point at a problem with WikiSense. Some of my tools need access to the full text of some articles and they use the WikiProxy located at http://toolserver.org/~daniel/WikiSense/WikiProxy.php. I think I'm not the only one using the WikiProxy. But this tool now isn't at "localhost" anymore and so some of my tools are broken... Maybe there is a possibility to fix this.
Well, don't try to access it at "localhost" then, but on "hemlock". I have configured to to allow access from nightshade too (or at least i tried -- if you get 403-errors, please tell me).
-- Daniel
toolserver-l@lists.wikimedia.org