Jump to content

ESET Remote Administrator on Debian, installation issue


Inknowa
 Share

Recommended Posts

Hi everyone, first, sorry about my english, I've got to improve it. I'm installing ESET Remote Administrator on a server running Debian, but I'm not an expert of Linux and I have issues constantly. I follow the steps of the install manual perfectly, but when I arrive to the part of the installation of the server, I've got an issue that I can't resolve. 

 

First, when I've got the next response:

 

Extracting archive, please wait...
Archive extracted to /tmp/tmp.fwDTVw37c7.
Checking OpenSSL ... done [OpenSSL 1.0.1t 3 May 2016]
Reading previous installation settings ... failure
Checking installed version... done
Status of current installation is: NEW
Checking database connection ... failure
 
Error: It is not possible to store big blocks of data in the database. Please reconfigure the database server first.
 
I've searched and I found that I've got to add a line in my my,cnf for this issue, but when I make it, I've got the same error. After that, I found that I have to add the configuration of innodb_log_file_size and innodb_log_files_in_group, but the problem is that when I make it, when I restart mysql server I've got the next error:
 
service mysql restart
Job for mysql.service failed. See 'systemctl status mysql.service' and 'journalctl -xn' for details.
 
I know I'm making something wrong, but I don't know where is the problem and I can't found a solution anywhere. Because of that, I put here my configuration of my.cnf and if somebody can help me it will make me a big favor:
 
#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "~/.my.cnf" to set user-specific options.
#
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# For explanations see
 
# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain "#" chars...
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
[client]
port            = 3306
socket          = /var/run/mysqld/mysqld.sock
 
# Here is entries for some specific programs
# The following values assume you have at least 32M ram
 
# This was formally known as [safe_mysqld]. Both versions are currently parsed.
[mysqld_safe]
socket          = /var/run/mysqld/mysqld.sock
nice            = 0
 
[mysqld]
#
# * Basic Settings
#
 
user            = mysql
pid-file        = /var/run/mysqld/mysqld.pid
socket          = /var/run/mysqld/mysqld.sock
port            = 3306
basedir         = /usr
datadir         = /var/lib/mysql
tmpdir          = /tmp
lc-messages-dir = /usr/share/mysql
skip-external-locking
max_allowed_packet = 33M
innodb_log_file_size = 200M
innodb_log_files_in_group = 2M
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address            = 127.0.0.1
#
# * Fine Tuning
#
key_buffer              = 16M
max_allowed_packet      = 4M
thread_stack            = 192K
thread_cache_size       = 8
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover         = BACKUP
#max_connections        = 100
#table_cache            = 64
#thread_concurrency     = 10
#
# * Query Cache Configuration
#
query_cache_limit       = 1M
query_cache_size        = 16M
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
# As of 5.1 you can enable the log at runtime!
#general_log_file        = /var/log/mysql/mysql.log
#general_log             = 1
#
# Error log - should be very few entries.
#
log_error = /var/log/mysql/error.log
#
# Here you can see queries with especially long duration
#slow_query_log_file = /var/log/mysql/mysql-slow.log
#slow_query_log      = 1
#long_query_time = 2
#log_queries_not_using_indexes
#
# The following can be used as easy to replay backup logs or for replication.
# note: if you are setting up a replication slave, see README.Debian about
#       other settings you may need to change.
#server-id              = 1
#log_bin                        = /var/log/mysql/mysql-bin.log
expire_logs_days        = 10
max_binlog_size         = 100M
#binlog_do_db           = include_database_name
#binlog_ignore_db       = include_database_name
#
# * InnoDB
#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!
# * Security Features
#
# Read the manual, too, if you want chroot!
# chroot = /var/lib/mysql/
#
# For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
#
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem
 
 
 
[mysqldump]
quick
quote-names
max_allowed_packet      = 16M
 
[mysql]
#no-auto-rehash # faster start of mysql but no tab completition
 
[isamchk]
key_buffer              = 16M
 
#
# * IMPORTANT: Additional settings that can override those from this file!
#   The files must end with '.cnf', otherwise they'll be ignored.
#
!includedir /etc/mysql/conf.d/
 

 

 

Thanks in advance!

Inknowa

Link to comment
Share on other sites

  • ESET Staff

Hi, I would recommend you to:

  1. backup your database (if you have any)
  2. uninstall mysql-server and uninstall ODBC connector (unixodbc libmyodbc)
  3. download and install mysql-server from official MySQL page hxxp://dev.mysql.com/downloads/repo/apt/
  4. download and install latest Generic Linux ODBC connector from hxxp://dev.mysql.com/downloads/connector/odbc/
Edited by janoo
Link to comment
Share on other sites

  • ESET Staff
max_allowed_packet = 33M

innodb_log_file_size = 200M
innodb_log_files_in_group = 2M

 

Hello,

 

parameter innodb_log_files_in_group is of numerical type and expects number between 1 and 100 according to documentation. I would suggest to try innodb_log_files_in_group = 2 and restart server.

Have you seen it using 2M somewhere in ESET documentation or KBs?

Link to comment
Share on other sites

Hi, thanks for your answers. Respect to the value of innodb_log_files_in_group, I forgot to say that I prove to put innodb_log_files_in_group = 2 without the M and it didn't works, for that reason I put 2M later. I'm going to follow your instructions janoo, and I will tell you the result. Thanks again

Link to comment
Share on other sites

  • ESET Staff

Hi, thanks for your answers. Respect to the value of innodb_log_files_in_group, I forgot to say that I prove to put innodb_log_files_in_group = 2 without the M and it didn't works, for that reason I put 2M later. I'm going to follow your instructions janoo, and I will tell you the result. Thanks again

 

Just checked again your configuration and there are two statements configuring value of max_allowed_packet in section [mysqld]. The second one (max_allowed_packet=4M) will override value of first and that will be reason why ERA database checks are failing.

 

Also be aware that ERA supports MySQL since version 5.5 and does not support MariaDB at all. More information about database check failures may be available in installer log: /var/log/eset/RemoteAdministrator/EraServerInstaller.log

Edited by MartinK
Link to comment
Share on other sites

Sorry, I have another problem. Following the steps included on the install manual, I've installed java and tomcat with the next command:

 

apt-get install openjdk-7-jdk tomcat7

 

It works good, but on the next step, that says to implement the packet of Web Console era.war with the command:

 

cp era.war /var/lib/tomcat7/webapps/

 

I have the next result:

 

cp era.war /var/lib/tomcat7/webapps/
cp: no se puede efectuar `stat' sobre «era.war»: No existe el fichero o el directorio
 
But I don't understand because I've installed tomcat7 without errors. Any suggestion?
 
EDIT: Resolved, I wasn't working on the correct directory.
Edited by Inknowa
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...