Hi, when starting up asemon logger, i am getting an error message in the log. The login and user exist. Does the asemon_logger user need to be aliased to dbo? Server user id 106 is asemon_logger
2023/03/01 11:28:30.887 main - ERROR connectSRV (1). Srv=<SERVERNAME> : com.sybase.jdbc4.jdbc.SybSQLException: Server user id 106 is not a valid user in database 'asemon'
Exception in thread "main" java.lang.NullPointerException
at asemon_logger.CnxMgr$ArchCnxPool.putArchCnx(CnxMgr.java:126)
at asemon_logger.Asemon_logger.main(Asemon_logger.java:581)
Thanks
Michael
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Michael,
on the Archive Server, the asemon login must be owner or alias to dbo in asemon database
On monitored servers, asemon login (if not sa) must be defined as a simple user in all databases
(in order to get object_names in all databases)
Best regards
JP
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Michael
it means asemon is already connected to your monitored server
This is a security in asemon_logger to avoid multi reconnections to same server which could use all available connections
You should terminate the connected asemon_logger or kill manually the established connection
Sometime, after a network problem, a connection can remain and disappears only after the network keep alive time out (2h hours by default)
Bestregards
JP
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, when starting up asemon logger, i am getting an error message in the log. The login and user exist. Does the asemon_logger user need to be aliased to dbo? Server user id 106 is asemon_logger
2023/03/01 11:28:30.887 main - ERROR connectSRV (1). Srv=<SERVERNAME> : com.sybase.jdbc4.jdbc.SybSQLException: Server user id 106 is not a valid user in database 'asemon'
Exception in thread "main" java.lang.NullPointerException
at asemon_logger.CnxMgr$ArchCnxPool.putArchCnx(CnxMgr.java:126)
at asemon_logger.Asemon_logger.main(Asemon_logger.java:581)
Hi Michael,
on the Archive Server, the asemon login must be owner or alias to dbo in asemon database
On monitored servers, asemon login (if not sa) must be defined as a simple user in all databases
(in order to get object_names in all databases)
Best regards
JP
Hi JP,
Thank you for that, all sorted now. I have started the logger and we are getting this error:
2023/03/14 12:21:29.336 <SERVERNAME>_SysConf - ERROR : asemon_logger is already connected. Closing this connection.
2023/03/14 12:21:45.005 <SERVERNAME>_CachePool - ERROR : asemon_logger is already connected. Closing this connection.
2023/03/14 12:21:45.883 <SERVERNAME>_ProcCache - ERROR : asemon_logger is already connected. Closing this connection.
2023/03/14 12:21:46.079 <SERVERNAME>_MonConf - ERROR : asemon_logger is already connected. Closing this connection.
2023/03/14 12:21:51.858 <SERVERNAME>_SysDev - ERROR : asemon_logger is already connected. Closing this connection.
2023/03/14 12:22:05.467 <SERVERNAME>_MemUsage - ERROR : asemon_logger is already connected. Closing this connection.
Of the 13 servers we have in the config file to monitor, only one is working.
Thanks
Michael
Hi Michael
it means asemon is already connected to your monitored server
This is a security in asemon_logger to avoid multi reconnections to same server which could use all available connections
You should terminate the connected asemon_logger or kill manually the established connection
Sometime, after a network problem, a connection can remain and disappears only after the network keep alive time out (2h hours by default)
Bestregards
JP
Thanks JP, this is working now.