I restarted the ServiceManager on the Video machine @ 11:15am. Following that, I tried to once again add the VideoProducerService from my Display/NodeManager machine. I'm attaching both the ServiceManager and VideoProducerService logs from the Video machine (where I'm writing this email from). Please let me know if any other information would be helpful.
-David ________________________________ From: Thomas D. Uram [mailto:tu...@mcs.anl.gov] Sent: Fri 4/25/2008 10:57 AM To: Cortijo, David Cc: ag-t...@mcs.anl.gov Subject: Re: [AG-TECH] VideoProducer refuses to initialize - urgent Hi David: There should be more error state in the VideoProducerService.log file. If that doesn't clearly identify the problem, send it along and I'll have a look. Tom On 4/25/08 9:00 AM, Cortijo, David wrote: > I've been working on a node that we had to upgrade from AG 2.1.2 to AG 3.1 > this week to address problems talking to the node manager. At this point, it > looks like I've got everything working except for the VideoProducer. > > For some reason, when I try to add the VideoProducer service, I get the > message "Add Service failed:VideoProducerService". My display machine/node > manager can talk to the video producer machine just fine (I see messages > generated in the Service Manager on the video machine). > > I'm using 3 Conexant BtPCI WDM Video Capture cards. Is it possible that the > VideoProducer process that tries to initialize just isn't seeing them > correctly? > > Below is what I see in ServiceManager.log on my Video machine when I initiate > the service add from the Node Manager. Any insight on this would be helpful. > > -David Cortijo > Brookhaven National Laboratory > > 04/25/08 09:58:15 3444 ServiceManager agservicemanager.py:103 INFO > AGServiceManager.AddService > 04/25/08 09:58:16 3444 ServiceManager agservicemanager.py:343 INFO > Installed service version: 3.8, package version: 3.8 > 04/25/08 09:58:16 3444 ServiceManager agservicemanager.py:378 DEBUG > Executing service VideoProducerService > 04/25/08 09:58:16 3444 ServiceManager agservicemanager.py:410 INFO > Running Service; options: ['C:\\Documents and Settings\\Richard > Horwitz\\Application > Data\\AccessGrid3\\local_services\\VideoProducerService\\VideoProducerService.py', > '--port', 55023, '--serviceManagerUri', > 'http://130.199.3.53:11000/ServiceManager', '--token', > '82c7033508f826fcdb238234dea493fd'] > 04/25/08 09:58:16 3444 ProcessManager processmanager.py:62 DEBUG Creating > process: C:\Python24\python.exe "C:\Documents and Settings\Richard > Horwitz\Application > Data\AccessGrid3\local_services\VideoProducerService\VideoProducerService.py" > --port 55023 --serviceManagerUri http://130.199.3.53:11000/ServiceManager > --token 82c7033508f826fcdb238234dea493fd > 04/25/08 09:58:16 3444 ProcessManager processmanager.py:75 DEBUG Create > process returns: (<PyHANDLE:940>, <PyHANDLE:948>, 3456, 3452) > 04/25/08 09:58:26 3444 ServiceManager agservicemanager.py:424 INFO > Service failed to register: 82c7033508f826fcdb238234dea493fd > 04/25/08 09:58:26 3444 Hosting servicecontainer.py:17 ERROR Processing > Failure > exceptions:Exception > Service failed to become reachable > [trace: C:\Python24\lib\site-packages\ZSI\ServiceContainer.py:108:_Dispatch > C:\Python24\lib\site-packages\AccessGrid3\AccessGrid\interfaces\AGServiceManager_interface.py:943:soap_AddService > C:\Python24\lib\site-packages\AccessGrid3\AccessGrid\AGServiceManager.py:147:AddService > C:\Python24\lib\site-packages\AccessGrid3\AccessGrid\AGServiceManager.py:425:__ExecuteService] > > >
VideoProducerService.log
Description: VideoProducerService.log
ServiceManager.log
Description: ServiceManager.log
