perfSONAR User Q&A and Other Discussion

[Andreas Haupt <>]

Hi Andrew,

On Tue, 2023-06-27 at 12:04 -0700, Andrew Lake wrote:
> Hi Andreas,
> 
> With selinux enabled, if you run “dnf reinstall perfsonar-toolkit-web-
> services” is it any better? The RPM loads a policy file.

[gordo-vm33] /root # dnf reinstall perfsonar-toolkit-web-services
[...]
  Running scriptlet: perfsonar-toolkit-web-services-5.0.3-1.el9.noarch   
1/2 
Failed to resolve typeattributeset statement at
/var/lib/selinux/targeted/tmp/modules/400/perfsonar-toolkit/cil:15
Failed to resolve AST
semodule:  Failed!

[...]

This also seemed to happen during installation:

[gordo-vm33] /root # grep -A 2 typeattributeset /var/log/dnf.rpm.log
2023-06-28T16:09:14+0200 INFO Failed to resolve typeattributeset statement at 
/var/lib/selinux/targeted/tmp/modules/400/lsregistrationdaemon/cil:30
Failed to resolve AST
semodule:  Failed!
--
2023-06-28T16:09:34+0200 INFO Failed to resolve typeattributeset statement at 
/var/lib/selinux/targeted/tmp/modules/400/perfsonar-toolkit/cil:15
Failed to resolve AST
semodule:  Failed!


Dashboard does not load properly as long as SELinux is set to enforcing.

> There is also the httpd_can_network_connect bool that should be getting
> set. 

This worked.

> Which OS are you using?

AlmaLinux-9.2

> I also wasn’t clear, was selinux enforcing on the host prior to the first
> time you installed?

Yes, system was installed freshly from scratch will SELinux enabled all
the time.


BTW: there is also a dependency issue during first installation:

2023-06-28T16:05:45+0200 SUBDEBUG Installed: 
pscheduler-server-5.0.3-1.el9.noarch
2023-06-28T16:05:58+0200 INFO Restarting PostgreSQL after configuration 
change.
Created symlink 
/etc/systemd/system/multi-user.target.wants/pscheduler-ticker.service → 
/usr/lib/system
d/system/pscheduler-ticker.service.
Created symlink 
/etc/systemd/system/postgresql.service.wants/pscheduler-ticker.service → 
/usr/lib/syste
md/system/pscheduler-ticker.service.
Created symlink 
/etc/systemd/system/multi-user.target.wants/pscheduler-runner.service → 
/usr/lib/system
d/system/pscheduler-runner.service.
Created symlink 
/etc/systemd/system/postgresql.service.wants/pscheduler-runner.service → 
/usr/lib/syste
md/system/pscheduler-runner.service.
Created symlink 
/etc/systemd/system/multi-user.target.wants/pscheduler-archiver.service → 
/usr/lib/syst
emd/system/pscheduler-archiver.service.
Created symlink 
/etc/systemd/system/postgresql.service.wants/pscheduler-archiver.service → 
/usr/lib/sys
temd/system/pscheduler-archiver.service.
Created symlink 
/etc/systemd/system/multi-user.target.wants/pscheduler-scheduler.service → 
/usr/lib/systemd/system/pscheduler-scheduler.service.
Created symlink 
/etc/systemd/system/postgresql.service.wants/pscheduler-scheduler.service → 
/usr/lib/systemd/system/pscheduler-scheduler.service.
Failed to enable unit: Unit file httpd.service does not exist.
Failed to start httpd.service: Unit httpd.service not found.
Failed to restart httpd.service: Unit httpd.service not found.
warning: %post(pscheduler-server-5.0.3-1.el9.noarch) scriptlet failed, exit 
status 5


It's probably not critical, though. I think, the Requires: statement in
the spec file needs to be changed to:

Requires(post): httpd

... in order to make sure httpd is installed already when post-install
scripts run.

Cheers,
Andreas
-- 
| Andreas Haupt            | E-Mail: 
|  DESY Zeuthen            | WWW:    http://www.zeuthen.desy.de/~ahaupt
|  Platanenallee 6         | Phone:  +49/33762/7-7359
|  D-15738 Zeuthen         | Fax:    +49/33762/7-7216

Attachment: smime.p7s
Description: S/MIME cryptographic signature