Welcome! » Log In » Create A New Profile

R: R: Cant start the server - SOLVED

Posted by Tommaso Bollini 
Tommaso Bollini
R: R: Cant start the server - SOLVED
May 24, 2018 01:59AM
Hi Eric and Shawn, I've solved with the re-installation of the packages:

gskcrypt64-8.0-14.51
gskssl64-8.0-14.51

that I got in the 6.4.3.2-TIV-TSMBAC-LinuxX86.tar from the ftp://storsys site.
Product version 8.0.14.51 of the above, in a 7.1.7 SP SLES11 environment works fine :)

Not solved with: http://www-01.ibm.com/support/docview.wss?uid=swg21642264

I even had solved, in a virtual clone of my 7.1.7 (server with testing purposes), with reinstall of the SP product only (Uninstall + Install) and with a 8.0-50.66 GSK release (8.1.0 BA).

Many many many thanks to you.
Regards.

-----Messaggio originale-----
Da: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Per conto di Shawn Drew
Inviato: giovedì 24 maggio 2018 04:50
A: ADSM-L@VM.MARIST.EDU
Oggetto: Re: [ADSM-L] R: [ADSM-L] Can't start the server

I had this problem when testing a restore to a different server with a slight different version of the gskit installed as a part of the client.
Check if this is the version you have installed:

http://www-01.ibm.com/support/docview.wss?uid=swg22007298

I was able to fix it by downgrading the gskit that comes with the TSM client and baclient.
Not sure if the appropriate fix levels are available. The article says AIX but affected me on RHEL6/7



On 5/23/2018 11:09 AM, Tommaso Bollini wrote:
> Hi Eric, yes I can do db2start or log on with the instance user on DB2. My get dbm cfg output is below.
> I've found that the stash file, it is written by the server: if I remove that file, the Spectrum recreates it.
> There is my problem: the file will have zero bytes in size; so no stash -> no login and after the final error SQL30082N for username/password invalid.
>
> Do you know how Spectrum read that password?
>
> I have tried this:
> http://www-01.ibm.com/support/docview.wss?uid=swg21642264
> But unsuccesfully. It seems that the SRVCON_PW_PLUGIN parameter its mandatory.
>
> db2 => get dbm cfg
>
> Database Manager Configuration
>
> Node type = Enterprise Server Edition with local and remote
> clients
>
> Database manager configuration release level = 0x1000
>
> CPU speed (millisec/instruction) (CPUSPEED) = 3.267047e-07
> Communications bandwidth (MB/sec) (COMM_BANDWIDTH) = 1.000000e+02
>
> Max number of concurrently active databases (NUMDB) = 32
> Federated Database System Support (FEDERATED) = NO
> Transaction processor monitor name (TP_MON_NAME) =
>
> Default charge-back account (DFT_ACCOUNT_STR) =
>
> Java Development Kit installation path (JDK_PATH) = /home/tsmadmin/sqllib/java/jdk64
>
> Diagnostic error capture level (DIAGLEVEL) = 3
> Notify Level (NOTIFYLEVEL) = 3
> Diagnostic data directory path (DIAGPATH) = /home/tsmadmin/sqllib/db2dump/
> Current member resolved DIAGPATH = /home/tsmadmin/sqllib/db2dump/
> Alternate diagnostic data directory path (ALT_DIAGPATH) =
> Current member resolved ALT_DIAGPATH =
> Size of rotating db2diag & notify logs (MB) (DIAGSIZE) = 1024
>
> Default database monitor switches
> Buffer pool (DFT_MON_BUFPOOL) = ON
> Lock (DFT_MON_LOCK) = OFF
> Sort (DFT_MON_SORT) = OFF
> Statement (DFT_MON_STMT) = OFF
> Table (DFT_MON_TABLE) = OFF
> Timestamp (DFT_MON_TIMESTAMP) = ON
> Unit of work (DFT_MON_UOW) = OFF
> Monitor health of instance and databases (HEALTH_MON) = OFF
>
> SYSADM group name (SYSADM_GROUP) = TSMSRVRS
> SYSCTRL group name (SYSCTRL_GROUP) =
> SYSMAINT group name (SYSMAINT_GROUP) =
> SYSMON group name (SYSMON_GROUP) =
>
> Client Userid-Password Plugin (CLNT_PW_PLUGIN) =
> Client Kerberos Plugin (CLNT_KRB_PLUGIN) =
> Group Plugin (GROUP_PLUGIN) =
> GSS Plugin for Local Authorization (LOCAL_GSSPLUGIN) =
> Server Plugin Mode (SRV_PLUGIN_MODE) = UNFENCED
> Server List of GSS Plugins (SRVCON_GSSPLUGIN_LIST) =
> Server Userid-Password Plugin (SRVCON_PW_PLUGIN) = dsmdb2pw
> Server Connection Authentication (SRVCON_AUTH) = NOT_SPECIFIED
> Cluster manager =
>
> Database manager authentication (AUTHENTICATION) = SERVER
> Alternate authentication (ALTERNATE_AUTH_ENC) = NOT_SPECIFIED
> Cataloging allowed without authority (CATALOG_NOAUTH) = NO
> Trust all clients (TRUST_ALLCLNTS) = YES
> Trusted client authentication (TRUST_CLNTAUTH) = CLIENT
> Bypass federated authentication (FED_NOAUTH) = NO
>
> Default database path (DFTDBPATH) = /home/tsmadmin
>
> Database monitor heap size (4KB) (MON_HEAP_SZ) = AUTOMATIC(90)
> Java Virtual Machine heap size (4KB) (JAVA_HEAP_SZ) = 2048
> Audit buffer size (4KB) (AUDIT_BUF_SZ) = 0
> Global instance memory (4KB) (INSTANCE_MEMORY) = AUTOMATIC(22523032)
> Member instance memory (4KB) = GLOBAL
> Agent stack size (AGENT_STACK_SZ) = 1024
> Sort heap threshold (4KB) (SHEAPTHRES) = 0
>
> Directory cache support (DIR_CACHE) = YES
>
> Application support layer heap size (4KB) (ASLHEAPSZ) = 15
> Max requester I/O block size (bytes) (RQRIOBLK) = 65535
> Workload impact by throttled utilities(UTIL_IMPACT_LIM) = 10
>
> Priority of agents (AGENTPRI) = SYSTEM
> Agent pool size (NUM_POOLAGENTS) = AUTOMATIC(100)
> Initial number of agents in pool (NUM_INITAGENTS) = 0
> Max number of coordinating agents (MAX_COORDAGENTS) = AUTOMATIC(200)
> Max number of client connections (MAX_CONNECTIONS) = AUTOMATIC(MAX_COORDAGENTS)
>
> Keep fenced process (KEEPFENCED) = YES
> Number of pooled fenced processes (FENCED_POOL) = AUTOMATIC(MAX_COORDAGENTS)
> Initial number of fenced processes (NUM_INITFENCED) = 0
>
> Index re-creation time and redo index build (INDEXREC) = RESTART
>
> Transaction manager database name (TM_DATABASE) = 1ST_CONN
> Transaction resync interval (sec) (RESYNC_INTERVAL) = 180
>
> SPM name (SPM_NAME) = tsp
> SPM log size (SPM_LOG_FILE_SZ) = 256
> SPM resync agent limit (SPM_MAX_RESYNC) = 20
> SPM log path (SPM_LOG_PATH) =
>
> TCP/IP Service name (SVCENAME) = 51500
> Discovery mode (DISCOVER) = SEARCH
> Discover server instance (DISCOVER_INST) = ENABLE
>
> SSL server keydb file (SSL_SVR_KEYDB) =
> SSL server stash file (SSL_SVR_STASH) =
> SSL server certificate label (SSL_SVR_LABEL) =
> SSL service name (SSL_SVCENAME) =
> SSL cipher specs (SSL_CIPHERSPECS) =
> SSL versions (SSL_VERSIONS) =
> SSL client keydb file (SSL_CLNT_KEYDB) =
> SSL client stash file (SSL_CLNT_STASH) =
>
> Maximum query degree of parallelism (MAX_QUERYDEGREE) = ANY
> Enable intra-partition parallelism (INTRA_PARALLEL) = NO
>
> Maximum Asynchronous TQs per query (FEDERATED_ASYNC) = 0
>
> No. of int. communication buffers(4KB)(FCM_NUM_BUFFERS) = AUTOMATIC(4096)
> No. of int. communication channels (FCM_NUM_CHANNELS) = AUTOMATIC(2048)
> Inter-node comm. parallelism (FCM_PARALLELISM) = 1
> Node connection elapse time (sec) (CONN_ELAPSE) = 10
> Max number of node connection retries (MAX_CONNRETRIES) = 5
> Max time difference between nodes (min) (MAX_TIME_DIFF) = 60
>
> db2start/db2stop timeout (min) (START_STOP_TIME) = 10
>
> WLM dispatcher enabled (WLM_DISPATCHER) = NO
> WLM dispatcher concurrency (WLM_DISP_CONCUR) = COMPUTED
> WLM dispatcher CPU shares enabled (WLM_DISP_CPU_SHARES) = NO
> WLM dispatcher min. utilization (%) (WLM_DISP_MIN_UTIL) = 5
>
> Communication buffer exit library list (COMM_EXIT_LIST) =
> Current effective arch level (CUR_EFF_ARCH_LVL) = V:10 R:5 M:0 F:7 I:0 SB:0
> Current effective code level (CUR_EFF_CODE_LVL) = V:10 R:5 M:0 F:7 I:0 SB:35354
>
> Keystore type (KEYSTORE_TYPE) = NONE
> Keystore location (KEYSTORE_LOCATION) =
>
>
>
>
> It seems a problem related to the Spectrum Protect binary. I can
>
> -----Messaggio originale-----
> Da: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Per conto di
> Loon, Eric van (ITOPT3) - KLM
> Inviato: mercoledì 23 maggio 2018 16:13
> A: ADSM-L@VM.MARIST.EDU
> Oggetto: Re: [ADSM-L] Can't start the server
>
> Hi Tommaso,
> I think this file should contain the userid and password used by TSM to connect to DB2. Are you able to restore this file from a recent backup?
> What happens when you log on to the instance user and issue a db2start command? If you can start db2 successful, do you receive output from the following command:
> $ db2 get dbm cfg
> Kind regards,
> Eric van Loon
> Air France/KLM Storage Engineering
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf
> Of Tommaso Bollini
> Sent: woensdag 23 mei 2018 15:37
> To: ADSM-L@VM.MARIST.EDU
> Subject: R: [ADSM-L] Can't start the server
>
> Hi Eric my errors are around that "digest file":
> Wed May 23 15:10:20 2018 11141 ReadSha1[443] Entering Wed May 23 15:10:20 2018 11141 ReadSha1[482] Opening file /home/tsmadmin/sqllib/tsmdbdata.TSMDB1 to read digest Wed May 23 15:10:20 2018 11141 ReadSha1[507] Only 0 bytes of 8 read from digest file Wed May 23 15:10:20 2018 11141 ValidatePassword[1070] Could not read saved digest Wed May 23 15:10:20 2018 11141 ValidatePasswordWithOS[1928] calling vfork() Wed May 23 15:10:20 2018 11141 ValidatePasswordWithOS[1956] Created process 11403 for password validation Wed May 23 15:10:20 2018 11403 dsmckpwd.c[182] Entering. Module version 7.1.7.0(71) Wed May 23 15:10:20 2018 11403 dsmckpwd.c[213] Waiting for request Wed May 23 15:10:20 2018 11403 dsmckpwd.c[226] Request received of type 1 Wed May 23 15:10:20 2018 11403 dsmckpwd.c[444] Validing with service "login"
> Wed May 23 15:10:20 2018 11403 dsmckpwd.c[458] Authenticating user.
> Wed May 23 15:10:20 2018 11403 dsmckpwd.c[356] ConvFunc entered with 1 msgs.
> Wed May 23 15:10:20 2018 11403 dsmckpwd.c[368] 0 msg_style PAM_PROMPT_ECHO_OFF received...continue.
> Wed May 23 15:10:20 2018 11403 dsmckpwd.c[462] Error 7 from
> pam_authenticate: Authentication failure Wed May 23 15:10:20 2018
> 11403 dsmckpwd.c[490] Completed with rc=2 Wed May 23 15:10:20 2018
> 11403 dsmckpwd.c[276] Exiting
>
> If I remove the file "/home/tsmadmin/sqllib/tsmdbdata.TSMDB1" (tsmadmin it's my instance account), I find a new file, with 0 bytes size.
> The startup dead with:
>
> ANR0162W SQL30082N Security processing failed with reason "24"
> ("USERNAME AND/OR PASSWORD INVALID" SQLSTATE=08001)
>
> Regards.
>
> -----Messaggio originale-----
> Da: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Per conto di
> Richard van Denzel
> Inviato: mercoledì 23 maggio 2018 14:39
> A: ADSM-L@VM.MARIST.EDU
> Oggetto: Re: [ADSM-L] Can't start the server
>
> I've seen this also quite recent. TSM was started with the service command (RHEL 6) and stopped by issueing HALT.
> The trying the service connand again to start resulted in a similar error.
>
> Sent from my Samsung S7 Edge
>
> Op wo 23 mei 2018 14:34 schreef Loon, Eric van (ITOPT3) - KLM <
> Eric-van.Loon@klm.com>:
>
>> Hi Tommaso,
>> Is the whole directory /home/tsmadmin/sqllib empty? I remember I have
>> seen this once in the past where the instance upgrade part failed
>> during a TSM server upgrade. This can be fixed by running the command
>> /opt/tivoli/tsm/db2/instance/db2iupdt <instance_user> Kind regards,
>> Eric van Loon Air France/KLM Storage Engineering
>>
>> -----Original Message-----
>> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf
>> Of Tommaso Bollini
>> Sent: dinsdag 22 mei 2018 17:42
>> To: ADSM-L@VM.MARIST.EDU
>> Subject: Can't start the server
>>
>> Hi specialist!
>> In the afternoon we have done an halt of the Spectrum Server 7.1.7
>> for an upgrade hardware on the server.
>> I can't start no more my "tsmadmin" instance. I have found this error
>> in
>> db2diag.log:
>>
>> 2018-05-22-16.50.36.339711+120 I77423730E538 LEVEL: Error
>> PID : 28275 TID : 140558731306752 PROC : db2sysc 0
>> INSTANCE: tsmadmin NODE : 000 DB : TSMDB1
>> APPHDL : 0-97
>> HOSTNAME: tsp
>> EDUID : 26 EDUNAME: db2agent (TSMDB1) 0
>> FUNCTION: DB2 UDB, bsu security, sqlexLogPluginMessage, probe:20 DATA #1 :
>> String with size, 143 bytes security plugin encountered an error
>> User: tsmadmin
>> File: /home/tsmadmin/sqllib/tsmdbdata.TSMDB1
>> Error: Error reading contents of digest file.
>>
>> Infact:
>>
>> /home/tsmadmin/sqllib/tsmdbdata.TSMDB1: empty
>>
>> Do you know how can correct this situation?
>>
>> Regards.
>> Tommaso Bollini
>> ********************************************************
>> For information, services and offers, please visit our web site:
>> http://www.klm.com. This e-mail and any attachment may contain
>> confidential and privileged material intended for the addressee only.
>> If you are not the addressee, you are notified that no part of the
>> e-mail or any attachment may be disclosed, copied or distributed, and
>> that any other action related to this e-mail or attachment is
>> strictly prohibited, and may be unlawful. If you have received this
>> e-mail by error, please notify the sender immediately by return e-mail, and delete this message.
>>
>> Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or
>> its employees shall not be liable for the incorrect or incomplete
>> transmission of this e-mail or any attachments, nor responsible for
>> any delay in receipt.
>> Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
>> Dutch
>> Airlines) is registered in Amstelveen, The Netherlands, with
>> registered number 33014286
>> ********************************************************
>>
> ********************************************************
> For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message.
>
> Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt.
> Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
> Dutch Airlines) is registered in Amstelveen, The Netherlands, with
> registered number 33014286
> ********************************************************
>
This message was imported via the External PhorumMail Module
Sorry, only registered users may post in this forum.

Click here to login