Jump to content

Era console login page doesn't shown up


macros
 Share

Go to solution Solved by MartinK,

Recommended Posts

hello,

 

when my client open eset remote admin console it say "ERR_CONNECTION_REFUSED"

check tomcat service : started.

restart server: doesn't solved the problem.

 

here last error log.

Last error log

Go to last error
Scope    Time    Text
CReportsModule    2016-Jun-02 07:09:53    CleanupThread ending: 177c
Kernel    2016-Jun-02 07:09:53    Stopping module: CReplicationModule
CReplicationModule    2016-Jun-02 07:09:53    CReplicationModuleBase: Stopping module
CReplicationModule    2016-Jun-02 07:09:53    CReplicationManager: Stopping replication control messages processing
CReplicationModule    2016-Jun-02 07:09:53    CStepProcessor: Stopping
CReplicationModule    2016-Jun-02 07:09:53    CStepProcessor: Stopping work queue operations
CReplicationModule    2016-Jun-02 07:09:53    CStepProcessor: Worker thread f6c stopped
CReplicationModule    2016-Jun-02 07:09:53    CStepProcessor: Worker thread 1484 stopped
CReplicationModule    2016-Jun-02 07:09:53    CStepProcessor: Worker thread f90 stopped
CReplicationModule    2016-Jun-02 07:09:53    CStepProcessor: Worker thread 175c stopped
CReplicationModule    2016-Jun-02 07:09:53    CStepProcessor: Worker thread 1754 stopped
CReplicationModule    2016-Jun-02 07:09:53    CStepProcessor: Worker thread 1758 stopped
CReplicationModule    2016-Jun-02 07:09:53    CStepProcessor: Worker thread 16fc stopped
CReplicationModule    2016-Jun-02 07:09:53    CStepProcessor: Worker thread 360 stopped
CReplicationModule    2016-Jun-02 07:09:53    CReplicationModuleBase: Starting module
CReplicationModule    2016-Jun-02 07:09:53    CStepProcessor: Starting
CReplicationModule    2016-Jun-02 07:09:53    CStepProcessor: Creating 8 worker threads
CReplicationModule    2016-Jun-02 07:09:53    CReplicationManager: Starting replication control messages processing
Kernel    2016-Jun-02 07:09:53    Stop was not possible: CReplicationModule
Kernel    2016-Jun-02 07:09:53    Checking system bus content.
CReplicationModule    2016-Jun-02 07:09:53    CStepProcessor: Starting worker thread 1ac4
CReplicationModule    2016-Jun-02 07:09:53    CStepProcessor: Starting worker thread c9c
CReplicationModule    2016-Jun-02 07:09:53    CStepProcessor: Starting worker thread c98
CReplicationModule    2016-Jun-02 07:09:53    CStepProcessor: Starting worker thread 1adc
CReplicationModule    2016-Jun-02 07:09:53    CStepProcessor: Starting worker thread ca0
CReplicationModule    2016-Jun-02 07:09:53    CStepProcessor: Starting worker thread c94
CReplicationModule    2016-Jun-02 07:09:53    CStepProcessor: Starting worker thread d04
CReplicationModule    2016-Jun-02 07:09:53    CStepProcessor: Starting worker thread 1bf8
Kernel    2016-Jun-02 07:09:53    Restarting module: CReportsModule
CReportsModule    2016-Jun-02 07:09:53    CReportGenerator::Init() Looaded 151 Query usage definition.
CReportsModule    2016-Jun-02 07:09:53    0 MessageProcessorThread started: 19b8
CReportsModule    2016-Jun-02 07:09:53    1 MessageProcessorThread started: cb4
CReportsModule    2016-Jun-02 07:09:53    2 MessageProcessorThread started: c74
CReportsModule    2016-Jun-02 07:09:53    3 MessageProcessorThread started: 1990
CReportsModule    2016-Jun-02 07:09:53    CleanupThread started: 183c
CDatabaseModule    2016-Jun-02 07:09:56    Database connection down. Exception:[Microsoft][ODBC SQL Server Driver]

Login failed for user 'era_user'. (18456)
CDatabaseModule    2016-Jun-02 07:09:56    Sending DatabaseStatusUpdate: isDbRunning=0
CDatabaseModule    2016-Jun-02 07:09:56    Database connection down. Exception:[Microsoft][ODBC SQL Server Driver][sql Server]Login failed for user 'era_user'. (18456)
CDataMinersModule    2016-Jun-02 07:09:56    CDefaultWriteLogHandler: Failed to write log of type AUDIT_EVENT with error: [Microsoft][ODBC SQL Server Driver][sql Server]Login failed for user 'era_user'. (18456)
Kernel    2016-Jun-02 07:09:56    Restarting module 'CReportsModule' failed with: [Microsoft][ODBC SQL Server Driver][sql Server]Login failed for user 'era_user'. (18456)

Generated at 2016-Jun-02 07:09:56 (2016-Jun-02 15:09:56 local time)

 

 

and trace.log in attachment.

 

how to solved this problem.

 

thank you.

trace.log

Link to comment
Share on other sites

  • ESET Staff

According to trace log database is not running properly or its configuration is not correct. Please verify database is running. Have you been doing any backup/restore or other administrative operations with database server? This may happen also during windows update -> database may be unavailable for some time. Have you tried to restart whole system?

Link to comment
Share on other sites

Go to services and check SQL SERVER (ERASQL)-default or what name you changed it to for ESET and confirm this service is started. if so then restart this service, restart Apache Tomcat 

service, go into the properties of ESET Remote Admin server service and take off automatic delayed start to just Automatic and then restart this service as well after applying changes. 

Try to access the console now. 

Link to comment
Share on other sites

hello,

 

user said other vendor has touch the server and dont know what they do with the server, since then era cannot be access.

2 days ago, we clean reinstall era server with mysql 5.6. everything looks ok until today, they said era cannot be access.

login page say: connection time-out.

 

ERAS service: running

Tomcat service: running

Mysql service: running

Windows firewall: off

 

restart whole system, nothing change. problem persist.

 

here last error.log

 

Last error log

Go to last error
Scope    Time    Text
Kernel    2016-Jun-08 06:17:53    Starting module CSNMPTrapSenderModule
CSNMPTrapSenderModule    2016-Jun-08 06:17:53    Starting module
CSNMPTrapSenderModule    2016-Jun-08 06:17:53    Started module
Kernel    2016-Jun-08 06:17:53    Started module CSNMPTrapSenderModule (used 0 KB)
Kernel    2016-Jun-08 06:17:53    Starting module CSyslogSenderModule
Kernel    2016-Jun-08 06:17:53    Started module CSyslogSenderModule (used 0 KB)
Kernel    2016-Jun-08 06:17:53    Starting module CReportPrinterModule
Kernel    2016-Jun-08 06:17:53    Started module CReportPrinterModule (used 120 KB)
Kernel    2016-Jun-08 06:17:53    Starting module LicenseModule
Kernel    2016-Jun-08 06:17:53    Started module LicenseModule (used 24 KB)
Kernel    2016-Jun-08 06:17:53    Starting module CMonitorModule
SchedulerModule    2016-Jun-08 06:17:53    Received message: RegisterTimeEvent
CEmailSenderModule    2016-Jun-08 06:17:53    Starting worker thread 1780
Kernel    2016-Jun-08 06:17:53    Started module CMonitorModule (used 488 KB)
Kernel    2016-Jun-08 06:17:53    Starting module CRepositoryModule
SchedulerModule    2016-Jun-08 06:17:53    Received message: RegisterTimeEvent
CRepositoryModule    2016-Jun-08 06:17:53    Processing repository synchronization request
Kernel    2016-Jun-08 06:17:53    Started module CRepositoryModule (used 28 KB)
Kernel    2016-Jun-08 06:17:53    Starting module CLogExportModule
Kernel    2016-Jun-08 06:17:53    Started module CLogExportModule (used 12 KB)
Kernel    2016-Jun-08 06:17:53    Starting module CPoliciesModule
Kernel    2016-Jun-08 06:17:53    Started module CPoliciesModule (used 0 KB)
Kernel    2016-Jun-08 06:17:53    Starting module CUsersModule
Kernel    2016-Jun-08 06:17:53    Started module CUsersModule (used 0 KB)
Kernel    2016-Jun-08 06:17:53    Starting module ConsoleApiModule
CRepositoryModule    2016-Jun-08 06:17:53    Synchronizing with remote repository
CRepositoryModule    2016-Jun-08 06:17:53    Synchronizing repository with url 'hxxp://repository.eset.com/v1/'
SchedulerModule    2016-Jun-08 06:17:53    Received message: RegisterTimeEvent
ConsoleApiModule    2016-Jun-08 06:17:53    0 MessageProcessorThread started: 5a0
Kernel    2016-Jun-08 06:17:53    Started module ConsoleApiModule (used 92 KB)
Kernel    2016-Jun-08 06:17:53    Used memory after modules start-up is 55596 KB
Service    2016-Jun-08 06:17:53    Kernel started
CDataMinersModule    2016-Jun-08 06:17:53    CFunctionalityLogDataMiner: Scheduled first publishing of funcitonality logs with 5s delay
SchedulerModule    2016-Jun-08 06:17:53    Received message: RegisterSleepEvent
AutomationModule    2016-Jun-08 06:17:53    NotificationTaskHandler: There are 1782 known localizable symbol names.
AutomationModule    2016-Jun-08 06:17:53    StaticObjectChangeHandler: ScheduleCheck: Next static object changes check in 15 seconds.
SchedulerModule    2016-Jun-08 06:17:53    Received message: RegisterSleepEvent
SchedulerModule    2016-Jun-08 06:17:53    Received message: RegisterSleepEvent
AutomationModule    2016-Jun-08 06:17:53    CActionsFacade: LoadAllTriggersWithMessage: Failed to load all triggers. Automation will not operate correctly!
CDataMinersModule    2016-Jun-08 06:17:53    DataMinerCompletionHandler: Failed to execute completion handler with: The associated promise has been destructed prior to the associated state becoming ready.

Generated at 2016-Jun-08 06:17:53 (2016-Jun-08 14:17:53 local time)

 

trace.log in attachment

 

and thank you for help.

trace.log

Link to comment
Share on other sites

  • ESET Staff
  • Solution

We have similar reports being just now investigated. It does seem SERVER is not properly working with latest MySQL ODBC driver (5.3.6) released this year. Any chance driver has been updated recently?  You may check it's version in Control Panel -> Administrative Tools -> Data Sources (ODBC) in tab "Drivers". In case "MySQL ODBC 5.3 Unicode Driver" will be of version 5.3.6, revert it to version 5.3.4 (Download from MySQL archive: hxxp://downloads.mysql.com/archives/c-odbc/).

Edited by MartinK
Link to comment
Share on other sites

hello,

 

yes, Mysql ODBC driver version 5.03.06.

then, i just need to do uninstall mysql-connector-odbc from control panel, then install version 5.3.4?

 

thank you

Link to comment
Share on other sites

  • ESET Staff

hello,

 

yes, Mysql ODBC driver version 5.03.06.

then, i just need to do uninstall mysql-connector-odbc from control panel, then install version 5.3.4?

 

thank you

 

Yes, uninstall "MySQL Connector/ODBC 5.3" and install older version - it should be named the same, except version will be older. Be sure you are re-installing driver for proper platform (x64), as difference is hardly visible in control panel in case you have also x86 version installed.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...