No entries before (10:31:24 -> 12:31:27): 2015/06/18 10:31:24 kid1| Beginning Validation Procedure 2015/06/18 10:31:24 kid1| Completed Validation Procedure 2015/06/18 10:31:24 kid1| Validated 0 Entries 2015/06/18 10:31:24 kid1| store_swap_size = 0.00 KB 2015/06/18 10:31:24 kid1| Accepting SSL bumped HTTP Socket connections at local=0.0.0.0:3128 remote=[::] FD 13 flags=1 2015/06/18 10:31:24 kid1| Accepting SNMP messages on 0.0.0.0:3401 2015/06/18 10:31:25 kid1| storeLateRelease: released 0 objects 2015/06/18 11:30:37 kid1| Error negotiating SSL connection on FD 17: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca (1/0) 2015/06/18 11:30:37 kid1| Error negotiating SSL connection on FD 17: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca (1/0) 2015/06/18 12:31:27 kid1| Set Current Directory to /squid-cache01/ 2015/06/18 12:31:27 kid1| Starting Squid Cache version 3.5.5 for x86_64-unknown-linux-gnu... 2015/06/18 12:31:27 kid1| Service Name: squid 2015/06/18 12:31:27 kid1| Process ID 1174 2015/06/18 12:31:27 kid1| Process Roles: worker 2015/06/18 12:31:27 kid1| With 32768 file descriptors available 2015/06/18 12:31:27 kid1| Initializing IP Cache... ... ... In /var/log/messages just a hint for SIGABRT (and the timestamp is always in 2h steps...): 2015-06-18T06:31:16.393051+02:00 proxy squid[21123]: Squid Parent: (squid-1) process 5770 exited due to signal 6 with status 0 2015-06-18T08:31:18.329729+02:00 proxy squid[29257]: Squid Parent: (squid-1) process 29261 exited due to signal 6 with status 0 2015-06-18T10:31:21.421409+02:00 proxy squid[29257]: Squid Parent: (squid-1) process 10384 exited due to signal 6 with status 0 2015-06-18T12:31:24.533701+02:00 proxy squid[29257]: Squid Parent: (squid-1) process 23816 exited due to signal 6 with status 0 But no hints, why squid will be killed with SIGABRT.... On Thu, Jun 18, 2015 at 11:19 AM, Ralf Hildebrandt <Ralf.Hildebrandt@xxxxxxxxxx> wrote: > * Tom Tom <tomtux007@xxxxxxxxx>: >> Hi >> >> Squid 3.5.5 on a SLES12 box with Rock and SSL-Bump enabled, reloads >> itself after every 2 hours (and only if there was initial some low >> traffic through it). Squid 3.3.13 on the same box doesn't reload >> itself after 2 hours. >> >> In the cache.log are no suspicious entries. Everything looks and feels >> normal (the same log is shown at 06:31:xx and 08:31:xx -> every 2 >> hours): > > It looks like squid is restarting itself; the logs prior to that should > indicate why. > > Maybe running in gdb yields more info: > http://wiki.squid-cache.org/SquidFaq/BugReporting > >> 2015/06/18 10:31:24 kid1| Starting Squid Cache version 3.5.5 for >> x86_64-unknown-linux-gnu... > > -- > Ralf Hildebrandt Charite Universitätsmedizin Berlin > ralf.hildebrandt@xxxxxxxxxx Campus Benjamin Franklin > http://www.charite.de Hindenburgdamm 30, 12203 Berlin > Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155 > _______________________________________________ > squid-users mailing list > squid-users@xxxxxxxxxxxxxxxxxxxxx > http://lists.squid-cache.org/listinfo/squid-users _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
