Weird thing in messages log

L

Leap

Verified User
Joined
Jun 15, 2016
Messages
38
Hi all,

This may be a weird question but I don't know where to look anymore...

I recently updated some servers from centos 7 to almalinux 8, I used the guide from Active8 (https://forum.directadmin.com/threads/how-to-inplace-upgrade-from-centos-7-to-almalinux-8-5.64994/). It seemed to work great, however....

Since the upgrade I got some weird things in de /var/log/messages file after each (hard) reboot...
(With hard reboot I mean cycle the power in WMware in this case).
It goes through the normal startup things then the following happens:

Apr 13 14:15:54 [SERVERNAME] mysqld[1276]: 2023-04-13 14:15:54 0 [Note] InnoDB: Buffer pool(s) load completed at 230413 14:15:54 Mar 20 11:31:57 [SERVERNAME] pure-ftpd[707176]: ([email protected]) [INFO] [email protected] is now logged in Mar 20 11:32:41 [SERVERNAME] pure-ftpd[707339]: ([email protected]) [INFO] [email protected] is now logged in ...

It seems to merge an old pure-ftpd log or something...
After those lines of code the following happens:

Apr 3 00:00:01 [SERVERNAME] systemd[1283741]: Started Mark boot as successful after the user session has run 2 minutes. Apr 3 00:00:01 [SERVERNAME] systemd[1283741]: Reached target Timers. Apr 3 00:00:01 [SERVERNAME] systemd[1283741]: Reached target Paths. Apr 3 00:00:01 [SERVERNAME] systemd[1283735]: Reached target Paths. ...

Then after that it continues with the normal procedures...

Does any one have any idea where to look for this?
 
Last edited:
First I would suggest to edit your message and mask that adress, at least partly and maybe the ip address.

But what is the problem exactly?
Is it that it shows the pure-ftpd login in the system log instead of in the pure-ftpd log or pureftpd-auth.log file?

Also the second part, it's just systemd messages, nothing to worry about. If you search on the internet for it, you will find it multiple times.
Amongst here:

Also here, but I have no subscribtion, seems it might be from some cronjob. I wouldn't worry about it.
access.redhat.com

Many messages are output for a user cron job in Red Hat Enterprise Linux 8 - Red Hat Customer Portal

Many messages were generated for a cron job running every one minute in Red Hat Enterprise Linux 8. The following is the sample. crond[1237]: (tester) RELOAD (/var/spool/cron/tester) systemd[1]: Created slice User Slice of UID 1000. systemd[1]: Started /run/user/1000 mount wrapper. systemd[1]...
access.redhat.com access.redhat.com
 
Thanks for the mask suggestion!

The problem is that I don't know if it is a problem, also I just want to know why it is there...
I can't seem to find a cron which runs on reboot (after powerloss)...
 
It might be a cron, not necessarily. Most likely the systemd is running in debug mode by default and providing too much info you don't need.

Same is to be found here:
unix.stackexchange.com

Centos8 - After a login systemd touches /boot/grub2

I'm using Centos8 on a mini-PC as a router/firewall, and run Tripwire. I'm the only one who ever logs in, always as a non-privileged user, not root (ssh root login is disabled). Every time I login...
unix.stackexchange.com unix.stackexchange.com
It's hard to tell why exactly it's there and big chance the user is the systemd-user.

It's no problem at all. If it was a problem, you would get error messages. Even warnings are not always a problem. These are just logs and a notice, so only logging, not a problem.
 
So, I don't need to worry...
Still would be interesting to find out where it is coming from...
 
Hello,

I saw the same once. And if I recollect it correct, I had to change rsyslog to syslog-ng to get it "fixed". I don't know why it happens. So you might try the same and see whether it will work in your case the same.
 
You must log in or register to reply here.
Back
Top