This is the reaction of the kmod service to an attempt by some other service (program) to stop it.
Kmod is a service for loading kernel modules, and stopping it on a running machine is pointless.
Perhaps there is confusion with the pid of the processes, perhaps something else.
Forget this matter...

Regards.

Something found here
etc/init.d/rc.local
restart|reload|force-reload)
        echo "Error: argument '$1' not supported" >&2
        exit 3

#! /bin/sh
### BEGIN INIT INFO
# Provides:          rc.local
# Required-Start:    $all
# Required-Stop:
# Default-Start:     2 3 4 5
# Default-Stop:
# Short-Description: Run /etc/rc.local if it exist
### END INIT INFO

PATH=/usr/sbin:/usr/bin:/sbin:/bin

. /lib/init/vars.sh
. /lib/lsb/init-functions

do_start() {
        if [ -x /etc/rc.local ]; then
                [ "$VERBOSE" != no ] && log_begin_msg "Running local boot scripts (/etc/rc.local)"
                /etc/rc.local
                ES=$?
                [ "$VERBOSE" != no ] && log_end_msg $ES
                return $ES
        fi
}

do_stop() {
        if [ -x /etc/rc.shutdown ]; then
                [ "$VERBOSE" != no ] && log_begin_msg "Running local shutdown scripts (/etc/rc.shutdown)"
                /etc/rc.shutdown
                ES=$?
                [ "$VERBOSE" != no ] && log_end_msg $ES
                return $ES
        fi
}

case "$1" in
    start)
        do_start
        ;;
    restart|reload|force-reload)
        echo "Error: argument '$1' not supported" >&2
        exit 3
        ;;
    status)
        # No-op
        exit 0
        ;;
    stop)
        do_stop
        exit 0
        ;;
    *)
        echo "Usage: $0 start|stop" >&2
        exit 3
        ;;
esac

Apart from that I've run out of ideas for what could be calling kmod. So I'd suggest ignoring the message, the script doesn't do anything when called with the stop parameter.

Exactly when does that message come out? Is it when you boot the system, log on, log off or shut it down?

less /etc/init.d/kmod should tell you what kmod is (unless all the comments are missing).

Try this:

ls -l /etc/rc?.d/*kmod*
lrwxrwxrwx 1 root root 14 May  9  2018 /etc/rcS.d/S09kmod -> ../init.d/kmod

You should get only 1 line, a symlink that tells the OS to run kmod start when bringing the system up. I suspect you have a stop link somewhere (it will be probably named something like K09kmod).

For belt and braces try ls -l /etc/rc?.d/ | grep kmod which searches the destination of the symlink. If still stuck grep meaningless /etc/rc?.d/* in case there is a stray copy of kmod somewhere.

Thanks, yes source of warning is string at /etc/init.d/kmod
Action '$1' is meaningless for this init script

freeartist-devuan@home:~$ ls -l /etc/rc?.d/ | grep kmod
lrwxrwxrwx 1 root root 14 Aug 18 23:11 S09kmod -> ../init.d/kmod
freeartist-devuan@home:~$ grep meaningless /etc/rc?.d/*
/etc/rcS.d/S09kmod:  log_warning_msg "Action '$1' is meaningless for this init script"
freeartist-devuan@home:~$ 

Ok. So i must ignore it? And i see this warning only when use lightdm, using slim i do not see it.

grep -i "(EE)\|(??)|fail \|segfault" /home/glenn/.xsession-errors
grep -i "(WW)\|(EE)\|(??)" /var/log/Xorg.0.log
tail /var/log/syslog 

Which should get you the same results, but slightly faster.

cat /home/glenn/.xsession-errors | grep -i "(EE)\|(??)|fail \|segfault"
cat /var/log/Xorg.0.log | grep -i "(WW)\|(EE)\|(??)"
cat /var/log/syslog | tail

you may use the same lookups with dmesg,  and swap the filtering around to search for a match of what your looking for.

I also have sys-type logs sent to tty11 & tty12 so I can easily switch to those consoles and see if anything has changed.

I hope this gives you some tips to work with.

all the best, GlennW (aka, GlennsPref)

It turns out somehow undignified and uninteresting.
If you delve into initialization systems, then at least you need to have a complete understanding of how it works, what kind of scripts and links they are.
Maybe start with this? But, of course, you know better...

less /etc/init.d/kmod should tell you what kmod is (unless all the comments are missing).

Try this:

ls -l /etc/rc?.d/*kmod*
lrwxrwxrwx 1 root root 14 May  9  2018 /etc/rcS.d/S09kmod -> ../init.d/kmod

You should get only 1 line, a symlink that tells the OS to run kmod start when bringing the system up. I suspect you have a stop link somewhere (it will be probably named something like K09kmod).

For belt and braces try ls -l /etc/rc?.d/ | grep kmod which searches the destination of the symlink. If still stuck grep meaningless /etc/rc?.d/* in case there is a stray copy of kmod somewhere.

freeartist-devuan@home:/etc/init.d$ grep meaningless *
kmod:  log_warning_msg "Action '$1' is meaningless for this init script"
freeartist-devuan@home:/etc/init.d$ ./kmod
Usage: ./kmod start.

freeartist-devuan@home:/etc/init.d$ ./kmod start
Loading kernel module lp.
Loading kernel module ppdev.
Loading kernel module parport_pc.
Loading kernel module cuse.
freeartist-devuan@home:/etc/init.d$ 

What is kmod?
And why i see this warning only at lightdm but no at slim?
Action 'stop' is meaningless for this init script ... (warning)

So looking in /etc/init.d/kmod might help. But do check as above to see if any other script could be generating it.

is there command for parsing all system logs to find this warning?

The log is a regular text file; any editor will find what you are looking for. Some DEs have utilities for viewing system files, the only benefit they provide is that the root password must be entered once to view all of them.

Or is it time to learn
https://www.howtogeek.com/496056/how-to … -on-linux/

P.S. I apologize, it was extremely inconvenient to type the text.
Look at this file in your home folder. Usually there is a log manager there, at least in my Trinity.

Revert back to slim from lightdm,
now shutdown log looks bit different than with lightdm, and no any warnings, thanks