Issue with authentification of sccagent on SCC 3.3 on IQ16 SP8 on Linux

[Former Member]

I've got an issue trying to connect to sccagent using SC on a fresh installed IQ16 SP8 on 64bit Linux. When tying to authenticate scc agent for a IQ DB server via SCC's admin console, I'm getting this message:

SCC agent localhost:9999 does not know Sybase IQ version string. Something is wrong with the IQ Agent plug-in.. SCC agent localhost:9999 does not know Sybase IQ version string. Something is wrong with the IQ Agent plug-in.

The error is also printed to $SYBASE/SCC-3_3/log/gateway.log

Any way to work this around?

[tayeb_hadjou]

Hi,

To compare with a couple of SCC reported issues, please answer questions:

I can see the Kernel version, but what is the exact Linux OS release (Suse, Redhat, ..)?

Do you use LDAP or other authentication methods?

What is the value of environement variable LANG SCC started with?

By the way, with IQ 16 SP08 and upper it is recommended to use IQ Cockpit.

Regards,

Tayeb.

[andreas_zigann]

Hello Tayeb,

thanks for the information with the Cockpit, I will check if it works.

I have installed IQ 16.08.32 today at a new server with a local user sybadm.

LANG=en_US.UTF-8

I have found note 1975917 which describes the problem on japanese based Linux. I tried to use

SALANG=EN

IQLANG=EN

but this did not solve the problem.

For this System I use a SLES for SAP 11 SP3 (Linux version 3.0.101-0.35-default (gcc version 4.3.4 [gcc-4_3-branch revision 152973] (SUSE Linux)).

I had several Problems with the environment of the user, because the SCC had some bad variable definitions, espacially the sccd, but I got it running.

First of all, I will try the cockpit. Perhaps I try also a installation with user root, but I do not like it.

If you have any idea how to use the SCC it would be nice.

Best Regards

Andreas

[saroj_bagai]

Do you have previous SCC installation or any other SCC installation on the same machine,  If yes, then stop that SCC. Is your IQ server running on same machine as SCC or on different machine,  If it IQ instance is running on different machine, then start SCC agent on IQ instance machine as well. Instead of local host, try to use full qualified hostname, check you /etc/hosts.

[andreas_zigann]

Hello,

I have already stopped sccd. I were able to start the cockpit and to call the website from my workplace. At the logon screen, I can not select a System, and a login with sccadmin is not possible (no reaction at the Screen).

I found following Information, but it don't work.

SAP IQ Cockpit (New) - What's New in SAP IQ 16.0 - SAP Library

SAP IQ Cockpit uses server-based authentication, which                    means that an SAP IQ system will not appear in the                    Login screen until an IQ database is created and started. In order to log into                        SAP IQ Cockpit for the first time, you can install                    either SAP IQ Cockpit or                        SAP Control Center to create an initial                        database:

• Start SAP IQ Cockpit, and create the demo                            database. Then, login using SAP IQ Cockpit and                            create the IQ database.
• Or, use SAP Control Center to create an IQ                            database. Then, login using SAP IQ Cockpit.

I have created and started the demo database and have restarted the cockpit demon. Nothing has changed.

Best Regards

Andreas

[saroj_bagai]

If your IQ demo database is up and running and IQ cockpit is still not able to discover it,  I would clear browser cache, stop IQ cockpit. Restart IQ cockpit, wait 5 min then connect using browser.   Cockpit discovery should be able to discover your IQ demo server. You will need to use IQ server login  e.g  DBA/<password>

also test with dblocate  to see if dblocate is able to locate your  IQ demo server

[andreas_zigann]

That was right.

I have

- restarted demo database

- checked if dblocate shows it

- restarted cockpitd

- waited several minutes

- was able to connect to iqdemo with dba

When creating the new database I get a new error:

Unable to connect to Cockpit agent hges2iq1:9999. Details: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: 127.0.0.1]

Best Regards

Andreas

[c_baker]

Just to throw my 2 cents in...have you checked your DNS or /etc/hosts settings and hostname?

Perhaps the listener for SCC or IQ is not starting correctly if you are using a DNS name that is not resolving to your correct IP address.

Chris

[andreas_zigann]

Thanks Chris, I have cheked it. DNS and /etc/hosts are consistent. Hostname and full qualified hostname are resolved by dns to the IP-Adress in /etc/hosts.

How can I check, if the agent is running correctly? The cockpit shows status unknown for demo database.

Regards

Andreas

[saroj_bagai]

cockpit agent port is 4992 and default uafadmin password is Sybase4me

http://scn.sap.com/docs/DOC-63709

For registering and authenticating agent

Registering and Authenticating an SAP IQ Cockpit Agent - About SAP IQ Cockpit - SAP Library

[andreas_zigann]

Thanks, I am just to unexperienced with sybase.

[saroj_bagai]

Are you able to register and authenticate Cockpit Agent?

[andreas_zigann]

Hello,

I could register the Agent but on authentication I get again the following error message:

com.sybase.scc.jmx.ManagedObjectGateway.err_invoke_op Cockpit agent hges2iq1:4992 does not know SAP IQ version string. Something is wrong with the IQ Agent plug-in.

The same on like during creating  a new database with SCC.

Best Regards

Andreas

[saroj_bagai]

could you please send us ls  for  $SYBASE/COCKPIT-4/plugins

and screen shots for Registering and authenticating Cockpit agent

[andreas_zigann]

Hello,

content of Directory:

CMAP  com.sybase.iq  IQ-CMAP  Readme.txt

Can you see the Pictures?

Best Regards

Andreas

[saroj_bagai]

Is your Cockpit running on same host machine as IQ server?  What is the exact version of IQ server?  and can you send us screen shot from Cockpit web interface/About

[andreas_zigann]

Hello,

yes the Cockpit is running on the same server. It is the version of 16.08.32 downloadable at sap marketplace.

Regards

Andreas

[saroj_bagai]

look like Repository might be messed up.  You can re-initialize Repository.

1. Stop SAP IQ Cockpit

2. cd $SYBASE/COCKPIT-4/services/Repository/db

3. mv repository.db  repository.db.org

4. mv repository.log repository.log.org

5.start SAP IQ Cockpit

6. clear browser cache

7. stop and restart browser

8. wait 5 min and then connect to IQ Cockpit  and to server

9. uafadmin default password is Sybase4me, you can change it later on

[andreas_zigann]

Hello,

this was solved by SAP Support via customer message by creating a link:

ln -s /usr/bin/env /bin/env

I were able to use env before but it might be hard coded to use /bin/env anywhere.

Best Regards

Andreas

[andreas_zigann]

Hello,

did you solve this problem?

I have got the sam now.

Regards

Andreas

[Former Member]

Well ... yes and no. First of all, I learned that IQ bundle needs to be installed as root as SCC seems to need it, even if it's stored below /opt/sybase or similar. fter playing further around it just happend to work.But I have no clue what in the end was the real missing point (so I didn't paste the answer here)

[claude]

Hi,

Please check if the firewall is blocking the connection of IQ Agent port.

Regards,

Claude

[Former Member]

Hi,

It's all running on localhost without active iptables as well as no SELinux or similar. Also netstat looks fine to me.

Proto Recv-Q Send-Q Local Address   
Foreign Address 
State
PID/Program name


tcp 
0
0 0.0.0.0:9998     
0.0.0.0:*       
LISTEN
-       



tcp 
0
0 0.0.0.0:9999     
0.0.0.0:*       
LISTEN
-       



tcp 
0
0 127.0.1.1:2000   
0.0.0.0:*       
LISTEN
-       



tcp 
0
0 127.0.0.1:2000   
0.0.0.0:*       
LISTEN
-       



tcp 
0
0 0.0.0.0:53650   
0.0.0.0:*       
LISTEN
-       



tcp 
0
0 0.0.0.0:38933   
0.0.0.0:*       
LISTEN
-       



tcp 
0
0 0.0.0.0:3638     
0.0.0.0:*       
LISTEN
-       



tcp 
0
0 0.0.0.0:22       
0.0.0.0:*       
LISTEN
-       



tcp 
0
0 0.0.0.0:8282     
0.0.0.0:*       
LISTEN
-       



tcp 
0
0 0.0.0.0:8283     
0.0.0.0:*       
LISTEN
-       



tcp6
0
0 :::3638         
:::*             
LISTEN
-       



tcp6
0
0 :::22           
:::*             
LISTEN
-       



udp 
0
0 0.0.0.0:52785   
0.0.0.0:*                   
-       



udp 
0
0 0.0.0.0:3726     
0.0.0.0:*                   
-       



udp 
0
0 0.0.0.0:53256   
0.0.0.0:*                   
-       



udp 
0
0 0.0.0.0:68       
0.0.0.0:*                   
-       



udp 
0
0 0.0.0.0:4446     
0.0.0.0:*                   
-       



udp 
0
0 0.0.0.0:5353     
0.0.0.0:*                   
-       



udp6
0
0 :::41359         
:::*                         
-       



udp6
0
0 :::33348         
:::*                         
-       



udp6
0
0 :::5353         
:::*                         
-

Also SCC seem sto start without major issue:

sybase@sql194-iq1:~$ source /opt/sybase/IQ.sh
Sourcing SYBASE.sh
sybase@sql194-iq1:~$ /opt/sybase/SCC-3_3/bin/scc.sh --start
Starting SCC Framework Server 3.3 GA
Copyright © 2013 SAP AG.  All rights reserved.
Agent Home:            /opt/sybase/SCC-3_3
Agent Version:        SCC Framework Server 3.3 GA (3.3.0.4872)
Node:                  sql194-iq1(127.0.1.1)
RMI Address:          sql194-iq1(127.0.1.1)
RMI Port:              9999
OS Name:              Linux
OS Version:            3.2.0-4-amd64
OS Architecture:      amd64
Platform:              linux
Bitwidth:              64
Available Processors:  4
Total Physical Memory: 6041 MB
Free Physical Memory:  5591 MB
java.library.path:    /opt/sybase/SCC-3_3/rtlib:/opt/sybase/SCC-3_3/bin/sa/bin_linux64
Java Home:            /opt/sybase/shared/SAPJRE-7_1_015_64BIT
Java Version:          1.7.0_51
Java VM Version:      7.1.015 24.51-b03
VM Process ID          3385@sql194-iq1
VM Arguments:          -Xms128m, -XX:MaxPermSize=128m, -XX:+HeapDumpOnOutOfMemoryError, -XX:HeapDumpPath=/opt/sybase/SCC-3_3/log, -Dcom.sybase.home=/opt/sybase, -Dcom.sybase.ua.toplevel=/opt/sybase/SCC-3_3, -Dcom.sybase.ua.home=/opt/sybase/SCC-3_3, -Dcom.sybase.platform=linux, -Djava.library.path=/opt/sybase/SCC-3_3/rtlib:/opt/sybase/SCC-3_3/bin/sa/bin_linux64, -Djava.security.policy=/opt/sybase/SCC-3_3/conf/java.policy, -Djava.util.logging.manager=com.sybase.ua.util.logging.bridge.JavaToLog4jLogManager, -Dcom.sybase.security.BootstrapConfigurationURL=file:////opt/sybase/SCC-3_3/conf/csibootstrap.properties
Message level:        WARN
Message Server State: Server Started
Warning:  org.apache.xerces.parsers.SAXParser: http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit
Compiler-Warnungen:
  WARNING:  'org.apache.xerces.jaxp.SAXParserImpl: http://javax.xml.XMLConstants/property/accessExternalDTD'
SAP Control Center successfully started
Agent RMI Connection URL:
    service:jmx:rmi:///jndi/rmi://sql194-iq1:9999/agent
SAP Control Center successfully started
SCC Web Console:
    http://sql194-iq1:8282/scc
    https://sql194-iq1:8283/scc
Type help for more options

Thanks,

Frank