Command: /usr/local/sbin/syslog-digest.py Time : 0.5066s Status : exited 0 Output : Syslog digest — 2026-08-02 02:05 EDT Processed 4,114 lines, filtered 3,221 (78%). 893 unknown (122 distinct) from 22 host(s). == abuse (1 distinct, 345 total) == Aug 2 01:05:06 abuse rsyslogd[21745]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Input/output error [v8.2404.0 try https://www.rsyslog.com/e/2433 ] [x345] == b0b02.cs.umd.edu (1 distinct, 1 total) == Aug 2 01:41:25 b0b02.cs.umd.edu rustdesk[1957448]: cannot open display: == cheezit.cs.umd.edu (11 distinct, 13 total) == Aug 2 01:30:36 cheezit.cs.umd.edu setroubleshoot[129145]: failed to retrieve rpm info for path '/var/log/falconctl.log': Aug 2 01:30:37 cheezit.cs.umd.edu setroubleshoot[129145]: SELinux is preventing /opt/CrowdStrike/falconctl18708 from append access on the file /var/log/falconctl.log. For complete SELinux messages run: sealert -l 63f66d53-fcfc-44da-a79e-c789b1ce2ce8 Aug 2 01:30:39 cheezit.cs.umd.edu setroubleshoot[129145]: SELinux is preventing /opt/CrowdStrike/falconctl18708 from write access on the file falconstore. For complete SELinux messages run: sealert -l 386506af-597f-4357-89de-bc382f369a6e Aug 2 01:30:50 cheezit.cs.umd.edu setroubleshoot[129517]: failed to retrieve rpm info for path '/var/lib/sss/pipes/nss': [x2] Aug 2 01:30:51 cheezit.cs.umd.edu setroubleshoot[129517]: SELinux is preventing /usr/bin/lsof from write access on the sock_file /var/lib/sss/pipes/nss. For complete SELinux messages run: sealert -l f570494d-54d2-4dac-97e2-28395659abf1 [x2] Aug 2 01:30:51 cheezit.cs.umd.edu setroubleshoot[129517]: SELinux is preventing /usr/bin/lsof from write access on the sock_file socket. For complete SELinux messages run: sealert -l 9ff2383b-9e1d-44ff-b8ae-af91637450ae Aug 2 01:31:31 cheezit.cs.umd.edu setroubleshoot[129984]: SELinux is preventing /usr/bin/python3.9 from read access on the file /etc/selinux/targeted/contexts/files/file_contexts.subs_dist. For complete SELinux messages run: sealert -l 679eb260-cf5d-4783-99f4-ce308edb3295 Aug 2 01:31:31 cheezit.cs.umd.edu setroubleshoot[129984]: SELinux is preventing /usr/bin/python3.9 from open access on the file /etc/selinux/targeted/contexts/files/file_contexts.subs_dist. For complete SELinux messages run: sealert -l 77caba8a-5cd0-4e18-b188-6e35c461772d Aug 2 01:31:31 cheezit.cs.umd.edu setroubleshoot[129984]: SELinux is preventing /usr/bin/python3.9 from read access on the file /etc/selinux/targeted/contexts/files/file_contexts.subs. For complete SELinux messages run: sealert -l d9c6dd0d-0a34-4430-a5ff-e985c55cb064 Aug 2 01:31:31 cheezit.cs.umd.edu setroubleshoot[129984]: SELinux is preventing /usr/bin/python3.9 from open access on the file /etc/selinux/targeted/contexts/files/file_contexts.subs. For complete SELinux messages run: sealert -l 8edbce57-8212-4ac8-af50-3fe403231eda Aug 2 01:31:31 cheezit.cs.umd.edu setroubleshoot[129984]: SELinux is preventing /usr/bin/python3.9 from map access on the file /etc/selinux/targeted/contexts/files/file_contexts.bin. For complete SELinux messages run: sealert -l 4a0cbe3b-6f49-4c7e-95c6-380f7aef806e == cmsc436-0101-redis (2 distinct, 2 total) == Aug 2 01:05:36 cmsc436-0101-redis krb5_child[670849]: Client 'admin@UMD.EDU' not found in Kerberos database Aug 2 01:05:38 cmsc436-0101-redis sshd-session[670845]: error: PAM: Authentication failure for admin from 34.79.138.101 == contest (9 distinct, 43 total) == Aug 2 01:06:24 contest goferd[1007]: [ERROR][worker-0] gofer.messaging.adapter.connect:33 - connect: proton+amqps://satellite8.cs.umd.edu:5647, failed: Connection amqps://satellite8.cs.umd.edu:5647 disconnected: Condition('proton.pythonio', 'Connection refused to all addresses') [x33] Aug 2 01:48:16 contest setroubleshoot[480656]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory libdnf.8paIYx. For complete SELinux messages run: sealert -l cb6b25c6-4765-4cf2-88a0-9b3b508e94e9 Aug 2 01:48:16 contest setroubleshoot[480656]: SELinux is preventing /usr/bin/gpgconf from add_name access on the directory repodata. For complete SELinux messages run: sealert -l 41cf7b1b-0f34-4609-98f2-b66e7825fef7 [x2] Aug 2 01:48:16 contest setroubleshoot[480656]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the file mirrorlist. For complete SELinux messages run: sealert -l fc20ff92-ea83-4f38-a24b-ddfd737a3141 Aug 2 01:48:17 contest setroubleshoot[480656]: SELinux is preventing /usr/libexec/platform-python3.6 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l ac675631-fa35-4e93-adc9-b692b18e53e5 Aug 2 01:48:17 contest setroubleshoot[480656]: SELinux is preventing /usr/libexec/platform-python3.6 from read access on the directory libdnf.8paIYx. For complete SELinux messages run: sealert -l 45d103b6-0810-4890-a705-990118577ce8 Aug 2 01:48:17 contest setroubleshoot[480656]: SELinux is preventing /usr/libexec/platform-python3.6 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 7e499113-2fd7-4f67-bec6-3521efbe3637 [x2] Aug 2 01:48:17 contest setroubleshoot[480656]: SELinux is preventing /usr/libexec/platform-python3.6 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 3928930b-a1ed-448d-950b-0665ac2adef8 Aug 2 01:48:17 contest setroubleshoot[480656]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory libdnf.LtLQCC. For complete SELinux messages run: sealert -l cb6b25c6-4765-4cf2-88a0-9b3b508e94e9 == csfw00a (1 distinct, 268 total) == Aug 2 01:04:34 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x268] == dojo (1 distinct, 1 total) == Aug 2 01:06:20 dojo sshd[867681]: error: Protocol major versions differ: 2 vs. 1 == hackerman (1 distinct, 1 total) == Aug 2 01:19:01 hackerman gnome-software[2060381]: failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code2: Failed to create file “/adminhomes/sajith/.config/dconf/user.QVQXS3”: Permission denied == hazfs.cs.umd.edu (11 distinct, 66 total) == Aug 2 01:53:07 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6] Aug 2 01:53:07 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6] Aug 2 01:53:07 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6] Aug 2 01:53:07 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6] Aug 2 01:53:07 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6] Aug 2 01:53:07 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6] Aug 2 01:53:07 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6] Aug 2 01:53:07 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6] Aug 2 01:53:07 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6] Aug 2 01:53:07 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6] Aug 2 01:53:07 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6] == idm00 (2 distinct, 2 total) == Aug 2 01:24:05 idm00 named[1455]: client @0x7f33048c7d98 10.73.245.12#63911: update '73.10.in-addr.arpa/IN' denied Aug 2 01:51:14 idm00 named[1455]: client @0x7f331054a7b8 10.73.240.42#63714: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Aug 2 01:36:02 idmp0 named[5198]: client @0x7f9924071208 10.73.240.43#55459: update '73.10.in-addr.arpa/IN' denied == inbound00.cs.umd.edu (2 distinct, 2 total) == Aug 2 01:51:46 inbound00.cs.umd.edu krb5_child[2031598]: Preauthentication failed Aug 2 02:03:52 inbound00.cs.umd.edu krb5_child[2034748]: Client 'admin@UMD.EDU' not found in Kerberos database == itmon02 (1 distinct, 24 total) == Aug 2 01:08:13 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x24] == netman.cs.umd.edu (2 distinct, 5 total) == Aug 2 01:32:43 netman.cs.umd.edu krb5_child[3918800]: Client 'admin@UMD.EDU' not found in Kerberos database [x4] Aug 2 01:32:49 netman.cs.umd.edu sshd[3918797]: error: PAM: Authentication failure for admin from 34.76.146.227 == newhonors2 (1 distinct, 24 total) == Aug 2 01:13:03 newhonors2 dhcpcd[612575]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Aug 2 01:09:09 outbound00.cs.umd.edu python3[1987698]: ldapdb [x6] == outbound01.cs.umd.edu (4 distinct, 10 total) == Aug 2 01:13:07 outbound01.cs.umd.edu python3[20341]: ldapdb [x6] Aug 2 01:31:42 outbound01.cs.umd.edu krb5_child[24843]: Preauthentication failed Aug 2 01:34:10 outbound01.cs.umd.edu krb5_child[25453]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] Aug 2 01:36:04 outbound01.cs.umd.edu sshd-session[25987]: error: Protocol major versions differ: 2 vs. 1 == sentry-docker00.cs.umd.edu (40 distinct, 40 total) == Aug 2 01:06:08 sentry-docker00.cs.umd.edu systemd-udevd[57551]: link_config: could not get ethtool features for veth5e40234 Aug 2 01:06:08 sentry-docker00.cs.umd.edu systemd-udevd[57551]: Could not set offload features of veth5e40234: No such device Aug 2 01:06:08 sentry-docker00.cs.umd.edu systemd-udevd[57577]: Could not generate persistent MAC address for veth05560d0: No such file or directory Aug 2 01:06:08 sentry-docker00.cs.umd.edu systemd-udevd[57578]: Could not generate persistent MAC address for veth0e0928a: No such file or directory Aug 2 01:06:08 sentry-docker00.cs.umd.edu systemd-udevd[57597]: Could not generate persistent MAC address for vethe1bedf4: No such file or directory Aug 2 01:06:08 sentry-docker00.cs.umd.edu systemd-udevd[57592]: Could not generate persistent MAC address for veth587be9e: No such file or directory Aug 2 01:06:08 sentry-docker00.cs.umd.edu systemd-udevd[57586]: Could not generate persistent MAC address for veth19554ab: No such file or directory Aug 2 01:06:08 sentry-docker00.cs.umd.edu systemd-udevd[57581]: Could not generate persistent MAC address for veth2cd2c2d: No such file or directory Aug 2 01:06:08 sentry-docker00.cs.umd.edu systemd-udevd[57607]: Could not generate persistent MAC address for veth1aae1b3: No such file or directory Aug 2 01:06:08 sentry-docker00.cs.umd.edu systemd-udevd[57608]: Could not generate persistent MAC address for veth9b47e79: No such file or directory Aug 2 01:08:48 sentry-docker00.cs.umd.edu systemd-udevd[59774]: link_config: could not get ethtool features for vethace7dd1 Aug 2 01:08:48 sentry-docker00.cs.umd.edu systemd-udevd[59774]: Could not set offload features of vethace7dd1: No such device Aug 2 01:08:48 sentry-docker00.cs.umd.edu systemd-udevd[59792]: Could not generate persistent MAC address for veth9822b04: No such file or directory Aug 2 01:08:48 sentry-docker00.cs.umd.edu systemd-udevd[59793]: Could not generate persistent MAC address for veth4991a70: No such file or directory Aug 2 01:26:17 sentry-docker00.cs.umd.edu systemd-udevd[67262]: link_config: could not get ethtool features for vethe1bedf4 Aug 2 01:26:17 sentry-docker00.cs.umd.edu systemd-udevd[67262]: Could not set offload features of vethe1bedf4: No such device Aug 2 01:26:17 sentry-docker00.cs.umd.edu systemd-udevd[67280]: Could not generate persistent MAC address for veth4c4e786: No such file or directory Aug 2 01:26:17 sentry-docker00.cs.umd.edu systemd-udevd[67281]: Could not generate persistent MAC address for veth38b2f63: No such file or directory Aug 2 01:26:17 sentry-docker00.cs.umd.edu systemd-udevd[67305]: Could not generate persistent MAC address for veth7b9efa4: No such file or directory Aug 2 01:26:17 sentry-docker00.cs.umd.edu systemd-udevd[67289]: Could not generate persistent MAC address for vethd106a67: No such file or directory Aug 2 01:26:17 sentry-docker00.cs.umd.edu systemd-udevd[67308]: Could not generate persistent MAC address for veth74a2b9e: No such file or directory Aug 2 01:26:17 sentry-docker00.cs.umd.edu systemd-udevd[67309]: Could not generate persistent MAC address for vethe5061d8: No such file or directory Aug 2 01:26:17 sentry-docker00.cs.umd.edu systemd-udevd[67340]: Could not generate persistent MAC address for veth63fa1f8: No such file or directory Aug 2 01:26:17 sentry-docker00.cs.umd.edu systemd-udevd[67333]: Could not generate persistent MAC address for veth1b71459: No such file or directory Aug 2 01:28:57 sentry-docker00.cs.umd.edu systemd-udevd[69470]: Could not generate persistent MAC address for vetha31675c: No such file or directory Aug 2 01:28:57 sentry-docker00.cs.umd.edu systemd-udevd[69471]: Could not generate persistent MAC address for vethf1c8f46: No such file or directory Aug 2 01:46:25 sentry-docker00.cs.umd.edu systemd-udevd[76665]: link_config: could not get ethtool features for veth4c4e786 Aug 2 01:46:25 sentry-docker00.cs.umd.edu systemd-udevd[76665]: Could not set offload features of veth4c4e786: No such device Aug 2 01:46:25 sentry-docker00.cs.umd.edu systemd-udevd[76739]: link_config: could not get ethtool features for veth7b9efa4 Aug 2 01:46:25 sentry-docker00.cs.umd.edu systemd-udevd[76739]: Could not set offload features of veth7b9efa4: No such device ... 10 more distinct messages not shown == strawberry (2 distinct, 8 total) == Aug 2 01:09:44 strawberry udisksd[1067]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST2000DM001_1CH164_W1E8J5KJ: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#0120010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#012 (g-io-error-quark, 0) [x6] Aug 2 01:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-2 (10 distinct, 13 total) == Aug 2 01:12:51 submit26-b9-2 setroubleshoot[849556]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l d506243c-d61e-48f3-b42a-4592c913deb0 [x2] Aug 2 01:12:51 submit26-b9-2 setroubleshoot[849556]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 3b4752ac-1b9a-4af9-a05b-32e4c2eb13ab [x2] Aug 2 01:12:51 submit26-b9-2 setroubleshoot[849556]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 29e5adbd-4381-4467-b40d-a2219101e096 Aug 2 01:12:51 submit26-b9-2 setroubleshoot[849556]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.7u0BuT/repodata/repomd.xml. For complete SELinux messages run: sealert -l 1b38f2ec-01ce-4343-8059-ba7494ecc5c4 Aug 2 01:12:51 submit26-b9-2 setroubleshoot[849556]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l e5f9af40-1f63-4924-b012-27ab2a7b2266 Aug 2 01:12:51 submit26-b9-2 setroubleshoot[849556]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.7u0BuT. For complete SELinux messages run: sealert -l 5c54db87-54a3-4a7c-97b4-b5c48d6c3543 Aug 2 01:12:51 submit26-b9-2 setroubleshoot[849556]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 63cd60e1-1e61-4276-afea-dd8526ffe8b2 Aug 2 01:12:51 submit26-b9-2 setroubleshoot[849556]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 81c7e9ec-e023-4c6d-b1ad-c02a242e655e Aug 2 01:12:51 submit26-b9-2 setroubleshoot[849556]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 6ae9a597-e123-4d74-8eec-a8ebe0f5e4d0 Aug 2 01:18:06 submit26-b9-2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-b9-3 (9 distinct, 9 total) == Aug 2 01:20:37 submit26-b9-3 setroubleshoot[769115]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 5b912a44-22fd-4560-b201-2a4e289b73f5 Aug 2 01:20:37 submit26-b9-3 setroubleshoot[769115]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 7f1df1e4-725e-4953-98eb-1079f908f543 Aug 2 01:20:37 submit26-b9-3 setroubleshoot[769115]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 40b8852a-f77b-44b4-affe-5f11fa33de43 Aug 2 01:20:37 submit26-b9-3 setroubleshoot[769115]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.bCginX/repodata/repomd.xml. For complete SELinux messages run: sealert -l 45a8019e-f6b5-4baa-92c1-862594b40d46 Aug 2 01:20:37 submit26-b9-3 setroubleshoot[769115]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l e9f0bfff-7784-4126-baa4-2bb06da56591 Aug 2 01:20:37 submit26-b9-3 setroubleshoot[769115]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.bCginX. For complete SELinux messages run: sealert -l 0b17cc3d-cdc6-4fe2-a11f-3892e7c41dc7 Aug 2 01:20:37 submit26-b9-3 setroubleshoot[769115]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 10e38c64-b65f-4cdd-901e-4375652d9a42 Aug 2 01:20:38 submit26-b9-3 setroubleshoot[769115]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 7fd9cf72-ef38-48e1-b6aa-b571b26a7b22 Aug 2 01:20:38 submit26-b9-3 setroubleshoot[769115]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l b9b11116-89bd-4a3c-980c-1d422c5dcee4 == submit26-clnb9 (9 distinct, 9 total) == Aug 2 01:31:56 submit26-clnb9 setroubleshoot[1663424]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 6783ed2b-5ae4-42b5-975a-4bf50eec4658 Aug 2 01:31:56 submit26-clnb9 setroubleshoot[1663424]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 9e7fa955-cc30-4804-ac8c-e1779e85946c Aug 2 01:31:56 submit26-clnb9 setroubleshoot[1663424]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 69bfa6e3-089c-40ff-9563-fd30787d0774 Aug 2 01:31:56 submit26-clnb9 setroubleshoot[1663424]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.iUe7gw/repodata/repomd.xml. For complete SELinux messages run: sealert -l 001acdb5-31ef-4e52-b10b-90f467a89ddc Aug 2 01:31:56 submit26-clnb9 setroubleshoot[1663424]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l edacddcf-16ed-4dc3-8d82-7c597d5dee23 Aug 2 01:31:56 submit26-clnb9 setroubleshoot[1663424]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.iUe7gw. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c Aug 2 01:31:56 submit26-clnb9 setroubleshoot[1663424]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 81cb3698-78f8-440a-8e3c-e5d1041e6b78 Aug 2 01:31:56 submit26-clnb9 setroubleshoot[1663424]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 792b472a-115c-4799-9805-fc7436f916b9 Aug 2 01:31:56 submit26-clnb9 setroubleshoot[1663424]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 15c83a86-837b-41e2-b662-b39cd4e361cb