Posts by symphosius

symphosius · Apr 4th 2017

Code

[ERROR] main::setupDbTasks: iMSCP::Stepper::_callback: Couldn't bring up the `eth0:1012' network interface: RTNETLINK answers: File exists at /usr/local/src/imscp-1.4.2/engine/PerlLib/iMSCP/Provider/NetworkInterface/Debian.pm line 101.
[ERROR] autoinstaller::Functions::install: An error occurred while performing installation steps
root@alpha:/usr/local/src/imscp-1.4.2#
root@alpha:/usr/local/src/imscp-1.4.2# ifconfig
eth0 Link encap:Ethernet HWaddr 4c:cc:6a:89:03:a6
inet addr:84.200.83.93 Bcast:84.200.83.255 Mask:255.255.255.0
inet6 addr: fe80::4ecc:6aff:fe89:3a6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5247744 errors:0 dropped:0 overruns:0 frame:0
TX packets:110388 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:496473759 (496.4 MB) TX bytes:16992248 (16.9 MB)
eth0:1012 Link encap:Ethernet HWaddr 4c:cc:6a:89:03:a6
inet addr:84.200.210.107 Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
eth0:1013 Link encap:Ethernet HWaddr 4c:cc:6a:89:03:a6
inet addr:84.200.210.108 Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
eth0:1014 Link encap:Ethernet HWaddr 4c:cc:6a:89:03:a6
inet addr:84.200.210.93 Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
eth0:1015 Link encap:Ethernet HWaddr 4c:cc:6a:89:03:a6
inet addr:84.200.210.92 Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:3746 errors:0 dropped:0 overruns:0 frame:0
TX packets:3746 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:647136 (647.1 KB) TX bytes:647136 (647.1 KB)
root@alpha:/usr/local/src/imscp-1.4.2#

Display More

symphosius · Apr 4th 2017

Code

Error while performing step: │
│ │
│ Processing setup tasks │
│ │
│ Error was: │
│ │
│ main::setupDbTasks: iMSCP::Stepper::_callback: Couldn't bring up the `eth0:1012' network interface: RTNETLINK answers: File exists at │
│ /usr/local/src/imscp-1.4.2/engine/PerlLib/iMSCP/Provider/NetworkInterface/Debian.pm line 101.

Server: Ubuntu 16.04 LTS

Looking at Debian.pm at Line 101 didn't tell me which file is addressed by this error. My server isn't reachable via http any more and downgrade to 1.3.16 is not supported. So how to finish the upgrade to 1.4.2 to get http up again?

symphosius · Jan 5th 2017

Thank you, I will stay on i-MSCP - managed interfaces.

symphosius · Jan 5th 2017

Thanks a lot, Nuxwin! My provider didn't solve the Problem, passed it over to i-MSCP forum. I don't know, what they tried out, but at least they told me it might be better, not to handle the network-interfaces by i-MSCP, using the 'manual' option. Do you think that's a good idea?

symphosius · Jan 5th 2017

ok, thank you!

symphosius · Jan 5th 2017

you got mail

symphosius · Jan 5th 2017

here it is:

Code

/etc/network/interfaces 788/788 100%
# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d
# i-MSCP [84.200.210.108] entry BEGIN
auto eth0:1013
iface eth0:1013 inet static
address 84.200.210.108
netmask 32
# i-MSCP [84.200.210.108] entry ENDING
# i-MSCP [84.200.210.93] entry BEGIN
auto eth0:1014
iface eth0:1014 inet static
address 84.200.210.93
netmask 32
# i-MSCP [84.200.210.93] entry ENDING
# i-MSCP [84.200.210.92] entry BEGIN
auto eth0:1015
iface eth0:1015 inet static
address 84.200.210.92
netmask 32
# i-MSCP [84.200.210.92] entry ENDING
# i-MSCP [84.200.210.107] entry BEGIN
auto eth0:1012
iface eth0:1012 inet static
address 84.200.210.107
netmask 32
# i-MSCP [84.200.210.107] entry ENDING

Display More

I did'nt configure any interface manually.

symphosius · Jan 5th 2017

The script is running into this Error(s):

Code

[ERROR] │ │ │ │ Error while performing step: │ │ │ │ Processing Modules::NetworkInterfaces (any) tasks for: network interfaces (ID all) │ │ │ │ Error was: │ │ │ │ iMSCP::Stepper::_callback: Could not bring up the `eth0:1012' network interface: RTNETLINK answers: File exists at │ │ /usr/local/src/imscp-1.3.15/engine/PerlLib/iMSCP/Provider/NetworkInterface/Debian.pm line 94. [ERROR] │ │ │ │ Error while performing step: │ │ │ │ Processing DB tasks │ │ │ │ Error was: │ │ │ │ main::setupDbTasks: iMSCP::Stepper::_callback: Could not bring up the `eth0:1012' network interface: RTNETLINK answers: File exists at │ │ /usr/local/src/imscp-1.3.15/engine/PerlLib/iMSCP/Provider/NetworkInterface/Debian.pm line 94. [ERROR] │ │ │ │ Error while performing step: │ │ │ │ Processing setup tasks │ │ │ │ Error was: │ │ │ │ main::setupDbTasks: iMSCP::Stepper::_callback: Could not bring up the `eth0:1012' network interface: RTNETLINK answers: File exists at │ │ /usr/local/src/imscp-1.3.15/engine/PerlLib/iMSCP/Provider/NetworkInterface/Debian.pm line 94.

the output of systemctl status apache2.service:

Code

apache2.service - LSB: Apache2 web server
Loaded: loaded (/etc/init.d/apache2; bad; vendor preset: enabled)
Drop-In: /lib/systemd/system/apache2.service.d
└─apache2-systemd.conf
Active: failed (Result: exit-code) since Thu 2017-01-05 18:32:38 CET; 37s ago
Docs: man:systemd-sysv-generator(8)
Process: 11447 ExecStart=/etc/init.d/apache2 start (code=exited, status=1/FAILURE)
Jan 05 18:32:38 alpha apache2[11447]: Output of config test was:
Jan 05 18:32:38 alpha apache2[11447]: [Thu Jan 05 18:32:38.612136 2017] [alias:warn] [pid 11456:tid 140439330649984] AH00671: The Alias directive in /etc/ap
Jan 05 18:32:38 alpha apache2[11447]: AH00526: Syntax error on line 38 of /etc/apache2/sites-enabled/symphosius.de_ssl.conf:
Jan 05 18:32:38 alpha apache2[11447]: SSLCertificateFile: file '/var/www/imscp/gui/data/certs/symphosius.de.pem' does not exist or is empty
Jan 05 18:32:38 alpha apache2[11447]: Action 'configtest' failed.
Jan 05 18:32:38 alpha apache2[11447]: The Apache error log may have more information.
Jan 05 18:32:38 alpha systemd[1]: apache2.service: Control process exited, code=exited status=1
Jan 05 18:32:38 alpha systemd[1]: Failed to start LSB: Apache2 web server.
Jan 05 18:32:38 alpha systemd[1]: apache2.service: Unit entered failed state.
Jan 05 18:32:38 alpha systemd[1]: apache2.service: Failed with result 'exit-code'.

Display More

The Server is reachable via SSH, how to get the apache runnig again?

symphosius · Sep 7th 2014

Thank You!

symphosius · Sep 6th 2014

Hi Folks,

I want to allow Directrory Listing only for one dedicatet Directory in a Subdomain, treated by I-MSCP, but I cannot find how to manage that in I-MSCP. If I-MSCP does not offer this option, which way should I prefer, not to run into conflicts with I-MSCP?

Posts by symphosius

Update from 1.3.16 to 1.4.2 failed

Update from 1.3.16 to 1.4.2 failed

Update 1.3.14 to 1.3.15 - Could not bring up the `eth0:1012' network interface

Update 1.3.14 to 1.3.15 - Could not bring up the `eth0:1012' network interface

Update 1.3.14 to 1.3.15 - Could not bring up the `eth0:1012' network interface

Update 1.3.14 to 1.3.15 - Could not bring up the `eth0:1012' network interface

Update 1.3.14 to 1.3.15 - Could not bring up the `eth0:1012' network interface

Update 1.3.14 to 1.3.15 - Could not bring up the `eth0:1012' network interface

how to allow Directory Listing

how to allow Directory Listing