jBase journaling issue (jlogdup)

Hello,

I'm trying to synchronize jBase journal logset on Server2 with Journal logset on Server1. Regarding to the jBase documentation I must configure listener at first (Server2) and then run jlogdup on Server1:

on Server2:
jlogdup input set=socket hostname=localhost port=4089 output set=logset

on Server1:
jlogdup input set=current output set=socket hostname=Server2 port=4089

But first command (on Server2) returns error "bind: Address already in use Unable to bind() socket, error 0".

My question is - what I must use instead of "socket" ?

Hi
looks like the port 4089 is already in use.

Hi,

Yes, you are right. That's happened because I've executed command (jlogdup on Server2) and then terminated (Ctrl+C, do you have any idea how to terminate it normally?).
Closing and opening new session helped.

Now I'm trying to execute jlogdup on Server2, error occurs:
Unable to connect to host 10.10.10.198 , error 111
connect: Connection refused

Firewall (centos) is turned off on both servers.

Hi
After Ctrl-C look at the processes list (ps -ef) and issue the command kill PID, where PID is jlgdup's process ID. I'm not sure how to do it "normally" but kill (without -9 parameter) shall do it all right. (but that's probably what you already used)

For "connection refused" I'm not sure what's the reason; can you connect to other ports? Like to SSH using SSH client?

It also could be that "small" port numbers are reserved for system services; you can try to use something like 20001 etc.

If nothing helps, mount the file system of server2 at server 1 remotely (you can use SSHFS, for example) and redirect the journal there without "socket" usage.

Hi,

VK, but generally - is it right way to synchronize jbase journal logsets?

on Server2:
jlogdup input set=socket hostname=localhost port=4089 output set=logset

on Server1:
jlogdup input set=current output set=socket hostname=Server2 port=4089

Hi
I haven't tried this particular setup myself.. Maybe it's better if you ask Temenos.
It's better if you try the basic setup first (on one server) if you haven't tried that yet...

Hi,

I've tried jlogdup on one server — it's works.

Hi
I don't even see the "socket" option at jBase knowledgebase documentation... New owners just changed the logo but some documentation haven't been updated for years... I think you can try to output the journal to remote file system as I suggested before.

I wasn't completely right... The documentation hadn't been updated for decades :)))

jBase patch PN4_10445

2005/01/12

Initial socket implementation for jlogdup

:))

I think you can try to output the journal to remote file system as I suggested before.

Where I can read about this method (output the journal to remote file system)? Is any docs available on the web?

Hi
the method is the same as to output log to local log files... You need to mount the remote file system (you're under Linux, aren't you?) and then to create log files there. On a remote server then you can apply this log as often as you can to keep the hot (or not so hot) replication DB.