Re: [Toolserver-l] Maintenance: Solaris Updates
Hello all, At Saturday 11 May 2013 03:24:05 DaB. wrote: > I will update the solaris user and web servers as well as the head nodes on we had problems with the nfs-service and had build up a temporary solution for the time the root sleeps. FYI. Sincerely, DaB. -- Userpage: [[:w:de:User:DaB.]] — PGP: 0x2d3ee2d42b255885 signature.asc Description: This is a digitally signed message part. ___ Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
Re: [Toolserver-l] Inodes have run out on yarrow's /var (fwd)
Arg...wrong sender again... -- Forwarded message -- Date: Fri, 10 May 2013 14:07:29 From: Marlen Caemmerer To: Wikimedia Toolserver Subject: Re: [Toolserver-l] Inodes have run out on yarrow's /var Hey, thanks a lot. On Fri, 10 May 2013, Tim Landscheidt wrote: I think I found the culprit: | timl@yarrow:~$ df -i /var/spool/cron/atjobs | FilesystemInodes IUsed IFree IUse% Mounted on | /dev/mapper/yarrow0-var | 915712 915712 0 100% /var | timl@yarrow:~$ With my privileges, I can't find out what's causing this. What I would look at first if I could would be /var/log/iptraf and /var/spool/postfix/*. What filled it up was /var/log/sudo-io. It creates 5 files for every time sudo is used. I once had a loop running including a sudo command - this might have caused the problem since nightshade is far away from this usage of inodes. Tried to log into syslog which works but the directory itself stays there and is used so I dont currently have any idea how to turn this off. After fixing this, we need Nagios alerts for /var as well. Done :). P. S.: Toolserver Office Hour + 10 days = today. What do you mean with this? Cheers Marlen/nosy ___ Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
Re: [Toolserver-l] Inodes have run out on yarrow's /var
I wrote: >> [...] >> Plus medium and longrun queues in yarrow are in error state. I tried >> cleaning them, but they failed again. > I think I found the culprit: > | timl@yarrow:~$ df -i /var/spool/cron/atjobs > | FilesystemInodes IUsed IFree IUse% Mounted on > | /dev/mapper/yarrow0-var > | 915712 915712 0 100% /var > | timl@yarrow:~$ > With my privileges, I can't find out what's causing this. > What I would look at first if I could would be > /var/log/iptraf and /var/spool/postfix/*. > [...] Merlissimo had filed https://jira.toolserver.org/browse/TS-1649 earlier. Now someone or something has freed about 96 % of inodes on /var, but left no note, so I don't know if the queues on yarrow can be enabled again. Tim ___ Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
[Toolserver-l] Amsterdam hackathon workshops
For all Amsterdam hackathon attendees We've made a first draft of the programme for the Amsterdam Hackathon. We have room for 6 workshops which will be run twice over the course of the Hackathon. Which topics should we cover in them? Based on your motivations, we've made a list of the top 8 topics that seem to be of interest. Please take a look at the page and let us know which topics you'd be most interested in: https://www.mediawiki.org/wiki/Amsterdam_Hackathon_2013/Topics For some of these workshops we're still looking for presenters. Are you interested? Let us know! (hackat...@wikimedia.nl) Think you could fill a 1h (interactive) workshop for one of these topics, but you're not sure? I'll help you create a workshop and help you practice beforehand. Finne (henna) On behalf of the programme committee ___ Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
