- 290: data system, Site russter, Fri 24-Jun-2005 16:10:16 MDT, How to restart covar process on russter2.
% for some reason the covar process stopped on May 1...here's what I see:
dir /usr/local/aster/projects/NIWOT/results/covar/
total 35224
drwxrwsr-x 2 maclean aster 20480 Apr 30 18:10 ./
drwxrwsr-x 3 maclean aster 4096 Sep 14 1998 ../
-rw-rw-r-- 1 sburns aster 286828 Jan 2 17:15 nwt.050101.nc
-rw-rw-r-- 1 sburns aster 286828 Jan 3 17:10 nwt.050102.nc
-rw-rw-r-- 1 sburns aster 286828 Jan 4 17:05 nwt.050103.nc
-rw-rw-r-- 1 sburns aster 286828 Jan 5 17:10 nwt.050104.nc
-rw-rw-r-- 1 sburns aster 286828 Jan 6 15:17 nwt.050105.nc
-rw-rw-r-- 1 sburns aster 286828 Jan 6 17:10 nwt.050106.nc
-rw-rw-r-- 1 sburns aster 286828 Jan 8 17:15 nwt.050107.nc
etc, etc
-rw-rw-r-- 1 sburns aster 296024 Apr 24 18:10 nwt.050423.nc
-rw-rw-r-- 1 sburns aster 296024 Apr 25 18:15 nwt.050424.nc
-rw-rw-r-- 1 sburns aster 296024 Apr 26 18:15 nwt.050425.nc
-rw-rw-r-- 1 sburns aster 296024 Apr 27 15:02 nwt.050426.nc
-rw-rw-r-- 1 sburns aster 296024 Apr 27 18:10 nwt.050427.nc
-rw-rw-r-- 1 sburns aster 296024 Apr 28 18:10 nwt.050428.nc
-rw-rw-r-- 1 sburns aster 296024 Apr 29 18:05 nwt.050429.nc
-rw-rw-r-- 1 sburns aster 296024 May 1 15:52 nwt.050430.nc
-rw-rw-r-- 1 sburns aster 273524 May 1 15:52 nwt.050501.nc
so i did:
mv /usr/local/aster/projects/NIWOT/results/covar/nwt.050501.nc .
then, cd /usr/local/isff/aster/projects/NIWOT/scripts/
e covar_redo
set begin = "2005 may 01 00:00"
then i did:
covar_redo
PROJECT=NIWOT OPS=ops1
and see:
dir /usr/local/aster/projects/NIWOT/results/covar/ | grep May
drwxrwsr-x 2 maclean aster 20480 May 11 08:49 ./
-rw-rw-r-- 1 sburns aster 296024 May 1 15:52 nwt.050430.nc
-rw-rw-r-- 1 sburns aster 294784 May 11 08:49 nwt.050501.nc
-rw-rw-r-- 1 sburns aster 294784 May 11 08:49 nwt.050502.nc
-rw-rw-r-- 1 sburns aster 154384 May 11 08:50 nwt.050503.nc
etc, etc.
then i ftped these files to specialk and restarted, "fluxcalcs.csh".
back on russter2 i did "check_aster"...ie:
check_aster
Wed May 11 08:59:24 MDT 2005
------------- Environment -------------
PROJECT = NIWOT, OPS=ops1
------------- Server tasks -------------
host user pid start exectime process
russter2 sburns 3734 Apr29 ? 00:00:00 adamserver
russter2 sburns 3736 Apr29 ? 00:00:17 nc_server
------------- Ingest tasks -------------
host user pid start exectime process
russter2 sburns 3738 Apr29 ? 00:00:00 ingest
russter2 sburns 4579 Apr29 ? 00:01:15 quacker
------------- Archive tasks -------------
host user pid start exectime process
russter2 root 4590 Apr29 ? 00:00:27 archive quacker .
-------------- Covar calcs --------------
host user pid start exectime process
-------------- X processes --------------
host user pid start exectime process
russter2 sburns 28967 07:40 pt00:00:02 xcockpit -a quacker -xrm *Monitor.f
-------------- Ingest Statistics ----------
station port status up since sample/sec serialErrs
quacker 1074 open Apr 29 11:37 36.00 0
-------------- Living adams --------------
quacker
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/hda3 5162828 753656 4146912 16% /usr/local
/dev/hda8 51088492 34082296 14410900 71% /data
-----------------------------------------
Wed May 11 08:59:25 MDT 2005
from "check_aster" it looks like the covar process is not running...so
i restarted the covar process on russter2, ie:
/usr/local/isff/aster/projects/NIWOT/scripts[81]: covar_quacker
PROJECT=NIWOT OPS=ops1
[1] 29483
now check_aster shows:
-------------- Covar calcs --------------
host user pid start exectime process
russter2 sburns 29483 09:01 pt00:00:00 covar -S -a quacker
ps -gaxu | grep cov
root 9 0.0 0.0 0 0 ? SW Apr29 0:00 [mdrecoveryd]
sburns 29483 0.4 0.6 3076 1664 pts/0 S 09:01 0:00 covar -S -a quacker
- 268: data system, Site russter, Mon 21-Mar-2005 15:12:45 MST, Data Archiving stopped on Feb 5, 2005
Sat, Feb 5 at 12:30 MST
-----------------------
the archiving of the hi-rate data had stopped..but it looks
like the covar data are still there...here's what I see:
-rw-rw-r-- 1 root aster 33921934 Feb 4 09:00 nwt050204.080000
-rw-rw-r-- 1 root aster 34267078 Feb 4 17:00 nwt050204.160000
-rw-rw-r-- 1 root aster 1409028 Feb 4 17:20 nwt050205.000000
-rw-rw-r-- 1 root aster 593920 Feb 5 12:40 nwt050205.193153
(it stopped at 17:20 yesterday...which is exactly the time i logged out!)...
sburns pts/0 toyon.mmm.ucar.e Fri Feb 4 08:16 - 17:20 (09:03)
to get things regoing again i did: "ndaqrestart quacker" on russter2
more info:
tail -100 /var/log/local/aster.log | more
Feb 3 16:24:59 russter2 ingest(quacker)[5132]: quacker russter2.32776 socket closed, 5 active connections
Feb 3 16:25:02 russter2 ingest(quacker)[5132]: quacker russter2.32778 socket closed, 4 active connections
Feb 3 16:25:11 russter2 ingest(quacker)[5132]: quacker russter2.32774 socket closed, 3 active connections
Feb 4 00:00:15 russter2 archive(quacker)[5143]: Opened: ./all/nwt050204.000000
Feb 4 00:00:15 russter2 covar[5153]: quacker@russter2: midnight rollover. Sample time: 2005 Feb 04 j035 00:00:00
Feb 4 00:10:15 russter2 nc_server[4348]: Created: /usr/local/aster/projects/NIWOT/results/covar/nwt.050204.nc
Feb 4 08:00:15 russter2 archive(quacker)[5143]: Opened: ./all/nwt050204.080000
Feb 4 08:16:36 russter2 ingest(quacker)[5132]: russter2 port 32780: setsockopt SO_SNDBUF=16384
Feb 4 08:16:36 russter2 ingest(quacker)[5132]: quacker DGRAM socket connected to russter2:32780, 3 active connections
Feb 4 16:00:15 russter2 archive(quacker)[5143]: Opened: ./all/nwt050204.160000
Feb 5 00:00:15 russter2 archive(quacker)[5143]: Opened: ./all/nwt050205.000000
Feb 5 00:00:15 russter2 covar[5153]: quacker@russter2: midnight rollover. Sample time: 2005 Feb 05 j036 00:00:00
Feb 5 00:10:20 russter2 nc_server[4348]: Created: /usr/local/aster/projects/NIWOT/results/covar/nwt.050205.nc
Feb 5 00:10:20 russter2 nc_server[4348]: Closing: /usr/local/aster/projects/NIWOT/results/covar/nwt.050203.nc
Feb 4 17:20:07 russter2 ingest(quacker)[5132]: quacker russter2.32780 socket closed, 3 active connections
Feb 5 00:20:07 russter2 archive(quacker)[5143]: EOF received on input from quacker@russter2
Feb 5 00:20:07 russter2 archive(quacker)[5143]: archiving stopped for quacker
Feb 4 17:20:07 russter2 ingest(quacker)[5132]: quacker russter2.32780 socket closed, 2 active connections
Feb 5 09:51:25 russter2 ingest[4350]: Unknown ADAM: 61.152.96.211
Feb 5 12:31:49 russter2 ingest[4350]: quacker ingest restarted, sending hangup to previous ingest, pid 5132
Feb 5 12:31:49 russter2 ingest(quacker)[5132]: quacker: signal SIGHUP (1) received
Feb 5 12:31:49 russter2 ingest(quacker)[5132]: quacker russter2.32784 socket closed, 1 active connections
Feb 5 12:31:49 russter2 ingest(quacker)[5132]: quacker shutting down
- 166: data system, Site quacker, Wed 03-Mar-2004 14:48:55 MST, Quacker Shutdown on night of 2/11
% quacker crash on the night of 2/11. . .brought back up the next
morning at ~9am. (this looks similar to the problem back in Nov, when
temperature was extremely cold.).
[root@quacker cuff]# /sbin/lsusb
Bus 001 Device 001: ID 0000:0000 Virtual Hub
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.00
bDeviceClass 9 Hub
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0000 Virtual
idProduct 0x0000 Hub
bcdDevice 0.00
iManufacturer 0
etc, etc...
Feb 11 21:44:02 quacker timeupdate[15026]: Adjusted clock 199 milliseconds forward. RPC calls took 4 milliseconds
Feb 11 22:44:03 quacker timeupdate[15026]: Adjusted clock 198 milliseconds forward. RPC calls took 4 milliseconds
Feb 11 22:45:37 quacker kernel: usb-uhci.c: interrupt, status 3, frame# 576
Feb 11 22:50:04 quacker chemcontrol: chemcontrol reset: Wed Feb 11 22:50:00 2004
Feb 11 22:53:30 quacker kernel: usb-uhci.c: interrupt, status 3, frame# 576
Feb 11 22:56:05 quacker kernel: usb-uhci.c: interrupt, status 3, frame# 576
Feb 11 23:01:04 quacker kernel: usb-uhci.c: interrupt, status 3, frame# 576
Feb 11 23:05:14 quacker kernel: usb-uhci.c: interrupt, status 3, frame# 576
Feb 11 23:14:35 quacker kernel: usb-uhci.c: interrupt, status 3, frame# 576
Feb 11 23:29:03 quacker kernel: usb-uhci.c: interrupt, status 3, frame# 576
Feb 11 23:37:04 quacker kernel: usb-uhci.c: interrupt, status 3, frame# 576
Feb 11 23:40:02 quacker kernel: usb-uhci.c: interrupt, status 3, frame# 576
Feb 11 23:44:04 quacker timeupdate[15026]: Adjusted clock 758 milliseconds forward. RPC calls took 4 milliseconds
Feb 11 23:52:06 quacker kernel: usb-uhci.c: interrupt, status 3, frame# 576
Feb 11 23:52:06 quacker kernel: usb.c: USB disconnect on device 00:07.2-1.1 address 3
Feb 11 23:52:06 quacker kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000998
Feb 11 23:52:06 quacker kernel: printing eip:
Feb 11 23:52:06 quacker kernel: c8866e46
Feb 11 23:52:06 quacker kernel: *pde = 00000000
Feb 11 23:52:06 quacker kernel: Oops: 0002
Feb 11 23:52:06 quacker kernel: CPU: 0
Feb 11 23:52:06 quacker kernel: EIP: 0010:[] Not tainted
Feb 11 23:52:06 quacker kernel: EFLAGS: 00010246
Feb 11 23:52:06 quacker kernel: eax: 00000000 ebx: 00000000 ecx: 00000000 edx: c797781c
Feb 11 23:52:06 quacker kernel: esi: c797781c edi: 00000000 ebp: c7977800 esp: c79fdf40
Feb 11 23:52:06 quacker kernel: ds: 0018 es: 0018 ss: 0018
Feb 11 23:52:06 quacker kernel: Process khubd (pid: 82, stackpage=c79fd000)
Feb 11 23:52:06 quacker kernel: Stack: c7977874 c7977874 c8868780 c8868760 c7b11ce4 c7f87c00 c883c0e5 c7f87c00
Feb 11 23:52:06 quacker kernel: c7977800 00000000 00000000 c7f87b0c 00000000 00000100 c7f86c8c c883e190
Feb 11 23:52:06 quacker kernel: c7f87b0c c7f87a0c c7f87a00 c7f86ca8 c7f86cb4 c7f87a00 c7f86c8c c883e81b
Feb 11 23:52:06 quacker kernel: Call Trace: [] [] [] [] []
Feb 11 23:52:06 quacker kernel: [] [] []
Feb 11 23:52:06 quacker kernel:
Feb 11 23:52:06 quacker kernel:
Feb 11 23:52:06 quacker kernel: Code: 89 98 98 09 00 00 8b 4c 24 04 ff 46 58 0f 8e cb 03 00 00 83
Feb 11 23:59:46 quacker kernel: <4>usb-uhci.c: interrupt, status 3, frame# 576
Feb 12 00:02:48 quacker kernel: usb-uhci.c: interrupt, status 3, frame# 576
Feb 12 00:04:33 quacker kernel: usb-uhci.c: interrupt, status 3, frame# 576
Feb 12 00:11:31 quacker kernel: usb-uhci.c: interrupt, status 3, frame# 576
Feb 12 00:13:11 quacker kernel: usb-uhci.c: interrupt, status 3, frame# 576
Feb 12 00:17:19 quacker kernel: usb-uhci.c: interrupt, status 3, frame# 576
Feb 12 00:19:40 quacker last message repeated 2 times
Feb 12 00:22:32 quacker kernel: usb-uhci.c: interrupt, status 3, frame# 576
Feb 12 00:24:59 quacker kernel: usb-uhci.c: interrupt, status 3, frame# 576
Feb 12 00:26:40 quacker kernel: usb-uhci.c: interrupt, status 3, frame# 576
Feb 12 00:28:51 quacker kernel: usb-uhci.c: interrupt, status 3, frame# 576
Feb 12 00:30:25 quacker last message repeated 2 times
Feb 12 00:32:59 quacker kernel: usb-uhci.c: interrupt, status 3, frame# 576
Feb 12 00:34:00 quacker kernel: usb-uhci.c: interrupt, status 3, frame# 576
etc, etc...
eventually the data system shuts down...
Feb 12 09:05:02 quacker kernel: usb-uhci.c: interrupt, status 3, frame# 811
Feb 12 09:05:06 quacker sshd[5855]: Accepted password for cuff from 10.0.0.1 port 37913 ssh2
Feb 12 09:05:07 quacker kernel: usb-uhci.c: interrupt, status 3, frame# 1725
Feb 12 09:05:07 quacker sshd(pam_unix)[5857]: session opened for user cuff by (uid=500)
Feb 12 09:05:12 quacker kernel: usb-uhci.c: interrupt, status 3, frame# 591
Feb 12 09:05:17 quacker kernel: usb-uhci.c: interrupt, status 3, frame# 1505
...couldn't kill the sio process:
[cuff@quacker adam]$ ./stop_adam
Waiting for sio to die ... 15030
6015
.15030
6015
.15030
6015
.15030
6015
.15030
6015
.15030
6015
.15030
6015
.15030
6015
. failed, still running
[cuff@quacker adam]$ ps -elf | grep sio
000 D root 15030 1 0 65 -10 - 340 down Jan02 ? 01:52:56 sio
000 D root 6015 1 0 65 -10 - 340 down 09:08 pts/1 00:00:00 sio
000 S cuff 6055 5858 0 73 0 - 440 pipe_w 09:15 pts/1 00:00:00 grep sio
eventually had to reboot to get it working again...the reboot was
fine.
- 137: data system, Site quacker, Tue 11-Nov-2003 10:12:58 MST, Rash of 4am Shutdowns.
November 11, 2003.
In the past week there has been many 4am shutdowns.
Here's a list of the days with 4am shutdowns:
-rw-rw-r-- 1 aturnip aster 9986888 Oct 22 04:06 nwt031022.080000
-rw-rw-r-- 1 aturnip aster 14813400 Oct 26 04:04 nwt031026.080000
-rw-rw-r-- 1 aturnip aster 15019180 Nov 1 04:21 nwt031101.080000
-rw-rw-r-- 1 aturnip aster 14981538 Nov 2 04:20 nwt031102.080000
-rw-rw-r-- 1 aturnip aster 14931314 Nov 4 04:20 nwt031104.080000
-rw-rw-r-- 1 aturnip aster 15140696 Nov 5 04:22 nwt031105.080000
-rw-rw-r-- 1 aturnip aster 14788922 Nov 8 04:03 nwt031108.080000
-rw-rw-r-- 1 aturnip aster 14998778 Nov 11 04:06 nwt031111.080000
Gordon fixed sendmail on Nov 6th....so, note that the shutdowns after
Nov 5th occur at 4:0x, while the ones before that date are at 04:2x.
- 96: data system, Site russter, Wed 13-Aug-2003 15:57:52 MDT, Tuesday, Aug. 12, 2003
Aug. 12, 2003
Noticed that data had not been sent down from russter since Aug. 8.
Russter was not on the network (couldn't ping).
However, I was up at the site on Aug. 10th and the russter was running fine - although it had hung when I logged in. this was most likely due to being off the network as this is typical behavior when russter is off-line.
will chekc with MRS to see if there are any known network problems.
- 53: data system, Site CU 26m Tower, Fri 13-Jun-2003 08:00:15 MDT, Power Outage on June 12th.
There was a brief (7 seconds?) power outage on June 12th.
From the quacker logs:
Jun 12 12:18:30 quacker apmd[965]: Now using Battery Power
Jun 12 12:18:37 quacker apmd[965]: Now using AC Power
Jun 12 12:18:37 quacker apmd[965]: Charge: * * * (100% 3:20)
Top and bottom breakers appear to be working ok (ie, s3.slow
and h2o.kr).
- 52: data system, Site CU 26m Tower, Thu 12-Jun-2003 15:28:56 MDT, CNR Data Logger Problem
Talked to Craig Knox at Campbell Sci about the
"*D failed. Check security code" error message
when trying to change the program on the CNR logger.
He said to check the security status of the program with
Edlog. goto "Options" ---> "Program Security".
lev 1-2-3 should all be zeros.
(I did this and everything was already set to zero).
Since this doesn't seem it will help the other suggestion
was to power cycle the logger. then, as the logger is coming
up hit "*C", then "0000", then "A-key" (maybe *A?). Hopefully,
this will clear out any security settings.
- 44: data system, Site none, Fri 30-May-2003 08:43:57 MDT, How to re-nice processes (from Gordon)
Date: Thu, 29 May 2003 14:04:27 MDT
To: sean@ucar.edu
From: Gordon Maclean
Subject: renice
# set nice value for adam and sio process:
find PID with: ps -elf
100 S root 8238 1 0 75 0 - 349 schedu 13:32 ? 00:00:00 timeupdate -h russter -t 3600
000 S root 8239 1 0 76 0 - 407 pipe_w 13:32 ? 00:00:00 logger -t start_adam_timeupdate -p local0.info
100 S root 8240 1 0 65 -10 - 369 pipe_w 13:32 ? 00:00:00
adam -h russter
000 S root 8241 1 0 76 0 - 407 pipe_w 13:32 ? 00:00:00
logger -t start_adam -p local0.info
000 S root 8242 8240 0 65 -10 - 338 schedu 13:32 ? 00:00:02 sio
000 S root 8243 8240 0 75 0 - 334 schedu 13:32 ? 00:00:00
heart
100 S root 8244 8240 0 75 0 - 350 schedu 13:32 ? 00:00:00 rserial -h russter
then "renice" the adam and sio processes...
renice -10 8240
renice -10 8242
- 33: data system, Site quacker, Fri 16-May-2003 15:44:14 MDT, cron files on the quacker.
Fri, May 16th.
Talked to Gordon...we were looking at the cron jobs on the quacker...
apparently it is doing a bunch of stuff which it doesn't need to
do...these jobs all start at around 4am. Here are details on what
I did:
Cron Logfile:
more /var/log/cron
May 11 04:05:00 quacker CROND[25970]: (root) CMD (/usr/bin/mrtg /etc/mrtg/mrtg.cfg)
May 11 04:10:00 quacker CROND[26029]: (root) CMD (/usr/bin/mrtg /etc/mrtg/mrtg.cfg)
May 11 04:10:00 quacker CROND[26030]: (root) CMD (/usr/lib/sa/sa1 1 1)
May 11 04:15:00 quacker CROND[26033]: (root) CMD (/usr/bin/mrtg /etc/mrtg/mrtg.cfg)
May 11 04:20:00 quacker CROND[26036]: (root) CMD (/usr/bin/mrtg /etc/mrtg/mrtg.cfg)
May 11 04:20:00 quacker CROND[26037]: (root) CMD (/usr/lib/sa/sa1 1 1)
May 11 04:22:00 quacker CROND[26040]: (root) CMD (run-parts /etc/cron.weekly)
May 11 04:22:00 quacker anacron[26044]: Updated timestamp for job `cron.weekly' to 2003-05-11
May 11 04:25:00 quacker CROND[2017]: (root) CMD (/usr/bin/mrtg /etc/mrtg/mrtg.cfg)
May 11 04:30:00 quacker CROND[2021]: (root) CMD (/usr/bin/mrtg /etc/mrtg/mrtg.cfg)
May 11 04:30:00 quacker CROND[2022]: (root) CMD (/usr/lib/sa/sa1 1 1)
May 11 04:35:00 quacker CROND[2025]: (root) CMD (/usr/bin/mrtg /etc/mrtg/mrtg.cfg)
May 11 04:40:00 quacker CROND[2028]: (root) CMD (/usr/bin/mrtg /etc/mrtg/mrtg.cfg)
May 11 04:40:00 quacker CROND[2029]: (root) CMD (/usr/lib/sa/sa1 1 1)
May 11 04:45:00 quacker CROND[2033]: (root) CMD (/usr/bin/mrtg /etc/mrtg/mrtg.cfg)
May 11 04:50:00 quacker CROND[2036]: (root) CMD (/usr/bin/mrtg /etc/mrtg/mrtg.cfg)
May 11 04:50:00 quacker CROND[2037]: (root) CMD (/usr/lib/sa/sa1 1 1)
May 11 04:55:00 quacker CROND[2040]: (root) CMD (/usr/bin/mrtg /etc/mrtg/mrtg.cfg)
May 11 05:00:00 quacker CROND[2043]: (root) CMD (/usr/bin/mrtg /etc/mrtg/mrtg.cfg)
..etc..etc...
note that this "mrtg" job is running every 5minutes or so...
here's the modified crontab file (where gordon commented out the mrtg stuff):
for more info about mrtg see the webpage:
http://www.ntop.org/Monitoring.html
(it looks like this is useful software for monitoring bandwidth on a
network...something we don't need at all!).
---------------------------
more /etc/crontab
SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=root
HOME=/
# run-parts
01 * * * * root run-parts /etc/cron.hourly
02 4 * * * root run-parts /etc/cron.daily
22 4 * * 0 root run-parts /etc/cron.weekly
42 4 1 * * root run-parts /etc/cron.monthly
# 0-59/5 * * * * root /usr/bin/mrtg /etc/mrtg/mrtg.cfg
---------------------------
Using the linconfig7.* files in /net/adm/linux/ (on the atd computer
syrah) the following cron files on the quacker were changed to
non-executable:
Cron files to disable:
-rwxr-xr-x 1 root root 1769 Jun 25 2002 /etc/cron.daily/dbbackup
-rwxr-xr-x 1 root root 418 Mar 25 2002 /etc/cron.daily/makewhatis.cron
-rwxr-xr-x 1 root root 197 May 24 2002 /etc/cron.daily/texpire
-rwxr-xr-x 1 root root 315 Feb 26 2002 /etc/cron.daily/tripwire-check
-rwxr-xr-x 1 root root 100 Apr 12 2002 /etc/cron.daily/tetex.cron
-rwxr-xr-x 1 root root 197 May 24 2002 /etc/cron.daily/texpire
-rwxr-xr-x 1 root root 414 Mar 25 2002 /etc/cron.weekly/makewhatis.cron
-rwxr-xr-x 1 root root 40 May 23 2002 /etc/cron.weekly/wwwoffle-purge
chmod -x /etc/cron.daily/dbbackup
chmod -x /etc/cron.daily/tripwire-check
chmod -x /etc/cron.daily/makewhatis.cron
chmod -x /etc/cron.daily/texpire
chmod -x /etc/cron.daily/tetex.cron
chmod -x /etc/cron.daily/texpire
chmod -x /etc/cron.weekly/wwwoffle-purge
chmod -x /etc/cron.weekly/makewhatis.cron
-rw-r--r-- 1 root root 1769 Jun 25 2002 /etc/cron.daily/dbbackup
-rw-r--r-- 1 root root 418 Mar 25 2002 /etc/cron.daily/makewhatis.cron
-rw-r--r-- 1 root root 197 May 24 2002 /etc/cron.daily/texpire
-rw-r--r-- 1 root root 315 Feb 26 2002 /etc/cron.daily/tripwire-check
-rw-r--r-- 1 root root 100 Apr 12 2002 /etc/cron.daily/tetex.cron
-rw-r--r-- 1 root root 197 May 24 2002 /etc/cron.daily/texpire
-rw-r--r-- 1 root root 414 Mar 25 2002 /etc/cron.weekly/makewhatis.cron
-rw-r--r-- 1 root root 40 May 23 2002 /etc/cron.weekly/wwwoffle-purge
ls -lag /etc/cron.daily/dbbackup /etc/cron.daily/tripwire-check /etc/cron.daily/makewhatis.cron /etc/cron.daily/texpire
ls -lag /etc/cron.daily/tetex.cron /etc/cron.daily/texpire /etc/cron.weekly/wwwoffle-purge /etc/cron.weekly/makewhatis.cron
here is a complete listing of the remaining cron files (some others may also
be unecessary):
listing of cron files:
ls -lag /etc/cron*/*
lrwxrwxrwx 1 root root 28 Sep 5 2002 /etc/cron.daily/00-logwatch -> ../log.d/scripts/logwatch.pl
-rwxr-xr-x 1 root root 135 Apr 17 2002 /etc/cron.daily/00webalizer
-rwxr-xr-x 1 root root 276 Jun 24 2001 /etc/cron.daily/0anacron
-rwxr-xr-x 1 root root 51 Apr 15 2002 /etc/cron.daily/logrotate
-rwxr-xr-x 1 root root 104 Apr 18 2002 /etc/cron.daily/rpm
-rwxr-xr-x 1 root root 132 Jun 25 2001 /etc/cron.daily/slocate.cron
-rwxr-xr-x 1 root root 193 Apr 13 2002 /etc/cron.daily/tmpwatch
-rwxr-xr-x 1 root root 188 Apr 12 2002 /etc/cron.d/sysstat
-rwxr-xr-x 1 root root 278 Jun 24 2001 /etc/cron.monthly/0anacron
-rwxr-xr-x 1 root root 277 Jun 24 2001 /etc/cron.weekly/0anacron
-rw-r--r-- 1 root root 1769 Jun 25 2002 /etc/cron.daily/dbbackup
-rw-r--r-- 1 root root 418 Mar 25 2002 /etc/cron.daily/makewhatis.cron
-rw-r--r-- 1 root root 100 Apr 12 2002 /etc/cron.daily/tetex.cron
-rw-r--r-- 1 root root 197 May 24 2002 /etc/cron.daily/texpire
-rw-r--r-- 1 root root 315 Feb 26 2002 /etc/cron.daily/tripwire-check
lrwxrwxrwx 1 root root 65 Sep 5 2002 /etc/cron.daily/wwwoffle-full-index -> /var/spool/wwwoffle/html/search/htdig/scripts/wwwoff\
le-htdig-full
-rw-r--r-- 1 root root 414 Mar 25 2002 /etc/cron.weekly/makewhatis.cron
-rw-r--r-- 1 root root 40 May 23 2002 /etc/cron.weekly/wwwoffle-purge
- 27: data system, Site CU 26m Tower, Tue 29-Apr-2003 14:29:49 MDT, Gordon Fix of ATI Data
Here's Gordon/Andrews e-mail about the fix to ATI Data:
---------------------------------------------
Date: Tue, 29 Apr 2003 12:51:58 MDT
To: turnipseed andrew a , sean
From: Gordon Maclean
Subject: Re: ati question
turnipseed andrew a wrote:
> I stopped/started the data (works OK over network, but sometimes you lose
> the terminal window when you log out of quacker - there's an ongoing
> process still active). Now it seems that channel 206 is not there at all.
>
> The last time I had the ATI on was last August - it was running through
> the Edgeport, but with data drop-outs.
>
> andrew
>
>
Andy,
I've got the ATI going. It was a parity problem.
Here's what I did, for future reference:
stop_adam
edited channed_config and commented out the entry for port 206
start_adam
On the quacker, then I used minicom to talk to the port:
minicom USB6
Once I changed minicom to 9600,E,7,1 (even parity) then
the data looked OK. I changed the parity to NONE on the sonic,
from one of the ATI menus that you get to by entering ESCAPE.
Under the first menu item on the main menu you can change things
like parity and baud rate.
After that, the quacker could talk to it.
(I did the stop_adam, edited channel_config, and then start_adam).
The 9600.7.7.1 entry in channel_config is defined in
$ASTER/config/sio_protocols. If you look there you'll see
that it is defined as parity=NONE (all of them are).
We could add one called something like 9600.E.7.7.1 for EVEN parity,
but I thought it was best to change the sonic, so that it is like
most other sensors. We've set up all our ATIs to be no parity.
So the entry in channel_config for the ATI is now 9600.8.8.1
I've created minicom configs so that you can talk to any of the
usb ports, 0-7, on the quacker with
minicom USBx
By default, minicom talks at 9600,N,8,1. For help, do ctrl-A,
followed by plain Z (it mentions that at the bottom of the screen).
ctrl-A followed by P brings up a menu to set the baud, parity and data bits.
Gordon
- 18: data system, Site none, Thu 03-Apr-2003 08:57:51 MST, Data System Stopped -- 4:22 am, Thursday April 3rd.
Thursday Morning, April 3rd.
The data system stopped collecting data at 4:22am:
On russter:
-rw-rw-r-- 1 aturnip aster 27413176 Apr 2 17:00 nwt030402.160000
-rw-rw-r-- 1 aturnip aster 27410998 Apr 3 01:00 nwt030403.000000
-rw-rw-r-- 1 aturnip aster 10662982 Apr 3 04:22 nwt030403.080000
-rw-rw-r-- 1 aturnip aster 32768 Apr 3 08:50 nwt030403.154932
the log on russter:
[~] tail /var/adm/messages
Mar 31 06:07:00 russter ntpdate[12037]: adjust time server 128.138.82.228 offset 0.3272636
Mar 31 18:07:01 russter ntpdate[14189]: adjust time server 128.138.82.228 offset 0.3331698
Mar 31 23:27:27 russter inetd[150]: config: 100083/rpc/tcp still active and was not reconfigured.
Apr 1 06:07:01 russter ntpdate[15180]: adjust time server 128.138.82.228 offset 0.3347296
Apr 1 18:07:01 russter ntpdate[16446]: adjust time server 128.138.82.228 offset 0.3410935
Apr 1 23:28:34 russter inetd[150]: config: 100083/rpc/tcp still active and was not reconfigured.
Apr 2 06:07:00 russter ntpdate[17397]: adjust time server 128.138.82.228 offset 0.3410732
Apr 2 18:07:01 russter ntpdate[18347]: adjust time server 128.138.82.228 offset 0.3454047
Apr 2 23:28:51 russter inetd[150]: config: 100083/rpc/tcp still active and was not reconfigured.
Apr 3 06:07:00 russter ntpdate[19307]: adjust time server 128.138.82.228 offset 0.3382631
On quacker:
[cuff@quacker ~]$ tail /var/log/messages
Apr 3 02:01:58 quacker timeupdate[1343]: Adjusted clock 221 milliseconds forward. RPC calls took 4 milliseconds
Apr 3 03:01:57 quacker timeupdate[1343]: Adjusted clock -1601 milliseconds forward. RPC calls took 362 milliseconds
Apr 3 04:01:59 quacker timeupdate[1343]: Adjusted clock 220 milliseconds forward. RPC calls took 4 milliseconds
Apr 3 05:02:00 quacker timeupdate[1343]: Adjusted clock 257 milliseconds forward. RPC calls took 3 milliseconds
Apr 3 06:02:02 quacker timeupdate[1343]: Adjusted clock 279 milliseconds forward. RPC calls took 4 milliseconds
Apr 3 07:02:03 quacker timeupdate[1343]: Adjusted clock 619 milliseconds forward. RPC calls took 4 milliseconds
Apr 3 08:02:04 quacker timeupdate[1343]: Adjusted clock 309 milliseconds forward. RPC calls took 4 milliseconds
Apr 3 08:48:37 quacker sshd[22836]: Accepted password for cuff from 10.0.0.1 port 43155 ssh2
Apr 3 08:48:38 quacker sshd[22838]: Setting tty modes failed: Invalid argument
I don't see anything strange in these logs...so this remains a mystery. It looks
to me like the data system on quacker is going...so, maybe this is a network problem??