Daemon bombed out, want to see why

kinetik · 06-08-2006, 06:11 AM

Hi again buddies!

I have a daemon running on my server, daemon name ibmproxy.

For some strange reason it just stopped! I've checked the messages logfile in /var/log, but nothing of interest there. If anything, it just shows that it was stopped by a user and started up successfully again 1 minute later.

Going by that, it should have worked all the time, but 5 minutes later it just wasn't running any more and I can't figure out why...

Any ideas please?

Thanks!

unSpawn · 06-08-2006, 06:41 AM

- are all resources or processes it depends on available or running?
- does it support debug level output you could increase?
- can you run it manually from strace?

kinetik · 06-08-2006, 07:46 AM

Hi unSpawn

I'm afraid your answers are a bit too advanced for my level of Nix-knowledge at this stage...

I'll try to answer as best I can though:

1. The process is fine now, but only after I started it up again
2. I have no idea if it supports debug level output, or even what debug level output is and how to use it
3. I'm not quite sure how strace works, but I can reseach it. One question for now about this: Is there a way to use this tool on already running processes?

Thanks for your reply!

unSpawn · 06-08-2006, 11:06 AM

I'm afraid your answers are a bit too advanced for my level of Nix-knowledge at this stage...
My apologies. Entirely my fault explaining enough.

1. The process is fine now, but only after I started it up again
I mean, reading the docs (/usr/share/doc/?), does it depend on other stuff? In other words: what is required for running this?

2. I have no idea if it supports debug level output, or even what debug level output is and how to use it
There's bound to be a man page and documentation for it. Maybe mosey on over to the IBM site?

3. I'm not quite sure how strace works, but I can reseach it. One question for now about this: Is there a way to use this tool on already running processes?
Sure: "man strace" and you'll notice the "-p" flag with which you can supply the process' PID. Best used with "-v -o /tmp/strace.log" which gives more verbose output and logs to a file for easy perusal.

nx5000 · 06-08-2006, 11:14 AM

Quote:

Originally Posted by unSpawn

Sure: "man strace" and you'll notice the "-p" flag with which you can supply the process' PID. Best used with "-v -o /tmp/strace.log" which gives more verbose output and logs to a file for easy perusal.

I would also add the flag -f which can help understand child processes communication

Code:

strace -f -v -o /tmp/strace.log -p <pid>

kinetik · 06-09-2006, 02:50 AM

unSpawn, nx5000, thanks alot for your input up to now.

I will give this a try and post my findings a bit later.

To unSpawn:

No need to apologize buddy! If anything it's me that should apologize for my ignorance

Thanks again for your help friend, I really do appreciate it.