Network lock failed

Two bugs to report.

First some background...I'm using Toolkit 1.1.5 connecting to CGate on a linux box. CGate connects to a PCI via a Lantronix MSS100. When I start Toolkit, I tell it to close the (local) project repository, I kill the CGate Toolkit started and then I tell Toolkit to connect to the remote repository.

Bug number one: the first time Toolkit tries to connect to the remote repository, it tells me that it failed to connect to it. I then tell it to connect again and it works. This appears to be perfectly repeatable. It always connects on the second attempt.

Next, I connected some fans to dimmers, tested them, and they worked. Then I reprogrammed the input units (E2000 series) that will control the fans and the dimmers. I didn't want to let anything run the power to the fans at anything other than 0% or 100%. So I programmed the dimmers to turn on only at 100% and the E2000's to use an on/off function rather than dimmer.

The problem is that when it came to the last unit, an E2000, Toolkit crashed while updating the network. I got a windows message saying it was creating an error log - I never got the Clipsal crash pop-up. At the time of the crash, the only change was to switch one of the E2000 buttons from a dimmer to an on/off - the group changes had already been made and written to the DB & network.

Upon restarting Toolkit, when I double-click on the E2000 (in DB or network), I get this message:

To recover from this, I had to reboot CGate - only then would Toolkit be able to access any units. I guess there are two problems with this:
(1) That Toolkit crashed in the first place
(2) That CGate allowed Toolkit to hold on to a network lock even after Toolkit had died (presumably the socket would have died so CGate should have been able to clean up after Toolkit).

Paul

 

Hi Paul,

Network locks timeout after 15mins.. but, I agree.. a feature that caused Network Locks to drop out when the initiating socket disconnected would be worthwhile.. I've logged it. Is the crash repeatable? If you turn off the Application Log and Live Groups in preferences, does the crash not occur?


Thanks for the report.

 

The connect-to-cgate-on-second-attempt bug is repeatable. But the crash I described hasn't happened again.

 

Toolkit crashed again. This time is was overnight while not being used. It gave the usual windows error message about a crashed program and saying it was writing a log .

Anything I can do to help isolate this? Would my toolkit.log file be of any help? Do others get this happen?

I'm using Toolkit 1.1.5 on win2k (cgate is running elsewhere)

 

Hi Paul,

Would you be able to Turn off the Application Log and Live Groups in preferences, leave it running overnight again and tell me if it crashes?

 

I've turned off live groups & app log in preferences, reprogrammed the same switch (from on/off to dimmer and back again) in case that had anything to do with it. I'll now will leave it running and see if it crashes again.

I still have the toolkit.log from when it crashed last time. Do you want to see it? If so, where should I send it?