rsyslogd was huped что это
собственно сабж
в логах запись:
syslog:
May 26 19:50:07 **** shutdown[21501]: shutting down for system halt
May 26 19:50:07 **** init: Switching to runlevel: 0
больше ничего интересного нету, только крон от мунина.
ну и включение
в момент выключения(подачи команды) никто к серверу подключен не был.
собственно вопрос, чем может быть вызвано выключение? похоже на нажатие кнопки, но сомневаюсь.
больше ничего интересного нету, только крон от мунина.
А софта для работы с бесперебойниками случаем нету в системе?
Попробуй прошерстить все логи за это же время (+/- минут 10). Может всплывёт что-то интересное.
похоже на нажатие кнопки, но сомневаюсь.
Корректное завершение работы по нажатию на кнопку «power» может быть только если установлен acpid или какая-нибудь среда рабочего стола.
[code]
May 26 06:25:02 ****** rsyslogd: [origin software=«rsyslogd» swVersion=«4.6.4» x-pid=«2419» x-info=»http://www.rsyslog.com«] rsyslogd was HUPed, type ‘lightweight’.
May 26 06:25:02 ****** rsyslogd: [origin software=„rsyslogd“ swVersion=„4.6.4“ x-pid=„2419“ x-info=»http://www.rsyslog.com«] rsyslogd was HUPed, type ‘lightweight’.
May 26 19:50:07 ****** shutdown[21501]: shutting down for system halt
[/code]
дальше думаю смысла смотреть логи нету.
acpid стоит.
но вот. бесперебойный нету. это сервер в селектеле.
до этого у него аптайм был уже примерно 150 дней, и не было проблем.
Rsyslogd was huped что это
]# cat /var/log/messages
May 17 03:32:02 hylafax-vm rsyslogd: [origin software=»rsyslogd» swVersion=»5.8.10″ x-pid=»1647″ x-info=»http://www.rsyslog.com»] rsyslogd was HUPed
——————————-
This in the only message that I can fing in messages log, it seems as the log is resetted but then the rsyslogd became HUPed and the system is freezed
Do you have any solution?
Regards
Since the issue happens at the same time for you all the time, i would look at the crontab for each user (and /etc/cron.weekly) to see what happens on the server at that time.
thanks for your reply. I already checked the /etc/cront.weekly directory, but is is empty. I checked also all /etc/cron.* directories, I commented the raid-check because it was schedulated on Sunday but the problem persist. I think it is a problem with the logrotate but I don’t know the precisious bug, The logrotate.conf is the following:
[root@hylafax-vm cron.daily]# cat /etc/logrotate.conf
# see «man logrotate» for details
# rotate log files weekly
weekly
# keep 4 weeks worth of backlogs
rotate 4
# create new (empty) log files after rotating old ones
create
# use date as a suffix of the rotated file
dateext
# uncomment this if you want your log files compressed
#compress
# RPM packages drop log rotation information into this directory
include /etc/logrotate.d
/var/log/btmp <
missingok
monthly
create 0600 root utmp
rotate 1
>
# system-specific logs may be also be configured here.
In your opinion is there a error?
Do you have any suggests?
i have exactly the same problem as tiger.
This is my /var/log/cron log 1 second before the entry inthe messages log.
root@CentOSVM:/var/log#cat cron-2015110
Nov 1 03:49:01 CentOSVM run-parts(/etc/cron.daily)[9634]: starting logrotate
root@CentOSVM:/var/log#cat messages-20151101
Nov 1 03:49:02 CentOSVM rsyslogd: [origin software=»rsyslogd» swVersion=»5.8.10″ x-pid=»1500″ x-info=»http://www.rsyslog.com»] rsyslogd was HUPed
Her my logorate config:
root@CentOSVM:/var/log#cat /etc/logrotate.conf
# see «man logrotate» for details
# rotate log files weekly
weekly
# keep 4 weeks worth of backlogs
rotate 4
# create new (empty) log files after rotating old ones
create
# use date as a suffix of the rotated file
dateext
# uncomment this if you want your log files compressed
#compress
# RPM packages drop log rotation information into this directory
include /etc/logrotate.d
/var/log/btmp <
missingok
monthly
create 0600 root utmp
rotate 1
>
Thread: rsyslogd was HUPed, type ‘lightweight’
Thread Tools
Display
/var/log/messages:
Jan 14 06:43:59 igate rsyslogd: [origin software=»rsyslogd» swVersion=»4.2.0″ x-pid=»831″ x-info=»http://www.rsyslog.com»] rsyslogd was HUPed, type ‘lightweight’.
Jan 14 06:43:59 igate rsyslogd: [origin software=»rsyslogd» swVersion=»4.2.0″ x-pid=»831″ x-info=»http://www.rsyslog.com»] rsyslogd was HUPed, type ‘lightweight’.
Jan 15 06:43:39 igate rsyslogd: [origin software=»rsyslogd» swVersion=»4.2.0″ x-pid=»831″ x-info=»http://www.rsyslog.com»] rsyslogd was HUPed, type ‘lightweight’.
Jan 16 06:52:50 igate rsyslogd: [origin software=»rsyslogd» swVersion=»4.2.0″ x-pid=»831″ x-info=»http://www.rsyslog.com»] rsyslogd was HUPed, type ‘lightweight’.
Jan 17 06:35:15 igate rsyslogd: [origin software=»rsyslogd» swVersion=»4.2.0″ x-pid=»831″ x-info=»http://www.rsyslog.com»] rsyslogd was HUPed, type ‘lightweight’.
May be Ubuntu server 9.10 is Alpha?
Re: rsyslogd was HUPed, type ‘lightweight’
/var/log/messages:
Jan 14 06:43:59 igate rsyslogd: [origin software=»rsyslogd» swVersion=»4.2.0″ x-pid=»831″ x-info=»http://www.rsyslog.com»] rsyslogd was HUPed, type ‘lightweight’.
Jan 14 06:43:59 igate rsyslogd: [origin software=»rsyslogd» swVersion=»4.2.0″ x-pid=»831″ x-info=»http://www.rsyslog.com»] rsyslogd was HUPed, type ‘lightweight’.
Jan 15 06:43:39 igate rsyslogd: [origin software=»rsyslogd» swVersion=»4.2.0″ x-pid=»831″ x-info=»http://www.rsyslog.com»] rsyslogd was HUPed, type ‘lightweight’.
Jan 16 06:52:50 igate rsyslogd: [origin software=»rsyslogd» swVersion=»4.2.0″ x-pid=»831″ x-info=»http://www.rsyslog.com»] rsyslogd was HUPed, type ‘lightweight’.
Jan 17 06:35:15 igate rsyslogd: [origin software=»rsyslogd» swVersion=»4.2.0″ x-pid=»831″ x-info=»http://www.rsyslog.com»] rsyslogd was HUPed, type ‘lightweight’.
May be Ubuntu server 9.10 is Alpha?
it is most certainly NOT alpha. i have been getting this on some of my Debian installs as well. i have not yet found an answer to it.
Thread: rsyslogd was HUPed, type ‘lightweight’
Thread Tools
Display
/var/log/messages:
Jan 14 06:43:59 igate rsyslogd: [origin software=»rsyslogd» swVersion=»4.2.0″ x-pid=»831″ x-info=»http://www.rsyslog.com»] rsyslogd was HUPed, type ‘lightweight’.
Jan 14 06:43:59 igate rsyslogd: [origin software=»rsyslogd» swVersion=»4.2.0″ x-pid=»831″ x-info=»http://www.rsyslog.com»] rsyslogd was HUPed, type ‘lightweight’.
Jan 15 06:43:39 igate rsyslogd: [origin software=»rsyslogd» swVersion=»4.2.0″ x-pid=»831″ x-info=»http://www.rsyslog.com»] rsyslogd was HUPed, type ‘lightweight’.
Jan 16 06:52:50 igate rsyslogd: [origin software=»rsyslogd» swVersion=»4.2.0″ x-pid=»831″ x-info=»http://www.rsyslog.com»] rsyslogd was HUPed, type ‘lightweight’.
Jan 17 06:35:15 igate rsyslogd: [origin software=»rsyslogd» swVersion=»4.2.0″ x-pid=»831″ x-info=»http://www.rsyslog.com»] rsyslogd was HUPed, type ‘lightweight’.
May be Ubuntu server 9.10 is Alpha?
Re: rsyslogd was HUPed, type ‘lightweight’
/var/log/messages:
Jan 14 06:43:59 igate rsyslogd: [origin software=»rsyslogd» swVersion=»4.2.0″ x-pid=»831″ x-info=»http://www.rsyslog.com»] rsyslogd was HUPed, type ‘lightweight’.
Jan 14 06:43:59 igate rsyslogd: [origin software=»rsyslogd» swVersion=»4.2.0″ x-pid=»831″ x-info=»http://www.rsyslog.com»] rsyslogd was HUPed, type ‘lightweight’.
Jan 15 06:43:39 igate rsyslogd: [origin software=»rsyslogd» swVersion=»4.2.0″ x-pid=»831″ x-info=»http://www.rsyslog.com»] rsyslogd was HUPed, type ‘lightweight’.
Jan 16 06:52:50 igate rsyslogd: [origin software=»rsyslogd» swVersion=»4.2.0″ x-pid=»831″ x-info=»http://www.rsyslog.com»] rsyslogd was HUPed, type ‘lightweight’.
Jan 17 06:35:15 igate rsyslogd: [origin software=»rsyslogd» swVersion=»4.2.0″ x-pid=»831″ x-info=»http://www.rsyslog.com»] rsyslogd was HUPed, type ‘lightweight’.
May be Ubuntu server 9.10 is Alpha?
it is most certainly NOT alpha. i have been getting this on some of my Debian installs as well. i have not yet found an answer to it.
Rsyslogd was huped что это
Hello,
Anyone know what the following means?
Mar 20 06:25:05 raspberrypi rsyslogd: [origin software=»rsyslogd» swVersion=»5.8.11″ x-pid=»1616″ x-info=»http://www.rsyslog.com»] rsyslogd was HUPed
. the message (in /var/log/messages) appears every day at the same time. Obviously, the SD card can handle one message per day for a very long time. I’m more curious though, as the rsyslog.com website looks a little ‘out of context’ (so to speak) for the RPi and although ‘professional support is just one click away’ (as they say) I wondered if anyone here has any ideas?
Re: rsyslogd was HUPed
So far, so confusing.
What that doesn’t explain, is that many Linux programs use the HUP signal as an instruction to re-read their configuration files. A program like rsyslogd is running all the time, and it probably only reads its configuration files when it starts. If the user makes some changes, rsyslogd wont notice and will continue doing things the old way. So the user can send a HUP signal to the rsyslogd process to tell it the configuration files have changed and it should read them again. Just to be sure, it seems something sends rsyslogd a HUP signal every day, in case the user changes something and forgets to send the signal.
You can send signals with the also confusingly named «kill» command. See its man page for details.