• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

Plesk don't start

E

ErikdeEngerd

Guest
Hi all

After upgrade to 8.3 , i can't login in plesk.
When i go to https://ns1.machine.com , the plesk default page is viewed , but when i go to https://ns1.machine.com:8443 i have , can not make connection with .......
After the command /etc/rc.d/init.d/psa start , i have this ,
Starting xinetd service... done
Starting named service... done
Starting mysqld service... done
Starting qmail service... done
Starting courier-imap service... done
Starting postgresql service... done
Starting psa-spamassassin service... done
Starting Plesk... failed
Starting drwebd service... failed

What can i do ,

thanks Erik
 
check the logs of the plesk service, they surelly will tell you what went wrong...
 
Logs

The logs tell's me nothing , see below , or you may have other logs? (httpsd_error_log)

Installing the package psa-autoinstaller-3.3.0-build33071215.17.i586
The packages were installed successfully.
[Wed Dec 26 16:01:08 2007] [notice] caught SIGTERM, shutting down

But what is shutting down? i don't no

Thanks
 
I have the same problem

[Wed Dec 26 16:01:08 2007] [notice] caught SIGTERM, shutting down
 
Heres my error LOG

[Thu Dec 27 14:25:05 2007] [warn] child process 23980 still did not exit, sending a SIGTERM
[Thu Dec 27 14:25:06 2007] [warn] child process 23982 still did not exit, sending a SIGTERM
[Thu Dec 27 14:25:06 2007] [warn] child process 24033 still did not exit, sending a SIGTERM
[Thu Dec 27 14:25:06 2007] [warn] child process 25998 still did not exit, sending a SIGTERM
[Thu Dec 27 14:25:06 2007] [warn] child process 26174 still did not exit, sending a SIGTERM
[Thu Dec 27 14:25:06 2007] [warn] child process 20870 still did not exit, sending a SIGTERM
[Thu Dec 27 14:25:06 2007] [warn] child process 26175 still did not exit, sending a SIGTERM
[Thu Dec 27 14:25:06 2007] [warn] child process 27683 still did not exit, sending a SIGTERM
[Thu Dec 27 14:25:06 2007] [warn] child process 18135 still did not exit, sending a SIGTERM
[Thu Dec 27 14:25:06 2007] [warn] child process 2503 still did not exit, sending a SIGTERM
[Thu Dec 27 14:25:06 2007] [warn] child process 2504 still did not exit, sending a SIGTERM
[Thu Dec 27 14:25:06 2007] [warn] child process 5697 still did not exit, sending a SIGTERM
[Thu Dec 27 14:25:06 2007] [warn] child process 22615 still did not exit, sending a SIGTERM
[Thu Dec 27 14:25:06 2007] [warn] child process 23189 still did not exit, sending a SIGTERM
[Thu Dec 27 14:25:06 2007] [warn] child process 24106 still did not exit, sending a SIGTERM
[Thu Dec 27 14:25:06 2007] [notice] mod_fcgid: process /var/www/vhosts/ofrinse.co.uk/httpdocs/test/fcgi/test.fcgi(3078) exit(shutting down), terminated by calling exit(), return code: 0
[Thu Dec 27 14:25:06 2007] [notice] mod_fcgid: process /var/www/vhosts/hughmail.co.uk/httpdocs/test/fcgi/test.fcgi(18094) exit(shutting down), terminated by calling exit(), return code: 0
[Thu Dec 27 14:25:08 2007] [warn] child process 23980 still did not exit, sending a SIGTERM
[Thu Dec 27 14:25:08 2007] [warn] child process 23982 still did not exit, sending a SIGTERM
[Thu Dec 27 14:25:08 2007] [warn] child process 24033 still did not exit, sending a SIGTERM
[Thu Dec 27 14:25:08 2007] [warn] child process 25998 still did not exit, sending a SIGTERM
[Thu Dec 27 14:25:08 2007] [warn] child process 26174 still did not exit, sending a SIGTERM
[Thu Dec 27 14:25:08 2007] [warn] child process 20870 still did not exit, sending a SIGTERM
[Thu Dec 27 14:25:08 2007] [warn] child process 26175 still did not exit, sending a SIGTERM
[Thu Dec 27 14:25:08 2007] [warn] child process 27683 still did not exit, sending a SIGTERM
[Thu Dec 27 14:25:08 2007] [warn] child process 18135 still did not exit, sending a SIGTERM
[Thu Dec 27 14:25:08 2007] [warn] child process 2503 still did not exit, sending a SIGTERM
[Thu Dec 27 14:25:08 2007] [warn] child process 2504 still did not exit, sending a SIGTERM
[Thu Dec 27 14:25:08 2007] [warn] child process 5697 still did not exit, sending a SIGTERM
[Thu Dec 27 14:25:08 2007] [warn] child process 22615 still did not exit, sending a SIGTERM
[Thu Dec 27 14:25:08 2007] [warn] child process 23189 still did not exit, sending a SIGTERM
[Thu Dec 27 14:25:08 2007] [warn] child process 24106 still did not exit, sending a SIGTERM
[Thu Dec 27 14:25:10 2007] [notice] caught SIGTERM, shutting down
[Thu Dec 27 14:27:51 2007] [notice] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t
[Thu Dec 27 14:27:51 2007] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Thu Dec 27 14:27:52 2007] [notice] Digest: generating secret for digest authentication ...
[Thu Dec 27 14:27:52 2007] [notice] Digest: done
[Thu Dec 27 14:27:52 2007] [notice] mod_python: Creating 4 session mutexes based on 256 max processes and 0 max threads.
[Thu Dec 27 14:27:53 2007] [notice] Apache/2.2.3 (Fedora) configured -- resuming normal operations
[Thu Dec 27 14:30:54 2007] [notice] caught SIGTERM, shutting down
 
Hello,

try running ... /etc/init.d/httpd configtest

And post back what you got.

httpd: Syntax error on line 209 of /etc/httpd/conf/httpd.conf: Syntax error on line 1 of /etc/httpd/conf.d/bw.conf: Cannot load /usr/lib64/httpd/modules/mod_bw.so into server: /usr/lib64/httpd/modules/mod_bw.so: undefined symbol: apr_atomic_cas
 
I have fixed my problem.

I commented out (using #):

#LoadModule bw_module /usr/lib64/httpd/modules/mod_bw.so

in

nano /etc/httpd/conf.d/bw.conf

HTTPD now works.
 
Ah, this mod_bw.so is part of plesks new bandwidth module.
 
it's not httpd

Hi

Thats not the problem
/etc/init.d/httpd configtest
Syntax OK

The site's are online , but plesk don't start , see above ,

any other idea?

thanks
 
the Plesk start issue, the problem was that the RPM package boost was not installed.

Thanks Erik
 
Hi ErikdeEngerd,

Can you please tell me how to solve the "RPM package boost" problem ?
I also have this problem

Starting xinetd service... done
Starting named service... done
Starting mysqld service... done
Starting qmail service... done
Starting courier-imap service... done
Starting postgresql service... done
Starting psa-spamassassin service... done
Starting Plesk... failed
Starting drwebd service... not insalled
 
Back
Top