• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Issue Broken after upgrade to Php 18 and Apache 2

jecalderon

New Pleskian
Server operating system version
Ubuntu 18
Plesk version and microupdate number
Obsidian 18.0.50.1
I upgraded PHP to latest version . Whn upgrading the Apache, the server stop working. I read errors with APache2 not able to fire.
root@web:~# sudo systemctl start apache2
Job for apache2.service failed because the control process exited with error code.
See "systemctl status apache2.service" and "journalctl -xe" for details.

Also
Active: failed (Result: exit-code) since Fri 2023-02-10 01:06:39 PST; 7min ago
Process: 7971 ExecStart=/usr/sbin/apachectl start (code=exited, status=139)

Feb 10 01:06:38 web.bosskeeper.com systemd[1]: Starting The Apache HTTP Server...
Feb 10 01:06:38 web.bosskeeper.com apachectl[7971]: [Fri Feb 10 01:06:38.756693 2023] [so:warn] [
Feb 10 01:06:39 web.bosskeeper.com apachectl[7971]: Segmentation fault
Feb 10 01:06:39 web.bosskeeper.com apachectl[7971]: Action 'start' failed.
Feb 10 01:06:39 web.bosskeeper.com apachectl[7971]: The Apache error log may have more informatio
Feb 10 01:06:39 web.bosskeeper.com systemd[1]: apache2.service: Control process exited, code=exit
Feb 10 01:06:39 web.bosskeeper.com systemd[1]: apache2.service: Failed with result 'exit-code'.
Feb 10 01:06:39 web.bosskeeper.com systemd[1]: Failed to start The Apache HTTP Server.
lines 1-15/15 (END)
└─apache2-systemd.conf: command not found
root@web:~# Active: failed (Result: exit-code) since Fri 2023-02-10 01:06:39 PST; 7min ago
-bash: syntax error near unexpected token `('
root@web:~# Process: 7971 ExecStart=/usr/sbin/apachectl start (code=exited, status=139)
-bash: syntax error near unexpected token `('
root@web:~#
root@web:~# Feb 10 01:06:38 web.bosskeeper.com systemd[1]: Starting The Apache HTTP Server...
Feb: command not found
root@web:~# Feb 10 01:06:38 web.bosskeeper.com apachectl[7971]: [Fri Feb 10 01:06:38.756693 2023] [so:warn] [
Feb: command not found
root@web:~# Feb 10 01:06:39 web.bosskeeper.com apachectl[7971]: Segmentation fault

Any help?

Feb: command not found
root@web:~# Feb 10 01:06:39 web.bosskeeper.com apachectl[7971]: Action 'start' failed.
Feb: command not found
root@web:~# Feb 10 01:06:39 web.bosskeeper.com apachectl[7971]: The Apache error log may have more informatio
Feb: command not found
root@web:~# Feb 10 01:06:39 web.bosskeeper.com systemd[1]: apache2.service: Control process exited, code=exit
Feb: command not found
root@web:~# Feb 10 01:06:39 web.bosskeeper.com systemd[1]: apache2.service: Failed with result 'exit-code'.
Feb: command not found
root@web:~# Feb 10 01:06:39 web.bosskeeper.com systemd[1]: Failed to start The Apache HTTP Server.
Feb: command not found
root@web:~# lines 1-15/15 (END)
-bash: syntax error near unexpected token `('
root@web:~#
 
Back
Top