This is not really a problem (the problem has been resolved I think) but more of a question. Recently we had an issue with our Doors and the FlexLM License Tool. A week ago Doors failed to run because it could not find the license file. It has been running for a long time without any issues. I.B.M. had me update the license software on the server which I did. It did not improve anything. I found out that I had to include a port number for IBMRatl because we have the server behind a firewall. Now the license file previously did not need that. I did find an old file that had the port 19354. I used that port and it is currently working. My question is has anyone ever experienced an issue similar to that? I do know that some patches were made on the server the previous night and am wondering if the patches could have done something. Seems strange to me that it has been working for so long without an issue and than Bam! we have one...
Thanks. Lee Ann Davidson - Thu Apr 30 14:48:42 EDT 2015 |
Re: Doors and a Firewall Hi,
I haven't experienced that but the following could be it. When you use DOORS, always 3 ports are used. 1. lmgrd - 19353 default on old license server. 27000 default on the new license server. 2. DOORS database server - 36677 default 3. Vendor daemon. old one uses telelogic vendor and new on uses ibmratl vendor. They both assign itself a random port available on the machine. but you can also specify a port it uses on the license file.
I'm guessing that someone set the vendor to use19354 on the old file but you didn't for the new one. So that the vendor couldn't find the available port for some reason and BAM ! |
Re: Doors and a Firewall knobutan - Thu Apr 30 20:29:01 EDT 2015 Hi,
I haven't experienced that but the following could be it. When you use DOORS, always 3 ports are used. 1. lmgrd - 19353 default on old license server. 27000 default on the new license server. 2. DOORS database server - 36677 default 3. Vendor daemon. old one uses telelogic vendor and new on uses ibmratl vendor. They both assign itself a random port available on the machine. but you can also specify a port it uses on the license file.
I'm guessing that someone set the vendor to use19354 on the old file but you didn't for the new one. So that the vendor couldn't find the available port for some reason and BAM ! I have figured all that out already. What I am curious as to why the system went down in the first place, The license file we had been using did not have the port specified. Not sure why we have to specify it now and how it worked with our firewall to begin with since only about 8 ports are opened. Now I don't mind puzzles but this one caused a lot of grief with a lot of people. The system has been working for a long time with the port not being assigned on the file. But I suppose I will just accept the fact that the issue of why is started will be a mystery.
Thanks for the reply. I may still poke around on my log files and see if I can shed light on the mystery. |
Re: Doors and a Firewall Lee Ann Davidson - Fri May 01 08:28:51 EDT 2015 I have figured all that out already. What I am curious as to why the system went down in the first place, The license file we had been using did not have the port specified. Not sure why we have to specify it now and how it worked with our firewall to begin with since only about 8 ports are opened. Now I don't mind puzzles but this one caused a lot of grief with a lot of people. The system has been working for a long time with the port not being assigned on the file. But I suppose I will just accept the fact that the issue of why is started will be a mystery.
Thanks for the reply. I may still poke around on my log files and see if I can shed light on the mystery. Somebody has probably been changing router settings. |
Re: Doors and a Firewall Lee Ann Davidson - Fri May 01 08:28:51 EDT 2015 I have figured all that out already. What I am curious as to why the system went down in the first place, The license file we had been using did not have the port specified. Not sure why we have to specify it now and how it worked with our firewall to begin with since only about 8 ports are opened. Now I don't mind puzzles but this one caused a lot of grief with a lot of people. The system has been working for a long time with the port not being assigned on the file. But I suppose I will just accept the fact that the issue of why is started will be a mystery.
Thanks for the reply. I may still poke around on my log files and see if I can shed light on the mystery. Did the problem happen after a license server restart? As specified earlier, the vendor daemon port is chosen at random unless it is specified in the license file. So perhaps at one point that vendor daemon port was open and then after a server restart the new random port # was no longer open. Or did the license file change? Perhaps the old license file did have the vendor port specified and the new one did not? |
Re: Doors and a Firewall kourosh - Thu May 07 12:19:57 EDT 2015 Did the problem happen after a license server restart? As specified earlier, the vendor daemon port is chosen at random unless it is specified in the license file. So perhaps at one point that vendor daemon port was open and then after a server restart the new random port # was no longer open. Or did the license file change? Perhaps the old license file did have the vendor port specified and the new one did not? Yes the server was restarted the night before and I am sure that the port was reset during that time. What I do not understand is that the server had been restarted before and it never acted like this. The firewall has only like 8 ports open and I am sure that it did not randomly pick an open port out of those that were available, it would be like picking all the winners of all the games for next football season, well maybe not lol. The license file did not change, but I am sure something changed as we do have people who have the right to go in and change things without saying jack (don't know why that is but we do, I cannot change anything on the server without going through several hoops). I am just going to chalk this up as to that and go with it. Makes me a bit upset as we had the system down for several days as I scratched my head trying to figure out what to do. I am going to keep a close eye on it for the next month or so to ensure that things are working properly.
Thanks for the help and input, it will just be a mystery without any clues for now... |