Red Hat Bugzilla – Bug 57106
mars_nwe does PANIC when loading, and then goes down
Last modified: 2015-03-04 20:09:57 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98)
Description of problem:
I have a Red-Hat Linux with mars installed.
I had no problems in the last 18 months.
Today, all the users cannot use this computer remotly.
When I did ps - ef | more, I couldn'd see the nwserv and nwbind.
I rebooted it, and after that, I tried
and after a moment I does down again.
the file /var/log/mars_nwe.log showns
NWB 0 7: PANIC!!
NWB 0 !!! SIG_SEGV !!! ncp_sequence = 7
NWS 0 0:write_wdata: Invalid argument to NWBIND
NWS 0 0:panic !!
NWS 0 0:child died: invalid argument child = nwbind, result=1
NWS 0 0:write_wdata : Broken pipe to NWBIND
NWS 0 0:close device=eth0, frame=2
NWS 0 0:close device=eth0, frame=4
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.I need to execute /etc/rc.d/rc2.d/S99mars-nwe start
Actual Results: I performed /etc/rc.d/rc2.d/S99mars-nwe status
< a moment latter>
Expected Results: nw_serv running/started
Have you installed any new software and checked wether the logfiles/disks might
be full? There is no logical reason why mars shouldn't work anymore...
Read ya, Phil
Thanks for the bug report.
However, Red Hat no longer include and maintains mars-nwe.
The Fedora Legacy project (http://fedoralegacy.org/) maintains some
older releases, and if you believe this bug is interesting to them,
please report the problem in the bug tracker at: