Resolved [PPP-27341] /dev/log Expected: socket. Actual: symlink | Filesystem issues

[knightsystems]

OS ‪Ubuntu 16.04.1 LTS‬
Product Plesk Onyx
Version 17.0.17 Update #12, last updated on Dec 24, 2016 06:27 AM

root@alice: ~ # plesk repair fs -v

Checking Linux system files

  There are incorrect permissions on some items: /dev/log ........... [ERROR]
    - Incorrect permissions on /dev/log. Expected: one of 0666.
      Actual: 0777.
      Incorrect type of /dev/log. Expected: socket. Actual: symlink
  Do you want to repair incorrect permissions? [Y/n] y
    Repairing incorrect permissions ................................. [2016-12-27 11:44:58] ERR [util_exec] proc_close() failed ['/opt/psa/admin/bin/fsmng' '--set-ac' '/dev/log'] with exit code [1]

  fsmng failed: ERROR:Expected and actual types of file '/dev/log' do not match: socket != symlink .

Maybe this provides you more information, but I'm not sure about it:

Expand/Collapse Block

root@alice: ~ # systemctl status systemd-journald-dev-log.socket
● systemd-journald-dev-log.socket - Journal Socket (/dev/log)
   Loaded: loaded (/lib/systemd/system/systemd-journald-dev-log.socket; static; vendor preset: enabled)
   Active: active (running) since Tue 2016-12-27 11:35:32 EST; 18min ago
     Docs: man:systemd-journald.service(8)
           man:journald.conf(5)
   Listen: /run/systemd/journal/dev-log (Datagram)

root@alice: ~ # ls -l /run/systemd/journal/dev-log
srw-rw-rw- 1 root root 0 Dec 27 11:35 /run/systemd/journal/dev-log

root@alice: ~ # systemctl cat systemd-journald-dev-log.socket
# /lib/systemd/system/systemd-journald-dev-log.socket
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

[Unit]
Description=Journal Socket (/dev/log)
Documentation=man:systemd-journald.service(8) man:journald.conf(5)
DefaultDependencies=no
Before=sockets.target

# Mount and swap units need this. If this socket unit is removed by an
# isolate request the mount and swap units would be removed too,
# hence let's exclude this from isolate requests.
IgnoreOnIsolate=yes

[Socket]
Service=systemd-journald.service
ListenDatagram=/run/systemd/journal/dev-log
Symlinks=/dev/log
SocketMode=0666
PassCredentials=yes
PassSecurity=yes

# Increase both the send and receive buffer, so that things don't
# block early. Note that journald internally uses the this socket both
# for receiving syslog messages, and for forwarding them to any other
# syslog, hence we bump both values.
ReceiveBuffer=8M
SendBuffer=8M

Any Idea how to fix this?

Thanks

 

[IgorG]

fsmng failed: ERROR:Expected and actual types of file '/dev/log' do not match: socket != symlink .

What is output of command:

# ls -la /dev/log

?

 

[knightsystems]

Hi Igor,
as requested:

root@alice: ~ #  ls -la /dev/log
lrwxrwxrwx 1 root root 28 Dec 27 11:44 /dev/log -> /run/systemd/journal/dev-log

 

[IgorG]

I confirm this Ubuntu16 related bug (can't reproduce it on CentOS). I have submitted corresponding bugreport PPP-27341.

 

[Anas_Altunji]

I have same ERROR on Ubuntu 16.04 also

 

[Hayk]

Please fix it SOAP

 

[knightsystems]

When will it get resolved?

 

[NamNam]

I've the same issue, plz fix it !

 

[Mango]

Any ETA for this?

 

[IgorG]

We are going to fix it in one of nearest updates.

 

[IgorG]

Fixed in MU#16.

 

[Dukemaster]

Hi @IgorG and all
I also have this error everytime after each Plesk Update, like one hour ago. Everytime I made an Plesk Update these two errors appear, but only since around one month. I wonder if it's the same cause, while You told us it will be fixed with MU#16. (January).
And everytime it will be repaired in one second by # plesk repair fs -v or plesk repair all -y. Otherwise I have no problems except my biggest one that HSTS is not working since I activated OSCP stapling and use own DNS server which are working absolutely well.

I made what you suggested to do. Please take a short look at the whole process after updating and making a # reboot:

root@server:~# plesk repair all -n
Reconfiguring the Plesk installation
Checking the Plesk database using the native database server tools .. [OK]
Checking the structure of the Plesk database ........................ [OK]
Checking the consistency of the Plesk database ...................... [OK]
Checking system users ............................................... [OK]
Checking Linux system files

There are incorrect permissions on some items:
/etc/psa-webmail/horde ............................................ [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -verbose

There are incorrect permissions on some items in directories used by
Backup Manager .................................................... [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -verbose

Checking virtual hosts' file system ................................. [OK]
Checking Plesk version .............................................. [OK]
Checking for custom configuration templates ......................... [OK]
Checking for the JkWorkersFile directive in the Apache configuration [OK]
Checking associations between domains and IP addresses .............. [OK]
Checking for corrupted reference between IP collections and IP
addresses ........................................................... [OK]
Checking for links between APS applications and subscriptions ....... [OK]
Checking for the Zend extension declaraion in php.ini ............... [OK]
Check symbolic links for latest virtual host config files ........... [OK]
Checking for system users home directories consistency .............. [OK]
Checking for records with empty name field in the Configurations table[OK]
Checking for nginx ULIMIT value ..................................... [OK]
Checking for extra configurations in database not owned by any object [OK]
Repairing web server configuration .................................. [OK]
Checking the usage of PHP handlers .................................. [OK]
Repairing the mail server configuration ............................. [OK]
Checking the DNS configuration file ................................. [OK]
Restoring DNS server configuration .................................. [OK]
Checking MySQL database servers ..................................... [OK]
Repair databases on available servers ............................... [OK]
Repair database users on available servers .......................... [OK]

Error messages: 2; Warnings: 0; Errors resolved: 0

exit status 1

root@server:~# plesk repair fs -v

Checking Linux system files ......................................... [OK]
Checking virtual hosts' file system ................................. [OK]

Error messages: 0; Warnings: 0; Errors resolved: 0

root@server:~# ls -la /dev/log
lrwxrwxrwx 1 root root 28 Jul 17 09:51 /dev/log -> /run/systemd/journal/dev-log
root@server:~#

I thought about the idea to make a full reinstall of PLESK + patches + updates, also to perhaps solve the HSTS problem all in one together, but it seems not necessary at all:

# plesk installer --select-release-current --reinstall-patch --upgrade-installed-components

Lots of greets