Charmed Quark Systems, Ltd. - Support Forums and Community
NameSrv Issues with installing 5_2_10 - Printable Version

+- Charmed Quark Systems, Ltd. - Support Forums and Community (https://www.charmedquark.com/vb_forum)
+-- Forum: General Discussion (https://www.charmedquark.com/vb_forum/forumdisplay.php?fid=3)
+--- Forum: CQC Support (https://www.charmedquark.com/vb_forum/forumdisplay.php?fid=9)
+--- Thread: NameSrv Issues with installing 5_2_10 (/showthread.php?tid=10508)



NameSrv Issues with installing 5_2_10 - pjgregory - 01-30-2018

I am travelling at the moment and with a few day's on the beach, decided to set my laptop up as a standalone system so I could play with some media ideas.  I first uninstalled the existing client only 5_2_1 system, deleting the CQC directory and did a new install as master server system with 5_2_10.  This failed first time as the password set page could not contact the CIDNameServer.  I ran uninstall again and found that theCIDNameSrv was still active in Task Manger.  So I closed it, then ran install again.

Tried this several times with and witout re-booting in between before I finally got 5_2_10 installed.  I created a few interfaces yesterday before leaving the laptop to sleep overnight.  This moring, all I get is the "Waiting for CQC" box and after a while another box with "Cannot contact CID Name Srv on Nueomancer:13502.

I have tried uninstalling and re-installing a few times, but still the same problem.  One thing is clear however.  The Uninstall routine does not remove the runnning name server from the task list without a re-boot.  You can also see it still listening on port 13502.  Even rebooting several times and checking that nothing is listening on port 13502 does not fix the problem.  Something has got confused - what do I do to try and fix it.

PJG


RE: NameSrv Issues with installing 5_2_10 - Dean Roddey - 01-30-2018

You can't let the machine sleep if you are running the full system. Well you can, just shut down the CQC App Shell service first. Typically, if you are going to do that sort of setup, you will install the service for Manual mode. That way, it only starts up if you ask it to, then you can stop it when you are done. Or you can do a full restart on the machine to make it restart.

I'm guessing that whatever went wrong is preventing the uninstaller from talking to the back end, so it can't stop them and clean up. Part of the reason is that sleeping is not for server stuff. It doesn't give larger services like the CQC back end time to shut down cleanly, and it could cause issues at some point because it'll just whack them mid-shutdown. Particularly if it ends up going through multiple wake up/sleep/wake up type cycles. That's just not something that complex server side processes are necessarily wound to deal with. Most folks don't have an issue with that, that I've heard, but it's not something that we'd promise would work.

There may also be an issue with trying to convert a client to a master. It's something not often done and there may be some issue there that no one has reported.

What I would do is:

1. Manually stop both services (CQC Application Shell and CQC Client Service)
2. Delete the CQC directory to clean up any old stuff, particularly any old client side configuration stuff
3. Restart the machine
4. Now run the installer and install it as a standalone system from scratch
5. Set it for manual mode startup

When you want to use it start the services. When you are done, stop them. You can use the Windows services interface to do that, or you can do it from a command line, or you could use our Tray Monitor program to do it.


RE: NameSrv Issues with installing 5_2_10 - pjgregory - 01-30-2018

Did everything you said but it still fails at the screen to enter the password.  The detail message is

01/01 00:00:00-Neuromancer, CQCInst, MainThread
{
    CIDOrbUC, CIDOrbUC_ThisFacility.cpp.716, Failed/Not Found, Error: 6003/0/0
    Could not contact the CIDLib Name Server (at Neuromancer:13502)
    The server at 192.168.43.138:13502 was not available
}

Now I ran the DOS utility netstat -an to see if the port was open.  What I found was that all the listening ports for CQC were active at the address 0.0.0.0 etc.  So the name server was on 0.0.0.0:13502, but there was no entry for 192.168.43:13502 which could explain why the installer cannot find it.   By the way, I have turned off IPv6 as the first time I tried this, the diagnostic gave an IPv6 address and there was no listening on that port either.  How do you force CQC to look in the correct place.

PJG


RE: NameSrv Issues with installing 5_2_10 - pjgregory - 01-30-2018

Just to be clear, 0.0.0.0:13502 was marked as LISTENING.


RE: NameSrv Issues with installing 5_2_10 - Dean Roddey - 01-30-2018

That's the 'any' address, which means it's listening on all available interfaces. I wouldn't turn off IPV6. That's generally assumed to be available on Windows these days and might cause issues with other things.

When you installed, what did you give as the name of the master server? Did you give it that laptop's name?

If so, then a common scenario is an anti-virus blocking the ports. The installer sets up exceptions for the Windows firewall, but if you have any other sort of AV or firewall software you might have to set up exceptions for CQC's ports.