Click to See Complete Forum and Search --> : how do I find out what is running during the night?


mis
03-28-2001, 11:13 AM
When I get up in the mornings I have screens of errors. They all start with DEBUG -- pg_ ??? --. Then they have something like UnUsed 0 Crashed 0 and more along those lines, I can write a few down tomorrow. But, it is only overnight. I am not getting any mail from cron but cron is running. I tried killing cron but got them still. How can I find out what is producing these and if it isn't anything to worry about how can I get it to stop reporting it? Also, I was in the middle of apt-get upgrade when this happened, am I screwed? I tried to do apt-get update when I got up and it had tons of errors about read already in progress. I left it alone and I am at work now so nothing I can really do now I don't guess.
Thanks,
Mis

:D DEBIAN :D

7
03-28-2001, 11:44 AM
Sorry I cant help. An actual hard problem.

Top!

bdg1983
03-28-2001, 12:01 PM
Plenty of strong coffee... ;)

Have you had a look at /var/log/messages or the crontab log file perhaps located in the same directory?

mis
03-28-2001, 02:29 PM
Originally posted by mdwatts:
Plenty of strong coffee... ;)

Have you had a look at /var/log/messages or the crontab log file perhaps located in the same directory?

I thougth /var/log/messages was for boot up problems? I will check though and look for a crontab log.

Molecule Man
03-28-2001, 02:39 PM
/var/log should have some usefull info.

bdg1983
03-28-2001, 05:30 PM
Yes, besides 'messages' in /var/log, you will find quite a few other log files. The cron log may be there.

X_console
03-28-2001, 10:31 PM
/var/log/messages isn't necessarily for boot up logs. Check your /etc/syslog.conf to find out what's being logged there as well as what's being logged where.

Lorithar
03-29-2001, 09:32 AM
*chortles*

And since this is occurring overnight, and only overnight...

at the command line try this command out (make sure you have a few minutes ...)
updatedb
This updates the 'locate' (file locator) database. -- on most systems this is cron'ed in at about 04:00.

If it is the cause, I'd need much more info (including the errors) to chase this.

mis
03-29-2001, 10:05 AM
Thanks for all the useful info but unfortunately while trying to install kde2 I broke things bad so I am going to have to reinstall. But this time I will write down things I do so I can be sure it doesn't break anything. Again thanks

Mis