Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

"subsys locked" message

  • 12-12-2002 4:01pm
    #1
    Lemming
    Registered Users, Registered Users 2 Posts: 14,149 ✭✭✭✭


    FINALLY got ntop 2.1.3 running

    christ, for such an *ahem* simple program, it is extrodinarily difficult to get running :mad:

    Anyway, I stopped the service to edit the init.d/ntop file (to start the daemon with various additional flags), but when i try to restart it gives me an "ok" message. If I then run '/etc/rc.d/init.d/ntop status', I get a "ntop dead but subsys locked" message.

    Anyone know how to rectify this little problem? (or where I can find the info for it?)

    At this stage I'm sick and tired of this f*cking program :mad:


Comments

  • #2
    dahamsta
    Banned (with Prison Access) Posts: 16,659 ✭✭✭✭dahamsta


    It probably exited improperly and left a PID file hanging around the filesystem somewhere. Have a look in /tmp and /var/run to see if there's an ntop.pid file, or else (if you're running RHL) run 'updatedb &' and 'locate ntop.pid'. If that doesn't find it, just run 'locate ntop | less' and have a poke through the results, see if anything jumps out at you. If you find it you can just delete it.

    That doesn't solve the underlying problem though, obviously. Did you check /var/log/messages? Did you see if there's an ntop logfile in /var/log?

    adam


  • #3
    Zaltais
    Closed Accounts Posts: 304 ✭✭Zaltais


    RedHat keeps it's lock files in /var/lock/subsys

    So for samba the file is /var/lock/subsys/smb

    file usually has the same name as the process so for ntop it's probably

    /var/lock/subsys/ntop

    If a daemon exits improperly and gets locked, deleting this guy usually does the trick - but it probably died because of something dodgy in the config file (or at least that's always been what's wrong when it's happened to me) so remember to go through each part of the config file carefully if it doesn't start again the second time...

    Cheers,

    Zaltais


  • #4
    Lemming
    Registered Users, Registered Users 2 Posts: 14,149 ✭✭✭✭Lemming


    I think there's a problem with ntop itself. It keeps starting no problem, and then either after about 5 mins it locks, or if I pass certain logging flags with the start up, it locks right away.

    Apparently other people on the ntop mailing list have been experiencing similar problems with the 5 min. thingy.


  • #5
    Zaltais
    Closed Accounts Posts: 304 ✭✭Zaltais


    Sorry, I've no idea mate.. maybe a problem with file permissions stopping ntop writing a logfile or something?

    maybe have a look at /var/log/messages and see if there's any more info in there that may help.

    I've never installed it myself so I couldn't really say.

    Let us know how you get on.


Advertisement