Synametrics Technologies

I installed Syncrify on an Ubuntu 10.04 server. The only customization I attempted was to change the install directory from /opt to /usr/local. Per your web site, tried to connect to port 5800 via HTTP. When that didn't work, I examined the host and found that nothing was listening on port 5800. By examining the listening port, I determined that Sincrify is listening on port 59459, and I am able to connect to it there. When I went through the admin setup, the final screen did show port 59459 for the access URL (although it actually gave an IP address of a virtual interface rather than the real NIC I'll actually use). Is the Syncrify install coded to use port 59459, or was there some environmental reason that prevented it from using port 5800? In any event, I'd suggest allowing the user to override the default TCP port at install time.

>I installed Syncrify on an Ubuntu 10.04 server. The only customization I attempted >was to change the install directory from /opt to /usr/local. Per your web site, tried >to connect to port 5800 via HTTP. When that didn't work, I examined the host and >found that nothing was listening on port 5800. By examining the listening port, I >determined that Sincrify is listening on port 59459, and I am able to connect to it >there. When I went through the admin setup, the final screen did show port 59459 >for the access URL (although it actually gave an IP address of a virtual interface >rather than the real NIC I'll actually use). Is the Syncrify install coded to use >port 59459, or was there some environmental reason that prevented it from using port >5800? In any event, I'd suggest allowing the user to override the default TCP port >at install time. Later I used the admin interface to specify the listening ports. I set 8100 as primary and left 5800 as secondary. I see these values as expected in AppConfig.xml, but upon restarting the server, it chose a new set of ports. The admin interface is now accessible only on port 52300. Nothing listening on either 8100 or 5800.

This is strange. Did the port in AppConfig.xml change to 52300? Hunaid. > >Later I used the admin interface to specify the listening ports. I set 8100 as primary >and left 5800 as secondary. I see these values as expected in AppConfig.xml, but >upon restarting the server, it chose a new set of ports. The admin interface is now >accessible only on port 52300. Nothing listening on either 8100 or 5800.