Any news on consolewd and that pesky "Inconsistency detected by ld.so..:"?

Check out the new FAQs (Frequently Asked Questions) board for a growing list of hints, tips and diagnostic suggestions.

[ejeklint]

I have set up latest Ubuntu on an Intel Mac mini and have problems getting consolewd to run. Well, actually it did run for a while before I moved location. I first tested in my apartment with my new WMR100N and consolewd started to produce data just fine. Then I went to my summer house, fired everything up (same HW, no SW changes) and the infamous error message

Code:

Inconsistency detected by ld.so: dl-minimal.c: 148: realloc: Assertion `ptr == alloc_last_block' failed!

turned up. I have read through the forum and tried to figure out what could be wrong, but no success. Any more info on this?

Oh, and many thanks for all the effort on WD for Linux!

/Per

[ejeklint]

Small and humble *bump* here. 

Anything I can do to help out with this?

[ejeklint]

Ah, I just found a new version. After download and install it now works just fine! 

I really appreciate the consoldewd utility. Donation is on its way.

Cheers!

/Per

[windy]

interesting
the new libcom.so that Yves created must have fixed the problem

[Yves]

Windy, out of curiosity, did you compile the version 3.3 and release it?
My guess is the old one was compiled on my system which is now a Fed core 9 32 bits.

Yves

 

[windy]

it is now, with the latest consolewd version...

[ejeklint]

Sigh... I'm bumping this thread again. This issue is not solved. After rebooting my machine I'm back in this "Inconsistency detected" thing, and it is quite mysterious. Last time I just reinstalled with the latest download, but that does not help today using the brand new build. I will gladly help debug this but need input from you Gurus.

So, any ideas?

[ejeklint]

A little more info: running Ubuntu server (no gui) 8.10 32 bit on an Intel Mac mini. "ls /lib/libc*" gives:

Code:

/lib/libc-2.8.90.so  /lib/libcap.so.2.10     /lib/libcidn.so.1       /lib/libconsole.so.0.0.0  /lib/libctutils.so.0
/lib/libcap.so.1     /lib/libcfont.so.0      /lib/libcom_err.so.2    /lib/libcrypt-2.8.90.so   /lib/libctutils.so.0.0.0
/lib/libcap.so.1.10  /lib/libcfont.so.0.0.0  /lib/libcom_err.so.2.1  /lib/libcrypt.so.1
/lib/libcap.so.2     /lib/libcidn-2.8.90.so  /lib/libconsole.so.0    /lib/libc.so.6

Strange thing that I got it to run once today, then rebooted, tried to run again and it's no go whatever I try.

[ejeklint]

More info, very interesting.  I did manage to start consolewd, but only when running in background. So "nohup ./GoWdconsole.sh &" works, but "./GoWdconsole.sh" does not. I just can't figure out an explanation for that...

[peetu]

Code:

Inconsistency detected by ld.so: dl-minimal.c: 148: realloc: Assertion `ptr == alloc_last_block' failed!

Hi, I have also the same problem. Short history: I ran Ubuntu 8.04 with WD console without any problems for two months. At some point (timing is bit unclear, I just can't remember), I installed minidlna for pushing data to my TV via ethernet. Installing the software required a huge amount of packages to be installed before I could compile and run it (list of packages can be found somewhere if needed).  After that the "Assertion failed" problem came up.

I didn't use too much time to fix the problem, but I installed Ubuntu 8.10 and everything started to work again (at this time with WD console version from March 10, 2009). Today, after running WD console roughly one month on the new installation,  I installed MythTV on the same host to get DLNA working again. I needed a reboot because I screwed up with group update (removed myself from the admin group , and after the reboot, the assertion failed problem occurred again.

The packages that were installed with mythtv are listed here:http://jokela.org/misc/installed_110409.txt. Any idea what is going wrong, and where? The problem seems to relate to some package that is installed with these sound/video/graphics softwares.

EDIT: And my weather station is Oregon Scientific WMR100.

/Petri

[ejeklint]

Hi, I have also the same problem. Short history: I ran Ubuntu 8.04 with WD console without any problems for two months...

Problem is back here. After a reboot it stopped working so today I made a brand new and clean Ubuntu 8.10 server installation, no GUI, and the very latest version (12 april) of wdisplay - version 5.93. Guess what, "Inconsistency detected...". Sigh. Don't know what to do now...

If anyone has it running on a Mac mini, which Linux distro are you using?

[n7dq]

I did some Googling on this error and dl-minimal.c code.  Serveral of the finds pointed to memory issues at the machine level though there were not a lot of solutions. How much memory do you have on your machine?  How much paging space?  One possible issue is that you are running out of memory.  One thing to do would be monitor your memory and paging usage as you start up consolewd.   I know consolewd does not require a lot of memory but depending on what else you are doing on the machine you could be over running memory and paging.

One other thing what do you have LD_LIBRARY_PATH set to, as GoWdConsole.sh resets that environment variable to use the deploy directory for consolewd.

Just a couple of thoughts.

Mike - N7DQ

[ejeklint]

There's more than enough of memory so I don't think that's an issue, and LD_LIBRARY_PATH is not used anywhere else either. The very odd thing that I sometimes, but only when remotely logged in, can get it to start... Anyhow, I will try another Linux distro as it *might* be just Ubuntu that has this problem.

[n7dq]

Well, Ubuntu should work.  Though what you just said about remote login is strange, I agree.  I am assuming the same login id for local login and remote login, right?  You may want to do an 'env | sort' locally and remotely and see if there is any difference in the environments prior to starting up consolewd.  There are environments that sets things up differently  based on local versus remote login. 

Are you starting a windows manager or just a terminal session locally?  On remote login are you just using SSH or some other type of terminal session?

Mike - N7DQ

[ejeklint]

Yes, same id for login, and there are no differences in env what I can see. I'm using terminal to do an ssh login. But I haven't been able to start consolewd in any way at all today so at least it's consistent now.