Re: NetworkManager fails to start during boot

[Ajay Garg <ajaygargnsit gmail com>]

Hi all.

I managed to figure out the reason; it was a case of misplaced script sequence.
The solution is to run a custom script, and this script NEEDS to be
run before "/etc/init.d/Networkmanager" is run at boot time.

I have one last query; kindly help me NM guys :)

"""
I am thinking of adding the custom-script-statements just at the
beginning of "start()" method of "/etc/init.d/NetworkManager", so that
this is always run prior to the NetworkManager script, no matter what
the sequence of NetworkManager script is.

So, would it be ok if I do some "sed" processing on the
"/etc/init.d/NetworkManager" ?
Is "/etc/init.d/NetworkManager" subject to change (text wise) ?
"""

Looking forward to a reply.


Thanks and Regards,
Ajay

On Thu, Apr 5, 2012 at 9:54 PM, Ajay Garg <ajaygargnsit gmail com> wrote:
> Hi all.
>
> I have a Fedora 14 image, and NetworkManager 0.8 has been configured to
> start at boot-time (at runlevel 5).
>
> However, after my system boots up, "ps -aux | grep -i "NetworkManager""
> shows no running NetworkManager.
> Instead, the following NM trace is obtained from "/var/log/messages" ::
>
> ##########################################################################################
> Dec 17 15:23:38 xo-05-2a-1f NetworkManager[636]: <warn> caught signal 11.
> Generating backtrace...
> Dec 17 15:23:38 xo-05-2a-1f powerd: starting
> Dec 17 15:23:38 xo-05-2a-1f powerd: configuring from /etc/powerd/powerd.conf
> Dec 17 15:23:38 xo-05-2a-1f NetworkManager[636]: ******************* START
> **********************************
> Dec 17 15:23:38 xo-05-2a-1f NetworkManager[636]: Frame 0: NetworkManager
> (nm_logging_backtrace+0x56) [0x80a1536]
> Dec 17 15:23:38 xo-05-2a-1f NetworkManager[636]: Frame 1: NetworkManager
> (0x8048000+0x8085ee5) [0x8085ee5]
> Dec 17 15:23:38 xo-05-2a-1f NetworkManager[636]: Frame 2: (vdso)
> (__kernel_sigreturn+0x0) [0xb782e400]
> Dec 17 15:23:38 xo-05-2a-1f NetworkManager[636]: Frame 3: NetworkManager
> (0x8048000+0x8076404) [0x8076404]
> Dec 17 15:23:38 xo-05-2a-1f NetworkManager[636]: Frame 4:
> /lib/libgobject-2.0.so.0 (g_cclosure_marshal_VOID__PARAM+0x88) [0xb7366588]
> Dec 17 15:23:38 xo-05-2a-1f NetworkManager[636]: Frame 5:
> /lib/libgobject-2.0.so.0 (g_closure_invoke+0x193) [0xb7349be3]
> Dec 17 15:23:38 xo-05-2a-1f kernel: [   29.646899] input: olpc-kbdshim
> virtual input as /devices/virtual/input/input7
> Dec 17 15:23:38 xo-05-2a-1f NetworkManager[636]: Frame 6:
> /lib/libgobject-2.0.so.0 (0xb733e000+0xb735c0f0) [0xb735c0f0]
> Dec 17 15:23:38 xo-05-2a-1f NetworkManager[636]: Frame 7:
> /lib/libgobject-2.0.so.0 (g_signal_emit_valist+0x80e) [0xb736524e]
> Dec 17 15:23:38 xo-05-2a-1f NetworkManager[636]: Frame 8:
> /lib/libgobject-2.0.so.0 (g_signal_emit+0x33) [0xb7365403]
> Dec 17 15:23:38 xo-05-2a-1f NetworkManager[636]: Frame 9:
> /lib/libgobject-2.0.so.0 (0xb733e000+0xb734b891) [0xb734b891]
> Dec 17 15:23:38 xo-05-2a-1f NetworkManager[636]: Frame 10:
> /lib/libgobject-2.0.so.0 (0xb733e000+0xb734ac70) [0xb734ac70]
> Dec 17 15:23:38 xo-05-2a-1f NetworkManager[636]: Frame 11:
> /lib/libgobject-2.0.so.0 (g_object_notify+0x551) [0xb734dbe1]
> Dec 17 15:23:38 xo-05-2a-1f NetworkManager[636]: Frame 12: NetworkManager
> (0x8048000+0x8073540) [0x8073540]
> Dec 17 15:23:38 xo-05-2a-1f NetworkManager[636]: Frame 13:
> /lib/libglib-2.0.so.0 (0xb721e000+0xb725a042) [0xb725a042]
> Dec 17 15:23:38 xo-05-2a-1f NetworkManager[636]: Frame 14:
> /lib/libglib-2.0.so.0 (g_main_context_dispatch+0x1d2) [0xb725e192]
> Dec 17 15:23:38 xo-05-2a-1f NetworkManager[636]: Frame 15:
> /lib/libglib-2.0.so.0 (0xb721e000+0xb725e978) [0xb725e978]
> Dec 17 15:23:38 xo-05-2a-1f NetworkManager[636]: Frame 16:
> /lib/libglib-2.0.so.0 (g_main_loop_run+0x18b) [0xb725f04b]
> Dec 17 15:23:38 xo-05-2a-1f NetworkManager[636]: Frame 17: NetworkManager
> (main+0x15d6) [0x80876b6]
> Dec 17 15:23:38 xo-05-2a-1f NetworkManager[636]: Frame 18: /lib/libc.so.6
> (__libc_start_main+0xe6) [0xb707ae36]
> Dec 17 15:23:38 xo-05-2a-1f NetworkManager[636]: Frame 19: NetworkManager
> (0x8048000+0x805df01) [0x805df01]
> Dec 17 15:23:38 xo-05-2a-1f NetworkManager[636]: ******************* END
> **********************************
> ##########################################################################################
>
>
> Any ideas, if this trace could lead to the problem-source?
>
>
> WIll be grateful for a reply.
>
>
>
> Thanks and Regards,
> Ajay