find: /proc/irq/: No such file or directory

Discussion in 'Bug Reports' started by jkeegan, Dec 26, 2009.

  1. jkeegan

    jkeegan New Member

    Just started getting this, on 4.0.11 or .12 Litespeed fails to start, throwing the following errors:

    [bin]# ./lswsctrl start
    find: /proc/irq/: No such file or directory
    read(): Invalid argument
    read(): Illegal seek
    [ERROR] Failed to start lshttpd!
    find: /proc/irq/: No such file or directory
    read(): Invalid argument
    read(): Illegal seek
    [ERROR] Failed to start lshttpd!
    find: /proc/irq/: No such file or directory
    read(): Invalid argument
    read(): Illegal seek
    [ERROR] Failed to start lshttpd!
    find: /proc/irq/: No such file or directory
    read(): Invalid argument
    read(): Illegal seek
    [ERROR] Failed to start lshttpd!
    find: /proc/irq/: No such file or directory
    read(): Invalid argument
    read(): Illegal seek
    [ERROR] Failed to start lshttpd!
    find: /proc/irq/: No such file or directory
    read(): Invalid argument
    read(): Illegal seek
    [ERROR] Failed to start lshttpd!
    find: /proc/irq/: No such file or directory
    read(): Invalid argument
    read(): Illegal seek
    [ERROR] Failed to start lshttpd!
    find: /proc/irq/: No such file or directory
    read(): Invalid argument
    read(): Illegal seek
    [ERROR] Failed to start lshttpd!
    find: /proc/irq/: No such file or directory
    read(): Invalid argument
    read(): Illegal seek
    [ERROR] Failed to start lshttpd!
    [bin]#


    Can't seem to work it out, Litespeed is dead in the water now. Just started happening for seemingly no reason.

    Thanks in advance for a quick response.
  2. mistwang

    mistwang LiteSpeed Staff

    Which version did you upgrade from?
    Are you using a VPS?
    "find: /proc/irq/ ..." is normal, it does not hurt. the error regarding "read()" is abnormal, Is there anything in error log?
    Can do "strace /usr/local/bin/lsws/lshttpd -d" and send us the output?
  3. jkeegan

    jkeegan New Member

    I ended up deleting the installation and reinstalling it... Not sure what the issue was but the reinstallation seemed to solve the issue. I'll be sure to update this thread if I see it again...

Share This Page