Hi-

I thought I could use some services to shut down firebird with classic. I get this error message.

I didn't know if it is safe or the preferred way to shut down classic  by just ctrl-c when

i used # ./fb_inet_server -m. The way I tried is like systemctl enable firebird-classic.socket

and systemctl start firebird-classic.socket.

Am I close to figuring out how to shut down and restart the service for the classic on fedora 24.

I picked classic because it said it is okay for not too many connections.

I am only practicing so I felt that would suffice. i found out though that the reason everything for

docs is missing is because it goes way back to at least 1.5. Also, it may predate systemd use and

that is why talk of xinetd or xinet or something. 

Please check log from below.... thx!

any help is appreciated. - jim

Jan 05 17:24:35 localhost.localdomain systemd[1]: firebird-classic.socket: Unit entered failed state.
Jan 05 17:24:59 localhost.localdomain systemd[1]: Closed Firebird Classic Activation Socket.
Jan 05 17:25:03 localhost.localdomain systemd[1]: firebird-classic.socket: Failed to listen on sockets: Permission den
Jan 05 17:25:03 localhost.localdomain systemd[1]: Failed to listen on Firebird Classic Activation Socket.
Jan 05 22:00:57 localhost.localdomain systemd[1]: Closed Firebird Classic Activation Socket.
Jan 05 22:06:34 localhost.localdomain systemd[1]: firebird-classic.socket: Failed to listen on sockets: Permission den
Jan 05 22:06:34 localhost.localdomain systemd[1]: Failed to listen on Firebird Classic Activation Socket.
Jan 05 22:08:05 localhost.localdomain systemd[1]: Closed Firebird Classic Activation Socket.
Jan 05 22:08:45 localhost.localdomain systemd[1]: firebird-classic.socket: Failed to listen on sockets: Permission den
Jan 05 22:08:45 localhost.localdomain systemd[1]: Failed to listen on Firebird Classic Activation Socket.
[root@localhost system]# systemctl start firebird-classic.socket
Job for firebird-classic.socket failed. See "systemctl status firebird-classic.socket" and "journalctl -xe" for details.
[root@localhost system]# journalctl -xe
-- Subject: Unit firebird-classic.socket has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit firebird-classic.socket has failed.
--
-- The result is failed.
Jan 05 22:13:40 localhost.localdomain polkitd[662]: Unregistered Authentication Agent for unix-process:19423:9092317 (
Jan 05 22:13:43 localhost.localdomain dbus-daemon[638]: [system] Activating service name='org.fedoraproject.Setroubles
Jan 05 22:13:43 localhost.localdomain dbus-daemon[638]: [system] Successfully activated service 'org.fedoraproject.Set
Jan 05 22:13:43 localhost.localdomain setroubleshoot[19436]: SELinux is preventing systemd from create access on the t
Jan 05 22:13:43 localhost.localdomain python3[19436]: SELinux is preventing systemd from create access on the tcp_sock
                                                     
                                                      *****  Plugin catchall (100. confidence) suggests   ************
                                                     
                                                      If you believe that systemd should be allowed create access on t
                                                      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 'systemd' --raw | audit2allow -M my-systemd
                                                      # semodule -X 300 -i my-systemd.pp