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
