Here you go (IP addresses removed):
12/07,00:00:04 ROTATE rushd.log rotated. pid=203, 0/1 busy, ONLINE
12/07,00:00:04 ROTATE wayne RUSHD 102.42a9c PID=203 Boot=12/04/09,14:07:03
12/07,09:47:26 SECURITY Daemon changed to Offline by root@wayne[], Remark:offline by dbrowne via login script state (offline) by root@wayne[]
12/07,12:20:35 SECURITY Daemon changed to Online by root@wayne[], Remark:online by dbrowne via logout script state (online) by root@wayne[]
12/07,12:20:36 SECURITY Daemon changed to Getoff by root@wayne[] state (getoff) by root@wayne[]
12/07,12:20:40 INIT.D Shutdown script '/usr/local/rush/etc/S99rush stop'
12/07,12:20:40 EXIT Shutdown script '/usr/local/rush/etc/S99rush stop'
---------
12/07,12:21:34 INIT.D Startup script '/usr/local/rush/etc/S99rush start'
12/07,12:21:34 INIT.D Executing: ( /usr/local/rush/etc/S99rush waitlocal && cd /usr/local/rush/var && /usr/libexec/StartupItemContext /usr/local/rush/bin/rushd ) &
12/07,12:21:34 INIT.D Local hostname wayne won't resolve (ping: cannot resolve wayne: Unknown host): 10 sec retries
12/07,12:21:45 LICENSE validated with server vegas
12/07,12:21:45 LICENSE expires 03/15/2036
12/07,12:21:45 START wayne RUSHD 102.42a9c PID=189 Boot=12/07/09,12:21:45 Online
12/07,12:21:45 INFO TCP listening on port 696, service 'rushd', sockfd=4
12/07,12:21:45 INFO UDP listening on port 696, service 'rushd', sockfd=5
12/07,12:21:45 CHECKPOINT START: Loading /usr/local/rush/var/jobs-checkpoint
12/07,12:21:45 CHECKPOINT DONE
12/07,12:21:51 SECURITY Daemon changed to Offline by root@wayne[], Remark:offline by dbrowne via login script state (offline) by root@wayne[172.21.7.9]
12/07,13:57:54 PUSH /usr/local/rush/etc/hosts pushed from ?@vegas:52291[]
12/07,13:58:45 INFO/HOST Reloading /usr/local/rush/etc/hosts
On Dec 7, 2009, at 12:52 PM, Greg Ercolano wrote:
[posted to rush.general]
Mr. Daniel Browne wrote:
> [posted to rush.general]
>
> Hi Greg,
>
> The 102.42a9c update seems to have fixed most of our operation =
> problems with Rush on SL (we love the new GUI look too, by the way), but =
> there is one thing we've noticed; rush on SL machines seems to stop =
> responding after pushing a hosts file. The failure happens even if the =
> file hasn't been changed. This requires you to restart the rush daemon, =
> much like how before this release we had to do whenever rush on an SL =
> machine stopped responding.
Hmm, can you send me the contents of the rushd.log from that machine
where the daemon stopped responding?
--
Greg Ercolano, erco@(email surpressed)
Seriss Corporation
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)
----------
Dan "Doc" Browne
System Administrator
Evil Eye Pictures
d.list at evileyepictures.com
Office: (415) 777-0666
|