LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Virtualization and Cloud
User Name
Password
Linux - Virtualization and Cloud This forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.

Notices


Reply
  Search this Thread
Old 11-03-2018, 02:23 AM   #1
siddharthav
LQ Newbie
 
Registered: Aug 2018
Location: Bengaluru, India
Posts: 17

Rep: Reputation: Disabled
systemctl restart networking command failure


Hi people,

while working on xen hypervisor, I am trying to create a bridge on ubuntu 16.04. but its ending up with "Job for networking.service failed because the control process exited with error code. See "systemctl status networking.service" and "journalctl -xe" for details. " error.

I followed this "http://xmodulo.com/install-xen-hypervisor.html"

anybody please help me.
 
Old 11-03-2018, 03:49 AM   #2
ondoho
LQ Addict
 
Registered: Dec 2013
Posts: 19,872
Blog Entries: 12

Rep: Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053
Quote:
Originally Posted by siddharthav View Post
See "systemctl status networking.service" and "journalctl -xe" for details. "
and, did you?
 
Old 11-03-2018, 05:46 AM   #3
siddharthav
LQ Newbie
 
Registered: Aug 2018
Location: Bengaluru, India
Posts: 17

Original Poster
Rep: Reputation: Disabled
I just end with that error any solution please.
 
Old 11-03-2018, 06:58 AM   #4
berndbausch
LQ Addict
 
Registered: Nov 2013
Location: Tokyo
Distribution: Mostly Ubuntu and Centos
Posts: 6,316

Rep: Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002
Like ondoho suggested, the solution is to follow the program's instructions, that is use systemctl status and journalctl to get more details. Without more details nobody can help you.

You can also try journalctl -u networking. This will display the journal for the networking service. The purpose of the journal is to provide information when the service doesn't work correctly or not at all.
 
Old 11-05-2018, 10:31 PM   #5
siddharthav
LQ Newbie
 
Registered: Aug 2018
Location: Bengaluru, India
Posts: 17

Original Poster
Rep: Reputation: Disabled
ok thank you will reach you back..,
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Restart systemctl*daemon​ - systemctl command not found cjosephl Linux - Newbie 7 11-11-2017 04:53 PM
systemctl restart network FAILED Joseph2016 Linux - Newbie 8 07-17-2016 05:08 AM
Systemctl command error gowlet CentOS 3 06-06-2016 04:13 AM
Systemctl command error gowlet Fedora 2 06-05-2016 11:04 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Virtualization and Cloud

All times are GMT -5. The time now is 11:04 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration