Isight + Ichat AV + PostgreSQL: problem solved

It seems like using the port 5432, officially owned by PostgreSQL, is conflictive with the use of Quicktime Videoconferencing, and this is the reason why I cannot use the Isight with Ichat at same time that the postmaster was running in the default port. The cryptic error “can’t get video from the camera” certainly does not help so much. Right now I’ve solved the issue and here is the recipe:

Parece ser que el puerto 5432, oficialmente en uso por PostgreSQL da problemas con Quicktime Videoconferencing, y esta era la causa por la que no podía efectuar conexiones de vídeo y veia el errorcito “Can’t get video from the camera”, que francamente, no ayudaba demasiado. Pues bien, he resuelto el problema, y he aquí la receta:

 

  • Be sure that camera, firewire ports, etc. are correctly configured and running. Apple ichat Support.

  • Increase the OSX shared memory as described here. This step isn’t required, PostgreSQL will work with 10.3 default config, but is almost secure that you will get into shared memory problems soon or later.

  • Get PostgreSQL source code, at the time of writing the current version is 8.0.1.

  • Compile it with this switch --with-pgport=28421. It should work with any non-reserved port, 28241 is only the one I’m using. By any obscure reason isn’t enough to change the port in any precompiled pg system.

    To check for non-oficially reserved ports, IANA has the last word.

  • Install it, test it, install the start-up scripts if you want to, and reboot.

Now you can have videoconferences while the postmaster is running.

¿Never compiled source code? Take the easy way and use these guides: Marc Liyanage, Apple or Michel Brewer.

As always, comments are welcome.

  • Asegúrate de que tu cámara, puertos firewire, etc están correctamente configurados (Documentos).

  • Aumenta la memoria compartida del OSX. Este paso no es obligatorio, PostgreSQL funciona correctamente con los parámetros por defecto del OSX 10.3, pero es muy posible que alguno de los procesos no se pueda activar por falta memoria.

  • Consigue el código fuente de PostgreSQL, en este momento la última versión es la 8.0.1.

  • Compila el código con este switch: `—with-pgport=28241’. Debería funcionar con cualquiera no reservado, 28241 es sólo el que estoy usando yo. Por algún oscuro motivo no basta con cambiar el puerto en la configuración de un sistema pg precompilado.

    Para comprobar los puertos no oficialmente reservados, IANA tiene la última palabra.

  • Instala el código recién compilado, comprueba que funciona correctamente, instala los scripts de arranque automático si los necesitas y reinicia.

Ahora ya puedes efectuar videoconferencias mientras el postmaster funciona en background.

¿No sabes cómo compilar el código? usa las guías de Marc Liyanage, Apple o Michel Brewer.

Como de costumbre, cualquier comentario será bienvenido.


Comments

De verdad, funciona. Yo le veo muy bien. Incluso favorecido. Debe ser la cara de satisfacción que se le pone a uno cuando resuelve un problema. Desde el colegio está uno en este dilema....

Concha Barral

Febrero 21, 2005

It would be interesting to know for how many people this solution works. For the colleagues I work with, increasing the OS X shared (unprotected) memory limits was the way to solve the problem. (And one of the OS X upgrades switched the settings back, which we all noticed because the systems would not work again.) We are running Postgres + iChat fine now, and Postgres is still configured with port 5432.

Also, I've got 3 comments on my blog site from people for whom the memory settings did also fix the problem.

I'd be happy to admit the problem may be more subtle and complex than either of us think. It's just that I would be surprised if it were as simple as a port issue. If people are able to solve the issue with the port change, please write something here. The accumulated body of experience will benefit us all.

Murray Todd Williams

Curious, I tried both ways separately, increasing shared memory (which I had enabled ages ago, since the 10.2 days), and changing the port everything where it appears in the postgresql config files and none of them worked alone under my dual G4 / 10.3.8 box.

Perhaps a system-specific compilation fixed something elsewhere.

Thanks! I forgot about this one.

I made sure I remembered it PostgreSQL on their Macs.">here.

Je je, ando buscando información y vengo a parar aquí...


Post a comment