Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
1
Hello,
I just installed cwp and I can not install clamav.
In the dashbord the status is "activating"
When I try to restart the service I have this message:
Job for clamd.service failed because timeout was exceeded. See "systemctl status clamd.service" and "journalctl -xe" for details.
I just installed cwp and I can not install clamav.
In the dashbord the status is "activating"
When I try to restart the service I have this message:
Job for clamd.service failed because timeout was exceeded. See "systemctl status clamd.service" and "journalctl -xe" for details.
Code: [Select]
[root@server ~]# systemctl status clamd.service
● clamd.service - clamd scanner () daemon
Loaded: loaded (/usr/lib/systemd/system/clamd.service; static; vendor preset: disabled)
Active: activating (start) since ven. 2018-02-02 10:43:13 CET; 12s ago
Control: 1389 (clamd)
CGroup: /system.slice/clamd.service
└─1389 /usr/sbin/clamd -c /etc/clamd.d/amavisd.conf --foreground=...
févr. 02 10:43:23 server.conceptsiteweb.fr clamd[1389]: Portable Executable...
févr. 02 10:43:23 server.conceptsiteweb.fr clamd[1389]: ELF support enabled.
févr. 02 10:43:23 server.conceptsiteweb.fr clamd[1389]: Mail files support ...
févr. 02 10:43:23 server.conceptsiteweb.fr clamd[1389]: OLE2 support enabled.
févr. 02 10:43:23 server.conceptsiteweb.fr clamd[1389]: PDF support enabled.
févr. 02 10:43:23 server.conceptsiteweb.fr clamd[1389]: SWF support enabled.
févr. 02 10:43:23 server.conceptsiteweb.fr clamd[1389]: HTML support enabled.
févr. 02 10:43:23 server.conceptsiteweb.fr clamd[1389]: XMLDOCS support ena...
févr. 02 10:43:23 server.conceptsiteweb.fr clamd[1389]: HWP3 support enabled.
févr. 02 10:43:23 server.conceptsiteweb.fr clamd[1389]: Self checking every...
Hint: Some lines were ellipsized, use -l to show in full.
Vous avez du courrier dans /var/spool/mail/root
Code: [Select]
[root@server ~]# journalctl -xe
févr. 02 10:44:54 server.conceptsiteweb.fr clamd[1639]: Limits: MaxHTMLNoTags limit set to 2097152 bytes.
févr. 02 10:44:54 server.conceptsiteweb.fr clamd[1639]: Limits: MaxScriptNormalize limit set to 5242880 byte
févr. 02 10:44:54 server.conceptsiteweb.fr clamd[1639]: Limits: MaxZipTypeRcg limit set to 1048576 bytes.
févr. 02 10:44:54 server.conceptsiteweb.fr clamd[1639]: Limits: MaxPartitions limit set to 50.
févr. 02 10:44:54 server.conceptsiteweb.fr clamd[1639]: Limits: MaxIconsPE limit set to 100.
févr. 02 10:44:54 server.conceptsiteweb.fr clamd[1639]: Limits: MaxRecHWP3 limit set to 16.
févr. 02 10:44:54 server.conceptsiteweb.fr clamd[1639]: Limits: PCREMatchLimit limit set to 10000.
févr. 02 10:44:54 server.conceptsiteweb.fr clamd[1639]: Limits: PCRERecMatchLimit limit set to 5000.
févr. 02 10:44:54 server.conceptsiteweb.fr clamd[1639]: Limits: PCREMaxFileSize limit set to 26214400.
févr. 02 10:44:54 server.conceptsiteweb.fr clamd[1639]: Archive support enabled.
févr. 02 10:44:54 server.conceptsiteweb.fr clamd[1639]: Algorithmic detection enabled.
févr. 02 10:44:54 server.conceptsiteweb.fr clamd[1639]: Portable Executable support enabled.
févr. 02 10:44:54 server.conceptsiteweb.fr clamd[1639]: ELF support enabled.
févr. 02 10:44:54 server.conceptsiteweb.fr clamd[1639]: Mail files support enabled.
févr. 02 10:44:54 server.conceptsiteweb.fr clamd[1639]: OLE2 support enabled.
févr. 02 10:44:54 server.conceptsiteweb.fr clamd[1639]: PDF support enabled.
févr. 02 10:44:54 server.conceptsiteweb.fr clamd[1639]: SWF support enabled.
févr. 02 10:44:54 server.conceptsiteweb.fr clamd[1639]: HTML support enabled.
févr. 02 10:44:54 server.conceptsiteweb.fr clamd[1639]: XMLDOCS support enabled.
févr. 02 10:44:54 server.conceptsiteweb.fr clamd[1639]: HWP3 support enabled.
févr. 02 10:44:54 server.conceptsiteweb.fr clamd[1639]: Self checking every 600 seconds.
févr. 02 10:45:01 server.conceptsiteweb.fr systemd[1]: Started Session 93 of user root.
-- Subject: L'unité (unit) session-93.scope a terminé son démarrage
2
Installation / Varnish
« on: December 21, 2017, 09:45:45 AM »
Hello,
From the CWP7 interface I installed Apache & Varnish Cache & Nginx Reverse Proxy but in the dashbord, I visualize a status failled.
If I try to start it I have the following error:
Job for varnish.service failed because the control process is exited with error code. See "systemctl status varnish.service" and "journalctl -xe" for details.
[root@vps44154 ~]# systemctl status varnish.service
● varnish.service - Varnish Cache, a high-performance HTTP accelerator
Loaded: loaded (/usr/lib/systemd/system/varnish.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since jeu. 2017-12-21 04:42:33 EST; 1min 35s ago
Process: 17293 ExecStart=/usr/sbin/varnishd -P /var/run/varnish.pid -f $VARNISH_VCL_CONF -a ${VARNISH_LISTEN_ADDRESS}:${VARNISH_LISTEN_PORT} -T ${VARNISH_ADMIN_LISTEN_ADDRESS}:${VARNISH_ADMIN_LISTEN_PORT} -S $VARNISH_SECRET_FILE -s $VARNISH_STORAGE $DAEMON_OPTS (code=exited, status=2)
déc. 21 04:42:33 vps44154 varnishd[17293]: },
déc. 21 04:42:33 vps44154 varnishd[17294]: Child (17304) Panic at: Thu, 21 Dec 2017 09:42:33 GMT
Assert error in MPL_New(), cache/cache_mempool.c line 244:
Condition((pthread_create(&mpl->thread, ((void *)0), mpl_guard, mpl)) == 0) not true....
déc. 21 04:42:33 vps44154 varnishd[17294]: Child (17304) said Child starts
déc. 21 04:42:33 vps44154 varnishd[17293]: Info: Child (17304) said Child starts
déc. 21 04:42:33 vps44154 varnishd[17293]: Debug: Child cleanup complete
déc. 21 04:42:33 vps44154 varnishd[17294]: Child cleanup complete
déc. 21 04:42:33 vps44154 systemd[1]: varnish.service: control process exited, code=exited status=2
déc. 21 04:42:33 vps44154 systemd[1]: Failed to start Varnish Cache, a high-performance HTTP accelerator.
déc. 21 04:42:33 vps44154 systemd[1]: Unit varnish.service entered failed state.
déc. 21 04:42:33 vps44154 systemd[1]: varnish.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
From the CWP7 interface I installed Apache & Varnish Cache & Nginx Reverse Proxy but in the dashbord, I visualize a status failled.
If I try to start it I have the following error:
Job for varnish.service failed because the control process is exited with error code. See "systemctl status varnish.service" and "journalctl -xe" for details.
[root@vps44154 ~]# systemctl status varnish.service
● varnish.service - Varnish Cache, a high-performance HTTP accelerator
Loaded: loaded (/usr/lib/systemd/system/varnish.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since jeu. 2017-12-21 04:42:33 EST; 1min 35s ago
Process: 17293 ExecStart=/usr/sbin/varnishd -P /var/run/varnish.pid -f $VARNISH_VCL_CONF -a ${VARNISH_LISTEN_ADDRESS}:${VARNISH_LISTEN_PORT} -T ${VARNISH_ADMIN_LISTEN_ADDRESS}:${VARNISH_ADMIN_LISTEN_PORT} -S $VARNISH_SECRET_FILE -s $VARNISH_STORAGE $DAEMON_OPTS (code=exited, status=2)
déc. 21 04:42:33 vps44154 varnishd[17293]: },
déc. 21 04:42:33 vps44154 varnishd[17294]: Child (17304) Panic at: Thu, 21 Dec 2017 09:42:33 GMT
Assert error in MPL_New(), cache/cache_mempool.c line 244:
Condition((pthread_create(&mpl->thread, ((void *)0), mpl_guard, mpl)) == 0) not true....
déc. 21 04:42:33 vps44154 varnishd[17294]: Child (17304) said Child starts
déc. 21 04:42:33 vps44154 varnishd[17293]: Info: Child (17304) said Child starts
déc. 21 04:42:33 vps44154 varnishd[17293]: Debug: Child cleanup complete
déc. 21 04:42:33 vps44154 varnishd[17294]: Child cleanup complete
déc. 21 04:42:33 vps44154 systemd[1]: varnish.service: control process exited, code=exited status=2
déc. 21 04:42:33 vps44154 systemd[1]: Failed to start Varnish Cache, a high-performance HTTP accelerator.
déc. 21 04:42:33 vps44154 systemd[1]: Unit varnish.service entered failed state.
déc. 21 04:42:33 vps44154 systemd[1]: varnish.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
Pages: [1]
