Verity "java.io.IOException: Read timed out" error?
ColdFusion, VerityHi anyone,
On CF 8.01 (CHF 2), Enterprise 64-bit, multi-server on Red Hat 5.3 I'm getting the following error whenever I try to do any action with a Verity collection:
An error occurred while performing an operation in the Search Engine library.
Error switching collection offline.: com.verity.api.administration.ConfigurationException: java.io.IOException: Read timed out
- By "anything", I mean creating, optimizing, deleteing, reindexing, etc. from the CF Admin or regular CF code.
- I've restarted CF and Verity multiple times to make sure it wasn't that
- I tried on 2 different machines, each with the same exact setup and config, and it happens on both, so I don't think it's specific to a machine
- I tried using the /tmp directory, which has pretty much full rights, as the path for creating some brand new indexes, but still get the error
- The strange thing is that this wasn't happening about 4 weeks ago, so I'm thinking this is probably an O/S (RHEL 5.3, 64-bit) update issue, or perhaps occurred when I applied CHF 2 for CF 8.01 a few weeks ago, though there's nothing about Verity in it.
Any ideas what it could be or what to try next? I'll be calling Adobe support shortly, but wanted to see if any of my blog followers had an idea?
TIA
David said:
Did you ever get anywhere with this? I've just noticed the same thing on MX7 but we're already doing everything in serial in the background so the other posts I've read on this issue aren't really appropriate.
Any update on your issues?
Thanks,
D
Any update on your issues?
Thanks,
D
cfZen said:
@David - I didn't think anyone read this post, so I didn't update it with what I'd found... Here goes:
It took manual intervention, where I deleted the collections stored on disk, and then updated the data xml file. Here's the linux commands I cobbled together, and now it all works. It seems that after about 60 or 70 collections are made, the errors start happening. So, keep the number of collections as low as you can:
sudo /opt/jrun4/verity/bin/cfsearch stop
sudo mv /opt/jrun4/verity/Data/host/admin/ /opt/jrun4/verity/Data/host/admin_bak1
sudo mkdir /opt/jrun4/verity/Data/host/admin
sudo chown nobody /opt/jrun4/verity/Data/host/admin
sudo cp /opt/jrun4/verity/Data/host/admin_bak1/admin0.xml /opt/jrun4/verity/Data/host/admin/admin0.xml
sudo chown nobody /opt/jrun4/verity/Data/host/admin/admin0.xml
sudo chown peoplexs /opt/jrun4/verity/Data/host/admin/admin0.xml
sudo chmod 777 /opt/jrun4/verity/Data/host/admin/admin0.xml
(use WinSCP to edit admin0.xml: remove all XML nodes in, and from )
sudo chown nobody /opt/jrun4/verity/Data/host/admin/admin0.xml
sudo rm -r /opt/jrun4/verity/collections/
sudo mkdir /opt/jrun4/verity/collections/
sudo chown nobody /opt/jrun4/verity/collections/
sudo /opt/jrun4/verity/bin/cfsearch start
It took manual intervention, where I deleted the collections stored on disk, and then updated the data xml file. Here's the linux commands I cobbled together, and now it all works. It seems that after about 60 or 70 collections are made, the errors start happening. So, keep the number of collections as low as you can:
sudo /opt/jrun4/verity/bin/cfsearch stop
sudo mv /opt/jrun4/verity/Data/host/admin/ /opt/jrun4/verity/Data/host/admin_bak1
sudo mkdir /opt/jrun4/verity/Data/host/admin
sudo chown nobody /opt/jrun4/verity/Data/host/admin
sudo cp /opt/jrun4/verity/Data/host/admin_bak1/admin0.xml /opt/jrun4/verity/Data/host/admin/admin0.xml
sudo chown nobody /opt/jrun4/verity/Data/host/admin/admin0.xml
sudo chown peoplexs /opt/jrun4/verity/Data/host/admin/admin0.xml
sudo chmod 777 /opt/jrun4/verity/Data/host/admin/admin0.xml
(use WinSCP to edit admin0.xml: remove all XML nodes in
sudo chown nobody /opt/jrun4/verity/Data/host/admin/admin0.xml
sudo rm -r /opt/jrun4/verity/collections/
sudo mkdir /opt/jrun4/verity/collections/
sudo chown nobody /opt/jrun4/verity/collections/
sudo /opt/jrun4/verity/bin/cfsearch start
.: HIDE REPLIES :.
cfZen said:
make that (use WinSCP to edit admin0.xml: remove all XML nodes in [Collections], and from [CollRefs])
David said:
Hi,
I ended up clearing out the verity workspace and collections and it all came back to life. Although the error has now gone, I'm not sure I really know the root cause of this though which annoying.
Thanks for getting back to me,
D
I ended up clearing out the verity workspace and collections and it all came back to life. Although the error has now gone, I'm not sure I really know the root cause of this though which annoying.
Thanks for getting back to me,
D
David Stockton said:
Hi,
The problem for me was that the work-space files had somehow become corrupt (I think during a CF7toCF8 upgrade).
I stopped all the CF services, deleted the following files:
cf8\verity\Data\services\ColdFusionK2_indexserver1\ws
... then re-created the collections from scratch.
The company I work for offer CF consulting and we'd be happy to help you solve your issues if you'd like some help with this...
http://www.cfconsultant.com/
@cfZen: Please feel free to edit this comment if you're not happy with me posting a commercial web-address here.
The problem for me was that the work-space files had somehow become corrupt (I think during a CF7toCF8 upgrade).
I stopped all the CF services, deleted the following files:
cf8\verity\Data\services\ColdFusionK2_indexserver1\ws
... then re-created the collections from scratch.
The company I work for offer CF consulting and we'd be happy to help you solve your issues if you'd like some help with this...
http://www.cfconsultant.com/
@cfZen: Please feel free to edit this comment if you're not happy with me posting a commercial web-address here.
.: HIDE REPLIES :.
ffonky said:
Hi thanks for the prompt answer.
ok let me tell you the whole story:
We have installed Reddot Liveserver 9 with verity
on SUSE Linux Enterprise Server 10 (x86_64).
Tis are our enveronment:
Using CATALINA_BASE: /usr/share/tomcat5_liveserver
Using CATALINA_HOME: /usr/share/tomcat5_liveserver
Using CATALINA_TMPDIR: /usr/share/tomcat5_liveserver/temp
Using JRE_HOME: /usr/java/jdk1.5.0_10/
Server version: Apache Tomcat/5.5.27
Server built: Aug 28 2008 10:08:26
Server number: 5.5.27.0
OS Name: Linux
OS Version: 2.6.16.21-0.8-smp
Architecture: amd64with the following details.
apache2-2.2.10-23.1
mod_jk-ap20-4.1.30-6.1.20060203
On 3 of the same Machines types and operating systems and environment with the same configuration the verity indexing is working fine.
It�s only on this machine that i�m having this problem.
Open text is saying they don�t support verity on
SUSE Linux Enterprise Server 10 (x86_64) so i should migrate the verity to 32bit system (no support on this issue then)
I have check the environment variables, set chmod -R 755 on the verity_home, uninstall and install liveserver, uninstall and install verity, tried your steps but it�s still not working.
Do you have any ideals which I should try.
How will your support be?
Thanks
frank
ok let me tell you the whole story:
We have installed Reddot Liveserver 9 with verity
on SUSE Linux Enterprise Server 10 (x86_64).
Tis are our enveronment:
Using CATALINA_BASE: /usr/share/tomcat5_liveserver
Using CATALINA_HOME: /usr/share/tomcat5_liveserver
Using CATALINA_TMPDIR: /usr/share/tomcat5_liveserver/temp
Using JRE_HOME: /usr/java/jdk1.5.0_10/
Server version: Apache Tomcat/5.5.27
Server built: Aug 28 2008 10:08:26
Server number: 5.5.27.0
OS Name: Linux
OS Version: 2.6.16.21-0.8-smp
Architecture: amd64with the following details.
apache2-2.2.10-23.1
mod_jk-ap20-4.1.30-6.1.20060203
On 3 of the same Machines types and operating systems and environment with the same configuration the verity indexing is working fine.
It�s only on this machine that i�m having this problem.
Open text is saying they don�t support verity on
SUSE Linux Enterprise Server 10 (x86_64) so i should migrate the verity to 32bit system (no support on this issue then)
I have check the environment variables, set chmod -R 755 on the verity_home, uninstall and install liveserver, uninstall and install verity, tried your steps but it�s still not working.
Do you have any ideals which I should try.
How will your support be?
Thanks
frank
David Stockton said:
Can you solve the problem but then the collections become corrupt after a short-time or can you not get the collections working at all?
Did you clear out all the work-space files from all the verity "servers"?
We wouldn't have the resources to be able to support you in that environment although we are very experienced in document management and know opentext.
If you're still unable to get anything working I'd try and find an opentext/verity consulting company who can help you.
Did you clear out all the work-space files from all the verity "servers"?
We wouldn't have the resources to be able to support you in that environment although we are very experienced in document management and know opentext.
If you're still unable to get anything working I'd try and find an opentext/verity consulting company who can help you.
.: HIDE REPLIES :.
frank said:
Interesten it will create the collection in the colls directory but within 60 secs. there will be rollback.
In the status.log:
Warning: /usr/share/tomcat5_liveserver/webapps/ROOT/WEB-INF/lib/se/verity/k2/_ilnx21/bin/mkvdk -collection /usr/share/tomcat5_liveserver/webapps/ROOT/WEB-INF/lib/se/verity/data/colls/rdls_tmp_demo_v_de_i_0 -create -style /usr/share/tomcat5_liveserver/webapps/ROOT/WEB-INF/lib/se/verity/data/stylesets/rdlsss_rdls_tmp_demo_i_0 -locale uni failed to exit within 60 seconds. Shutdown the process.
When I try to create this manually it works.
/usr/share/tomcat5_liveserver/webapps/ROOT/WEB-INF/lib/se/verity/k2/_ilnx21/bin/mkvdk -collection /usr/share/tomcat5_liveserver/webapps/ROOT/WEB-INF/lib/se/verity/data/colls/rdls_tmp_demo_v_de_i_0
There is also in the audit.log this:
2009-08-19 12:28:33 anonymous FAILED:(-6220) K2AdminIndexCreate
That means ther is a problem wit the script if it doesn�t end within 60 secs but don�t know where to look for.
Thanks
frank
In the status.log:
Warning: /usr/share/tomcat5_liveserver/webapps/ROOT/WEB-INF/lib/se/verity/k2/_ilnx21/bin/mkvdk -collection /usr/share/tomcat5_liveserver/webapps/ROOT/WEB-INF/lib/se/verity/data/colls/rdls_tmp_demo_v_de_i_0 -create -style /usr/share/tomcat5_liveserver/webapps/ROOT/WEB-INF/lib/se/verity/data/stylesets/rdlsss_rdls_tmp_demo_i_0 -locale uni failed to exit within 60 seconds. Shutdown the process.
When I try to create this manually it works.
/usr/share/tomcat5_liveserver/webapps/ROOT/WEB-INF/lib/se/verity/k2/_ilnx21/bin/mkvdk -collection /usr/share/tomcat5_liveserver/webapps/ROOT/WEB-INF/lib/se/verity/data/colls/rdls_tmp_demo_v_de_i_0
There is also in the audit.log this:
2009-08-19 12:28:33 anonymous FAILED:(-6220) K2AdminIndexCreate
That means ther is a problem wit the script if it doesn�t end within 60 secs but don�t know where to look for.
Thanks
frank
Loading....