• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Resolved Strange systemd messages piling up

tkalfaoglu

Silver Pleskian
Server operating system version
AlmaLinux
Plesk version and microupdate number
Obsidian
Every few seconds I see new entries in the logs like:

Code:
systemd[7051]: Failed to canonicalize path '/usr/local/psa/admin/.config/systemd/user.control/run-user-10123.mount.wants': Permission denied
systemd[7051]: Failed to canonicalize path '/usr/local/psa/admin/.config/systemd/user/run-user-10123.mount.wants': Permission denied
systemd[7051]: Failed to canonicalize path '/usr/local/psa/admin/.config/systemd/user.control/run-user-10123.mount.requires': Permission denied
systemd[7051]: Failed to canonicalize path '/usr/local/psa/admin/.config/systemd/user/run-user-10123.mount.requires': Permission denied
systemd[7051]: Failed to canonicalize path '/usr/local/psa/admin/.config/systemd/user.control/run-user-10123.mount.d': Permission denied
systemd[7051]: Failed to canonicalize path '/usr/local/psa/admin/.config/systemd/user/run-user-10123.mount.d': Permission denied

I checked and /usr/local/psa/admin/.config/systemd/user.control/ path did not exist on the system, so I created the user.control directory with chmod 777, but still the error continues..

The user 10123 exists on the system - regular web hosting customer.
But the user number keeps changing too -- a few seconds later I got the same "block" of errors for a different user number..

What shall I do?
 
This is NodeJS bug #EXTNODEJS-231.

As a possible workaround, create empty files that appear in the error message. For example:

# touch /usr/local/psa/admin/.config/systemd/user/run-user-10123.mount.d
 
This is NodeJS bug #EXTNODEJS-231.

As a possible workaround, create empty files that appear in the error message. For example:

# touch /usr/local/psa/admin/.config/systemd/user/run-user-10123.mount.d
I tried that first, but the permission errors continued -- besides the system is very creative with the names and the userid's so you probably need to create hundreds of these files/folders.

I instead changed the systemd logging levels.. it's all quiet now!
 
Unfortunately if I lower the logging levels I also miss some important information.. Is there any news about this bug?

I'm getting about a dozen of them EVERY SECOND..

Thanks!
-t
 
This is NodeJS bug #EXTNODEJS-231.

As a possible workaround, create empty files that appear in the error message. For example:

# touch /usr/local/psa/admin/.config/systemd/user/run-user-10123.mount.d
Btw, I did that just now, I created all the files mentioned in journalctl , it still kept giving Permission Denied.. So I set them to 777, it still keeps giving Permission Denied..
 
Btw you CAN disable the systemd logging -- or raise its level so it won't log anything or very little.
But that also stops other logging, like postfix I found.
 
Back
Top