Re: haproxy syslog comptible
I don´t think it´s changed in 12 but on 11.2 I´m using in haproxy.conf global daemon maxconn 512 # Total Max Connections. This is dependent on ulimit nbproc 1 ssl-default-bind-options no-sslv3 no-tls-tickets ssl-default-bind-ciphers EECDH+AESGCM:AES256+EECDH:AES128+EECDH:AES256+RSA log 192.168.0.2 local2 defaults log global In syslog.conf # HAProxy local2.*/var/log/haproxy.log On 2019-06-24 16:56, sth...@nethelp.no wrote: I mean you talk about different syslogd, not from FreeBSD: syslogd: illegal option -- O usage: syslogd [-468ACcdFknosTuv] [-a allowed_peer] [-b bind_address] [-f config_file] [-l [mode:]path] [-m mark_interval] [-P pid_file] [-p log_socket] Ah, I am see -- I am need syslogd from FreeBSD-12, thx. The option certainly exists in 11.3-PRERELEASE also: SYNOPSIS syslogd [-468ACcdFHkNnosTuv] [-a allowed_peer] [-b bind_address] [-f config_file] [-l [mode:]path] [-m mark_interval] [-O format] [-P pid_file] [-p log_socket] [-S logpriv_socket] Steinar Haug, Nethelp consulting, sth...@nethelp.no ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: APU2, legacy firmware 4.0.22, FreeBSD 12.0 hangs in boot
On 2019-01-04 21:10, Kurt Jaeger wrote: Hi! What do the newer firmwares give you ? i.e. why upgrade ? On my APU3s I am running and havent seen any issues with it ? Are there new features ? I had an issue, FreeBSD 12.0 would only boot *very* slowly. That's why I started upgrading to legacy 4.0.22, which would not boot at all, then to 4.8.05, which worked 8-) I upgraded to 12.0-RELEASE-p1 yesterday and am running coreboot v4.0.18 on apu2c4 with no issues. \\Clay ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: troubleshooting before hard reset
On 2018-01-15 10:40, Eugene Grosbein wrote: 15.01.2018 16:31, Marko Cupać wrote: Hi, one of my ageing servers, HP DL380g5, which is serving a bunch of non-critical production jails on FreeBSD 11.1, bacame inaccessible over weekend. I have physical access, its disks and NICs are showing activity, but it doesn't send anything to monitor over VGA, also I guess it doesn't recognise keyboard (num lock led does nothing). Before I hard reset it, is there anything I can do to troubleshoot the problem? I tried serial port as well but it gives nothing on either 9600 or 115200 baud. I guess OS needs to be configured beforehand for serial access. Yes. If keyboard seems to be dead and there is no video output, I'm afraid you can't get anything useful from the box other than sniffing traffic from its MAC address, if any. And check MAC address table of network switch for server's MAC address if you have managed switch. Else, just reset it. Have you tried remote console access via the iLO? Sometimes that still works when the physical VGA doesn't. \\Clay ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.1 RELENG_9 Unable to cleanly dismount root partition on shutdown
On 27.08.2012 10:06, Matt Smith wrote: I posted on this mailing list two weeks ago and never received any replies so I decided to raise a PR via the web form. But I think I submitted it under the wrong category and it's marked as low priority as well. But I think this is something that is a potential serious problem if I end up getting a corrupted filesystem so I'm posting here again in the hope somebody can help this time. The PR is amd64/170646. I'm now running the latest RELENG_9 code as of 25th August as I've done a new buildworld/kernel. I still get the same problem. When I reboot it I get WARNING: / was not properly dismounted and it rebuilds from journal. On shutdown I get the messages pasted below. I'm running amd64 with GPT partitioning, UFS2 with softupdates and softupdates journalling enabled. I have a custom kernel but I don't think I took anything important out of it. Syncing disks, vnodes remaining...7 7 2 0 0 done All buffers synced. fsync: giving up on dirty 0xfe0007102780: tag devfs, type VCHR usecount 1, writecount 0, refcount 2292 mountedhere 0xfe00729ca00 flags (VI(0x200)) v_object 0xfe0005101910 ref 0 pages 23509 lock type devfs: EXCL by thread 0xfe00018fe08e0 (pid 1) dev label/root umount of / failed (35) Then when the box comes back up again it detects that / was not unmounted cleanly and recovers from journal before marking it clean once more. My uname: FreeBSD tao.xtaz.co.uk 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #0: Sat Aug 25 12:34:52 BST 2012 r...@tao.xtaz.co.uk:/usr/obj/usr/src/sys/TAO amd64 My glabel status: Name Status Components gpt/gptboot N/A ada0p1 gptid/bfe99d62-e00f-11e1-8623-00012e475ffb N/A ada0p1 label/root N/A ada0p2 label/swap N/A ada0p3 My fstab: /dev/label/root / ufs rw 1 1 /dev/label/swap none swap sw 0 0 My gpart: = 34 1250263661 ada0 GPT (596G) 34 1024 1 freebsd-boot (512k) 1058 990 - free - (495k) 2048 1228931072 2 freebsd-ufs (586G) 1228933120 21330575 3 freebsd-swap (10G) Hi Matt I'm far from anything near an expert on file systems but I'd suggest you remove softupdates and leave journaling on. tunefs -n disable There's no need to have both on and although I agree that both SHOULD work together there's no reason to have them on together. It will only slow down writes to the file system. Effectively soft updates was a go-between before journalin was introduced. //Clay ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 9.1 RELENG_9 Unable to cleanly dismount root partition on shutdown
On 27.08.2012 11:15, Matt Smith wrote: On 2012-08-27 10:25, c...@milos.co.za wrote: I'm far from anything near an expert on file systems but I'd suggest you remove softupdates and leave journaling on. tunefs -n disable There's no need to have both on and although I agree that both SHOULD work together there's no reason to have them on together. It will only slow down writes to the file system. Effectively soft updates was a go-between before journalin was introduced. Really? This is SU+J journalling that I'm using. Not gjournal. Surely SU+J does require softupdates to be on as it's part of the same thing? Output from tunefs -p: tunefs: soft updates: (-n) enabled tunefs: soft update journaling: (-j) enabled tunefs: gjournal: (-J) disabled I saw that you had soft updates and soft updates journaling in your original email. What you have is correct. That is how 9.x sets up the FS by default nowadays. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
