JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for LCG-ROLLOUT Archives


LCG-ROLLOUT Archives

LCG-ROLLOUT Archives


LCG-ROLLOUT@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

LCG-ROLLOUT Home

LCG-ROLLOUT Home

LCG-ROLLOUT  April 2007

LCG-ROLLOUT April 2007

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: crashing network server

From:

Ronald Starink <[log in to unmask]>

Reply-To:

LHC Computer Grid - Rollout <[log in to unmask]>

Date:

Fri, 20 Apr 2007 15:16:47 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (156 lines)

Hi Maxim,

I agree that it makes sense to check potential physical causes for
problems and not just rule them out. Nevertheless, in this case I think
it is highly unlikely that only 3 RBs start giving trouble at the same
day and none of the ~300 hosts in the same room.

Below are the answers to your questions.

>>> 1. Can you please tell where are these servers physically located:
>>> Do they share the same room ?
Yes.

>>> 2. Do they share the same power line ?
No.

>>> 3. what is the power protection are you using ?
I have no idea.

>>> 4. Do they share storage ?
No.

>>> 5. What is the average temperature in the place they're located at ?
~22 Celsius.

>>> 6. what's the amount of memory and swap on each of them, what's their
>>> loadavg, what does vmstat show ?
                RAM     swap avail/used    load avg.
bosheks:        3 GB    1 GB / 0 GB        0.48 0.60 0.62
boswachter:     5 GB    5 GB / 0 GB        0.27 0.30 0.28
boszwijn:       8 GB    4 GB / 0 GB        0.33 0.26 0.20

>>> 7. which linux kernel/distribution are you using ? ( sorry for not
>>> investigating this via gstat app )
All 3: CentOS 3.7, with kernel 2.4.21-47.ELsmp


Cheers,
Ronald




Maxim Kovgan wrote:
> NO, I am not confused.
> some memory failures are caused by power, those mem fails are causing
> misc ( incl. SIGSEGV ) stuff,
> so... the 1st thing is to see the hardware side is ok.
> then, low level software, and only then I'd look further...
> many places to look for.
> 
> And since we still have no clear understanding of what is causing the
> daemons to segfault... we better try any new ideas, ( assuming you've
> googled yourself to the point you know it's not a known issue, and I
> think you're a serious person who does this... )
> 
> And, these ideas don't cost much.
> 
> Do we agree on this ?
> 
> I mean, when something _wierd_ and time sporadic is happening, I always
> start diagnosing from the lowest level possible: power, etc.
> From the data presented I have not negated this possibility.
> 
> Best regards,
> 
> Max.
> 
> 
> Jeff Templon wrote:
>> Hi Maxim,
>>
>> I think you're following a false lead.  The "network server" is a
>> piece of software, one of the daemon pieces of the LCG-RB.  It's not a
>> "network server machine" like you are probably thinking.   The LCG-RB
>> machine as a piece of hardware works fine, the daemon, called "network
>> server", on this machine, is crashing.
>>
>>                     JT
>>
>> Maxim Kovgan wrote:
>>> 1. Can you please tell where are these servers physically located:
>>> Do they share the same room ?
>>> 2. Do they share the same power line ?
>>> 3. what is the power protection are you using ?
>>> 4. Do they share storage ?
>>> 5. What is the average temperature in the place they're located at ?
>>> 6. what's the amount of memory and swap on each of them, what's their
>>> loadavg, what does vmstat show ?
>>> 7. which linux kernel/distribution are you using ? ( sorry for not
>>> investigating this via gstat app )
>>>
>>> Regards.
>>>
>>>
>>>
>>> Ronald Starink wrote:
>>>> Hi all,
>>>>
>>>> Since a few days, our resource brokers suffer from frequently crashing
>>>> network servers. The crashes occur when a new connection from the UI is
>>>> set up, either via an edg-job-submit or an edg-job-get-output. They do
>>>> not occur on every connection and are not related to connections by a
>>>> specific user or from a specific user interface.
>>>>
>>>> The following fragment from /var/edgwl/networkserver/log/events.log
>>>> shows a crash on 17:39:04 when a new connection came in.
>>>>
>>>> 19 Apr, 17:38:16 [7] -I- "CFSI::doPurge": Preparing to Purge.
>>>> 19 Apr, 17:38:16 [7] -W- "CFSI::doPurge": JobId object for purging
>>>> created: https://bosheks.nikhef.nl:9000/1tRxIPpaaNiR4Z6vxFIZEw
>>>> 19 Apr, 17:38:16 [7] -F- "CFSI::LogPurgeJobN": Logging Purge Request.
>>>> 19 Apr, 17:38:18 [7] -I- "Manager::run": Command done
>>>> 19 Apr, 17:39:04 [9] -I- "Manager::run": Connection from: erf.nikhef.nl
>>>> 19 Apr, 17:40:11 [0] -F- "   NS::main":
>>>> --------------------------------------
>>>> 19 Apr, 17:40:11 [0] -F- "   NS::main": Starting Network Server...
>>>> 19 Apr, 17:40:11 [0] -F- "  NSR::drop": Already running in an
>>>> unprivileged account...
>>>> [.....]
>>>> 19 Apr, 17:40:11 [0] -F- "   NS::main":
>>>> --------------------------------------
>>>> 19 Apr, 17:40:21 [2] -I- "Manager::run": Connection from: erf.nikhef.nl
>>>> 19 Apr, 17:40:22 [2] -I- "Manager::run": Authentication with host
>>>> erf.nikhef.nl succeeded for *************************
>>>>
>>>> Tracing the edg-wl-ns daemon indicates that there is a segmentation
>>>> violation:
>>>>
>>>> [root@boszwijn root]# strace -Ff -p 3999
>>>> Process 3999 attached - interrupt to quit
>>>> futex(0x9c6fe9c, FUTEX_WAIT, 1, NULL)   = -1 EINTR (Interrupted
>>>> system call)
>>>> +++ killed by SIGSEGV +++
>>>>
>>>>
>>>> This problem occurs since Tuesday on our three resource brokers that
>>>> are
>>>> available for production: bosheks.nikhef.nl, boswachter.nikhef.nl and
>>>> boszwijn.nikhef.nl. The latter is a new machine that was first
>>>> installed
>>>> last Tuesday. The three hosts combine the resource broker with a BDII.
>>>>
>>>> We did not perform middleware upgrades on Tuesday. The package versions
>>>> installed on the RB correspond to those specified in the meta package
>>>> lcg-RB-3.0.10-1.
>>>>
>>>> The fact that only RBs have this problem probably indicates to "some"
>>>> problem in the configuration on our site, but we have run out of ideas
>>>> about the possible cause.
>>>>
>>>> Any help is much appreciated.
>>>>
>>>> Thanks,
>>>> Ronald

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

March 2020
February 2020
January 2020
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
February 2018
January 2018
November 2017
October 2017
September 2017
July 2017
June 2017
May 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
2006
2005
2004
2003


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager