• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue upgrade ssd make plesk down

F

forumsolutions79

New Pleskian
Hey,

we installed new server but now i am not able to connect plesk via browse but when i am able to connect via ssh when i am running command

service sw-cp-server restart

i am getting following output

Code: 
Redirecting to /bin/systemctl restart sw-cp-server.service
Job for sw-cp-server.service failed because the control process exited with error code. See "systemctl status sw-cp-server.service" and "journalctl -xe" for details.

after running journalctl -xe

i am getting

Code: 
Mar 30 01:01:59 plesk.glitch.win systemd[1]: Unit plesk-web-socket.service entered failed state.
Mar 30 01:01:59 plesk.glitch.win systemd[1]: plesk-web-socket.service failed.
Mar 30 01:02:01 plesk.glitch.win systemd[1]: Created slice User Slice of administrator.
-- Subject: Unit user-10000.slice has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit user-10000.slice has finished starting up.
--
-- The start-up result is done.
Mar 30 01:02:01 plesk.glitch.win rsyslogd[6509]: imjournal: fopen() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Read-only file system [v8.24.0-34.el7 try http://www.rsyslog.com/e/2013 ]
Mar 30 01:02:01 plesk.glitch.win systemd[1]: Started Session 203 of user administrator.
-- Subject: Unit session-203.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-203.scope has finished starting up.
--
-- The start-up result is done.
Mar 30 01:02:01 plesk.glitch.win CROND[24910]: (administrator) CMD (/opt/plesk/php/7.3/bin/php -q /var/www/vhosts/glitch.win/httpdocs/cmd.php xf:run-jobs)
Mar 30 01:02:01 plesk.glitch.win rsyslogd[6509]: action 'action 3' resumed (module 'builtin:omfile') [v8.24.0-34.el7 try http://www.rsyslog.com/e/2359 ]
Mar 30 01:02:01 plesk.glitch.win rsyslogd[6509]: file '/var/log/cron': open error: Read-only file system [v8.24.0-34.el7 try http://www.rsyslog.com/e/2433 ]
Mar 30 01:02:01 plesk.glitch.win rsyslogd[6509]: action 'action 3' resumed (module 'builtin:omfile') [v8.24.0-34.el7 try http://www.rsyslog.com/e/2359 ]
Mar 30 01:02:01 plesk.glitch.win rsyslogd[6509]: file '/var/log/cron': open error: Read-only file system [v8.24.0-34.el7 try http://www.rsyslog.com/e/2433 ]
Mar 30 01:02:01 plesk.glitch.win rsyslogd[6509]: action 'action 3' resumed (module 'builtin:omfile') [v8.24.0-34.el7 try http://www.rsyslog.com/e/2359 ]
Mar 30 01:02:01 plesk.glitch.win rsyslogd[6509]: file '/var/log/cron': open error: Read-only file system [v8.24.0-34.el7 try http://www.rsyslog.com/e/2433 ]
Mar 30 01:02:01 plesk.glitch.win rsyslogd[6509]: action 'action 3' resumed (module 'builtin:omfile') [v8.24.0-34.el7 try http://www.rsyslog.com/e/2359 ]
Mar 30 01:02:01 plesk.glitch.win rsyslogd[6509]: file '/var/log/cron': open error: Read-only file system [v8.24.0-34.el7 try http://www.rsyslog.com/e/2433 ]
Mar 30 01:02:01 plesk.glitch.win rsyslogd[6509]: action 'action 3' resumed (module 'builtin:omfile') [v8.24.0-34.el7 try http://www.rsyslog.com/e/2359 ]
Mar 30 01:02:01 plesk.glitch.win rsyslogd[6509]: file '/var/log/cron': open error: Read-only file system [v8.24.0-34.el7 try http://www.rsyslog.com/e/2433 ]
Mar 30 01:02:01 plesk.glitch.win rsyslogd[6509]: action 'action 3' resumed (module 'builtin:omfile') [v8.24.0-34.el7 try http://www.rsyslog.com/e/2359 ]
Mar 30 01:02:01 plesk.glitch.win rsyslogd[6509]: file '/var/log/cron': open error: Read-only file system [v8.24.0-34.el7 try http://www.rsyslog.com/e/2433 ]
Mar 30 01:02:01 plesk.glitch.win rsyslogd[6509]: action 'action 3' resumed (module 'builtin:omfile') [v8.24.0-34.el7 try http://www.rsyslog.com/e/2359 ]
Mar 30 01:02:01 plesk.glitch.win rsyslogd[6509]: file '/var/log/cron': open error: Read-only file system [v8.24.0-34.el7 try http://www.rsyslog.com/e/2433 ]
Mar 30 01:02:01 plesk.glitch.win rsyslogd[6509]: action 'action 3' resumed (module 'builtin:omfile') [v8.24.0-34.el7 try http://www.rsyslog.com/e/2359 ]
Mar 30 01:02:01 plesk.glitch.win rsyslogd[6509]: file '/var/log/cron': open error: Read-only file system [v8.24.0-34.el7 try http://www.rsyslog.com/e/2433 ]
Mar 30 01:02:01 plesk.glitch.win rsyslogd[6509]: action 'action 3' resumed (module 'builtin:omfile') [v8.24.0-34.el7 try http://www.rsyslog.com/e/2359 ]
Mar 30 01:02:01 plesk.glitch.win rsyslogd[6509]: file '/var/log/cron': open error: Read-only file system [v8.24.0-34.el7 try http://www.rsyslog.com/e/2433 ]
Mar 30 01:02:01 plesk.glitch.win rsyslogd[6509]: action 'action 3' resumed (module 'builtin:omfile') [v8.24.0-34.el7 try http://www.rsyslog.com/e/2359 ]
Mar 30 01:02:01 plesk.glitch.win rsyslogd[6509]: file '/var/log/cron': open error: Read-only file system [v8.24.0-34.el7 try http://www.rsyslog.com/e/2433 ]
Mar 30 01:02:01 plesk.glitch.win rsyslogd[6509]: action 'action 3' suspended, next retry is Thu Mar 30 01:02:31 2023 [v8.24.0-34.el7 try http://www.rsyslog.com/e/2007 ]
Mar 30 01:02:01 plesk.glitch.win rsyslogd[6509]: imjournal: fopen() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Read-only file system [v8.24.0-34.el7 try http://www.rsyslog.com/e/2013 ]
Mar 30 01:02:01 plesk.glitch.win rsyslogd[6509]: imjournal: fopen() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Read-only file system [v8.24.0-34.el7 try http://www.rsyslog.com/e/2013 ]
Mar 30 01:02:01 plesk.glitch.win systemd[1]: Removed slice User Slice of administrator.
-- Subject: Unit user-10000.slice has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit user-10000.slice has finished shutting down.
 
What's the output of
# mount
?
Do you see any entries with read-only file system ("(ro, ..." instead of "(rw, ..." your root partition?
 
yes when i try to restart
service sw-cp-server restart
i am getting output

Code: 
Job for sw-cp-server.service failed because the control process exited with error code. See "systemctl status sw-cp-server.service" and "journalctl -xe" for details.

and when i run journalctl -xe

i am getting output

Code: 
Mar 30 01:06:38 plesk.domain.win systemd[1]: Failed to start Postfix Mail Transport Agent.
-- Subject: Unit postfix.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit postfix.service has failed.
--
-- The result is failed.
Mar 30 01:06:38 plesk.domain.win systemd[1]: Unit postfix.service entered failed state.
Mar 30 01:06:38 plesk.domain.win systemd[1]: postfix.service failed.
Mar 30 01:06:40 plesk.domain.win systemd[1]: plesk-task-manager.service holdoff time over, scheduling restart.
Mar 30 01:06:40 plesk.domain.win systemd[1]: plesk-php74-fpm.service holdoff time over, scheduling restart.
Mar 30 01:06:40 plesk.domain.win rsyslogd[6509]: imjournal: fopen() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Read-only file system [v8.24.0-34.el7 try http://www.rsyslog.com/e/2013 ]
Mar 30 01:06:40 plesk.domain.win systemd[1]: Stopped The PHP 7.4.33 FastCGI Process Manager.
-- Subject: Unit plesk-php74-fpm.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit plesk-php74-fpm.service has finished shutting down.
Mar 30 01:06:40 plesk.domain.win systemd[1]: plesk-php74-fpm.service failed to run 'start' task: Read-only file system
Mar 30 01:06:40 plesk.domain.win systemd[1]: Failed to start The PHP 7.4.33 FastCGI Process Manager.
-- Subject: Unit plesk-php74-fpm.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit plesk-php74-fpm.service has failed.
--
-- The result is failed.
Mar 30 01:06:40 plesk.domain.win systemd[1]: Unit plesk-php74-fpm.service entered failed state.
Mar 30 01:06:40 plesk.domain.win systemd[1]: plesk-php74-fpm.service failed.
Mar 30 01:06:40 plesk.domain.win systemd[1]: Stopped Plesk Task Manager Service.
-- Subject: Unit plesk-task-manager.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit plesk-task-manager.service has finished shutting down.
Mar 30 01:06:40 plesk.domain.win systemd[1]: Started Plesk Task Manager Service.
-- Subject: Unit plesk-task-manager.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit plesk-task-manager.service has finished starting up.
--
-- The start-up result is done.
Mar 30 01:06:40 plesk.domain.win plesk-task-manager[26088]: 2023/03/30 01:06:40 Cannot open '/var/log/plesk/task-manager.log' log for writing: open /var/log/plesk/task-manager.log: read-only file system
Mar 30 01:06:40 plesk.domain.win rsyslogd[6509]: imjournal: fopen() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Read-only file system [v8.24.0-34.el7 try http://www.rsyslog.com/e/2013 ]
Mar 30 01:06:40 plesk.domain.win systemd[1]: plesk-task-manager.service: main process exited, code=exited, status=1/FAILURE
Mar 30 01:06:40 plesk.domain.win systemd[1]: Unit plesk-task-manager.service entered failed state.
Mar 30 01:06:40 plesk.domain.win systemd[1]: plesk-task-manager.service failed.

[root@plesk ~]# service sw-cp-server restart
Redirecting to /bin/systemctl restart sw-cp-server.service
Job for sw-cp-server.service failed because the control process exited with error code. See "systemctl status sw-cp-server.service" and "journalctl -xe" for details.
[root@plesk ~]# systemctl status sw-cp-server.service"
> ^C
[root@plesk ~]# systemctl status sw-cp-server.service
● sw-cp-server.service - Startup script for Plesk control panel server
   Loaded: loaded (/usr/lib/systemd/system/sw-cp-server.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2023-03-30 01:09:38 CEST; 17s ago
  Process: 26842 ExecStartPre=/usr/sbin/sw-cp-serverd -q -t (code=exited, status=1/FAILURE)

Mar 30 01:09:38 plesk.domain.win systemd[1]: Starting Startup script for Plesk control panel server...
Mar 30 01:09:38 plesk.domain.win sw-cp-serverd[26842]: nginx: [alert] could not open error log file: open() "/var/log/sw-cp-server/error_log" failed (30: Read-only file system)
Mar 30 01:09:38 plesk.domain.win sw-cp-serverd[26842]: 2023/03/30 01:09:38 [emerg] 26842#0: open() "/var/log/plesk/httpsd_access_log" failed (30: Read-only file system)
Mar 30 01:09:38 plesk.domain.win sw-cp-serverd[26842]: nginx: configuration file /etc/sw-cp-server/config test failed
Mar 30 01:09:38 plesk.domain.win systemd[1]: sw-cp-server.service: control process exited, code=exited status=1
Mar 30 01:09:38 plesk.domain.win systemd[1]: Failed to start Startup script for Plesk control panel server.
Mar 30 01:09:38 plesk.domain.win systemd[1]: Unit sw-cp-server.service entered failed state.
Mar 30 01:09:38 plesk.domain.win systemd[1]: sw-cp-server.service failed.
sudo mount -l

output

Code: 
sysfs on /sys type sysfs (rw,relatime)
proc on /proc type proc (rw,relatime)
devtmpfs on /dev type devtmpfs (rw,nosuid,size=32832668k,nr_inodes=8208167,mode=755)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_prio,net_cls)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
configfs on /sys/kernel/config type configfs (rw,relatime)
/dev/md2 on / type ext4 (ro,relatime,data=ordered)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=35,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=26299)
/dev/md1 on /boot type ext3 (rw,relatime,data=ordered)
tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=6571476k,mode=700)


df -i output

Code: 
Filesystem       Inodes   IUsed    IFree IUse% Mounted on

/dev/md2       60375040 7012009 53363031   12% /

devtmpfs        8208167     412  8207755    1% /dev

tmpfs           8214341       1  8214340    1% /dev/shm

tmpfs           8214341     606  8213735    1% /run

tmpfs           8214341      16  8214325    1% /sys/fs/cgroup

/dev/md1         131072     350   130722    1% /boot

tmpfs           8214341       1  8214340    1% /run/user/0

when i trying to remount sudo mount -o remount,rw /dev/md2 /

and i am getting

Code: 
mount: / not mounted or bad option

       In some cases useful info is found in syslog - try
       dmesg | tail or so.

dmesg | tail


Code: 
[12834.188848] EXT4-fs (md2): Couldn't remount RDWR because of unprocessed orphan inode list.  Please umount/remount instead

[12834.189437] EXT4-fs (md2): Couldn't remount RDWR because of unprocessed orphan inode list.  Please umount/remount instead

[12834.190214] EXT4-fs (md2): Couldn't remount RDWR because of unprocessed orphan inode list.  Please umount/remount instead

[12856.183885] EXT4-fs (md2): Couldn't remount RDWR because of unprocessed orphan inode list.  Please umount/remount instead

[12931.890337] EXT4-fs (md2): Couldn't remount RDWR because of unprocessed orphan inode list.  Please umount/remount instead

[13038.758669] EXT4-fs (md2): Couldn't remount RDWR because of unprocessed orphan inode list.  Please umount/remount instead

[13529.541805] EXT4-fs (md2): Couldn't remount RDWR because of unprocessed orphan inode list.  Please umount/remount instead

[13546.134414] EXT4-fs (md2): Couldn't remount RDWR because of unprocessed orphan inode list.  Please umount/remount instead

[15343.283918] EXT4-fs (md2): Couldn't remount RDWR because of unprocessed orphan inode list.  Please umount/remount instead

[16201.961401] EXT4-fs (md2): Couldn't remount RDWR because of unprocessed orphan inode list.  Please umount/remount instead




please someone help
 
So the problem is
/dev/md2 on / type ext4 (ro,relatime,data=ordered)
it would need to be
/dev/md2 on / type ext4 (rw,relatime,data=ordered)
but you probably figured that out already.

When you search in Google for "Couldn't remount RDWR because of unprocessed orphan inode list. Please umount/remount instead" you'll find proper articles that help how to resolve this.
 
You must log in or register to reply here.

Similar threads

M
Question Plesk E-Mail Security | Failed to start clamd scanner (amavisd) daemon
Replies
7
Views
1K
Raul A.
R
K
Issue Docker containers don't start after plesk/extension upgrades
Replies
0
Views
2K
kassi
K
O
Resolved Update Plesk 18.0.68 on CentOS7 result in no website reachable and email not working anymore
Replies
3
Views
462
Onkeltom01
O
I
Resolved Mariadb does not start when upgrading plesk to 18.0.58 Update 1
Replies
2
Views
2K
ivanes82
I
M
Question Upgrade MariaDB 10.3 to 10.11 via Plesk 18.0.61 on Debian 10
Replies
1
Views
987
Kaspar@Plesk
Kaspar@Plesk
Back
Top