Re: [OpenSER-Users] Strange OpenXCAP behaviour in virtualizedenvironment

Dear all I finally found the mistake: My VMWare ESX server for virtualization is not connected to the internet, my local PC was. It didn't come to my mind ever before. Although - I never saw it documented anywhere, that OpenXCAP needs internet access for downloading the namespace files. I would _really_ recommend to add this to the installations instructions on openxcap.org. Have a nice weekend! Sebastian ________________________________ From: Schumann Sebastian Sent: Friday, 11. January 2008 11:54 AM To: users(a)openser.org Subject: [OpenSER-Users] Strange OpenXCAP behaviour in virtualizedenvironment Dear all This week, I tried again to bring up finally the OpenXCAP server. I tried it first acc. the instruction on OpenXCAP.org on my local virtual VMWare Server 1.0 (before, I always used virtualized ESX server). It worked without major issues, meaning I could install lenny, all required files even via apt-get and the OpenXCAP was running. Surprising for me though, because it never worked yet. Now, when I take _the same_ virtual disk and export it to VMWare ESX server, I get the previously discussed errors: Sep 25 17:01:21 openxcap openxcap[11876]: [-] Log opened. Sep 25 17:01:21 openxcap openxcap[11876]: [-] Starting Open XCAP 0.9.3 Sep 25 17:01:27 openxcap openxcap[11876]: [-] Traceback (most recent call last): Sep 25 17:01:27 openxcap openxcap[11876]: [-] File "/usr/bin/openxcap", line 56, in ? Sep 25 17:01:27 openxcap openxcap[11876]: [-] from xcap.server import XCAPServer Sep 25 17:01:27 openxcap openxcap[11876]: [-] File "/usr/lib/python2.4/site-packages/xcap/server.py", line 21, in ? Sep 25 17:01:27 openxcap openxcap[11876]: [-] from xcap import authentication Sep 25 17:01:27 openxcap openxcap[11876]: [-] File "/usr/lib/python2.4/site-packages/xcap/authentication.py", line 21, in ? Sep 25 17:01:27 openxcap openxcap[11876]: [-] from xcap.appusage import getApplicationForURI Sep 25 17:01:27 openxcap openxcap[11876]: [-] File "/usr/lib/python2.4/site-packages/xcap/appusage/__init__.py", line 466, in ? Sep 25 17:01:27 openxcap openxcap[11876]: [-] applications = {'xcap-caps': XCAPCapabilitiesApplication(), Sep 25 17:01:27 openxcap openxcap[11876]: [-] File "/usr/lib/python2.4/site-packages/xcap/appusage/__init__.py", line 64, in __init__ Sep 25 17:01:27 openxcap openxcap[11876]: [-] self.xml_schema = etree.XMLSchema(xml_schema_doc) Sep 25 17:01:27 openxcap openxcap[11876]: [-] File "xmlschema.pxi", line 67, in etree.XMLSchema.__init__ Sep 25 17:01:27 openxcap openxcap[11876]: [-] etree.XMLSchemaParseError: Document is not valid XML Schema How can this be possible? I tried three times with three different machines. They work in VMware Server but not in ESX server. I don't find any answer at all neither can I imagine anyhow, how an application error like this occurs running the program on the very same, identical virtualized system with just two different virtualization platforms around. Anybody else has experiences in that, encountered somehow same strange behaviour with the application or has any other advice? I would really welcome every hint in somehow a direction to solve this. I didn't plan to extend my virtual OpenSER testing platform with a local PC, but it seems I have no other possibility so far... Thanks for your help! A nice weekend to all of you. Best regards Sebastian