[SOLVED] Duplicate log entry for /var/lib/mysql/mysqld.log

teoberi · 01-15-2024, 01:05 AM

Quote:

cron for user root /usr/bin/run-parts /etc/cron.daily 1> /dev/null
Contact photo
From root@xxx.ro on 2024-01-15 04:40
Details Headers
error: mysql:21 duplicate log entry for /var/lib/mysql/mysqld.log
error: found error in file mysql, skipping

In /etc/logrotate.d/ I have:
mariadb
mysql
A simple Google search:
https://www.ucartz.com/clients/knowl...ysqld.log.html
https://www.suse.com/support/kb/doc/?id=000016984
We proceed in the same way, what can we delete?

Thom1b · 01-15-2024, 01:18 AM

Hi,
I guess /etc/logrotate.d/mysql was in mariadb and had been replaced by /etc/logrotate.d/mariadb. You can simply delete /etc/logrotate.d/mysql.

Same issue here since dcron sends error mail

teoberi · 01-15-2024, 01:28 AM

Quote:

Originally Posted by Thom1b

Hi,
I guess /etc/logrotate.d/mysql was in mariadb and had been replaced by /etc/logrotate.d/mariadb. You can simply delete /etc/logrotate.d/mysql.

Same issue here since dcron sends error mail

I suspected this, but it would be good if it was officially resolved.

teoberi · 01-17-2024, 01:50 AM

Final solution!
When starting MariaDB we get:

Quote:

mysqld_safe Logging to '/var/lib/mysql/xxx.err'.

In /etc/logrotate.d in the mysql file it appears:

Quote:

/var/lib/mysql/mysqld.log

In /etc/logrotate.d/ in the mariadb file it appears:

Quote:

/var/lib/mysql/mysqld.log /var/lib/mysql/mariadb.log /var/log/mysql/*.log

In mariadb.SlackBuild appears:

Quote:

mv $PKG/etc/logrotate.d/mariadb $PKG/etc/logrotate.d/mariadb.new

Files /usr/share/mysql/mariadb.logrotate is identical to /etc/logrotate.d/mariadb
In conclusion, I think that the /etc/logrotate.d/mysql file can be deleted.

An even better solution is to uninstall MariaDB and replace it with PostgreSQL.

(proceed carefully because now Apache depends on MariaDB)

Petri Kaukasoina · 01-17-2024, 03:59 AM

Quote:

Originally Posted by teoberi

the /etc/logrotate.d/mysql file can be deleted.

An older mariadb package contains file '/etc/logrotate.d/mysql.new'. Files with suffix .new are moved to place without .new. upgradepkg uses removepkg to remove the old package, but removepkg can't remove /etc/logrotate.d/mysql because it tries to remove the original /etc/logrotate.d/mysql.new and it does not exist. That's why obsolete config files are always left behind when either the package is removed or upgraded to a new version without that file.

Petri Kaukasoina · 01-17-2024, 05:20 AM

Quote:

Originally Posted by Petri Kaukasoina

obsolete config files are always left behind when either the package is removed or upgraded to a new version without that file.

What are these obsolete config files:

Code:

#!/bin/sh
# obsolete_new: find obsolete .new files
# pk 2024-01-17
cd /var/log/removed_packages
grep -h '\.new$' *|sort -u|\
while read fnew; do
  cd /var/log/packages
  f=${fnew%.new}
  if ! grep -qE "^$fnew$|^$f$" *; then    
    [ -f "/$f" -a ! -L "/$f" ] && echo "/$f"
  fi
done

teoberi · 01-17-2024, 07:45 AM

Examples found:
/etc/gamin/gaminrc -> package removed form Slackware on Sun Nov 20 00:54:24 UTC 2022 (l/gamin-0.1.10-x86_64-9.txz: Removed.)
/etc/login.access replaced with /etc/security/access.conf
/etc/rc.d/rc.openvpn -> package removed (by me)
/var/log/spooler -> I still don't know what's with him
https://support.hpe.com/hpesc/public...ocLocale=en_US

Quote:

/var/log/cups /var/log/spooler - All printer and printing related log messages.

https://stackify.com/linux-logs/
/var/log/spooler
Rarely used and often empty. When used, it contains messages from USENET

Something I still don't understand:
/etc/iproute2/bpf_pinning
/etc/iproute2/ematch_map
/etc/iproute2/group
/etc/iproute2/nl_protos
/etc/iproute2/rt_dsfield
/etc/iproute2/rt_protos
/etc/iproute2/rt_realms
/etc/iproute2/rt_scopes
/etc/iproute2/rt_tables
files with the extension .new exist in the package iproute2-6.7.0-x86_64-1.txz
https://packages.slackware.com/?r=sl...x86_64-1.txz&f

Petri Kaukasoina · 01-17-2024, 08:05 AM

Quote:

Originally Posted by teoberi

/var/log/spooler -> I still don't know what's with him

sysklogd-1.5.1-x86_64-3-upgraded-2020-06-26,23:12:41:var/log/spooler.new
But it's not in the latest sysklogd package.

Quote:

Originally Posted by teoberi

/etc/iproute2/bpf_pinning
/etc/iproute2/ematch_map
/etc/iproute2/group
/etc/iproute2/nl_protos
/etc/iproute2/rt_dsfield
/etc/iproute2/rt_protos
/etc/iproute2/rt_realms
/etc/iproute2/rt_scopes
/etc/iproute2/rt_tables
files with the extension .new exist in the package iproute2-6.7.0-x86_64-1.txz

The files with same names are in /usr/lib/iproute2 now. The directory /etc/iproute2 should be empty.

BroX · 01-20-2024, 07:51 AM

Quote:

Originally Posted by Petri Kaukasoina

What are these obsolete config files:

Code:

#!/bin/sh
# obsolete_new: find obsolete .new files
# pk 2024-01-17
cd /var/log/removed_packages
grep -h '\.new$' *|sort -u|\
while read fnew; do
  cd /var/log/packages
  f=${fnew%.new}
  if ! grep -qE "^$fnew$|^$f$" *; then    
    [ -f "/$f" -a ! -L "/$f" ] && echo "/$f"
  fi
done

Code:

line 5: /usr/bin/grep: Argument list too long

What could be wrong with my grep?

Petri Kaukasoina · 01-20-2024, 08:24 AM

Quote:

Originally Posted by BroX

Code:

line 5: /usr/bin/grep: Argument list too long

What could be wrong with my grep?

Nothing wrong in it. You have so many files in /var/log/removed_packages that '*' expands to too long a command line.

Petri Kaukasoina · 01-20-2024, 08:43 AM

Try this instead:

Code:

#!/bin/sh
# obsolete_new: find obsolete .new files
# pk 2024-01-17 2024-01-20
cd /var/log/removed_packages
find . -type f -exec grep -h '\.new$' '{}' +|sort -u|\
while read fnew; do
  cd /var/log/packages
  f=${fnew%.new}
  if ! grep -qE "^$fnew$|^$f$" *; then    
    [ -f "/$f" -a ! -L "/$f" ] && echo "/$f"
  fi
done

BroX · 01-20-2024, 09:42 AM

Quote:

Originally Posted by Petri Kaukasoina

Try this instead:

Code:

#!/bin/sh
# obsolete_new: find obsolete .new files
# pk 2024-01-17 2024-01-20
cd /var/log/removed_packages
find . -type f -exec grep -h '\.new$' '{}' +|sort -u|\
while read fnew; do
  cd /var/log/packages
  f=${fnew%.new}
  if ! grep -qE "^$fnew$|^$f$" *; then    
    [ -f "/$f" -a ! -L "/$f" ] && echo "/$f"
  fi
done

Petri Kaukasoina · 01-20-2024, 09:50 AM

I don't know if it's possible to install so many packages that even /var/log/packages would have too many file names for the second grep in the script. This version changes also that one to use find:

Code:

#!/bin/sh
# obsolete_new: find obsolete .new files
# pk 2024-01-17 2024-01-20
cd /var/log/removed_packages
find . -type f -exec grep -h '\.new$' '{}' +|sort -u|\
while read fnew; do
  cd /var/log/packages
  f=${fnew%.new}
  if ! find . -type f -exec grep -qE "^$fnew$|^$f$" '{}' +; then
    [ -f "/$f" -a ! -L "/$f" ] && echo "/$f"
  fi
done

drumz · 01-22-2024, 07:49 AM

Quote:

Originally Posted by Petri Kaukasoina

I don't know if it's possible to install so many packages that even /var/log/packages would have too many file names for the second grep in the script. This version changes also that one to use find:

Code:

#!/bin/sh
# obsolete_new: find obsolete .new files
# pk 2024-01-17 2024-01-20
cd /var/log/removed_packages
find . -type f -exec grep -h '\.new$' '{}' +|sort -u|\
while read fnew; do
  cd /var/log/packages
  f=${fnew%.new}
  if ! find . -type f -exec grep -qE "^$fnew$|^$f$" '{}' +; then
    [ -f "/$f" -a ! -L "/$f" ] && echo "/$f"
  fi
done

I get one false positive (guessing due to the plus sign in the file name?):

Code:

# obsolete_new 
/etc/grub.d/20_memtest86+
# grep 20_memtest86 /var/lib/pkgtools/packages/*
/var/lib/pkgtools/packages/memtest86+-6.20-x86_64-1_SBo:etc/grub.d/20_memtest86+.new

Petri Kaukasoina · 01-22-2024, 09:24 AM

Yes, it seems to be due to the '-E' option of the second grep. I used extended regular expressions to be able to match either 'file.new' or 'file' lines in the packages directory. But '+' has a special meaning in regexps. (So do '*' and '?' but fortunately they are seldom used in file names.)

I think it should work if we change

Code:

grep -qE "^$fnew$|^$f$"

to

Code:

grep -q -e "^$fnew$" -e "^$f$"

Would you try this below?

Code:

#!/bin/sh
# obsolete_new: find obsolete .new files
# pk 2024-01-17 2024-01-20 2024-01-22
cd /var/log/removed_packages
find . -type f -exec grep -h '\.new$' '{}' +|sort -u|\
while read fnew; do
  cd /var/log/packages
  f=${fnew%.new}
  if ! find . -type f -exec grep -q -e "^$fnew$" -e "^$f$" '{}' +; then
    [ -f "/$f" -a ! -L "/$f" ] && echo "/$f"
  fi
done