Topic: Squid

[david000]

Code: [Select]

Subject:  Cron <root@sme10> squid -k rotate

squid: ERROR: Could not send signal 10 to process 1849: (3) No such process
After the last couple of server updates I'm seeing Cron squid email alerts.   A quick google suggested a restart should fix it, which it did on the first occasion. I need to restart again to fix the current one.

I wondered how to ID the root cause  ? 

[ReetP]

We know there are issue with logging.

JP had been doing a huge rewrite of the logging code whist working stupid hours a day in hospital and with two young children.

https://bugs.koozali.org/show_bug.cgi?id=10484
https://bugs.koozali.org/show_bug.cgi?id=946
https://bugs.koozali.org/show_bug.cgi?id=11873
https://bugs.koozali.org/show_bug.cgi?id=11867
https://bugs.koozali.org/show_bug.cgi?id=11866
https://bugs.koozali.org/show_bug.cgi?id=11813

And probably some others I have missed. All of this will be coming out soon. Currently I think ka lot of rpms are in testing - please feel free to try them on a TEST VM and report back.

You should REALLY follow all bugs to keep abreast of thing via Bugzilla, some of the wiki bug pages, or the bug mailing list:

https://lists.contribs.org/mailman/listinfo/bugteam

[david000]

Thanks, ReetP.  I'll fire up the VM and have a look at testing some RPMs when I can get to it.

Best


David

[TerryF]

Currently have a sytem running with all the latest logging updates, test box only at this stage, so far so good, hasnt blown up as yet still a work in progress, please jump in and test more hands etc

[Jean-Philippe Pialasse]

squid error is probably not related.  it is more related to log rotate. 
just noise.
unless you get issue like unable to browse internet after the cron email. 


speaking of updates it works smoothly. probably needs to add few more filter because systemd spams a lot to messages now

[david000]

squid error is probably not related.  it is more related to log rotate. 
just noise.
unless you get issue like unable to browse internet after the cron email. 


speaking of updates it works smoothly. probably needs to add few more filter because systemd spams a lot to messages now

For my implementation we only collect mail and view locally using the web mail. We also use Ibays for small bits of user storage. I'm not seeing any issues in terms of functionality.

On the updates, they seem to work smoothly with the exception where a couple of times it seems to have hung during the server manager install, where IIRC it was doing a php update (maybe).  There was a note on here which mentioned it from a different user.  If it happens again I'll note how far it gets before I restart\reconfigure.



 

[Jean-Philippe Pialasse]

so just noise in your case. 
note however if sme server is your gateway by default it is transparent proxying your web browsing so it squid fails you might have issue browsing.

manager update is not that reliable currently because of added security level over the years like csrf tokens, session timeout, and probably httpd restart following php or web related rpms. few bugs are open about that. 

[david000]

On updates is it better not use the server manager and instead go with #yum update from Putty ?

[Jean-Philippe Pialasse]

yes. 

probably future will use an update method similar to what proxmox do: a webconsole with the command running on loading. 

[Peasant]

That was the error that alerted me to the squid problem I had a couple of weeks ago - squid wouldn't start at all because of a squid.pid file that had been left behind for some reason.

It's interesting that you are having the problem of having to restart squid after doing updates. On my own machine I have the same problem, but with dovecot and fail2ban. I've not had time to investigate any further, though I'm sure I came across a post somewhere that said that fail2ban would not start after an update.

[Jean-Philippe Pialasse]

That was the error that alerted me to the squid problem I had a couple of weeks ago - squid wouldn't start at all because of a squid.pid file that had been left behind for some reason.

here this is not just log noise but we have something that actually fails. 

any template custom for squid ?
any change tot he default squid db values ?

[Peasant]

here this is not just log noise but we have something that actually fails. 

any template custom for squid ?
any change tot he default squid db values ?

It was a clean install on a new server, and I had just completed a restore from backup made from the Server Manager. The first sign of a problem was that Opera and Edge browsers couldn't connect, but Firefox worked fine. Then I got the error email the next morning, and on further investigation found that squid had not started.

After a bit of googling I found that this could be caused by a squid.pid file, and I eventually found it, deleted it, and everything has been fine since. Squid started OK on the next reboot. However I've not done any updates yet, so that will be the next test. The thread is here https://forums.koozali.org/index.php/topic,54768.0.html

The problem on my machine is dovecot not starting after installing updates - as I said, I've not had time to do any diagnostics, or look at log files to see what is going on. I've not even had time to see if it will start after a straight reboot. Fail2ban doesn't start either, but I'm sure I've seen a thread on that elsewhere.

[Jean-Philippe Pialasse]

let’s use the same wording.

if there is a restore this is not a clean install.

Would you say this is a scoop of unflavored ice cream mixed with chocolate and mint flavors ?

So you have a SME 10 with workstation restore from your v9 and squid was not working.  Symptoms were browsers which were configured to use the proxy were not able to display any website and in place were displaying a network access error.
While a browser not configured to use the proxy was fine browsing the internet. 

First question have you issued the post-upgrade and rebooted after your restored ?
if not this is normal to have all expected system down.

Second question, what returns /sbin/e-smith/templates

Third question, what returns config show squid

[Peasant]

let’s use the same wording.

if there is a restore this is not a clean install.

Would you say this is a scoop of unflavored ice cream mixed with chocolate and mint flavors ?

So you have a SME 10 with workstation restore from your v9 and squid was not working.  Symptoms were browsers which were configured to use the proxy were not able to display any website and in place were displaying a network access error.
While a browser not configured to use the proxy was fine browsing the internet. 

First question have you issued the post-upgrade and rebooted after your restored ?
if not this is normal to have all expected system down.

Second question, what returns /sbin/e-smith/templates

Third question, what returns config show squid

I stand corrected, you are right, it wasn't a clean install. In my defence I had followed the sequence required to restore a new server to the letter. You were very good in helping me some time ago on this, and gave me detailed instructions.

Question 1: Yes, I had done signal-event post-upgrade; signal-event reboot from the command line on the server, twice.

I won't have the answer to either of the other questions for a few days, as the machine is remote, and although I can access the server manager, I cannot access the server using a terminal.

[david000]

An update from my side,

updating via yum update seems to have been more effective and the squid emails have gone away.