On 2023-02-04, Haines Brown wrote:
> - Forwarded message from Greg Wooledge -
>
> Date: Thu, 2 Feb 2023 08:57:30 -0500
> From: Greg Wooledge
> To: debian-user@lists.debian.org
> Subject: Re: Fw: locating blocked port
>
> I finally managed to get jabref to ru
- Forwarded message from Greg Wooledge -
Date: Thu, 2 Feb 2023 08:57:30 -0500
From: Greg Wooledge
To: debian-user@lists.debian.org
Subject: Re: Fw: locating blocked port
I finally managed to get jabref to run.
I looked at waht aprocess was using the PIS as you suggest.
$ ps -fp
On Thu, Feb 02, 2023 at 08:48:43AM -0500, Haines Brown wrote:
> Now the quetion is, what process is using that port?
>
>$ sudo ss -pt state listening 'sport = :6050'
>Recv-Q Send-Q Local Address:Port Peer Address:Port Process
>0 1 [:::127.0.0.1]:6050 *:*
After stumblin about and wasting people's time. I may have made some
progress.
First was the kind help that the jabref port can be found by searching
on line for "net.sf.jabref.logic.remote.server" Remote port number".
Doing so revealed that jabref's default port is probably 6050. I
wouild nev
On Wed, Feb 1, 2023 at 5:24 PM wrote:
>
> [...]
> Begin forwarded message:
>
> Date: Wed, 1 Feb 2023 06:09:32 -0500
> From: Haines Brown
> To: debian-u...@howorth.org.uk
> Subject: Re: locating blocked port
>
> On Tue, Jan 31, 2023 at 10:09:28PM +, debi
s may end up in my bitbucket soon.
Begin forwarded message:
Date: Wed, 1 Feb 2023 06:09:32 -0500
From: Haines Brown
To: debian-u...@howorth.org.uk
Subject: Re: locating blocked port
On Tue, Jan 31, 2023 at 10:09:28PM +, debian-u...@howorth.org.uk
wrote:
> Haines Brown wrote:
> >
This ENTIRE THREAD is a gigantic cautionary tale for developers. This is
why trying to minimize the amount of information present in your error
messages is NOT helpful.
The Microsoft paradigm of "don't show technical details in error messages
because it will scare the users" is bullshit. But to
Hello
On 2023-01-31 16:05, Haines Brown wrote:
I have an application that refuses to start because its port is
blocked. But I have difficulty knowing what port it is
$ java -jar /usr/local/share/JabRef/JabRef-3.2.jar &
[1] 4831
haines@lenin:~$ Jan 31, 2023 8:36:39 AM
net.sf.jabref.logi
On Tue, Jan 31, 2023 at 03:51:20PM -0500, Haines Brown wrote:
> On Tue, Jan 31, 2023 at 12:13:03PM -0500, Henning Follmann wrote:
>
> > I think this is just futile. Why would you do all this painful stuff,
> > which might not get you close to what you really want - running that app.
>
> Are you
Le 31/01/2023 à 16:31, Casey Deccio a écrit :
On Jan 31, 2023, at 8:05 AM, Haines Brown wrote:
I have an application that refuses to start because its port is
blocked. But I have difficulty knowing what port it is
I would try strace, which shows you all system calls being made. In this
Haines Brown wrote:
> $ jabref
> 15:43:56.614 [AWT-EventQueue-0] WARN
> net.sf.jabref.logic.remote.server.RemoteListenerServerLifecycle -
> Port is blocked
> java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind0(Native Method) ~[?:?]
> at sun.nio.
On Tue, Jan 31, 2023 at 12:13:03PM -0500, Henning Follmann wrote:
> I think this is just futile. Why would you do all this painful stuff,
> which might not get you close to what you really want - running that app.
Are you implying the problem should not occur?
> For now I just assume you insta
On Tue, Jan 31, 2023 at 11:30:02AM -0500, Haines Brown wrote:
> On Tue, Jan 31, 2023 at 08:31:38AM -0700, Casey Deccio wrote:
> >
> >
> > > On Jan 31, 2023, at 8:05 AM, Haines Brown wrote:
> > >
> > > I have an application that refuses to start because its port is
> > > blocked. But I have d
On Tue, Jan 31, 2023 at 10:05:12AM -0500, Haines Brown wrote:
> I have an application that refuses to start because its port is
> blocked. But I have difficulty knowing what port it is
>
>$ java -jar /usr/local/share/JabRef/JabRef-3.2.jar &
> [1] 4831
> haines@lenin:~$ Jan 31, 2023 8:36
On Tue, Jan 31, 2023 at 08:31:38AM -0700, Casey Deccio wrote:
>
>
> > On Jan 31, 2023, at 8:05 AM, Haines Brown wrote:
> >
> > I have an application that refuses to start because its port is
> > blocked. But I have difficulty knowing what port it is
> I would try strace, which shows you all
> On Jan 31, 2023, at 8:05 AM, Haines Brown wrote:
>
> I have an application that refuses to start because its port is
> blocked. But I have difficulty knowing what port it is
I would try strace, which shows you all system calls being made. In this case,
it is probably bind() that is ret
Hi,
Haines Brown wrote:
> I have an application that refuses to start because its port is
> blocked. But I have difficulty knowing what port it is
>
[...]
>
> $ strings $(which jabref) | wc -l
> 56
This "56" does NOT mean, jabref is listening on Port 56.
It only means, that the jabre
On Tue, 31 Jan 2023 10:05:12 -0500
Haines Brown wrote:
> I have an application that refuses to start because its port is
> blocked. But I have difficulty knowing what port it is
>
>$ java -jar /usr/local/share/JabRef/JabRef-3.2.jar &
> [1] 4831
> haines@lenin:~$ Jan 31, 2023 8:36:39 A
> On Jan 31, 2023, at 8:05 AM, Haines Brown wrote:
>
> I have an application that refuses to start because its port is
> blocked. But I have difficulty knowing what port it is
I would try strace, which shows you all system calls being made. In this case,
it is probably bind() that is ret
I have an application that refuses to start because its port is
blocked. But I have difficulty knowing what port it is
$ java -jar /usr/local/share/JabRef/JabRef-3.2.jar &
[1] 4831
haines@lenin:~$ Jan 31, 2023 8:36:39 AM
net.sf.jabref.logic.remote.server.Remote
ListenerServerLifecycl
20 matches
Mail list logo
