Terminating hanging subprocesses.

Hello!.. Here is the problem I am having. My GUI is designed to take input and write it out to files, then kick off an external program that runs with this data. The big problem is that I've tried everyway I know in the Runtime API to run an executable in a directory other than the home directory (usually c:\Windows). exe's exist in other directories obviously, so why is this so difficult. Anyway to sidestep the issue, I thought of moving the file to the windows directory via the java app, then everything works fine. The problem is that I have to return this File to its original directory when the program terminates so it can find it when restarted. Only, when the exe stops, the program stays active which means you cant move it around. I've tried everything I know to terminate this process manually, but the only thing that works is System.exit(0), and that kills everything... Does this make sense? Does anyone have any suggestions? This is the LAST little hurtle I need to get over to make this program fully operational.
Thanks!!!!

Thanks!.. That link eventually led me to everything that I needed. Damn, runtime.exec() is a tricky little beast isn't it.....
Thanks again.
Brian.

Similar Messages

Terminal hang on opening second tab

hi,
I hope this is the right forum.
Since I upgraded to 10.5, my Terminal keeps crashing as I open a second tab or a new window. This doesn't always happen, but when it happens, this behaviour will continue until I reboot OS X. Then it may be gone for a while or, if I'm unlucky, not.
As a power-terminal-user, this is very disturbing. It even happens with non-OsX-Terminals like iTerm or Terminator. On opening a second terminal window, there is no response from the window and according to top the terminal application I opened the second tab in has an average CPU usage of 99%.
There is no .profile or something, I tried it with bash and zsh as a standard shell, there's no difference.
Please, is there a solution?

I am having this problem too, but only if I run a certain program that leaves a lot of hanging processes around. Other symptoms I noticed:
* Many processes owned by root called "login". I see that there is one even when it's working normally, but I was getting something like 10.
* Typing common commands ("ps") in an existing terminal window caused some sort of kernel-level loop that could not be killed.
Even reboot hung, so I have been forced to power-down, twice so far.

Terminal Hangs a few minutes after I SSH in to a remote host

I ssh into my work computer. I work for a few minutes and it just completely hangs. I don't know what is happening. I don't think it is a network problem, as I am able to log in for about 4 to 5 minutes before it completely freezes. Also, I can successfully connect from my iPad/iPhone, so it is a problem with my laptop terminal.

one of the software you installed may cause this issue. ( could be windows update )
if you remember the last time that your computer worked properly, use windows restore. if you don't, try to perform clean windows installation.
( you can also try to re-install power management before system recovery )

Mail in terminal hangs forever

If I try to send a subject line only email from the terminal using:
mail -s "hello" [email protected]
it just hangs forever. Any ideas how to fix it?

It isn't hanging. It is waiting for you to type your message and then enter Control D to terminate the message.

Terminal hangs at login occasionally

Hi,
So this has now happened twice. When opening a new terminal window, or new tab, the terminal will just hang at the 'login' process. It will never actually present a prompt. Quitting terminal and restarting did no good. Also, perhaps related, I had to do a hard shutdown, as it hung during the restart process.

Have you made any recent changes to your shell's initialization scripts?
try cranking up the verbosity, typically by using something like: 'set -xv'
Which file to use depends on if you're using a login shell or not.
if login shell add it to one of these files:
~/.bash_profile, ~/.bash_login, or ~/.profile
if not a login shell add it to the ~/.bashrc file.
for example
$ head .profile
#!/bin/bash
set -xv
Then just start another Terminal.app session. Watch for where it hangs.

Terminal Hangs During SSH

I recently set up an OS X Server for the first time on an Xserve. My previous experience is with linux.
Since I've set up the server, when ssh'ing to the server, my terminal session is constantly hanging. It happens every few minutes. Maybe related is that the WGM app hangs too, even more quickly.
During sessions, I set the network router to DMZ to allow all traffic to the server, and the firewall is off.
I didn't see any other posts like this. Any pointers to where it is discussed or ideas on where to start looking?

Yes, I can ping the server from a seperate session when it happens. A bit more info...
My server is at another location behind a NAT router with DMZ enabled to the server. All other machines are off at the time. At my end, I'm on a Powerbook, also behind a NAT router. At both ends, the network connectivity seems to be running fine.
This issue does not happen when I am at the server's location on the same subnet. Also, when it does happen, it always is when I have paused activity for several seconds (like when reading something) or when I take the focus off the terminal session window. I can actually recreate the problem by doing one of these two things.
Thanks for your help!
PowerBook G4 / OS X Server 10.4 Mac OS X (10.4.4)

Terminal hangs every 10 seconds for 15 seconds

Hello!
New Mac user here, but I'm a crusty old linux guy at heart.
Brand new iMac (3.4 GHz I7) with Mavericks 10.9.2, pretty fresh out of the box. I've installed a few things: BBedit, Coda, XCode, macports etc.
The terminal has started pausing for 15 seconds, every 10. That is, 10 seconds of me entering commands etc, and then it will hang, spin the pinwheel, and then resume as if nothing happened. This repeats every 10 seconds.
It only appears to do it when terminal has the focus, because otherwise, this Mac rarely pinwheels for what I use it for so far.
any ideas?

Log?

Mac Pro hangs on authentication

I have a Mac Pro dual-dual 3GHz which has a sporadic issue where (as far as I can tell) processes hang when authentication is attempted.
I haven't seen any rhyme or reason to when this occurs. Sometimes, I will be in the middle of working, and I will notice that Terminal hangs when I try to open a new window. Other times, it will occur after the machine has gone to sleep (it wakes up fine, but then attempting to log in will hang).
When this issue is occurring, all the following will hang:
* Logging in via loginwindow
* Switching users
* Logging in via SSH
* Performing sudo
* Opening a new Terminal window
The problem doesn't always go away upon rebooting. Sometimes, I reboot and everything is normal; on other occasions, the login window will hang after I enter my username and password and click Log in, even after multiple reboots.
This problem has never occurred when rebooting in safe mode. However, often I can reboot in safe mode, log in, everything appears normal (for safe mode), but when I reboot in normal mode, the inability to authenticate occurs again.
When this problem is occurring, it occurs on all accounts.
Eventually, after enough reboots, I am able to log in and work normally (until the next time it happens).
Also, I have never noticed anything wrong with either CPU or memory usage when this problem is occurring.
On one occasion when this was happening, I happened to have an open root SSH session available. I ran sc_usage on securityd and found that it was waiting on 'machmsg_overwritetrap'. It waited over 5 minutes without anything further happening. I'm not sure what, if anything, this indicates. (Also, 'LASTPATHNAME_WAITEDFOR' was blank.)
Any ideas would be welcome.

Corupted object.... I had this under 10.3.x..... had to wipe clean and reload OS X from CD.
I read in a post that you could boot in safe mode, and delete "something" (I do not remember now) where the authentification data is stored and then you re-create your users... search past posts.
My suggestion of a clean reload is a safer bet that you will have a clean system.

I save a file and Snow Leopard hangs

Looking for some simple summary comments here.
Since going to SL, I keep having hangs and crashes. I have read through the discussions, but never seen one quite like mine reported.
I have cleaned fonts etc etc but...
1. Open Application (this occurs with nearly every app)
2. Either "Save-As" and existing but edited file, or save for the first-time an NEW file.
Application hangs...
On checking 9 out of 10 times it HAS saved the document, but just will not return to the application.
I have to FORCE QUIT and re-start.
Sometimes this error seems to get exponentially worse. ie, I try to start Terminal to check it out and terminal hangs, console and activity monitor the same. Then it can cascade so that all my applications are stuck, but only after "saving" to the drive.
Any ideas ? solutions ? Has anyone else experienced this?

HI,
First, repair disk permissions.
Quit any open applications/programs. Launch Disk Utility. (Applications/Utilities) Select MacintoshHD in the panel on the left, select the FirstAid tab. Click: Repair Disk Permissions. When it's finished from the Menu Bar, Quit Disk Utility and restart your Mac. If you see a long list of "messages" in the permissions window, it's ok. That can be ignored. As long as you see, "Permissions Repair Complete" when it's finished... you're done. Quit Disk Utility and restart your Mac.
If that didn't help, check the startup disk for errors...
*Insert your SL installer disk* and Restart, holding down the "C" key until grey Apple appears.
Go to Installer menu and launch Disk Utility.
Select your HDD (manufacturer ID) in the left panel.
Select First Aid in the Main panel.
*(Check S.M.A.R.T Status of HDD at the bottom of right panel. It should say: Verified)*
Click Repair Disk on the bottom right.
If DU reports disk does not need repairs quit DU and restart.
If DU reports errors Repair again and again until DU reports disk is repaired.
When you are finished with DU, from the Menu Bar, select Utilities/Startup Manager.
Select your start up disk and click Restart
While you have the Disk Utility window open, look at the bottom of the window. Where you see Capacity and Available. *Make sure there is always 10% to 15% free disk space*
Mac OS X: How to force background maintenance tasks (logs and temporary items)
Carolyn

HT201366 Can anyone else terminal out of their home directory after the security update on the weekend?

syntax: machine:~user$ cd \
That SHOULD take me to \volume1\
However what happens is terminal hangs at > and does nothing and I remain in \volume1\users\homedirectory
so I tired BASH. Same thing. Terminal just hangs as if it doesn't know what to do.
I've verified that all three of my Mac's are doing the same thing after this weekend. The only reason I was alerted to this, is a Firend called me with the same problem and asked if the syntax was correct.
cd .. seems to work but only one level at a time where as cd \ would take you right to volume1.

You've been spending too much time in Windows.
Use the other Slash.

Emagic emi 26 audio interface not working

I want to turn my old dell inspiron 8100 PIII 1.2 Ghz / 512 MB RAM into my sound center, attached to active loudspeakers and a huge USB external harddrive.
Running arch linux and recently did pacman -Suy.
The internal sound card is broken, I only get distorted sounds (in windows as well).
I want to use my a bit dated emagic emi 26 usb audio interface.
The linux installations has (the exact paths are maybe different, writing from another machine now):
/lib/modules/2.6.27-9-generic/kernel/drivers/usb/misc/emi26.ko
/lib/firmware/emi26
So it seems the interface is supported.
However, when I plug it in, nothing happens. Some LEDs light up on the interface,
but /proc/asound/cards only shows my Maestro3 sound card, also alsamixer
doesn't see the device.
If I enter "lsusb", the terminal hangs, no Ctrl-C helps! I can't even kill -9 it as root!
I have snd_usb_audio and emi26 in my MODULES in rc.conf, while having
!audio and !usb_midi there too.
lsmod shows that emi26 is loaded, as well as snd_usb_audio.
Does anybody have an idea on how to go about this?
I guess there must be some problem with the driver...
Thanks for any help

Hello,
"and now I cannot get sound out of my interface, even after trying to unistall that program and reinstall my interface driver"
Try using AppZapper: http://www.apple.com/downloads/macosx/systemdiskutilities/appzapper.html
This way you make sure you have UNinstalled all the associated files.
Carolyn

Arch to Arch: NFS mounts not visible in file explorer

Hi all,
After a long use of Windows I'm coming back to Arch, but with some agony.
I have a NAS which shares my home directory over both cifs and nfs. It runs ARCH.
When I mount the share on my desktop (also Arch) I can browse to it in xterm. I can ls the directories and files without a problem. When I try to open them however, the terminal hangs. Copying, moving, opening, altering ... it all doesnt work. The Xterm just freezes.
When i open the folder with pcmanfm, it doesn't even show the directories.
The weird thing: yesterday it worked, today no go.
Desktop fstab:
192.168.1.2:/home/wouter /media/wouter nfs auto,user 0 0
Server exports:
/home/wouter 192.168.1.53(rw,async,nohide)
- The NFS service are running fine because my ESXi server its datastore is stored over NFS on the NAS.
- The NFS services on the desktop are running.
- Both systems are running the latest package version.
- File permissions are correctly set: 700 wouter:users

Same problem here.

Installing IEs4linux from the repos - how to?

I got ies4linux from the repos (I guess community), and ran the script to install IE6. Now when starting it with wine iexplorer.exe it wants to install Mozilla - unfortunately that doesn't work.
[ ~/.ies4linux/ie6/drive_c/Program Files/Internet Explorer ] wine iexplore.exe
fixme:shell:StopWatchMode () stub!
fixme:ole:CoResumeClassObjects stub
fixme:shdocvw:go_home stub
fixme:urlmon:URLMonikerImpl_BindToObject use running object table
fixme:urlmon:ObtainUserAgentString (0, 0x7de0c70b, 0x7de0c704): stub
fixme:urlmon:ObtainUserAgentString (0, 0x1290e8, 0x7de0c704): stub
fixme:wininet:InternetLockRequestFile STUB
err:cabinet:FDICopy FDIIsCabinet failed.
err:mshtml:check_version Could not open VERSION file
Could not load Mozilla. HTML rendering will be disabled.
fixme:shdocvw:ClOleCommandTarget_QueryStatus (0x1265b4)->((null) 1 0x33f1ec (nil))
fixme:shdocvw:ClOleCommandTarget_Exec (0x1265b4)->((null) 25 2 0x33f200 (nil))
fixme:shdocvw:ClOleCommandTarget_Exec (0x1265b4)->((null) 26 2 0x33f200 (nil))
fixme:shdocvw:ClientSite_GetContainer (0x1265b4)->(0x33f23c)
fixme:shdocvw:ClOleCommandTarget_Exec (0x1265b4)->({000214d1-0000-0000-c000-000000000046} 37 0 0x33f358 (nil))
fixme:shdocvw:ClOleCommandTarget_Exec (0x1265b4)->({000214d1-0000-0000-c000-000000000046} 84 0 (nil) 0x33f390)
fixme:shdocvw:ClOleCommandTarget_Exec (0x1265b4)->((null) 29 2 0x33fcc0 (nil))
fixme:shdocvw:DocHostUIHandler_GetDropTarget (0x1265b4)
fixme:shdocvw:ClOleCommandTarget_Exec (0x1265b4)->({000214d0-0000-0000-c000-000000000046} 69 0 (nil) 0x33fc08)
fixme:shdocvw:ClOleCommandTarget_Exec (0x1265b4)->({000214d0-0000-0000-c000-000000000046} 69 0 (nil) 0x33fc08)
fixme:shdocvw:ClOleCommandTarget_Exec (0x1265b4)->((null) 26 2 0x33fca0 (nil))
fixme:shdocvw:ClOleCommandTarget_Exec (0x1265b4)->((null) 29 2 0x33fcb0 (nil))
fixme:shdocvw:ClOleCommandTarget_Exec (0x1265b4)->({000214d1-0000-0000-c000-000000000046} 103 0 (nil) (nil))
fixme:shdocvw:ClOleCommandTarget_Exec (0x1265b4)->({de4ba900-59ca-11cf-9592-444553540000} 2315 0 (nil) (nil))
fixme:shdocvw:ClOleCommandTarget_Exec (0x1265b4)->((null) 35 0 (nil) (nil))
fixme:shdocvw:ClOleCommandTarget_Exec (0x1265b4)->((null) 28 2 0x33fc08 (nil))
fixme:shdocvw:ClientSite_GetContainer (0x1265b4)->(0x33fb4c)
fixme:shdocvw:InPlaceFrame_SetStatusText (0x1265b4)->(0xb7ded9b1)
fixme:shdocvw:ClOleCommandTarget_Exec (0x1265b4)->((null) 25 2 0x33fa80 (nil))
fixme:shdocvw:ClOleCommandTarget_Exec (0x1265b4)->((null) 26 2 0x33fa80 (nil))
fixme:shdocvw:ClOleCommandTarget_Exec (0x1265b4)->((null) 21 2 (nil) (nil))
The Aur doesn't really help either.

Same problem here. Did you also get this message when installing IE6?
~/.ies4linux/downloads/ie6/EN-US/SETUPW95.CAB: No such file or directory
I looked for SETUPW95.CAB somewhere else and dropped it in ~/.ies4linux/downloads/ie6/EN-US. After that, I get:
IEs4Linux installations finished!
To run your IEs, type:
ie6
When, after a succesful install, running IE6 as 'ie6', everything just works fine (so far).
EDIT: Unfortunately, I only succeed to start IE6 once. After I close the Wine-application, the terminal hangs and, according to ps, the instance remains open. After closing it the hard way I am not able to start IE anymore, a reinstall using the ies4linux-script is necessary.
Last edited by Marcel- (2008-07-16 23:52:43)

Forzen gray screen at boot

I'm using an iMac that was new in Dec '12. 27-inch I think it's still the current model.
Lately I've been getting long if not terminal hang-ups at boot on the plain gray screen.
The only system maintenance I have with this Mac is to confirm and correct my preferences on the main drive, through Disk Utility. I know there is much more to clean up in the system.
What program should I be using to do this with?
I used to use Onyx, but that is now only a pay program now. If I must use a pay program I want to get the best value for the program.
So my question is two questions.....
1. Are there free programs that will clean up the caches and whatever else needs attending to?
2. What is the best pay program for maintaing a Mac?
Thanks

Take each of these steps that you haven't already tried. Stop when the problem is resolved.
Step 1
The first step in dealing with a boot failure is to secure your data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since your last backup, you can skip this step.
There are several ways to back up a Mac that is unable to boot. You need an external hard drive to hold the backup data.a. Boot into Recovery by holding down the key combination command-R at the startup chime, or from a local Time Machine backup volume (option key at startup.) Release the keys when you see a gray screen with a spinning dial. When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.”
b. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, boot the non-working Mac in target disk mode by holding down the key combination command-T at the startup chime. Connect the two Macs with a FireWire or Thunderbolt cable. The internal drive of the machine running in target mode will mount as an external drive on the other machine. Copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
c. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
Step 2
Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to boot, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can boot now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
If you've booted from an external storage device, make sure that your internal boot volume is selected in the Startup Disk pane of System Preferences.
Step 3
Boot in safe mode. Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Post for further instructions.
Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
When you boot in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, your boot volume is damaged and the drive is probably malfunctioning. In that case, go to step 5.
If you can boot and log in now, empty the Trash, and then open the Finder Info window on your boot volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then reboot as usual (i.e., not in safe mode.)
If the boot process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
Step 4
Sometimes a boot failure can be resolved by resetting the NVRAM.
Step 5
Launch Disk Utility in Recovery mode (see step 1.) Select your startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then reboot as usual.
Step 6
Boot into Recovery again. When the OS X Utilities screen appears, follow the prompts to reinstall the OS. If your Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
Note: You need an always-on Ethernet or Wi-Fi connection to the Internet to use Recovery. It won’t work with USB or PPPoE modems, or with proxy servers, or with networks that require a certificate for authentication.
Step 7
Repeat step 6, but this time erase the boot volume in Disk Utility before installing. The system should automatically reboot into the Setup Assistant. Follow the prompts to transfer your data from a backup.
Step 8
A dead logic-board battery in a Mac Pro can cause a gray screen at boot. Typically the boot failure will be preceded by loss of the startup disk and system clock settings. See the user manual for replacement instructions.
Step 9
If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store to have the machine tested.

Bdb deadlocks when opening database

When I call _dbp->open(), the library hangs. I am attempting to test how BDB works during system crashes, in order to code my application appropriately, but these hangs are difficult to work with.
I am running multiple processes all reading and writing to a single database. I then kill off the processes one at a time, until one of the terminations hangs all the other processes reading or writing to that database. I understand the database may at that time be in a bad state and may need to be re-opened with the DB_RECOVER flag, but I don't get any kind of an error message on the other processes reading or writing to the database. They just hang. (it looks like they are waiting for the lock of the terminated process to be closed).
I have code to check for a DB_RUNRECOVERY error number returned as part of the exception thrown during a db->open() operation, so I can then can db->open() again with the DB_RECOVER option, but db->open() never returns.
I have tried setting the transaction timeout values and lock timeout values, but nothing seems to be working.
I have tried working with the DB_REGISTER option, but would prefer not to limit each process to a single environment. I'd like to hide the BDB environment entirely from the caller and simply require the database name.
Any assistance would be appreciated,
Todd

I do not have the option of launching a separate process to monitor the database. Unfortunately, I have resigned to the fact I must provide a separate thread to test for failures and deadlocks.
As a result, I have created a static process-wide "EnvironmentManager" class to maintain a collection of Environments and Databases opened by the current process. This ensures the process will only have a single instance of any Environment open. As a result, I should be able to open my environment(s) with DB_REGISTER and DB_RECOVER.
I also created a monitor thread. This thread does the following:
foreach open environment
envp->lock_detect(0,DB_LOCK_DEFAULT,NULL);
envp->failchk(0);
If a DbException with errno set to DB_RUNRECORY occurs, I do the following:
     Close each database opened within the faulted environment
     Close the environment
     Re-Open the environment
     Re-Open each database
I would like to cycle through any open transactions, locks and cursors to close them, but it appears I do not have access to them.
My test engine runs in an infinite loop doing the following:
- Open Environment and Database
- Write 200 records
- Read 200 records
- Get a count of records
- Close the database and environment
To test the failures, I launch multiple instances of the test engine then kill the processes one at a time. Obviously my production application with do a normal shut-down under normal conditions, but I need to handle time when an application crashes unexpectedly. I understand problems will occur, my goal is simply to get the system to throw exceptions that I can recover from. I need to resolve all dead-lock issues that can hang my application and all unexpected application-aborts that occur as a result of DB_ASSERT failures.
The problems I am now encountering after implementing all of this:
1) After a process has crashed and I attempt to ‘recover’ from within another running process, I am getting an exception regarding an open file handle to __db.register.
PANIC: fatal region error detected; run recovery
File handles still open at environment close
Open file handle: C:\__db.register
assert failure: ..\mutex\mut_win32.c/174: "__ip != NULL && __ip->dbth_state != THREAD_OUT"
2) If I try to run the same application multiple times quickly by double clicking on the same executable, I get the following exception:
DB_REGISTER limits processes to one open DB_ENV handle per environment
DbEnv::open: Invalid argument
Both of these issues appear to be with the DB_REGISTER option being specified when I open the environment, but things get much murkier if I remove that option.
If I do not specify DB_REGISTER and DB_RECOVER on the command line, it is possible for my call to DbEnv->Open() to hang indefinitely. Otherwise, I would call Open() once and if it failed, call it again with DB_RECOVER.
Please let me know how to proceed. How have other people handled running Berkeley DB across multiple processes?
Regards,
Todd

Terminating hanging subprocesses.

Similar Messages

Maybe you are looking for