RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1683527 - "Reloading" message on a fresh reboot after enabling squid [rhel-8]
Summary: "Reloading" message on a fresh reboot after enabling squid [rhel-8]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: squid-4-module
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Luboš Uhliarik
QA Contact: Maryna Nalbandian
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-27 06:39 UTC by Maryna Nalbandian
Modified: 2021-01-14 09:44 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-05 21:21:56 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:3476 0 None None None 2019-11-05 21:22:02 UTC

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
Note You need to log in before you can comment on or make changes to this bug.