There has to be something I'm misunderstanding. I can simply start "screen" on another Linux box and it opens up just fine, but when I try starting "screen" on my Linux box, it seems as though it's trying to execute a command or something. Screen then terminates after it gives me this error message on the bottom of the screen.
Any ideas?
Related
When I use screen, it works fine except up to the point where I need to re-attach. My suspicion is that the sort of "shelled" environment I am using is not letting screen fully detach although I am unsure of whether that is the case.
My current environment is this: ssh -> cygwin bash shell -> screen
Everything works fine but when I try to attach with screen -r (id), the command doesn't do anything, I don't get any output and when checking with screen -ls the screen session is still listed as detached. I researched this but can only come up with other people who either get a dead screen session or some error. I don't get either, the command runs and gives no output leaving the screen detached. I have a feeling this is something to do with screen not detaching fully because of the layered shells but have no idea how to fix it.
Any suggestions?
I’ve started weblogic through putty:
./startWebLogic.sh
After that server started successfully.
But when I close the putty window, the server stops working
How can I keep weblogic running after I close the putty window?
Thanks!
You will want to use something like the following:
nohup ./startWebLogic.sh &
Nohup is a unix command, used to start another program, in such a way that it does not terminate when the parent process is terminated.
You can also output it to a file if you'd like:
nohup ./startWebLogic.sh > admin_server.out &
Simple Steps:
after the login through putty follow the below steps:
Go directory of server where "startWebLogic.sh" this command located.
typed command "screen" press enter (A new Screen will opened)
In the new screen type your run command "./startWebLogic.sh".
Press Ctrl+a then press d(without holding Ctrl) you will return back previous screen)
if like to go again your server log screen typed command "screen -r"
Akbar
I use tmux 1.6-2 on a Debian 7.6 (wheezy).
I open a new session and start a long running script that gives updates in form of a progress bar and an activity indicator (spinning bar: /-\|/ ).
When I detach and reattach everything is still fine. But after some random time when I reattach the screen content is stuck. No spinning bar, no progress. I looked into the following:
I can see in top that the process is still running
I can successfully enter tmux commands (like new window, detach, etc.)
I can kill the script with Ctrl-C, but the tmux screen doesn't change
Ctrl-S and Ctrl-Q (like suggested in other threads) doesn't help
Any help is very much appreciated.
I managed to unfreeze my tmux session by running choose-client command from tmux's command line <prefix> :
where prefix is C-b by default
I found the solution in the bug report (by Taisuke Yamada).
I'm having small problem with the rails console in Rails 3.
I'm using a Mac and zsh in terminal. When I run the rails console I'm prompted with this:
ruby-head :001 >
When I try to use the up arrow to repeat last command I get an error sound and the command is not shown. Also to use tab as auto complete I have to press tab twice.
Another problem is that it takes about 10 seconds from I give the rails console command until the console is displayed. Is that normal?
Regards,
Johann
Check for a file in your home directory called .inputrc and see if it contains:
set editing-mode vi
For me that was the issue and removing that line sets things back to normal. Now I'm just wondering how on earth that file ended up getting created.
All,
I have a COM Server Component (a .Dll) which is developed by someone. When I invoke (using invoke()) a function in that COM Server, it throws the error 0x800706BE -The remote procedure call failed. Interestingly it throws this error only few times!!. it works fine for the rest of the times!!.
The issue is reported in a windows 2k8 64 bit OS & Win 7 32 bit.
Any idea what could be the issue?
would it an issue with the COM Server or COM Client ?
is there any way by which I can narrow down to know the culprit?
Thanks,
Bytes
ok. It seems I have found out the problem. The COM Server(.dll) was crashing the moment I called Invoke() on that. The problem seems to be in the COM Server.
Hope it will be helpful for someone.
1 : Open an elevated command prompt. To do this, swipe in from the right edge of the screen, and then tap Search. Or, if you are using a mouse, point to the lower-right corner of the screen, and then click Search. Type Command Prompt in the Search box, right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow.
2 : Type the following commands. Press Enter after each command.
Note: It may take several minutes for each command operation to be completed.
DISM.exe /Online /Cleanup-image /Scanhealth
DISM.exe /Online /Cleanup-image /Restorehealth
3 : Close the command prompt, and then run Windows Update again.