[Rdo-list] Query regarding RDO Juno-1 install on CentOS7
Deepak Shetty
dpkshetty at gmail.com
Tue Dec 30 06:38:29 UTC 2014
Adding more details on the fact that I was unable to chkconfig OFF
network.service
[root at rhsdev1 multi-user.target.wants]# systemctl status network.service
network.service - LSB: Bring up/down networking
Loaded: loaded (/etc/rc.d/init.d/network)
Active: failed (Result: exit-code) since Tue 2014-12-30 17:13:10 IST;
17min ago
Dec 30 17:13:08 rhsdev1.lab.eng.blr.redhat.com dhclient[2169]: DHCPDISCOVER
on em1 to 255.255.255.255 port 67 interval 11 (xid=0x35011ab0)
Dec 30 17:13:08 rhsdev1.lab.eng.blr.redhat.com dhclient[2169]: DHCPREQUEST
on em1 to 255.255.255.255 port 67 (xid=0x35011ab0)
Dec 30 17:13:08 rhsdev1.lab.eng.blr.redhat.com dhclient[2169]: DHCPOFFER
from 10.70.47.254
Dec 30 17:13:08 rhsdev1.lab.eng.blr.redhat.com dhclient[2169]: DHCPACK from
10.70.47.254 (xid=0x35011ab0)
Dec 30 17:13:10 rhsdev1.lab.eng.blr.redhat.com dhclient[2169]: bound to
10.70.45.1 -- renewal in 38250 seconds.
Dec 30 17:13:10 rhsdev1.lab.eng.blr.redhat.com network[1964]: Determining
IP information for em1... done.
Dec 30 17:13:10 rhsdev1.lab.eng.blr.redhat.com network[1964]: [ OK ]
Dec 30 17:13:10 rhsdev1.lab.eng.blr.redhat.com systemd[1]: network.service:
control process exited, code=exited status=1
Dec 30 17:13:10 rhsdev1.lab.eng.blr.redhat.com systemd[1]: Failed to start
LSB: Bring up/down networking.
Dec 30 17:13:10 rhsdev1.lab.eng.blr.redhat.com systemd[1]: Unit
network.service entered failed state.
[root at rhsdev1 multi-user.target.wants]# chkconfig network on
[root at rhsdev1 multi-user.target.wants]# chkconfig network
[root at rhsdev1 multi-user.target.wants]# service network status
Configured devices:
lo br-ex em1 em2
Currently active devices:
lo em1 virbr0
[root at rhsdev1 multi-user.target.wants]# systemctl disable network.service
network.service is not a native service, redirecting to /sbin/chkconfig.
Executing /sbin/chkconfig network off
[root at rhsdev1 multi-user.target.wants]# systemctl enable network.service
network.service is not a native service, redirecting to /sbin/chkconfig.
Executing /sbin/chkconfig network on
The unit files have no [Install] section. They are not meant to be enabled
using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
*But the interesting news is that, post system reboot:*
I have NM disabled, network service failed state, but still networking
works for my server
I am able to ping it, ssh into it, both inbound and outbound networking are
working fine
If both NM and network service are down, whats managing the networking here
?
Is there some other systemd target/unit file that I need to enable instead
of network.service ?
thanx,
deepak
On Tue, Dec 30, 2014 at 11:41 AM, Deepak Shetty <dpkshetty at gmail.com> wrote:
>
>
> On Mon, Dec 29, 2014 at 9:04 PM, Patrick Laimbock <patrick at laimbock.com>
> wrote:
>
>> On 29-12-14 15:39, Deepak Shetty wrote:
>>
>>> > You need to disable NetworkManager and enable network service. Before
>>> you run Packstack you will also need to setup the ifcfg-XXXX network
>>> interfaces on all nodes and activate them.
>>>
>>> Why can't packstack handle this itself if it doesn't support NM? I m
>>>
>>
>> Ask the developers. Patches welcome.
>>
>> concerned about the manual steps involved and losing on my n/w
>>> connections in case i do anything wrong.
>>>
>>
>> Yes that's a risk so make sure to have the steps figured out before doing
>> anything. Having direct access to a (serial) console comes in handy if
>> things fall apart.
>>
>> Is there any reference on how
>>> to do this, i couldn't find anything specific on the quickstart page.
>>>
>>
>> I'm not aware of an RDO guide on this subject. The steps on each node are:
>> - create appropriate ifcfg-XXX files
>> - stop NetworkManager
>> - disable NetworkManager
>> - enable network
>> - start network
>>
>> You probably want to do the last 4 steps in one long command or else you
>> will loose connectivity after stopping NetworkManager if you are not using
>> a console.
>
>
> My current ifcfg-em1 is :
>
> [root at rhsdev1 network-scripts]# cat ifcfg-em1
> # Generated by dracut initrd
> DEVICE="em1"
> ONBOOT=yes
> NETBOOT=yes
> UUID="fd67c34e-9aad-44b7-a980-b5288ad3c442"
> IPV6INIT=yes
> BOOTPROTO=dhcp
> HWADDR="c8:1f:66:c6:d5:fc"
> TYPE=Ethernet
> NAME="em1"
>
> I did this:
>
> # systemctl stop NetworkManager.service ; chkconfig NetworkManager off;
> systemctl restart network.service ; chkconfig network on
>
> Note: Forwarding request to 'systemctl disable NetworkManager.service'.
> rm '/etc/systemd/system/multi-user.target.wants/NetworkManager.service'
> rm '/etc/systemd/system/dbus-org.freedesktop.NetworkManager.service'
> rm '/etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service'
> Job for network.service failed. See 'systemctl status network.service' and
> 'journalctl -xn' for details.
>
> [root at rhsdev1 network-scripts]# systemctl status network.service
> network.service - LSB: Bring up/down networking
> Loaded: loaded (/etc/rc.d/init.d/network)
> Active: failed (Result: exit-code) since Tue 2014-12-30 17:01:00 IST;
> 30s ago
>
> Dec 30 17:01:00 rhsdev1.lab.eng.blr.redhat.com network[24948]: RTNETLINK
> answers: File exists
> Dec 30 17:01:00 rhsdev1.lab.eng.blr.redhat.com network[24948]: RTNETLINK
> answers: File exists
> Dec 30 17:01:00 rhsdev1.lab.eng.blr.redhat.com network[24948]: RTNETLINK
> answers: File exists
> Dec 30 17:01:00 rhsdev1.lab.eng.blr.redhat.com network[24948]: RTNETLINK
> answers: File exists
> Dec 30 17:01:00 rhsdev1.lab.eng.blr.redhat.com network[24948]: RTNETLINK
> answers: File exists
> Dec 30 17:01:00 rhsdev1.lab.eng.blr.redhat.com network[24948]: RTNETLINK
> answers: File exists
> Dec 30 17:01:00 rhsdev1.lab.eng.blr.redhat.com network[24948]: RTNETLINK
> answers: File exists
> Dec 30 17:01:00 rhsdev1.lab.eng.blr.redhat.com systemd[1]:
> network.service: control process exited, code=exited status=1
> Dec 30 17:01:00 rhsdev1.lab.eng.blr.redhat.com systemd[1]: Failed to
> start LSB: Bring up/down networking.
> Dec 30 17:01:00 rhsdev1.lab.eng.blr.redhat.com systemd[1]: Unit
> network.service entered failed state.
>
> I modified em1 to:
>
> [root at rhsdev1 network-scripts]# cat ifcfg-em1
> # Generated by dracut initrd
> DEVICE="em1"
> ONBOOT=yes
> NETBOOT=yes
> UUID="fd67c34e-9aad-44b7-a980-b5288ad3c442"
> IPV6INIT=yes
> BOOTPROTO=dhcp
> #HWADDR="c8:1f:66:c6:d5:fc"
> NM_CONTROLLED=no
> TYPE=Ethernet
> NAME="em1"
>
> [root at rhsdev1 network-scripts]# service network restart
> Restarting network (via systemctl): Job for network.service failed. See
> 'systemctl status network.service' and 'journalctl -xn' for details.
> [FAILED]
> [root at rhsdev1 network-scripts]# systemctl restart network.service
> Job for network.service failed. See 'systemctl status network.service' and
> 'journalctl -xn' for details.
> [root at rhsdev1 network-scripts]# systemctl status network.service
> network.service - LSB: Bring up/down networking
> Loaded: loaded (/etc/rc.d/init.d/network)
> Active: failed (Result: exit-code) since Tue 2014-12-30 17:07:34 IST;
> 6s ago
> Process: 26318 ExecStart=/etc/rc.d/init.d/network start (code=exited,
> status=1/FAILURE)
>
> Dec 30 17:07:34 rhsdev1.lab.eng.blr.redhat.com network[26318]: RTNETLINK
> answers: File exists
> Dec 30 17:07:34 rhsdev1.lab.eng.blr.redhat.com network[26318]: RTNETLINK
> answers: File exists
> Dec 30 17:07:34 rhsdev1.lab.eng.blr.redhat.com network[26318]: RTNETLINK
> answers: File exists
> Dec 30 17:07:34 rhsdev1.lab.eng.blr.redhat.com network[26318]: RTNETLINK
> answers: File exists
> Dec 30 17:07:34 rhsdev1.lab.eng.blr.redhat.com network[26318]: RTNETLINK
> answers: File exists
> Dec 30 17:07:34 rhsdev1.lab.eng.blr.redhat.com network[26318]: RTNETLINK
> answers: File exists
> Dec 30 17:07:34 rhsdev1.lab.eng.blr.redhat.com network[26318]: RTNETLINK
> answers: File exists
> Dec 30 17:07:34 rhsdev1.lab.eng.blr.redhat.com systemd[1]:
> network.service: control process exited, code=exited status=1
> Dec 30 17:07:34 rhsdev1.lab.eng.blr.redhat.com systemd[1]: Failed to
> start LSB: Bring up/down networking.
> Dec 30 17:07:34 rhsdev1.lab.eng.blr.redhat.com systemd[1]: Unit
> network.service entered failed state.
>
>
>
> *So in short, disabling NM and enabling/restarting network isn't working
> as my network service is getting into error state*thanx,
> deepak
>
>
>
>
>>
>> HTH,
>> Patrick
>>
>> _______________________________________________
>> Rdo-list mailing list
>> Rdo-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/rdo-list
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rdoproject.org/pipermail/dev/attachments/20141230/9cf3a78b/attachment.html>
More information about the dev
mailing list