[ome-users] web client Image display and export error

Ilya Goldberg igg at nih.gov
Fri Oct 7 16:29:43 BST 2005


On Oct 6, 2005, at 2:25 PM, McCaughey, Michael J wrote:

> I have encountered two small problems running OME web client and I'm  
> looking for help.
>
> First, if I try to export an image using the web client, I get the  
> following error:
> Error serving OME::Web::XMLFileExport: /usr/bin/xsltproc returned  
> non-zero exit status: 1024
> warning: failed to load external entity "/OME/xml/OME-CA2OME.xslt"
> cannot parse /OME/xml/OME-CA2OME.xslt
>
> Alas, for disk reasons I had to install OME in /home/OME, not /OME.  
> This file is located in /home/OME/xml. I've deleted and reinstalled  
> the distribution a few times, but cannot correct this error. Any  
> ideas?

We don't have a lot of experience with non-/OME installations  
unfortunately.  You might try this:
psql ome
ome=# select value from configuration where name = 'xml_dir';

If this returns /OME/xml, then you may be able to fix it by manually  
resetting the XML directory:
ome=# update configuration set value = '/home/OME/xml' where name =  
'xml_dir';

Probably a scan through the rest of the configuration settings wouldn't  
hurt to make sure other directories are set properly:
ome=# select * from configuration;


>
> My second problem involves image thumbnails; they do not appear on web  
> client screen. The page generated by serve.pl includes:
> <img  
> src="http://localhost.localdomain/cgi-bin/omeis? 
> Method=GetThumb&PixelsID=1" Usemap="#Image1">
>
> which implies that serve.pl is returning localhost.localdomain for the  
> server hostname. uname -n and hostname commands return the correct  
> FQDN for the server. Where does serve.pl get the host info?

I'm not sure how this happened, because the installer uses the hostname  
command (or, perl's equivalent of it) to get the default hostname.   
Also, it asks for confirmation of the OMEIS URL.
You can change this manually after the fact as well.
psql ome
ome=# select * from repositories;
ome=# update repositories set  
image_server_url='http://my.host.edu/cgi-bin/omeis' where  
image_server_url = 'http://localhost.localdomain/cgi-bin/omeis';

Note that changing these things manually in the database introduces an  
inconsistency between the database and the settings stored in  
/etc/ome-install.store.  Next time you install (i.e. update), the  
defaults will come from /etc/ome-install.store and not from the DB.  If  
you change the settings in the installer from the defaults provided,  
then the settings will be made consistent, but then maybe your  
installation will not work again?

You can manipulate the binary /etc/ome-install.store file manually as  
well by first dumping a text version of it:
perl -MData::Dumper -MStorable -e 'print  
Dumper(retrieve("/etc/ome-install.store"))' > ome-install.eval
edit the ome-install.eval file, which is plain text, then re-compile it  
to the binary file:
perl -MStorable -e 'eval `cat ome-install.eval`; store  
($VAR1,"/etc/ome-install.store")'


It would be a great service to us if you could register bugs in  
bugzilla (http://bugs.openmicroscopy.org.uk/) for the parts of your  
system that do not appear to be working with an installation in a  
non-/OME location (the XML bug, and any others you encounter).

Thanks
Ilya



>
> Thanks,
> Mike
>
> 	
> _______________________________________________
> ome-users mailing list
> ome-users at lists.openmicroscopy.org.uk
> http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-users




More information about the ome-users mailing list