Aaron Birkland <birkland@...> writes: > > > > Hey Aaron, just thought I'd let you know I was able to get multicast > > journaling to work on two W2K8 Server VMs without any problems. That > > pretty much confirms that my previous issues are with how I've got the > > Ubuntu VMs configured. > > That makes sense. Looking at the log, the first instance of a journal > failure contains: > java.rmi.ConnectException: Connection refused to host: 127.0.1.1; > > The journalling code will throw an exception every time it tries to > write to a transport that had failed open() - your original exception > included one of these subsequent exceptions. At the NSDL, we configure > log4j to write journal messages to a separate appender - one that will > e-mail the first error, and ignore the rest. Generally, the most useful > journal exceptions occur at the opening or closing of a journal file. > > -Aaron > > ------------------------------------------------------------------------------ > Return on Information: > Google Enterprise Search pays you back > Get the facts. > http://p.sf.net/sfu/google-dev2dev >
Dear All, I know this is an old thread. But I got exactly the same problem with Journal Receiver 3.4 . I tested with the same master server with 3 follower servers one by one. Only Windows one can have journal files written on the journal folder. The two Linux just showing the info below. And the repository becomes read only in the second save attempt. 21:13:40.128 [main] INFO o.f.s.j.r.m.rmi.RmiJournalReceiver - RmiJournalReceive r is ready - journal directory is '/j' In the Windows machine, more log message will be displayed when there are journal files writing to disk. I tried not starting Journal receiver at all. Then the master cannot start. That means my master server knows that there is a journal receiver running but it just not able to write file?... I ran the journal receiver using root account so it should be able to write to any folder.. Please help... thank you... Regards, Lai. ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Fedora-commons-users mailing list Fedora-commons-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
