Re: [Veritas-bu] Strange Errors
Weve seen the activity monitor failure when one of the fibre cards in our HP-UX master server has gone away. On HP we can reset the fibre card with the server still on line using fcmsutil. Not sure if its possible in Linux or how to do it if so. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dustin D'Amour Sent: Friday, September 08, 2006 10:33 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Strange Errors Im getting following errors: Activity Monitor failed and must be restarted. To recover, first correct the problem described below and then select Refresh. Connection refused Ive tried stopping and restarting services and no go still get same error. I dont understand why Im all of the sudden getting the Connection refused part of the error message. Nothing has changed in the last week that I can see that would cause this. Also this problem is just not with the Activity monitor when I try to change the host properties I get: Library Initialization failed. Cobra communication error (195) (MM Status 195) Sometimes I do not get that error and Im able to open the host properties up but then I do not get anything in the dialog when I try clicking on one of the options such as Client Attributes or any of the other options. Using NetBackup 6.0 MP3 and running it on suse enterprise Linux 9.3 Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Strange Errors
Yeah, you should install ICS before installing NB 6.0x and do not use FQDN hostnames, use the short hostname only. Otherwise, you will have a whole sleuth of errors, like you are seeing. Justin. On Fri, 8 Sep 2006, Dustin D'Amour wrote: I'm getting following errors: Activity Monitor failed and must be restarted. To recover, first correct the problem described below and then select Refresh. Connection refused I've tried stopping and restarting services and no go still get same error. I don't understand why I'm all of the sudden getting the Connection refused part of the error message. Nothing has changed in the last week that I can see that would cause this. Also this problem is just not with the Activity monitor when I try to change the host properties I get: Library Initialization failed. Cobra communication error (195) (MM Status 195) Sometimes I do not get that error and I'm able to open the host properties up but then I do not get anything in the dialog when I try clicking on one of the options such as Client Attributes or any of the other options. Using NetBackup 6.0 MP3 and running it on suse enterprise Linux 9.3 Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com http://www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Strange Errors
We did install ICS before installing NB. So just use the hostname and not the domain name (ie hostname.domainname.zzz) ? Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Friday, September 08, 2006 8:56 AM To: Dustin D'Amour Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Strange Errors Yeah, you should install ICS before installing NB 6.0x and do not use FQDN hostnames, use the short hostname only. Otherwise, you will have a whole sleuth of errors, like you are seeing. Justin. On Fri, 8 Sep 2006, Dustin D'Amour wrote: I'm getting following errors: Activity Monitor failed and must be restarted. To recover, first correct the problem described below and then select Refresh. Connection refused I've tried stopping and restarting services and no go still get same error. I don't understand why I'm all of the sudden getting the Connection refused part of the error message. Nothing has changed in the last week that I can see that would cause this. Also this problem is just not with the Activity monitor when I try to change the host properties I get: Library Initialization failed. Cobra communication error (195) (MM Status 195) Sometimes I do not get that error and I'm able to open the host properties up but then I do not get anything in the dialog when I try clicking on one of the options such as Client Attributes or any of the other options. Using NetBackup 6.0 MP3 and running it on suse enterprise Linux 9.3 Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com http://www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Strange Errors
Yup, correct, that solved 95% of my problems with NetBackup 6.0. On Fri, 8 Sep 2006, Dustin D'Amour wrote: We did install ICS before installing NB. So just use the hostname and not the domain name (ie hostname.domainname.zzz) ? Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Friday, September 08, 2006 8:56 AM To: Dustin D'Amour Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Strange Errors Yeah, you should install ICS before installing NB 6.0x and do not use FQDN hostnames, use the short hostname only. Otherwise, you will have a whole sleuth of errors, like you are seeing. Justin. On Fri, 8 Sep 2006, Dustin D'Amour wrote: I'm getting following errors: Activity Monitor failed and must be restarted. To recover, first correct the problem described below and then select Refresh. Connection refused I've tried stopping and restarting services and no go still get same error. I don't understand why I'm all of the sudden getting the Connection refused part of the error message. Nothing has changed in the last week that I can see that would cause this. Also this problem is just not with the Activity monitor when I try to change the host properties I get: Library Initialization failed. Cobra communication error (195) (MM Status 195) Sometimes I do not get that error and I'm able to open the host properties up but then I do not get anything in the dialog when I try clicking on one of the options such as Client Attributes or any of the other options. Using NetBackup 6.0 MP3 and running it on suse enterprise Linux 9.3 Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com http://www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Strange Errors
Also, when I say just the hostname, I mean during the ICS installation. On Fri, 8 Sep 2006, Dustin D'Amour wrote: We did install ICS before installing NB. So just use the hostname and not the domain name (ie hostname.domainname.zzz) ? Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Friday, September 08, 2006 8:56 AM To: Dustin D'Amour Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Strange Errors Yeah, you should install ICS before installing NB 6.0x and do not use FQDN hostnames, use the short hostname only. Otherwise, you will have a whole sleuth of errors, like you are seeing. Justin. On Fri, 8 Sep 2006, Dustin D'Amour wrote: I'm getting following errors: Activity Monitor failed and must be restarted. To recover, first correct the problem described below and then select Refresh. Connection refused I've tried stopping and restarting services and no go still get same error. I don't understand why I'm all of the sudden getting the Connection refused part of the error message. Nothing has changed in the last week that I can see that would cause this. Also this problem is just not with the Activity monitor when I try to change the host properties I get: Library Initialization failed. Cobra communication error (195) (MM Status 195) Sometimes I do not get that error and I'm able to open the host properties up but then I do not get anything in the dialog when I try clicking on one of the options such as Client Attributes or any of the other options. Using NetBackup 6.0 MP3 and running it on suse enterprise Linux 9.3 Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com http://www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Strange Errors
Is this when the Master and Media are separate as I should have mentioned we have a single master/ media server, the fibre cards are alright I believe as the IBM tool is not reporting any errors on either of the HBAs. Correction the following error has a typo: Library Initialization failed. Cobra communication error (195) (MM Status 195 It should be Library Initialization failed.Corba communication error (195) (MM Status 195 Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare From: Jeff Lightner [mailto:[EMAIL PROTECTED] Sent: Friday, September 08, 2006 9:06 AM To: Dustin D'Amour; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Strange Errors Weve seen the activity monitor failure when one of the fibre cards in our HP-UX master server has gone away. On HP we can reset the fibre card with the server still on line using fcmsutil. Not sure if its possible in Linux or how to do it if so. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dustin D'Amour Sent: Friday, September 08, 2006 10:33 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Strange Errors Im getting following errors: Activity Monitor failed and must be restarted. To recover, first correct the problem described below and then select Refresh. Connection refused Ive tried stopping and restarting services and no go still get same error. I dont understand why Im all of the sudden getting the Connection refused part of the error message. Nothing has changed in the last week that I can see that would cause this. Also this problem is just not with the Activity monitor when I try to change the host properties I get: Library Initialization failed. Cobra communication error (195) (MM Status 195) Sometimes I do not get that error and Im able to open the host properties up but then I do not get anything in the dialog when I try clicking on one of the options such as Client Attributes or any of the other options. Using NetBackup 6.0 MP3 and running it on suse enterprise Linux 9.3 Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Strange Errors
Anyway to change the hostname after the install, we have had this thing up for 3 months now and this is the first time it has done this. The only thing that has changed is the IP address but that was done about 3 weeks ago and we never had a problem until Tuesday of the current week. Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Friday, September 08, 2006 9:16 AM To: Dustin D'Amour Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Strange Errors Also, when I say just the hostname, I mean during the ICS installation. On Fri, 8 Sep 2006, Dustin D'Amour wrote: We did install ICS before installing NB. So just use the hostname and not the domain name (ie hostname.domainname.zzz) ? Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Friday, September 08, 2006 8:56 AM To: Dustin D'Amour Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Strange Errors Yeah, you should install ICS before installing NB 6.0x and do not use FQDN hostnames, use the short hostname only. Otherwise, you will have a whole sleuth of errors, like you are seeing. Justin. On Fri, 8 Sep 2006, Dustin D'Amour wrote: I'm getting following errors: Activity Monitor failed and must be restarted. To recover, first correct the problem described below and then select Refresh. Connection refused I've tried stopping and restarting services and no go still get same error. I don't understand why I'm all of the sudden getting the Connection refused part of the error message. Nothing has changed in the last week that I can see that would cause this. Also this problem is just not with the Activity monitor when I try to change the host properties I get: Library Initialization failed. Cobra communication error (195) (MM Status 195) Sometimes I do not get that error and I'm able to open the host properties up but then I do not get anything in the dialog when I try clicking on one of the options such as Client Attributes or any of the other options. Using NetBackup 6.0 MP3 and running it on suse enterprise Linux 9.3 Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com http://www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Strange Errors
In the cases I was speaking of it was when the Java GUI on my desktop was pointed to the activity monitor of the master. We do have media servers as well but they werent the issue. Ive not seen the robot communication failure youre seeing. Were using an HP OEMed STK and its connections are SCSI via fibre bridges including the robotic control. From: Dustin D'Amour [mailto:[EMAIL PROTECTED] Sent: Friday, September 08, 2006 11:22 AM To: Jeff Lightner; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Strange Errors Is this when the Master and Media are separate as I should have mentioned we have a single master/ media server, the fibre cards are alright I believe as the IBM tool is not reporting any errors on either of the HBAs. Correction the following error has a typo: Library Initialization failed. Cobra communication error (195) (MM Status 195 It should be Library Initialization failed.Corba communication error (195) (MM Status 195 Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare From: Jeff Lightner [mailto:[EMAIL PROTECTED] Sent: Friday, September 08, 2006 9:06 AM To: Dustin D'Amour; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Strange Errors Weve seen the activity monitor failure when one of the fibre cards in our HP-UX master server has gone away. On HP we can reset the fibre card with the server still on line using fcmsutil. Not sure if its possible in Linux or how to do it if so. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dustin D'Amour Sent: Friday, September 08, 2006 10:33 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Strange Errors Im getting following errors: Activity Monitor failed and must be restarted. To recover, first correct the problem described below and then select Refresh. Connection refused Ive tried stopping and restarting services and no go still get same error. I dont understand why Im all of the sudden getting the Connection refused part of the error message. Nothing has changed in the last week that I can see that would cause this. Also this problem is just not with the Activity monitor when I try to change the host properties I get: Library Initialization failed. Cobra communication error (195) (MM Status 195) Sometimes I do not get that error and Im able to open the host properties up but then I do not get anything in the dialog when I try clicking on one of the options such as Client Attributes or any of the other options. Using NetBackup 6.0 MP3 and running it on suse enterprise Linux 9.3 Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Strange Errors
Ah, ok, there is another thing too.. If you run cold backups it can also cause weird problems like that. The netbackup engineer from symantec told me its only 70% fixed in MP3, if you run cold backups it can cause severe problems. Justin. On Fri, 8 Sep 2006, Dustin D'Amour wrote: Anyway to change the hostname after the install, we have had this thing up for 3 months now and this is the first time it has done this. The only thing that has changed is the IP address but that was done about 3 weeks ago and we never had a problem until Tuesday of the current week. Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Friday, September 08, 2006 9:16 AM To: Dustin D'Amour Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Strange Errors Also, when I say just the hostname, I mean during the ICS installation. On Fri, 8 Sep 2006, Dustin D'Amour wrote: We did install ICS before installing NB. So just use the hostname and not the domain name (ie hostname.domainname.zzz) ? Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Friday, September 08, 2006 8:56 AM To: Dustin D'Amour Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Strange Errors Yeah, you should install ICS before installing NB 6.0x and do not use FQDN hostnames, use the short hostname only. Otherwise, you will have a whole sleuth of errors, like you are seeing. Justin. On Fri, 8 Sep 2006, Dustin D'Amour wrote: I'm getting following errors: Activity Monitor failed and must be restarted. To recover, first correct the problem described below and then select Refresh. Connection refused I've tried stopping and restarting services and no go still get same error. I don't understand why I'm all of the sudden getting the Connection refused part of the error message. Nothing has changed in the last week that I can see that would cause this. Also this problem is just not with the Activity monitor when I try to change the host properties I get: Library Initialization failed. Cobra communication error (195) (MM Status 195) Sometimes I do not get that error and I'm able to open the host properties up but then I do not get anything in the dialog when I try clicking on one of the options such as Client Attributes or any of the other options. Using NetBackup 6.0 MP3 and running it on suse enterprise Linux 9.3 Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com http://www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Strange Errors
Also I noticed that the services are stopping themselves, I'll restart them and a few minutes later they are stopped again. Anybody have this problem with the other 'strange errors' issue? Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Friday, September 08, 2006 10:11 AM To: Dustin D'Amour Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Strange Errors Ah, ok, there is another thing too.. If you run cold backups it can also cause weird problems like that. The netbackup engineer from symantec told me its only 70% fixed in MP3, if you run cold backups it can cause severe problems. Justin. On Fri, 8 Sep 2006, Dustin D'Amour wrote: Anyway to change the hostname after the install, we have had this thing up for 3 months now and this is the first time it has done this. The only thing that has changed is the IP address but that was done about 3 weeks ago and we never had a problem until Tuesday of the current week. Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Friday, September 08, 2006 9:16 AM To: Dustin D'Amour Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Strange Errors Also, when I say just the hostname, I mean during the ICS installation. On Fri, 8 Sep 2006, Dustin D'Amour wrote: We did install ICS before installing NB. So just use the hostname and not the domain name (ie hostname.domainname.zzz) ? Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Friday, September 08, 2006 8:56 AM To: Dustin D'Amour Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Strange Errors Yeah, you should install ICS before installing NB 6.0x and do not use FQDN hostnames, use the short hostname only. Otherwise, you will have a whole sleuth of errors, like you are seeing. Justin. On Fri, 8 Sep 2006, Dustin D'Amour wrote: I'm getting following errors: Activity Monitor failed and must be restarted. To recover, first correct the problem described below and then select Refresh. Connection refused I've tried stopping and restarting services and no go still get same error. I don't understand why I'm all of the sudden getting the Connection refused part of the error message. Nothing has changed in the last week that I can see that would cause this. Also this problem is just not with the Activity monitor when I try to change the host properties I get: Library Initialization failed. Cobra communication error (195) (MM Status 195) Sometimes I do not get that error and I'm able to open the host properties up but then I do not get anything in the dialog when I try clicking on one of the options such as Client Attributes or any of the other options. Using NetBackup 6.0 MP3 and running it on suse enterprise Linux 9.3 Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com http://www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Strange Errors
Depends what services you are talking about, I will take a guess, nbemm? On Fri, 8 Sep 2006, Dustin D'Amour wrote: Also I noticed that the services are stopping themselves, I'll restart them and a few minutes later they are stopped again. Anybody have this problem with the other 'strange errors' issue? Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Friday, September 08, 2006 10:11 AM To: Dustin D'Amour Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Strange Errors Ah, ok, there is another thing too.. If you run cold backups it can also cause weird problems like that. The netbackup engineer from symantec told me its only 70% fixed in MP3, if you run cold backups it can cause severe problems. Justin. On Fri, 8 Sep 2006, Dustin D'Amour wrote: Anyway to change the hostname after the install, we have had this thing up for 3 months now and this is the first time it has done this. The only thing that has changed is the IP address but that was done about 3 weeks ago and we never had a problem until Tuesday of the current week. Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Friday, September 08, 2006 9:16 AM To: Dustin D'Amour Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Strange Errors Also, when I say just the hostname, I mean during the ICS installation. On Fri, 8 Sep 2006, Dustin D'Amour wrote: We did install ICS before installing NB. So just use the hostname and not the domain name (ie hostname.domainname.zzz) ? Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Friday, September 08, 2006 8:56 AM To: Dustin D'Amour Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Strange Errors Yeah, you should install ICS before installing NB 6.0x and do not use FQDN hostnames, use the short hostname only. Otherwise, you will have a whole sleuth of errors, like you are seeing. Justin. On Fri, 8 Sep 2006, Dustin D'Amour wrote: I'm getting following errors: Activity Monitor failed and must be restarted. To recover, first correct the problem described below and then select Refresh. Connection refused I've tried stopping and restarting services and no go still get same error. I don't understand why I'm all of the sudden getting the Connection refused part of the error message. Nothing has changed in the last week that I can see that would cause this. Also this problem is just not with the Activity monitor when I try to change the host properties I get: Library Initialization failed. Cobra communication error (195) (MM Status 195) Sometimes I do not get that error and I'm able to open the host properties up but then I do not get anything in the dialog when I try clicking on one of the options such as Client Attributes or any of the other options. Using NetBackup 6.0 MP3 and running it on suse enterprise Linux 9.3 Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com http://www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Strange Errors
Hm, ouch. Like I said though, the naming scheme that was chosen during the initial install is what solved the majority of my issues, the second was the cold catalog backups. Justin. On Fri, 8 Sep 2006, Dustin D'Amour wrote: Nbpem is the most common, bprd, nbrb, nbvault, and bmpd are the trouble makers. Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Friday, September 08, 2006 11:43 AM To: Dustin D'Amour Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Strange Errors Depends what services you are talking about, I will take a guess, nbemm? On Fri, 8 Sep 2006, Dustin D'Amour wrote: Also I noticed that the services are stopping themselves, I'll restart them and a few minutes later they are stopped again. Anybody have this problem with the other 'strange errors' issue? Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Friday, September 08, 2006 10:11 AM To: Dustin D'Amour Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Strange Errors Ah, ok, there is another thing too.. If you run cold backups it can also cause weird problems like that. The netbackup engineer from symantec told me its only 70% fixed in MP3, if you run cold backups it can cause severe problems. Justin. On Fri, 8 Sep 2006, Dustin D'Amour wrote: Anyway to change the hostname after the install, we have had this thing up for 3 months now and this is the first time it has done this. The only thing that has changed is the IP address but that was done about 3 weeks ago and we never had a problem until Tuesday of the current week. Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Friday, September 08, 2006 9:16 AM To: Dustin D'Amour Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Strange Errors Also, when I say just the hostname, I mean during the ICS installation. On Fri, 8 Sep 2006, Dustin D'Amour wrote: We did install ICS before installing NB. So just use the hostname and not the domain name (ie hostname.domainname.zzz) ? Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Friday, September 08, 2006 8:56 AM To: Dustin D'Amour Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Strange Errors Yeah, you should install ICS before installing NB 6.0x and do not use FQDN hostnames, use the short hostname only. Otherwise, you will have a whole sleuth of errors, like you are seeing. Justin. On Fri, 8 Sep 2006, Dustin D'Amour wrote: I'm getting following errors: Activity Monitor failed and must be restarted. To recover, first correct the problem described below and then select Refresh. Connection refused I've tried stopping and restarting services and no go still get same error. I don't understand why I'm all of the sudden getting the Connection refused part of the error message. Nothing has changed in the last week that I can see that would cause this. Also this problem is just not with the Activity monitor when I try to change the host properties I get: Library Initialization failed. Cobra communication error (195) (MM Status 195) Sometimes I do not get that error and I'm able to open the host properties up but then I do not get anything in the dialog when I try clicking on one of the options such as Client Attributes or any of the other options. Using
Re: [Veritas-bu] Strange Errors
Nbpem is the most common, bprd, nbrb, nbvault, and bmpd are the trouble makers. Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Friday, September 08, 2006 11:43 AM To: Dustin D'Amour Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Strange Errors Depends what services you are talking about, I will take a guess, nbemm? On Fri, 8 Sep 2006, Dustin D'Amour wrote: Also I noticed that the services are stopping themselves, I'll restart them and a few minutes later they are stopped again. Anybody have this problem with the other 'strange errors' issue? Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Friday, September 08, 2006 10:11 AM To: Dustin D'Amour Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Strange Errors Ah, ok, there is another thing too.. If you run cold backups it can also cause weird problems like that. The netbackup engineer from symantec told me its only 70% fixed in MP3, if you run cold backups it can cause severe problems. Justin. On Fri, 8 Sep 2006, Dustin D'Amour wrote: Anyway to change the hostname after the install, we have had this thing up for 3 months now and this is the first time it has done this. The only thing that has changed is the IP address but that was done about 3 weeks ago and we never had a problem until Tuesday of the current week. Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Friday, September 08, 2006 9:16 AM To: Dustin D'Amour Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Strange Errors Also, when I say just the hostname, I mean during the ICS installation. On Fri, 8 Sep 2006, Dustin D'Amour wrote: We did install ICS before installing NB. So just use the hostname and not the domain name (ie hostname.domainname.zzz) ? Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf that nerfed the fix for the update of the patch that broke the fix that was fixed. --Unkown ...Be not afraid of greatness: some are born great, some achieve greatness, and some have greatness thrust upon them. --William Shakespeare -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Friday, September 08, 2006 8:56 AM To: Dustin D'Amour Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Strange Errors Yeah, you should install ICS before installing NB 6.0x and do not use FQDN hostnames, use the short hostname only. Otherwise, you will have a whole sleuth of errors, like you are seeing. Justin. On Fri, 8 Sep 2006, Dustin D'Amour wrote: I'm getting following errors: Activity Monitor failed and must be restarted. To recover, first correct the problem described below and then select Refresh. Connection refused I've tried stopping and restarting services and no go still get same error. I don't understand why I'm all of the sudden getting the Connection refused part of the error message. Nothing has changed in the last week that I can see that would cause this. Also this problem is just not with the Activity monitor when I try to change the host properties I get: Library Initialization failed. Cobra communication error (195) (MM Status 195) Sometimes I do not get that error and I'm able to open the host properties up but then I do not get anything in the dialog when I try clicking on one of the options such as Client Attributes or any of the other options. Using NetBackup 6.0 MP3 and running it on suse enterprise Linux 9.3 Dustin D'Amour Coyote Solutions Group 505.742.0066 www.coyotesolutions.com http://www.coyotesolutions.com Relax...it's just an update for the patch to fix the nerf
RE: [Veritas-bu] Strange errors in netapp messages log after upgrade of nbu from 5.1 to 60MP2 -- diag gear
I'm not sure about the sniffer issue, but I do know Data OnTap v7.1 includes updated support for NBU 6.0 (at least NBU's support of snapvaults). Are you running the latest code on the Nearstores? Check out http://now.netapp.com/NOW/knowledge/docs/ontap/rel71/html/ontap/rnote/fe atures.shtml HTH - Hadrian -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, May 16, 2006 2:40 AM To: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Strange errors in netapp messages log after upgrade of nbu from 5.1 to 60MP2 -- diag gear Well NetBackup 6 includes support for sharing drives between NDMP and non-NDMP use, so must include logic that probably was not there before. Check the version of ONTAP is supported with your version of NetBackup. You can turn on detailed NDMP tracing on the NetBackup for NDMP Server - where the option is installed. It gets very bulky but can trace every NDMP exchange. If your clocks are synch'd you may be able to see what is happening. The IBM LTO-2 drive does support the WRITE ATTRIBUTE command, according to the manual. It writes to the Medium Auxilliary Memory i.e. the LTO-CM cartridge memory. I guess it's possible that NetBackup 6 now has support for attempting to write to this, as one field available for use is Backup Date. Maybe this is not working properly - without the detail of what was being written you cannot see if it is being done correctly. William D L Brown George Drew [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 15-May-2006 19:07 To Len Boyle [EMAIL PROTECTED] cc veritas-bu@mailman.eng.auburn.edu Subject Re: [Veritas-bu] Strange errors in netapp messages log after upgrade of nbu from 5.1 to 60MP2 -- diag gear Len, This message means that you have some device in the path to your tape drive that isn't happy with 16-byte CDBs (some scsi-3 commands). This one in particular is the scsi-3 WRITE ATTRIBUTE command. (Reference: http://t10.org/ftp/t10/drafts/spc4/spc4r04.pdf) George On Sat, 13 May 2006, Len Boyle wrote: Good Day, We upgraded a netbackup master running on solaris 9 from 5.1mp3 to 60MP2. This master runs ndmp backups on 6 R200's with fibre direct attached IBM LTO-2 tape drives. After the netbackup upgrade, with no changes with the tape drives, tape library or netapps we started to see the following messages in the /etc/messages file on the netapp. We are being told by netapp and symantec that this is a problem with scsi commands, but they report that they can not tell us what the offending scsi commands are, unless we hook up a sniffer. So my question to this group, is Any hints on what one should use to act as a sniffer for this scsi connection? That is what company makes good sniffers, and what are the different features one should look for? Thanks for any info you guys can throw this way. Fri May 12 07:54:31 EDT [scsi.cmd.contingentAllegiance:error]: Device 3a.51: Contingent allegiance: cdb 0x8d. Fri May 12 08:00:01 EDT [kern.uptime.filer:info]: 8:00am up 57 days, 18:59 427592 NFS ops, 3947850238 CIFS ops, 9 HTTP ops, 0 DAFS ops, 0 FCP ops, 0 iSCSI ops Fri May 12 08:03:16 EDT [scsi.cmd.contingentAllegiance:error]: Device 3b.52: Contingent allegiance: cdb 0x8d. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Strange errors in netapp messages log after upgrade of nbu from 5.1 to 60MP2 -- diag gear
Len, This message means that you have some device in the path to your tape drive that isn't happy with 16-byte CDBs (some scsi-3 commands). This one in particular is the scsi-3 WRITE ATTRIBUTE command. (Reference: http://t10.org/ftp/t10/drafts/spc4/spc4r04.pdf) George On Sat, 13 May 2006, Len Boyle wrote: Good Day, We upgraded a netbackup master running on solaris 9 from 5.1mp3 to 60MP2. This master runs ndmp backups on 6 R200's with fibre direct attached IBM LTO-2 tape drives. After the netbackup upgrade, with no changes with the tape drives, tape library or netapps we started to see the following messages in the /etc/messages file on the netapp. We are being told by netapp and symantec that this is a problem with scsi commands, but they report that they can not tell us what the offending scsi commands are, unless we hook up a sniffer. So my question to this group, is Any hints on what one should use to act as a sniffer for this scsi connection? That is what company makes good sniffers, and what are the different features one should look for? Thanks for any info you guys can throw this way. Fri May 12 07:54:31 EDT [scsi.cmd.contingentAllegiance:error]: Device 3a.51: Contingent allegiance: cdb 0x8d. Fri May 12 08:00:01 EDT [kern.uptime.filer:info]: 8:00am up 57 days, 18:59 427592 NFS ops, 3947850238 CIFS ops, 9 HTTP ops, 0 DAFS ops, 0 FCP ops, 0 iSCSI ops Fri May 12 08:03:16 EDT [scsi.cmd.contingentAllegiance:error]: Device 3b.52: Contingent allegiance: cdb 0x8d. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
