Fixed in https://github.com/i-MSCP/imsc…261cbe65bcd5386bd35393eb0
Please, just replace the remove() method by delFile() were appropriate in your current version. The Try/Catch are not available in latest released version.
Posts by Nuxwin
-
-
Ok, I did just check. The bug is in i-MSCP core (iMSCP::Service library).
should be
Basically put, that's not a bug from the PhpSwitcher plugin. That's a bug in the IMSCP::Service core library. Just edit that file and change the method as showed above, then retry. You need edit the file inside the archive directory: engine/PerlLib/iMSCP/Service.pm. As I see, there is two lines with that bug:
- https://github.com/i-MSCP/imsc…Lib/iMSCP/Service.pm#L136
- https://github.com/i-MSCP/imsc…Lib/iMSCP/Service.pm#L145
This bug will be fixed in next maintenance release. Thank you for your report.
-
Hat den bitte keiner eine idee?
That look like a bug... There is not remove() method in the iMSCP::File library (core). The method should be delFile(). I'll check.
Please say us the version of your PhpSwitcher plugin.
-
-
If you make a dist upgrade as stated in my previous answer this should solve the problem. The is-enabled API support for SysVinit scripts has been added lately in Debian Jessie systemd package:
Display MoreCode- systemd (215-17+deb8u7) stable; urgency=medium
- * bus: Fix bus_print_property() to use "int" for booleans.
- This fixes the problem that on big endian architectures, like mips or
- powerpc, boolean properties that were retrieved via sd-bus were always
- set to 0 (no). (Closes: #774430)
- * systemctl: Add is-enabled support for SysV init scripts.
- The update-rc.d utility does not provide is-enabled, so implement it
- ourselves in systemctl using the same logic as systemd-sysv-install from
- Stretch. (Closes: #809405)
- * core: If the start command vanishes during runtime don't hit an assert.
- This can happen when the configuration is changed and reloaded while we
- are executing a service. Let's not hit an assert in this case.
- (Closes: #856985)
- * automount: If an automount unit is masked, don't react to activation
- anymore.
- Otherwise we'll hit an assert sooner or later. (Closes: #856035)
- -- Michael Biebl <biebl@debian.org> Fri, 10 Mar 2017 06:02:49 +0100
Basically put, you have an older version of the systemd package.
Don't forget for the furture: Before updating i-MSCP, you need always update your system, as stated in the documentation.
Latest systemd package under Jessie is:
Shell-Script- root@jessie64:/usr/local/src/systemd/systemd-215/debian# LANG=C apt-cache policy systemd
- systemd:
- Installed: 215-17+deb8u8
- Candidate: 215-17+deb8u8
- Version table:
- *** 215-17+deb8u8 0
- 500 http://security.debian.org/ jessie/updates/main amd64 Packages
- 100 /var/lib/dpkg/status
- 215-17+deb8u7 0
- 500 http://deb.debian.org/debian/ jessie/main amd64 Packages
-
I cannot reproduce the issue.
Distribution version
Systemd version
The part which should fails
Shell-Script- ...
- [DEBUG] iMSCP::DbTasksProcessor::processDbTasks: Processing Modules::ServerIP tasks...
- [DEBUG] iMSCP::DbTasksProcessor::processDbTasks: Processing Modules::ServerIP tasks for: 192.168.1.133 (ID 1)
- [DEBUG] iMSCP::Execute::execute: /bin/systemctl is-enabled networking
- [DEBUG] iMSCP::Provider::Service::Abstract::_exec: enabled
- [DEBUG] iMSCP::DbTasksProcessor::processDbTasks: Processing Modules::ServerIP tasks for: 192.168.1.134 (ID 2)
- [DEBUG] iMSCP::Execute::execute: ip addr del 192.168.1.134/24 dev eth0
- [DEBUG] iMSCP::Execute::execute: ip -4 addr add 192.168.1.134/24 dev eth0
- ...
So please first, upgrade your system. Latest Debian Jessie is 8.11, not 8.7.
Once done, retry. If after that the problem still occurs, you'll have to provide me a access to the server for further investigation.
-
Re,
There is no missing file... I'll make a test on Debian Jessie. As I suspect, systemd version from jessie is not able to say if one service is enabled when only the sysvinit script is provided. Give me some minutes to investigate please.
-
I don't know if its a bug, or was just a problem on our side with the not removed mysql entry from the not needed ssl cert after removing the corresponding domain, so I thought I give the answer here aswell.
Read my previous answer. Basically put, SQL query to remove orphaned SSL cert was wrong. This bug has been fixed as already stated. You need update your i-MSCP instance.
-
Good evening,
That would be great if you followed our reporting rules which are available at Reporting rules - Reminder
That would be also even better if you updated your i-MSCP installation prior reporting a bug which has been already fixed. As the error say, this has nothing to do with the LetsEncrypt plugin.
You need update to latest released version: i-MSCP 1.5.3 (build 2018120800) RELEASED
Thread closed.
See also:
-
Fixed through online support.