Error posted below - still thinking along the lines of ports...!?
port 8446 is open/listening.
Code:
2013-07-02 10:51:27,129 TRACE [org.jboss.remoting.transport.socket.ServerThread.processInvocation] preparing to process next invocatio
n invocation
2013-07-02 10:51:27,129 TRACE [org.jboss.remoting.transport.socket.ServerThread.readVersion] blocking to read version from input strea
m
2013-07-02 10:51:27,203 TRACE [org.jboss.remoting.transport.socket.ServerThread.dorun] SocketException received. This is likely due to
client disconnecting and resetting connection.
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:168)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2196)
at java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2376)
at java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:2443)
at java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2515)
at java.io.ObjectInputStream.read(ObjectInputStream.java:800)
at org.jboss.remoting.transport.socket.ServerThread.readVersion(ServerThread.java:824)
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:510)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
2013-07-02 10:51:27,204 DEBUG [org.jboss.remoting.transport.socket.ServerThread.dorun] WorkerThread#0[xx.xx.xx.xx1419] closing socketW
rapper: ServerSocketWrapper[Socket[addr=/xx.xx.xx.xx,port=1419,localport=8446].2909a1]
2013-07-02 10:51:27,204 DEBUG [org.jboss.remoting.transport.socket.ServerSocketWrapper.close] unable to writing CLOSING byte
java.net.SocketException: Broken pipe
That maybe a red herring, after investigating further the final message logged to the server.log is actually a timeout:
Hi all - i currently run a domain strifex.net. This domain has a dedicated IP address and in having that, should be able to run a ventrilo VoIP server from it. I uploaded all the needed files etc... and am able to connect to it, if and only if i enable DMZ to my local machine - then i am able to... (1 Reply)
I need some help with a project I am working on.
I am writing a database application to manage some access lists. While this is for internal use only, the IT infrastructure is US Army managed. This severely limits which software I am allowed to use. I have a RHEL v5.2 server which uses some... (2 Replies)
Hi Guys,
RHEL 4.4
I was reviewing an app failure on one of our hosts and I encountered this entry on syslog:
Feb 22 08:54:46 saturn-host rc: Starting start_server_daemon: succeeded
there's timestamp, saturn-host is the servername, rc is the linux rc wrapper script, "Starting" is on... (1 Reply)
Hi,
I am trying to close all possible ports on my solaris and linux servers.
I am stuck on the following ports on both Solaris 10 (local zone) and Linux (Suse) servers.
Here is nmap output :
PORT STATE SERVICE
22/tcp open ssh
80/tcp open http
1720/tcp open H.323/Q.931... (6 Replies)
Hi,
I'm using RHEL 4.5, and currently due to some special circumstances that required me to use this small monitor about 7"
The problem is while using this monitor with windows, the monitor able to show the graphic/view.. but while using redhat it unable to detect. This monitor has no... (7 Replies)
nmap is a network utility which gives u information about open ports on ur system. for eg
$ nmap 10.226.112.202
PORT STATE SERVICE
7/tcp open echo
13/tcp open daytime
22/tcp open ssh
23/tcp open telnet
37/tcp open time
1100/tcp open unknown
these open... (2 Replies)
Dear All ,
One of our Oracle Database Server , which got hanged a couple of days before , so that we could not login to the Server , but it was pinging.
So we tried various options and at last we did a reboot of this server.
To find out the root cause of the Server Hang , when i checked the... (2 Replies)
Hi All
On one of my sandbox machine, I want to replace RHEL 6.2 to RHEL 7.3.
I am using both developer editions.
rhel-server-7.3-x86_64-dvd.iso ... This is what I have downloaded from
Red Hat Enterprise Linux Download | Red Hat Developers
My understanding is this file would work as a... (1 Reply)
Discussion started by: videsh77
1 Replies
LEARN ABOUT CENTOS
ksc
KSC(1) User Commands KSC(1)NAME
ksc - Linux kernel module source checker
SYNOPSIS
ksc [ -d | --directory ] DIRECTORY
ksc [ -k | --ko ] FILE
OPTIONS
KSC accepts command-line arguments, and has both a long and short form usage. You can use either style or combine them to specify
options. When the tool is run with kernel module sources it checks for all four architectures, and when run with binary kernel modules, it
checks for the specific architecture for which the binary was built.
Valid RHEL whitelist releases are rhel6.0, rhel6.1, rhel6.2, rhel6.3, rhel6.4
-h, --help
show this help message and exit
-c CONFIG, --config=CONFIG
path to the local ksc.conf file. If not specified the tool tries to read from ~/ksc.conf and if that is also not found then from
/etc/ksc.conf
-d DIRECTORY, --directory=DIRECTORY
path to the directory
-i, --internal
to create text files to be used internally.
-k KO, --ko=KO
path to the ko file. You should either use -d or -k to run the KSC tool, but not both. If both -d and -k option is used at the
same time then only -d is used and the -k option is discarded.
-n RELEASENAME, --name=RELEASENAME
Red Hat release against which the bug is to be filed. Default value is 6.5
-p PREVIOUS, --previous=PREVIOUS
path to the previous resultset file and submit it as a bug to Red Hat Bugzilla.
-r RELEASE, --release=RELEASE
RHEL whitelist release used for comparison
-s, --submit
Submits the report to the Red Hat bugzilla (https://bugzilla.redhat.com). The credentials need to be in the /etc/ksc.conf file. The
tool will prompt for bugzilla password.
The configuration file looks like below:
[bugzilla]
user=user@redhat.com
partner=partner-name
partnergroup=partner-group
server=https://bugzilla.redhat.com/xmlrpc.cgi
-v, --version
Prints KSC version number
ksc - Version 0.9.11 Feb 2014 KSC(1)