[Toolserver-l] Maintenance

Hi, The previous announced maintenance has been completed successfully. In case of problems, open an issue in the TS project in JIRA. For problems relating to the conversion of nightshade to Solaris (e.g. missing software), open an issue in the TS project and include "[solaris]" at the start

Re: [Toolserver-l] Compressing stats files better (was; Re: /mnt/user-store is full)

emijrp: > We can compress to xz while the new disks arrive. I read that it is about 24 > TB, so, we can revert to gzip in the future. PS: Yes, we are installing 24TB of disks (12x 2TB disks), but this is raw space. To begin with, a 2TB disk is only 1,862 GB of real space. Assuming we configure

Re: [Toolserver-l] Compressing stats files better (was; Re: /mnt/user-store is full)

emijrp: > We can compress to xz while the new disks arrive. I read that it is about 24 > TB, so, we can revert to gzip in the future. I suggested xz pretty much as an emergency fix; we don't want to delete the files, but they do take up a lot of space. I don't mind switching back to gzip when we

Re: [Toolserver-l] I10N and toolserver subdomains

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Peter Körner: > I'd like to have this possibility in my tools to select the source > wikipedia. If s/o uses it for translation, that's his thing ;) So I'd > too vote for this feature. This is one good reason *not* to implement this feature -- we mig

[Toolserver-l] General maintenance notice: January 3rd, 2011

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On the morning (UTC) of January 3rd we will performance general maintenance[0] on all servers. Services will be affected as follows: Service | Expected impact --+--

Re: [Toolserver-l] /mnt/user-store is full

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aryeh Gregor: > I'm looking at this, but I have no brighter idea than just running du > on it, which is taking a very long time. I wrote a tool called summdisk for this, which produces reports on per-user disk usage:

[Toolserver-l] Reboot of amaranth

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, At 19:20 UTC Wikimedia accidentally rebooted amaranth (the Toolserver system in the US) during maintenance. This caused an outage of JIRA, MediaWiki, FishEye and MySQL database replication for around 5 minutes. - river. -BEGIN PGP

Re: [Toolserver-l] mysql quries killing script

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mashiah Davidson: > Am I right that I need to check s3 replag as well for this particular > case but do not have to check replag on s2, s5 and s1? Yes. The server sets are: s1; s3/s6; s2/s5. In addition commons (s4) is present on all servers.

Re: [Toolserver-l] mysql quries killing script

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mashiah Davidson: > The script was working with just one DB cluster (s3/s6), so I've > checked just it's replication lag. There isn't an "s3/s6" replication lag. There's an s3 replication lag and an s6 replication lag. If your query was running o

Re: [Toolserver-l] Two beginner questions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Михајло Анђелковић: > I was returning the server whatever it was sending to me as a ping. This is > how it worked like two years ago. Has something changed? This is the correct way to do it, but many IRC client implementations are lazy and are writt

Re: [Toolserver-l] Two beginner questions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 MZMcBride: > Gahhh, this list. Nobody suggested just using Python's Twisted? Someone is suggesting it: you. That's pretty much the point of the list; there's more than one person on it. - river. -BEGIN PGP SIGNATURE- Version: GnuPG

Re: [Toolserver-l] mysql quries killing script

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mashiah Davidson: > ERROR 1317 (70100) at line 6874: Query execution was interrupted > last replicated timestamp: 20101207214400 > replag: 00:00:01 > Could anyone explain whether it was possible that a query (even a long > running one) has been kille

Re: [Toolserver-l] Two beginner questions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sumurai8 (DD): >     text = IRC.recv(1024) >     msgs = text.split('\n') This seems to have a bug: if there's more than 1024 bytes waiting, you could receive only part of the final message; so you will truncate that message, and the next recv will re

Re: [Toolserver-l] [Toolserver-announce] General maintenance notice: December 6th

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This maintenance was mostly completed. Upgrade of web applications (JIRA/MediaWiki) was postponed and will be finished tomorrow. In case of problems, please file an issue in JIRA. - river. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1

Re: [Toolserver-l] [Toolserver-announce] Hardware failure affecting s2/s5

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bryan Tong Minh: > It's amazing how fast you guys fixed this issue. Well, mostly I just sit at home and call Sun, and they send someone to fix the problem. So the speed of the fix is directly proportional to how much we pay Sun ;-) - river

Re: [Toolserver-l] [Toolserver-announce] Hardware failure affecting s2/s5

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The suspected faulty part has been replaced and MySQL is now running again. We will continue to monitor the system over the weekend. - river. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAkz499EACgkQIXd7fCuc5vL

Re: [Toolserver-l] [Toolserver-announce] Hardware failure affecting s2/s5

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, It looks like the server failed entirely overnight, so s2/s5 is unavailable for now. Unfortunately the engineer bought the wrong parts this morning, so we will try again this afternoon. - river. -BEGIN PGP SIGNATURE- Version: G

Re: [Toolserver-l] nightshade will be converted to Solaris on January 3, 2011

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jacobi Carter: > Will my statically compiled Go code run on Solaris like it did on > Linux? No, compiled software needs to be recompiled for Solaris. There is currently no Go compiler for Solaris, but if you need one, we can look at porting either

Re: [Toolserver-l] nightshade will be converted to Solaris on January 3, 2011

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Purodha Blissenbach: > I have reported *) a few incompatibilities in very basic tools and bash > that I have not the faintest idea of how to get around them under Solaris. Please files issues in JIRA and include "[solaris]" in the subject line. I do

Re: [Toolserver-l] [Toolserver-announce] Hardware failure affecting s2/s5

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 River Tarnell: > However, we will need to shut down the system either today or later this week > to replace the faulty part, which will cause under 30 minutes outage for > s2/s5. This maintenance has been scheduled for 1030h UTC[0] tomo

Re: [Toolserver-l] [Toolserver-announce] Hardware failure affecting s2/s5

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 River Tarnell: > The s2/s5 server is currently experiencing some hardware issues. As we > currently only have a single server for s2/s5, this may result in outages for > these clusters. Hi, We have identified the cause of the fault a

[Toolserver-l] Hardware failure affecting s2/s5

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, The s2/s5 server is currently experiencing some hardware issues. As we currently only have a single server for s2/s5, this may result in outages for these clusters. We have raised an SR with Sun to replace the faulty hardware. - river

Re: [Toolserver-l] Are months shorter in 2011?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nakor: > I renewed my account today for "6 months" and the new expiration date is > May 17 2011. I do not care the two weeks difference but just wanted to > check if it was a bug in the renewal tool. It actually renews your account for 168 days (24

[Toolserver-l] Software update schedule

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, After this month's maintenance, which includes quite a few software updates/changes, I'd like to come up with a coherent strategy for updating software. The aim is to balance the inconvenience of updates (which can require changes from users)

Re: [Toolserver-l] General maintenance notice: December 6th

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Marco Schuster: > please use a service like http://www.timeanddate.com/worldclock/ in > the future when specifying dates/times. Sorry, I don't understand what you're asking for here. Can you give an example? - river. -BEGIN PGP SIGNATUR

Re: [Toolserver-l] General maintenance notice: December 6th

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aryeh Gregor: > On Mon, Nov 29, 2010 at 11:27 AM, River Tarnell > wrote: > > Start time: Monday, 6th December, 12AM UTC > > End time: Monday, 6th December, 8AM UTC (estimated) > Are these reversed or what? No. 12AM (h)

Re: [Toolserver-l] Extracting basic revision data

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Михајло Анђелковић: > Namespaces are easily determined from the page prefix, I am not > bothered if there are any anomalies out there (i.e. page starting with > "User talk:" being in NS 0) There are no page namespace prefixes in the databases. IOW, "

[Toolserver-l] General maintenance notice: December 6th

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On the morning (UTC) of December 6th we will perform general maintenance[0] on all servers. Services will be affected as follows: Service | Expected impact -+---

Re: [Toolserver-l] Extracting basic revision data

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Михајло Анђелковић: > WHERE rev_id > 0 AND rev_id < [...] AND rev_deleted = 0; Please check that MySQL plans this correctly (using the rev_id index). > If this is generally allowed to do, my question is how large chunks of > data can I take at once,

Re: [Toolserver-l] Changes to software libraries in /opt/ts

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mauro Girotto: > 2010/11/14 River Tarnell : > I'm trying to switch from CC to gcc. My app uses mysqlpp library. Does > /opt/ts/lib contain the libraries of Sun Studio? If I compile with -L > /opt/ts/lib -lmysqlpp I've a linkin

Re: [Toolserver-l] Problem with matplolib / pylab

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Robin Krahl: > ImportError: ld.so.1: python: fatal: relocation error: file > /opt/ts/python/2.6/lib/python2.6/site-packages/matplotlib/_path.so: > symbol > __1cDstdMbasic_string4Ccn0ALchar_traits4Cc__n0AJallocator4Cc___J__nullref_: > referenced symbol

Re: [Toolserver-l] php scripts timing out after 2 minutes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ryan Kaldari: > My PHP scripts for the contests tool seem to be consistently timing > out after 2 minutes now. I have max_execution_time set to 7 minutes in > both the scripts themselves and in .htaccess. The contests tool is > pretty much unusable wit

Re: [Toolserver-l] alternative way to get wikipedia dump while server is down

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 (Removing wikitech-l cc since I'm not subscribed there.) Platonides: > Roan Kattouw wrote: > > 2010/11/26 Bryan Tong Minh : > >> Somehow I think that publishing an entire dump violates the "do not > >> publish significant parts of an article" rule. >

Re: [Toolserver-l] php scripts timing out after 2 minutes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ryan Kaldari: > My PHP scripts for the contests tool seem to be consistently timing > out after 2 minutes now. I don't see anything in the sever configuration that would cause this. I've raised an issue with Zeus support. - river. -BEG

Re: [Toolserver-l] Default Python will change to 2.7

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Kinzler: > This might actually be a reason to not roll out 2.7 and wait for a fixed > version. Is there a statement from the python people on this? It's quite simple to patch our version of 2.7 to revert the change, since it seems like the int

[Toolserver-l] Default Python will change to 2.7

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, During the general maintenance on Dec 6th, we will change the default Python version (/usr/bin/python) on the Solaris user servers from 2.6 to 2.7. You may wish to test your tools with /usr/bin/python2.7 before then. - river. -BEGI

Re: [Toolserver-l] Fast local storage

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Marco Schuster: > I can imagine a use of this for everything that uses the static or xml > dumps, as well as unpacking or packing large files. Do you have any numbers for a particular use case? - river. -BEGIN PGP SIGNATURE- Version:

[Toolserver-l] Fast local storage

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, A feature we may provide to users in the future is servers with fast local (not NFS) storage for use by tools. This would be something like user-store, except per-server. This storage would be redundant (RAID), but not backed up. If anyone fe

Re: [Toolserver-l] Jobs with running time limitation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mauro Girotto: > Is possible to have some notifications when a job exceeds the running > time set by h_rt? Yes, by setting s_rt to a lower value. When s_rt is exceeded, the program will receive SIGUSR1, so you can clean up and exit yourself. $ qsu

Re: [Toolserver-l] Newbie question: definition of a "heavy job" for toolserver

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alex Brollo: > Have I some Unix tool to evaluate server resource used running a script? Yes, but it depends on operating system. If you're using a Solaris server (willow), use prstat: $ prstat -aU $LOGNAME Or on Linux (nightshade), use top: $ t

Re: [Toolserver-l] Newbie question: definition of a "heavy job" for toolserver

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alex Brollo: > My question is: how many pywikipedia readings/editing per hour are a "heavy" > toolserver job? We don't usually measure resource use in "pywikipedia readings/editing per hour" ;-) The most common indicators of resource use are CPU time

Re: [Toolserver-l] SGE can now be used for *all* tools

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sorry for the flood of announcements about SGE today. I think this should be the last one. > This policy has now changed, and SGE can be used for all jobs, including > long-running jobs. This effectively obsoletes Phoenix and similar tools, > sin

Re: [Toolserver-l] SGE can now be used for *all* tools

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alex Brollo: > Thanks. A question. I'm a new toolserver user, presently working at a long > list of personal "Hello world" tests. Next scheduled "Hello world" was cron > test. Is your suggestion to step over cron, and to try to learn SGE from the > be

[Toolserver-l] SGE can now be used for *all* tools

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, In the past, our policy on SGE (batch job scheduling) was that it should only be used for jobs which run once then exit, and that it should not be used for jobs which run continuously. This policy has now changed, and SGE can be used for all jo

Re: [Toolserver-l] [Toolserver-announce] SGE on web servers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > The webservers (wolfsbane and ortelius) have been added as SGE submit hosts, Since the webservers have a lot of idle CPU (about 90%), I've now added them as SGE execution hosts as well, so SGE jobs will run on these systems. We'll monitor to mak

Re: [Toolserver-l] RAM disk?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Marc A. Pelletier: > >> You can use /tmp, which is a memory filesystem for exactly this reason. > >> (But > >> only on Solaris systems, not Linux, so you probably want to use willow.) > Wait, why isn't your /tmp be mounted with tmpfs? (Hm. Debian

[Toolserver-l] nightshade will be converted to Solaris on January 3, 2011

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Since no major issues have been raised regarding the conversion of nightshade to Solaris, this has been schedule for the maintenance window on January 3rd, 2011. For more information, see

[Toolserver-l] SGE on web servers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, The webservers (wolfsbane and ortelius) have been added as SGE submit hosts, which means you can submit jobs from these servers (e.g. from CGI scripts). However, jobs will not run on these servers. - river. -BEGIN PGP SIGNATURE

[Toolserver-l] Changes to software libraries in /opt/ts

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, During the next maintenance window (Dec 6), we will switch from Sun Studio to GCC as the standard C and C++ compiler for ts-specs (/opt/ts). If you have have locally-compiled C or C++ software, you should read the rest of this mail. Otherwis

Re: [Toolserver-l] RAM disk?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Matthew P. Del Buono: > I'm in the conceptual phase of a new bot but it requires a bit of > processing. Unfortunately the only way this processing can be done is by > writing out two small files. > However, the processing should be very fast, and aft

Re: [Toolserver-l] Account expiry

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kay Drangmeister: > The same happened for me when I tried to set the license during the > acctrenew process. It did not work. I cancelled acctrenew and started > setlicense (sp?) separately, and it worked. After that, acctrenew > worked, too (without r

Re: [Toolserver-l] [Toolserver-announce] Account expiry

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 River Tarnell: > * Running setmail and setlicense within acctrenew currently doesn't work. This should now be fixed. - river. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16

Re: [Toolserver-l] Account expiry

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Platonides: > That would be your UNIX password. I don't know if it's joined to LDAP, It is, which is why setpass will refuse to run if a password is already set. willow% setpass setpass: password already set setpass: use passwd(1) to change your pass

Re: [Toolserver-l] Account expiry

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bongwon Suh: > In addition, when I was trying to run 'passwd', I got the following > message. > > wiki_researc...@willow:~$ passwd > passwd: Changing password for wiki_res > passwd: User unknown: wiki_res This should now be fixed, although if you h

Re: [Toolserver-l] [Toolserver-announce] Account expiry

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, So to clear up some issues which have arisen: * Running setmail and setlicense within acctrenew currently doesn't work. I'll fix this later today, in the mean time you can run them manually. * If you do not have an email address set and cann

Re: [Toolserver-l] Account expiry

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 James Hare: > For those of us not on a Solaris system, how will renewal work? You cannot be "not on a Solaris system". Toolserver accounts are shared between all servers, so you can use the same credentials to log into any server, and renewing your

Re: [Toolserver-l] Fwd: [Tagging] Download huge file via HTTP

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Peter Körner: > This works for the small files (md5sums) but the 3.1G VMDK File is not > accessible: http://toolserver.org/~mazder/osm_vm/ This is a known issue with ZWS; files larger than 2GB will not work. Sorry. - river. -BEGIN PGP SI

[Toolserver-l] Account expiry

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Users were supposed to received an automated mail 28 days before account expiry (which is currently 1 Dec for most users), but due to an issue with the program which sends the mails, they were not sent. The problem has been fixed and users wil

Re: [Toolserver-l] enable gz compression

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Peter Körner: > I tried to use this directive in various ways in .htaccess files in > various places but it did not seem to have any impact. Any ideeas? I have enable compression globally for: text/plain text/html application/x-javascript It might

Re: [Toolserver-l] enable gz compression

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Peter Körner: > You're right, I'm sorry. Is there a way to enable js compression? Did the solution Platonides suggested not work? - river. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (FreeBSD) iEYEARECAAYFAkzSgpMACgkQIXd7fCuc5vJZKwC

Re: [Toolserver-l] Upload many GB to Internet Archive

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 emijrp: > I would like that an admin reply me if there isn't any problem with using a > lot of upstream bandwidth resources for this. A few hundred GB isn't a lot of bandwidth ;-) - river. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16

Re: [Toolserver-l] enable gz compression

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Peter Körner: > There are known bugs with some versions of IE and compressed JS so they > need to be excluded somehow, see > http://httpd.apache.org/docs/2.0/mod/mod_deflate.html According to that page, MSIE has no problems with compressed content, b

[Toolserver-l] New maintenance policy

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, In the past some users have complained that we don't have a regular maintenance policy, so it's difficult to plan long tasks around downtime. To solve this, we will be implementing the following maintenance schedule: https://wiki.tools

[Toolserver-l] Maintenance on web services

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Web services (JIRA, FishEye, MediaWiki) are currently offline while we move the host machine (amaranth) to a different rack. This should take less than an hour. - river. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (FreeBSD) i

[Toolserver-l] s4 replication lag

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, There was ~1.5 hours of replication lag on s4 (commons) on all servers, starting around 1600h UTC, because Wikimedia upgraded the s4 master to MySQL 5.1, and trainwreck (our replication tool) does not understand the 5.1 binlog format. I have n

[Toolserver-l] Perl 5.10 removed

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Perl 5.10 has now been removed from the Solaris login servers. - river. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (FreeBSD) iEYEARECAAYFAkycQ3YACgkQIXd7fCuc5vIoxQCgo5+uWmAWXMZEKNsKxOSxNl6Q wNsAn1ugrNCzBtmBhckvfjTpFLExnu9Q =9o8

[Toolserver-l] Python 3.1

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Python 3.1 is now available on the Solaris login servers as /usr/bin/python3 (or /usr/bin/python3.1 to require a specific version). The only module installed so far is "oursql", to provide MySQL connectivity. (MySQLdb is not installed, since

Re: [Toolserver-l] Maintenance notice for Tuesday, 21st

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This maintenance has been completed. - river. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (FreeBSD) iEYEARECAAYFAkyZWOsACgkQIXd7fCuc5vI+aACfXnkEW3MEeZ5P8Z4aK2afpqHV N90AnAhcnIwIEiI74VUujKrxCo8fh22R =RH59 -END PGP SIGNATURE-

[Toolserver-l] Maintenance notice for Tuesday, 21st

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This is a maintenance notice for today, Tuesday the 21st. Service | Expected impact - --+- ptolemy: OpenStreetMap| Complete outage for under 10 m

[Toolserver-l] nightshade reboot

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, nightshade was rebooted at 5:05 AM on Tuesday (UTC) for a kernel update. - river. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (FreeBSD) iEYEARECAAYFAkyYPR4ACgkQIXd7fCuc5vLpAQCeNEff17OzRYlfvIXhunm+3+xU QnAAnjByPEDEijD1Pm7waivrNUd

[Toolserver-l] Mono upgrade on Solaris

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Mono on the Solaris login servers has been upgraded from 2.4.2.2 to 2.6.7. - river. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (FreeBSD) iEYEARECAAYFAkyX/5MACgkQIXd7fCuc5vJ7fACfVJDz3q/ZhLtHmfbaqmDjbXMZ kGAAnjqs6m699q31R0LmDTvQc

[Toolserver-l] Perl upgrade to 5.12.2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Perl on the Solaris systems will shortly be upgraded from 5.12.1 to 5.12.2. This should have no impact on users. - river. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (FreeBSD) iEYEARECAAYFAkySPGEACgkQIXd7fCuc5vLuPQCfawQtGLeDnC

Re: [Toolserver-l] Removal of Perl 5.10 on Solaris systems

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Carl (CBM): > Please remember to change /etc/default/login when you do it (maybe you > already had this in mind). The default path at the moment seems to > choose perl 5.10 explicitly, not /usr/bin/perl . Hm. I've fixed this; I'll leave the removal o

Re: [Toolserver-l] using local perl

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ted Timmons: > The problem is that there's no local Config.pm at the given location. In > other words, /etc/perl/CPAN/Config.pm in step 3 does not exist. That > makes it hard to follow step 4 and beyond. I think it's unlikely that a /etc/perl direct

Re: [Toolserver-l] Conversion of nightshade to Solaris

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Platonides: > And perhaps not too hard. A naive implementation could just store > requests into a vixie cron that sent its processes into the jobserver > (by changing its shell maybe?). Adding support for "every 2 hours" is not difficult at all, and i

Re: [Toolserver-l] Conversion of nightshade to Solaris

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Simon Walker: > Bryan Tong Minh: >> I really like the crontab syntax of vixie cron, especially @reboot and >> /. Would it be possible to use vixie on Solaris? > Or the jobserver to be sorted out for scheduling tasks maybe? I notice that > per-month sc

[Toolserver-l] Conversion of nightshade to Solaris

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, After some internal discussion and previous consultation with users, we have decided to standardise on Solaris for the login and web servers. We will therefore be converting nightshade from Linux to Solaris at some point in the future. There

[Toolserver-l] Removal of Perl 5.10 on Solaris systems

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Some time ago we changed the default Perl on Solaris login servers to 5.12. Since then, no one has reported any problems with 5.12; we will therefore be removing Perl 5.10 later this week (that is, /usr/bin/perl5.10 and /opt/ts/perl/5.10/bin/p

Re: [Toolserver-l] need CPAN module installed on nightshade

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Q: > So I dont have to file another ticket every time the module is upgraded > to fix a bug. We currently do Perl module upgrades the same way as other software -- infrequently, and all at once. Would it be more useful if they were done more regula

Re: [Toolserver-l] need CPAN module installed on nightshade

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mike.lifeguard: > Any chance you'd write up a tutorial on installing Perl modules in one's > $HOME? I think it'd be helpful, as this isn't the first time it has > cropped up. It's already described here: https://wiki.toolserver.org/view/Perl but it's

Re: [Toolserver-l] need CPAN module installed on nightshade

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ted Timmons: > I'm a newbie to the toolserver world. Who do I contact to get perl's > Time::ParseDate installed on a toolserver (specifically, nightshade)? All software installation requests should go to JIRA (https://jira.toolserver.org), in the TS

Re: [Toolserver-l] Maintenance: user-store; all database clusters tonight

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This maintenance has been completed successfully. - river. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (FreeBSD) iEYEARECAAYFAkyMJlcACgkQIXd7fCuc5vJGBwCfVuuSE6jB8j8Gr7yq9mmotmzY PTIAoJyWfKH9JAjoRqY5bNN8D+XO7l4P =3KmV -END PGP SIG

[Toolserver-l] Mail changes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, We have replaced sendmail on the Solaris login servers with the Postfix MTA. This should not make any difference to users, except that it should fix the problem with cron mails not being delivered. - river. -BEGIN PGP SIGNATURE

Re: [Toolserver-l] cron and email

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andrew Steinborn: > > Andrew Steinborn: > >> I am not getting cron emails, and think that my cron tasks are not > >> working. > > What is your username? > andrew is my username. Your cron jobs are running, but there is an issue with sending mail. I'm

[Toolserver-l] Maintenance: user-store; all database clusters tonight

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 (I have the impression that our maintenance notices are not always very clear, since people are sometimes surprised when we carry out previously-announced maintenance. So, here's a new and hopefully improved notification format.) This is a maintena

Re: [Toolserver-l] cron and email

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andrew Steinborn: > I am not getting cron emails, and think that my cron tasks are not > working. What is your username? - river. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (FreeBSD) iEYEARECAAYFAkyLm1EACgkQIXd7fCuc5vIfJgCeLsfvua0

Re: [Toolserver-l] Maintenance on hyacinth (s3/s4/s6); login/web servers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This maintenance was completely successfully. There was about 5 minutes downtime of the web server due to a software issue (which is now fixed). - river. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (FreeBSD) iEYEARECAAYFAkyK+xsACgk

Re: [Toolserver-l] Maintenance on hyacinth (s3/s4/s6); login/web servers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Slight change to this maintenance: we will first test the Solaris upgrade on rosemary, one of the s1 database servers, before upgrading willow. This will push back the upgrade by about an hour, but will not impact users. - river. -

Re: [Toolserver-l] Maintenance on hyacinth (s3/s4/s6); login/web servers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andrew Steinborn: > Nice. Downtime for my bots. Yes, there will be under 10 minutes' downtime while the system reboots after the upgrade. This is unavoidable; the only other option is that we would never, ever upgrade the OS or even reboot the serv

[Toolserver-l] Maintenance on hyacinth (s3/s4/s6); login/web servers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Later tonight we will upgrade the OS on hyacinth (s3/s4/s6 server). This will involve ~30 minutes downtime, but should have no impact on users. We will also upgrade the OS on willow at the same time, which should require <10 minutes downtime.

Re: [Toolserver-l] user-store disk usage

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Schwen: > Uhm, I see 215G in /mnt/user-store/wikiminiatlas/, I thought that is > the lions share of my stuff. Where is the other half? hemlock# du -sh iip-cache-dschwen 201Giip-cache-dschwen - river. -BEGIN PGP SIGNATURE-

Re: [Toolserver-l] user-store disk usage

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Here is the per-user usage report: schutz : 822.69G in 14604 files cmarqu : 492.62G in 126629282 files

Re: [Toolserver-l] user-store disk usage

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Frederic Schutz: > ==> over 20% of the data is mine... This is only 20%, and as far as I know does not grow at the rate that would explain the recent increase in user-store disk usage. Still, if you find no one is using the older files, and they ar

[Toolserver-l] user-store disk usage

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, If you are currently using disk space on user-store, please check your usage and delete any unneeded files. There is only 70GB of space left on the volume now. (I will produce a more detailed report of who's using space later...) - ri

Re: [Toolserver-l] High replag on s2/s5

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, We have identified the cause of the s2/s5 problem as being the previously announced MySQL changes. Only s2/s5 was adversely affected because it had a different (older) filesystem configuration than the other servers. We have reverted this chan

[Toolserver-l] High replag on s2/s5

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, There is currently a large amount of replication lag on the s2/s5 server. This might be related to a failed disk which will be replaced next week. In the mean time we will continue to monitor it. - river. -BEGIN PGP SIGNATURE-

Re: [Toolserver-l] MySQL maintenance tonight

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This maintenance was completed successfully. - river. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (FreeBSD) iEYEARECAAYFAkx3GQ8ACgkQIXd7fCuc5vJv/wCfYYF+U4snxH6CEXCtjhpbiIAH TgUAn3iIJduQGmUZB/0FBzaqG3UE40jP =52Iv -END PGP SIGNATUR

[Toolserver-l] MySQL maintenance tonight

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I will be restarting all MySQL servers later tonight / tomorrow morning (UTC). For user databases (sql), there will be < 30 minutes downtime. For -rr replicated database, there will be no downtime except on s2/s5, where there will be < 30 minu

Re: [Toolserver-l] MySQL & Ruby changes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Happy-melon: > Why the Ruby downgrade? Because it seems that a lot of third-party software has not been updated to work with Ruby 1.9 yet. Rather than spending hours patching it, it's easier to change the default (supported) version. - r

[Toolserver-l] MySQL & Ruby changes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, We are about to make two changes to the Solaris login servers: * MySQL will be linked with libreadline instead of libeditline. The new MySQL will be more compatible with MySQL on Linux, but will not be able to read existing .mysql_history

<    1   2   3   4   5   6   7   8   9   >