Hi all
I've just installed SA1101 on SLES9 SP3.
Using the system command "ps -axw" I noticed, in addition to standard
dbsrv11 process, a java process "samonitor" ...

Who have launched it ? I have only started dbsrv11 using the following
/etc/init.d script:

....
/opt/sqlanywhere11/bin64/dbsrv11 -gp 4096 -ud -xtcpip(Port=2640) -c8m
-nAsa11DbServ -o/opt/sqlanywhere11/AsaLog.txt -gk ALL
/opt/sqlanywhere11/demo.db
....

This is the Log:
================================================== =====================
I. 11/08 01:04:00. Could not connect to ServerMonitor:
I. 11/08 01:04:00. connectionString =
ENG=Asa11DbServ;IDLE=0;LTO=900;LINKS=TCPIP
(IP=DevServ:2640;VERIFY=no;DOBROAD=none);;CON=Moni tor1
I. 11/08 01:04:00. userId = mdba
I. 11/08 01:04:00. java.sql.SQLException: [Sybase][ODBC Driver][SQL
Anywhere]Invalid user ID or password
I. 11/08 01:04:00. at
ianywhere.ml.jdbcodbc.IDriver.makeODBCConnection(N ative Method)
I. 11/08 01:04:00. at
ianywhere.ml.jdbcodbc.IDriver.connect(IDriver.java :669)
I. 11/08 01:04:00. at
java.sql.DriverManager.getConnection(DriverManager .java:582)
I. 11/08 01:04:00. at
java.sql.DriverManager.getConnection(DriverManager .java:185)
I. 11/08 01:04:00. at
com.ianywhere.serverMonitor.DataCollector.getServe rMonitorConnection(DataCollector.java:260)
I. 11/08 01:04:00. at
com.ianywhere.serverMonitor.DataCollector$MonitorI nitializer.run(DataCollector.java:373)
I. 11/08 01:04:00. at
java.util.concurrent.ThreadPoolExecutor$Worker.run Task(ThreadPoolExecutor.java:885)
I. 11/08 01:04:00. at
java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:907)
I. 11/08 01:04:00. at java.lang.Thread.run(Thread.java:619)
I. 11/08 01:04:00. java.lang.NullPointerException
I. 11/08 01:04:00. at
com.ianywhere.serverMonitor.SAMonitor.<init>(SAMon itor.java:54)
I. 11/08 01:04:00. at
com.ianywhere.serverMonitor.SAMonitor.getNewMonito r(SAMonitor.java:34)
I. 11/08 01:04:00. at
com.ianywhere.serverMonitor.DataCollector$MonitorI nitializer.run(DataCollector.java:376)
I. 11/08 01:04:00. at
java.util.concurrent.ThreadPoolExecutor$Worker.run Task(ThreadPoolExecutor.java:885)
I. 11/08 01:04:00. at
java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:907)
I. 11/08 01:04:00. at java.lang.Thread.run(Thread.java:619)
================================================== =============

Thanks.

Hi Nicola,

This is the SQL Anywhere Monitor, a tool to monitor SQL Anywhere and MobiLink servers. It is included with the full SQL Anywhere install, and it is also packaged in a standalone 'deployment' installer.

If it's running, it means it's either been started manually by means of running the samonitor.sh script or a service for it has been created as a result of running the standalone SA Monitor installer.
Does the directory /opt/samonitor11 exist? If so, the standalone installer was likely run. If not, find out the pid of this dbsrv11 process using ps. Then, look to see where the symbolic link
/proc/<pid>/cwd points to. This may give you a hint as to where the Monitor resides.

Why it's failing to connect is a separate question. Once you find out where it is being run from, and if you're interested in trying it out, we can work on that.

Ray

Nicola Cisternino wrote:

Hi Ray, and thanks for replay.

I have understood why .....
I only started dbsrv11 in my script but in the .db list to start I
included "samonitor.db" too !
When the samonitor.db is started either at startup or manually by Sybase
Central, a java process start automatically ...
In the next days I will investigate on the SA Monitor features ;-)
Thanks.
Nicola.


Ray Ruvinskiy [Sybase iAnywhere] ha scritto:

That makes sense.

For the SQL Anywhere Monitor to work properly, you should use the /opt/sqlanywhere11/bin32/samonitor.sh script to start it. Starting it directly will not work.

Ray

Nicola Cisternino wrote: