AndrewG10i's questions

I just have started using CentOS8 + podman in scope of migration from CentOS7 + docker. The issue is the following:

1. When firewalld is stopped - DNS works fine inside container:

   [root@dev1 ~]# systemctl stop firewalld
   [root@dev1 ~]# podman run -it alpine ping gmail.com
   PING gmail.com (172.217.161.133): 56 data bytes
   64 bytes from 172.217.161.133: seq=0 ttl=54 time=6.027 ms
   64 bytes from 172.217.161.133: seq=1 ttl=54 time=5.892 ms
   64 bytes from 172.217.161.133: seq=2 ttl=54 time=5.757 ms
   ^C
   --- gmail.com ping statistics ---
   3 packets transmitted, 3 packets received, 0% packet loss
   round-trip min/avg/max = 5.757/5.892/6.027 ms
   

2. But once firewalld is launched - DNS stop working inside container, even though network itself (ping) works fine:

   [root@dev1 ~]# systemctl start firewalld
   [root@dev1 ~]# podman run -it alpine ping gmail.com
   ping: bad address 'gmail.com'
   [root@dev1 ~]#
   [root@dev1 ~]#
   [root@dev1 ~]# podman run -it alpine ping 8.8.8.8
   PING 8.8.8.8 (8.8.8.8): 56 data bytes
   64 bytes from 8.8.8.8: seq=0 ttl=54 time=4.536 ms
   64 bytes from 8.8.8.8: seq=1 ttl=54 time=7.059 ms
   64 bytes from 8.8.8.8: seq=2 ttl=54 time=4.924 ms
   ^C
   --- 8.8.8.8 ping statistics ---
   3 packets transmitted, 3 packets received, 0% packet loss
   round-trip min/avg/max = 4.536/5.506/7.059 ms
   

3. DNS can work fine in container when it is launched with --net=host param:

   [root@dev1 ~]# podman run -it --net=host  alpine ping gmail.com
   PING gmail.com (172.217.161.133): 56 data bytes
   64 bytes from 172.217.161.133: seq=0 ttl=55 time=4.981 ms
   64 bytes from 172.217.161.133: seq=1 ttl=55 time=5.445 ms
   64 bytes from 172.217.161.133: seq=2 ttl=55 time=4.635 ms
   ^C
   --- gmail.com ping statistics ---
   3 packets transmitted, 3 packets received, 0% packet loss
   round-trip min/avg/max = 4.635/5.020/5.445 ms
   

Any suggestions on how to resolve this issue?

UPDATE: As of 13/Dec/2020 this issue is not reproducible on "CentOS Linux release 8.3.2011".

I use the following systemd script for GlassFish 4 on CentOS 7:

[Unit]
Description = GlassFish Server v4.1
After = syslog.target network.target

[Service]
User=glassfish
ExecStart = /usr/bin/java -jar /home/glassfish/glassfish4/glassfish/lib/client/appserver-cli.jar start-domain
ExecStop = /usr/bin/java -jar /home/glassfish/glassfish4/glassfish/lib/client/appserver-cli.jar stop-domain
ExecReload = /usr/bin/java -jar /home/glassfish/glassfish4/glassfish/lib/client/appserver-cli.jar restart-domain
Type = forking

[Install]
WantedBy = multi-user.target

The issue that when execute command "asadmin restart-domain" via web application itself or via NetBeans IDE, or via GlassFish Web admin page => Server => Restart - all processes of GlassFish got halted thus no one able to relaunch the GlassFish again.

In CentOS 6 with original GlassFish script (SysV) - everything works fine.

Any ideas how to fix that?

Edit 1:

1) status of the process after failed restart

# systemctl status glassfish
● glassfish.service - GlassFish Server v4.1.2
    Loaded: loaded (/etc/systemd/system/glassfish.service; enabled; vendor preset: disabled)
    Active: inactive (dead) since Thu 2017-05-25 02:25:46 CDT; 11s ago
  Process: 13465 ExecStop=/usr/bin/java -jar /local/glassfish4/glassfish/lib/client/appserver-cli.jar stop-domain (code=exited, status=0/SUCCESS)
  Process: 13338 ExecStart=/usr/bin/java -jar /local/glassfish4/glassfish/lib/client/appserver-cli.jar start-domain (code=exited, status=0/SUCCESS)
 Main PID: 13351 (code=exited, status=0/SUCCESS)

May 25 02:25:24 dev3.local systemd[1]: Starting GlassFish Server v4.1.2...
May 25 02:25:28 dev3.local java[13338]: Waiting for domain1 to start ....
May 25 02:25:28 dev3.local java[13338]: Successfully started the domain : domain1
May 25 02:25:28 dev3.local java[13338]: domain  Location: /local/glassfish4/glassfish/domains/domain1
May 25 02:25:28 dev3.local java[13338]: Log File: /local/glassfish4/glassfish/domains/domain1/logs/server.log
May 25 02:25:28 dev3.local java[13338]: Admin Port: 4848
May 25 02:25:28 dev3.local java[13338]: Command start-domain executed successfully.
May 25 02:25:29 dev3.local systemd[1]: Started GlassFish Server v4.1.2.
May 25 02:25:46 dev3.local java[13465]: CLI306: Warning - The server located at /local/glassfish4/glassfish/domains/domain1 is not running.
May 25 02:25:46 dev3.local java[13465]: Command stop-domain executed successfully.

2) status of the process after failed restart (having RestartForceExitStatus=SIGUSR1 in systemd config file)

#systemctl status glassfish
● glassfish.service - GlassFish Server v4.1.2
    Loaded: loaded (/etc/systemd/system/glassfish.service; enabled; vendor preset: disabled)
    Active: failed (Result: exit-code) since Thu 2017-05-25 02:15:16 CDT; 15s ago
  Process: 12994 ExecStop=/usr/bin/java -jar /local/glassfish4/glassfish/lib/client/appserver-cli.jar stop-domain (code=exited, status=0/SUCCESS)
  Process: 12859 ExecStart=/usr/bin/java -jar /local/glassfish4/glassfish/lib/client/appserver-cli.jar start-domain (code=exited, status=0/SUCCESS)
 Main PID: 12872 (code=exited, status=12)

May 25 02:13:36 dev3.local java[12859]: domain  Location: /local/glassfish4/glassfish/domains/domain1
May 25 02:13:36 dev3.local java[12859]: Log File: /local/glassfish4/glassfish/domains/domain1/logs/server.log
May 25 02:13:36 dev3.local java[12859]: Admin Port: 4848
May 25 02:13:36 dev3.local java[12859]: Command start-domain executed successfully.
May 25 02:13:37 dev3.local systemd[1]: Started GlassFish Server v4.1.2.
May 25 02:15:15 dev3.local systemd[1]: glassfish.service: main process exited, code=exited, status=12/n/a
May 25 02:15:16 dev3.local java[12994]: CLI306: Warning - The server located at /local/glassfish4/glassfish/domains/domain1 is not running.
May 25 02:15:16 dev3.local java[12994]: Command stop-domain executed successfully.
May 25 02:15:16 dev3.local systemd[1]: Unit glassfish.service entered failed state.
May 25 02:15:16 dev3.local systemd[1]: glassfish.service failed.