Search squid archive

Re: Error Question

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2024-06-12 17:51, Jonathan Lee wrote:
when killing squid I only get the following and no core dumps core does does work

Glad you have a working "sanity check" test! I agree with FreeBSD forum folks that you have proven that your OS does have core dumps enabled (in general). Now we need to figure out what is the difference between that working test script and Squid.

Please start Squid from the command line, with -N command line option (among others that you might be using already), just like you start the "sanity check" test script. And then kill Squid as you kill the test script.

If the above does not produce a Squid core file, then I would suspect that Squid runs as "squid" user while the test script runs as "root". Try starting the test script as "squid" user (you may be able to use "sudo -u squid ..." for that).

If same user does not expose the difference, start the test script from the directory where you told Squid to dump core.


HTH,

Alex.


I have tested it with a sanity check with the help of FreeBSD forum users. However it just does not show a core dump for me on anything kill -11 kill -6 killall or kill -SIGABRT. I have it set in the config to use coredump directory also forums.freebsd.org <https://forums.freebsd.org/threads/core-dumps.93778/page-2>


Jun 12 14:49:09	kernel	pid 87824 (squid), jid 0, uid 100: exited on signal 6
Jun 12 14:47:52	kernel	pid 87551 (squid), jid 0, uid 0: exited on signal 11


On Jun 12, 2024, at 10:19, Jonathan Lee <jonathanlee571@xxxxxxxxx> wrote:

You know what it was, it needed to be bound to the loopback and not just the LAN, again I am still working on getting a core dump file manually. Will update once I get one. Chmod might be needed.
Sent from my iPhone

On Jun 12, 2024, at 06:13, Alex Rousskov <rousskov@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

On 2024-06-11 23:32, Jonathan Lee wrote:

So I just run this on command line SIGABRT squid?

On Unix-like systems, the command to send a process a signal is called "kill": https://www.man7.org/linux/man-pages/man1/kill.1p.html

For example, if you want to abort a Squid worker process that has OS process ID (PID) 12345, you may do something like this:

  sudo kill -SIGABRT 12345

You can use "ps" or "top" commands to learn PIDs of processes you want to signal.


also added an item to the Netgate forum to, but not many users are Squid wizards

Beyond using a reasonable coredump_dir value in squid.conf, the system administration problems you need to solve to enable Squid core dumps are most likely not specific to Squid.


HTH,

Alex.


It’s funny as soon as I enabled the sysctl command and set the directory it won’t crash anymore. I also changed it to reside on the loopback before it was only on my lan interface. I run an external drive as my swap partition or a swap drive, it works I get crash reports when playing around with stuff. /dev/da0 or something it dumps to it and when it reboots shows in the var/crash folder and will display on gui report ready, again if anyone else knows pfSense let me know. I also added an item to the Netgate forum to, but not many users are Squid wizards so it might take a long time to get any community input over there.



_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.squid-cache.org/listinfo/squid-users




[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux