• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Messages log not working?

P

Pleskie

Regular Pleskian
A while ago I upgraded (from version 12.5) to Plesk Onyx.

Today a few times I entered my password wrong by mistake. I wanted to see in the log what exactly happened. So I went to var/log to see the "messages" log. However, this file was empty except this line:

... rsyslogd: [origin software="rsyslogd" swVersion="7.4.7" x-pid="159" x-info="http://www.rsyslog.com"] rsyslogd was HUPed

What does this mean?

Also l see in this same directory that the log "secure" is totally empty.

This doesn't seem alright.

Can anyone tell me what is going on?
 
Hi Pleskie,

I strongly assume, that you use "systemd", instead of "sysvinit" on your server and if you don't configure your server in a different way, then "rsyslogd" has been replaced with "journalctl".
If you don't like the "Binary log" from journalctl, you just pass it over to "rsyslogd" and you will see log - messages in the old standarts.
 
Thanks UFHH01

I don't know (yet) what you mean.

I see in the old logs the logging stopped since February 20.

I see this message:

... rsyslogd: [origin software="rsyslogd" swVersion="7.4.7" x-pid="159" x-info="http://www.rsyslog.com"] rsyslogd was HUPed

What does this mean, and whyu did the logging stop?

Is it something that Plesk changed?

I don't know what to do now. Is this a bug? If so, how do I solve this?
 
Hi Pleskie,

Pleskie said:
Is it something that Plesk changed?
Click to expand...
No.

Pleskie said:
Is this a bug?
Click to expand...
No.

You should consider to inform yourself about "systemd" and "sysvinit" over the documentation of your operating system.
In addition, it might as well help to google the combination: "YOUR-OPERATING-SYSTEM" "systemd" "rsyslogd"

Since the server configuration which log - configuration is used on your server is not at all a Plesk related task, you should consider top open a thread at => Home > Forum > General Discussion > Open Topics
 
Pretty strange. Why it stopped? :-s

It always worked and I didn't change anything ... opened a new topic on the forum you suggested.
 
You must log in or register to reply here.

Similar threads

M
Resolved Failed to start The Apache HTTP Server: SELinux impedisce a /usr/sbin/httpd un accesso open su file /var/log/modsec_audit.log. -- SOLVED --
Replies
0
Views
2K
mmcomputers
M
tkalfaoglu
Question Spamd, per-user configuration
Replies
0
Views
578
tkalfaoglu
tkalfaoglu
B
Resolved Update broke FTP access
Replies
5
Views
959
Sebahat.hadzhi
Sebahat.hadzhi
J
Input Log browser started causing high load
Replies
10
Views
2K
jorge ceballos
J
V
Issue Smarthost + SRS = relay?
Replies
2
Views
10K
vanlier
V
Back
Top