Unloading an unloadable NLM
One of the frustrating things about NetWare has always been its distinct lack of a decent process killer. Part of this was perhaps over-confidence on the part of Drew Major (and others), thinking that we would never need a process killer because there would be no such thing as a runaway process on NetWare. Another (good) reason might be that killing a process can sometimes be as risky as letting it run, even if it runs until the next server restart.
With NetWare 6, we got a fairly useful bash implementation, along with some standard utilities (grep, egrep, fgrep, cat, etc.). We also happened to get kill and killall. Now, the problem with kill is, of course, that one needs a process id to feed it. Naturally, among the things we lack is a port of ps (don't ask me why!). Trying killall results in a slew of public symbol errors (at least for me). So, what to do?
Related posts:
- Mass renaming files at the OS/2 command line Sometimes, command shells are simply inadequate to the task. This...
- NLM Memory Tuning Sometimes, it pays to look at the obvious, even when...
- A sincere apology to users of my YUM repo mirror No good deed goes unpunished. Setting things in motion...
- Still more PHP 5.3 fixes for Joomla! 1.5 Clearly documented code can be maintained by third parties,...
- Yet another method to grab download-disabled slideshows from SlideShare Just a quick one-liner to sequentially download files using cURL,...
NLM Memory Tuning
Physician, heal thyself...
One of my NetWare servers has been suffering of late with some runaway memory consumption (I'll leave it for another post to discuss the difference between excessive memory consumption and memory leakage, but suffice it to say, that these are non synonymous conditions). Logging in tonight to check the progress on some backups, I was greeted with:
SERVER-5.70-0 [nmID=2000A] Short term memory allocator is out of memory. 10 attempts to get more memory failed. request size in bytes 65536 from Module MYSQLD.NLM
I've not seen MYSQLD run short of memory before, so I took a closer look (backups were still active). I loaded SEG.NLMto see what was going on. The first thing that hit me was that NWMKDE.NLM was consuming over 700MB of RAM, or approximately 21% of the total installed memory in the machine.
Hmmm... What could be the matter, here? Other than Backup Exec, I have no Btrieve apps running on the server. All of the non-system databases run on MySQL on that box. TID # 7003770 references TID # 3216963 (formerly TID # 10058100), which makes reference to deleting the BTI.LCK file created in SYS:SYSTEM. I looked, and sure enough, BTI.LCK was a 0 length file. I deleted it, unloaded BSPXCOM.NLM, BTCPCOM.NLM, and NWMKDE.NLM, and reloaded all of them (I checked my BTI.CFG, and NWMKDE was configured to use 1MB of RAM for cache). Sure enough, memory consumption returned to normal.
Who knows?
Related posts:
- Unloading an unloadable NLM Unloading stubborn NetWare Loadable Modules can be an arduous task,...
- On the ungrateful nature of users and the OSS development community The concept of "free" is a broad one. Sometimes, grasping...
- WordPress, WooCommerce, and the elusive WP_MEMORY_LIMIT issue Proper placement of a variable's definition can be critical...
- OS/2 NetWare Requester FAQ While this FAQ does show its age, there are a...
- Novell Client for Windows (32-bit) Internal Error 0x00008993 This is an interesting one, and apparently either not documented...
Recent Posts
- Novell Client for Windows (32-bit) Internal Error 0x00008993
- Noisy utility company email
- The importance of Common User Access design guidelines in 2018
- Navigating Coinbase’s customer support
- Configuring the IOGEAR GWU627 wireless ethernet bridge device under ArcaOS (and OS/2)
Categories
Support Pages
Posts by Date
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
| « Jun | ||||||
| 1 | ||||||
| 2 | 3 | 4 | 5 | 6 | 7 | 8 |
| 9 | 10 | 11 | 12 | 13 | 14 | 15 |
| 16 | 17 | 18 | 19 | 20 | 21 | 22 |
| 23 | 24 | 25 | 26 | 27 | 28 | |
Log In
Email Notifications
RSS Feeds
Recent Comments
- LewisR on Installing Windows Server 2008 R2 x64 on the HP Proliant DL380 G4
- LewisR on Installing Windows Server 2008 R2 x64 on the HP Proliant DL380 G4
- justintd on Installing Windows Server 2008 R2 x64 on the HP Proliant DL380 G4
- LewisR on WP Post to PDF Enhanced
- pdfsc on WP Post to PDF Enhanced