Client 215 Betas

[quote user="qilin"][quote user="Graham"]

Hmm. Later versions of Synapse use Cheyenne web server on port 8002.

Can you check in task manager if Cheyenne is running ( it should be in system tray as icon ). Perhaps you're blocking it?

Try browssing to http://localhost:8002 and see if you get a 404 ...

[/quote]

Cheyenne is running on task bar. I don't think I am blocking it since it was working before this last client. When I change the port to 8001, page can display correctly. http://localhost:8002 gives "Internet Explorer cannot display the webpage" message, not 404

[/quote]That message means that Cheyenne is not working as a web server. Please check to make sure it is not being blocked.


Port 8001 is the old web server which is still running .. I'm keeping it for other purposes so that's why it still works.

Cheyenne maintains a log directory in the same directory where it is started from.

Have a look at the file default-access.log and see if it's receiving any requests from the browser.

Or, delete the log, and try browsing to localhost:8002 to see if anything appears in the log.

Also, there should be a file called "httpd.cfg" in the same directory as cheyenne.

There should be a line

listen [ 8002 ]

in the globals section. That defines what port Cheyenne is listening on.

<h3>R215B2 6 Mar 2009</h3>

• Drops back to using the Synapse web browser if it can't connect to Cheyenne web browser

<h3></h3>

Qilin, this is a fix for you, but I really think we should find out why Cheyenne is not working for you. Cheyenne is not my software but I think the author would like to know if there are vista 64 problems.


What happens now is that on startup, Synapse will start up cheyenne, and then try to connect to it on port 8002. If it can't connect, it will thereafter drop back to using the original Synapse web browser on port 8001.

If your httpd.cfg was missing that line, you must have deleted it!

the file comes from my site and is downloaded at the same time as it downloads cheyenne.

Or, you could have moved it to a different directory and not copied the httpd.cfg .. in which case Cheyenne creates a default one which attempts to listen on port 80. Which of course is blocked in Vista.

I was going to do a Mac OSX client .. but there was a distinct lack of support for the idea.

And as I don't even have time to maintain the linux client .. I suspect it is not going to happen.

<h2 style="background-repeat: no-repeat; background-image: url('http://www.compkarori.co.nz:8090/skins/common/icons/editor-h1.gif'); font-family: Tahoma,Verdana,sans-serif; margin-bottom: 4px; padding-bottom: 0px; color: #000000; text-decoration: none; font-size: 16pt; background-position: 100% 0%">R84B29 for Windows ( server )
</h2>

<ul style="margin-top: 1.5em; margin-bottom: 0px; list-style-type: disc"><li style="line-height: 1.25">New - creates the tables needed for acroforms support

[/list]

<h2 style="background-repeat: no-repeat; background-image: url('http://www.compkarori.co.nz:8090/skins/common/icons/editor-h1.gif'); font-family: Tahoma,Verdana,sans-serif; margin-bottom: 4px; padding-bottom: 0px; color: #000000; text-decoration: none; font-size: 16pt; background-position: 100% 0%"></h2>

There is no support in the Synapse client yet for Acroforms.

When I restart (with the [Restart] button) my clients, it takes 25 seconds to see the login screen. Same with clicking on synapse.exe.

It is like this on all my PCs now. Is this a cheyenne.exe thing ? What exactly is going on ?

Is it just me ?

Must be my web server that responds to requests for information on updates etc that is causing the delay.

It takes me about 18 seconds for login screen to appear.

If that is going to be the length of time from now on, it might be more informative to the end user to describe what is going on.

But for there to be a 20 second pause with nothing on the screen, people will wonder what is going on.

How about something like this popup right away ?

And then when the server responds ... the login boxes appear.

Should you reboot your server ? This used to take 2 seconds now it takes 24 !

It's a hosted web server in Texas. I have no control over it.

It doesn't seem to be the update check afterall ... have to track down where this delay is coming from.

What vesion did you first notice it?

I have found the problem.

Synapse client uses the time server time-a.nist.gov ( see http://tf.nist.gov/service/time-servers.html ) but it is no longer reachable. After 21 seconds Synapse times out, and continues hence the long delay at start up.


I have advised the person who's email appears on that site that several servers are down.

I will change the time server to time.nist.gov which is working ...

My startup to the login screen is now 3 seconds switching to the working NIST time server. [H]

heh.

Can we get a new beta with the new Time Server ?

Probably tomorrow ...

Great. Thanks.

[]