Почему busybox вдруг ни с того ни с сего уходит в ребут?

Question

[Kamikadze1024]

Busybox уходит в ребут вдруг ни с того, ни с сего. Из-за чего это может быть? Как предупредить возникновение подобных ситуаций?

Железка на основе процессора nuvoton nuc 970.

Отрывок лога:

Jul  6 11:57:43 (none) syslog.info syslogd exiting
Jul  6 11:57:54 (none) syslog.info syslogd started: BusyBox v1.22.1
Jul  6 11:57:55 (none) daemon.info init: starting pid 543, tty '': '-/bin/sh'
Jul  7 09:59:46 (none) syslog.info syslogd started: BusyBox v1.22.1
Jul  7 09:59:47 (none) daemon.info init: starting pid 543, tty '': '-/bin/sh'
Jul  7 12:30:54 (none) syslog.info syslogd started: BusyBox v1.22.1
Jul  7 12:30:55 (none) daemon.info init: starting pid 542, tty '': '-/bin/sh'
Jul 10 12:12:37 (none) syslog.info syslogd started: BusyBox v1.22.1
Jul 10 12:12:38 (none) daemon.info init: starting pid 543, tty '': '-/bin/sh'
Jul 10 13:33:03 (none) daemon.info init: starting pid 707, tty '': '/bin/umount -a -r'
Jul 10 13:33:03 (none) daemon.info init: starting pid 708, tty '': '/sbin/swapoff -a'
Jul 10 13:33:04 (none) daemon.info init: The system is going down NOW!
Jul 10 13:33:04 (none) syslog.info syslogd exiting
Jul 10 13:33:12 (none) syslog.info syslogd started: BusyBox v1.22.1
Jul 10 13:33:17 (none) daemon.info init: starting pid 577, tty '': '/bin/umount -a -r'
Jul 10 13:33:18 (none) daemon.info init: starting pid 583, tty '': '/sbin/swapoff -a'
Jul 10 13:33:18 (none) daemon.info init: The system is going down NOW!
Jul 10 13:33:18 (none) syslog.info syslogd exiting
Jul 10 13:33:27 (none) syslog.info syslogd started: BusyBox v1.22.1
Jul 10 13:33:28 (none) daemon.info init: starting pid 542, tty '': '-/bin/sh'
Jul 12 11:41:10 (none) syslog.info syslogd started: BusyBox v1.22.1
Jul 12 11:41:11 (none) daemon.info init: starting pid 542, tty '': '-/bin/sh'
Jul 13 11:22:44 (none) syslog.info syslogd started: BusyBox v1.22.1
Jul 13 11:22:45 (none) daemon.info init: starting pid 542, tty '': '-/bin/sh'
Jul 13 14:00:03 (none) syslog.info syslogd started: BusyBox v1.22.1
Jul 13 14:00:04 (none) daemon.info init: starting pid 543, tty '': '-/bin/sh'
Jul 13 16:24:43 (none) syslog.info syslogd started: BusyBox v1.22.1
Jul 13 16:24:44 (none) daemon.info init: starting pid 542, tty '': '-/bin/sh'
Jul 14 08:39:19 (none) syslog.info syslogd started: BusyBox v1.22.1
Jul 14 08:39:20 (none) daemon.info init: starting pid 542, tty '': '-/bin/sh'
Jul 14 10:38:37 (none) syslog.info syslogd started: BusyBox v1.22.1
Jul 14 10:38:38 (none) daemon.info init: starting pid 542, tty '': '-/bin/sh'
Jul 17 10:34:38 (none) syslog.info syslogd started: BusyBox v1.22.1
Jul 17 10:34:39 (none) daemon.info init: starting pid 542, tty '': '-/bin/sh'
Jul 17 10:35:10 (none) daemon.info init: starting pid 676, tty '': '/bin/umount -a -r'
Jul 17 10:35:10 (none) daemon.info init: starting pid 677, tty '': '/sbin/swapoff -a'
Jul 17 10:35:10 (none) daemon.info init: The system is going down NOW!
Jul 17 10:35:10 (none) syslog.info syslogd exiting
Jul 17 10:35:20 (none) syslog.info syslogd started: BusyBox v1.22.1
Jul 17 10:35:25 (none) daemon.info init: starting pid 573, tty '': '/bin/umount -a -r'
Jul 17 10:35:26 (none) daemon.info init: starting pid 579, tty '': '/sbin/swapoff -a'
Jul 17 10:35:26 (none) daemon.info init: The system is going down NOW!
Jul 17 10:35:26 (none) syslog.info syslogd exiting
Jul 17 10:35:34 (none) syslog.info syslogd started: BusyBox v1.22.1
Jul 17 10:35:35 (none) daemon.info init: starting pid 542, tty '': '-/bin/sh'
Jul 17 21:44:04 (none) syslog.info syslogd started: BusyBox v1.22.1
Jul 17 21:44:05 (none) daemon.info init: starting pid 542, tty '': '-/bin/sh'
Jul 18 10:36:45 (none) syslog.info syslogd started: BusyBox v1.22.1
Jul 18 10:36:46 (none) daemon.info init: starting pid 542, tty '': '-/bin/sh'
Jul 18 15:12:50 (none) daemon.info init: starting pid 1380, tty '': '/bin/umount -a -r'
Jul 18 15:12:50 (none) daemon.info init: starting pid 1382, tty '': '/sbin/swapoff -a'
Jul 18 15:12:50 (none) daemon.info init: The system is going down NOW!
Jul 18 15:12:50 (none) syslog.info syslogd exiting
Jul 18 15:12:57 (none) syslog.info syslogd started: BusyBox v1.22.1
Jul 18 15:12:58 (none) daemon.info init: starting pid 543, tty '': '-/bin/sh'
Jul 18 16:50:31 (none) daemon.info init: starting pid 843, tty '': '/bin/umount -a -r'
Jul 18 16:50:31 (none) daemon.info init: starting pid 845, tty '': '/sbin/swapoff -a'
Jul 18 16:50:31 (none) daemon.info init: The system is going down NOW!
Jul 18 16:50:31 (none) syslog.info syslogd exiting
Jul 18 16:50:40 (none) syslog.info syslogd started: BusyBox v1.22.1
Jul 18 16:50:41 (none) daemon.info init: starting pid 542, tty '': '-/bin/sh'
Jul 18 17:13:32 (none) syslog.info syslogd started: BusyBox v1.22.1
Jul 18 17:13:33 (none) daemon.info init: starting pid 542, tty '': '-/bin/sh'
Jul 19 10:55:47 (none) syslog.info syslogd started: BusyBox v1.22.1
Jul 19 10:55:48 (none) daemon.info init: starting pid 542, tty '': '-/bin/sh'

Answer 1

[jcmvbkbc]

Из-за чего это может быть?

Из-за содержимого /etc/inittab? Или /etc/crontab?

Comments

[Kamikadze1024]

В /etc/inittab написано следующее:

/etc # cat inittab 
# /etc/inittab init(8) configuration for BusyBox
#
# Copyright (C) 1999-2004 by Erik Andersen <[e-mail]>
#
#
# Note, BusyBox init doesn't support runlevels.  The runlevels field is
# completely ignored by BusyBox init. If you want runlevels, use sysvinit.
#
#
# Format for each entry: <id>:<runlevels>:<action>:<process>
#
# <id>: WARNING: This field has a non-traditional meaning for BusyBox init!
#
#	The id field is used by BusyBox init to specify the controlling tty for
#	the specified process to run on.  The contents of this field are
#	appended to "/dev/" and used as-is.  There is no need for this field to
#	be unique, although if it isn't you may have strange results.  If this
#	field is left blank, it is completely ignored.  Also note that if
#	BusyBox detects that a serial console is in use, then all entries
#	containing non-empty id fields will be ignored.  BusyBox init does
#	nothing with utmp.  We don't need no stinkin' utmp.
#
# <runlevels>: The runlevels field is completely ignored.
#
# <action>: Valid actions include: sysinit, respawn, askfirst, wait, once,
#                                  restart, ctrlaltdel, and shutdown.
#
#       Note: askfirst acts just like respawn, but before running the specified
#       process it displays the line "Please press Enter to activate this
#       console." and then waits for the user to press enter before starting
#       the specified process.
#
#       Note: unrecognised actions (like initdefault) will cause init to emit
#       an error message, and then go along with its business.
#
# <process>: Specifies the process to be executed and it's command line.
#
# Note: BusyBox init works just fine without an inittab. If no inittab is
# found, it has the following default behavior:
#         ::sysinit:/etc/init.d/rcS
#         ::askfirst:/bin/sh
#         ::ctrlaltdel:/sbin/reboot
#         ::shutdown:/sbin/swapoff -a
#         ::shutdown:/bin/umount -a -r
#         ::restart:/sbin/init
#
# if it detects that /dev/console is _not_ a serial console, it will
# also run:
#         tty2::askfirst:/bin/sh
#         tty3::askfirst:/bin/sh
#         tty4::askfirst:/bin/sh
#
# Boot-time system configuration/initialization script.
# This is run first except when booting in single-user mode.
#
::sysinit:/etc/init.d/rcS

# /bin/sh invocations on selected ttys
#
# Note below that we prefix the shell commands with a "-" to indicate to the
# shell that it is supposed to be a login shell.  Normally this is handled by
# login, but since we are bypassing login in this case, BusyBox lets you do
# this yourself...
#
# Start an "askfirst" shell on the console (whatever that may be)
::once:-/bin/sh
# Start an "askfirst" shell on /dev/tty2-4
#tty2::askfirst:-/bin/sh
#tty3::askfirst:-/bin/sh
#tty4::askfirst:-/bin/sh

# /sbin/getty invocations for selected ttys
#tty4::respawn:/sbin/getty 38400 tty5
#tty5::respawn:/sbin/getty 38400 tty6

# Example of how to put a getty on a serial line (for a terminal)
#::respawn:/sbin/getty -L ttyS0 9600 vt100
#::respawn:/sbin/getty -L ttyS1 9600 vt100
#
# Example how to put a getty on a modem line.
#::respawn:/sbin/getty 57600 ttyS2

# Stuff to do when restarting the init process
::restart:/sbin/init

# Stuff to do before rebooting
::ctrlaltdel:/sbin/reboot
::shutdown:/bin/umount -a -r
::shutdown:/sbin/swapoff -a

Есть ли в нем что-то некорректное?

[jcmvbkbc]

Есть ли в нем что-то некорректное?

Вроде нормально выглядит. Проверил у себя -- работает, из шелла не выходит, если его убить не перезагружается.

::ctrlaltdel:/sbin/reboot

Может кто-то Ctrl-Alt-Del нажимает? Ведь явно же по логам выполняются команды

::shutdown:/bin/umount -a -r
::shutdown:/sbin/swapoff -a

[Kamikadze1024]

Нажать Ctrl-Alt-Del пользователю невозможно. Все происходит самопроизвольно.