Arch Linux

glennph93

Member

Registered: 2013-07-21

Posts: 6

[Solved]Mariadb Not listening on port 3306? Mythtv cannot connect

Just did an update and it seems mythtv cannot connect to the database. The mariadb starts ok and is running.

● mariadb.service - MariaDB database server
   Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
   Active: active (running) since Sun 2017-09-03 14:20:44 EDT; 1min 45s ago
  Process: 517 ExecStartPost=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
  Process: 324 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ]   && syst
  Process: 315 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
 Main PID: 399 (mysqld)
   Status: "Taking your SQL requests now..."
    Tasks: 27 (limit: 4915)
   CGroup: /system.slice/mariadb.service
           └─399 /usr/bin/mysqld

Sep 03 14:20:41 mythtv mysqld[399]: 2017-09-03 14:20:41 139668301328256 [Note] InnoDB: Completed initialization of buffer pool
Sep 03 14:20:41 mythtv mysqld[399]: 2017-09-03 14:20:41 139668301328256 [Note] InnoDB: Highest supported file format is Barracuda.
Sep 03 14:20:43 mythtv mysqld[399]: 2017-09-03 14:20:43 139668301328256 [Note] InnoDB: 128 rollback segment(s) are active.
Sep 03 14:20:43 mythtv mysqld[399]: 2017-09-03 14:20:43 139668301328256 [Note] InnoDB: Waiting for purge to start
Sep 03 14:20:43 mythtv mysqld[399]: 2017-09-03 14:20:43 139668301328256 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.36-82.1 
Sep 03 14:20:43 mythtv mysqld[399]: 2017-09-03 14:20:43 139667771655936 [Note] InnoDB: Dumping buffer pool(s) not yet started
Sep 03 14:20:43 mythtv mysqld[399]: 2017-09-03 14:20:43 139668301328256 [Note] Plugin 'FEEDBACK' is disabled.
Sep 03 14:20:44 mythtv mysqld[399]: 2017-09-03 14:20:44 139668301328256 [Note] /usr/bin/mysqld: ready for connections.
Sep 03 14:20:44 mythtv mysqld[399]: Version: '10.1.26-MariaDB'  socket: '/run/mysqld/mysqld.sock'  port: 0  MariaDB Server
Sep 03 14:20:44 mythtv systemd[1]: Started MariaDB database server.
lines 1-22/22 (END)

The port: 0 above makes me think its not listening to port 3306. Also Nmap doesn't show it..

Other addresses for localhost (not scanned): ::1
rDNS record for 127.0.0.1: localhost.localdomain
Not shown: 993 closed ports
PORT     STATE SERVICE
22/tcp   open  ssh
80/tcp   open  http
111/tcp  open  rpcbind
139/tcp  open  netbios-ssn
445/tcp  open  microsoft-ds
631/tcp  open  ipp
2049/tcp open  nfs

Nmap done: 1 IP address (1 host up) scanned in 0.10 seconds

this is my.cnf:

cat /etc/mysql/my.cnf 
# Example MariaDB config file for medium systems.
#
# This is for a system with little memory (32M - 64M) where MariaDB plays
# an important part, or systems up to 128M where MariaDB is used together with
# other programs (such as a web server)
#
# MariaDB programs look for option files in a set of
# locations which depend on the deployment platform.
# You can copy this option file to one of those
# locations. For information about these locations, do:
# 'my_print_defaults --help' and see what is printed under
# Default options are read from the following files in the given order:
# More information at: http://dev.mysql.com/doc/mysql/en/option-files.html
#
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.

# The following options will be passed to all MariaDB clients
[client]
#password	= your_password
port		= 3306
socket		= /run/mysqld/mysqld.sock

# Here follows entries for some specific programs

# The MariaDB server
[mysqld]
port		= 3306
socket		= /run/mysqld/mysqld.sock
skip-external-locking
key_buffer_size = 16M
max_allowed_packet = 1M
table_open_cache = 64
sort_buffer_size = 512K
net_buffer_length = 8K
read_buffer_size = 256K
read_rnd_buffer_size = 512K
myisam_sort_buffer_size = 8M

# Point the following paths to different dedicated disks
#tmpdir		= /tmp/

# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
# 
skip-networking

# Replication Master Server (default)
# binary logging is required for replication
log-bin=mysql-bin

# binary logging format - mixed recommended
binlog_format=mixed

# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id	= 1

# Replication Slave (comment out master section to use this)
#
# To configure this host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
#    the syntax is:
#
#    CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
#    MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
#
#    where you replace <host>, <user>, <password> by quoted strings and
#    <port> by the master's port number (3306 by default).
#
#    Example:
#
#    CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
#    MASTER_USER='joe', MASTER_PASSWORD='secret';
#
# OR
#
# 2) Set the variables below. However, in case you choose this method, then
#    start replication for the first time (even unsuccessfully, for example
#    if you mistyped the password in master-password and the slave fails to
#    connect), the slave will create a master.info file, and any later
#    change in this file to the variables' values below will be ignored and
#    overridden by the content of the master.info file, unless you shutdown
#    the slave server, delete master.info and restart the slaver server.
#    For that reason, you may want to leave the lines below untouched
#    (commented) and instead use CHANGE MASTER TO (see above)
#
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id       = 2
#
# The replication master for this slave - required
#master-host     =   <hostname>
#
# The username the slave will use for authentication when connecting
# to the master - required
#master-user     =   <username>
#
# The password the slave will authenticate with when connecting to
# the master - required
#master-password =   <password>
#
# The port the master is listening on.
# optional - defaults to 3306
#master-port     =  <port>
#
# binary logging - not required for slaves, but recommended
#log-bin=mysql-bin

# Uncomment the following if you are using InnoDB tables
#innodb_data_home_dir = /var/lib/mysql
#innodb_data_file_path = ibdata1:10M:autoextend
#innodb_log_group_home_dir = /var/lib/mysql
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
#innodb_buffer_pool_size = 16M
#innodb_additional_mem_pool_size = 2M
# Set .._log_file_size to 25 % of buffer pool size
#innodb_log_file_size = 5M
#innodb_log_buffer_size = 8M
#innodb_flush_log_at_trx_commit = 1
#innodb_lock_wait_timeout = 50

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[myisamchk]
key_buffer_size = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout

Any ideas?

Last edited by glennph93 (2017-09-03 19:27:39)

hoerbert

Member

Registered: 2013-04-03

Posts: 87

Re: [Solved]Mariadb Not listening on port 3306? Mythtv cannot connect

Your mariadb is only accessible via local socket and not via network at all. "skip-networking" in the my.cnf is the key.

glennph93

Member

Registered: 2013-07-21

Posts: 6

Re: [Solved]Mariadb Not listening on port 3306? Mythtv cannot connect

Thanks I just realized that, commented that out and now its listening..Must have changed config file on update.

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,424

Website

Re: [Solved]Mariadb Not listening on port 3306? Mythtv cannot connect

Must have changed config file on update.

Pacman would have warned you about this, if it was the case.

Please remember to mark your thread as [Solved] by editing your first post and prepending it to the title.

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

glennph93

Member

Registered: 2013-07-21

Posts: 6

Re: [Solved]Mariadb Not listening on port 3306? Mythtv cannot connect

Pacman would have warned you about this, if it was the case.

Yeah I look for that and didn't see anything about it:

[2017-09-03 12:46] [ALPM] upgraded lua52-bitop (1.0.2-7 -> 1.0.2-8)
[2017-09-03 12:46] [ALPM] upgraded mariadb-clients (10.1.25-1 -> 10.1.26-1)
[2017-09-03 12:46] [ALPM] upgraded mariadb (10.1.25-1 -> 10.1.26-1)
[2017-09-03 12:46] [ALPM] upgraded mpg123 (1.25.4-1 -> 1.25.6-1)
[2017-09-03 12:46] [ALPM] upgraded perl-dbd-mysql (4.043-1 -> 4.043-3)
[2017-09-03 12:46] [ALPM] upgraded perl-socket6 (0.28-2 -> 0.28-4)

Was listening before the update

Thanks

hoerbert

Member

Registered: 2013-04-03

Posts: 87

Re: [Solved]Mariadb Not listening on port 3306? Mythtv cannot connect

I don't know if you want to investigate this further (since you marked your thread as *solved*), but in the my.cnf included in the mariadb-arch-package, the skip-networking line is in fact commented out. So I would assume that you yourself or something else you did has activated that line after the update.