Hi, let me resend my request hoping there is the one who can point at the solution of the problem.
There are two machines: computer1 and computer2. Parameters of computer1: perl 5.6.1 sname=solaris, osvers=2.8, archname=sun4-solaris-thread-64int-ld DBI 1.41 DBI::ProxyServer 0.3005 DBD::Oracle 1.16 DBD::Proxy 0.2004 RPC::PlServer 0.2018 RPC::PlClient 0.2018 Storable 2.11 Parameters of computer2: perl 5.8.0 osname=linux, osvers=2.4.21-23.elsmp, archname=i386-linux-thread-multi DBI 1.48 DBI::ProxyServer 0.3005 DBD::Oracle 1.16 DBD::Proxy 0.2004 RPC::PlServer 0.2018 RPC::PlClient 0.2018 Storable 2.15 I have dbiproxy daemon running on computer1 with standard configuration. Unfortunately, from time to time while connecting from computer2 it crushes with an error: ====== Child died: Storable binary image v2.7 more recent than I am (v2.6) at blib/lib/Storable.pm (autosplit into blib/lib/auto/Storable/thaw.al) line 369 thread 373, at /usr/local/lib/perl5/site_perl/5.6.1/RPC/PlServer/Comm.pm line 179 thread 373 ====== After that I have to restart daemon to make dbiproxy work again. Why is that? Which modules these versions (2.7 and 2.6) concern? Both Storable modules have different versions. How can I avoid it? There is also one interesting thing. I have two identical scripts on computer1 and computer2 testing my dbiproxy connection. Let's call them testproxy_comp1.pl and testproxy_comp2.pl. After restarting dbiproxy deamon testproxy_comp2.pl fails because of: ====== Cannot log in to DBI::ProxyServer: Unexpected EOF from server at /usr/lib/perl5/site_perl/5.8.0/RPC/PlClient.pm line 79' ====== Then I run testproxy_comp1.pl and it is OK. After that I run testproxy_comp2.pl again and now it runs with no errors. Is anybody able to explain that strange situation? Thank you for your help in advance. Wojciech Pietron
