Bug 1683527

Summary: "Reloading" message on a fresh reboot after enabling squid [rhel-8]
Product: Red Hat Enterprise Linux 8 Reporter: Maryna Nalbandian <mnalband>
Component: squid-4-moduleAssignee: Luboš Uhliarik <luhliari>
Status: CLOSED ERRATA QA Contact: Maryna Nalbandian <mnalband>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.0CC: bnater, jorton, luhliari
Target Milestone: rcKeywords: Reopened
Target Release: 8.0Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-05 21:21:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Maryna Nalbandian 2019-02-27 06:39:02 UTC
Description of problem:
After fresh reboot there is "reloading" message after enabling squid. 
    
# systemctl enable squid
    Created symlink /etc/systemd/system/multi-user.target.wants/squid.service → /usr/lib/systemd/system/squid.service.

# systemctl status squid -l
    ● squid.service - Squid caching proxy
       Loaded: loaded ( ]8;;file://host-8-251-250.host.centralci.eng.rdu2.redhat.com/usr/lib/systemd/system/squid.service/usr/lib/systemd/system/squid.service ]8;;; enabled; vendor preset: disabled)
       Active: active (running) since Thu 2019-02-21 04:26:37 EST; 3min 30s ago
      Process: 1062 ExecReload=/usr/sbin/squid $SQUID_OPTS -k reconfigure -f $SQUID_CONF (code=exited, status=0/SUCCESS)
      Process: 652 ExecStart=/usr/sbin/squid $SQUID_OPTS -f $SQUID_CONF (code=exited, status=0/SUCCESS)
      Process: 638 ExecStartPre=/usr/libexec/squid/cache_swap.sh (code=exited, status=0/SUCCESS)
     Main PID: 876 (squid)
        Tasks: 3 (limit: 11532)
       Memory: 23.2M
       CGroup: /system.slice/squid.service
               ├─ 876 /usr/sbin/squid -f /etc/squid/squid.conf
               ├─ 892 (squid-1) --kid squid-1 -f /etc/squid/squid.conf
               └─1070 (logfile-daemon) /var/log/squid/access.log
 
    Feb 21 04:26:33 host-8-251-250.host.centralci.eng.rdu2.redhat.com systemd[1]: Starting Squid caching proxy...
    Feb 21 04:26:37 host-8-251-250.host.centralci.eng.rdu2.redhat.com systemd[1]: squid.service: Unit cannot be reloaded because it is inactive.
    Feb 21 04:26:37 host-8-251-250.host.centralci.eng.rdu2.redhat.com squid[876]: Squid Parent: will start 1 kids
    Feb 21 04:26:37 host-8-251-250.host.centralci.eng.rdu2.redhat.com squid[876]: Squid Parent: (squid-1) process 892 started
    Feb 21 04:26:38 host-8-251-250.host.centralci.eng.rdu2.redhat.com systemd[1]: Reloading Squid caching proxy.
    Feb 21 04:26:38 host-8-251-250.host.centralci.eng.rdu2.redhat.com systemd[1]: Reloaded Squid caching proxy.

Version-Release number of selected component (if applicable):
squid-4.4-4.module+el8+2479+dae5d0d3


How reproducible:
100%

Steps to Reproduce:
1. systemctl enable squid
2. Reboot the machine
3. systemctl status squid -l

Actual results:
"Reloaded Squid caching proxy."

Expected results:
"Started Squid caching proxy."

Additional info:
On rhel-7 the message is "Started Squid caching proxy."

Comment 13 errata-xmlrpc 2019-11-05 21:21:56 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:3476