• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Issue \run\systemd\sessions -> full folder

hardbrasil

Regular Pleskian
Hello fellas,

our folder \run is full, i remove some logs and release couple MB to initialization of services.
The folder that is full is \run\systemd\sessions and i am unable to List this directory (too many files)
my doubt is, how can i erase this content, and if is permitted to erase them.

this happen some days after the server was hacked (some web sites was phished) maybe is coincidence.

thanks

Filesystem Size Used Avail Use% Mounted on
/dev/mapper/centos-root 579G 272G 308G 47% /
devtmpfs 1.5G 0 1.5G 0% /dev
tmpfs 1.5G 0 1.5G 0% /dev/shm
tmpfs 1.5G 1.4G 107M 93% /run
tmpfs 1.5G 0 1.5G 0% /sys/fs/cgroup
/dev/sda1 473M 262M 211M 56% /boot
tmpfs 298M 0 298M 0% /run/user/0
tmpfs 298M 0 298M 0% /run/user/10021
tmpfs 298M 0 298M 0% /run/user/10004
tmpfs 298M 0 298M 0% /run/user/10008
tmpfs 298M 0 298M 0% /run/user/10018
tmpfs 298M 0 298M 0% /run/user/10009
tmpfs 298M 0 298M 0% /run/user/10026
tmpfs 298M 0 298M 0% /run/user/30
 
Using 'find' to list a subset of the files may workaround the limitations of 'ls' - the following command:

find /run/systemd/sessions/ -mtime -1

...will find any files newer than 1 day. (-2 = newer than 2 days and so on.)

If that works you can delete the listed files by running:

find /run/systemd/sessions/ -mtime -1 -exec rm -f {} \;

Obviously take great caution with this command and deleting files - I couldn't comment on whether you *should* delete those files and what impact that will have.
 
Back
Top