On 2/14/22 09:34, Majed Zouhairy wrote:
2022/02/14 17:29:50 kid1| Starting Squid Cache version 5.4
2022/02/14 17:29:56 kid1| FATAL: check failed: opening()
exception location: FwdState.cc(663) noteDestinationsEnd
...
2022/02/14 17:30:03 kid1| FATAL: check failed: opening()
exception
i restarted the system and now it shows:
2022/02/14 17:29:50 kid1| Starting Squid Cache version 5.4 for
x86_64-suse-linux-gnu...
2022/02/14 17:29:50 kid1| Service Name: squid
2022/02/14 17:29:50 kid1| Process ID 1731
2022/02/14 17:29:50 kid1| Process Roles: worker
2022/02/14 17:29:50 kid1| With
On 2/14/22 08:49, Majed Zouhairy wrote:
i have squid 4.17 on the machine assembled from source but i did an
uninstall
sudo make uninstall
before installing 5.4 from the package manager..should i have stopped
the squid before uninstalling?
or is there something else?
Sorry, I cannot give you
i have squid 4.17 on the machine assembled from source but i did an
uninstall
sudo make uninstall
before installing 5.4 from the package manager..should i have stopped
the squid before uninstalling?
or is there something else?
On 2/14/22 16:41, Alex Rousskov wrote:
On 2/14/22 07:25, Majed Zou
On 2/14/22 07:25, Majed Zouhairy wrote:
now on 5.4 i get:
...
2022/02/14 15:14:33 kid1| commBind Cannot bind socket FD 44 to [::]:8080: (98)
Address already in use
2022/02/14 15:14:33 kid1| Closing HTTP(S) port [::]:8080
2022/02/14 15:14:33 kid1| FATAL: Unable to open HTTP Socket
2022/02/14 15
now on 5.4 i get:
2022/02/14 15:14:32 kid1| FATAL: Unable to open HTTP Socket
2022/02/14 15:14:32 kid1| Squid Cache (Version 5.4): Terminated abnormally.
CPU Usage: 0.401 seconds = 0.357 user + 0.044 sys
Maximum Resident Size: 101920 KB
Page faults with physical i/o: 0
2022/02/14 15:14:32 kid1| C
On 1/18/22 2:51 AM, Amos Jeffries wrote:
> On 8/01/22 05:02, Alex Rousskov wrote:
>> On 1/7/22 9:34 AM, Amos Jeffries wrote:
>>> Others include altering the fundamental AsyncJob API behaviour -
>>> affecting every feature in Squid at their most fundamental levels.
>> I disagree with the above summ
On 8/01/22 05:02, Alex Rousskov wrote:
On 1/7/22 9:34 AM, Amos Jeffries wrote:
On 7/01/22 06:00, Alex Rousskov wrote:
On 1/6/22 6:53 AM, Majed Zouhairy wrote:
after upgrading today to 5.3 i'm getting:
2022/01/06 14:27:18 kid1| FATAL: check failed: opening()
exception location: FwdStat
On 1/7/22 9:34 AM, Amos Jeffries wrote:
> On 7/01/22 06:00, Alex Rousskov wrote:
>> On 1/6/22 6:53 AM, Majed Zouhairy wrote:
>>> after upgrading today to 5.3 i'm getting:
>>
>>> 2022/01/06 14:27:18 kid1| FATAL: check failed: opening()
>>> exception location: FwdState.cc(628) noteDestinationsEn
On 7/01/22 06:00, Alex Rousskov wrote:
On 1/6/22 6:53 AM, Majed Zouhairy wrote:
peace i have squid with ufdb guard, after upgrading today to 5.3 i'm
getting:
2022/01/06 14:27:18 kid1| FATAL: check failed: opening()
exception location: FwdState.cc(628) noteDestinationsEnd
what is the c
On 1/6/22 6:53 AM, Majed Zouhairy wrote:
> peace i have squid with ufdb guard, after upgrading today to 5.3 i'm
> getting:
> 2022/01/06 14:27:18 kid1| FATAL: check failed: opening()
> exception location: FwdState.cc(628) noteDestinationsEnd
> what is the cause?
This is most likely bug 5055 f
peace i have squid with ufdb guard, after upgrading today to 5.3 i'm
getting:
2022/01/06 14:47:35| Processing: acl localhet src 169.254.0.0/16 # RFC
3927 link-local (directly plugged) machines
2022/01/06 14:47:35| Processing: acl SSL_ports port 443
2022/01/06 14:47:35| Processing: acl S
12 matches
Mail list logo
