toasters

toasters@lists.teaparty.net

2 participants
13529 discussions

Spam
by Bokkelkamp Ernst 26 Mar '02

26 Mar '02

I hate to say this, but I am considering leaving the list. I have been silently in the background for a long time because of not having a toy, I mean filer, to play with but it looks that the mailing list is currently being abused. I already have one yahoo account blocked, but it becomes a bit more difficult with the latest message from Jinjiang Shengyi Shoes Co., Ltd. (Manufcturer). Bye Ernie Here is the header: Received: from mail1.siemens.de ([139.23.33.14]) by mchx07da.mchm.siemens.de with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id HM60G0V3; Tue, 26 Mar 2002 18:08:21 +0100 Received: from goliath.siemens.de (goliath.siemens.de [192.35.17.28]) by mail1.siemens.de (8.11.6/8.11.6) with ESMTP id g2QH8KW03511 for <Ernst.Bokkelkamp(a)mch10.sbs.de>; Tue, 26 Mar 2002 18:08:20 +0100 (MET) Received: from smtp2.mathworks.com (smtp.mathworks.com [144.212.95.12]) by goliath.siemens.de (8.11.6/8.11.6) with ESMTP id g2QH8JR08728 for <Ernst.Bokkelkamp(a)mch10.sbs.de>; Tue, 26 Mar 2002 18:08:19 +0100 (MET) Received: from mail.mathworks.com (turing.mathworks.com [144.212.95.101]) by smtp2.mathworks.com (8.11.6/8.11.6) with ESMTP id g2QGoh104179; Tue, 26 Mar 2002 11:50:43 -0500 (EST) Received: (from majordom@localhost) by mail.mathworks.com (8.11.2/8.11.2) id g2QGcvH26842; Tue, 26 Mar 2002 11:38:57 -0500 (EST) Received: from smtp2.mathworks.com (smtp.mathworks.com [144.212.95.12]) by mail.mathworks.com (8.11.2/8.11.2) with ESMTP id g2QGct526827 for <toasters(a)mathworks.com>; Tue, 26 Mar 2002 11:38:56 -0500 (EST) Received: from smtp.mathworks.com (scanner.mathworks.com [144.212.95.161]) by smtp2.mathworks.com (8.11.6/8.11.6) with ESMTP id g2QGcs101506 for <toasters(a)mathworks.com>; Tue, 26 Mar 2002 11:38:54 -0500 (EST) Received: from hadrian.uk.mathworks.com (ns.uk.mathworks.com [192.168.72.250]) by smtp.mathworks.com (8.11.6/8.11.6) with ESMTP id g2QGcqp01491 for <toasters(a)mathworks.com>; Tue, 26 Mar 2002 11:38:52 -0500 (EST) Received: from petter ([218.5.139.13]) by hadrian.uk.mathworks.com (8.11.6/8.11.6) with SMTP id g2QGcmP23867 for <toasters(a)mathworks.com>; Tue, 26 Mar 2002 16:38:49 GMT Message-Id: <200203261638.g2QGcmP23867(a)hadrian.uk.mathworks.com> From: mike (Manufacturer of shoes) <5626512(a)963.net> Reply-To: r-start(a)163.com Subject: Jinjiang Shengyi Shoes Co., Ltd. (Manufcturer) Date: Wed, 27 Mar 2002 00:20:45 +0800 X-Mailer: 007 Direct Email Easy Sender: owner-toasters(a)mathworks.com Precedence: bulk

5 4

Re: SNMP Failure Detection
by Alek O. Komarnitsky (N-CSC) 26 Mar '02

26 Mar '02

> From owner-toasters(a)mathworks.com Tue Mar 26 12:14 MST 2002 > > Hello Toasters. > > I've been using a script to monitor disk failures on our filers. It's worked pretty well in the past, but I've hit a snag today... > > Normally I can tell if a disk has failed in one of two ways: > 1) Check the SNMP "disks.failed" value, if !eq 1, we've got a problem. > 2) Check via SNMP, the total number of disks, then check the number of active disks, and add to it the number of spare disks. If total disks !eq to active plus spare disk, then there is a failure. Have you thought about using syslog and triggering on an event? As Jay's Email implied, we forward syslog (and auditlog) events to our loghosts and do misc. processing on them using Swatch, with auto-notification of "interesting" events. I don't know if the specific issue you had triggered a syslog event, but you might check your logs to see if something was there. Just a thought, alek

1 0

New better, quicker cheaper version of Bit Shark Coming Soon!
by Ken Belanger 26 Mar '02

26 Mar '02

Check out this website www.bitshark.com It will change IP on the Internet for ever! Ken

1 0

Re: SNMP Failure Detection
by Rune Bakken 26 Mar '02

26 Mar '02

Don Cunningham <donc(a)bedford.progress.com> writes: > This could be related to a similar situation we saw recently with a > failed disk. We don't use SNMP but the filer email notification facility. > Anyway, a disk failed and was subsequently removed by the OS and didn't > generate an email. So essentially the system didn't know that the disk > ever existed - similar to what you describe. I placed a call to NetApp > and they said this shouldn't ever happen(the OS automatically removing > a failed disk) and that it is a bug that will be fixed in a later release. > Check your system log for a disk failure message followed immediately > by a removal message for the failed disk. If it's there then you've > probably got the bug. Hmm, this seems to happen almost as often as not -- I am fairly aggressive on upgrading, due to obscure problems with SAN Backup, so I suspect that the bug has not yet been corrected. (I was told earlier this year that it was an unpublished bug) When it comes to the script mentioned earlier, I would suggest that the script somehow stores the value from the prevous run, and then report an error if the number decreases - that is at least what I am planning to do Real Soon Now(tm). >>>>>>>>>>>>.rune -- Rune Bakken Senior System Administrator Telenor Business Company (Nextra), IP-Services Ph: +47 22 77 03 93

1 0

RE: Spam
by Knight, Jason 26 Mar '02

26 Mar '02

> Otherwise, I will have to remove my address also. Me too, in case anyone is counting votes. -----Original Message----- From: Ed Marsh [mailto:edmarsh@ti.com] Sent: Tuesday, March 26, 2002 12:45 PM To: toasters(a)mathworks.com Subject: Re: Spam Ernest, Thanks for taking the time to look at the headers. I have received several spam messages today, so I have gone back to look at the source. All but one came through this list. I suggest that this list be restricted to only members in order to eliminate the spam. Otherwise, I will have to remove my address also. -Ed Bokkelkamp Ernst wrote: > I hate to say this, but I am considering leaving the list. I have been > silently in the background for a long time because of not having a > toy, I mean filer, to play with but it looks that the mailing list is > currently being abused. I already have one yahoo account blocked, but > it becomes a bit more difficult with the latest message from Jinjiang > Shengyi Shoes Co., Ltd. (Manufcturer). > > Bye > Ernie > > Here is the header: > > Received: from mail1.siemens.de ([139.23.33.14]) by > mchx07da.mchm.siemens.de with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) > id HM60G0V3; Tue, 26 Mar 2002 18:08:21 +0100 > Received: from goliath.siemens.de (goliath.siemens.de [192.35.17.28]) > by mail1.siemens.de (8.11.6/8.11.6) with ESMTP id g2QH8KW03511 > for <Ernst.Bokkelkamp(a)mch10.sbs.de>; Tue, 26 Mar 2002 18:08:20 > +0100 > (MET) > Received: from smtp2.mathworks.com (smtp.mathworks.com [144.212.95.12]) > by goliath.siemens.de (8.11.6/8.11.6) with ESMTP id g2QH8JR08728 > for <Ernst.Bokkelkamp(a)mch10.sbs.de>; Tue, 26 Mar 2002 18:08:19 +0100 > (MET) > Received: from mail.mathworks.com (turing.mathworks.com [144.212.95.101]) > by smtp2.mathworks.com (8.11.6/8.11.6) with ESMTP id g2QGoh104179; > Tue, 26 Mar 2002 11:50:43 -0500 (EST) > Received: (from majordom@localhost) > by mail.mathworks.com (8.11.2/8.11.2) id g2QGcvH26842; > Tue, 26 Mar 2002 11:38:57 -0500 (EST) > Received: from smtp2.mathworks.com (smtp.mathworks.com [144.212.95.12]) > by mail.mathworks.com (8.11.2/8.11.2) with ESMTP id g2QGct526827 > for <toasters(a)mathworks.com>; Tue, 26 Mar 2002 11:38:56 -0500 (EST) > Received: from smtp.mathworks.com (scanner.mathworks.com [144.212.95.161]) > by smtp2.mathworks.com (8.11.6/8.11.6) with ESMTP id g2QGcs101506 > for <toasters(a)mathworks.com>; Tue, 26 Mar 2002 11:38:54 -0500 (EST) > Received: from hadrian.uk.mathworks.com (ns.uk.mathworks.com > [192.168.72.250]) > by smtp.mathworks.com (8.11.6/8.11.6) with ESMTP id g2QGcqp01491 > for <toasters(a)mathworks.com>; Tue, 26 Mar 2002 11:38:52 -0500 (EST) > Received: from petter ([218.5.139.13]) > by hadrian.uk.mathworks.com (8.11.6/8.11.6) with SMTP id > g2QGcmP23867 > for <toasters(a)mathworks.com>; Tue, 26 Mar 2002 16:38:49 GMT > Message-Id: <200203261638.g2QGcmP23867(a)hadrian.uk.mathworks.com> > From: mike (Manufacturer of shoes) <5626512(a)963.net> > Reply-To: r-start(a)163.com > Subject: Jinjiang Shengyi Shoes Co., Ltd. (Manufcturer) > Date: Wed, 27 Mar 2002 00:20:45 +0800 > X-Mailer: 007 Direct Email Easy > Sender: owner-toasters(a)mathworks.com > Precedence: bulk

1 0

RE: Toasters - How can one forward auditlog events to syslog
by Perry, Jay 26 Mar '02

26 Mar '02

A while back, Alek asked if there was a way to forward auditlog events to a syslog. Since that time, we (Alek and I) have come up with a solution that is available on the NOW website as a Knowledgebase solution titled "How do I forward audit log messages to a syslog log host?" (solution ID ntapcs5526). For those that don't have NOW access, I am posting it here as well. Alek has had this in production for a while now (about a month), and as far as I know it is working out OK (although it required some new filtering, as the auditlog messages are much more verbose than the syslog messages - multiple lines and so forth). To set this up, you must modify the syslog.conf file on the loghost and the /etc/syslog.conf file on the filer or NetCache appliance that is the source of the messages. (For more information about the filer's syslog.conf file, see the respective Data ONTAP man page). Here are detailed steps: 1) On the log host, modify syslog.conf as follows: Add a line: local7.*[one_or_more_tabs][path_to_log_file] Basically, the auditlog messages will arrive as facility local7. 2) Make sure that any selectors of the form *.<level> get changed to *.<level>;local7.none. Otherwise those selectors will receive all of the audit log messages as well. 3) After completing your changes to syslog.conf on the log host, force the syslog daemon to reload its configuration file (on many systems this will involve sending a HUP signal to a process called syslogd). Refer to your log host's OS manuals for details on how this is done for your particular OS. 4) Modify the filer's /etc/syslog.conf file as follows: Add a line: cmdsaudit.auditlog[one_or_more_tabs]@[loghost_ip_or_name] The filer will automatically detect the change to syslog.conf and load it. This may take a couple of minutes though. You will know the change took place because a syslog message will appear that looks like: Wed Feb 20 21:58:52 GMT [syslogd:info]: syslogd: restarted It is worth noting that audit log messages are much more verbose than syslog messages. A typical syslog entry is a single line. A typical audit log entry looks like: date [method of access] :START:command incoming hostname date [method of access] :IN:command "input" command being sent to filer date [method of access] :OUT: output from command (may be multiple lines) date [method of access] :END:command Hope you find this useful, and thanks to Alek for helping out with this! Jay Perry jay.perry(a)netapp.com > -----Original Message----- > From: Alek O. Komarnitsky (N-CSC) [mailto:alek@ast.lmco.com] > Sent: Wednesday, February 20, 2002 8:08 AM > To: toasters(a)mathworks.com > Subject: Toasters - How can one forward auditlog events to syslog > > > I've searched the archives for the answer to this question > and searched > with Google, but have not found it ... yet! ;-) > > We use syslog quite a bit to log stuff remotely, but there are > certain events (such as root rsh activity) that are logged into > auditlog that do NOT show up in syslog - we are logging *.info. > > Is there a way to get those events also sent to syslog > so that we can use what is defined in /etc/syslog.conf to > forward those events to our loghosts? > > Thanx, > alek >

1 0

Re: SNMP Failure Detection
by Don Cunningham 26 Mar '02

26 Mar '02

This could be related to a similar situation we saw recently with a failed disk. We don't use SNMP but the filer email notification facility. Anyway, a disk failed and was subsequently removed by the OS and didn't generate an email. So essentially the system didn't know that the disk ever existed - similar to what you describe. I placed a call to NetApp and they said this shouldn't ever happen(the OS automatically removing a failed disk) and that it is a bug that will be fixed in a later release. Check your system log for a disk failure message followed immediately by a removal message for the failed disk. If it's there then you've probably got the bug. Regards, _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ Don Cunningham - UNIX SysAdmin _/ Progress Software Corp. _/ _/ don.cunningham(a)progress.com _/ 14 Oak Park _/ _/ (781)280-4252 _/ Bedford, MA 01730-1485 _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ "Wherever beer is brewed, all is well - whenever beer is _/ _/ drunk, life is good." -Czech proverb _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ > > Hello Toasters. > > I've been using a script to monitor disk failures on our filers. It's worked pretty well in the past, but I've hit a snag today... > > Normally I can tell if a disk has failed in one of two ways: > 1) Check the SNMP "disks.failed" value, if !eq 1, we've got a problem. > 2) Check via SNMP, the total number of disks, then check the number of active disks, and add to it the number of spare disks. If total disks !eq to active plus spare disk, then there is a failure. > > The second method is often needed for the failures that "slip through the cracks", and is sufficent. However today a disk failed and in doing so was removed from the TOTAL disk count, and not added as a failed disk, so in a case where I have 84 disks, I get the following output from my script: > > The global message is: "The system's global status is normal. " > Total disk count is: 83 > The Active Disk Count is: 82 > The Spare Disk Count is: 1 > The Failed Disk Count is: 0 > > > I've omitted the non-relevent output from my script, which does simple snmpget's from the Net-SNMP app. Anyway, three things went wrong here, > the global message doesn't reflect a failure. The total disk count was decremented when it should not have and the failed disk count is still eq to zero. > Now, because I know that all our filers should always have 2 spare disks I can rewrite my scripts to look for this, however I had previously written them in a very portable way, which hardcoding the number of spares to look for will degridate... > > Any ideas why this happens? I'm sure I'm not the only one who's seen this. > > Ben Rockwood > brockwood(a)homestead-inc.com

1 0

Jinjiang Shengyi Shoes Co., Ltd. (Manufcturer)
by mike 26 Mar '02

26 Mar '02

Dear Sir or Madam:, OUR COMPANY--Jinjiang R-Start Shoes Trading Co., Ltd.-- HAS SUCCESSFULLY INCOPORATED ONE SHOE'S FACTORY- SHENGYI SHOES CO.. NOW OUR ORIGINAL COMPANY'S NAME HAS BEEN RENAMED- JINJIANG SHENGYI SHOES CO., LTD. THAT'S MEANS, WE HAVE TRANSFORMED A PROFESSIONAL SHOE'S MANUFACTURER. SHOULD OUR TRANSFORMATION BRING INCONVINIENCE TO YOU, WISH TO FORGIVE IT. HOPE OUR NEW ROLE WOULD HELP TO FURTHER OUR BUSINESS RELATIONS IN THE FUTURE! ÎÒ¹«ËŸÔÃû"œúœÊÐÈðÐËÐ¬ÒµÓÐÏÞ¹«ËŸ"£¬ÏÖœøÐÐÖØ×é£¬³É¹ŠŒæ²¢"œúœÊÐÊ¢ÒÚÐ¬³§"£¬ÏÖÖØÐÂÃüÃûÎª"œúœÊÐÊ¢ÒÚÏðœºÐ¬ÒµÓÐÏÞ¹«ËŸ",ÕâÒâÎ¶×ÅÎÒ¹«ËŸÒÑ³É¹ŠµØŽÓ"Ã³Ò×¹«ËŸ"Ïò"ÖÆÔìÉÌ"×ª±ä£¬ÎÒÃÇµÄ×ª±äÈôžøÄúŽúÀŽ²»±ã£¬ŸŽÇëÔÁÂ£¡Ï£ÍûÎÒÃÇµÄžÄ±äÓÐÀûÓÚÏà»¥Ö®ŒäµÄœøÒ»²œºÏ×÷£¡ ÈôÓÐÈÎºÎÒÉÎÊ£¬ÇëÓëÎÒÃÇÁªÏµ£¡ ÉÌÆí£¡ Contact person£ºMS.SALLY WANG & MR. MIKE Jinjiang Shengyi Shoes Co., Ltd. (Manufcturer) œúœÊÐÊ¢ÒÚÏðœºÐ¬ÒµÓÐÏÞ¹«ËŸ Add.: Gaoxia Industry Avenue, Qingyang Town, Jinjiang City, Fujian Province, China µØÖ·£ºÖÐ¹úž£œšÊ¡œúœÊÐÇàÑôžßÏŒ¹€ÒµÇø TEL: 86-595- 5626511 5626512 FAX: 86-595- 5626513 Email: r-start(a)163.com http://footwears.ebigchina.com

1 0

ADV-get ya gamble on!
by Rocco 26 Mar '02

26 Mar '02

1 0

limit read and write block sizes
by Jim Harm 25 Mar '02

25 Mar '02

We have very bad read times when using default rsize/wsize. There was some discussion about using smaller values. Can someone summarize why and what size to use? I thought it was a router or switch bug that was to be fixed. -- }}}===============>> LLNL James E. Harm (Jim); jharm(a)llnl.gov System Administrator Compaq Clusters (925) 422-4018 Page: 423-7705x57152

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

toasters