- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: kill fbackup
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
тАО11-08-2009 07:01 PM
тАО11-08-2009 07:01 PM
Here's what happen, I issued kill -9 to kill fbackup and I think it is now a ghost process, and we can't perform backup anymore. Aside from reboot, is there other way to kill this proccess. I'm using HPUX 11.11 9000/800. Thnaks in advance guys. Sample of ps -ef|grep fbackup:
root 6216 1 0 Nov 7 pts/tk 0:00 /usr/sbin/fbackup -f /dev/rmt/14m -0 -u -v -c /var/adm/fbackupf
root 3759 1 0 Nov 7 ? 0:00 /usr/sbin/fbackup -f /dev/rmt/14m -0 -u -v -c /var/adm/fbackupf
root 29363 5988 1 10:31:39 pts/11 0:00 grep fbackup
root 2000 1 0 Nov 7 ? 0:00 /usr/sbin/fbackup -f /dev/rmt/14m -0 -u -v -c /var/adm/fbackupf
root 12701 20575 0 Nov 7 pts/tk 0:00 /usr/sbin/fbackup -f /dev/rmt/14m -0 -u -v -c /var/adm/fbackupf
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-08-2009 07:24 PM
тАО11-08-2009 07:24 PM
Re: kill fbackup
root 3759 1 0 Nov 7 ? 0:00 /usr/sbin/fbackup -f /dev/rmt/14m -0 -u -v -c /var/adm/fbackupf
root 29363 5988 1 10:31:39 pts/11 0:00 grep fbackup
root 2000 1 0 Nov 7 ? 0:00 /usr/sbin/fbackup -f /dev/rmt/14m -0 -u -v -c /var/adm/fbackupf
root 12701 20575 0 Nov 7 pts/tk 0:00 /usr/sbin/fbackup -f /dev/rmt/14m -0 -u -v -c /var/adm/fbackupf<<<<<<<<<<<<
I will start with below
kill -9 3759 29363 2000 12701
if not reboot
"ghost" processes you actually mean "zombie" processes. You can't kill them (because they are already dead and can certainly never respond to a signal which is all a kill is). Zombie's consume no resources (other than a process table slot) and do no real harm.
- Tags:
- zombie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-08-2009 07:35 PM
тАО11-08-2009 07:35 PM
Re: kill fbackup
Any other inputs?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-08-2009 08:13 PM
тАО11-08-2009 08:13 PM
SolutionI assume you have issued several kill -9 signals and fbackup does not respond. So the program is hung, waiting on some service from the kernel. Your program will not terminate until the condition causing the hang is removed. Normally, I would expect this kind of a problem with a network backup but the above appears to be a tape backup. Check your syslog.log for hardware errors. Also, are you backing up data from a network filesystem (NFS or CIFS?). Or are you using LUNs from a SAN system? Any of these conditions could cause the program to hang while waiting for the kernel to complete the I/O.
There isn't any way to terminate fbackup until it starts running again. Therefore a reboot is required. This will also remove the shared memory segments that wwere orphaned by fbackup.
kill signals actually do not terminate a program. Instead, the signal (like kill -15) is stored in the program's process table and the program will immediately check the signal. A well writen program (like fbackup) will senes the signal and gracefully shutdown. However, kill -9 cannot be sensed or trapped like other signals. kill -9 will forcefully remove the program without allowing any cleanup for files and shared memory. Use it as a very last resort.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-08-2009 09:23 PM
тАО11-08-2009 09:23 PM
Re: kill fbackup
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-08-2009 11:50 PM
тАО11-08-2009 11:50 PM
Re: kill fbackup
These are hung processes, not zombies. And you can kill zombies by killing the zombie master.
- Tags:
- zombie master
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-09-2009 12:58 AM
тАО11-09-2009 12:58 AM