Sponsored Content
Top Forums UNIX for Advanced & Expert Users connection to localhost:10.0 host broken (explicit kill or server shutdown) Post 302209719 by tekjunky on Saturday 28th of June 2008 02:25:23 AM
Old 06-28-2008
This looks like tomcat is trying to open a GUI in X and you do not have X forwarded properly or not at all. The "-Y" switch just enables trusted X11 forwarding however you still need an X running on the client and the client must be "trusted". You may have to run "xhost +" or "xhost + <servername>" on the server (not client) to allow X to be attached to from a remote server/session.

Have you tried VNC rather than ssh to run this application?
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

rc scripts, do i need to kill them on shutdown?

We have a bunch of tools, that run on linux and on unix, I've got start up scripts that bring up their license managers when the unix box boots, do I need kill scripts for when the box is shutting down? I've not seen much documentation on this, just on getting the license managers started, but... (1 Reply)
Discussion started by: kymberm
1 Replies

2. UNIX for Advanced & Expert Users

Recover X Forwarding after broken connection

Hello, today I logged in on a remote machine via "ssh -X ..." and started a screen session. In this i started OpenOffice.org writer by writing "oowriter". After some time the connection got lost (The network here is quite unstable). Now I logged in again via "ssh -X ...". The screen session is... (1 Reply)
Discussion started by: schola
1 Replies

3. Solaris

PING - Unknown host 127.0.0.1, Unknown host localhost - Solaris 10

Hello, I have a problem - I created a chrooted jail for one user. When I'm logged in as root, everything work fine, but when I'm logged in as a chrooted user - I have many problems: 1. When I execute the command ping, I get weird results: bash-3.00$ usr/sbin/ping localhost ... (4 Replies)
Discussion started by: Przemek
4 Replies

4. UNIX for Dummies Questions & Answers

ssh_exchange_identification: Connection closed by remote host Connection closed

Hi Everyone, Good day. Scenario: 2 unix servers -- A (SunOS) and B (AIX) I have an ftp script to sftp 30 files from A to B which happen almost instantaneously i.e 30 sftp's happen at the same time. Some of these sftp's fail with the following error: ssh_exchange_identification: Connection... (1 Reply)
Discussion started by: jeevan_fimare
1 Replies

5. UNIX for Dummies Questions & Answers

localhost [127.0.0.1] did not issue MAIL/EXPN/VRFY/ETRN during connection to MTA

hardware = raq550 running on strongbolt2. my sendmail log is littered with this entry all through the day: localhost did not issue MAIL/EXPN/VRFY/ETRN during connection to MTA it occurrs every 15 minutes. I don't have any problem sending or receiving mail. I did a search on google but couldn't... (0 Replies)
Discussion started by: tonj
0 Replies

6. Cybersecurity

IPF pass in connection to port 21 even with no explicit rule

I'm running IPF on solaris 10 bash-3.00# ipf -V #display ipf version ipf: IP Filter: v4.1.9 (592) Kernel: IP Filter: v4.1.9 Running: yes Log Flags: 0 = none set Default: pass all, Logging: available Active list: 1 Feature mask: 0x107 with the following rules bash-3.00# ipfstat -o -i... (0 Replies)
Discussion started by: h@foorsa.biz
0 Replies

7. Infrastructure Monitoring

clstat X connection ... broken ?

Hi. Could you help me with this problem ? When I run clstat then I got this error message: 1:root@test1:/root # clstat X connection to localhost:10.0 broken (explicit kill or server shutdown). I got the same error for both nodes. If I would run xclstat I would understand that there... (5 Replies)
Discussion started by: phobus
5 Replies

8. UNIX Desktop Questions & Answers

Listening on localhost - cannot connect to host using port 3010

Hi Guys, my issue is - I have people connecting to my hosts from the outside world (for POC testing). There application listens on a port 3010 which is bound to the localhost. Using netstat -an | grep LISTEN it is the only port that is bound - ie: ftp, ssh etc listen on all interfaces. I need... (1 Reply)
Discussion started by: brian112
1 Replies

9. AIX

X connection to localhost:10.0 broken (explicit kill or server shutdown)

I want to run applet on AIX 6 machine. I already have setup $DISPLAY variable for putty session by selecting X11 option. I got below error for any X related commands (xclock, X, applet viewer ) X connection to localhost:10.0 broken (explicit kill or server shutdown). Please can anyone... (0 Replies)
Discussion started by: kailas.girase
0 Replies

10. SuSE

Connection is broken because of underlying network issues

Hi Guys, I have two databases where I copy archivelog files from server A to server B frequently...yesterday we did the VM upgrade now...I am struggling to copy/ship the files from server A to server B... I manually tested the file transfer but the big files, e.g 46M, stall. I can copy small... (2 Replies)
Discussion started by: Phuti
2 Replies
SLIRPVDE(1)						      General Commands Manual						       SLIRPVDE(1)

NAME
slirpvde - Virtual Distributed Ethernet-Slirp interface SYNOPSIS
slirpvde OPTIONS [ socketdir ] DESCRIPTION
slirpvde is a slirp interface for a VDE network. Slirpvde connects all the units (virtual or real machines) to the network of the host where slirpvde runs as it were a NAT/Masquerading router. The default route is the node 2 (10.0.2.2 in the default network configuration) and DNS is re-mapped in node 3 (10.0.2.3). Slirpvde runs using standard user privileges (no need for root access): all the connections are re-generated by slirpvde itself. IPv4 only. IPv6 is still unsupported (will be supported when slirpvde will be rewritten using the LWIPv6 network stack). OPTIONS
-s, --sock, --socket, --vdesock, --unix directory specify the VDE switch directory (default /var/run/vde.ctl). The VDE switch directory can be also specified at the end of the com- mand, as illustrated by the optional parameter socketdir in the synopsis section, above. When '-' is used in place of the VDE switch directory, slirpvde works as a plug (see vde_plug(1)). The command: dpipe vde_plug = ssh remote.machine.org slirpvde - which is the same as: dpipe vde_plug = ssh remote.machine.org slirpvde -s - connects the default local switch to a remote slirpvde. -p, --pidfile filename specify the name of the file which contains the PID of slirpvde. -g, --group group specify the UNIX group for the VDE communication socket. -m, --mod mode specify the octal UNIX permissions for the VDE communication socket. -P, --port port specify the port of the vde switch whern slirpvde must be connected. -d, --daemon detach from terminal and run slirpvde in background. -H, --host address [ / masklen ] specify the host address (default 10.0.2.2/24). This option automatically defines the network. e.g. -H 192.168.55.1 or: --host 10.1.2.3/16 The default value for masklen is 24. If the host part of the address is zero this option defines only the network. The default host addr is addr 2, the default dns proxy is 3. e.g. -H 10.1.0.0/16 defines the network only. The host address is 10.1.0.2 and the DNS proxy 10.1.0.3. -n, --network address [ / masklen ] specify the network address (default 10.0.2.0/24). Deprecated, it has been included for back compatibility only. It is an alias of -H, --host. -N, --dns address Specify the address of the dns server. If this is an address inside the slirp network, slirvde acts as a dns proxy on that address. The slirpvde dhcp server sends this dns address to the clients. By default this is the host number 3 in the slirpvde network. Using the default network it is 10.0.2.3. Warning: do not use the same address for host and dns. -D, --dhcp turn on the DHCP server for the network autoconfiguration of all the units connected to the VDE. It is possible to specify the start address assigned by the DHCP server as follows: --dhcp=10.1.1.44 DHCP assign addresses starting at host number 15 by default. Using the default network it starts from 10.0.2.15 -L port:vde_host:vde_hostport specifyes a TCP port redirection. All the TCP packets received by the host running slirpvde at port port will be forwarded to vde_host at port vde_hostport. -U port:vde_host:vde_hostport specifyes a UDP port redirection. All the UDP packets received by the host running slirpvde at port port will be forwarded to vde_host at port vde_hostport. -X vde_host[:display.[screen]]i redirect a X window screen of a virtual machine. Slirpvde gets the first unused X display on the host running slirpvde and redirects all the requests to vde_host. display and screen] must be specified when different from :0.0. -x port:unix_socket_path] redirect a port of the virtual router (usually 10.0.2.2) to a unix stream socket. It is used for example to redirect a X display of the hosting computer on the virtual network. e.g. -x6000:/tmp/.X11-unix/X0. (A suitable xhost configuration is needed (e.g. 'xhost local:'). -t, --tftp pathname slirpvde enables a tftp server sharing (read-only) the directory at pathname. -q, --quiet Quiet; do not write anything to standard output. NOTICE
Virtual Distributed Ethernet is not related in any way with www.vde.com ("Verband der Elektrotechnik, Elektronik und Informationstechnik" i.e. the German "Association for Electrical, Electronic & Information Technologies"). SEE ALSO
vde_switch(1), vde_plug(1), vde_plug2tap(1), dpipe(1). AUTHOR
VDE is a project by Renzo Davoli <renzo@cs.unibo.it>. This tool includes software developed by Danny Gasparovski: Slirp code is by Danny Gasparovsky. Bootp/DHCP code is by Fabrice Bellard. Virtual Distributed Ethernet June 15, 2008 SLIRPVDE(1)
All times are GMT -4. The time now is 12:39 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy