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
after running journalctl -xe
i am getting
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.