- Community Home
- >
- Servers and Operating Systems
- >
- Operating System - HP-UX
- >
- System Administration
- >
- Error in lseek and ioctl
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- 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
- Email to a Friend
- Report Inappropriate Content
09-14-2012 12:07 AM
09-14-2012 12:07 AM
Re: Error in lseek and ioctl
Hi Dennis,
I used the below command
tusc -pfea -o /tmp/resultfile pid
If you didnt get any good infromation from this , i will do it once more and post .
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
09-14-2012 12:58 AM - edited 09-14-2012 06:50 PM
09-14-2012 12:58 AM - edited 09-14-2012 06:50 PM
Re: Problems with crontab and scp
>tusc -pfea -o /tmp/resultfile pid
It appears you did this after that PID forked the process that does the real work?
Can you get a ps(1) output of that PID and its child, so you can make sure you are tracing the right process.
Or if this is done on a continual basis, trace the parent of PID and that will eventually have some useful data.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
09-14-2012 04:27 AM
09-14-2012 04:27 AM
Re: Error in lseek and ioctl
can you add set -x at the begining of your script
/eytools/eybin/get_linuxinfo.sh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
09-14-2012 06:10 PM
09-14-2012 06:10 PM
Re: Error in lseek and ioctl
Hi Dennis,
Parent PID of this process is crond , can i track with the PID of cron.
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
09-14-2012 06:50 PM
09-14-2012 06:50 PM
Re: Problems with crontab and scp
>can I track with the PID of cron?
Yes but it may give too much if there are other activities.
You could replace your crontab entry with a script that invokes tusc on your real script.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
09-15-2012 07:26 PM
09-15-2012 07:26 PM
Re: Problems with crontab and scp
Hi,
I am attaching the output of tusc . Could you please check the output for the server ussecavldnaut1. This is one of the server which i am facing issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-08-2012 07:29 PM
10-08-2012 07:29 PM
SolutionHi Team,
Thanks a lot for the help. The issue is resolved . The problem was with the time zone . The main servers was on GMT and the clients having EDT. So i just changed execution time of script in crontab. Now its working fine . Thanks a lot for your help.
Regards
- « Previous
-
- 1
- 2
- Next »
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP