Sometimes Xcode does not stop the debugging process properly and the only way to kill that process seems to be a reboot of the mac.
I can not kill it via shell command (kill -9, or actually sudo - kill -9). I also tried to remove the process from the launchctl table before killing with the command, which also does not work, the command returns 'No such process'.
Is there really no other way than rebooting the system in such a case??
Thanks.
Try looking here: Couldn't register with the bootstrap Server and here: iPhone - strange error when testing on simulator
I myself experienced this occasionally, but I've never managed to resolve it using any of the methods stated. Hate to say this, but I always end up restarting the Mac to fix it.
Related
We recently did a GitLab upgrade from 11.x up to 12.9.2. It all went well; however, when I do gitlab-ctl pg-upgrade it shows the DB being 10.12. But when I do gitlab-rake gitlab:env:info it shows 10.7.
If I drop into gitlab-rails dbconsole it shows:
psql (10.12, server 10.7)
I didn't originally set this server or instance up. Any idea why it would be showing two different versions (does 10.12 mean the client is 10.12, the server is still 10.7?) Ideally the server would be 10.12.
Thanks for any help.
Answered my own question after further digging.
I ran a stat on /opt/gitlab/embedded/postgresql/10/bin/postgres and it showed that it was indeed changed when we did the upgrade.
Then I ran an lsof and saw that the postgres process had this binary open with a (deleted) marker, meaning it had the previous file still open in memory.
I ran a gitlab-ctl stop and a gitlab-ctl start and now it's showing properly when I do gitlab-rails dbconsole.
Should've done all that first!
After using sshfs on my Mac I am no longer able to see my user directory.
When I open a terminal window I see the following:
Last login: Mon May 22 10:54:30 on ttys003
mkdir: /Users/<username>/.bash_sessions: Device not configured
-bash: /Users/<username>/.bash_profile: Device not configured
touch: /Users/<username>/.bash_sessions/35166655-583B-47CC-9BCF-5E785DD5E46E.historynew: Device not configured
Is there any way to fix this?
Cheers
Paul
I used to use sshfs and got this error; the only way to fix it I found without rebooting was:
sudo diskutil umount force /path/to/mount
I've recently been trying https://github.com/spion/adbfs-rootless for something else and find I can get into the same situation, the "fix" works in that case as well.
Wasn't getting anywhere so took a chance and did a reboot. Everything seems to be OK now.
I am currently working on centos running on intel atom board. I mistakenly renamed lic-2.17.so to _libc-2.17.so
library on my board, when I reboot the board it is giving me below error.
[ OK ] Reached target Initrd Default Target.
systemd-journald[136]: Received SIGTERM
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
Is there any possible way to get back to the original state.
I entered into grub prompt and able to see cat /lib64/_libc-2.17.so. Not Sure,
how to rename this to original name
Thanks in advance.
Can you enter run-level 3 from grub?
if so,
sudo mv /lib64/_libc-2.17.so /lib64/libc-2.17.so
if you can't enter run-level 3, you can try using a live DVD/USB to run the above command, you're just going to have to manually search for the right partition which the incorrectly named file is located.
Otherwise, I'm afraid you're going to need to reinstall the OS.
Sometimes my Eclipse hangs and I need to kill it violently. However, I have been unable to do it properly. It seems that kill -9 does not actually shut it down in a proper way since I can still see the hanged window. What command sequence would kill my Eclipse properly so I could restart it?
I am running Ubuntu 12.10 and Eclipse 4.2(Juno).
You can also use jps -l to get all of the process id's of java processes
You need to kill the javaw process on which Eclipse runs (usually it is the one with about 1GB memory usage :) )
Based on the answer of Uku and Michael you can do the following:
On your terminal first run:
jps -l
Check the pid of the process that is running Eclipse and copy the pid.
Then kill the process id by running:
// use the actual process id
kill -p {the_copied_pid}
When I start the `Paste' web server in daemon mode, it seems to kill off it's ability to reload when the timestamp of a source file is updated.
Here is how I start the daemon...
cd ${project} && ../bin/paster serve --reload --daemon development.ini; cd ..;
...which defeats one of the main points of using Paste (for me).
Has anyone come across this or know what I'm doing wrong?
To be complete, the file that I'm changing is a controller file.
The version is `PasteScript 1.7.3'
I believe that the two options are essentially incompatible, since the reloader stops the server with a SIGTERM and the daemon-ized server is impervious to that -- and since daemon is intended for running in a production environment, and reload for a development/debugging environment, I guess that their incompatibility is not seen as a big loss. I imagine a customized reloader, tailored to properly stop and restart the daemonized server, could certainly be developed, but I don't know of any existing one.
I had a similar problem and circumvented the problem. I currently have paster running on a remote host, but I am still developing, so I needed a means to restart paster, but manually by hand was too time consuming, and daemon didnt work. So I always had to keep a shell window open to the server and running paster without --daemon in there. Once I finished my work for that day, and i closed the shell, paster died, which is bad.
I circumvented that by running paster non daemonized in a "screen".
Simply type "screen" in your shell of choice, you will usually depending on your linux be presented with a virtual terminal, that will keep running even when you log out your remote session. Start paster as usually in your new "window" (the screen) with --reload but without daemon, and then detach the window, so you can return to your normal shell (detach = CTRL-A, then press D). You can re-enter that screen by typing "screen -r". If you would like to kill it, reconnect it (screen -r) and inside the screen type CTRL-A, then press K.
Hope that helps.