[JoshuaZ]

Does anyone know of a good way to make 10.3 Server have a schedule for restarting? I would like to have it set up to auto shutdown and restart once a week, due to the fact that it occasionally just freezes.

Any and all advice is welcome.

[jay3ld]

Does The System Preferences have Energy Saver with Schedule??

[Chuckit]

Don't you think maybe it would be a good idea to fix whatever's freezing it?

[JoshuaZ]

Originally Posted by Chuckit

Don't you think maybe it would be a good idea to fix whatever's freezing it?

You'd think, but I believe it would involve upgrading from a B&W G3 to something better, which the department doesn't have in its budget.

[JoshuaZ]

Hey, I have a question. These freezes keep happening, and heres what my error log says right before it freezes up.

Jul 8 03:15:02 completelyinsane syslogd: restart
Jul 8 03:15:02 completelyinsane syslogd: hostname changed, "localhost" to "completelyinsane"
Jul 8 03:15:03 completelyinsane 700.daily.server.cyrus: Error: '/etc/MailServicesOther.plist' dictionary 'postfix' does not contain a dictionary with key 'log_rolling_days_enabled'.

Ideas?

[JoshuaZ]

lhost SystemStarter: Waiting for IPFilter
Jul 8 18:09:24 localhost last message repeated 6 times
Jul 8 18:09:25 localhost /usr/share/servermgrd/cgi-bin/servermgr_ipfilter: ipfw config:Info:Finished applying generated rules in 27585 ms
Jul 8 18:09:25 localhost /usr/share/servermgrd/cgi-bin/servermgr_ipfilter: ipfw config:Info:Timing: Finished applying NAT rules
Jul 8 18:09:25 localhost /usr/share/servermgrd/cgi-bin/servermgr_ipfilter: ipfw config:Info:Timing: Finished applying local rules
Jul 8 18:09:27 localhost SystemStarter: Waiting for IPFilter
Jul 8 18:09:30 localhost SystemStarter: Waiting for IPFilter
Jul 8 18:09:31 localhost ConsoleMessage: Disabling IPFilter
Jul 8 18:09:31 localhost SystemStarter: Disabling IPFilter
Jul 8 18:09:32 localhost SystemStarter: Startup complete.
Jul 8 18:12:02 localhost ntpd[259]: time set -0.013744 s
Jul 8 18:12:02 localhost ntpd[259]: synchronisation lost
Jul 8 18:12:10 localhost ConsoleMessage: Stopping network time synchronization
Jul 8 18:12:10 localhost ntpd[259]: ntpd exiting on signal 15

From a different freeze I had tonight. Any idea?

[JoshuaZ]

looks like someone was trying to pop into the server.

localhost sshd[1865]: Failed password for root from 212.0.140.11 port 36146 ssh2
Jul 9 01:17:24 localhost xinetd[393]: service ssh, IPV6_ADDRFORM setsockopt() failed: Protocol not available (errno = 42)
Jul 9 01:17:24 localhost xinetd[393]: START: ssh pid=1867 from=212.0.140.11
Jul 9 01:17:27 localhost sshd[1867]: Failed password for root from 212.0.140.11 port 36228 ssh2
Jul 9 01:17:27 localhost xinetd[393]: service ssh, IPV6_ADDRFORM setsockopt() failed: Protocol not available (errno = 42)
Jul 9 01:17:27 localhost xinetd[393]: START: ssh pid=1869 from=212.0.140.11
Jul 9 01:17:30 localhost sshd[1869]: Failed password for root from 212.0.140.11 port 36606 ssh2
Jul 9 01:17:30 localhost xinetd[393]: service ssh, IPV6_ADDRFORM setsockopt() failed: Protocol not available (errno = 42)
Jul 9 01:17:30 localhost xinetd[393]: START: ssh pid=1871 from=212.0.140.11
Jul 9 01:17:33 localhost sshd[1871]: Failed password for root from 212.0.140.11 port 37031 ssh2
Jul 9 01:17:33 localhost xinetd[393]: service ssh, IPV6_ADDRFORM setsockopt() failed: Protocol not available (errno = 42)
Jul 9 01:17:33 localhost xinetd[393]: START: ssh pid=1873 from=212.0.140.11
Jul 9 01:17:36 localhost sshd[1873]: Illegal user test from 212.0.140.11

[Simon Mundy]

Hard to say for sure, but it looks like your network is going up and down, or you're experiencing heavy traffic (enough to make you lose a connection). Do you have physical access to the box?

The repeated attempts to SSH to your box are the result of a very annoying but poorly aimed script kiddy attack. It loops through a bunch of obvious username/password combinations to see if it can gain access (how many admins do you reckon would have 'root/password' as their l/p? ). It's harmless in the same way a fly would hassle you through a picnic, but if enough attempts happen simultaeously you may go nuts trying to shoo them away I ended up changing my SSH port and that was the end of that.