license server error
Lorry Litman
LLitman@exchange.hsc.mb.ca
Thu, 6 Feb 2003 13:51:55 -0600
Hi,
Thank-you to all that replied.
The problem was resolved by increasing the number of decnet links through
NCP.
I've included below information that helped should this be of use to anyone
else out there.
Thanx
Lorry
Problem Description
In an effort to resolve problems with 7.10 on Alpha AXP appearing to hang we
have put together this checklist to isolate probable areas.
Solution Description
Have the system administrator check whether the quotas for the license
daemon is sufficient for your system. Please refer to Appendix A at the end
of this document as a guideline. After making necessary changes, stop and
restart the license daemon for the new quotas to take effect. To do this,
run the command file COGNOS$LICENSE:COGNOS_LICENSE_MODIFY.COM. Select
option 4 to stop and de-install the license daemon and then option 2 to
install and start the license daemon again.
The client should be using a permanent key that originally came with the
7.10 media or by their sales representative.
If the error occurs after following the above step properly, use the below
checklist to help isolate the problem.
1. Check the COGNOS$LICENSE:COGNOSDA_ERR.LOG for any error
messages.
2. Check the state of the license daemon,
? Obtain the process id (PID) of the license daemon by doing a
$ SHOW SYSTEM
and locating the process named cognosd_FLEXlm.
? Use the DEC System Dump Analyzer (SDA) utility to get the state of the
license daemon process as follows
$ ANALYZE/SYSTEM
OpenVMS AXP (TM) System analyzer
SDA> set process/index=<pid of cognosd_FLEXlm>
SDA> show process
Process index: 001A Name: cognosd_FLEXlm Extended PID: 2040009A
-------------------------------------------------------------------
Process status: 00141001 RES,WAKEPEN,PHDRES,LOGIN
Required capabilities: 0000000C QUORUM,RUN
PCB address 80EB5E80 JIB address 80ED2D40
PHD address 81C04000 Swapfile disk address 00000000
Master internal PID 0001001A Subprocess count 0
Internal PID 0001001A Creator internal PID 00000000
Extended PID 2040009A Creator extended PID 00000000
State LEF Termination mailbox 0000
Previous CPU Id 00000000 Current CPU Id 00000000
Previous ASNSEQ 0000000000005A34 Previous ASN 0000000000000003
Current priority 13 # of threads 0000000000000000
Initial process priority 8 Delete pending count 0
Base priority 8 AST's active NONE
UIC [00001,000004] AST's remaining 101
Mutex count 0 Buffered I/O count/limit 255/256
Waiting EF cluster 0 Direct I/O count/limit 100/100
Abs time of last event 0295341B BUFIO byte count/limit 94816/94816
Event flag wait mask FFFFFFF9 # open files allowed left 102
Swapped copy of LEFC0 00000000 Timer entries allowed left 16
Verify that these values are sufficiently high enough. You may wish to
direct the output to a file to pass a long to a Cognos representative.
3. Check the number of DECnet links on the system. There does not
appear to be any direct to obtain the number of active links other than to
count each entry through NCP. To help ease this task, use the following
commands,
$ MC NCP SHOW KNOWN LINKS STATUS TO <file-spec>
$ SEARCH <file-spec> "cognosd"/STATISTICS/OUTPUT=NL:
Files searched: 1 Buffered I/O count: 4
Records searched: 15 Direct I/O count: 3
Characters searched: 672 Page faults: 21
Records matched: 2 Elapsed CPU time: 0 00:00:00.02
Lines printed: 2 Elapsed time: 0 00:00:00.04
There is a total 8 of DECnet links being used, 4 of which are
PowerHouse 7.10 processes. The number of records search, after subtracting
first 7 records for the header, is the total number of DECnet links being
used on the system. The number of records matched multiplied by 2 is the
number of DECnet links being used by Powerhouse 7.10 because each user
requires a pair of DECnet links. The total number of DECnet links should be
less than the maximum links specified in NCP. The maximum links can be
verified as follow,
$ MC NCP
NCP> SHOW EXEC CHAR
Node Volatile Characteristics as of 24-Nov-1995 15:17:31
Executor node = 1.69 (SURAK)
Identification = DECnet for OpenVMS AXP 6.1
Management version = V4.0.0
.
.
.
Maximum links = 612
Delay factor = 80
.
.
.
4. If any of the above steps reveals that quotas are insufficient, have the
system administrator make the necessary changes, stop and restart the
license daemon. If the problem persists, gather the following information
below to forward to a Cognos Customer Support.
? Any errors in the COGNOS$LICENSE:COGNOSDA_ERR.LOG file
? The output from the SDA and the number of Maximum links
? The version of OpenVMS operating system
? The version of PowerHouse, e.g. 7.10E, 7.10E6 etc..
? The number of users running PowerHouse on the system at the time of the
failure.
5. Check the system parameter PQL_MBYTLM, which governs the maximum number
of bytes available to a given detached process. Monitor the cognosd_flexlm
process to see if it is reaching this limit. If so, reset the parameter to
a higher limit.
APPENDIX A
System Configuration for the License Manager
There are a number of parameters that need to be adjusted in order
to ensure that the License Manager runs properly in your environment.
On a heavily loaded system, the License Manager may be swapped out from main
memory. This will cause any PowerHouse application not to connect to the
License Manager. To prevent this, start the License Manager with the
"/NOSWAPPING" qualifier.
DECnet Links The FLEXlm license manager runs as a detached process and
uses DECnet links to control access to all PowerHouse 7.10 components. Each
PowerHouse 7.10 user requires a pair of DECnet logical links. You must
ensure that you have set the DECnet Maximum links to a sufficiently high
value. This can be calculated as follows:
MAXIMUM LINKS =
( 2 * Maximum number of PowerHouse 7.10 users )
+ ( number of Links used for all other DECnet activities )
To modify the number of DECnet links on your system, use the
following command sequence:
$ MCR NCP
NCP> define exec maximum links <calc-value>
NCP> set exec state off
NCP> exit
$ @SYS$STARTUP:STARNET.COM
I/O Channel Additional I/O channel are required for the DECnet links
used by the License Manager
Count and you must ensure that the CHANNELCNT parameter has been modified
to sufficiently high value.
Note: In order to change CHANNELCNT, you will need to set it in
SYSGEN and then reboot your system. You should plan this ahead of time.
The necessary CHANNELCNT value can be calculated as follows:
CHANNELCNT = ( I/O Channels required by system already )
+ ( Maximum # of PowerHouse 710 Users )
Maximum Another parameter that you may want to examine in
conjunction with the License
Processes manager is the MAXPROCESSCNT which may have to be increased.
File Limit on Each PowerHouse 7.10 user causes a channel to be opened to
the license daemon. You
Cognos License must ensure that the detached process runs with large enough
parameter values on
Daemon File limit, Buffer I/O limit, and Asynchronous System Traps (AST)
limit. To check this, after installing PowerHouse 7.10, edit the file
COGNOS$LICENSE:COGNOS_LICENSE_STARTUP.COM
and ensure that the three above mentioned parameters on the RUN
command have large enough values.
The necessary FILE_LIMIT value can be calculated as follows:
FILE_LIMIT = 3 + ( maximum number of PowerHouse users )
The BUFFER_LIMIT value can be calculated as follows:
BUFFER_LIMIT = 5400 + ( 200 * maximum number of PowerHouse users )
The AST_LIMIT can be calculated as follows:
AST_LIMIT = 2 + ( maximum number of PowerHouse users )
The following is an extract from a COGNOS_LICENSE_STARTUP.COM file
with the limits that may need changing hilited.
$ ON CONTROL_Y THEN CONTINUE
$ IF F$GETSYI("ARCH_NAME") .EQS. "VAX"
$ THEN
$ cogdaemon = "COGNOS$LICENSE:COGNOSD"
$ ELSE
$ cogdaemon = "COGNOS$LICENSE:COGNOSDA"
$ ENDIF
.
.
.
$ IF local_node .EQS. license_server_node
$ THEN
$ RUN/DETACHED -
/OUTPUT='cogdaemon'.LOG -
/ERROR='cogdaemon'_ERR.LOG -
/AST_LIMIT=102/BUFFER_LIMIT=25400/ENQUEUE_LIMIT=1 -
/EXTENT=4096/FILE_LIMIT=103/MAXIMUM_WORKING_SET=1024 -
/PAGE_FILE=20000/PRIORITY=8/WORKING_SET=1024/IO_BUFFERED=256 -
'cogdaemon'.EXE
$ IF $STATUS .NE. 1
$ THEN
$ display "%COGNOS-F-CLDSFA, Cognos license daemon
startup failed on ''license_server_node'"
$ ELSE
$ display "%COGNOS-I-CLDDST, Cognos license daemon
started on ''license_server_node'"
$ @COGNOS$LICENSE:COGNOS_LICENSE_SYMBOLS.COM
$ display ""
$ ENDIF
$ ELSE
$ display "%COGNOS-I-CLDNND, Cognos license daemon not
initiated on ''local_node'."
$ display "-COG-I-CLDNOD, daemon starts up on node
''license_server_node'."
$ @COGNOS$LICENSE:COGNOS_LICENSE_SYMBOLS.COM
$ display ""
$ ENDIF
Only AST_LIMIT, BUFFER_LIMIT, and FILE_LIMIT need to be adjusted,
based on the number of users, for the COGNOS_LICENSE_STARTUP.COM file.
> -----Original Message-----
> From: Lorry Litman [mailto:llitman@exchange.hsc.mb.ca]
> Sent: 06 February 2003 16:05
> To: powerh-l@lists.swau.edu
> Subject: license server error
>
>
> Good morning,
>
> There is a problem with the Cognos License server on our GS160's which
> sporadically prevents connecting to a Powerhouse session.
>
> We are running PH 7.10.G1 on our Alpha's VMS 6.2 and our Galaxy's VMS 7.2.
> We have recently started migrating users from the Alpha's to the
> Galaxys's.
>
> We have been experienceing the license server error on the
> Galaxy's which we
> didn't have on the Alpha's.
>
> The message that typically displays when trying to invoke a PowerHouse
> component (e.g. QUICK, QUIZ, QTP, QDESIGN etc) is:
>
> *E* Licensing: PH-AXP-RUNTIME PH-AXP-REPORTING-ONLY
> PH-AXP-RUNTIME-WITH-REPORTING(200) PH-AXP-DEVELOPMENT(5) cannot connect to
> license server
>
> Any ideas/suggestions that you may have would be appreciated as this is a
> potentially serious problem affecting many users and needs to be
> resolved as
> soon as possible.
>
> Thanx
> Lorry