Re: [AG-TECH] Probs starting VIC&RAT on AGTK3.01 winxp
I would expect to find some conflict like the one you've already sought. In addition to looking for files like "c:\documents" , have you looked for a conflict with "c:\documents and settings\jww\application" ? The fact that it worked at some point and has stopped makes me suspect that a conflicting file has appeared in one of these locations. We'll fix this problem in a future release. Let me know how things work out for you so we can be sure to address the problem you're seeing, if it turns out to be something new. Thanks, Tom Sebastian Adams wrote: > Hi there, > > One of the machines here has an odd prob starting the vic & rat executables. > Example error: > > eg audioservice.log > 06/02/06 12:00:27 2984 Toolkit agservice.py:182 INFO SetStream: ignoring > trivial re-configuration > 06/02/06 12:00:27 2984 Toolkit audioservice.py:274 INFO Starting > AudioService > 06/02/06 12:00:27 2984 Toolkit audioservice.py:275 INFO executable = > C:\Documents and Settings\JWW\Application > Data\AccessGrid3\local_services\AudioService\rat.exe > 06/02/06 12:00:27 2984 Toolkit audioservice.py:277 INFO options = > ['-C', u'AGSC Venue Server Lobby', '-S', u'c0ab9a180f6c420a2c48365f6d2f3d12', > '-f', 'L16-16K-Mono', u'sam.ag.manchester.ac.uk/10824'] > 06/02/06 12:00:27 2960 ProcessManager processmanager.py:138 ERROR > couldn't shutdown process : (1444, 'PostThreadMessage', > 'Invalid thread identifier.') > Traceback (most recent call last): > File > "C:\Python23\lib\site-packages\AccessGrid3\AccessGrid\Platform\win32\ProcessManager.py", > line 131, in TerminateProcess > win32api.PostThreadMessage(self.threadid[pid], 18, 0, 0) > error: (1444, 'PostThreadMessage', 'Invalid thread identifier.') > 06/02/06 12:00:27 2984 ProcessManager processmanager.py:62 DEBUG Creating > process: C:\Documents and Settings\JWW\Application > Data\AccessGrid3\local_services\AudioService\rat.exe -C "AGSC Venue Server > Lobby" -S c0ab9a180f6c420a2c48365f6d2f3d12 -f L16-16K-Mono > sam.ag.manchester.ac.uk/10824 > 06/02/06 12:00:27 2984 ProcessManager processmanager.py:100 ERROR process > creation failed: (193, 'CreateProcess', '%1 is not a valid Win32 > application.') > Traceback (most recent call last): > File > "C:\Python23\lib\site-packages\AccessGrid3\AccessGrid\Platform\win32\ProcessManager.py", > line 73, in StartProcess > startup_info) > error: (193, 'CreateProcess', '%1 is not a valid Win32 application.') > > similarlarly for vic (videoproducerservice.log): > > 06/02/06 12:14:08 2884 Toolkit videoproducerservice.py:324 INFO > enabled: 1 > 06/02/06 12:14:08 2884 Toolkit agservice.py:171 INFO SetStream: [consume > ster.ac.uk 10194 > 06/02/06 12:14:08 2884 Toolkit videoproducerservice.py:175 INFO Mapping > windows device: Logitech QuickCam Pro 4000 > 06/02/06 12:14:08 2884 Toolkit videoproducerservice.py:303 INFO Starting > VideoProducerService > 06/02/06 12:14:08 2884 Toolkit videoproducerservice.py:304 INFO > executable = C:\Documents and Settings\JWW\Application > Data\AccessGrid3\local_services\VideoProducerService\vic.exe > 06/02/06 12:14:08 2884 Toolkit videoproducerservice.py:305 INFO options > = ['-u', 'C:/DOCUME~1/JWW/LOCALS~1/Temp/VideoProducerService_2920.vic', '-C', > 'Logitech QuickCam Pro 4000', '-X', u'site=c0ab9a180f6c420a2c48365f6d2f3d12', > u'sam.ag.manchester.ac.uk/10194'] > 06/02/06 12:14:08 2884 ProcessManager processmanager.py:62 DEBUG Creating > process: C:\Documents and Settings\JWW\Application > Data\AccessGrid3\local_services\VideoProducerService\vic.exe -u > C:/DOCUME~1/JWW/LOCALS~1/Temp/VideoProducerService_2920.vic -C "Logitech > QuickCam Pro 4000" -X site=c0ab9a180f6c420a2c48365f6d2f3d12 > sam.ag.manchester.ac.uk/10194 > 06/02/06 12:14:08 2884 ProcessManager processmanager.py:100 ERROR process > creation failed: (193, 'CreateProcess', '%1 is not a valid Win32 > application.') > Traceback (most recent call last): > File > "C:\Python23\lib\site-packages\AccessGrid3\AccessGrid\Platform\win32\ProcessManager.py", > line 73, in StartProcess > startup_info) > error: (193, 'CreateProcess', '%1 is not a valid Win32 application.') > > So it looks like python getting confused with the path/arguments or somesuch? > I have checked that there isn't a directory called c:\documents which could > cause this prob. > > I can start (without probs) vic & rat with the correct arguments via command > line. > > At first I thought it was another application (statistica) installed on the > PC which uses the .svc extension for macros - but have uninstalled that > without resolution. > > AGTK has worked the machine in the past but has stopped working at some point > (both agtk 2.4 & 3.01 exhibit the same prob). > > Many thanks, Seb > > Seb Adams > CEH Computer Support > Tel 01524 595818 > >
[AG-TECH] Probs starting VIC&RAT on AGTK3.01 winxp
Hi there, One of the machines here has an odd prob starting the vic & rat executables. Example error: eg audioservice.log 06/02/06 12:00:27 2984 Toolkit agservice.py:182 INFO SetStream: ignoring trivial re-configuration 06/02/06 12:00:27 2984 Toolkit audioservice.py:274 INFO Starting AudioService 06/02/06 12:00:27 2984 Toolkit audioservice.py:275 INFO executable = C:\Documents and Settings\JWW\Application Data\AccessGrid3\local_services\AudioService\rat.exe 06/02/06 12:00:27 2984 Toolkit audioservice.py:277 INFO options = ['-C', u'AGSC Venue Server Lobby', '-S', u'c0ab9a180f6c420a2c48365f6d2f3d12', '-f', 'L16-16K-Mono', u'sam.ag.manchester.ac.uk/10824'] 06/02/06 12:00:27 2960 ProcessManager processmanager.py:138 ERROR couldn't shutdown process : (1444, 'PostThreadMessage', 'Invalid thread identifier.') Traceback (most recent call last): File "C:\Python23\lib\site-packages\AccessGrid3\AccessGrid\Platform\win32\ProcessManager.py", line 131, in TerminateProcess win32api.PostThreadMessage(self.threadid[pid], 18, 0, 0) error: (1444, 'PostThreadMessage', 'Invalid thread identifier.') 06/02/06 12:00:27 2984 ProcessManager processmanager.py:62 DEBUG Creating process: C:\Documents and Settings\JWW\Application Data\AccessGrid3\local_services\AudioService\rat.exe -C "AGSC Venue Server Lobby" -S c0ab9a180f6c420a2c48365f6d2f3d12 -f L16-16K-Mono sam.ag.manchester.ac.uk/10824 06/02/06 12:00:27 2984 ProcessManager processmanager.py:100 ERROR process creation failed: (193, 'CreateProcess', '%1 is not a valid Win32 application.') Traceback (most recent call last): File "C:\Python23\lib\site-packages\AccessGrid3\AccessGrid\Platform\win32\ProcessManager.py", line 73, in StartProcess startup_info) error: (193, 'CreateProcess', '%1 is not a valid Win32 application.') similarlarly for vic (videoproducerservice.log): 06/02/06 12:14:08 2884 Toolkit videoproducerservice.py:324 INFOenabled: 1 06/02/06 12:14:08 2884 Toolkit agservice.py:171 INFO SetStream: [consume ster.ac.uk 10194 06/02/06 12:14:08 2884 Toolkit videoproducerservice.py:175 INFO Mapping windows device: Logitech QuickCam Pro 4000 06/02/06 12:14:08 2884 Toolkit videoproducerservice.py:303 INFO Starting VideoProducerService 06/02/06 12:14:08 2884 Toolkit videoproducerservice.py:304 INFO executable = C:\Documents and Settings\JWW\Application Data\AccessGrid3\local_services\VideoProducerService\vic.exe 06/02/06 12:14:08 2884 Toolkit videoproducerservice.py:305 INFO options = ['-u', 'C:/DOCUME~1/JWW/LOCALS~1/Temp/VideoProducerService_2920.vic', '-C', 'Logitech QuickCam Pro 4000', '-X', u'site=c0ab9a180f6c420a2c48365f6d2f3d12', u'sam.ag.manchester.ac.uk/10194'] 06/02/06 12:14:08 2884 ProcessManager processmanager.py:62 DEBUG Creating process: C:\Documents and Settings\JWW\Application Data\AccessGrid3\local_services\VideoProducerService\vic.exe -u C:/DOCUME~1/JWW/LOCALS~1/Temp/VideoProducerService_2920.vic -C "Logitech QuickCam Pro 4000" -X site=c0ab9a180f6c420a2c48365f6d2f3d12 sam.ag.manchester.ac.uk/10194 06/02/06 12:14:08 2884 ProcessManager processmanager.py:100 ERROR process creation failed: (193, 'CreateProcess', '%1 is not a valid Win32 application.') Traceback (most recent call last): File "C:\Python23\lib\site-packages\AccessGrid3\AccessGrid\Platform\win32\ProcessManager.py", line 73, in StartProcess startup_info) error: (193, 'CreateProcess', '%1 is not a valid Win32 application.') So it looks like python getting confused with the path/arguments or somesuch? I have checked that there isn't a directory called c:\documents which could cause this prob. I can start (without probs) vic & rat with the correct arguments via command line. At first I thought it was another application (statistica) installed on the PC which uses the .svc extension for macros - but have uninstalled that without resolution. AGTK has worked the machine in the past but has stopped working at some point (both agtk 2.4 & 3.01 exhibit the same prob). Many thanks, Seb Seb Adams CEH Computer Support Tel 01524 595818 -- This message (and any attachments) is for the recipient only. NERC is subject to the Freedom of Information Act 2000 and the contents of this email and any reply you make may be disclosed by NERC unless it is exempt from release under the Act. Any material supplied to NERC may be stored in an electronic records management system.
Re: [AG-TECH] Linux AG RPMs on RHEL?
Dear Thad we are using AG2.4 on RHEL4 (acturally, Scientific Linux4), it works fine. we had also tried AG 3.0 (beta version) before on RHEL4 using Fedora 4 RPMs, it got some problmes. it seems ok if we use Fedoras3 RPMs on RHEL4. However, right now, we just simply use Fedora for AG3.0.1. Best regard! gen-tao On Jun 2 2006, Thad Sze wrote: > >Does anyone out there have any experience using the RPMs for AG >(either 2.4 or 3.0.1) packaged for Fedora on a RHEL system? In the >past I've been pretty successful jumping between with other software >but I was curious if anybody had any previous experience... > >Thanks, > >Thad > > > >Thaddeus Sze >Information Technology >Division of Engineering and Applied Sciences >Harvard University > > >
Re: [AG-TECH] Linux AG RPMs on RHEL?
Indeed. Though I did have to modify the yum repo files to point explicitly at the fedora 3/i386 path... -T On Jun 1, 2006, at 7:14 PM, Jeremy Mann wrote: > Thad, I just installed the Fedora Core 3 RPMs for our CentOS 4 system > (based on RHEL 4) and it worked perfectly. > > On 6/1/06, Thad Sze wrote: >> >> Does anyone out there have any experience using the RPMs for AG >> (either 2.4 or 3.0.1) packaged for Fedora on a RHEL system? In the >> past I've been pretty successful jumping between with other software >> but I was curious if anybody had any previous experience... >> >> Thanks, >> >> Thad >> >> >> >> Thaddeus Sze >> Information Technology >> Division of Engineering and Applied Sciences >> Harvard University >> >> >> > > > -- > Jeremy Thaddeus Sze Information Technology Division of Engineering and Applied Sciences Harvard University
Re: [AG-TECH] Linux AG RPMs on RHEL?
Thad, I just installed the Fedora Core 3 RPMs for our CentOS 4 system (based on RHEL 4) and it worked perfectly. On 6/1/06, Thad Sze wrote: > > Does anyone out there have any experience using the RPMs for AG > (either 2.4 or 3.0.1) packaged for Fedora on a RHEL system? In the > past I've been pretty successful jumping between with other software > but I was curious if anybody had any previous experience... > > Thanks, > > Thad > > > > Thaddeus Sze > Information Technology > Division of Engineering and Applied Sciences > Harvard University > > > -- Jeremy
[AG-TECH] Linux AG RPMs on RHEL?
Does anyone out there have any experience using the RPMs for AG (either 2.4 or 3.0.1) packaged for Fedora on a RHEL system? In the past I've been pretty successful jumping between with other software but I was curious if anybody had any previous experience... Thanks, Thad Thaddeus Sze Information Technology Division of Engineering and Applied Sciences Harvard University
