Lamp Mariadb install error

[kitkat]

The guide contains another error that's probably preventing the database from starting...

innodb_log_file_size - 32M should be innodb_log_file_size = 32M (equals instead of minus)

[DVB Hardware]

The guide contains another error that's probably preventing the database from starting...

innodb_log_file_size - 32M should be innodb_log_file_size = 32M (equals instead of minus)

You have hawk eyes, good find !!! I will try it now
ALSO an extra space
innodb_buffer_pool_ size = 256M
innodb_buffer_pool_ size = 256M

Mariadb is running but instituted a new error connecting to zm Apache is running fine
Not Found The requested URL was not found on this server. http://192.168.1.201/zm/
Trying to find a log, is it apache or zm to give me a hint


Miscellaneous:
1 camera 640x480 to play with
Like I said previously it only a P5Q motherboard with a Q6600 processor been running Master for ever with 4g ram but just added 4 more gig. Due to playback java error stated by iconner, it was beyond my skills to track it down so I just wiped the server and start fresh...its been a while.

Asker said the install bash script was updated about 2 months ago, so I had used an older one I guess

[kitkat]

The guide contains another error that's probably preventing the database from starting...

innodb_log_file_size - 32M should be innodb_log_file_size = 32M (equals instead of minus)

You have hawk eyes, good find !!! I will try it now
ALSO an extra space
innodb_buffer_pool_ size = 256M
innodb_buffer_pool_ size = 256M

Mariadb is running but instituted a new error connecting to zm Apache is running fine
Not Found The requested URL was not found on this server. http://192.168.1.201/zm/
Trying to find a log, is it apache or zm to give me a hint


Miscellaneous:
1 camera 640x480 to play with
Like I said previously it only a P5Q motherboard with a Q6600 processor been running Master for ever with 4g ram but just added 4 more gig. Due to playback java error stated by iconner, it was beyond my skills to track it down so I just wiped the server and start fresh...its been a while.

Asker said the install bash script was updated about 2 months ago, so I had used an older one I guess

404 Not Found is an Apache message. It sounds like the ZM configuration file (which defines the /zm* aliases) isn't being loaded. It's typically, well on CentOS anyway, a symlink pointing from /etc/httpd/conf.d/zoneminder.conf to /etc/zm/www/zoneminder.conf

I caught the extra space as well: viewtopic.php?f=44&t=31329#p124470

Any problems when you changed the size of the InnoDB logfile?

[iconnor]

I've updated the wiki

[DVB Hardware]

Any problems when you changed the size of the InnoDB logfile?

I tried 1/2 the values no go
innodb_buffer_pool_size and innodb_log_file_size have default values if not set acorfing to mariadb so I entered those values and it still tanked. wish I wrote them down.
If I comment out the innodb all boots and runs fine in zm from what I see

Its bugging me, I don't want it to reflect on zm if someone new has the same problem
------------------------------------------------------------------------------
I just logged in to my HP dv6 upstairs
innnodb's enabled error on zm install
Job for zoneminder.service failed because the control process exited with error code.
See "systemctl status zoneminder.service" and "journalctl -xe" for details.

innob's comented out
zm installed and running

------------------------------------------------------------------------------
Yes innodb' below "[mysqld]"

[Magic919]

Check the DB logs and get to the bottom of the problem.

[kitkat]

Any problems when you changed the size of the InnoDB logfile?

I tried 1/2 the values no go
innodb_buffer_pool_size and innodb_log_file_size have default values if not set acorfing to mariadb so I entered those values and it still tanked. wish I wrote them down.
If I comment out the innodb all boots and runs fine in zm from what I see

Its bugging me, I don't want it to reflect on zm if someone new has the same problem
------------------------------------------------------------------------------
I just logged in to my HP dv6 upstairs
innnodb's enabled error on zm install
Job for zoneminder.service failed because the control process exited with error code.
See "systemctl status zoneminder.service" and "journalctl -xe" for details.

innob's comented out
zm installed and running

------------------------------------------------------------------------------
Yes innodb' below "[mysqld]"

I think that the failure to start is very probably related to changing the size of the InnoDB log files (barring any other typos and errors in the guide of course!), but this is coming from my CentOS-centric perspective and it may be that mariadb/MySQL doesn't behave this way on other distros.

The mariadb log (/var/log/mariadb/mariadb.log on CentOS) should show what's going on - This will display the last ten errors in that file:

Code: Select all

grep -i error /var/log/mariadb/mariadb.log | tail

If the output contains something like this then the log files are very likely to be the problem:

Code: Select all

InnoDB: Error: log file ./ib_logfile0 is of different size 0 78643200 bytes

(The lack of such output doesn't rule out the log files being a problem because there may be later errors hiding them and you should inspect the logs in more detail.)

If you do see those errors then you can try this to see if they self-repaired:

Code: Select all

grep -i "InnoDB: Log" /var/log/mariadb/mariadb.log | tail

A good result would look something like this:

Code: Select all

190319 16:17:05  InnoDB: Log file ./ib_logfile0 did not exist: new to be created

(The leading digits are a YYMMDD datestamp so you can tell whether they're recent or not.)

So, if you see errors but not 'to be created' messages then the log files may well be the problem, and you should be able to fix it like this:

Code: Select all

# Stop the database server
sudo systemctl stop mariadb

# Move the old log files out of the way.
# We could delete but let's keep them so we 
# can put them back if it still fails
sudo mv -f /var/lib/mysql/ib_logfile? /tmp/

# Edit my.cnf and add the innodb_* entries
# to the [mysqld] section
sudo nano /etc/my.cnf

# Restart the database
sudo systemctl start mariadb

# Wait a few seconds and then look for messages in the log
grep -i "InnoDB: Log" /var/log/mariadb/mariadb.log | tail

Hopefully you'll see a "InnoDB: Log file ./ib_logfileX did not exist: new to be created" message or two, but if it still doesn't start then you'll have to inspect the logs for other problems.

A very minor thought is the spaces around the ' = ' in my.cnf. I'm sure they're probably fine but I've never seen them used and I always avoid whitespace where possible. My my.cnf contains these innodb_* directives under [mysqld]

Code: Select all

innodb_stats_on_metadata=off
innodb_file_per_table=on
innodb_log_file_size=128M
innodb_buffer_pool_size=1024M

(If you use other values, log_file_size should generally be one-eighth of buffer_pool_size.)

Good luck!

[DVB Hardware]

In the order of your code execute

grep -i error /var/log/mariadb/mariadb.log | tail

root@POS-SERVER:/home/jimmy# grep -i error /var/log/mariadb/mariadb.log | tail
grep: /var/log/mariadb/mariadb.log: No such file or directory

--------------------------------------------------------------------------------------
InnoDB: Error: log file ./ib_logfile0 is of different size 0 78643200 bytes

root@POS-SERVER:/home/jimmy# grep -i error /var/log/mariadb/mariadb.log | tail
grep: /var/log/mariadb/mariadb.log: No such file or directory
root@POS-SERVER:/home/jimmy# InnoDB: Error: log file ./ib_logfile0 is of different size 0 78643200 bytes
InnoDB:: command not found

---------------------------------------------------------------------------------------
grep -i "InnoDB: Log" /var/log/mariadb/mariadb.log | tail

root@POS-SERVER:/home/jimmy# grep -i "InnoDB: Log" /var/log/mariadb/mariadb.log | tail
grep: /var/log/mariadb/mariadb.log: No such file or directory

----------------------------------------------------------------------------------------------
190319 16:17:05 InnoDB: Log file ./ib_logfile0 did not exist: new to be created

root@POS-SERVER:/home/jimmy# 190319 16:17:05 InnoDB: Log file ./ib_logfile0 did not exist: new to be created 190319: command not found

*** A ib_logfile0 file created in /tmp but it is 100.7mb

Add innodb and restart

root@POS-SERVER:/home/jimmy# sudo systemctl start mariadb
Job for mariadb.service failed because the control process exited with error code.
See "systemctl status mariadb.service" and "journalctl -xe" for details.

----------------------------------------------------------------------------------------------
root@POS-SERVER:/home/jimmy# status mariadb,service

● mariadb.service - MariaDB 10.6.5 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/mariadb.service.d
└─migrated-from-my.cnf-settings.conf
Active: failed (Result: exit-code) since Tue 2021-11-30 10:37:38 EST; 2min 1s ago
Docs: man:mariadbd(8)
https://mariadb.com/kb/en/library/systemd/
Process: 5072 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exite>
Process: 5084 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exit>
Process: 5093 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`cd /usr/>
Process: 5102 ExecStart=/usr/sbin/mariadbd $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION>
Main PID: 5102 (code=exited, status=1/FAILURE)

Nov 30 10:37:38 POS-SERVER systemd[1]: Starting MariaDB 10.6.5 database server...
Nov 30 10:37:38 POS-SERVER sh[5099]: error: Found option without preceding group in config file: /etc/>
Nov 30 10:37:38 POS-SERVER sh[5099]: Fatal error in defaults handling. Program aborted
Nov 30 10:37:38 POS-SERVER mariadbd[5102]: error: Found option without preceding group in config file:>
Nov 30 10:37:38 POS-SERVER mariadbd[5102]: Fatal error in defaults handling. Program aborted
Nov 30 10:37:38 POS-SERVER systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAI>
Nov 30 10:37:38 POS-SERVER systemd[1]: mariadb.service: Failed with result 'exit-code'.
Nov 30 10:37:38 POS-SERVER systemd[1]: Failed to start MariaDB 10.6.5 database server.
~
~
lines 1-21/21 (END)

--------------------------------------------------------------------------------------------------------------
root@POS-SERVER:/home/jimmy# journalctl -xe

Nov 30 10:43:06 POS-SERVER zmfilter[5426]: ERR [Error reconnecting to db: errst>
Nov 30 10:43:06 POS-SERVER zmfilter[5426]: ERR [Error reconnecting to db: errst>
Nov 30 10:43:06 POS-SERVER zmfilter[5425]: ERR [Error reconnecting to db: errst>
Nov 30 10:43:06 POS-SERVER zmfilter[5425]: ERR [Error reconnecting to db: errst>
Nov 30 10:43:06 POS-SERVER zmdc[1072]: ERR ['zmfilter.pl --filter_id=1 --daemon>
Nov 30 10:43:06 POS-SERVER zmdc[1072]: ERR ['zmfilter.pl --filter_id=2 --daemon>
Nov 30 10:43:07 POS-SERVER zmwatch[1138]: ERR [Error reconnecting to db: errstr>
Nov 30 10:43:09 POS-SERVER zmc_m1[1122]: ERR [zmc_m1] [Can't run query INSERT I>
( 0, 100, 'Bulk', from_unixtime( 16382>
Nov 30 10:43:09 POS-SERVER zmc_m1[1122]: ERR [zmc_m1] [Can't run query INSERT I>
(0,100,1,1,0,0,0,0,0,0,0,0,0,0,0,0): C>
Nov 30 10:43:09 POS-SERVER zmc_m1[1122]: ERR [zmc_m1] [Can't run query UPDATE E>
Nov 30 10:43:13 POS-SERVER sudo[5446]: jimmy : TTY=pts/0 ; PWD=/home/jimmy ;>
Nov 30 10:43:13 POS-SERVER sudo[5446]: pam_unix(sudo:session): session opened f>
Nov 30 10:43:13 POS-SERVER su[5447]: (to root) jimmy on pts/0
Nov 30 10:43:13 POS-SERVER su[5447]: pam_unix(su:session): session opened for u>
Nov 30 10:43:17 POS-SERVER zmwatch[1138]: ERR [Error reconnecting to db: errstr>
Nov 30 10:43:18 POS-SERVER zmstats[1174]: ERR [Error reconnecting to db: errstr>
Nov 30 10:43:23 POS-SERVER zmc_m1[1122]: ERR [zmc_m1] [Can't run query INSERT I>
( 0, 200, 'Bulk', from_unixtime( 16382>
Nov 30 10:43:23 POS-SERVER zmc_m1[1122]: ERR [zmc_m1] [Can't run query INSERT I>
(0,200,1,1,0,0,0,0,0,0,0,0,0,0,0,0): C>
Nov 30 10:43:23 POS-SERVER zmc_m1[1122]: ERR [zmc_m1] [Can't run query UPDATE E>
lines 1253-1275/1275 (END)

[kitkat]

OK...

grep is saying "/var/log/mariadb/mariadb.log: No such file or directory" so your log file isn't at /var/log/mariadb/mariadb.log.

Hmm.. Or perhaps it is there but you need sudo to access it? (I always forget that bit because I'm usually root. Yeah, I know...) To avoid that sort of problem you could probably sudo su and get root privileges for the whole session.

Basically, try the grep stuff again but prefixed with sudo (and a space!) or make sure you have root privileges some other way and see what it says. If it still says it can't find the file then you'll have to locate it and substitute the correct path in the commands.

Some of the things I posted and which you tried were examples of output rather than actual commands

This looks to be a problem though:

Code: Select all

Nov 30 10:37:38 POS-SERVER sh[5099]: error: Found option without preceding group in config file: /etc/>
Nov 30 10:37:38 POS-SERVER sh[5099]: Fatal error in defaults handling. Program aborted
Nov 30 10:37:38 POS-SERVER mariadbd[5102]: error: Found option without preceding group in config file:>
Nov 30 10:37:38 POS-SERVER mariadbd[5102]: Fatal error in defaults handling. Program aborted

There may of course be other flog_file_size related errors to come but it's not even getting that far. Maybe paste your entire my.cnf here so we can see what it looks like, with the edits and without.

[DVB Hardware]

I was logged in as root

I also did a filesystem search for mariadb.log, nothing

[DVB Hardware]

Maybe paste your entire my.cnf here so we can see what it looks like, with the edits and without.

There is no my.cnf, well there is but empty, Mariadb uses 50-server.cnf

Inno is commented out with #, this is a clean install
-----------------------------------------------------------------------------------------------------------------
GNU nano 4.8 /etc/mysql/mariadb.conf.d/50-server.cnf
#
# These groups are read by MariaDB server.
# Use it for options that only the server (but not clients) should see

# this is read by the standalone daemon and embedded servers
[server]

# this is only for the mysqld standalone daemon
[mysqld]

#
# * Basic Settings
#

user = mysql
pid-file = /run/mysqld/mysqld.pid
basedir = /usr
datadir = /var/lib/mysql
tmpdir = /tmp
lc-messages-dir = /usr/share/mysql
lc-messages = en_US
skip-external-locking

# Broken reverse DNS slows down connections considerably and name resolve is
# safe to skip if there are no "host by domain name" access grants
#skip-name-resolve

# 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
performance_schema = on

#innodb_file_per_table = ON
#innodb_buffer_pool_ size = 32M
#innodb_log_file_size - 4M

#
# * Fine Tuning
#

#key_buffer_size = 128M
#max_allowed_packet = 1G
#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_options = BACKUP
#max_connections = 100
#table_cache = 64

#
# * Logging and Replication
#

# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
# Recommend only changing this at runtime for short testing periods if needed!
#general_log_file = /var/log/mysql/mysql.log
#general_log = 1

# When running under systemd, error logging goes via stdout/stderr to journald
# and when running legacy init error logging goes to syslog due to
# /etc/mysql/conf.d/mariadb.conf.d/50-mysqld_safe.cnf
# Enable this if you want to have error logging into a separate file
#log_error = /var/log/mysql/error.log
# Enable the slow query log to see queries with especially long duration
#slow_query_log_file = /var/log/mysql/mariadb-slow.log
#long_query_time = 10
#log_slow_verbosity = query_plan,explain
#log-queries-not-using-indexes
#min_examined_row_limit = 1000

# 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

#
# * SSL/TLS
#

# For documentation, please read
# https://mariadb.com/kb/en/securing-conn ... nd-server/
#ssl-ca = /etc/mysql/cacert.pem
#ssl-cert = /etc/mysql/server-cert.pem
#ssl-key = /etc/mysql/server-key.pem
#require-secure-transport = on

#
# * Character sets
#

# MySQL/MariaDB default is Latin1, but in Debian we rather default to the full
# utf8 4-byte character set. See also client.cnf
character-set-server = utf8mb4
collation-server = utf8mb4_general_ci

#
# * 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!
# Most important is to give InnoDB 80 % of the system RAM for buffer use:
# https://mariadb.com/kb/en/innodb-system ... _pool_size
#innodb_buffer_pool_size = 8G

# this is only for embedded server
[embedded]

# This group is only read by MariaDB servers, not by MySQL.
# If you use the same .cnf file for MySQL and MariaDB,
# you can put MariaDB-only options here
[mariadb]

# This group is only read by MariaDB-10.6 servers.
# If you use the same .cnf file for MariaDB of different versions,
# use this group for options that older servers don't understand
[mariadb-10.6]

[Magic919]

This bit of the config explains where the logs are -

# When running under systemd, error logging goes via stdout/stderr to journald
# and when running legacy init error logging goes to syslog due to
# /etc/mysql/conf.d/mariadb.conf.d/50-mysqld_safe.cnf
# Enable this if you want to have error logging into a separate file
#log_error = /var/log/mysql/error.log

[DVB Hardware]

I tried to set "log_error = /home/ljimmy/desktop/error.log" so I don't have to dig for it ( no good) won't write to it.
enabled it at log_error = /var/log/mysql/error.log

2021-12-01 15:54:21 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-12-01 15:54:21 0 [Note] InnoDB: Number of pools: 1
2021-12-01 15:54:21 0 [Note] InnoDB: Using generic crc32 instructions
2021-12-01 15:54:21 0 [Note] InnoDB: Using Linux native AIO
2021-12-01 15:54:21 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
2021-12-01 15:54:21 0 [Note] InnoDB: Completed initialization of buffer pool
2021-12-01 15:54:28 0 [Note] InnoDB: 128 rollback segments are active.
2021-12-01 15:54:28 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2021-12-01 15:54:28 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2021-12-01 15:54:28 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2021-12-01 15:54:28 0 [Note] InnoDB: 10.6.5 started; log sequence number 25138040; transaction id 64310
2021-12-01 15:54:28 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2021-12-01 15:54:28 0 [Note] Plugin 'FEEDBACK' is disabled.
2021-12-01 15:54:29 0 [ERROR] /usr/sbin/mariadbd: unknown variable 'innodb_buffer_pool_ size=32M'
2021-12-01 15:54:29 0 [ERROR] Aborting

[DVB Hardware]

Well I think I had enough beating a dead horse on this.
I spent days researching Innodb beyond my skills to reason why the settings are there

I have a xampp install for Point of sale testing, same mariadb version on win 10

I used the Innodb settings from xampp in linux and it worked
I also increased the file_per_table and the Log_file_size in linux to 256M and 32M respectively and that worked also, with the additional variables

Crazy as this test was, It didn't matter to me since I would reformat the pc and start over, install expendable.

Im just going to leave innodb settings out and let mariadb use its default variables.

Thanks guys, hope I didn't waste to much of your time

Jimmy

Screenshot_4.jpg (220.01 KiB) Viewed 14096 times

[Magic919]

Your logs show it is using the default of 128MB

Code: Select all

2021-12-01 15:54:21 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728

I'm not sure why you'd want to change it.