Command: /usr/local/sbin/syslog-digest.py Time : 0.1613s Status : exited 0 Output : Syslog digest — 2026-10-11 06:05 EDT Processed 5,614 lines, filtered 3,008 (53%). 2,606 unknown (186 distinct) from 20 host(s). == abuse (1 distinct, 346 total) == Oct 11 05:05:25 abuse rsyslogd[1033]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Input/output error [v8.2404.0 try https://www.rsyslog.com/e/2433 ] [x346] == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 11 05:22:37 b0b02.cs.umd.edu rustdesk[2584799]: cannot open display: == grades01.cs.umd.edu (1 distinct, 1 total) == Oct 11 05:48:21 grades01.cs.umd.edu puppet-agent[29581]: The directory '/srv/grades' contains 2471 entries, which exceeds the default soft limit 1000 and may cause excessive resource consumption and degraded performance. To remove this warning set a value for `max_files` parameter or consider using an alternate method to manage large directory trees == idm00 (1 distinct, 1 total) == Oct 11 05:54:45 idm00 named[2816192]: client @0x7fd0f4042088 10.73.240.42#59614: update '73.10.in-addr.arpa/IN' denied == idmh1 (14 distinct, 168 total) == Oct 11 05:07:09 idmh1 check-named-alive[307041]: zone cs.umd.edu: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 05:07:09 idmh1 check-named-alive[307102]: zone csdlabs.umd.edu: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 05:07:09 idmh1 check-named-alive[307166]: zone csic.umd.edu: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 05:07:09 idmh1 check-named-alive[307227]: zone 72.10.in-addr.arpa: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 05:07:09 idmh1 check-named-alive[307288]: zone 73.10.in-addr.arpa: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 05:07:10 idmh1 check-named-alive[307351]: zone 88.10.in-addr.arpa: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 05:07:10 idmh1 check-named-alive[307412]: zone 28.172.in-addr.arpa: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 05:07:10 idmh1 check-named-alive[307473]: zone 125.8.128.in-addr.arpa: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 05:07:10 idmh1 check-named-alive[307534]: zone 126.8.128.in-addr.arpa: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 05:07:10 idmh1 check-named-alive[307597]: zone 127.8.128.in-addr.arpa: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 05:07:11 idmh1 check-named-alive[307658]: zone 128.8.128.in-addr.arpa: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 05:07:11 idmh1 check-named-alive[307719]: zone 129.8.128.in-addr.arpa: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 05:07:11 idmh1 check-named-alive[307780]: zone 130.8.128.in-addr.arpa: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 05:07:11 idmh1 check-named-alive[307841]: zone 131.8.128.in-addr.arpa: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] == idmp0 (15 distinct, 169 total) == Oct 11 05:07:45 idmp0 check-named-alive[151434]: zone cs.umd.edu: local SOA serial 1791691939 lags newest peer 1791695702 by 3763 (threshold 3600); not acting [x12] Oct 11 05:07:45 idmp0 check-named-alive[151495]: zone csdlabs.umd.edu: local SOA serial 1791691940 lags newest peer 1791695702 by 3762 (threshold 3600); not acting [x12] Oct 11 05:07:46 idmp0 check-named-alive[151556]: zone csic.umd.edu: local SOA serial 1791691940 lags newest peer 1791695702 by 3762 (threshold 3600); not acting [x12] Oct 11 05:07:46 idmp0 check-named-alive[151617]: zone 72.10.in-addr.arpa: local SOA serial 1791691940 lags newest peer 1791695702 by 3762 (threshold 3600); not acting [x12] Oct 11 05:07:46 idmp0 check-named-alive[151678]: zone 73.10.in-addr.arpa: local SOA serial 1791691940 lags newest peer 1791695702 by 3762 (threshold 3600); not acting [x12] Oct 11 05:07:46 idmp0 check-named-alive[151739]: zone 88.10.in-addr.arpa: local SOA serial 1791691940 lags newest peer 1791695702 by 3762 (threshold 3600); not acting [x12] Oct 11 05:07:47 idmp0 check-named-alive[151800]: zone 28.172.in-addr.arpa: local SOA serial 1791691940 lags newest peer 1791695702 by 3762 (threshold 3600); not acting [x12] Oct 11 05:07:47 idmp0 check-named-alive[151861]: zone 125.8.128.in-addr.arpa: local SOA serial 1791691940 lags newest peer 1791695702 by 3762 (threshold 3600); not acting [x12] Oct 11 05:07:47 idmp0 check-named-alive[151922]: zone 126.8.128.in-addr.arpa: local SOA serial 1791691940 lags newest peer 1791695702 by 3762 (threshold 3600); not acting [x12] Oct 11 05:07:48 idmp0 check-named-alive[151983]: zone 127.8.128.in-addr.arpa: local SOA serial 1791691939 lags newest peer 1791695702 by 3763 (threshold 3600); not acting [x12] Oct 11 05:07:48 idmp0 check-named-alive[152044]: zone 128.8.128.in-addr.arpa: local SOA serial 1791691939 lags newest peer 1791695702 by 3763 (threshold 3600); not acting [x12] Oct 11 05:07:48 idmp0 check-named-alive[152105]: zone 129.8.128.in-addr.arpa: local SOA serial 1791691939 lags newest peer 1791695702 by 3763 (threshold 3600); not acting [x12] Oct 11 05:07:49 idmp0 check-named-alive[152166]: zone 130.8.128.in-addr.arpa: local SOA serial 1791691940 lags newest peer 1791695702 by 3762 (threshold 3600); not acting [x12] Oct 11 05:07:49 idmp0 check-named-alive[152227]: zone 131.8.128.in-addr.arpa: local SOA serial 1791691940 lags newest peer 1791695702 by 3762 (threshold 3600); not acting [x12] Oct 11 05:39:23 idmp0 named[61110]: client @0x7fd7e4007ab8 10.73.240.43#64030: update '73.10.in-addr.arpa/IN' denied == idmv0 (14 distinct, 168 total) == Oct 11 05:05:27 idmv0 check-named-alive[3478097]: zone cs.umd.edu: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x12] Oct 11 05:05:27 idmv0 check-named-alive[3478158]: zone csdlabs.umd.edu: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x12] Oct 11 05:05:27 idmv0 check-named-alive[3478219]: zone csic.umd.edu: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x12] Oct 11 05:05:27 idmv0 check-named-alive[3478280]: zone 72.10.in-addr.arpa: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x12] Oct 11 05:05:28 idmv0 check-named-alive[3478341]: zone 73.10.in-addr.arpa: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x12] Oct 11 05:05:28 idmv0 check-named-alive[3478402]: zone 88.10.in-addr.arpa: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x12] Oct 11 05:05:28 idmv0 check-named-alive[3478463]: zone 28.172.in-addr.arpa: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x12] Oct 11 05:05:28 idmv0 check-named-alive[3478524]: zone 125.8.128.in-addr.arpa: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x12] Oct 11 05:05:28 idmv0 check-named-alive[3478585]: zone 126.8.128.in-addr.arpa: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x12] Oct 11 05:05:28 idmv0 check-named-alive[3478646]: zone 127.8.128.in-addr.arpa: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x12] Oct 11 05:05:29 idmv0 check-named-alive[3478707]: zone 128.8.128.in-addr.arpa: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x12] Oct 11 05:05:29 idmv0 check-named-alive[3478768]: zone 129.8.128.in-addr.arpa: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x12] Oct 11 05:05:29 idmv0 check-named-alive[3478829]: zone 130.8.128.in-addr.arpa: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x12] Oct 11 05:05:29 idmv0 check-named-alive[3478890]: zone 131.8.128.in-addr.arpa: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x12] == itmon02 (1 distinct, 4 total) == Oct 11 05:08:19 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x4] == krispykreme.cs.umd.edu (2 distinct, 2 total) == Oct 11 05:06:05 krispykreme.cs.umd.edu sshd-session[345980]: pam_access(sshd:auth): access denied for user `root' from `77.239.124.105' Oct 11 05:06:07 krispykreme.cs.umd.edu sshd-session[345978]: error: PAM: Authentication failure for root from 77.239.124.105 == munin (2 distinct, 8 total) == Oct 11 05:52:59 munin sudo[3220606]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x4] Oct 11 05:52:59 munin sudo[3220606]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x4] == newhonors2 (1 distinct, 24 total) == Oct 11 05:13:03 newhonors2 dhcpcd[3864973]: dhcpcd is not running [x24] == ntop00 (97 distinct, 97 total) == Oct 11 05:05:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6850) *** Oct 11 05:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6850) *** Oct 11 05:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6850, QN: 69/69, ET: 0) *** Oct 11 05:05:10 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6850, QN: 4264/4264, ET: 9) *** Oct 11 05:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 6851) *** Oct 11 05:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 6851, QN: 4299/4299, ET: 0) *** Oct 11 05:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 6851) *** Oct 11 05:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 6851, QN: 50/50, ET: 0) *** Oct 11 05:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6852) *** Oct 11 05:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6852) *** Oct 11 05:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6852, QN: 57/57, ET: 0) *** Oct 11 05:10:11 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6852, QN: 4422/4422, ET: 10) *** Oct 11 05:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 6853) *** Oct 11 05:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 6853, QN: 4451/4451, ET: 0) *** Oct 11 05:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 6853) *** Oct 11 05:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 6853, QN: 60/60, ET: 0) *** Oct 11 05:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6854) *** Oct 11 05:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6854) *** Oct 11 05:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6854, QN: 60/60, ET: 0) *** Oct 11 05:15:10 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6854, QN: 4410/4410, ET: 9) *** Oct 11 05:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 6855) *** Oct 11 05:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 6855, QN: 4422/4422, ET: 0) *** Oct 11 05:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 6855) *** Oct 11 05:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 6855, QN: 75/75, ET: 0) *** Oct 11 05:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6856) *** Oct 11 05:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6856) *** Oct 11 05:20:02 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6856, QN: 75/75, ET: 1) *** Oct 11 05:20:09 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6856, QN: 4319/4319, ET: 8) *** Oct 11 05:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 6857) *** Oct 11 05:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 6857, QN: 4344/4344, ET: 0) *** ... 67 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Oct 11 05:09:09 outbound00.cs.umd.edu python3[1515367]: ldapdb [x6] == outbound01.cs.umd.edu (2 distinct, 8 total) == Oct 11 05:08:31 outbound01.cs.umd.edu python3[2990786]: ldapdb [x7] Oct 11 05:09:40 outbound01.cs.umd.edu systemd[1]: Configuration file /usr/lib/systemd/system/authentication_milter.service is marked executable. Please remove executable permission bits. Proceeding anyway. == strawberry (7 distinct, 38 total) == Oct 11 05:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 11 05:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 11 05:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 11 05:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 11 05:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 11 05:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 11 05:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit10-cln25 (5 distinct, 1539 total) == Oct 11 05:05:13 submit10-cln25 rsyslogd: imjournal: fopen() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Input/output error [v8.24.0-57.el7_9.3 try http://www.rsyslog.com/e/2013 ] [x334] Oct 11 05:05:22 submit10-cln25 rsyslogd: file '/var/log/messages': open error: Input/output error [v8.24.0-57.el7_9.3 try http://www.rsyslog.com/e/2433 ] [x1200] Oct 11 05:25:00 submit10-cln25 systemd: Failed at step USER spawning /usr/libexec/pcp/bin/pmlogger_check: Input/output error [x2] Oct 11 05:28:00 submit10-cln25 systemd: Failed at step USER spawning /usr/libexec/pcp/bin/pmie_check: Input/output error [x2] Oct 11 05:30:00 submit10-cln25 systemd: Failed at step USER spawning /usr/libexec/pcp/bin/pmlogger_daily: Input/output error == submit26-b9-3 (1 distinct, 1 total) == Sep 13 11:20:06 submit26-b9-3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f2 (1 distinct, 1 total) == Oct 11 05:08:08 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f3 (9 distinct, 12 total) == Oct 11 05:06:50 submit26-b9-f3 setroubleshoot[2858289]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l a653b772-cbcd-438b-bae5-23c3dc69b31b Oct 11 05:06:50 submit26-b9-f3 setroubleshoot[2858289]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 3e904634-6caa-4202-8c92-f139db798859 Oct 11 05:06:50 submit26-b9-f3 setroubleshoot[2858289]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 580b20e4-ec2c-433d-905c-5bd417fba033 [x2] Oct 11 05:06:50 submit26-b9-f3 setroubleshoot[2858289]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.uEBpPH/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f [x2] Oct 11 05:06:50 submit26-b9-f3 setroubleshoot[2858289]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l bff72452-d40a-430b-9060-dd0a48f5b6ba [x2] Oct 11 05:06:50 submit26-b9-f3 setroubleshoot[2858289]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.uEBpPH. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Oct 11 05:06:50 submit26-b9-f3 setroubleshoot[2858289]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 6da64b94-7024-45a9-b8c2-3b9812517407 Oct 11 05:06:50 submit26-b9-f3 setroubleshoot[2858289]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 64cbe179-abf1-4d5a-bade-bb164897ee65 Oct 11 05:06:50 submit26-b9-f3 setroubleshoot[2858289]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l d2e35b1a-e27c-4f91-9217-2bb1204e1e68 == submit26-b9-f4 (10 distinct, 12 total) == Oct 11 05:24:54 submit26-b9-f4 setroubleshoot[822315]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l ee160f23-b161-4f4a-9985-c4edfd3a5beb [x2] Oct 11 05:24:54 submit26-b9-f4 setroubleshoot[822315]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 89a83821-4b24-4081-9973-0a79ca6ed5b4 [x2] Oct 11 05:24:54 submit26-b9-f4 setroubleshoot[822315]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l f73955d6-1416-45f9-bab6-ff1f3ea07e9d Oct 11 05:24:54 submit26-b9-f4 setroubleshoot[822315]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.dYdlUE/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Oct 11 05:24:54 submit26-b9-f4 setroubleshoot[822315]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 20293136-86a3-40ba-a651-cff48d36059e Oct 11 05:24:54 submit26-b9-f4 setroubleshoot[822315]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.dYdlUE. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Oct 11 05:24:54 submit26-b9-f4 setroubleshoot[822315]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l eec250fb-073f-456d-93bc-f98776fd476d Oct 11 05:24:54 submit26-b9-f4 setroubleshoot[822315]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l c9209e04-a349-43d5-8cb2-3e303e48df74 Oct 11 05:24:54 submit26-b9-f4 setroubleshoot[822315]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 3178d5f5-80e9-404b-92b7-9bef397a8915 Oct 11 05:28:10 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL