Solved (SOLVED) u2ec: Error unlocking 18: 9 Bad file descriptor

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

Ro berto

Regular Contributor
Hello fellow members:

I am trying to print a pdf, my hp printer which does not have wireless capability is connected through usb to the router (RT-AC86U).
Usually when having trouble printing I would just execute
Code:
service restart_u2ec
and the printer would work again and print the document.

But now it doesn't want :/

When taking a look at system log I see the following:

Code:
Jul 24 12:00:13 dropbear[5280]: Child connection from 192.168.1.10:41956
Jul 24 12:00:13 dropbear[5280]: Password auth succeeded for 'robertozombie' from 192.168.1.10:41956
Jul 24 12:00:13 rc_service: service 5283:notify_rc restart_u2ec
Jul 24 12:00:13 custom_script: Running /jffs/scripts/service-event (args: restart u2ec)
Jul 24 12:00:14 dropbear[5280]: Exit (robertozombie) from <192.168.1.10:41956>: Exited normally
Jul 24 12:00:21 u2ec: Error unlocking 14: 9 Bad file descriptor

The last line shows an error, I don't know if this is the culprit, what do you think?

Thanks
 

Ro berto

Regular Contributor
Just to add,

I already rebooted the printer and the router, and still cannot get it to print.
 

ColinTaylor

Part of the Furniture
Are you still getting the Bad file descriptor message in your log?

Maybe you have run out of them. SSH into the router and post the output of these commands:

cat /proc/sys/fs/file-nr

ulimit -a
 

Ro berto

Regular Contributor
Hi Colin,

Yeah, still getting the bad file descriptor message in the log, here are the outputs of the commands you wrote:

Code:
[email protected]:/tmp/home/root# cat /proc/sys/fs/file-nr
1344    0       43984
[email protected]:/tmp/home/root# ulimit -a
-f: file size (blocks)             unlimited
-t: cpu time (seconds)             unlimited
-d: data seg size (kb)             unlimited
-s: stack size (kb)                2048
-c: core file size (blocks)        0
-m: resident set size (kb)         unlimited
-l: locked memory (kb)             64
-p: processes                      1719
-n: file descriptors               1024
-v: address space (kb)             unlimited
-w: locks                          unlimited
-e: scheduling priority            0
-r: real-time priority             0
[email protected]:/tmp/home/root#

Thanks
 

Ro berto

Regular Contributor
Whenever I restart the printer service, the printer prints a document that I sent on the 1st of July, and it stays on the "printing status" (see attached pic), cancel or restart seems to do nothing...
Capture.PNG


Roberto
 

Ro berto

Regular Contributor
Last edited:

Ro berto

Regular Contributor
Out of curiosity, what do you mean with this? (in bolds)

Are you still getting the Bad file descriptor message in your log?

Maybe you have run out of them. SSH into the router and post the output of these commands:

cat /proc/sys/fs/file-nr

ulimit -a
 

ColinTaylor

Part of the Furniture
Out of curiosity, what do you mean with this? (in bolds)
There are limits on the amount of system resources that can be used. So for example, if you had some rogue process that was in a loop opening more and more files you would eventually reach the limit on the number of files that can be open at a given time.
 

Ro berto

Regular Contributor
The root cause problem were the faulty windows drivers vs. HP's drivers

see this post
 

Similar threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top