Hi Josep
On May 24, 2006, at 10:50, [EMAIL PROTECTED] wrote:
Hi Christian. Thanks for the quick reply.
Let's see...
About the registration, we are in contact with SWREG and I hope to
get it
today. No probs there.
About using keychain, as a matter of fact we do. The script updates
plugins
in several servers, and the user only validates against the first
one. We
cannot store permanently the password for security reasons.
The keychain is not 100% secure, but it's MUCH better than having a
password in clear text in a script. If you always provide the
password interactively, that's even more secure, of course.
And last, my problem. I've activated debug and tried to reproduce the
problem, both whith cp and rsync. I have separate debug files for each
case, which I've attached to this e-mail.
Thanks! Next time you send log files, please send them in private e-
mail directly to me, for privacy reasons and because most list
members won't be interested in the 2 MB attachment.
[...]
I've looked at your log. The point where it stops is a write to the file
es.liberty.isis.comun_1.0.0\lib\.ComercialEJB.jar.Wta4Hn
The relevant lines are (function performed by thread 8 and on behalf
of thread 8):
366.639 8 cifsrpc/trace: writeAndX srv=0x00194a98 as uid=4098
tid=4097 fid=32790 offset=0x5c000 numIov=1
486.608 0 cifsserver/db0: cifsserver: RPC timeout occurred,
disconnecting server
486.608 0 oderrorcfg/trace: odErrorCfgCreate: created error
CIFSMOD_ERR_SMBTIMEOUT
486.608 0 cifsserver/db1: cifsserver: rx thread terminating for
srv=0x00194a98
486.608 0 main/db0: sending GUI update; reason=user auth mech changed
due to lost connection
486.608 0 odsocket/fd: closing fd=11 [stream socket, disconnect]
486.608 8 cifsrpc/trace: writeAndX returns error: CIFSMOD_ERR_SMBTIMEOUT
486.608 8 nfsmnt/trace: *** nfs3 return NFS2ERR_ACCES [-274081335].
The server has not sent a reply to the write for 2 mintes. This
usually indicates that the server crashed. Can you confirm that? What
type of server is this? Which operating system?
In any case we can track it down to a problem on the server. You
should be able to find more info in the server's log.
Regards, Christian.
--
DI Christian Starkjohann <[EMAIL PROTECTED]>
OBJECTIVE DEVELOPMENT Software GmbH
_______________________________________________
Sharity-talk mailing list
[email protected]
To unsubscribe see http://at.obdev.at/mailman/listinfo/sharity-talk
