- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: pfmstat-tkt SEP was restarting
Operating System - Linux
1752809
Members
6097
Online
108789
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-10-2011 02:51 AM
тАО02-10-2011 02:51 AM
Re: pfmstat-tkt SEP was restarting
>I'm suspecting issue with RAM eventhough the server is not showing anything.
That's possible.
One possible way to diagnose it would be to switch the package to the server that does not crash, and then run memtest86 or some other rigorous memory test in a continuous loop on the crashy server for a few days or so.
> In the other member of the cluster the same application is working properly. After we swicth over to the other member , the same package is getting crashed .
Are both servers at exactly the same patch level? Perhaps one member has a patched version of some library, and the other has a buggy, unpatched version?
On both nodes, run this command (all on one line):
rpm -qa --queryformat '%{NAME}%{VERSION}%{RELEASE}.%{ARCH}\n' | sort > packages.$(hostname -s).txt
You'll get one file on each node: packages.ips122.txt and packages.ips222.txt. Move both files to the same node, and then run:
diff -u packages.ips122.txt packages.ips222.txt
If the nodes don't have exactly the same versions of RPM packages installed, this command will tell you the differences. If it outputs nothing, the lists are identical.
MK
That's possible.
One possible way to diagnose it would be to switch the package to the server that does not crash, and then run memtest86 or some other rigorous memory test in a continuous loop on the crashy server for a few days or so.
> In the other member of the cluster the same application is working properly. After we swicth over to the other member , the same package is getting crashed .
Are both servers at exactly the same patch level? Perhaps one member has a patched version of some library, and the other has a buggy, unpatched version?
On both nodes, run this command (all on one line):
rpm -qa --queryformat '%{NAME}%{VERSION}%{RELEASE}.%{ARCH}\n' | sort > packages.$(hostname -s).txt
You'll get one file on each node: packages.ips122.txt and packages.ips222.txt. Move both files to the same node, and then run:
diff -u packages.ips122.txt packages.ips222.txt
If the nodes don't have exactly the same versions of RPM packages installed, this command will tell you the differences. If it outputs nothing, the lists are identical.
MK
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-10-2011 03:14 AM
тАО02-10-2011 03:14 AM
Re: pfmstat-tkt SEP was restarting
The package version is same ,
The package is not crashing if we run it in non problamatic server.
The package is not crashing if we run it in non problamatic server.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2011 11:44 PM
тАО02-17-2011 11:44 PM
Re: pfmstat-tkt SEP was restarting
I had reduced my RAM to 16GB in the problamatic server .Now the package is working fine in the server .
But i have a doubt
We have two servers in cluster . One server was of 16GB and the other was of 32GB.
Is it required that two nodes in the cluster should have same capacity of RAM ?
Means is it required that my two nodes in the cluster should be of either 32GB or 16GB?
But i have a doubt
We have two servers in cluster . One server was of 16GB and the other was of 32GB.
Is it required that two nodes in the cluster should have same capacity of RAM ?
Means is it required that my two nodes in the cluster should be of either 32GB or 16GB?
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP