Re: Please help interpret this error message
On 2014-06-24, at 6:48, Joseph Areeda newsre...@areeda.com wrote: I have a C++ program that runs on multiple systems. It uses a proprietary network protocol contained in a shared object. On one of the systems I get this error regularly but not often enough to use a debugger: NDS library error: Resource temporarily unavailable It only seems to happen on one system, my workstation. I've reinstalled the library. I have Googled my heart out and while I see the error reported in other packages I haven't found anything that explains what it means. NDS is the name of the service (Network Data Service). The only hints I've gotten suggest it might mean the network interface itself might be involved but nothing else seems to have a problem. If it were a bug in the library I'd expect to see it on the other systems which are in production. Any clues as to what it means or where to read up on it would be greatly appreciated. Some library call returned EAGAIN. The prime suspect is usually fork(2), but in the case of a network library, I'd look at send(2) first. Hth Stephan -- Stephan Wiesand DESY - DV - Platanenallee 6 15738 Zeuthen, Germany
RE: yum segfaulting
I had similar problem before, someone changed the stock system libz.so with a newer version libz.so, which yum didn't like it! Zhi-Wei Lu IET-CR-Network Operations Center University of California, Davis (530) 752-0155 -Original Message- From: owner-scientific-linux-us...@listserv.fnal.gov [mailto:owner-scientific-linux-us...@listserv.fnal.gov] On Behalf Of Werf, C.G. van der (Carel) Sent: Tuesday, June 24, 2014 12:23 AM To: 'scientific-linux-users@fnal.gov' Subject: yum segfaulting Hi, I have two identical SL 5.3 fileservers, who function as a DRBD-pair. One of them was recently completely replaced with identical hardware, so I had to image the old one, and install OS-image on new server. But now, when I run yum on the new server, it returns a segmentation fault (even a simple: # yum --help). Googling this, a lot of pages hint for a memory error. But, running a memtest did not show any error. So far, only yum returns the segmentation fault. Does anyone have any clue for this ? Regards, Carel van der Werf
Re: Please help interpret this error message
Thanks Stephan, On 06/24/2014 01:07 AM, Stephan Wiesand wrote: On 2014-06-24, at 6:48, Joseph Areeda newsre...@areeda.com wrote: I have a C++ program that runs on multiple systems. It uses a proprietary network protocol contained in a shared object. On one of the systems I get this error regularly but not often enough to use a debugger: NDS library error: Resource temporarily unavailable It only seems to happen on one system, my workstation. I've reinstalled the library. I have Googled my heart out and while I see the error reported in other packages I haven't found anything that explains what it means. NDS is the name of the service (Network Data Service). The only hints I've gotten suggest it might mean the network interface itself might be involved but nothing else seems to have a problem. If it were a bug in the library I'd expect to see it on the other systems which are in production. Any clues as to what it means or where to read up on it would be greatly appreciated. Some library call returned EAGAIN. The prime suspect is usually fork(2), but in the case of a network library, I'd look at send(2) first. Hth Stephan
Re: Please help interpret this error message
On Tuesday 24 June 2014 8:54 am, Joseph Areeda wrote: Thanks Stephan, On 06/24/2014 01:07 AM, Stephan Wiesand wrote: On 2014-06-24, at 6:48, Joseph Areeda newsre...@areeda.com wrote: I have a C++ program that runs on multiple systems. It uses a proprietary network protocol contained in a shared object. On one of the systems I get this error regularly but not often enough to use a debugger: NDS library error: Resource temporarily unavailable It only seems to happen on one system, my workstation. I've reinstalled the library. I have Googled my heart out and while I see the error reported in other packages I haven't found anything that explains what it means. NDS is the name of the service (Network Data Service). The only hints I've gotten suggest it might mean the network interface itself might be involved but nothing else seems to have a problem. If it were a bug in the library I'd expect to see it on the other systems which are in production. Any clues as to what it means or where to read up on it would be greatly appreciated. Some library call returned EAGAIN. The prime suspect is usually fork(2), but in the case of a network library, I'd look at send(2) first. Hth Stephan Do you have a managed switch behind a router in system? Maybe a 1G Hz router feeding a 100K Hz router? Most newer boxes have a 1GHz NIC (built in) in them. We have a managed 1 G Hz switch that is managed and we have a Motorola router that is less than 1 GHz with factory default set up. The switch shows up on our network as a device! I sort of wondered about it as a cause of our stack up (slowness) sometimes in the afternoon. I have never seen much discussion about a managed switch and network performance. Larry Linder Larry Linder
Re: Please help interpret this error message
On 06/24/2014 06:56 AM, Larry Linder wrote: On Tuesday 24 June 2014 8:54 am, Joseph Areeda wrote: Thanks Stephan, On 06/24/2014 01:07 AM, Stephan Wiesand wrote: On 2014-06-24, at 6:48, Joseph Areeda newsre...@areeda.com wrote: I have a C++ program that runs on multiple systems. It uses a proprietary network protocol contained in a shared object. On one of the systems I get this error regularly but not often enough to use a debugger: NDS library error: Resource temporarily unavailable It only seems to happen on one system, my workstation. I've reinstalled the library. I have Googled my heart out and while I see the error reported in other packages I haven't found anything that explains what it means. NDS is the name of the service (Network Data Service). The only hints I've gotten suggest it might mean the network interface itself might be involved but nothing else seems to have a problem. If it were a bug in the library I'd expect to see it on the other systems which are in production. Any clues as to what it means or where to read up on it would be greatly appreciated. Some library call returned EAGAIN. The prime suspect is usually fork(2), but in the case of a network library, I'd look at send(2) first. Hth Stephan Do you have a managed switch behind a router in system? Maybe a 1G Hz router feeding a 100K Hz router? Most newer boxes have a 1GHz NIC (built in) in them. We have a managed 1 G Hz switch that is managed and we have a Motorola router that is less than 1 GHz with factory default set up. The switch shows up on our network as a device! I sort of wondered about it as a cause of our stack up (slowness) sometimes in the afternoon. I have never seen much discussion about a managed switch and network performance. Larry Linder Larry Linder Well thanks again Stephan, my problem was indeed a socket timeout problem. This project is a proxy server for the proprietary protocol, a stand alone threaded java to C++ interface. Some moron (me) put the timeout on listen connection instead of the client session socket. D'Oh! Larry, I do not use a managed switch. Best, Joe
Re: EL 7 in-place upgrade
On Tue, 2014-06-24 at 20:28 -0700, Yasha Karant wrote: Is the above zstream mechanism available for SL6.5 to SL7x migration? If not, is there to be a functional equivalent? Red Hat has not historically released z-stream sources. There is some talk in the centos project of cobbling together a Fedora-like pre-upgrade package, which is what I assume Red Hat is describing. In a production environment, it would be insane to take that path. Steve
Re: EL 7 in-place upgrade
On 06/24/2014 09:26 PM, S.Tindall wrote: On Tue, 2014-06-24 at 20:28 -0700, Yasha Karant wrote: Is the above zstream mechanism available for SL6.5 to SL7x migration? If not, is there to be a functional equivalent? Red Hat has not historically released z-stream sources. There is some talk in the centos project of cobbling together a Fedora-like pre-upgrade package, which is what I assume Red Hat is describing. In a production environment, it would be insane to take that path. Steve I was not referring to the Fedora mechanism. Some licensed-for-fee commercial unix environments (not linux) used on primary servers allow for major release upgrade in place. Does the Red Hat method that is mentioned by Red Hat allow for this, or is the Red Hat enterprise z-stream insane to use in a production situation? If it is not insane but actually is effective, are there no Linux or GPL encumbrances on z-stream that force Red Hat to release the source? Yasha Karant
