# dnf install gdal gdal-devel
Last metadata expiration check: 0:22:02 ago on Sat 11 Feb 2023 11:49:32 PM JST.
Error:
Problem 1: conflicting requests
- nothing provides libdap.so.25()(64bit) needed by gdal-3.0.4-11.el8.x86_64
- nothing provides libdapclient.so.6()(64bit) needed by gdal-3.0.4-11.el8.x86_64
- nothing provides libdapserver.so.7()(64bit) needed by gdal-3.0.4-11.el8.x86_64
Problem 2: package gdal-devel-3.0.4-11.el8.x86_64 requires libgdal.so.26()(64bit), but none of the providers can be installed
- package gdal-devel-3.0.4-11.el8.x86_64 requires gdal-libs(x86-64) = 3.0.4-11.el8, but none of the providers can be installed
- conflicting requests
- nothing provides libdap.so.25()(64bit) needed by gdal-libs-3.0.4-11.el8.x86_64
- nothing provides libdapclient.so.6()(64bit) needed by gdal-libs-3.0.4-11.el8.x86_64
- nothing provides libdapserver.so.7()(64bit) needed by gdal-libs-3.0.4-11.el8.x86_64
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
# Rocky-PowerTools.repo
#
# The mirrorlist system uses the connecting IP address of the client and the
# update status of each mirror to pick current mirrors that are geographically
# close to the client. You should use this for Rocky updates unless you are
# manually picking other mirrors.
#
# If the mirrorlist does not work for you, you can try the commented out
# baseurl line instead.
[powertools]
name=Rocky Linux $releasever - PowerTools
mirrorlist=https://mirrors.rockylinux.org/mirrorlist?arch=$basearch&repo=PowerTools-$releasever
#baseurl=http://dl.rockylinux.org/$contentdir/$releasever/PowerTools/$basearch/os/
gpgcheck=1
enabled=0
countme=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rockyofficial
# mysql -u root -p
Enter password:
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 17
Server version: 10.3.32-MariaDB MariaDB Server
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]> create user 'mmuser'@'%' identified by 'xxxxxx';
MariaDB [(none)]> create database mattermost;
MariaDB [(none)]> grant all privileges on mattermost.* to 'mmuser'@'%';
# systemctl daemon-reload
# systemctl start mattermost.service
Job for mattermost.service failed because the control process exited with error code.
See "systemctl status mattermost.service" and "journalctl -xe" for details.
いきなり失敗しました! 多分、ここで躓きます(TT) 内容を確認します。
# journalctl -xe
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mattermost.service has failed.
--
-- The result is failed.
5月 28 06:07:39 localhost.localdomain setroubleshoot[14220]: AnalyzeThread.run(): Cancel pending alarm
5月 28 06:07:39 localhost.localdomain setroubleshoot[14220]: SELinux is preventing /usr/lib/systemd/systemd from execute access on t>
5月 28 06:07:39 localhost.localdomain setroubleshoot[14220]: SELinux is preventing /usr/lib/systemd/systemd from execute access on t>
***** Plugin catchall (100. confidence) suggests ******************>
If you believe that systemd should be allowed execute access on the ma>
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# ausearch -c '(ttermost)' --raw | audit2allow -M my-ttermost
# semodule -X 300 -i my-ttermost.pp
5月 28 06:07:39 localhost.localdomain setroubleshoot[14220]: AnalyzeThread.run(): Set alarm timeout to 10
5月 28 06:07:42 localhost.localdomain org.gnome.Shell.desktop[6472]: Window manager warning: last_user_time (10454099) is greater th>
5月 28 06:07:42 localhost.localdomain org.gnome.Shell.desktop[6472]: Window manager warning: W3 appears to be one of the offending w>
# systemctl start mattermost
Job for mattermost.service failed because the control process exited with error code.
See "systemctl status mattermost.service" and "journalctl -xe" for details.
[root@localhost ~]# journalctl -xe
5月 28 06:15:58 localhost.localdomain dbus-daemon[934]: [system] Successfully activated service 'org.fedoraproject.SetroubleshootPrivileged'
5月 28 06:15:59 localhost.localdomain setroubleshoot[15253]: SELinux is preventing /usr/lib/systemd/systemd from 'read, open' accesses on the file /opt/mattermost/bin/mattermost. For complete SELinux >
5月 28 06:15:59 localhost.localdomain setroubleshoot[15253]: SELinux is preventing /usr/lib/systemd/systemd from 'read, open' accesses on the file /opt/mattermost/bin/mattermost.
***** Plugin restorecon (99.5 confidence) suggests ************************
If you want to fix the label.
/opt/mattermost/bin/mattermost default label should be bin_t.
Then you can run restorecon. The access attempt may have been stopped due to insufficient permissions to access a parent directory in whic>
Do
# /sbin/restorecon -v /opt/mattermost/bin/mattermost
***** Plugin catchall (1.49 confidence) suggests **************************
If you believe that systemd should be allowed read open access on the mattermost file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# ausearch -c '(ttermost)' --raw | audit2allow -M my-ttermost
# semodule -X 300 -i my-ttermost.pp