So "perl imscp-autoinstall -d"? (Or is there a better/specific command)
Posts by Heart1010
-
-
After editing /etc/imscp/php/php.data file which imscp command I have to call so the new settings take effect?
-
...wird wohl auf i-MSCP >= 1.3.1 and PHP opcache - Unable to allocate shared memory segment zurückzuführen gewesen sein.
-
Have you tried to use 127.0.0.1 as hostname in the installer when asked (instead of deafult localhost)?
-
My Server uptime was ~500 days.... I rebooted the server and tried again to update and now it was successful. Strange.
-
..added missing information in #1.
Here is the output of # php5-fpm -i | grep 'apc'
Display MoreCode- # php5-fpm -i | grep 'apc'
- /etc/php5/fpm/conf.d/20-apcu.ini,
- apc
- apcu
- apc.coredump_unmap => Off => Off
- apc.enable_cli => Off => Off
- apc.enabled => On => On
- apc.entries_hint => 4096 => 4096
- apc.gc_ttl => 3600 => 3600
- apc.mmap_file_mask => no value => no value
- apc.preload_path => no value => no value
- apc.rfc1867 => Off => Off
- apc.rfc1867_freq => 0 => 0
- apc.rfc1867_name => APC_UPLOAD_PROGRESS => APC_UPLOAD_PROGRESS
- apc.rfc1867_prefix => upload_ => upload_
- apc.rfc1867_ttl => 3600 => 3600
- apc.serializer => php => php
- apc.shm_segments => 1 => 1
- apc.shm_size => 256M => 256M
- apc.slam_defense => On => On
- apc.smart => 0 => 0
- apc.ttl => 0 => 0
- apc.use_request_time => On => On
- apc.writable => /tmp => /tmp
-
Hallo,
I'm updating to 1.3.1 and at the end of this update process I get this error:
Code- [ERROR] │ │ │ │ Error while performing step: │ │ │ │ Processing setup tasks │ │ │ │ Error was: │ │ │ │ Servers::httpd::apache_php_fpm::start: Could not start the php5-fpm service: iMSCP::Provider::Service::Sysvinit::_exec: Job for │ │ php5-fpm.service failed. See 'systemctl status php5-fpm.service' and 'journalctl -xn' for details. at │ │ /usr/local/src/imscp/imscp-1.3.1/engine/PerlLib/iMSCP/Service.pm line 158. │ │ │ │ Please have a look at http://i-mscp.net/forum if you need help.
journalctl -xn output:Code- -- Logs begin at Di 2016-09-13 15:13:43 CEST, end at Mi 2016-09-14 14:26:48 CEST. --Sep 14 14:26:48 vsrv58002 systemd[1]: Started LSB: Starts ProFTPD daemon.-- Subject: Unit proftpd.service has finished start-up-- Defined-By: systemd-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel---- Unit proftpd.service has finished starting up.---- The start-up result is done.Sep 14 14:26:48 vsrv58002 proftpd[15648]: 31.15.64.125 - ProFTPD 1.3.5 (stable) (built Tue May 19 2015 11:09:58 UTC) standalone mode STARTUPSep 14 14:26:48 vsrv58002 systemd[1]: Starting The PHP FastCGI Process Manager...-- Subject: Unit php5-fpm.service has begun with start-up-- Defined-By: systemd-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel---- Unit php5-fpm.service has begun starting up.Sep 14 14:26:48 vsrv58002 kernel: php5-fpm[15653]: segfault at ffffffffffffffff ip 00007f7909df974c sp 00007ffd8b22a248 error 7 in libpthread-2.Sep 14 14:26:48 vsrv58002 php5-fpm-checkconf[15651]: Segmentation faultSep 14 14:26:48 vsrv58002 php5-fpm[15655]: [14-Sep-2016 14:26:48] NOTICE: PHP message: PHP Fatal error: PHP Startup: apc_mmap: mmap failed: inSep 14 14:26:48 vsrv58002 kernel: php5-fpm[15655]: segfault at ffffffffffffffff ip 00007f15e6d6474c sp 00007ffef708dbe8 error 7 in libpthread-2.Sep 14 14:26:48 vsrv58002 systemd[1]: php5-fpm.service: main process exited, code=killed, status=11/SEGVSep 14 14:26:48 vsrv58002 systemd[1]: Failed to start The PHP FastCGI Process Manager.-- Subject: Unit php5-fpm.service has failed-- Defined-By: systemd
When I manually stop php5-fpm service and start it again, it works. But I still get this error when I try to update imscp to 1.3.1
Display MoreCode- # service php5-fpm stop
- # service php5-fpm start
- # systemctl status php5-fpm.service
- ● php5-fpm.service - The PHP FastCGI Process Manager
- Loaded: loaded (/lib/systemd/system/php5-fpm.service; enabled)
- Active: active (running) since Mi 2016-09-14 14:30:37 CEST; 4s ago
- Process: 15773 ExecStartPre=/usr/lib/php5/php5-fpm-checkconf (code=exited, status=0/SUCCESS)
- Main PID: 15777 (php5-fpm)
- Status: "Ready to handle connections"
- CGroup: /system.slice/php5-fpm.service
- └─15777 php-fpm: master process (/etc/php5/fpm/php-fpm.conf)
- Sep 14 14:30:37 vsrv***2 systemd[1]: Started The PHP FastCGI Process Manager.
Debian Jessie 8.5
PHP 5.6.24-0+deb8u1 (cli) (built: Jul 26 2016 08:17:07) -
Tested the updated fail2ban jail.local from the wiki and getting these errors.
Are there filters missing in filter.d folder for ngix-*?Display MoreShell-Script- # service fail2ban status
- Jun 16 09:03:38 vsrv58002 fail2ban[1839]: ERROR Unable to read the filter
- Jun 16 09:03:38 vsrv58002 fail2ban[1839]: ERROR Errors in jail 'imscp-noscript'. Skipping...
- Jun 16 09:03:38 vsrv58002 fail2ban[1839]: WARNING 'usedns' not defined in 'imscp-overflows'. Using default one: 'warn'
- Jun 16 09:03:38 vsrv58002 fail2ban[1839]: ERROR Found no accessible config files for 'filter.d/nginx-overflows' under /etc/fail2ban
- Jun 16 09:03:38 vsrv58002 fail2ban[1839]: ERROR Unable to read the filter
- Jun 16 09:03:38 vsrv58002 fail2ban[1839]: ERROR Errors in jail 'imscp-overflows'. Skipping...
- Jun 16 09:03:38 vsrv58002 fail2ban[1839]: WARNING 'usedns' not defined in 'roundcube'. Using default one: 'warn'
- Jun 16 09:03:38 vsrv58002 fail2ban[1839]: WARNING 'usedns' not defined in 'rainloop'. Using default one: 'warn'
- Jun 16 09:03:38 vsrv58002 fail2ban[1839]: failed!
- Jun 16 09:03:38 vsrv58002 systemd[1]: Started LSB: Start/stop fail2ban.
-
-
1.2.2 at the moment... you're right, waiting for 1.2.3 is a good idea (so jessie specific things are already present when running the autoinstaller...)