Re: squid reorg
Hi. After build squid with --disable-arch-native the squid server was able to start. I have copied your ./config line. ### squid-3.4.2# ./configure --disable-strict-error-checking --enable-shared --datadir=/usr/local/share/squid --libexecdir=/usr/local/libexec/squid --disable-loadable-modules --enable-arp-acl --enable-auth --enable-delay-pools --enable-follow-x-forwarded-for --enable-forw-via-db --enable-http-violations --enable-icap-client --enable-ipv6 --enable-referer-log --enable-removal-policies=lru heap --enable-ssl --enable-stacktraces --with-default-user=_squid --with-filedescriptors=8192 --with-pidfile=/var/run/squid.pid --with-pthreads --with-swapdir=/var/squid/cache --enable-pf-transparent --prefix=/usr/local --sysconfdir=/etc/squid --mandir=/usr/local/man --infodir=/usr/local/info --localstatedir=/var/squid --disable-silent-rules --disable-arch-native ### Cheers Aleks Am 24-01-2014 20:45, schrieb Aleksandar Lazic: Hi. The squid-3.3.11 runs ok. Am 24-01-2014 12:40, schrieb Aleksandar Lazic: As soon as I'am back at home I will install it. Am 24-01-2014 09:59, schrieb Stuart Henderson: I suspect it's trying to use 128-bit atomic ops (CMPXCHG16B) which this cpu doesn't support (no CX16 in the cpu flags - thanks for the complete dmesg, and yes this is a good place to report the problem). I'll take a look into it. Could you try squid-3.3 too please, so we can see if that also has this problem? Aleksandar Lazic al-obdpo...@none.at wrote: Hi. I got Illegal instruction (core dumped) after installation. I have done the following. PKG_PATH=http://openbsd.cs.fau.de/pub/OpenBSD/snapshots/packages/i386/ export PKG_PATH pkg_add -i -v squid choosed squid-3.4.2 vi /etc/squid/squid.conf changed the line http_port 3128 to http_port 3128 intercept dmesg OpenBSD 5.5-beta (GENERIC) #232: Fri Jan 17 15:59:15 MST 2014 t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Geode(TM) Integrated Processor by AMD PCS (AuthenticAMD 586-class) 499 MHz cpu0: FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CFLUSH,MMX,MMXX,3DNOW2,3DNOW real mem = 536375296 (511MB) avail mem = 515727360 (491MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 20/70/03, BIOS32 rev. 0 @ 0xfac40 pcibios0 at bios0: rev 2.0 @ 0xf/0x1 pcibios0: pcibios_get_intr_routing - function not supported pcibios0: PCI IRQ Routing information unavailable. pcibios0: PCI bus #0 is the last bus bios0: ROM list: 0xc8000/0xa800 cpu0 at mainbus0: (uniprocessor) mtrr: K6-family MTRR support (2 registers) amdmsr0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (bios) 0:20:0: io address conflict 0x6100/0x100 0:20:0: io address conflict 0x6200/0x200 pchb0 at pci0 dev 1 function 0 AMD Geode LX rev 0x33 glxsb0 at pci0 dev 1 function 2 AMD Geode LX Crypto rev 0x00: RNG AES vr0 at pci0 dev 6 function 0 VIA VT6105M RhineIII rev 0x96: irq 11, address 00:00:24:d0:6f:34 ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034 vr1 at pci0 dev 7 function 0 VIA VT6105M RhineIII rev 0x96: irq 5, address 00:00:24:d0:6f:35 ukphy1 at vr1 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034 vr2 at pci0 dev 8 function 0 VIA VT6105M RhineIII rev 0x96: irq 9, address 00:00:24:d0:6f:36 ukphy2 at vr2 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034 vr3 at pci0 dev 9 function 0 VIA VT6105M RhineIII rev 0x96: irq 12, address 00:00:24:d0:6f:37 ukphy3 at vr3 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034 ral0 at pci0 dev 14 function 0 Ralink RT2860 rev 0x00: irq 10, address 98:fc:11:eb:3c:65 ral0: MAC/BBP RT2860 (rev 0x0103), RF RT2850 (MIMO 2T2R) hifn0 at pci0 dev 17 function 0 Hifn 7955/7954 rev 0x00: LZS 3DES ARC4 MD5 SHA1 RNG AES PK, 32KB dram, irq 15 glxpcib0 at pci0 dev 20 function 0 AMD CS5536 ISA rev 0x03: rev 3, 32-bit 3579545Hz timer, watchdog, gpio, i2c gpio0 at glxpcib0: 32 pins iic0 at glxpcib0 pciide0 at pci0 dev 20 function 2 AMD CS5536 IDE rev 0x01: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: SDCFXS-016G wd0: 1-sector PIO, LBA48, 15279MB, 31293360 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 pciide0: channel 1 ignored (disabled) ohci0 at pci0 dev 21 function 0 AMD CS5536 USB rev 0x02: irq 7, version 1.0, legacy support ehci0 at pci0 dev 21 function 1 AMD CS5536 USB rev 0x02: irq 7 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 AMD EHCI root hub rev 2.00/1.00 addr 1 isa0 at glxpcib0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com0: console com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard pcppi0 at isa0 port 0x61 spkr0 at pcppi0 nsclpcsio0 at isa0 port 0x2e/2: NSC PC87366 rev 9: GPIO VLM TMS gpio1 at nsclpcsio0: 29 pins npx0 at
Re: squid reorg
I suspect it's trying to use 128-bit atomic ops (CMPXCHG16B) which this cpu doesn't support (no CX16 in the cpu flags - thanks for the complete dmesg, and yes this is a good place to report the problem). I'll take a look into it. Could you try squid-3.3 too please, so we can see if that also has this problem? Aleksandar Lazic al-obdpo...@none.at wrote: Hi. I got Illegal instruction (core dumped) after installation. I have done the following. PKG_PATH=http://openbsd.cs.fau.de/pub/OpenBSD/snapshots/packages/i386/ export PKG_PATH pkg_add -i -v squid choosed squid-3.4.2 vi /etc/squid/squid.conf changed the line http_port 3128 to http_port 3128 intercept dmesg OpenBSD 5.5-beta (GENERIC) #232: Fri Jan 17 15:59:15 MST 2014 t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Geode(TM) Integrated Processor by AMD PCS (AuthenticAMD 586-class) 499 MHz cpu0: FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CFLUSH,MMX,MMXX,3DNOW2,3DNOW real mem = 536375296 (511MB) avail mem = 515727360 (491MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 20/70/03, BIOS32 rev. 0 @ 0xfac40 pcibios0 at bios0: rev 2.0 @ 0xf/0x1 pcibios0: pcibios_get_intr_routing - function not supported pcibios0: PCI IRQ Routing information unavailable. pcibios0: PCI bus #0 is the last bus bios0: ROM list: 0xc8000/0xa800 cpu0 at mainbus0: (uniprocessor) mtrr: K6-family MTRR support (2 registers) amdmsr0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (bios) 0:20:0: io address conflict 0x6100/0x100 0:20:0: io address conflict 0x6200/0x200 pchb0 at pci0 dev 1 function 0 AMD Geode LX rev 0x33 glxsb0 at pci0 dev 1 function 2 AMD Geode LX Crypto rev 0x00: RNG AES vr0 at pci0 dev 6 function 0 VIA VT6105M RhineIII rev 0x96: irq 11, address 00:00:24:d0:6f:34 ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034 vr1 at pci0 dev 7 function 0 VIA VT6105M RhineIII rev 0x96: irq 5, address 00:00:24:d0:6f:35 ukphy1 at vr1 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034 vr2 at pci0 dev 8 function 0 VIA VT6105M RhineIII rev 0x96: irq 9, address 00:00:24:d0:6f:36 ukphy2 at vr2 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034 vr3 at pci0 dev 9 function 0 VIA VT6105M RhineIII rev 0x96: irq 12, address 00:00:24:d0:6f:37 ukphy3 at vr3 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034 ral0 at pci0 dev 14 function 0 Ralink RT2860 rev 0x00: irq 10, address 98:fc:11:eb:3c:65 ral0: MAC/BBP RT2860 (rev 0x0103), RF RT2850 (MIMO 2T2R) hifn0 at pci0 dev 17 function 0 Hifn 7955/7954 rev 0x00: LZS 3DES ARC4 MD5 SHA1 RNG AES PK, 32KB dram, irq 15 glxpcib0 at pci0 dev 20 function 0 AMD CS5536 ISA rev 0x03: rev 3, 32-bit 3579545Hz timer, watchdog, gpio, i2c gpio0 at glxpcib0: 32 pins iic0 at glxpcib0 pciide0 at pci0 dev 20 function 2 AMD CS5536 IDE rev 0x01: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: SDCFXS-016G wd0: 1-sector PIO, LBA48, 15279MB, 31293360 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 pciide0: channel 1 ignored (disabled) ohci0 at pci0 dev 21 function 0 AMD CS5536 USB rev 0x02: irq 7, version 1.0, legacy support ehci0 at pci0 dev 21 function 1 AMD CS5536 USB rev 0x02: irq 7 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 AMD EHCI root hub rev 2.00/1.00 addr 1 isa0 at glxpcib0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com0: console com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard pcppi0 at isa0 port 0x61 spkr0 at pcppi0 nsclpcsio0 at isa0 port 0x2e/2: NSC PC87366 rev 9: GPIO VLM TMS gpio1 at nsclpcsio0: 29 pins npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 usb1 at ohci0: USB revision 1.0 uhub1 at usb1 AMD OHCI root hub rev 1.00/1.00 addr 1 vscsi0 at root scsibus0 at vscsi0: 256 targets softraid0 at root scsibus1 at softraid0: 256 targets root on wd0a (35dc92839f31a39d.a) swap on wd0b dump on wd0b # /usr/local/sbin/squid -X 2014/01/23 23:15:42.727| src/debug.cc(425) parseOptions: command-line -X overrides: ALL,7 2014/01/23 23:15:42.729| src/cache_manager.cc(102) registerProfile: registering legacy mem 2014/01/23 23:15:42.730| src/cache_manager.cc(87) registerProfile: registered profile: mem 2014/01/23 23:15:42.731| src/cache_manager.cc(102) registerProfile: registering legacy squidaio_counts 2014/01/23 23:15:42.732| src/cache_manager.cc(87) registerProfile: registered profile: squidaio_counts 2014/01/23 23:15:42.732| src/cache_manager.cc(87) registerProfile: registered profile: diskd 2014/01/23 23:15:42.733| src/fs/rock/RockStoreFileSystem.cc(44) setup: Will use Rock FS 2014/01/23 23:15:42.733| Startup: Initializing Authentication Schemes ... 2014/01/23 23:15:42.733| Startup: Initialized Authentication
Re: squid reorg
As soon as I'am back at home I will install it. Am 24-01-2014 09:59, schrieb Stuart Henderson: I suspect it's trying to use 128-bit atomic ops (CMPXCHG16B) which this cpu doesn't support (no CX16 in the cpu flags - thanks for the complete dmesg, and yes this is a good place to report the problem). I'll take a look into it. Could you try squid-3.3 too please, so we can see if that also has this problem? Aleksandar Lazic al-obdpo...@none.at wrote: Hi. I got Illegal instruction (core dumped) after installation. I have done the following. PKG_PATH=http://openbsd.cs.fau.de/pub/OpenBSD/snapshots/packages/i386/ export PKG_PATH pkg_add -i -v squid choosed squid-3.4.2 vi /etc/squid/squid.conf changed the line http_port 3128 to http_port 3128 intercept dmesg OpenBSD 5.5-beta (GENERIC) #232: Fri Jan 17 15:59:15 MST 2014 t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Geode(TM) Integrated Processor by AMD PCS (AuthenticAMD 586-class) 499 MHz cpu0: FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CFLUSH,MMX,MMXX,3DNOW2,3DNOW real mem = 536375296 (511MB) avail mem = 515727360 (491MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 20/70/03, BIOS32 rev. 0 @ 0xfac40 pcibios0 at bios0: rev 2.0 @ 0xf/0x1 pcibios0: pcibios_get_intr_routing - function not supported pcibios0: PCI IRQ Routing information unavailable. pcibios0: PCI bus #0 is the last bus bios0: ROM list: 0xc8000/0xa800 cpu0 at mainbus0: (uniprocessor) mtrr: K6-family MTRR support (2 registers) amdmsr0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (bios) 0:20:0: io address conflict 0x6100/0x100 0:20:0: io address conflict 0x6200/0x200 pchb0 at pci0 dev 1 function 0 AMD Geode LX rev 0x33 glxsb0 at pci0 dev 1 function 2 AMD Geode LX Crypto rev 0x00: RNG AES vr0 at pci0 dev 6 function 0 VIA VT6105M RhineIII rev 0x96: irq 11, address 00:00:24:d0:6f:34 ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034 vr1 at pci0 dev 7 function 0 VIA VT6105M RhineIII rev 0x96: irq 5, address 00:00:24:d0:6f:35 ukphy1 at vr1 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034 vr2 at pci0 dev 8 function 0 VIA VT6105M RhineIII rev 0x96: irq 9, address 00:00:24:d0:6f:36 ukphy2 at vr2 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034 vr3 at pci0 dev 9 function 0 VIA VT6105M RhineIII rev 0x96: irq 12, address 00:00:24:d0:6f:37 ukphy3 at vr3 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034 ral0 at pci0 dev 14 function 0 Ralink RT2860 rev 0x00: irq 10, address 98:fc:11:eb:3c:65 ral0: MAC/BBP RT2860 (rev 0x0103), RF RT2850 (MIMO 2T2R) hifn0 at pci0 dev 17 function 0 Hifn 7955/7954 rev 0x00: LZS 3DES ARC4 MD5 SHA1 RNG AES PK, 32KB dram, irq 15 glxpcib0 at pci0 dev 20 function 0 AMD CS5536 ISA rev 0x03: rev 3, 32-bit 3579545Hz timer, watchdog, gpio, i2c gpio0 at glxpcib0: 32 pins iic0 at glxpcib0 pciide0 at pci0 dev 20 function 2 AMD CS5536 IDE rev 0x01: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: SDCFXS-016G wd0: 1-sector PIO, LBA48, 15279MB, 31293360 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 pciide0: channel 1 ignored (disabled) ohci0 at pci0 dev 21 function 0 AMD CS5536 USB rev 0x02: irq 7, version 1.0, legacy support ehci0 at pci0 dev 21 function 1 AMD CS5536 USB rev 0x02: irq 7 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 AMD EHCI root hub rev 2.00/1.00 addr 1 isa0 at glxpcib0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com0: console com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard pcppi0 at isa0 port 0x61 spkr0 at pcppi0 nsclpcsio0 at isa0 port 0x2e/2: NSC PC87366 rev 9: GPIO VLM TMS gpio1 at nsclpcsio0: 29 pins npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 usb1 at ohci0: USB revision 1.0 uhub1 at usb1 AMD OHCI root hub rev 1.00/1.00 addr 1 vscsi0 at root scsibus0 at vscsi0: 256 targets softraid0 at root scsibus1 at softraid0: 256 targets root on wd0a (35dc92839f31a39d.a) swap on wd0b dump on wd0b # /usr/local/sbin/squid -X 2014/01/23 23:15:42.727| src/debug.cc(425) parseOptions: command-line -X overrides: ALL,7 2014/01/23 23:15:42.729| src/cache_manager.cc(102) registerProfile: registering legacy mem 2014/01/23 23:15:42.730| src/cache_manager.cc(87) registerProfile: registered profile: mem 2014/01/23 23:15:42.731| src/cache_manager.cc(102) registerProfile: registering legacy squidaio_counts 2014/01/23 23:15:42.732| src/cache_manager.cc(87) registerProfile: registered profile: squidaio_counts 2014/01/23 23:15:42.732| src/cache_manager.cc(87) registerProfile: registered profile: diskd 2014/01/23 23:15:42.733| src/fs/rock/RockStoreFileSystem.cc(44) setup: Will use Rock FS 2014/01/23 23:15:42.733| Startup: Initializing
Re: squid reorg
Hi. The squid-3.3.11 runs ok. Am 24-01-2014 12:40, schrieb Aleksandar Lazic: As soon as I'am back at home I will install it. Am 24-01-2014 09:59, schrieb Stuart Henderson: I suspect it's trying to use 128-bit atomic ops (CMPXCHG16B) which this cpu doesn't support (no CX16 in the cpu flags - thanks for the complete dmesg, and yes this is a good place to report the problem). I'll take a look into it. Could you try squid-3.3 too please, so we can see if that also has this problem? Aleksandar Lazic al-obdpo...@none.at wrote: Hi. I got Illegal instruction (core dumped) after installation. I have done the following. PKG_PATH=http://openbsd.cs.fau.de/pub/OpenBSD/snapshots/packages/i386/ export PKG_PATH pkg_add -i -v squid choosed squid-3.4.2 vi /etc/squid/squid.conf changed the line http_port 3128 to http_port 3128 intercept dmesg OpenBSD 5.5-beta (GENERIC) #232: Fri Jan 17 15:59:15 MST 2014 t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Geode(TM) Integrated Processor by AMD PCS (AuthenticAMD 586-class) 499 MHz cpu0: FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CFLUSH,MMX,MMXX,3DNOW2,3DNOW real mem = 536375296 (511MB) avail mem = 515727360 (491MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 20/70/03, BIOS32 rev. 0 @ 0xfac40 pcibios0 at bios0: rev 2.0 @ 0xf/0x1 pcibios0: pcibios_get_intr_routing - function not supported pcibios0: PCI IRQ Routing information unavailable. pcibios0: PCI bus #0 is the last bus bios0: ROM list: 0xc8000/0xa800 cpu0 at mainbus0: (uniprocessor) mtrr: K6-family MTRR support (2 registers) amdmsr0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (bios) 0:20:0: io address conflict 0x6100/0x100 0:20:0: io address conflict 0x6200/0x200 pchb0 at pci0 dev 1 function 0 AMD Geode LX rev 0x33 glxsb0 at pci0 dev 1 function 2 AMD Geode LX Crypto rev 0x00: RNG AES vr0 at pci0 dev 6 function 0 VIA VT6105M RhineIII rev 0x96: irq 11, address 00:00:24:d0:6f:34 ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034 vr1 at pci0 dev 7 function 0 VIA VT6105M RhineIII rev 0x96: irq 5, address 00:00:24:d0:6f:35 ukphy1 at vr1 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034 vr2 at pci0 dev 8 function 0 VIA VT6105M RhineIII rev 0x96: irq 9, address 00:00:24:d0:6f:36 ukphy2 at vr2 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034 vr3 at pci0 dev 9 function 0 VIA VT6105M RhineIII rev 0x96: irq 12, address 00:00:24:d0:6f:37 ukphy3 at vr3 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034 ral0 at pci0 dev 14 function 0 Ralink RT2860 rev 0x00: irq 10, address 98:fc:11:eb:3c:65 ral0: MAC/BBP RT2860 (rev 0x0103), RF RT2850 (MIMO 2T2R) hifn0 at pci0 dev 17 function 0 Hifn 7955/7954 rev 0x00: LZS 3DES ARC4 MD5 SHA1 RNG AES PK, 32KB dram, irq 15 glxpcib0 at pci0 dev 20 function 0 AMD CS5536 ISA rev 0x03: rev 3, 32-bit 3579545Hz timer, watchdog, gpio, i2c gpio0 at glxpcib0: 32 pins iic0 at glxpcib0 pciide0 at pci0 dev 20 function 2 AMD CS5536 IDE rev 0x01: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: SDCFXS-016G wd0: 1-sector PIO, LBA48, 15279MB, 31293360 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 pciide0: channel 1 ignored (disabled) ohci0 at pci0 dev 21 function 0 AMD CS5536 USB rev 0x02: irq 7, version 1.0, legacy support ehci0 at pci0 dev 21 function 1 AMD CS5536 USB rev 0x02: irq 7 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 AMD EHCI root hub rev 2.00/1.00 addr 1 isa0 at glxpcib0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com0: console com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard pcppi0 at isa0 port 0x61 spkr0 at pcppi0 nsclpcsio0 at isa0 port 0x2e/2: NSC PC87366 rev 9: GPIO VLM TMS gpio1 at nsclpcsio0: 29 pins npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 usb1 at ohci0: USB revision 1.0 uhub1 at usb1 AMD OHCI root hub rev 1.00/1.00 addr 1 vscsi0 at root scsibus0 at vscsi0: 256 targets softraid0 at root scsibus1 at softraid0: 256 targets root on wd0a (35dc92839f31a39d.a) swap on wd0b dump on wd0b # /usr/local/sbin/squid -X 2014/01/23 23:15:42.727| src/debug.cc(425) parseOptions: command-line -X overrides: ALL,7 2014/01/23 23:15:42.729| src/cache_manager.cc(102) registerProfile: registering legacy mem 2014/01/23 23:15:42.730| src/cache_manager.cc(87) registerProfile: registered profile: mem 2014/01/23 23:15:42.731| src/cache_manager.cc(102) registerProfile: registering legacy squidaio_counts 2014/01/23 23:15:42.732| src/cache_manager.cc(87) registerProfile: registered profile: squidaio_counts 2014/01/23 23:15:42.732| src/cache_manager.cc(87) registerProfile: registered profile: diskd 2014/01/23 23:15:42.733|
Re: squid reorg
Hi Stuart. I just seen your mail in the archive. http://marc.info/?t=13835139422r=1w=2 I want to use the latest squid 3.4 with intercept mode on http_port and https_port and pf divert-to on my soekris net5501-70 . I offer you to test the new 3.4 packages on current as soon as it is ready. Best regards Aleks
Re: squid reorg
On 2014/01/24 00:07, Aleksandar Lazic wrote: Hi Stuart. I just seen your mail in the archive. http://marc.info/?t=13835139422r=1w=2 I want to use the latest squid 3.4 with intercept mode on http_port and https_port and pf divert-to on my soekris net5501-70 . I offer you to test the new 3.4 packages on current as soon as it is ready. Best regards Aleks This is already in -current, test reports are welcome. $ sudo pkg_add squid Ambiguous: choose package for squid a 0: None 1: squid-3.3.11 2: squid-3.4.2 Your choice:
Re: squid reorg
Thank you. I will take a look and give feedback. Am 24-01-2014 00:12, schrieb Stuart Henderson: On 2014/01/24 00:07, Aleksandar Lazic wrote: Hi Stuart. I just seen your mail in the archive. http://marc.info/?t=13835139422r=1w=2 I want to use the latest squid 3.4 with intercept mode on http_port and https_port and pf divert-to on my soekris net5501-70 . I offer you to test the new 3.4 packages on current as soon as it is ready. Best regards Aleks This is already in -current, test reports are welcome. $ sudo pkg_add squid Ambiguous: choose package for squid a 0: None 1: squid-3.3.11 2: squid-3.4.2 Your choice:
squid reorg
Hi. I got Illegal instruction (core dumped) after installation. I have done the following. PKG_PATH=http://openbsd.cs.fau.de/pub/OpenBSD/snapshots/packages/i386/ export PKG_PATH pkg_add -i -v squid choosed squid-3.4.2 vi /etc/squid/squid.conf changed the line http_port 3128 to http_port 3128 intercept dmesg OpenBSD 5.5-beta (GENERIC) #232: Fri Jan 17 15:59:15 MST 2014 t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Geode(TM) Integrated Processor by AMD PCS (AuthenticAMD 586-class) 499 MHz cpu0: FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CFLUSH,MMX,MMXX,3DNOW2,3DNOW real mem = 536375296 (511MB) avail mem = 515727360 (491MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 20/70/03, BIOS32 rev. 0 @ 0xfac40 pcibios0 at bios0: rev 2.0 @ 0xf/0x1 pcibios0: pcibios_get_intr_routing - function not supported pcibios0: PCI IRQ Routing information unavailable. pcibios0: PCI bus #0 is the last bus bios0: ROM list: 0xc8000/0xa800 cpu0 at mainbus0: (uniprocessor) mtrr: K6-family MTRR support (2 registers) amdmsr0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (bios) 0:20:0: io address conflict 0x6100/0x100 0:20:0: io address conflict 0x6200/0x200 pchb0 at pci0 dev 1 function 0 AMD Geode LX rev 0x33 glxsb0 at pci0 dev 1 function 2 AMD Geode LX Crypto rev 0x00: RNG AES vr0 at pci0 dev 6 function 0 VIA VT6105M RhineIII rev 0x96: irq 11, address 00:00:24:d0:6f:34 ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034 vr1 at pci0 dev 7 function 0 VIA VT6105M RhineIII rev 0x96: irq 5, address 00:00:24:d0:6f:35 ukphy1 at vr1 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034 vr2 at pci0 dev 8 function 0 VIA VT6105M RhineIII rev 0x96: irq 9, address 00:00:24:d0:6f:36 ukphy2 at vr2 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034 vr3 at pci0 dev 9 function 0 VIA VT6105M RhineIII rev 0x96: irq 12, address 00:00:24:d0:6f:37 ukphy3 at vr3 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034 ral0 at pci0 dev 14 function 0 Ralink RT2860 rev 0x00: irq 10, address 98:fc:11:eb:3c:65 ral0: MAC/BBP RT2860 (rev 0x0103), RF RT2850 (MIMO 2T2R) hifn0 at pci0 dev 17 function 0 Hifn 7955/7954 rev 0x00: LZS 3DES ARC4 MD5 SHA1 RNG AES PK, 32KB dram, irq 15 glxpcib0 at pci0 dev 20 function 0 AMD CS5536 ISA rev 0x03: rev 3, 32-bit 3579545Hz timer, watchdog, gpio, i2c gpio0 at glxpcib0: 32 pins iic0 at glxpcib0 pciide0 at pci0 dev 20 function 2 AMD CS5536 IDE rev 0x01: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: SDCFXS-016G wd0: 1-sector PIO, LBA48, 15279MB, 31293360 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 pciide0: channel 1 ignored (disabled) ohci0 at pci0 dev 21 function 0 AMD CS5536 USB rev 0x02: irq 7, version 1.0, legacy support ehci0 at pci0 dev 21 function 1 AMD CS5536 USB rev 0x02: irq 7 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 AMD EHCI root hub rev 2.00/1.00 addr 1 isa0 at glxpcib0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com0: console com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard pcppi0 at isa0 port 0x61 spkr0 at pcppi0 nsclpcsio0 at isa0 port 0x2e/2: NSC PC87366 rev 9: GPIO VLM TMS gpio1 at nsclpcsio0: 29 pins npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 usb1 at ohci0: USB revision 1.0 uhub1 at usb1 AMD OHCI root hub rev 1.00/1.00 addr 1 vscsi0 at root scsibus0 at vscsi0: 256 targets softraid0 at root scsibus1 at softraid0: 256 targets root on wd0a (35dc92839f31a39d.a) swap on wd0b dump on wd0b # /usr/local/sbin/squid -X 2014/01/23 23:15:42.727| src/debug.cc(425) parseOptions: command-line -X overrides: ALL,7 2014/01/23 23:15:42.729| src/cache_manager.cc(102) registerProfile: registering legacy mem 2014/01/23 23:15:42.730| src/cache_manager.cc(87) registerProfile: registered profile: mem 2014/01/23 23:15:42.731| src/cache_manager.cc(102) registerProfile: registering legacy squidaio_counts 2014/01/23 23:15:42.732| src/cache_manager.cc(87) registerProfile: registered profile: squidaio_counts 2014/01/23 23:15:42.732| src/cache_manager.cc(87) registerProfile: registered profile: diskd 2014/01/23 23:15:42.733| src/fs/rock/RockStoreFileSystem.cc(44) setup: Will use Rock FS 2014/01/23 23:15:42.733| Startup: Initializing Authentication Schemes ... 2014/01/23 23:15:42.733| Startup: Initialized Authentication Scheme 'basic' 2014/01/23 23:15:42.733| Startup: Initialized Authentication Scheme 'digest' 2014/01/23 23:15:42.733| Startup: Initialized Authentication Scheme 'negotiate' 2014/01/23 23:15:42.733| Startup: Initialized Authentication Scheme 'ntlm' 2014/01/23 23:15:42.733| Startup: Initialized Authentication. 2014/01/23 23:15:42.739|
Re: squid reorg.
Hi, On Sun, Nov 03, 2013 at 09:23:01PM +, Stuart Henderson wrote: The diff at http://junkpile.org/squid.reorg.diff (not inline as it's 360kB) reorganises the squid ports; it removes squid27 now that the main squid port works on more arches, and splits www/squid into stable (with the latest 3.3 release) and snapshot (adding a 3.4 release). It also enables the rock storage backend (particularly useful for people playing with the SMP support) and builds a few more helper applications (mostly switched from build a fixed list of helpers to build everything we can and then remove what we don't want). Any comments, OKs? I just swapped out Squid 3.3.8 from a 5.4 machine because of severe problems: The proxy crashed frequently with this line in cache.log: FATAL: Too few filedescriptors available in the system (97 usable of 8192). But I had this in /etc/squid/squid.conf: max_filedescriptors 1024 I also had this in my /etc/login.conf: proxy:\ :ignorenologin:\ :datasize=infinity:\ :maxproc=128:\ :openfiles=1024:\ :stacksize-cur=64M:\ :localcipher=blowfish,8:\ :tc=default: And I had the login class set to 'proxy' using vipw. Now I have renamed the login class to 'squid' and the 2.7 squid at least starts with this message: With 1024 file descriptors available Don't know whether the 3.4 line works better... I never had problems with squid on that machine since 3.x or 4.x, when I originally installed it, so I guess that it's squid 3.3.8 which was causing the problems. IOW, I'd probably rather kick out 3.3 instead of 2.7. Kind regards, --Toni++
Re: squid reorg.
On 2014/01/09 17:48, Toni Mueller wrote: I just swapped out Squid 3.3.8 from a 5.4 machine because of severe problems: The proxy crashed frequently with this line in cache.log: FATAL: Too few filedescriptors available in the system (97 usable of 8192). But I had this in /etc/squid/squid.conf: max_filedescriptors 1024 I also had this in my /etc/login.conf: proxy:\ :ignorenologin:\ :datasize=infinity:\ :maxproc=128:\ :openfiles=1024:\ :stacksize-cur=64M:\ :localcipher=blowfish,8:\ :tc=default: And I had the login class set to 'proxy' using vipw. Now I have renamed the login class to 'squid' and the 2.7 squid at least starts with this message: With 1024 file descriptors available Don't know whether the 3.4 line works better... You don't mention how you start squid, but if you use the rc.d script, the class *must* be named after the daemon, i.e. squid. As a proxy is necessarily FD-hungry I made sure the pkg-readme specifically covers this.. I never had problems with squid on that machine since 3.x or 4.x, when I originally installed it, so I guess that it's squid 3.3.8 which was causing the problems. IOW, I'd probably rather kick out 3.3 instead of 2.7. 2.7 hasn't been developed upstream for years, do you have enough information that you could file a bug or at least write a mail to their list about the handling when out of FDs? Last time I brought this up there, I got the impression squid is meant to handle this more cleanly..
Re: squid reorg.
Hi Stuart, On Thu, Jan 09, 2014 at 06:20:26PM +, Stuart Henderson wrote: On 2014/01/09 17:48, Toni Mueller wrote: proxy:\ :ignorenologin:\ :datasize=infinity:\ :maxproc=128:\ :openfiles=1024:\ :stacksize-cur=64M:\ :localcipher=blowfish,8:\ :tc=default: And I had the login class set to 'proxy' using vipw. Now I have renamed the login class to 'squid' and the 2.7 squid at least starts with this message: With 1024 file descriptors available Don't know whether the 3.4 line works better... You don't mention how you start squid, but if you use the rc.d script, the class *must* be named after the daemon, i.e. squid. yes, I use the rc.d script, but was not aware of this requirement. But squid did not respect the config file setting either, which motivated me to downgrade the package. As a proxy is necessarily FD-hungry I made sure the pkg-readme specifically covers this.. Of course - but I have kern.maxfiles = 16000, and still saw the problem. The kernel is 5.4 stable, now with an additional patch to silence bge(4) buffer overrun errors (based on a tip that Mike gave on misc@). 2.7 hasn't been developed upstream for years, Ok... :/ do you have enough information that you could file a bug or at least write a mail to their list about the handling when out of FDs? Last time I brought this up there, I got the impression squid is meant to handle this more cleanly.. Hmmm? I'm not sure what exactly you or they night want or need. I have these fatal notices in the log file and complaints of the users that Internet does not work. Is there a way that I can inspect the limits in effect for a given running process? Kind regards, --Toni++
Re: squid reorg.
On 2014/01/09 20:39, Toni Mueller wrote: Hi Stuart, On Thu, Jan 09, 2014 at 06:20:26PM +, Stuart Henderson wrote: On 2014/01/09 17:48, Toni Mueller wrote: proxy:\ :ignorenologin:\ :datasize=infinity:\ :maxproc=128:\ :openfiles=1024:\ :stacksize-cur=64M:\ :localcipher=blowfish,8:\ :tc=default: And I had the login class set to 'proxy' using vipw. Now I have renamed the login class to 'squid' and the 2.7 squid at least starts with this message: With 1024 file descriptors available Don't know whether the 3.4 line works better... You don't mention how you start squid, but if you use the rc.d script, the class *must* be named after the daemon, i.e. squid. yes, I use the rc.d script, but was not aware of this requirement. But squid did not respect the config file setting either, which motivated me to downgrade the package. As a proxy is necessarily FD-hungry I made sure the pkg-readme specifically covers this.. Of course - but I have kern.maxfiles = 16000, and still saw the problem. The kernel is 5.4 stable, now with an additional patch to silence bge(4) buffer overrun errors (based on a tip that Mike gave on misc@). squid can't itself do anything to raise the limit above what you have set in login.conf, kern.maxfiles is irrelevant if the login.conf limit for the class is lower. 2.7 hasn't been developed upstream for years, Ok... :/ do you have enough information that you could file a bug or at least write a mail to their list about the handling when out of FDs? Last time I brought this up there, I got the impression squid is meant to handle this more cleanly.. Hmmm? I'm not sure what exactly you or they night want or need. I have these fatal notices in the log file and complaints of the users that Internet does not work. If squid runs out of FDs, the idea is that it should clamp the connection limit to below what it finds it can use (though some people have occasionally run into high-cpu loops in that situation). http://www.squid-cache.org/mail-archive/squid-users/201305/0353.html If you don't have a squid class and use rc.d/squid, it will use limits from daemon, default 128 iirc. This might be beyond what it can cope with so perhaps it just exits, I'm not sure what is the intended behaviour then. Is there a way that I can inspect the limits in effect for a given running process? I'm not aware of a way.. Best I can suggest is to find what a newly created process in that group will get: sudo -c squid sh -c ulimit -n sudo -c daemon sh -c ulimit -n
Re: squid reorg.
On Thu, Jan 09, 2014 at 08:08:04PM +, Stuart Henderson wrote: On 2014/01/09 20:39, Toni Mueller wrote: Of course - but I have kern.maxfiles = 16000, and still saw the problem. squid can't itself do anything to raise the limit above what you have set in login.conf, kern.maxfiles is irrelevant if the login.conf limit for the class is lower. Yes - I only wanted to say that squid should imho not run into limits imposed elsewhere. I'm not sure what exactly you or they night want or need. I have these fatal notices in the log file and complaints of the users that Internet does not work. If squid runs out of FDs, the idea is that it should clamp the connection limit to below what it finds it can use (though some people have occasionally run into high-cpu loops in that situation). The cpu on that box is basically idle. If you don't have a squid class and use rc.d/squid, it will use limits from daemon, default 128 iirc. This might be beyond what it can cope with so perhaps it just exits, I'm not sure what is the intended behaviour then. Strange - it logged that it started with 8192 file descriptors, which is way beyond what I specified in two locations (also in the config file!), and what is in the 'daemon' login class. I have no idea where it gets this value from, or the minimum value I can configure there. Imho, problem #1 is that it ignores the config file setting, and problem #2 is that it does not gracefully cope with the out of FD situation. http://www.squid-cache.org/Doc/config/max_filedescriptors/ sudo -c squid sh -c ulimit -n sudo -c daemon sh -c ulimit -n Thank you! That gets me the expected values... Kind regards, --Toni++
squid reorg.
The diff at http://junkpile.org/squid.reorg.diff (not inline as it's 360kB) reorganises the squid ports; it removes squid27 now that the main squid port works on more arches, and splits www/squid into stable (with the latest 3.3 release) and snapshot (adding a 3.4 release). It also enables the rock storage backend (particularly useful for people playing with the SMP support) and builds a few more helper applications (mostly switched from build a fixed list of helpers to build everything we can and then remove what we don't want). Any comments, OKs?
Re: squid reorg.
On Sun, Nov 3, 2013, at 04:23 PM, Stuart Henderson wrote: The diff at http://junkpile.org/squid.reorg.diff (not inline as it's 360kB) reorganises the squid ports; it removes squid27 now that the main squid port works on more arches, and splits www/squid into stable (with the latest 3.3 release) and snapshot (adding a 3.4 release). It also enables the rock storage backend (particularly useful for people playing with the SMP support) and builds a few more helper applications (mostly switched from build a fixed list of helpers to build everything we can and then remove what we don't want). Any comments, OKs? I'm fine with it, I'm currently using the new Squid and had no plans to use the old one anyway. Then again I'm only root on amd64 and i386 systems. -- Shawn K. Quinn skqu...@rushpost.com
