Re: weird save-entropy behaviour
On Monday 16 November 2009 00:58, Mel Flynn wrote: > Does the cron log (/var/log/cron) show that it was run as operator around > the time it started? > /usr/sbin/cron[47350]: (operator) CMD (/usr/libexec/save-entropy) > > Even if it wasn't, I don't see a reason for such a buildup. Unlesssince > stdin isn't sending anything, it could be the scripts wait indefinitely for > user confirmation, then finally get killed off by some limit. There should > be some hint at that in /var/log/messages around 5:50. > The script should probably do mv -f in line 76. > you were right. there was something at the messages. Nov 15 05:50:49 hostname sshd[1126]: error: accept: Software caused connection abort Nov 15 05:50:49 hostname last message repeated 6 times weird. the only thing in auth.log about sshd[1126] is: Nov 13 12:31:51 hostname sshd[1126]: Server listening on :: port 22. Nov 13 12:31:51 hostname sshd[1126]: Server listening on 0.0.0.0 port 22. and the message that was in the messages log too. -- Real programmers don't document. If it was hard to write, it should be hard to understand. signature.asc Description: This is a digitally signed message part.
Re: weird save-entropy behaviour
On Sunday 15 November 2009 23:38:10 Ed Jobs wrote: > On Monday 16 November 2009 00:12, Mel Flynn wrote: > > Did the operator uid change or perhaps shared with another uid? > > Check both `id operator` and `id 2`. > > > > Secondly, why did this stop? Seems like a weird question to ask, but > > since this script is supposed to run every 11 minutes, there should not > > be a reason for this to stop, if there's a race condition. > > # id operator > uid=2(operator) gid=5(operator) groups=5(operator) > # id 2 > uid=2(operator) gid=5(operator) groups=5(operator) > > As for the orer part, why did it stop, i really have no clue. All the > messages arrived at root's mailbox at 5:57, tho the date in them said that > they were sent at 5:50. > It's really strange because I was locked out from the computer at 2:29, so > it's not something I did. and there's nothing that cron runs at that time. Does the cron log (/var/log/cron) show that it was run as operator around the time it started? /usr/sbin/cron[47350]: (operator) CMD (/usr/libexec/save-entropy) Even if it wasn't, I don't see a reason for such a buildup. Unlesssince stdin isn't sending anything, it could be the scripts wait indefinitely for user confirmation, then finally get killed off by some limit. There should be some hint at that in /var/log/messages around 5:50. The script should probably do mv -f in line 76. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: weird save-entropy behaviour
On Monday 16 November 2009 00:12, Mel Flynn wrote:
>
> Did the operator uid change or perhaps shared with another uid?
> Check both `id operator` and `id 2`.
>
> Secondly, why did this stop? Seems like a weird question to ask, but since
> this script is supposed to run every 11 minutes, there should not be a
> reason for this to stop, if there's a race condition.
>
# id operator
uid=2(operator) gid=5(operator) groups=5(operator)
# id 2
uid=2(operator) gid=5(operator) groups=5(operator)
As for the orer part, why did it stop, i really have no clue. All the messages
arrived at root's mailbox at 5:57, tho the date in them said that they were
sent at 5:50.
It's really strange because I was locked out from the computer at 2:29, so
it's not something I did. and there's nothing that cron runs at that time.
by the way:
the mails that i got were not only about /var/db/entropy/saved-entropy.2, but
/var/db/entropy/saved-entropy.{1,2,3,4,5,6,8} as well
--
Real programmers don't document. If it was hard to write, it should be hard to
understand.
signature.asc
Description: This is a digitally signed message part.
Re: weird save-entropy behaviour
On Sunday 15 November 2009 17:30:02 Ed Jobs wrote: > Yesterday, i noticed a very weird behaviour on my computer (which is > running 8.0-RC3 btw. > The shells were not responding and the load was insane, and constantly > going up. At the time i managed to lock myself out, the load was 84 and > growing (i have a screenshot if anyone is interested). > > That happened last night. Today, the computer was ok and i managed to ssh > into it. The root account was spammed with two types of cron mails. > > half of them said: > mv: /var/db/entropy/saved-entropy.2: No such file or directory > > and the other half said: > override r operator/operator for /var/db/entropy/saved-entropy.2? > (y/n [n]) not overwritten > > So i know that it's the save-entropy cron job, but i doubt that was > supposed to happen, and i have never touched that directory. Anyone has an > idea? Did the operator uid change or perhaps shared with another uid? Check both `id operator` and `id 2`. Secondly, why did this stop? Seems like a weird question to ask, but since this script is supposed to run every 11 minutes, there should not be a reason for this to stop, if there's a race condition. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
