i'm checking my logs and noticed my box was rebooted about a day ago but i didnt do anything. did anyone eles's box get rebooted? here is the log:

Jan 11 01:02:32 www init: Switching to runlevel: 0
Jan 11 01:02:32 www mgetty[522]: failed dev=ttyS0, pid=522, got signal 15, exiting
Jan 11 01:02:36 www sshd[319]: Received signal 15; terminating.
Jan 11 03:02:40 www kernel: Kernel logging (proc) stopped.
Jan 11 03:02:40 www kernel: Kernel log daemon terminating.
Jan 11 03:02:42 www exiting on signal 15
Jan 11 03:07:11 www syslogd 1.3-3: restart.

also, throughout my logs, i see A LOT of proftpd stuff..about every 15 minutes, a connection comes from localhost and then the log follows with:

localhost[127.0.0.1]) - FTP session closed.

anyone know whats up with this?

Yes, I see it too in my logs. And the FTP entries are probably tera-byte's monitors making sure the server is up.

My server rebooted about about 2 weeks ago.. I contacted tera-byte and they said it was probably because they moved it or something. Then someone in here said that they seem to reboot by themselves from time to time..

Saeed

do your /var/logs/messages have all those proftpd stuff in it.

My 4webspace server has the proftpd stuff in it to.
I think Chicken is right about why they are there.

/Tobias

http://www.has.it - Site using a server from 4webspace.net

Tera-Byte's monitors wouldn't probe from localhost. That indicates that the connection is originating from the local system, such as the server monitoring itself. Look for something in the crontab that may be spawning the connections every 15 minutes.

Jepp, CJB is right. In the crontab there is a servercheck every 15.

# Monitor services to make sure everything is still okay.
0,15,30,45 * * * * root /usr/local/sbin/swatch >>/var/cobalt/adm.log 2>&1

Sorry, yes I missed that. If you see this:

Jan 14 13:28:30 xxxxxx proftpd[30301]: xxx.xxx.xxx.xxx (whatsup.tera-byte.com[204.209.57.11]) - FTP session closed.

-then *this* is tera-byte's monitoring.

is it okay to kill the local monitoring or should we just leave it?

Well, I'd personally leave it since if it finds a service down it will automatically restart the service (not a bad thing really). Up to you.