Marko Cupać | 18 Aug 15:09 2015

ping from web application

Hi,

I use web applicaton (net-mgmt/phpipam) which should have the ability
to check hosts' availability via ping. I can even specify path to ping
executable.

This functionality does not work on FreeBSD by default, and suggested
workaround is to set setuid bit on /sbin/ping.

I don't like to modify permissions of base files. Is there an
alternative solution? e.g. a port?

Thank you in advance,
--

-- 
Marko Cupać
https://www.mimar.rs/
_______________________________________________
freebsd-stable <at> freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"
Damien Fleuriot | 17 Aug 18:22 2015

[POSSIBLE BUG] 10-STABLE CARP erroneously becomes master on boot

Hello list,

I'm seeing this very peculiar behaviour between 2 10-STABLE boxes.

Host A is CARP Master with advskew 20 and runs 10.2-BETA1 from 10/07
Host B is CARP Backup with advskew 150 and runs 10.2-PRERELEASE from 12/08

When I configure CARP in rc.conf on host B, it becomes Master on boot, and
host A remains Master as well.
When I force a state change on host B (ifconfig vlanx vhid y state backup),
it transitions to Backup then again to Master.

When I comment out the CARP configuration in rc.conf , and configure CARP
manually on host B's interfaces after it boots, it correctly becomes and
remains Backup.

Below is the excerpt from rc.conf pertaining to CARP configuration, the
only difference between the 2 hosts being their advskew.

Host A
== BEGIN

ifconfig_vlan410_alias0="vhid 110 pass passhere advskew 20 alias
10.104.10.251/32"

== END

Host B
== BEGIN

(Continue reading)

Daniel Braniss | 17 Aug 09:27 2015
Picon
Picon

ix(intel) vs mlxen(mellanox) 10Gb performance

hi,
	I have a host (Dell R730) with both cards, connected to an HP8200 switch at 10Gb.
	when writing to the same storage (netapp) this is what I get:
		ix0:		~130MGB/s
		mlxen0	~330MGB/s
	this is via nfs/tcpv3

	I can get similar (bad) performance with the mellanox if I increase the file size
	to 512MGB.
	so at face value, it seems the mlxen does a better use of resources than the intel.
	Any ideas how to improve ix/intel’s performance?

	cheers,
		dnny

_______________________________________________
freebsd-stable <at> freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"
Cy Schubert | 17 Aug 07:49 2015

Re: 10.2: ntp update breaks DCF77 clock

In message <1439744220.242.87.camel <at> freebsd.org>, Ian Lepore writes:
> 
> 
> --=-yOSDvPzQIQnw2oRARoLp
> Content-Type: text/plain; charset="us-ascii"
> Content-Transfer-Encoding: 7bit
> 
> On Sun, 2015-08-16 at 08:10 +0100, Matthew Seaman wrote:
> > On 15/08/2015 16:46, Christian Weisgerber wrote:
> > > The ntp code is not very transparent, but I think the root cause
> > > are the ntp/config.h changes that came with the 4.2.8p3 update.  A
> > > number of previously disabled obscure clock drivers were enabled,
> > > but crucially CLOCK_RAWDCF was disabled, and this is the PARSE
> > > subdriver needed to use the popular DCF77 serial receivers.
> > > 
> > > Frankly, it looks like we used to have a carefully considered
> > > selection of clock drivers which has been blindly splattered with
> > > the upstream defaults in the last update.
> > 
> > Hmmm.... I suggest raising a PR with patches to revert the changes in
> > the set of enabled clock drivers (or merge with the current list).  It's
> > not going to get you a working DCF77 receiver in a -RELEASE version any
> > time soon, I'm afraid, as you'll have to wait until the next release for
> > the changes to percolate down, but having a sensible list of enabled
> > clock drivers in base is definitely a good move.
> > 
> 
> I wonder: is there a reason to not enable all (or most of) the refclocks
> in base and in ports?  Well, at least all the ones that build on
> freebsd... a disturbing number of them fail to compile because they
(Continue reading)

Christian Kratzer | 16 Aug 19:16 2015
Picon

freebsd-update to 10.2-RELEASE broken ?

Hi,

I have been trying to update several of my FreeBSD 10.1 amd64 VM to 10.2-RELEASE with freebsd-update and
have been failing with an incorrect hash error.

This is what happens with a plain vanilla 10.1-RELEASE vm when I try to update to 10.2-RELEASE

--snipp--
root <at> test10:~ck # uname -a
FreeBSD test10.cksoft.de 10.1-RELEASE FreeBSD 10.1-RELEASE #0 r274401: Tue Nov 11 21:02:49 UTC 2014    
root <at> releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64
root <at> test10:~ck # freebsd-update upgrade -r 10.2-RELEASE
Looking up update.FreeBSD.org mirrors... none found.
Fetching metadata signature for 10.1-RELEASE from update.FreeBSD.org... done.
Fetching metadata index... done.
Inspecting system... done.

The following components of FreeBSD seem to be installed:
kernel/generic world/base world/doc world/games world/lib32

The following components of FreeBSD do not seem to be installed:
src/src

Does this look reasonable (y/n)? y

Fetching metadata signature for 10.2-RELEASE from update.FreeBSD.org... done.
Fetching metadata index... done.
Fetching 1 metadata patches. done.
Applying metadata patches... done.
Fetching 1 metadata files... done.
(Continue reading)

Chris Anderson | 15 Aug 20:47 2015
Picon

libopie problems after upgrade to 10.2

just upgraded from 10.1-RELEASE-p16 to 10.2-RELEASE using freebsd-update.

after the upgrade, I began getting errors because pam_opie.so.5 has an
unsatisfied link to libopie.so.7 (my system only has libopie.so.8).

I notice a fresh install of 10.2-RELEASE does indeed contain libopie.so.7,
so I'm curious how I managed to get into this state in the first place and
whether it is anything I should worry about. This machine has only been
upgraded using freebsd-update and I'm pretty sure it started from
10.0-RELEASE.

I have temporarily worked around with an entry in libmap.

Here are the files involved:

# ls -l /usr/lib/pam_opie*
lrwxr-xr-x  1 root  wheel    13 Sep 27  2013 /usr/lib/pam_opie.so ->
pam_opie.so.5
-r--r--r--  1 root  wheel  7000 Aug 14 11:56 /usr/lib/pam_opie.so.5
lrwxr-xr-x  1 root  wheel    19 Sep 27  2013 /usr/lib/pam_opieaccess.so ->
pam_opieaccess.so.5
-r--r--r--  1 root  wheel  5568 Aug 14 11:56 /usr/lib/pam_opieaccess.so.5

# ls -l /usr/lib/libopie*
-r--r--r--  1 root  wheel  84582 Aug 14 11:57 /usr/lib/libopie.a
lrwxr-xr-x  1 root  wheel     12 Sep 29  2014 /usr/lib/libopie.so ->
libopie.so.8
-r--r--r--  1 root  wheel  38280 Oct  5  2014 /usr/lib/libopie.so.8
-r--r--r--  1 root  wheel  88048 Aug 14 11:57 /usr/lib/libopie_p.a
_______________________________________________
(Continue reading)

Christian Weisgerber | 15 Aug 17:46 2015
Picon

10.2: ntp update breaks DCF77 clock

I have a little Soekris box whose ONLY task is to get the time from
a simple DCF77 time signal receiver and redistribute it with NTP.
The update from 10.1 to 10.2 has broken this functionality.

The relevant ntp.conf configuration...

server 127.127.8.0 mode 14
fudge 127.127.8.0 time1 0.235

... now results in the obscure error message:

PARSE receiver #0: parse_start: parse_setfmt() FAILED.

The ntp code is not very transparent, but I think the root cause
are the ntp/config.h changes that came with the 4.2.8p3 update.  A
number of previously disabled obscure clock drivers were enabled,
but crucially CLOCK_RAWDCF was disabled, and this is the PARSE
subdriver needed to use the popular DCF77 serial receivers.

Frankly, it looks like we used to have a carefully considered
selection of clock drivers which has been blindly splattered with
the upstream defaults in the last update.

I don't know how to proceed here.  The system ntpd is broken.  The
ntpd in ports also doesn't enable this clock type by default, so
no package.  The whole raison d'être for this setup was to have a
maintenance-free NTP server that does not require custom compiling
ntpd.  *sigh*

--

-- 
(Continue reading)

Tim Daneliuk | 14 Aug 15:15 2015

Swap Questions

I just built a 10.2 machine on a cloud-based VPS (Digital Ocean) that has
512M of memory and 1G of swap partition.  I am seeing a ton of errors like
this:

Aug 14 00:01:22 myhost kernel: swap_pager_getswapspace(10): failed
Aug 14 00:01:22 myhost kernel: swap_pager_getswapspace(14): failed
Aug 14 00:01:22 myhost kernel: swap_pager_getswapspace(11): failed
Aug 14 00:01:22 myhost kernel: swap_pager_getswapspace(6): failed
Aug 14 00:01:22 myhost kernel: swap_pager_getswapspace(7): failed
Aug 14 00:01:22 myhost last message repeated 2 times

So, I added this to fstab (after creating /usr/swap0):

md99	none	swap	sw,file=/usr/swap0	0	0

And then did this:

swapon -aq

But, when I do a swapinfo, all I can see is the "disk" swap partition
that comes standard with the VPS:

Device          1K-blocks     Used    Avail Capacity
/dev/gpt/swapfs   1048576   456572   592004    44%

Two questions:

1) Is this reasonable behavior from  a machine wiht 512M of memory and
   a 1G swap partition?  I am doing things like running clamscan and
   buildworld at the same time. That's why I tried to add space with
(Continue reading)

Aristedes Maniatis | 14 Aug 07:58 2015
Picon

merging commiter headers

I've just upgraded three machines from 10.1 to 10.2. Congratulations on the release...

This was one of the worst upgrade experiences in my FreeBSD history, going back to 4.0 days. I used
freebsd-update but I was absolutely swamped with merging the svn (nee cvs) headers in roughly 80 files.

<<<<<<< current version
# $FreeBSD: release/10.0.0/etc/periodic/security/800.loginfail 254974 2013-08-27 21:20:28Z jlh $
=======
# $FreeBSD: releng/10.2/etc/periodic/security/800.loginfail 263661 2014-03-23 12:58:48Z brueffer $
>>>>>>> 10.2-RELEASE

Let's leave aside why users would care what commit number, date or user last touched this file. Let's assume
that you don't need a header to tell you the path of the file you are looking at. And let's leave aside why
release is now releng (are we saving bytes?). And let's leave aside why the diff shows an upgrade from 10.0
to 10.2 when actually this was from 10.1 to 10.2.

Can't some merge tool inside freebsd-update just sort this out for me? Please? Not only does it take over 45
minutes to go through all those files, but I feel sure I missed something.

Ari

--

-- 
-------------------------->
Aristedes Maniatis
ish
http://www.ish.com.au
Level 1, 30 Wilson Street Newtown 2042 Australia
phone +61 2 9550 5001   fax +61 2 9550 4001
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
_______________________________________________
(Continue reading)

jenkins-admin | 13 Aug 06:04 2015
Picon

FreeBSD_stable_10 - Build #1616 - Failure

FreeBSD_stable_10 - Build #1616 - Failure:

Build information: https://jenkins.FreeBSD.org/job/FreeBSD_stable_10/1616/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_stable_10/1616/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_stable_10/1616/console

Change summaries:

No changes

The end of the build log:

Started by an SCM change
Started by an SCM change
Building remotely on jenkins-10.freebsd.org (FreeBSD-10) in workspace /builds/FreeBSD_stable_10
Updating svn://svnmir.freebsd.org/base/stable/10 at revision '2015-08-13T03:51:09.950 +0000'
FATAL: java.io.IOException: Unexpected termination of the channel
hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
	at hudson.remoting.Request.abort(Request.java:296)
	at hudson.remoting.Channel.terminate(Channel.java:815)
	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69)
	at ......remote call to jenkins-10.freebsd.org(Native Method)
	at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1361)
	at hudson.remoting.Request.call(Request.java:171)
	at hudson.remoting.Channel.call(Channel.java:752)
	at hudson.FilePath.act(FilePath.java:980)
	at hudson.FilePath.act(FilePath.java:969)
	at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:897)
	at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:833)
	at hudson.scm.SCM.checkout(SCM.java:485)
(Continue reading)

dweimer | 12 Aug 20:09 2015
Picon

Possible Error in the FreeBSD 10.2 Release Notes/Man page for TCP

I was reading through the Release notes, and decided to enable 
net.inet.tcp.pmtud_blackhole_detection in my test environment. It 
appears that the monitoring tunable 
net.inet.tcp.pmtud_blackhole_min_activated is incorrectly listed. Using 
sysctl -a | grep net.inet.tcp.pmtud, doesn't show it as a result. The 
test system is running RC3 built on the 7th from revision 286391 of the 
https://svn.freebsd.org/base/releng/10.2 tree.

root <at> freebsd:/usr/src # sysctl -a | grep net.inet.tcp.pmtud
net.inet.tcp.pmtud_blackhole_mss: 1200
net.inet.tcp.pmtud_blackhole_failed: 0
net.inet.tcp.pmtud_blackhole_activated_min_mss: 0
net.inet.tcp.pmtud_blackhole_activated: 0
net.inet.tcp.pmtud_blackhole_detection: 1

I did confirm that the pmtud_blackhole_min_activated option is also 
listed in the tcp(4) man page page as well.

If anyone is more familiar with this than I am can they look into seeing 
if there is indeed an error, or if I am missing something here.

--

-- 
Thanks,
    Dean E. Weimer
    http://www.dweimer.net/
_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"

(Continue reading)


Gmane