After server reboot agents and mdm not recognised anymore

[tobiasperschon 0]

I'm using ERA on an CentOS 7 x64 with MariaDB. ERA, MDM, an Agent, MariaDB, Tomcat are installed on the server. (Firewall Ports opened are 2223,2222,9981,9980,443)

Everything seems to be working - ASAP tasks are starting with +30 min delay but thats not the issue at hand.

 

After installing updates I rebooted the server and now all the clients and the server itself wich were displayed with the Symbols for Agent and MDM are now in the list but the symbols are missing.

The MDM server is now not selectable for device enrolment tasks, but everything worked before the reboot.

New Clients with Agents show up in the Lost and Found but don't get the symbol for "agent". There is also some of the client info missing (under details)

 

There are no really useful (to me) error messages in the logs:

 

/var/log/eset/RemoteAdministrator/Server/trace.log

2015-08-30 09:36:49 Error: CReplicationModule [Thread 7f53097f2700]: CStepProcessor: Failed to process network message of type 202 because of missing replication context
2015-08-30 10:10:00 Error: CReplicationModule [Thread 7f530aff5700]: CStepProcessor: Failed to process network message of type 202 because of missing replication context
2015-08-30 11:01:46 Error: CReplicationModule [Thread 7f530cff9700]: CStepProcessor: Failed to process network message of type 204 because of missing replication context
2015-08-30 13:06:08 Error: CReplicationModule [Thread 7f530a7f4700]: CStepProcessor: Failed to process network message of type 204 because of missing replication context
2015-08-30 18:14:03 Error: NetworkModule [Thread 7f5326ffd700]: Error in SendCallback: Broken pipe;Error code: 32; SessionId:2132
2015-08-30 19:38:01 Error: CReplicationModule [Thread 7f530b7f6700]: CStepProcessor: Failed to process network message of type 209 because of missing replication context
2015-08-30 19:38:01 Error: CReplicationModule [Thread 7f530b7f6700]: CStepProcessor: Failed to process network message of type 209 because of missing replication context
2015-08-30 19:38:01 Error: CReplicationModule [Thread 7f530b7f6700]: CStepProcessor: Failed to process network message of type 209 because of missing replication context
2015-08-30 19:38:01 Error: CReplicationModule [Thread 7f530b7f6700]: CStepProcessor: Failed to process network message of type 209 because of missing replication context
 

 

/var/log/eset/RemoteAdministrator/Agent/trace.log

2015-08-30 08:47:32 Error: CMDMCoreConnectorModule [Thread 7fa7d77f6700]: Cannot connect to MDMCore using IPv6: Net Exception, Address family not supported
2015-08-30 08:47:32 Error: CMDMCoreConnectorModule [Thread 7fa7d77f6700]: Net Exception
2015-08-30 08:47:32 Error: CMDMCoreConnectorModule [Thread 7fa7d77f6700]: Net Exception

 

but these errors don't occur periodically...

 

Can somebody point me in the right direction?

Do you need additional infos?

[Marcos 5,070]

First of all MariaDB is not officially supported by ERA v6. Will ask developers to have a look at the excerpt from the trace log if the error could be caused by using an unsupported db.

[tobiasperschon 0]

First of all MariaDB is not officially supported by ERA v6. Will ask developers to have a look at the excerpt from the trace log if the error could be caused by using an unsupported db.

 

MariaDB is supposed to be an drop-in replacement for mysql, so I thought that I could use it instead of mysql on centos.

Are these errors connected to the "missing symbols"?

[Megachip 5]

 

/var/log/eset/RemoteAdministrator/Agent/trace.log

2015-08-30 08:47:32 Error: CMDMCoreConnectorModule [Thread 7fa7d77f6700]: Cannot connect to MDMCore using IPv6: Net Exception, Address family not supported

2015-08-30 08:47:32 Error: CMDMCoreConnectorModule [Thread 7fa7d77f6700]: Net Exception

2015-08-30 08:47:32 Error: CMDMCoreConnectorModule [Thread 7fa7d77f6700]: Net Exception

This is a known, but seems still not fixed, bug with the mdm daemon.

 

See here and here.

[tobiasperschon 0]

okay I uninstalled MDM and I will wait if the agents on the clients are recognised again.

 

Edit: No luck so far... I also reinstalled Agent on the ERA server

Edited September 1, 2015 by tobiasperschon

[tobiasperschon 0]

Update:

 

ERA is starting to drive me crazy. I did a full fresh reinstall with ERA 6.2 now only tomcat, era and an agent are present on the server. Era Server appeared in the list with the agent symbol (only the agent symbol, I think there is also a symbol for era server?) then I added some clients - on all of them I removed the old one and did a fresh reinstall of the agent. Replication is working but in ERA Console there is a mixed picture: one out of three displayed agent and endpoint symbol and also PC Infos are displayed correctly (under details) the other two don't display any OS or PC info and no agent symbol and the don't show the installed endpoint AV. In addition after waiting a night the agent symbol from the era server entry disapeared in addition with all the OS and PC information...

 

what is going on? why is stuff working only sometimes, while other times only working half the way?

[Marcos 5,070]

As for the record "2015-08-30 08:47:32 Error: CMDMCoreConnectorModule [Thread 7fa7d77f6700]: Cannot connect to MDMCore using IPv6: Net Exception, Address family not supported", this means that communication with agents via IPv6 failed. Then communication via IPv4 was attempted which seems to have succeeded as there's no mention of that error with regard to IPv4.

 

Installed ERA Server is not indicated by an icon. There are only icons for ERA components (MDM, RDS, Agent) and an icon symbolizing the type of the OS (desktop/server). If you don't see an agent icon for a particular computer after reinstalling agent followed by sending a wake-up call, check the agent trace log on the client for errors. You can pm me the trace log for analysis.

[tobiasperschon 0]

If you don't see an agent icon for a particular computer after reinstalling agent followed by sending a wake-up call, check the agent trace log on the client for errors. You can pm me the trace log for analysis.

 

thank you for your offer! I just reinstalled the complete server with Debian 8 (with Debian 7 the era console could not connect to era server - maybe because of outdated openssl-lib) and now everything is working perfectly. All added computers are showing up with all symbols. Tasks get executed immediately and results are seen almost instantly in ERA console.

 

Is it now possible with ERA 6.2 to install MDM on the same server?