- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Linux
- >
- General
- >
- Warning: Problem with cfg2html script
General
turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
-
-
Categories
- Solutions
- IT Transformation
- Topics
- Big Data
- Cloud
- Security
- Infrastructure
- Strategy and Technology
- Products
- Cloud
- Integrated Systems
- Networking
- Servers and Operating Systems
- Services
- Storage
- Company
- Events
- Partner Certification
- Welcome
- Welcome
- Announcements
- Tips and Tricks
- Feedback
-
Blogs
- Alliances
- Around the Storage Block
- Behind the scenes @ Labs
- Converged Data Center Infrastructure
- Digital Transformation
- Grounded in the Cloud
- HPE Careers
- Infrastructure Insights
- Inspiring Progress
- Internet of Things (IoT)
- My Learning Certification
- Networking
- OEM Solutions
- Servers: The Right Compute
- Technical Support Services
- Telecom IQ
- Transforming IT
- Quick Links
-
Categories
-
Forums
-
Blogs
-
InformationEnglish
Warning: Problem with cfg2html script
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
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
06-01-2010 01:17 AM
06-01-2010 01:17 AM
Warning: Problem with cfg2html script
Warning: Problem with cfg2html script
We have discovered a problem with the cfg2html script which is run occasionally on the Linux servers to gather config information.
The script contains a call to ldconfig "configure dynamic linker run-time bindings", which then runs with the parameters -vN. This causes the script to re-link libraries.
The problem has arisen on gbahel92/93 and 94 (the Storapart servers), when this script re-links the library libxml2.so.2 to a default value, rather than the version which is required to run the applications, thereby causing them to fail.
In order to prevent this re-linking from taking place, we have 2 options
1) Run the script with -k to prevent kernel checks, however this may not be suitable as we would require these kernel details for some investigations.
2) Amend the script to call ldconfig with the parameters -vNX The addition of the X prevents libraries from being relinked.
As far as we know, this has only affected the Storapart servers so far, but it's possible that this could have updated links on other servers that we're not aware of.
The script contains a call to ldconfig "configure dynamic linker run-time bindings", which then runs with the parameters -vN. This causes the script to re-link libraries.
The problem has arisen on gbahel92/93 and 94 (the Storapart servers), when this script re-links the library libxml2.so.2 to a default value, rather than the version which is required to run the applications, thereby causing them to fail.
In order to prevent this re-linking from taking place, we have 2 options
1) Run the script with -k to prevent kernel checks, however this may not be suitable as we would require these kernel details for some investigations.
2) Amend the script to call ldconfig with the parameters -vNX The addition of the X prevents libraries from being relinked.
As far as we know, this has only affected the Storapart servers so far, but it's possible that this could have updated links on other servers that we're not aware of.
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.
End of content
United States
Hewlett Packard Enterprise International
© Copyright 2017 Hewlett Packard Enterprise Development LP