shibd not writing to its log files

[Goldberg, Arthur P]

Hello Shibboleth experts

I’m running shibd on CentOS Linux release 7.9.2009 (Core).

It’s shibboleth 3.2.2. “test configuration file for problems” says:
$ shibd -t
2022-07-06 13:05:03 CRIT XMLTooling.Config : libcurl lacks OpenSSL-specific options, this will greatly limit functionality
overall configuration is loadable, check console or log for non-fatal problems

shibd is started with “systemctl start shibd”. Its status looks ok:
$ systemctl -l status shibd
● shibd.service - Shibboleth Service Provider Daemon
   Loaded: loaded (/usr/lib/systemd/system/shibd.service; disabled; vendor preset: disabled)
   Active: active (running) since Wed 2022-07-06 12:43:06 EDT; 26min ago
     Docs: https://wiki.shibboleth.net/confluence/display/SP3/Home
 Main PID: 68441 (shibd)
   CGroup: /system.slice/shibd.service
           └─68441 /usr/sbin/shibd -f -F

Jul 06 12:43:06 omop-leaf-temp systemd[1]: Starting Shibboleth Service Provider Daemon...
Jul 06 12:43:06 omop-leaf-temp systemd[1]: Started Shibboleth Service Provider Daemon.

But no log messages are generated. In fact, no log messages have been generated for a long time:

$ pwd
/var/log/shibboleth

root at omop-leaf-temp:[log/shibboleth]$ ls -lt | head
total 9832
-rw-r--r-- 1 shibd   24779 Nov 18  2021 shibd_warn.log
-rw-r--r-- 1 shibd 1000055 Nov 17  2021 shibd.log
-rw-r--r-- 1 shibd 1000156 Nov 11  2021 transaction.log
-rw-r--r-- 1 shibd 1000088 Nov  5  2021 transaction.log.1
-rw-r--r-- 1 shibd 1000091 Oct 24  2021 transaction.log.2
-rw-r--r-- 1 shibd 1000059 Oct  3  2021 transaction.log.3
-rw-r--r-- 1 shibd 1000029 Sep  5  2021 transaction.log.4
-rw-r--r-- 1 shibd 1000221 Aug 19  2021 shibd.log.1
-rw-r--r-- 1 shibd 1000023 Aug 15  2021 transaction.log.5

root at omop-leaf-temp:[log/shibboleth]$ tail shibd.log
2021-11-17 16:23:28 INFO Shibboleth.AttributeExtractor.XML [6] [default]: skipping SAML 2.0 Attribute with Name: http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name, Format:urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified
2021-11-17 16:23:28 INFO Shibboleth.SessionCache [6] [default]: new session created: ID (_dbc585d8785d3c6a0ebb9681e508ef36) IdP (https://sts.windows.net/77e89d61-570f-43b0-b9e4-634f462e34b8/) Protocol(urn:oasis:names:tc:SAML:2.0:protocol) Address (10.254.185.251)
2021-11-17 16:30:28 INFO XMLTooling.StorageService : purged 17 expired record(s) from storage
2021-11-17 16:45:27 INFO XMLTooling.StorageService : purged 17 expired record(s) from storage
2021-11-17 17:00:26 INFO XMLTooling.StorageService : purged 15 expired record(s) from storage
2021-11-17 17:15:25 INFO XMLTooling.StorageService : purged 15 expired record(s) from storage
2021-11-17 17:26:29 WARN OpenSAML.MessageDecoder.SAML2SOAP [7] [default]: ignoring incorrect content type ()
2021-11-17 17:30:25 INFO XMLTooling.StorageService : purged 15 expired record(s) from storage
2021-11-17 17:45:24 INFO XMLTooling.StorageService : purged 16 expired record(s) from storage
2021-11-17 18:00:24 INFO XMLTooling.StorageService : purged 15 expired record(s) from storage
How would you recommend debugging the absence of log messages? (I’m working on a development clone of our production VM, so I can do anything without disturbing our users.)

Thanks in advance
Arthur

-- 
Arthur Goldberg, PhD
https://labs.icahn.mssm.edu/msdw/
https://labs.icahn.mssm.edu/minervalab/scientific-computing-and-data
Associate Professor of Genetics and Genomic Sciences
Institute for Data Science and Genomic Technology
Mount Sinai School of Medicine

mailto:Arthur.Goldberg at mssm.edu
646 526 5020
https://mssm.zoom.us/my/arthur.goldberg?pwd=LzByMGJOZC9wM3A2aHV6OU94eUtSQT09