Hi,
These are some last lines of jlogdup logfile
10*1*1329824679*1372153745 WRITE /jbase/jspooler/jspool_log
DEVCONFIG*9627
10*1*1329824897*1372153745 WRITE /jbase/jspooler/jspool_log
DEVCONFIG*9172
0*0*0*1372153746
EOF
11:49:06 25 JUN 2013 : STATUS:
Termination Statistics: usr 1016.14 , sys 3621.59 , elapsed 161m17.05
INPUT : 35829722 records , 0 blocks , -322285481 record bytes , 0 errors
OUTPUT: 0 records , 5196925 blocks , 0 bytes , 0 errors
11:49:06 25 JUN 2013 : STATUS:
Program terminated. Exit code is 0
Can You see EOF ??? - jlogdup was started with terminate=wait
Piotr
W dniu sobota, 8 czerwca 2013 14:36:02 UTC+2 użytkownik VK napisał:
>
> > looks like a simple end of the ssh session
>
> Just a thought... is your ssh client configured to have keepalive on?
>
>
> On Jun 5, 9:16 am, My_jBase <[email protected]> wrote:
> > Hello,
> >
> > This appears to be a problem with the option terminate=wait. After
> > restarting the jlogdup process operates as long as it's rewriting data
> from
> > logset to the remote database - it stops working as soon as it's done
> > rewriting the data, It terminates at the moment when it comes to the
> > end, although the journal process is still active.
> >
> > What should I do ?
> > Piotr
>
--
--
IMPORTANT: T24/Globus posts are no longer accepted on this forum.
To post, send email to [email protected]
To unsubscribe, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/jBASE?hl=en
---
You received this message because you are subscribed to the Google Groups
"jBASE" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
