Re: netbsd 6 instance on amazon

[el kalin <kalin%el.net@localhost>]

not really. this machine it's pretty busy and the php log is dumped in the syslog too. there are no other system messages - except php warnings. 

i do have a pre-problem image of this machine which i did put up and now monitoring too. but there has been a lot of work done since then and i rather resolve this because moving everything over will be a very problematic at this point....

the strange thing is that it always happens pretty much exactly at the same time. and there are no cron jobs that are scheduled for that time. but it's always a few minutes before the default daily cron at 3:15. like i said it doesn't happened every day but this week happened twice and it gets to be annoying since i don't get to know about it until later in the morning...

thanks...

On Sat, Nov 2, 2013 at 11:20 AM, matthew sporleder <msporleder%gmail.com@localhost> wrote:

On Sat, Nov 2, 2013 at 7:10 AM, el kalin <kalin%el.net@localhost> wrote:
>
>
> hi all...
>
> i'm running an netbsd 6 (6.0 NetBSD 6.0 (XEN3_DOMU) amd64) instance on
> amazon since december last year. everything was working nicely until about 2
> months ago when the system sporadically started rebooting itself. it happens
> once a week on average. sometimes twice. the last line in the messages log
> always looks like this:
>
> ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
> ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@Nov  2
> 07:21:55 ip-10-62-123-59 syslogd[310]: restart
>
>
> it always happens right before the default daily cron (which is set for 3:15
> am by default). around 3:12 am.
>
> the only things the machine runs are httpd and mysqld..
>
> has anybody experienced this? i would greatly appreciate any thoughts that
> can resolve this problem...
>
> thanks...

Is there anything further up in the log to indicate a sender of that message?

Also, have you tried terminating and rebuilding (caveat data loss,
etc) to get onto another amazon host?