- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Common audit log failures for libogltls.so and loc...
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
тАО07-29-2008 01:27 PM
тАО07-29-2008 01:27 PM
Common audit log failures for libogltls.so and locales.1/C
I'm relatively new to the audit logging features of HP-UX. We have 2 messages that are continuously showing up in the audit logs of which I'm not sure of the source. We're running HP-UX 11.23 (May 2005).
One of the features we have turned on are open/close access failures. Every 30 seconds or so, a process is spawned that attempts to open the following shared library and file. This generates a large amount of log entries as the system runs autonomously, continually filling the logs and making it scrutinizingly tedious finding audit failures of relevance.
/opt/graphics/OpenGL/lib/hpux32/libogltls.so
/usr/lib/nls/loc/hpux32/locales.1/C
The failure for the lib0gltls.so is logged because it is not exist but the problem I'm having is locating which service is turned on that accesses these files. The log provides a process ID however by the time it is logged, the process no longer exists.
Does anyone happen to know what service might be looking to access these files or how I might go about finding it?
Thanks in advance for your help.
Bryan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-29-2008 09:37 PM
тАО07-29-2008 09:37 PM
Re: Common audit log failures for libogltls.so and locales.1/C
1) Check the existence of these files. Install their depots that provide them if missing.
2) If present, make sure SHLIB_PATH in the startup or any compile scripts includes their locations.
3) Make sure the libraries and executables are IA-64 binaries.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2008 12:43 AM
тАО07-30-2008 12:43 AM
Re: Common audit log failures for libogltls.so and locales.1/C
The first may exist if you have OGL installed and dld.so automatically checks for it for every? stinkin' exec(2).
The latter doesn't exist on any system. Years ago setlocale(3) used to do a stat(2) on the shlib before calling shl_load(3) but somehow they decided why check twice.
(This seems silly since there never was that locale and a strcmp for "C" would be easy.)
So your problem is that you keep starting processes. But if it's every 30 seconds, this is normal.
So you should rethink logging access failures. Or you need to filter out these useless messages.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2008 10:45 AM
тАО07-30-2008 10:45 AM
Re: Common audit log failures for libogltls.so and locales.1/C
When you say dld.so checks for libogltls.so every exec, is this for *all* exec calls or is it only for exec calls that use the libogltls.so library? (I would assume only for execs that use the libogltls.so) If it's for all execs, that would make sense whey there are so many entries in the audit log.
I was just hoping to prevent the process from running since this system is not doing anything graphics related anyway.
Bryan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2008 09:10 PM
тАО07-30-2008 09:10 PM
Re: Common audit log failures for libogltls.so and locales.1/C
>If it's for all execs, that would make sense whey there are so many entries in the audit log.
Yes, every stinkin' one that uses shlibs.
If you update your dld patch to something newer like PHSS_37947, it will go away.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2008 09:11 PM
тАО07-30-2008 09:11 PM
Re: Common audit log failures for libogltls.so and locales.1/C
Generic how? I said exactly why they occur.