# Monitoring Webproxy Service and Location DB

**URL:** <https://community.ipfire.org/t/monitoring-webproxy-service-and-location-db/11780>\
**Category:** Monitoring\
**Created:** [21 June 2024 18:35 UTC](https://community.ipfire.org/t/monitoring-webproxy-service-and-location-db/11780 "2024-06-21T18:35:12Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![pablo78](https://community.ipfire.org/user_avatar/community.ipfire.org/pablo78/32/12788_2.png) [@pablo78](https://community.ipfire.org/u/pablo78)\
**Post date:** [21 June 2024 18:35 UTC](https://community.ipfire.org/t/monitoring-webproxy-service-and-location-db/11780/1 "2024-06-21T18:35:13Z")

</div>

Hello

I monitor my ipfire system via SSH using CheckMK.  
Today I noticed that the web proxy service was not running and the location database was out of date.

→ [https://community.ipfire.org/t/ubuntu-repo-not-accessible/11779/4](https://community.ipfire.org/t/ubuntu-repo-not-accessible/11779/4)

How can I monitor the status of the web proxy service?  
Is there a process?

What about checking the location database and its up-to-dateness?

Thanks in advance  
Paul

---

<div class="post-metadata">

**Author:** ![markadewet](https://community.ipfire.org/user_avatar/community.ipfire.org/markadewet/32/16561_2.png) [@markadewet](https://community.ipfire.org/u/markadewet)\
**Post date:** [21 June 2024 19:04 UTC](https://community.ipfire.org/t/monitoring-webproxy-service-and-location-db/11780/2 "2024-06-21T19:04:33Z")

</div>

With thanks and acknowledgment to @bonnietwin:  
Just in case could you try to run `location update`  
There has been an issue as per this post onwards.

> [@Squid was not started at RPI](https://community.ipfire.org/t/squid-was-not-started-at-rpi/11528/2):
>
> Hi guys!!!. I have the same problem but I have been able to determine what is causing it. If I check the following boxes, it does not start the WebProxy: The funny thing is that yesterday, everything was working perfectly. I have tried restarting the Operator’s Router from the Router’s Web Interface (I need to try doing a physical shutdown) but it has not been solved. Has anyone else had the same thing happen to them?. Gracias y saludos desde España.

---

<div class="post-metadata">

**Author:** ![bbitsch](https://community.ipfire.org/user_avatar/community.ipfire.org/bbitsch/32/7420_2.png) [@bbitsch](https://community.ipfire.org/u/bbitsch)\
**Post date:** [21 June 2024 19:21 UTC](https://community.ipfire.org/t/monitoring-webproxy-service-and-location-db/11780/3 "2024-06-21T19:21:57Z")

</div>

To be precise:  
How old was the database? IMO the update period is 1 week.  
The problem was located in the location db file and/or the asnbl-helper program.  
Most topics about this issue showed the stopping of squid, which can be seen in the WUI yet. The reason of the stopping could be seen in the logs.

To minimize the problem of faulty db files a shorter update period could be considered. But this demands konowledge about the error in the file and the error handling in the helper prog.

---

<div class="post-metadata">

**Author:** ![bonnietwin](https://community.ipfire.org/user_avatar/community.ipfire.org/bonnietwin/32/12350_2.png) [@bonnietwin](https://community.ipfire.org/u/bonnietwin)\
**Post date:** [21 June 2024 19:58 UTC](https://community.ipfire.org/t/monitoring-webproxy-service-and-location-db/11780/4 "2024-06-21T19:58:36Z")

</div>

> [@pablo78](#):
>
> How can I monitor the status of the web proxy service?  
> Is there a process?

Yes there is a process. That is how the status of stopped or running is obtained in the Services menu.

The web proxy status can be found with the following command

`/etc/rc.d/init.d/squid status`

---

<div class="post-metadata">

**Author:** ![bonnietwin](https://community.ipfire.org/user_avatar/community.ipfire.org/bonnietwin/32/12350_2.png) [@bonnietwin](https://community.ipfire.org/u/bonnietwin)\
**Post date:** [21 June 2024 20:07 UTC](https://community.ipfire.org/t/monitoring-webproxy-service-and-location-db/11780/5 "2024-06-21T20:07:12Z")

</div>

> [@bbitsch](#):
>
> How old was the database? IMO the update period is 1 week.

The update period is 1 week from when fcron was started so different IPFire’s will update weekly but the specific date in the week will be different.

> [@bbitsch](#):
>
> To minimize the problem of faulty db files a shorter update period could be considered.

I think users need to be careful with this.

Every IPFire that is running 24/7 will get updated currently every week.

If that period is reduced then the load on the IPFire location database server would increase.

I would expect that to ensure the load on the server is not too excessive there will be code on the server to blacklist IP’s that try and access too frequently.

---

<div class="post-metadata">

**Author:** ![pablo78](https://community.ipfire.org/user_avatar/community.ipfire.org/pablo78/32/12788_2.png) [@pablo78](https://community.ipfire.org/u/pablo78)\
**Post date:** [30 June 2024 18:33 UTC](https://community.ipfire.org/t/monitoring-webproxy-service-and-location-db/11780/6 "2024-06-30T18:33:57Z")

</div>

I am now monitoring the Squid process and hope to be informed promptly if it stops again

 ![grafik](https://community.ipfire.org/uploads/default/original/2X/c/c70e5e8aa7cef5b986318d2d2d60ed418cbdb279.png)
