• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved Error systemctl restart network

Branko

Branko

Basic Pleskian
Hello,

When I try to systemctl restart network the following error pops up
Job for network.service failed because the control process exited with error code. See "systemctl status network.service" and "journalctl -xe" for details.

After systemctl status network.service there is

● network.service - LSB: Bring up/down networking
Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2017-09-22 14:37:30 CEST; 1min 5s ago
Docs: man:systemd-sysv-generator(8)
Process: 14068 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)
Memory: 21.7M
CGroup: /system.slice/network.service
└─7380 /sbin/dhclient -1 -q -lf /var/lib/dhclient/dhclient--eth0.l...

Sep 22 14:37:30 web.lifecorporate.com network[14068]: RTNETLINK answers: File...
Sep 22 14:37:30 web.lifecorporate.com network[14068]: RTNETLINK answers: File...
Sep 22 14:37:30 web.lifecorporate.com network[14068]: RTNETLINK answers: File...
Sep 22 14:37:30 web.lifecorporate.com network[14068]: RTNETLINK answers: File...
Sep 22 14:37:30 web.lifecorporate.com network[14068]: RTNETLINK answers: File...
Sep 22 14:37:30 web.lifecorporate.com network[14068]: RTNETLINK answers: File...
Sep 22 14:37:30 web.lifecorporate.com systemd[1]: network.service: control pr...
Sep 22 14:37:30 web.lifecorporate.com systemd[1]: Failed to start LSB: Bring ...
Sep 22 14:37:30 web.lifecorporate.com systemd[1]: Unit network.service entere...
Sep 22 14:37:30 web.lifecorporate.com systemd[1]: network.service failed.
Hint: Some lines were ellipsized, use -l to show in full.

It all happened after trrying to setup IPv6 on my VPS server.

Content in /etc/sysconfig/network-scripts/ifcfg-eth0 is


DEVICE="eth0"
ONBOOT=yes
NETBOOT=yes
IPV6INIT=yes
IPV6_DEFAULTGW=fe80::1
IPV6_DEFAULTDEV=eth0
BOOTPROTO=dhcp
TYPE=Ethernet
NAME="eth0"
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
PEERDNS=yes
PEERROUTES=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPV6ADDR_SECONDARIES="2001:1af8:4700:a121:1200::5/128 2001:1af8:4700:a121:1200:$$:1200::4/128 2001:1af8:4700:a121:1200::3/128 2001:1af8:4700:a121:1200::2/128 2$$/128 2001:1af8:4700:a121:1200::1/128"


Also tried stoping and starting NetworkManager but there is error
Failed to start NetworkManager.service: Unit not found.

Every response is highly appreciated, thank you ina advance.

Must note that my server is up and running, and network is avaliable. As I can tell everything is functioning good.
 
Hi Branko,

to investigate issues/errors/problems, it is always wise to add:
  • YOUR current used operating system
  • YOUR current used Plesk version ( incl. # MU )

The more information you add, the better might be ( possible ) solutions and work-arounds, to solve your issue.

Unfortunately, you shortened your error - messages, so that we are not able to see the full messages. :(
Hint: Some lines were ellipsized, use -l to show in full.
Click to expand...

Branko said:
Also tried stoping and starting NetworkManager but there is error
Failed to start NetworkManager.service: Unit not found.
Click to expand...
No informations about: => "systemctl status NetworkManager.service" / "journalctl -xe" ?
 
Hello UFHH01, thank you for answering, and sorry for my delay.
I've been on a little vacation.

I will give you soon detailed information.
 
Hello, here goes some more info:

Version: Plesk Onyx v17.5.3_build1705170317.16 os_CentOS 7
OS: CentOS Linux 7.4.1708 (Core)

For systemctl status network.service -l there is

● network.service - LSB: Bring up/down networking
Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2017-10-18 17:24:32 CEST; 6min ago
Docs: man:systemd-sysv-generator(8)
Process: 559 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)
Memory: 21.7M
CGroup: /system.slice/network.service
└─798 /sbin/dhclient -1 -q -lf /var/lib/dhclient/dhclient--eth0.lease -pf /var/run/dhclient-eth0.pid -H web eth0

Oct 18 17:24:32 web.lifecorporate.com network[559]: it work better with this distribution.
Oct 18 17:24:32 web.lifecorporate.com network[559]: Please report for this software via the CentOS Bugs Database:
Oct 18 17:24:32 web.lifecorporate.com network[559]: My View - CentOS Bug Tracker
Oct 18 17:24:32 web.lifecorporate.com network[559]: exiting.
Oct 18 17:24:32 web.lifecorporate.com network[559]: failed.
Oct 18 17:24:32 web.lifecorporate.com network[559]: [FAILED]
Oct 18 17:24:32 web.lifecorporate.com systemd[1]: network.service: control process exited, code=exited status=1
Oct 18 17:24:32 web.lifecorporate.com systemd[1]: Failed to start LSB: Bring up/down networking.
Oct 18 17:24:32 web.lifecorporate.com systemd[1]: Unit network.service entered failed state.
Oct 18 17:24:32 web.lifecorporate.com systemd[1]: network.service failed


And for journalctl -xe

Support: systemd-devel Info Page
--
-- Unit session-5.scope has finished starting up.
--
-- The start-up result is done.
Oct 18 17:35:01 web.lifecorporate.com systemd[1]: Starting Session 5 of user root.
-- Subject: Unit session-5.scope has begun start-up
-- Defined-By: systemd
-- Support: systemd-devel Info Page
--
-- Unit session-5.scope has begun starting up.
Oct 18 17:35:01 web.lifecorporate.com CROND[3613]: (root) CMD (/var/asl/bin/asl --rep_report >/dev/null 2>&1)
Oct 18 17:35:35 web.lifecorporate.com postfix/master[2444]: warning: master_wakeup_timer_event: service pickup(public/pickup): Connection refused
Oct 18 17:35:58 web.lifecorporate.com dovecot[1109]: service=imap, [email protected], ip=[52.169.20.163]. Logged out rcvd=1091, sent=21275
Oct 18 17:35:58 web.lifecorporate.com dovecot[1109]: service=imap, [email protected], ip=[52.169.20.163]. Logged out rcvd=482, sent=2565
Oct 18 17:35:58 web.lifecorporate.com dovecot[1109]: imap-login: Login: user=<[email protected]>, method=LOGIN, rip=52.169.20.163, lip=5.79.100.17, mpid=3667, TLS, session=<LEgL/9NbGM00qR
Oct 18 17:35:59 web.lifecorporate.com dovecot[1109]: imap-login: Login: user=<[email protected]>, method=LOGIN, rip=52.169.20.163, lip=5.79.100.17, mpid=3670, TLS, session=<u6kU/9NbJs00qR
Oct 18 17:35:59 web.lifecorporate.com dovecot[1109]: imap-login: Login: user=<[email protected]>, method=LOGIN, rip=52.169.20.163, lip=5.79.100.17, mpid=3672, TLS, session=</Cwc/9NbKM00qR
Oct 18 17:35:59 web.lifecorporate.com dovecot[1109]: service=imap, [email protected], ip=[52.169.20.163]. Logged out rcvd=209, sent=1294
Oct 18 17:36:33 web.lifecorporate.com postfix/anvil[2950]: statistics: max connection rate 1/60s for (smtp:191.96.249.63) at Oct 18 17:26:33
Oct 18 17:36:33 web.lifecorporate.com postfix/anvil[2950]: statistics: max connection count 1 for (smtp:191.96.249.63) at Oct 18 17:26:33
Oct 18 17:36:33 web.lifecorporate.com postfix/anvil[2950]: statistics: max cache size 3 at Oct 18 17:33:31
Oct 18 17:36:35 web.lifecorporate.com postfix/master[2444]: warning: master_wakeup_timer_event: service pickup(public/pickup): Connection refused
~

Can you help something with this, please?
 
Hi Branko,

Branko said:
warning: master_wakeup_timer_event: service pickup(public/pickup): Connection refused
Click to expand...
Points to a misconfiguration at your "/etc/postfix/master.cf"

The standard configuration of postfix is based on the unix interface usage, but newer operating system will use fifo for "pickup" and "qmgr". Plesk should have added:
Code: 
pickup fifo n - - 60 1 pickup
qmgr fifo n - n 1 1 qmgr
... and you should make sure, that
Code: 
pickup unix n - - 60 1 pickup
qmgr unix n - n 300 1 qmgr
... has been commented with a "#" in front of the standart configuration lines.​


For your network issue, it could be a good idea to REREAD the IP(s) over your Plesk Control Panel ( => "Home > Tools & Settings > IP Addresses" - Button "Reread IP" ), or by using the command ( logged in as user "root" over SSH ) over the command line => /usr/local/psa/bin/ipmanage --reread
 
Thank you for fast response, you are really great.

Did already the fix for unix to fifa, checked now again, but it is properly done.
Also, I have done REREAD before, tried it again, but it didn't help.

Restarted server also, but it is the same error.

Could it be some IP clash? It started happening after adding IPv6 addresses to the server.
Is there some safe command for IP flushing that would you recommend?

Thank you very much again, everything you say is helpful.
 
When done # postfix check

postfix/postfix-script: warning: not set-gid or not owner+group+world executable: /usr/sbin/postdrop
postfix/postfix-script: warning: /usr/lib/sendmail and /usr/sbin/sendmail differ
postfix/postfix-script: warning: Replace one by a symbolic link to the other

 
After ls -al /usr/sbin/sendmail && ls -al /usr/lib/sendmail

lrwxrwxrwx 1 root root 21 Aug 18 17:20 /usr/sbin/sendmail -> /etc/alternatives/mta
lrwxrwxrwx 1 root root 30 Aug 18 17:20 /usr/lib/sendmail -> /etc/alternatives/mta-sendmail

How to "Replace one by a symbolic link to the other"?
 
Hi Branko,

Branko said:
Is there some safe command for IP flushing
Click to expand...
There is no such "feature" or command as your network - configuration is not equivalent to "iptables" for example. ;) But you are still able to remove your whole configuration ( first over the Plesk Control Panel and pls. check afterwards, that there is no leftover at your network - scripts - folder ( => /etc/sysconfig/network-scripts ) on your server ).

Pls check afterwards, that your basic configuration works without issues and only if this is the case, you would try another new IPv6 configuration attempt.

Pls. don't modify any sendmail related links/symlinks/configuration. There are in most cases fine and working as expected and have got nothing to do with your network settings. :). But correct the
Branko said:
not set-gid or not owner+group+world executable: /usr/sbin/postdrop
Click to expand...
... issue, with ( logged in user "root" over SSH ):
Code: 
postfix set-permissions


If you experience issues with postfix and sendmail, it is most likely the case, that you tried to install the "sendmail" - package with your software package manager ( "yum" / or "apt-get"/"aptitude", depending to your operating system ). Pls. note, that Plesk has it's very own package here ( which comes with the corresponding "plesk-mail-XXX-driver" and any additional packages might conflict here. Pls. remove any additional "sendmail" - packages and correct possible related issues with the example commands:
Code: 
plesk installer --select-product-id plesk --select-release-current --install-component qmail
plesk installer --select-product-id plesk --select-release-current --install-component postfix
or/and use the Plesk Repair Utility to correct possible misconfigurations:
Code: 
plesk repair mail -y -v
 
UFHH01 said:
For your network issue, it could be a good idea to REREAD the IP(s) over your Plesk Control Panel ( => "Home > Tools & Settings > IP Addresses" - Button "Reread IP" ), or by using the command ( logged in as user "root" over SSH ) over the command line => /usr/local/psa/bin/ipmanage --reread
Click to expand...

Even after REREAD from Plesk control panel and server restart the problem remains.
Are there any other options?

I fixed Postfix issues.
 
Last edited:
Hello, I removed all IPv6 addresses. Server is working great, everything is up.

But network still cannot be restarted.

Here goes error details:

[root@web ~]# journalctl -xe
Nov 07 14:52:39 web.lifecorporate.com network[16949]: it work better with this distribution.
Nov 07 14:52:39 web.lifecorporate.com network[16949]: Please report for this software via the CentOS Bugs Database:
Nov 07 14:52:39 web.lifecorporate.com network[16949]: My View - CentOS Bug Tracker
Nov 07 14:52:39 web.lifecorporate.com network[16949]: exiting.
Nov 07 14:52:39 web.lifecorporate.com dhclient[17112]:
Nov 07 14:52:39 web.lifecorporate.com network[16949]: failed.
Nov 07 14:52:39 web.lifecorporate.com dhclient[17112]: This version of ISC DHCP is based on the release available
Nov 07 14:52:39 web.lifecorporate.com dhclient[17112]: on ftp.isc.org. Features have been added and other changes
Nov 07 14:52:39 web.lifecorporate.com dhclient[17112]: have been made to the base software release in order to make
Nov 07 14:52:39 web.lifecorporate.com dhclient[17112]: it work better with this distribution.
Nov 07 14:52:39 web.lifecorporate.com dhclient[17112]:
Nov 07 14:52:39 web.lifecorporate.com dhclient[17112]: Please report for this software via the CentOS Bugs Database:
Nov 07 14:52:39 web.lifecorporate.com dhclient[17112]: My View - CentOS Bug Tracker
Nov 07 14:52:39 web.lifecorporate.com dhclient[17112]:
Nov 07 14:52:39 web.lifecorporate.com dhclient[17112]: exiting.
Nov 07 14:52:39 web.lifecorporate.com network[16949]: [FAILED]
Nov 07 14:52:39 web.lifecorporate.com network[16949]: RTNETLINK answers: File exists
Nov 07 14:52:39 web.lifecorporate.com network[16949]: RTNETLINK answers: File exists
Nov 07 14:52:39 web.lifecorporate.com network[16949]: RTNETLINK answers: File exists
Nov 07 14:52:39 web.lifecorporate.com network[16949]: RTNETLINK answers: File exists
Nov 07 14:52:39 web.lifecorporate.com network[16949]: RTNETLINK answers: File exists
Nov 07 14:52:39 web.lifecorporate.com network[16949]: RTNETLINK answers: File exists
Nov 07 14:52:39 web.lifecorporate.com network[16949]: RTNETLINK answers: File exists
Nov 07 14:52:39 web.lifecorporate.com network[16949]: RTNETLINK answers: File exists
Nov 07 14:52:39 web.lifecorporate.com network[16949]: RTNETLINK answers: File exists
Nov 07 14:52:39 web.lifecorporate.com systemd[1]: network.service: control process exited, code=exited status=1
Nov 07 14:52:39 web.lifecorporate.com systemd[1]: Failed to start LSB: Bring up/down networking.
-- Subject: Unit network.service has failed
-- Defined-By: systemd
-- Support: systemd-devel Info Page
--
-- Unit network.service has failed.
--
-- The result is failed.
Nov 07 14:52:39 web.lifecorporate.com systemd[1]: Unit network.service entered failed state.
Nov 07 14:52:39 web.lifecorporate.com systemd[1]: network.service failed.
Nov 07 14:52:39 web.lifecorporate.com polkitd[555]: Unregistered Authentication Agent for unix-process:16943:2246126 (system bus name :1.252, object path /org/freedesktop/PolicyKit1/Authentica
Nov 07 14:52:40 web.lifecorporate.com dovecot[1140]: pop3-login: Login: user=<[email protected]>, method=DIGEST-MD5, rip=178.148.17.29, lip=5.79.100.17, mpid=17131, TLS, session=<VDdY4mRdLGiy
Nov 07 14:52:43 web.lifecorporate.com postfix/smtpd[16751]: warning: hostname smtp29.digitalsearchengine.in does not resolve to address 191.96.249.105: Name or service not known
Nov 07 14:52:43 web.lifecorporate.com postfix/smtpd[16751]: connect from unknown[191.96.249.105]
Nov 07 14:52:43 web.lifecorporate.com plesk_saslauthd[16755]: No such user '[email protected]' in mail authorization database
Nov 07 14:52:43 web.lifecorporate.com plesk_saslauthd[16755]: failed mail authenticatication attempt for user '[email protected]' (password len=17)
Nov 07 14:52:43 web.lifecorporate.com postfix/smtpd[16751]: warning: unknown[191.96.249.105]: SASL LOGIN authentication failed: authentication failure
Nov 07 14:52:43 web.lifecorporate.com postfix/smtpd[16751]: disconnect from unknown[191.96.249.105]
Nov 07 14:52:44 web.lifecorporate.com dovecot[1140]: service=pop3, [email protected], ip=[178.148.17.29]. Disconnected: Logged out rcvd=24, sent=248, top=0/0, retr=0/0, del=0/6, size=208
Nov 07 14:52:47 web.lifecorporate.com dovecot[1140]: pop3-login: Login: user=<[email protected]>, method=DIGEST-MD5, rip=178.148.17.29, lip=5.79.100.17, mpid=17138, TLS, session=<nEjN4mRdLWi
Nov 07 14:52:48 web.lifecorporate.com dovecot[1140]: service=pop3, [email protected], ip=[178.148.17.29]. Disconnected: Logged out rcvd=24, sent=307, top=0/0, retr=0/0, del=0/8, size=34
Nov 07 14:52:50 web.lifecorporate.com dovecot[1140]: pop3-login: Login: user=<[email protected]>, method=DIGEST-MD5, rip=178.148.17.29, lip=5.79.100.17, mpid=17143, TLS, session=</nT+4mR
Nov 07 14:52:50 web.lifecorporate.com dovecot[1140]: service=pop3, [email protected], ip=[178.148.17.29]. Disconnected: Logged out rcvd=24, sent=690, top=0/0, retr=0/0, del=0/21, si
lines 1222-1270/1270 (END)


Can you suggest solution?
 
I am hosting on LeaseWeb. I saw in their docs that they forbid DHCP.

Is it ok to set up BOOTPROTO=static ?

What consequences will it make? Is DHCP default Plesk option? Or is it just in my server settings?

Just for a reminder my system is:
Version: Plesk Onyx v17.5.3_build1705170317.16 os_CentOS 7
OS: CentOS Linux 7.4.1708 (Core)
 
And additional error details

[root@web ~]# systemctl status network.service
● network.service - LSB: Bring up/down networking
Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2017-11-07 15:32:11 CET; 8s ago
Docs: man:systemd-sysv-generator(8)
Process: 32006 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)
Memory: 21.7M
CGroup: /system.slice/network.service
└─799 /sbin/dhclient -1 -q -lf /var/lib/dhclient/dhclient--eth0.lease -pf /var/run/dhclient-eth0.pid -H web eth0

Nov 07 15:32:11 web.lifecorporate.com network[32006]: RTNETLINK answers: File exists
Nov 07 15:32:11 web.lifecorporate.com network[32006]: RTNETLINK answers: File exists
Nov 07 15:32:11 web.lifecorporate.com network[32006]: RTNETLINK answers: File exists
Nov 07 15:32:11 web.lifecorporate.com network[32006]: RTNETLINK answers: File exists
Nov 07 15:32:11 web.lifecorporate.com network[32006]: RTNETLINK answers: File exists
Nov 07 15:32:11 web.lifecorporate.com network[32006]: RTNETLINK answers: File exists
Nov 07 15:32:11 web.lifecorporate.com systemd[1]: network.service: control process exited, code=exited status=1
Nov 07 15:32:11 web.lifecorporate.com systemd[1]: Failed to start LSB: Bring up/down networking.
Nov 07 15:32:11 web.lifecorporate.com systemd[1]: Unit network.service entered failed state.
Nov 07 15:32:11 web.lifecorporate.com systemd[1]: network.service failed.
 
Ok, I changed BOOTPROTO=none in /etc/sysconfig/network-scripts/ifcfg-eth0
Network restarted without an issue.

My /etc/sysconfig/network-scripts/ifcfg-eth0 now looks like this

DEVICE="eth0"
ONBOOT="yes"
NETBOOT=yes
IPV6INIT=yes
IPV6_DEFAULTGW=fe80::1
IPV6_DEFAULTDEV=eth0
BOOTPROTO=none
TYPE=Ethernet
NAME="eth0"
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
PEERDNS=yes
PEERROUTES=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPV6ADDR_SECONDARIES="2001:1af8:4700:a121:1200::1/64"

Do you see here something problematic? Is there something missing that I should add? Or something to remove or change?
 
You must log in or register to reply here.

Similar threads

G
Issue network.service LSB: Bring up/down networking
Replies
0
Views
1K
gianni_inside
G
R
Resolved Failed to start Raise network interfaces
Replies
1
Views
172
Retr0
R
Oscar Segura
Issue Upgrading from Ubuntu 20.04 to 22.04: failed reboot
Replies
0
Views
919
Oscar Segura
Oscar Segura
K
Issue DB query failed: "SET sql_mode = ''" Error: SQLSTATE[HY000] [2002] No such file or directory File Mysql.php Line 68
Replies
13
Views
4K
Tskito
T
Endre
Issue Server Error 500 Plesk\Exception\Database DB query failed: SQLSTATE[HY000] [2002] No such file or directory
Replies
15
Views
7K
MihaiNecreala
M
Back
Top