[5b12a] emhttp crashed, segfaults if I restart it

[draug3n]

Hi

 

Last week I tried to set one of my shares to use my cache drive. After I hit "Apply" in the web interface, emhttp hung. I killed it from the console, and tried to start it over, but I'm now getting a segfault. Syslog says:

 

Nov  7 10:29:45 mimer emhttp: unRAID System Management Utility version 5.0-beta12a (Lime Tech)
Nov  7 10:29:45 mimer emhttp: Copyright (C) 2005-2011, Lime Technology, LLC (Lime Tech)
Nov  7 10:29:45 mimer emhttp: Pro key detected, GUID: 05DC-A731-PBBV-BYYBMTQ7F4A8 (Other emhttp)
Nov  7 10:29:45 mimer emhttp: rdevName.22 not found (Other emhttp)
Nov  7 10:29:45 mimer emhttp: diskFsStatus.1 not found (Other emhttp)
Nov  7 10:29:45 mimer kernel: emhttp[20127]: segfault at 0 ip b74a1760 sp bfcac0a0 error 4 in libc-2.11.1.so[b7428000+15c000] (Errors)

 

A forum search shows that this error has been seen as early as 5b8, and also at least for one person also running 5b12a.

 

Any ideas on how to proceed?

[Joe L.]

Hi

 

Last week I tried to set one of my shares to use my cache drive. After I hit "Apply" in the web interface, emhttp hung. I killed it from the console, and tried to start it over, but I'm now getting a segfault. Syslog says:

 

Nov  7 10:29:45 mimer emhttp: unRAID System Management Utility version 5.0-beta12a (Lime Tech)
Nov  7 10:29:45 mimer emhttp: Copyright (C) 2005-2011, Lime Technology, LLC (Lime Tech)
Nov  7 10:29:45 mimer emhttp: Pro key detected, GUID: 05DC-A731-PBBV-BYYBMTQ7F4A8 (Other emhttp)
Nov  7 10:29:45 mimer emhttp: rdevName.22 not found (Other emhttp)
Nov  7 10:29:45 mimer emhttp: diskFsStatus.1 not found (Other emhttp)
Nov  7 10:29:45 mimer kernel: emhttp[20127]: segfault at 0 ip b74a1760 sp bfcac0a0 error 4 in libc-2.11.1.so[b7428000+15c000] (Errors)

 

A forum search shows that this error has been seen as early as 5b8, and also at least for one person also running 5b12a.

 

Any ideas on how to proceed?

can you get a status listing from the "md" driver by typing:

/root/mdcmd status

 

It looks as if emhttp is not finding the variables in it it expects, and was not coded to handle the case when they did not.  ( it is looking for rdevName.22 and diskFsStatus.1 )

 

Joe L.

[draug3n]

here you go

mdcmd_status.txt

[stealth82]

Same problem here with 5b14.

[prostuff1]

try typing this first:

/etc/rc.d/rc.unRAID stop

 

then follow with launching emhttp.

[gbdesai]

I have the SAME EXACT error.  What is this resource/variable it can't find, I've been running for nearly 2 months with no problems on 12a.  A reboot doesn't help, nor does the stop unraid and restart emhttp...

[mgoh99]

I also get consistent emhttp crashes with b14.  If i restart I get a segmentation fault error.  I'm forced to restart the entire server. 

 

Does anyone have any leads as to why this is happening?

[hgelpke]

Same problem here with b14. I also don't see rc.unRAID in the rc.d directory.

[spants]

same problem on b14, switching back to b13 doesnt fix it..

 

restarting emhttp:

Feb  6 12:55:39 Tower emhttp: unRAID System Management Utility version 5.0-beta14

Feb  6 12:55:39 Tower emhttp: Copyright © 2005-2011, Lime Technology, LLC

Feb  6 12:55:39 Tower emhttp: Pro key detected, GUID: 090C-1000-AA09-xxxxxxx

Feb  6 12:55:39 Tower emhttp: rdevName.22 not found

Feb  6 12:55:39 Tower emhttp: diskFsStatus.1 not found

Feb  6 12:55:39 Tower kernel: emhttp[15555]: segfault at 0 ip b74ed760 sp bf8df720 error 4 in libc-2.11.1.so[b7474000+15c000]

 

I saw on here http://lime-technology.com/forum/index.php?topic=13864.0 that same problem was caused by usb stick going out. Have emailed Tom for new guid.

 

 

[WeeboTech]

1. it could be a memory problem. A seg fault in libc.so means a lower level call is trying to access memory it cannot. A memory error could set a pointer to the wrong location.  Do a memtest86.

 

2. A bad value in the superblock.dat could be corrupting the whole table. I'm guessing here.

it could be a problem with the usb stick, or a corruption when the add to the config failed.

 

Note that an almost full usb key is prone to errors as sectors cannot be easily reassigned.

 

Possible remedies.

 

1. memt86

2. build a new superblock.dat file, I think you use the initconfig command but I do not remember.

3. If your USB key is almost full. clear files you do not need.

4. reformat your USB key and rebuild it from a backup. Including superblock.

 

 

If that doesn't work there's a bigger issue that I've not thought about.

 

Keep in mind every time you start or stop the array, the superblock on the flashkey is updated.

There is a field in it that has a time field that is updated. So even though you may not have added a drive, modifying the user share forces the array to be stopped, modified, then started.

 

[spants]

1. it could be a memory problem. A seg fault in libc.so means a lower level call is trying to access memory it cannot. A memory error could set a pointer to the wrong location.  Do a memtest86.

 

2. A bad value in the superblock.dat could be corrupting the whole table. I'm guessing here.

it could be a problem with the usb stick, or a corruption when the add to the config failed.

 

Note that an almost full usb key is prone to errors as sectors cannot be easily reassigned.

 

Possible remedies.

 

1. memt86

2. build a new superblock.dat file, I think you use the initconfig command but I do not remember.

3. If your USB key is almost full. clear files you do not need.

4. reformat your USB key and rebuild it from a backup. Including superblock.

 

 

If that doesn't work there's a bigger issue that I've not thought about.

 

Keep in mind every time you start or stop the array, the superblock on the flashkey is updated.

There is a field in it that has a time field that is updated. So even though you may not have added a drive, modifying the user share forces the array to be stopped, modified, then started.

 

Thanks for the info. I have been running memtest and it seems ok.

Reformatted several test with the same error - no gui except unmenu

wiped out all the extra modules - still the same.

Then disabled my ESET 5.0 antivirus web scan and it all starts working!!!! I think that eset is crashing the gui.

 

What a waste of 5 hours of my life!

 

see http://lime-technology.com/forum/index.php?topic=18333.0