Title: Message
Simon
 
Symantec did try their best, various logs and traces where submitted, NBU and OS. They presumed an OS related issue and was then informed to get in touch with SUN. This is when we decided to increase the swap. Clutching at straws I know but it seems to have resolved the issue.
 
Nothing has changed on the system that we are aware of and the machine has only been up for 67 days. Reason we increased the swap is because it had 4Gb less swap than the rest of our masters too.
 
A reboot would've more than likely resolved the problem, however this is not always an option due to large NDMP backups still running.
 
Regards
 
Dave


From: WEAVER, Simon [mailto:[EMAIL PROTECTED]
Sent: 21 August 2006 12:48
To: Clooney, David; [email protected]
Subject: RE: [Veritas-bu] Weird vmd scenario

Hello again Dave
Ok, well then.... I for one am puzzled!
 
Firstly (and importantly), why did Symantec not pick this up?
Second, why do you need to increase the swap? - Has something actually changed without you knowing?
Third, would a reboot have actually solved the problem?
 
Finally, how long has the box been up for ? Maybe a reboot would clear down the memory / swap and release it (similar to what Windows does!)

Regards

Simon Weaver
3rd Line Technical Support
Windows Domain Administrator

EADS Astrium Limited, B23AA IM (DCS)
Anchorage Road, Portsmouth, PO3 5PU

Email: [EMAIL PROTECTED]

-----Original Message-----
From: Clooney, David [mailto:[EMAIL PROTECTED]
Sent: 21 August 2006 12:44
To: WEAVER, Simon; [email protected]
Subject: RE: [Veritas-bu] Weird vmd scenario

Just doubled the swap and it seems to be working now.
 
Regards
 
Dave
 
 


From: WEAVER, Simon [mailto:[EMAIL PROTECTED]
Sent: 21 August 2006 12:42
To: Clooney, David; [email protected]
Subject: RE: [Veritas-bu] Weird vmd scenario

Dave
Well it sounds like a process or a process part of a tree may be down. How and why, I cannot explain, but it may be an idea to reboot and see if it comes back?
 
As you stated, no changes have been made; How long has the server been online without a reboot? It does sound like another Daemon or Service has either hung, or not properly started. In which case I would reboot first, before doing anything else.
 
Surprised Symantec did not ask to perform a reboot though
 
 

Regards

Simon Weaver
3rd Line Technical Support
Windows Domain Administrator

EADS Astrium Limited, B23AA IM (DCS)
Anchorage Road, Portsmouth, PO3 5PU

Email: [EMAIL PROTECTED]

-----Original Message-----
From: Clooney, David [mailto:[EMAIL PROTECTED]
Sent: 21 August 2006 12:35
To: WEAVER, Simon; [email protected]
Subject: RE: [Veritas-bu] Weird vmd scenario

Simon
 
NO reboot as of yet as we want to get to the bottom of it so we can avoid it happening again.
 
Yep all disk space is fine.
 
Just increased the swap too and still the problem occurs.
 
Regards
 
Dave


From: WEAVER, Simon [mailto:[EMAIL PROTECTED]
Sent: 21 August 2006 12:28
To: Clooney, David; [email protected]
Subject: RE: [Veritas-bu] Weird vmd scenario

DAve
Is there enough disk space where the images are stored? Or where the application is installed?
 
Im sort of assuming a reboot was and had been carried out ?
 
 

Regards

Simon Weaver
3rd Line Technical Support
Windows Domain Administrator

EADS Astrium Limited, B23AA IM (DCS)
Anchorage Road, Portsmouth, PO3 5PU

Email: [EMAIL PROTECTED]

-----Original Message-----
From: Clooney, David [mailto:[EMAIL PROTECTED]
Sent: 21 August 2006 12:22
To: [email protected]
Subject: [Veritas-bu] Weird vmd scenario

Hi All
 
Have a weird scenario going on, master/media  server Solaris 8
 
All of a sudden with no system changes whatsoever, we started getting error code 81's  (Media Manager volume daemon (vmd) is not active) early this morning Initially I thought that vmd had died however it was still chugging away although seemed to have a resource limit on it now.
 
We are in a situation where where have 5 NDMP jobs running, as soon a manually kick off failed jobs from the evening . another 10 would kick in and ten would fail with the above. the ten that kick in go through and complete.
 
Whilst the new ten jobs are running , if you run a vmoprcmd on the master/media you receive the following
 
hostname:/# vmoprcmd
volume daemon fork failed (85)
 
and the daemon log reflects the below.
 
09:54:04.892 [5688] <2> process_request: passing VxSS credentials to oprd
09:54:04.892 [5688] <2> start_oprd: starting oprd, sockfd = 6, nosig = yes
09:54:04.893 [5688] <16> start_oprd: fork() failed: Not enough space (12)
09:54:04.894 [5688] <16> listen_loop: abnormal exit: 85
 
It seems as though a resource issue somewhere along the line, Symantec have no ideas so I'm at a loose end ..
 
Has anyone come across this situation before.
 
Regards
 
Dave
 
 



Notice to recipient:
The information in this internet e-mail and any attachments is confidential and may be privileged. It is intended solely for the addressee. If you are not the intended addressee please notify the sender immediately by telephone. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful.


When addressed to external clients any opinions or advice contained in this internet e-mail are subject to the terms and conditions expressed in any applicable governing terms of business or client engagement letter issued by the pertinent Bank of America group entity.

If this email originates from the U.K. please note that Bank of America, N.A., London Branch and Banc of America Securities Limited are authorised and regulated by the Financial Services Authority.


This email is for the intended addressee only.
If you have received it in error then you must not use, retain, disseminate or otherwise deal with it.
Please notify the sender by return email.
The views of the author may not necessarily constitute the views of Astrium Limited.
Nothing in this email shall bind Astrium Limited in any contract or obligation.

Astrium Limited, Registered in England and Wales No. 2449259
Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England



Notice to recipient:
The information in this internet e-mail and any attachments is confidential and may be privileged. It is intended solely for the addressee. If you are not the intended addressee please notify the sender immediately by telephone. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful.


When addressed to external clients any opinions or advice contained in this internet e-mail are subject to the terms and conditions expressed in any applicable governing terms of business or client engagement letter issued by the pertinent Bank of America group entity.

If this email originates from the U.K. please note that Bank of America, N.A., London Branch and Banc of America Securities Limited are authorised and regulated by the Financial Services Authority.


This email is for the intended addressee only.
If you have received it in error then you must not use, retain, disseminate or otherwise deal with it.
Please notify the sender by return email.
The views of the author may not necessarily constitute the views of Astrium Limited.
Nothing in this email shall bind Astrium Limited in any contract or obligation.

Astrium Limited, Registered in England and Wales No. 2449259
Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England



Notice to recipient:
The information in this internet e-mail and any attachments is confidential and may be privileged. It is intended solely for the addressee. If you are not the intended addressee please notify the sender immediately by telephone. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful.


When addressed to external clients any opinions or advice contained in this internet e-mail are subject to the terms and conditions expressed in any applicable governing terms of business or client engagement letter issued by the pertinent Bank of America group entity.

If this email originates from the U.K. please note that Bank of America, N.A., London Branch and Banc of America Securities Limited are authorised and regulated by the Financial Services Authority.


This email is for the intended addressee only.
If you have received it in error then you must not use, retain, disseminate or otherwise deal with it.
Please notify the sender by return email.
The views of the author may not necessarily constitute the views of Astrium Limited.
Nothing in this email shall bind Astrium Limited in any contract or obligation.

Astrium Limited, Registered in England and Wales No. 2449259
Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England



Notice to recipient:
The information in this internet e-mail and any attachments is confidential and may be privileged. It is intended solely for the addressee. If you are not the intended addressee please notify the sender immediately by telephone. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful.


When addressed to external clients any opinions or advice contained in this internet e-mail are subject to the terms and conditions expressed in any applicable governing terms of business or client engagement letter issued by the pertinent Bank of America group entity.

If this email originates from the U.K. please note that Bank of America, N.A., London Branch and Banc of America Securities Limited are authorised and regulated by the Financial Services Authority.


_______________________________________________
Veritas-bu maillist  -  [email protected]
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Reply via email to