Centos 7 Openvz install problem

Hello,

Hi, i have this error? have any idea?

the web panel does not open. It's a 503 error. I've reinstalled it many times.

Eyl 20 15:25:49 server.fazli.com systemd[1]: Started gunicorn daemon.
-- Subject: Unit gunicorn.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit gunicorn.service has finished starting up.
--
-- The start-up result is done.
Eyl 20 15:25:49 server.fazli.com systemd[1]: Starting gunicorn daemon...
-- Subject: Unit gunicorn.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit gunicorn.service has begun starting up.
Eyl 20 15:25:49 server.fazli.com systemd[18440]: Failed at step EXEC spawning /usr/local/CyberCP/bin/gunicorn: No such file or directory
-- Subject: Process /usr/local/CyberCP/bin/gunicorn could not be executed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The process /usr/local/CyberCP/bin/gunicorn could not be executed and failed.
--
-- The error number returned by this process is 2.
Eyl 20 15:25:49 server.fazli.com systemd[1]: gunicorn.service: main process exited, code=exited, status=203/EXEC
Eyl 20 15:25:49 server.fazli.com kill[18442]: Usage:
Eyl 20 15:25:49 server.fazli.com kill[18442]: kill [options] [...]
Eyl 20 15:25:49 server.fazli.com kill[18442]: Options:
Eyl 20 15:25:49 server.fazli.com kill[18442]: -a, --all do not restrict the name-to-pid conversion to processes
Eyl 20 15:25:49 server.fazli.com kill[18442]: with the same uid as the present process
Eyl 20 15:25:49 server.fazli.com kill[18442]: -s, --signal send specified signal
Eyl 20 15:25:49 server.fazli.com kill[18442]: -q, --queue use sigqueue(2) rather than kill(2)
Eyl 20 15:25:49 server.fazli.com kill[18442]: -p, --pid print pids without signaling them
Eyl 20 15:25:49 server.fazli.com kill[18442]: -l, --list [=] list signal names, or convert one to a name
Eyl 20 15:25:49 server.fazli.com kill[18442]: -L, --table list signal names and numbers
Eyl 20 15:25:49 server.fazli.com kill[18442]: -h, --help display this help and exit
Eyl 20 15:25:49 server.fazli.com kill[18442]: -V, --version output version information and exit
Eyl 20 15:25:49 server.fazli.com kill[18442]: For more details see kill(1).
Eyl 20 15:25:49 server.fazli.com systemd[1]: gunicorn.service: control process exited, code=exited status=1
Eyl 20 15:25:49 server.fazli.com systemd[1]: Unit gunicorn.service entered failed state.
Eyl 20 15:25:49 server.fazli.com systemd[1]: gunicorn.service failed.
Eyl 20 15:25:49 server.fazli.com systemd[1]: Started gunicorn daemon.
-- Subject: Unit gunicorn.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit gunicorn.service has finished starting up.
--
-- The start-up result is done.
Eyl 20 15:25:49 server.fazli.com systemd[1]: Starting gunicorn daemon...
-- Subject: Unit gunicorn.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit gunicorn.service has begun starting up.
Eyl 20 15:25:49 server.fazli.com systemd[18447]: Failed at step EXEC spawning /usr/local/CyberCP/bin/gunicorn: No such file or directory
-- Subject: Process /usr/local/CyberCP/bin/gunicorn could not be executed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The process /usr/local/CyberCP/bin/gunicorn could not be executed and failed.
--
-- The error number returned by this process is 2.
Eyl 20 15:25:49 server.fazli.com systemd[1]: gunicorn.service: main process exited, code=exited, status=203/EXEC
Eyl 20 15:25:49 server.fazli.com kill[18449]: Usage:
Eyl 20 15:25:49 server.fazli.com kill[18449]: kill [options] [...]
Eyl 20 15:25:49 server.fazli.com kill[18449]: Options:
Eyl 20 15:25:49 server.fazli.com kill[18449]: -a, --all do not restrict the name-to-pid conversion to processes
Eyl 20 15:25:49 server.fazli.com kill[18449]: with the same uid as the present process
Eyl 20 15:25:49 server.fazli.com kill[18449]: -s, --signal send specified signal
Eyl 20 15:25:49 server.fazli.com kill[18449]: -q, --queue use sigqueue(2) rather than kill(2)
Eyl 20 15:25:49 server.fazli.com kill[18449]: -p, --pid print pids without signaling them
Eyl 20 15:25:49 server.fazli.com kill[18449]: -l, --list [=] list signal names, or convert one to a name
Eyl 20 15:25:49 server.fazli.com kill[18449]: -L, --table list signal names and numbers
Eyl 20 15:25:49 server.fazli.com kill[18449]: -h, --help display this help and exit
Eyl 20 15:25:49 server.fazli.com kill[18449]: -V, --version output version information and exit
Eyl 20 15:25:49 server.fazli.com kill[18449]: For more details see kill(1).
Eyl 20 15:25:49 server.fazli.com systemd[1]: gunicorn.service: control process exited, code=exited status=1
Eyl 20 15:25:49 server.fazli.com systemd[1]: Unit gunicorn.service entered failed state.
Eyl 20 15:25:49 server.fazli.com systemd[1]: gunicorn.service failed.
Eyl 20 15:25:49 server.fazli.com systemd[1]: Started gunicorn daemon.
-- Subject: Unit gunicorn.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit gunicorn.service has finished starting up.
--
-- The start-up result is done.
Eyl 20 15:25:49 server.fazli.com systemd[1]: Starting gunicorn daemon...
-- Subject: Unit gunicorn.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit gunicorn.service has begun starting up.
Eyl 20 15:25:49 server.fazli.com systemd[18454]: Failed at step EXEC spawning /usr/local/CyberCP/bin/gunicorn: No such file or directory

Comments

  • GNU nano 2.3.1 File: /var/log/installLogs.txt

    [04-36-51-Thu-Sep-2018] Successfully extracted CyberPanel!
    [04-36-51-Thu-Sep-2018] Updating settings.py!
    [04-36-51-Thu-Sep-2018] settings.py updated!
    [04-36-52-Thu-Sep-2018] Successfully prepared migrations file!
    [04-36-55-Thu-Sep-2018] Migrations file successfully executed!
    [04-36-55-Thu-Sep-2018] Static content moved!
    [04-36-55-Thu-Sep-2018] Permissions successfully changed for '/usr/local/CyberCP'
    [04-36-55-Thu-Sep-2018] Owner for '/usr/local/CyberCP' successfully changed!
    [04-36-55-Thu-Sep-2018] CLI setup successfull!
    [04-36-57-Thu-Sep-2018] Cronie successfully installed!
    [04-36-58-Thu-Sep-2018] Cronie successfully enabled at system startup!
    [04-36-58-Thu-Sep-2018] Crond successfully started!
    [04-36-58-Thu-Sep-2018] Crond successfully restarted!
    [04-36-59-Thu-Sep-2018] tldextract successfully installed! [pip]
    [04-37-03-Thu-Sep-2018] Succcessfully installed opendkim!
    [04-37-12-Thu-Sep-2018] Project dependant modules installed successfully!
    [04-37-13-Thu-Sep-2018] virtualenv installed successfully!
    [04-37-16-Thu-Sep-2018] virtualenv setuped successfully!
    [04-37-34-Thu-Sep-2018] Failed to install project dependant modules! [setupVirtualEnv]
    [04-37-38-Thu-Sep-2018] CyberPanel installation successfully completed!
  • You installed on Centos 7 minimal?
  • edited November 15
    I'm having the same problem and it's still not solved. DigitalOcean and VirtualBox even the same (VirtualBox can activate on the update before arriving)

    @usmannasir @CyberPanel
Sign In or Register to comment.
Support CyberPanel CyberPanel Discord

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!